When I received my phone a couple weeks ago, I unlocked the bootloader and installed TWRP. DIdn't root, as I had already updated to 33R. A few days ago I decided to encrypt the phone, which went smoothly. The only issue is that now when I attempt to boot to recovery, I get the stock CM recovery, not TWRP. Yes, I unchecked the update CM recovery in developer options. I tried to re-flash TWRP this morning, and it appeared to work fine, ADB indicated success, but upon reboot again I still only boot to CM recovery, not TWRP.
I've seen some anecdotal evidence that encryption does indeed mess with the recovery and make it less usable, but I thought that TWRP was one of the exceptions to this. Just curious for others' experiences with this.
I'm running TWRP 2.801 with encryption and it works fine, doesn't revert on reboot. Not sure if it matters, but I'm running CM11 nightly and applied TWRP via fastboot
Related
So I was on Marshmallow, got tired of the excessive battery drain and SD card limitations, and flashed back to Lollipop. I was able to flash TWRP, but then when I rebooted, I was told there was an update, so I reflashed the stock recovery and updated. Now I can't get back to TWRP. I flashed it repeatedly and every time I reboot into recovery, it's still on stock. I've lost root and nothing I've tried works. WTF?
Nevermind, I just tried flashing TWRP 2.8.7.1 and it worked. 2.8.7.3 apparently does not anymore.
Can a mod delete this?
It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
ali4ek said:
It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
Click to expand...
Click to collapse
Not sure I got any advice since you've already tried what I would've suggested. I sideloaded SuperSU-v2.79-201612051815.zip by booting into TWRP through fastboot and it worked for me. I read in another thread that some people were stuck on the nvidia logo for a good 15 mins and then it was fine. How long did you wait? I flashed TWRP after rooting because flashing it through fastboot wouldn't stick, but I can't see how that could matter.
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Sokraates said:
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Click to expand...
Click to collapse
I've been following the threads throughout the day and it seems to be a common problem after using flashfire. There's a thread on a potential fix here:
https://forum.xda-developers.com/shield-tablet/help/k1-fix-able-to-charge-tablet-ac-adapter-t3554261
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
MuTec said:
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
Click to expand...
Click to collapse
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
U99Dev said:
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
Click to expand...
Click to collapse
As it seems I did not, good thing that its written right at the TWRP download page...
Can't remember doing this when I installed TWRP first but as it seems I did.
Everything is working fine, just flashed Nexus OS and it booted.
Thank you so much dude
Apologies for being a member of this forum for so long and making this my first post. Regardless of this being my first post, these forums have been a life saver many times, and I would like to thank the very knowledgeable people who frequent these forums for all the time, effort, and patience that the put into new development and answering questions for those like me, who have a lot to learn yet.
Now to my issue...
I have had my OnePlus 7 Pro (Global) for a couple weeks now. It is on Android Pie, and I intend on keeping it on Pie for a while. I rooted it straight out of the box with Magisk 19.3 and TWRP 3.3.1-4 (Guacamole)(Installed by zip to both partitions) and it has been working great. No problems at all.
Two things have changed today, so I'm not sure which is the issue, if either are. One is that I updated to Magisk 20, and the other is that I tried to boot into recovery with and OTG cable attached with a 256g sansdisk flash drive attached to that. This is when it booted into bootloader instead of TWRP.
I disconnected the OTG cable and rebooted into system. I still had root from Magisk, so I attempted to reboot into recovery again, only to find that I booted into the bootloader again. Now I figured that I had lost TWRP, so I hooked my phone up to my windows 10 computer to flash custom recovery once again. I had read that it is possible to install TWRP to the ramdisk now through advanced settings, so I booted into temporary TWRP and selected the TWRP.img file to install to ramdisk. The command line said it was a success, so I backed out of that screen and rebooted into recovery. Once again, I was booted into the bootloader.
I disconnected my phone and booted into system. I still had root and everything was working as usual, so I reconnected my phone again and tried to install TWRP to both partitions as I did originally. The terminal went through the process rather quickly (usually it takes a minute or so to install TWRP), but claimed it was a success and that I lost root, like it should. I backed it up a screen, reboot to recovery.. no dice.
I've tried to take Magisk back to 19.4, but it didn't effect whether TWRP would stick.
I have a TWRP backup that I took of everything a couple days ago. I thought about trying to restore and see if that works, but I wanted to run it by you all to see if maybe somebody else has had this issue.
Could the attempt at rebooting into recovery while connected to OTG have done this?
Thank you all in advance for the assistance. I'm aware that this post is long winded, but I am also aware that you all like as much info as possible.
Thanks.
##############################################
Update
##############################################
My phone is working now, but not before I massacred it. I attempted to restore with that twrp backup I had while temporarily booted into twrp, through the twrp.img, through adb. I had it on the phone, so I figured I could use it.
I don't know if it was a corrupted backup, or if the process wasn't orthodox enough, but the restore crashed in the twrp terminal. I tried to boot into system and found that I had bricked the phone.
I ended up having to use the msm-downloadtool that I found here on xda. It was a lifesaver for sure.
Anyway, I figured that I'd update this thread. My phone is completely reset, bootloader unlocked, rooted, with custom recovery once again. I'm not sure what the cause was for the initial issue. I would still be interested to hear of any theories.
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.