Database Develop

[Recovery][TWRP3][ALL] Main thread of TWRP for Xperia E1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Unlocking Bootloader/Root/Recovery (Required)
Just follow steps from Sony Developer World Mobile
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
1 - Make sure you have a Recovery pre-installed (via boot partition or bootstrap hack) and Bootloader Unlocked
2 - Download the latest version
3 - Flash it via your recovery
Now you ask "i still have the CWM Philz, what to do?"
You will need a custom kernel with support to load recovery from FOTAKernel, check this
For now only one Custom Kernel support it, the FalconSS Kernel
4 - Flash FalconSSKernel or any other Kernel with this support via recovery
5 - And Enjoy!!!
TWRP3 - Support from Stock KitKat to CM14.1 Based- Zip Flashable - https://www.androidfilehost.com/?fid=457095661767133664
Support: All Xperia E1 Variants
How to get into recovery: The LEDs will flash green, in this moment you can press Volume buttons and wait, you will see a Blue/Cyan color in LEDs, you will enter iin recovery.[/B]
No issues related to TWRP3 (If you found someone, just report. Thanks!)
https://github.com/TeamVee-SS

Great work

nvt992 said:
Great work
Click to expand...
Click to collapse
Thanks

Caio99BR said:
Thanks
Click to expand...
Click to collapse
why only 2.8.1?
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
why only 2.8.1?
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
We need to get CM11 working, so TWRP of Android KK branch, after get this working we will go to CM12.1 and TWRP of Android LP Branch and by last TWRP3 of MM branch.
Understand?

The device tree?
GITHUB?

porcha18 said:
The device tree?
GITHUB?
Click to expand...
Click to collapse
Oh sorry, i will update thread.

Wtf? I can't boot into 3.x... I have 2.8 (R1) installed, the. zip doesn't work and the image file in Rasher won't work either. I have FalconSS kernel installed, (of course) TWRP 2.8 and Sony Xperia E1 Stock Lite but I cannot get this to work. Fastboot I'm also having problems with; the drivers are being a fricken pain in the ass rn... If someone could link me the offical drivers that would be awesome thanks

xeonyt12 said:
Wtf? I can't boot into 3.x... I have 2.8 (R1) installed, the. zip doesn't work and the image file in Rasher won't work either. I have FalconSS kernel installed, (of course) TWRP 2.8 and Sony Xperia E1 Stock Lite but I cannot get this to work. Fastboot I'm also having problems with; the drivers are being a fricken pain in the ass rn... If someone could link me the offical drivers that would be awesome thanks
Click to expand...
Click to collapse
In Flashtool you can find Shuang (MSM8210/MSM8610) drivers, and also Sony generic drivers that will work

Kizoky said:
In Flashtool you can find Shuang (MSM8210/MSM8610) drivers, and also Sony generic drivers that will work
Click to expand...
Click to collapse
@Kizoky For some reason, those drivers won't install... it just says 'Drivers Failed to install'; no error code or anything.... idk anymore

Wow TWRP 3.0:victory:
You're one of the best dev of this forum thank you bro :highfive:
EDIT : erm, big fail, i forgot to wipe chache/dalvik any idea to get out of this situation ? Bc now twrp 3.0 won't boot

MrGunBest said:
Wow TWRP 3.0:victory:
You're one of the best dev of this forum thank you bro :highfive:
EDIT : erm, big fail, i forgot to wipe chache/dalvik any idea to get out of this situation ? Bc now twrp 3.0 won't boot
Click to expand...
Click to collapse
I will try to fix it, sorry, i said it is in wip, the recovery works but not pass of TeamWin screen, why idk.

Caio99BR said:
I will try to fix it, sorry, i said it is in wip, the recovery works but not pass of TeamWin screen, why idk.
Click to expand...
Click to collapse
NP bro'
everybody do some fails, but i'm sure you'll make it boot:fingers-crossed:

btw guys do you have 2 recoveries ,cwm and twrp ,too?

sad2kac said:
btw guys do you have 2 recoveries ,cwm and twrp ,too?
Click to expand...
Click to collapse
Actualy, the dual recovery exploit, use the bootstrap folder into the root of the storage to boot a recovery without having a UB, then if you want a PhilZ and TWRP, you unlock your BL, flash TWRP 2.8, Caio kernel AND THEN you have dual recovery

Ok, so far I got TWRP flashed, but the problem is it shows the TWRP start logo, but doesn't boot to the UI/Options. I waited for 15 minutes and it didn't boot. Hope this can get fixed

xeonyt12 said:
Ok, so far I got TWRP flashed, but the problem is it shows the TWRP start logo, but doesn't boot to the UI/Options. I waited for 15 minutes and it didn't boot. Hope this can get fixed
Click to expand...
Click to collapse
As he said, he havn't tested the recovery

Tested on R0r2 FalconSS Kernel, TWRP 3.0 Passed on Recovery but not on UI/Option on Xperia E1 (D2005). Hope it can be fixed. Good work though.

TWRP 2.8.1.0 R2 is on!
Fixed font size
Fixed device set
Partially fixed mtp
Removed default max brightness
I think so
Not is really NEED to update, but is more good than the previous release
You still need FalconSSKernel or kernel compatible with load FOTAKernel ramdisk

Caio99BR said:
TWRP 2.8.1.0 R2 is on!
Fixed font size
Fixed device set
Partially fixed mtp
Removed default max brightness
I think so
Not is really NEED to update, but is more good than the previous release
You still need FalconSSKernel or kernel compatible with load FOTAKernel ramdisk
Click to expand...
Click to collapse
Does this include the new kernel compression stuff?

[RECOVERY] Team Win Recovery Project (TWRP)

Team Win Recovery Project 3.x​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
One recovery to rule them all:
The common TWRP is compatible with GT-P3100, GT-P3110, GT-P3113, GT-P5100, GT-P5110 and GT-P5113 at the same time.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or lost Data!
* Please do some research if you have any concerns about this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* If you dont like this recovery: Stay away from this thread!
*/
Download:
http://andi34.github.io/recoveries_tab2.html
Note:
The new "Common TWRP" won't be able to flash Roms compiled before 22.03.2016.
Important links:
https://twrp.me - official TWRP page
https://twrp.me/FAQ - official FAQ
http://andi34.github.io/faq.html - FAQ by myself
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA:DevDB Information
[unified] TWRP, Tool/Utility for the Samsung Galaxy Tab 2
Contributors
Android-Andi
Version Information
Status: Stable
Created 2016-09-18
Last Updated 2016-09-18

Reserved
DEVICE SPECIFIC TWRP
Device specific TWRP are discontinued!
Please note: our kernel detects your Tab2 variant at boot and chooses the right driver and config for your device! In some cases (e.g. if the mainboard or the screen got replaced) your device variant isn't detected right and it will use wrong driver!
I am not sure how many user are affected, but in such case we can skip the intelligent board detection and hardcode the variant.
Attached device specific TWRP should work to flash latest Android 7 builds.
Feel free to buy me a coconut water if it helped you to keep your Tab still, after many years, almost up to date.

Old recovery threads have been closed because device specific recoveries are discontinued and cwm & philz touch are not maintained anymore.
Let's keep this thread on topic here please:
- No rom questions
- no questions about other recoveries
- make sure posting a recovery.log, maybe dmesg if you have issues on this common twrp
~ All my work, news etc. on http://andi34.github.io ~

Thank you Andi for your kindness... I don't see twrp 3.0.2.5 in your files. Is it OK to install it

zidane01 said:
Thank you Andi for your kindness... I don't see twrp 3.0.2.5 in your files. Is it OK to install it
Click to expand...
Click to collapse
Yeah, it is ok. I'll upload it tomorrow to androidfilehost. It was a quick test to check if eMMC 4.5 work fine (some tab2 seem to have newer emmc, because of that current twrp wasn't able to use the emmc and flashing wasn't possible. Its also the reason why latest builds don't boot on some tab2 and getting only a black screen).
~ All my work, news etc. on http://andi34.github.io ~

hey man, thank you for the recovery and ROM. I am currently running the official kitkat cyanogenmod on the old recovery. So to install and use this recovery, do I just flash it using the current recovery, or is there some other steps i need to follow?

arnavb8 said:
hey man, thank you for the recovery and ROM. I am currently running the official kitkat cyanogenmod on the old recovery. So to install and use this recovery, do I just flash it using the current recovery, or is there some other steps i need to follow?
Click to expand...
Click to collapse
right, you can flash it with your current recovery (if you download the zip)

arnavb8 said:
hey man, thank you for the recovery and ROM. I am currently running the official kitkat cyanogenmod on the old recovery. So to install and use this recovery, do I just flash it using the current recovery, or is there some other steps i need to follow?
Click to expand...
Click to collapse
Just flash it via current recovery :good:

Hello! Thank you for your good work, Android-Andi
Anyway, I'm just asking. Does everytime I update my CM13, do I also need to re-flash the Common TWRP? (Flash TWRP > Update CM13 > Flash TWRP again)

Kursem said:
Hello! Thank you for your good work, Android-Andi
Anyway, I'm just asking. Does everytime I update my CM13, do I also need to re-flash the Common TWRP? (Flash TWRP > Update CM13 > Flash TWRP again)
Click to expand...
Click to collapse
no not needed

Perfect & faster recovery 3.0.2-6.... Works very correctly for me ... Ty Andi

TWRP 3.0.2-7 uploaded
- Update the ext-csd.rev check for eMMC5.1 (fixes emmc detection for some tab2)

Hey everyone., how to install twrp in tablet,,?

jimwel said:
Hey everyone., how to install twrp in tablet,,?
Click to expand...
Click to collapse
Do u know how to use Odin?
If yes, flash twrp using Odin

ok, I know how to use odin, but am I flashing the twrp tar.md5 file only or is there something else I'm supposed to be flashing? can't find a thorough guide for rooting the galaxy tab 2 7.0 p3113

You can read here
BlaineLondon said:
ok, I know how to use odin, but am I flashing the twrp tar.md5 file only or is there something else I'm supposed to be flashing? can't find a thorough guide for rooting the galaxy tab 2 7.0 p3113
Click to expand...
Click to collapse
http://forum.xda-developers.com/sitesearch.php?q=How to root p3113 (here is wrong thread for this )
---------- Post added at 18:55 ---------- Previous post was at 18:47 ----------
jimwel said:
Hey everyone., how to install twrp in tablet,,?
Click to expand...
Click to collapse
Take zip twrp , sent zip to SD & install via recovery...Or take .tar-md5 file and flash it with Odin... From here by Andi : https://andi34.github.io/recoveries_tab2.html (you must read first)

Windows Defender detected a Trojan in the latest TWRP zip (3.0.2-8).
https://www.androidfilehost.com/?w=...d44fd3d141077f60723133fd33b53c552b55892a840a0
Not sure if it's a false positive, or if maybe the Android File Host mirror was infected.
Update: I searched the md5 in VirusTotal and it came up clean
https://www.virustotal.com/en/file/...86575991df34d1ebd93aaf4a6fea9bf9f4c/analysis/
I also redownloaded the zip file a 2nd time, with no virus warning. So looks like it was a false alarm.

I use 3.0.3-0 .... Excellent ! Thanks Andi

I have tried the common 3.0.3-0 on my tab 2 7.0 (p3110) but it installs larger than the screen and the touch wont work, connected mouse to OTG but nothing would work. ended up forcing a shutdown and reflash old version.

peeko1979 said:
I have tried the common 3.0.3-0 on my tab 2 7.0 (p3110) but it installs larger than the screen and the touch wont work, connected mouse to OTG but nothing would work. ended up forcing a shutdown and reflash old version.
Click to expand...
Click to collapse
Sounds like your bootloader makes trouble.
Edit:
https://androidfilehost.com/?w=files&flid=37700
Flash the one for your device using Odin.
Gesendet von meinem A0001 mit Tapatalk

[TOOL][TISSOT]Tissot Suite V2.0 [Remove Bootloader Unlock Warning][Backup Partitions]

Hi Guys
Today i'm Presenting Tissot Suite V2.0
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features & Info:​
-Veriffy the Deivce (ADB recognized)
-Unlock Bootloader
-Boot TWRP 3.2.1-2 Recovery
-Remove Bootloader Unlocked Warning
-Backup your Partitions
-Pull, edit, flash build.prop
- Pull apk from system
- Boot in Bootloader mode.
- Backup Modem to Internal Storage
- Flash Modem from Backup
- Reboot bootloader.
-Go to recovery.
-Reboot the Phone.
-Flash Partitions From Backup
-Restore Stock Original Splash Image
-Flash Stock Rom and Lock Your Bootloader Auto (You need to place the files in folder ,This is Beta Feature i Haven't tested yet...)
Instructions:
1.Unpack the Tools Zip
2.Run the Tissot_Suite.bat
3.Connect the Device
Download:​
Get It​
Issues:​
I dont know of any, you tell me.​
Donate:​
You can Support This Project for Next Release with Paypal Donations for my Work ,List with People who Donated will be posted in this OP.​
P.S If you like the Tool smash the Thanks Button​
Enjoy!​
XDA:DevDB Information
[TOOL][TISSOT]Tissot Suite V2.0 [Remove Boot Warning] [Bootloader-Unlock][Backup].etc, Tool/Utility for the Xiaomi Mi A1
Contributors
Alek Dev
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2018-04-14
Created 2018-04-14
Last Updated 2018-04-15

Changelog:​
Version 2.0​-Remove Bootloader Unlocked Warning
-Flash Partitions From Backup
-Restore Stock Original Splash Image
-Flash Stock Rom and Lock Your Bootloader Auto (You need to place the files in folder ,This is Beta Feature i Haven't tested yet...)
Version 1.0​-First Release

Thank you so much dude.Hope you will be able to add imei flash and backup tool soon.:good:

You can add the feature to flash stock rom

Any Linux version

??????

Today coming new version with new feature to remove the Bootloader Unlocked Watermark [emoji6]
Sent from my Mi A1 using Tapatalk

Alek Dev said:
Today coming new version with new feature to remove the Bootloader Unlocked Watermark [emoji6]
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Oh, wow. May I ask how is that possible?

UPDATE!!!:​
Version 2.0​-Remove Bootloader Unlocked Warning
-Flash Partitions From Backup
-Restore Stock Original Splash Image
-Flash Stock Rom and Lock Your Bootloader Auto (You need to place the files in folder ,This is Beta Feature i Haven't tested yet...)
Download:​​
Get It​

Alek Dev said:
Today coming new version with new feature to remove the Bootloader Unlocked Watermark [emoji6]
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Wonderfull,
May i ask how the tool proceed to remove the warning?

Alek Dev said:
UPDATE!!!:
Version 2.0​-Remove Bootloader Unlocked Warning
-Flash Partitions From Backup
-Restore Stock Original Splash Image
-Flash Stock Rom and Lock Your Bootloader Auto (You need to place the files in folder ,This is Beta Feature i Haven't tested yet...)
Download:
Get It​
Click to expand...
Click to collapse
Getting permission denied error while backing up partitions also I'm not able to pull apk from device it is also giving error

Midomad said:
Wonderfull,
May i ask how the tool proceed to remove the warning?
Click to expand...
Click to collapse
I make custom splash which removes the bootloader warning and the tool first erases the splash then updates with the new one... that's it
Sent from my Mi A1 using Tapatalk

gthakur said:
Getting permission denied error while backing up partitions also I'm not able to pull apk from device it is also giving error
Click to expand...
Click to collapse
Run as Admin the Tissot suite bat also enable developer options and check Allow usb debugging that will work you will get some prompt and check that Yes
Sent from my Mi A1 using Tapatalk

Alek Dev said:
Run as Admin the Tissot suite bat also enable developer options and check Allow usb debugging that will work you will get some prompt and check that Yes
Click to expand...
Click to collapse
Sir getting this type of error while pulling apk from bat file . I am running it as administrator.
Thanks for your time

gthakur said:
Sir getting this type of error while pulling apk from bat file . I am running it as administrator.
Thanks for your time
Click to expand...
Click to collapse
Thank you i will check and fix[emoji6]
Sent from my Mi A1 using Tapatalk

Remove Bootloader Unlocked working fine..
Thanks for the Tool

Nice.. thanks for sharing buddy

try removing unlock bootloader splash, and it work.
But the animations is to slow, not blink up like stock.

gusbalaa said:
try removing unlock bootloader splash, and it work.
But the animations is to slow, not blink up like stock.
Click to expand...
Click to collapse
Yeah stays black at the part when says Bootloader warning this is the reason i was thinking to replace that part but it's very hard...
Sent from my Mi A1 using Tapatalk

Thanks for this! I do have 2 concerns.
1.
Code:
adb reboot bootloader
TIMEOUT /T 10 /NOBREAK
Is not necessary. Issuing a fastboot command will wait for the device to get into fastboot and will perform the command once it's there.
2.How were you able to fix the splash.img? Some folsk were trying to get the bootloader unlocked warnings removed but no one has succeeded so far. I'll try out your splash image a bit later to see if it's removed all of them.
Edit - Yes, it did remove all bootloader warnings.

[LOCKED BOOTLOADER] Temporary TWRP3.3.1 for Samsung Galaxy S7Edge (Snapdragon) G935XX

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
DOWNLOAD:
Download TWRP from here
HOW DO I ENTER RECOVERY:
- Flash ENG OREO RECOVERY via Odin in AP slot
- Reboot into recovery
If you are on android 8.0 and this is first time using this TWRP you need to install modified fstab.qcom into /system/vendor/etc if not you will fall into encryption issues
WARNING: this require data wipe otherwise skip over next step
- Windows user: Run fstab.bat
- Linux user: Run fstab.sh in terminal
- Wipe data/factory reset
To enter TWRP recovery
- Windows: Run twrp.bat
- Linux: Run twrp.sh in terminal
BUGS:
- MTP
THANKS:
@jrkruse for most stuff, guides and help
Hashcode
TWRP team
jcadduono for device tree

reserved

Wait can we flash roms now?

Leone/kyleproxx said:
Wait can we flash roms now?
Click to expand...
Click to collapse
Why not, but dont flash custom recovery/boot img we still locked

afaneh92 said:
Why not, but dont flash custom recovery/boot img we still locked
Click to expand...
Click to collapse
Um it doesn't work for my sprint s7 edge, it a on bootloader 7 btw
Edit: when I try to flash in odingbit says fuse 2 binary 1

Leone/kyleproxx said:
Um it doesn't work for my sprint s7 edge, it a on bootloader 7 btw
Edit: when I try to flash in odingbit says fuse 2 binary 1
Click to expand...
Click to collapse
Your recovery partition fused on B2 you cant flash recovery from older Rev.

afaneh92 said:
Your recovery partition fused on B2 you cant flash recovery from older Rev.
Click to expand...
Click to collapse
would you be able to fix it so i can?

Wait, what is this if the bootloader is locked?

rlewis312010 said:
Wait, what is this if the bootloader is locked?
Click to expand...
Click to collapse
I think this allows you to install roms even with the locked bootloader
Edit: if you are willing to try this try installing one of the port roms for snapdragon

Leone/kyleproxx said:
would you be able to fix it so i can?
Click to expand...
Click to collapse
If there ENG recovery with rev2 you can run it
Leone/kyleproxx said:
I think this allows you to install roms even with the locked bootloader
Edit: if you are willing to try this try installing one of the port roms for snapdragon
Click to expand...
Click to collapse
As I said before skip installing custom boot/recovery img

afaneh92 said:
If there ENG recovery with rev2 you can run it
As I said before skip installing custom boot/recovery img
Click to expand...
Click to collapse
Could I build a recovery myselft?

Flagged as Virus in Windows Defender
Windows flagged both downloads as Trojans (Win32/Spursint.F!cl) Has anyone else downloaded with this warning or did AFH get spammed?

Sagoode said:
Windows flagged both downloads as Trojans (Win32/Spursint.F!cl) Has anyone else downloaded with this warning or did AFH get spammed?
Click to expand...
Click to collapse
I was able to download but I cant install because of fuse 2 binary 1 error

i got this to work and actually flashed the norma s9+ port from hillary trump on my g935t. (after removing the kernel insall lines from the updater script) since the rom was made for the 9350 it was VERY buggy/laggy. BUT IT DID BOOT UP!!!!!:laugh::laugh::laugh::laugh:
now we just need someone to build us a rom...:good:

bigTINY779 said:
i got this to work and actually flashed the norma s9+ port from hillary trump on my g935t. (after removing the kernel insall lines from the updater script) since the rom was made for the 9350 it was VERY buggy/laggy. BUT IT DID BOOT UP!!!!!:laugh::laugh::laugh::laugh:
now we just need someone to build us a rom...:good:
Click to expand...
Click to collapse
And to make a rev 2 eng recovery file so u can install twrp

Leone/kyleproxx said:
And to make a rev 2 eng recovery file so u can install twrp
Click to expand...
Click to collapse
the one provided here worked for me

bigTINY779 said:
the one provided here worked for me
Click to expand...
Click to collapse
Read the conversations above from beginning to ed then ull understand

I'm also getting fuse 2 > binary 1 when I try to flash it.
Wish I had not installed the updates a few days ago. :/

bigTINY779 said:
i got this to work and actually flashed the norma s9+ port from hillary trump on my g935t. (after removing the kernel insall lines from the updater script) since the rom was made for the 9350 it was VERY buggy/laggy. BUT IT DID BOOT UP!!!!!:laugh::laugh::laugh::laugh:
now we just need someone to build us a rom...:good:
Click to expand...
Click to collapse
Try flashing magisk and see if we now have a new root alternative
---------- Post added at 10:18 AM ---------- Previous post was at 10:16 AM ----------
@jrkruse could you make a rev 2 ENG Oreo recovery?

Leone/kyleproxx said:
Try flashing magisk and see if we now have a new root alternative
---------- Post added at 10:18 AM ---------- Previous post was at 10:16 AM ----------
@jrkruse could you make a rev 2 ENG Oreo recovery?
Click to expand...
Click to collapse
Please stop posting things you dont know about!
We cant make stock recovery, samsung do.
Also you cant flash custom boot.img or modify it by any root method. Only boot.img or recovery.img signed by samsung can be flashed.

[CLOSED][ROM][12][BETA] LineageOS 19.1 for Samsung Galaxy A3 2017 (a3y17lte) (SM-A320F)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before installing the ROM https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
What works :
-you tell me
Bugs :
Camera 1080p video recording lag
not working codec2: (disabled)
no working gps
no working Bluetooth headset mic in calls
no working fingerprint
vsync is in the future
selinux permissive
broken drm (widevine)
Keep in mind that some LineageOS features have not been completed yet this is not a device bug and please do not report those
in this rom thread, also do not post bug reports for known issues or bug reports without proper
a) Logcat
b) proc/last_kmsg (or proc/kmsg)
c) data/tombstones
d) dmesg
0. [RECOMMENDED] Make sure you have an Oreo bootloader and modem before installing this. (ie : you have been in stock oreo once)
1. [RECOMMENDED] Do a good backup first
2. [ONCE] Make sure you did flash the inital Astrako's repartition script (https://forum.xda-developers.com/t/tool-a320fl-f-y-repartition-script-for-vendor-support.3951105/) to create a vendor partition.
Flashing this script will install (an old) TWRP.
3. Make sure you are using TWRP 3.7.0 (mentionned below)
4. [OPTIONAL/ONCE] Flash my custom repartition script (https://t.me/debieLineageOS/180) to shrink partition sizes, then format data.
6. [CLEAN FLASH] In recovery wipe everything except SD and OTG.
7. Flash LineageOS.
8. [OPTIONAL] Flash MindtheGApps .
9. [OPTIONAL] Flash Magisk.
10. Reboot. Booting should take less than 3 mins.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Note : Flashing a repartition script should only be done once (unless you flash stock or the pit file which revert them) unless a release not say so.
Install gapps right after installing the rom itself don't try to boot to system before that if you want to use gapps (Or wipe data before installing them)
Download :
androidfilehost
Made by : @Flominator Astrako and @GonicTEAM @TheObcd
Device trees : https://github.com/samsungexynos7870/android_device_samsung_a3y17lte/tree/lineage-19.1-oss_bsp-vndk
ROM OS Version : Android 12.1
Kernel : 3.18
Telegram Support Group

Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?

Bernique said:
Thank you for this work.
Click to expand...
Click to collapse
that wasn't me

Bernique said:
I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
report bugs to @Flominator

F-Google said:
that wasn't me
Click to expand...
Click to collapse
Why do you create a thread then ? Since it is Flominator work, he could choose to or not to share his work here. What is the goal to share the work of another person without being able to help ?

Bernique said:
I cannot enter any more into recovery, it gives a loop on Orangefox screen.
Click to expand...
Click to collapse
It works fine with TWRP6.X .Flominator told us to use TWRP in telegram .

TheObcd said:
It works fine with TWRP6.X .Flominator told us to use TWRP in telegram .
Click to expand...
Click to collapse
yes, use twrp 3.70 from @Batuhantrkgl

Bernique said:
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download

@F-Google Pls add this as a waring in:
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before installing the ROM https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
- put (Beta) in thread title
this build has still a lot of bugs:
Camera 1080p video recording lag
not working codec2: (disabled)
no working gps
no working Bluetooth headset mic in calls
no working fingerprint
vsync is in the future
selinux permissive
broken drm (widevine)
- add bugs to buglist.
Initialy this was the reasone why I didnt post on xda yet.
- add step by step guide install instructions from stock rom to this for newbies like:
1. ...
2. ...
3. ...
as the install process is more way more complex than on other devices.
- provide a link of mindgapps mirror as they are reccomended by LineageOS themselves
-give astrako and gonic credits
best regards Flominator

Bernique said:
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
sorry to you, but the only fix is to reflash the recovery with pc.

Flominator said:
sorry to you, but the only fix is to reflash the recovery with pc.
Click to expand...
Click to collapse
Thank for your thoughts, but I was somehow aware of the risk, especially when there is no comment on the status of the development.
Thanks to all for the new TWRP, I missed this information

@F-Google thx for updateing the thread

F-Google said:
0. [RECOMMENDED] Make sure you have an Oreo bootloader and modem before installing this. (ie : you have been in stock oreo once)
1. [RECOMMENDED] Do a good backup first
2. [ONCE] Make sure you did flash the inital Astrako's repartition script (https://forum.xda-developers.com/t/tool-a320fl-f-y-repartition-script-for-vendor-support.3951105/) to create a vendor partition.
Flashing this script will install (an old) TWRP.
3. Make sure you are using OrangeFox R11.0 (https://forum.xda-developers.com/t/...f-y-orangefox-recovery-project-r11-0.4032121/) (or TWRP 3.6+ (https://t.me/debieLineageOS/1766) in case you use LineageOS18+).
4. Download the Lineage build (https://t.me/debieLineageOS/172), optionally GApps (https://opengapps.org/) and Magisk (https://github.com/topjohnwu/Magisk/releases).
5. [OPTIONAL/ONCE] Flash my custom repartition script (https://t.me/debieLineageOS/180) to shrink partition sizes, then format data.
6. [CLEAN FLASH] In recovery wipe everything except SD and OTG.
7. Flash LineageOS.
8. [OPTIONAL] Flash GApps (arm64, pico or nano only).
9. [OPTIONAL] Flash Magisk.
10. Reboot. Booting should take less than 3 mins.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
/!\ OTA builds do NOT guarantee dirty flashing will work fine. (Magisk can cause issues for instance)
Note : Flashing a repartition script should only be done once (unless you flash stock or the pit file which revert them) unless a release not say so.
Click to expand...
Click to collapse
May you not blindly copy past what I wrote in telegram ? This tutorial is about the LineageOS17 releases I share on github/telegram. Some sentences are not appropriated here. I let you correct them. Furthmore you're free to use control + k to insert link .
About OTA, I am not aware of Flominator doing so (but I may be wrong).

TheObcd said:
May you not blindly copy past what I wrote in telegram ? This tutorial is about the LineageOS17 releases I share on github/telegram. Some sentences are not appropriated here. I let you correct them. Furthmore you're free to use control + k to insert link .
About OTA, I am not aware of Flominator doing so (but I may be wrong).
Click to expand...
Click to collapse
corrected wrong and outdated things

F-Google said:
corrected wrong and outdated things
Click to expand...
Click to collapse
Still some work to do...

@roirraW "edor" ehT please can you close the thread, the rom is WIP again @Flominator will post when it's done

F-Google said:
@roirraW "edor" ehT please can you close the thread, the rom is WIP again @Flominator will post when it's done
Click to expand...
Click to collapse
Thread has been closed on request of OP!
@F-Google Just a remark: The best, most efficient and fastest way to get such requests accomplished is to alert the moderators team via the report function instead of posting the request and pinging a moderator. Please be aware, with 75M+ posts in 3.5M+ threads were unable to monitor posts. And moderators are spread all over the globe and due to different timezones pings might not be noticed for many hours or for days/weeks in case of a moderator's absence. Contrary, a report will alert "the moderator on duty".
Regards
Oswald Boelcke
Senior Moderator
CC: @roirraW "edor" ehT