Latest TWRP? - T-Mobile Samsung Galaxy S6

Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.

Aqua1ung said:
Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.
Click to expand...
Click to collapse
https://dl.twrp.me/zeroflte/

datdirtyscrew said:
https://dl.twrp.me/zeroflte/
Click to expand...
Click to collapse
Thank you! One of the things that I find irritating about TWRP Manager is that it asks me to confirm/verify the partition where TWRP gets flashed to. Now how can I possibly know if dev/block/platform/15570000.ufs/by-name/RECOVERY is the right place for my device? (Is it?) The second thing that bothers me about TWRP Manager is that it doesn't correctly detect the latest TWRP version, and often it offers to install an older version.

Did twrp-2.8.7.2-zeroflte.img.tar work for you?
After updating to DOI1, I get boot loops after trying to flash TWRP.
I can get into recovery and download mode just fine, but it won't boot to the OS.

RiskPrime said:
Did twrp-2.8.7.2-zeroflte.img.tar work for you? After updating to DOI1, I get boot loops after trying to flash TWRP. I can get into recovery and download mode just fine, but it won't boot to the OS.
Click to expand...
Click to collapse
I bit the bullet eventually (sesing as flashing TWRP via ODIN is a PITA), and flashed TWRP using TWRP Manager. I got an error message upon flashing, though it looks like TWRP flashed just fine. (Go figure!) Anyway, TWRP Manager flashes TWRP 2.8.7.1. It may be that TWRP people didn't consider TWRP 2.8.7.2 safe enough to flash, which is why TWRP Manager doesn't offer the option. That may be your explanation for your troubles.

Related

Can't install TWRP after updating to Nougat

I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.
Gutito said:
I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.
Click to expand...
Click to collapse
that would be because the TWRP in SRK Tools is only for android 6 (EMUI 4.1 - 4.1.1) and not for android 7 (EMUI 5 - 5.1)
the recovery that you need to use in order for twrp to be installed is this one https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.0/twrp-3.1.0-0-eva.img
then once its installed boot up your phone and then type in "adb reboot recovery" and that will then boot your device into TWRP 3.1.0.0
Thank you, it worked!
Another question, but now related to SuperSU.
I am with the 2.79 version of SuperSU and I downloaded the binary .zip of this version and flashed it by twrp. The problem is that it keeps saying ""There is no SU binary installed and SuperSU cannot install it. This is a problem!".
I already got it to work. Thanks btw
Gutito said:
I already got it to work. Thanks btw
Click to expand...
Click to collapse
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!
kzip said:
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!
Click to expand...
Click to collapse
I solved it by this post https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
I ended up not using super su but If you want you can use it instead of the one suggested there
By flashing the file provided in the post, I managed to automatically get access to super user (root)

Oneplus 6 Bootloop after flashing Magisk over Oxygen OS Beta 11

Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.
This might go without saying but after flashing Magisk are you also wiping Dalvik?
Nuzzlet said:
Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.
Click to expand...
Click to collapse
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.
TLX317 said:
This might go without saying but after flashing Magisk are you also wiping Dalvik?
Click to expand...
Click to collapse
Yes I am
mixlex said:
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.
Click to expand...
Click to collapse
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.
Nuzzlet said:
Yes I am
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.
Click to expand...
Click to collapse
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help
a4abbas said:
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help
Click to expand...
Click to collapse
At the moment I'm just using regular TWRP actually. Havnt used blue since I switched the beta builds. I actually remember having trouble finding a download for Blu spark. What are your issues?

Latest rooted boot image (9.5.11)

Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX
Why do need the boot.img for root ?
I never used it for root my device.
khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?
Since Jul 9, 2019.
Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Does this work for the global version??
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.
lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA
Flashing this on International breaks the WiFi. Does anyone have the international version?
Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..
Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".

TWRP gets replaced by stock recovery

So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.

Can't access twrp 3.4.0.1, H870

Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally without deleting any of my data, but does not enter twrp either. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition' and some other errors. I think that version is too old for my rom, so I'm afraid to use it for backup/flash. My phone is LG G6 H870, Android 9, software version V30b. The phone is not rooted, the bootloader is unlocked. Tried to erase cache partition and install twrp 3.4.01 again, didn't work. I can't install Skyhawk or Orangefox becuase I can't use twrp.
Is anybody facing this problem too?
Thanks!
Bootloader unlocked?
Mendoo said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yes
Thelock1 said:
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition', I think that version is too old for my rom. My phone is LG G6 H870, Android 9, software version V30b. My phone is not rooted.
Is anybody facing this problem too?
Thanks!
Click to expand...
Click to collapse
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
jis251 said:
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
Click to expand...
Click to collapse
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Thelock1 said:
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Click to expand...
Click to collapse
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
jis251 said:
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
Click to expand...
Click to collapse
Ok, thanks, I'll try to find a solution, or maybe I'll just wait for the next version of twrp.
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
AlejandroMota said:
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
Click to expand...
Click to collapse
Yes, I know I have to install twrp again every time I let the stock rom boot, but the only version of twrp working is 3.2.3 and I think that was released before the G6 received official Android 9 update, so that's why I'm not very confident using it. I've tried to enter recovery immediately after I've installed it, so I don't think that's the problem.
I have the same problem on the LG G6 H870. I won't get to TWRP. I tried several versions of TWRP and nothing.
Edit.
This twrp is functional:
https://androidfilehost.com/?w=files&flid=289997
After installation using fastboot, restart directly to twrp using power+vol. down.
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Update TWRP 3.1 to 3.4 problem
Thelock1 said:
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Click to expand...
Click to collapse
Hi, I don't know if this goes here, I hope you can help me, I update twrp from version 3.1 to 3.4 and now I can't access twrp, how can I fix it?
Hello again, I answer myself, and if it helps someone else, using adb fastboot with twrp 3.2 Melina solves it and twrp works perfectly again.

Categories

Resources