Database Develop

Latest TWRP?

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.

TWRP deletes my OS [LineageOS][Redmi4x]

So I have a lineageOS on my redmi 4x and a twrp recovery, but whenever I try to flash something new from TWRP (I tried magisk and some other thing) it completely deleted my OS, I had a backup so its not a problem, but how could I flash something new again? Should I wipe something or what?

Use Latest 3.1.1/3.2.0 TWRP from official TWRP page. It's a Recovery Problem.. if you're On N go for latest 3.2.0 and Also check if you're Device is not encrypted (like you can't see Internal storage In TWRP) Clean Flash ROM, If anything Doesn't work... This is strange, I heard this issue the first time. Maybe Recovery Problem, Try and Reply.

SleepyWeeb said:
So I have a lineageOS on my redmi 4x and a twrp recovery, but whenever I try to flash something new from TWRP (I tried magisk and some other thing) it completely deleted my OS, I had a backup so its not a problem, but how could I flash something new again? Should I wipe something or what?
Click to expand...
Click to collapse
If your Problem solved report back

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?

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.

Flashing problem on Chinese version K20 Pro (raphael)

Hello there,
I'm using the Xiaomi.eu latest Beta rom ATM. I'm trying to flash other roms (like lineage OS 17.1 for example) but it seems to reboot to fastboot everytime. I've tried doing a clean flash, formatting data, dirty flashing. Nothing seems to help it boot into the new rom.
Clearly I'm doing something wrong. If I try flashing the recommended Chinese vendor firmware (stable version), I get an error 7..but my TWRP is up to date as recommended.
If anyone has any idea where I'm going wrong, that would help a lot.
Thanks

therightperson_630 said:
Hello there,
I'm using the Xiaomi.eu latest Beta rom ATM. I'm trying to flash other roms (like lineage OS 17.1 for example) but it seems to reboot to fastboot everytime. I've tried doing a clean flash, formatting data, dirty flashing. Nothing seems to help it boot into the new rom.
Clearly I'm doing something wrong. If I try flashing the recommended Chinese vendor firmware (stable version), I get an error 7..but my TWRP is up to date as recommended.
If anyone has any idea where I'm going wrong, that would help a lot.
Thanks
Click to expand...
Click to collapse
Don't know what your doing wrong, but this is my failsafe method should nothing else work.
Flash the latest Chinese 11.0.5 fastboot ROM. Make sure you don't lock the bootloader if using the Mi Flash Tool.
Boot into MIUI once to allow it to finalise the install, you don't need to do the initial phone setup once it boots into MIUI.
Boot into fastboot and install TWRP. I recommend the latest from mauronofrio which should be 3.1.1-32
Boot immediately into TWRP. I use the volume up button while powering up the phone.
Perform a factory reset in TWRP (using the swipe button), then format data (need to type 'yes' to confirm).
Reboot into TWRP using the TWRP boot menu, this ensures the newly formatted data partition is correctly mounted.
Copy over the ROM you want and GApps if needed, then flash.
Boot into your new ROM, everything should be OK. Then boot back into TWRP to install Magisk if you want root.

Yep that seems to have done the trick. At first I was getting frustrated because I thought I was downloading the right Chinese ROM, turns out I was downloading the recovery version instead of the fastboot one.
I think it wasn't working because I was on the beta channel. Switching over to the stable channel meant I had to go through a fastboot flash apparently. I've seen this before on my OP3.
Got lineage OS loaded, thanks for your help!