Database Users

[Q] Stuck in recovery boot loop...?

While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?

It happened to me once. I pushed the power button for 60 seconds as it supposed to do a kind of battery pull, and it worked.

HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???

Lordificated said:
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Click to expand...
Click to collapse
I've done this twice to my nexus now and I think I found a reliable way to restore to running condition. YMMV
1)Boot the nexus into fastboot (power and both volume keys) when you power up.
2)Attach your usb cable from the PC (or MAC I guess, dont have one to try)
3)start WUG Nexxus Root Toolkit. 'Launch' advanced utilities.
4)Test your fastboot with Quick tools. check the button at Fastboot-Bootloader and click 'List Devices' if the box that pops up is empty then fastboot isn't working (I can't help you there and it must be working to continue).
5)If fastboot shows a device then go to "Boot Temporary" and click 'Custom Recovery'.
6)I selected 'Touch TWRP' but CMW may work as well. This will reboot you into (temp)TWRP and from there you can force a reboot that will reset the 'Recovery' flag that has locked your bootloader.
7)Give it a few minutes (be patient for 5 minutes) and hopefully you reboot to where you were prior to this mess.
Long time lurker and couldn't fix my fails without everyone here.
Thanks to all.
Bill

HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.

zeroedout420 said:
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
Click to expand...
Click to collapse
I guess mine worked because I was still on stock bootloader and adding TWRP was an important key but the 5 minutes seems to be the solution after all the rest.

recovery boot loop:- Is coz, one of your partitions would be facing problems while mounting.. So Wipe the Partition and Format it with Ext-2 file format. and reboot the Mobile. Then it'll stops rebooting.

Do you have a Samsung device?
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.

carltasmania said:
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
Click to expand...
Click to collapse
How do you install cf-autoroot when stuck in a boot loop with samsung galaxy S device if there is no fastboot?

My phone is stuck in bootloop too. It shows Twrp at the starting and then restarts. What am i supposed to do? I need help ASAP please

*Help* Phone keeps on booting into TWRP and then doesn't respond.

I just flashed TWRP for the first time but it comes up with "Unmodified System Partition" but touchscreen doesn't work for some reason so I cant select anything. I tried removing the battery and rebooting my phone (Galaxy S4 19505) But it just boots back into recovery for TWRP in the "Unmodified System Partition" . Please Help, thanks.
Edit: Should I delete the TWRP disk image from my pc? (My phone also keeps vibrating while turned off). I have also noticed that there is a non physical home back and menue button, did I download the wrong version? I used the TWRP app to download and flash the image.

Hi,
Download the latest image or tar from here: https://dl.twrp.me/jfltexx/ and flash it with either Odin or Heimdall.
Not quite sure about the notice, is it on the screen that asks you if you want to keep the system partition read-only? Then you either need to swipe or click ok.
Normally flashing a recovery should not produce the problems you are describing, did you only flash the recovery?

Can't access Recovery, only fastboot and the universal bootloader, please help!

So after stupidly trying to update twrp through twrp instead of fastboot, I can only access fastboot and the universal bootloader installed on the phone. If I don't do anything, the phone simply goes through universal bootloader and I see a small penguin before the screen goes back and I need to restart the phone again. However, in the bootloader I can select to go to fastboot which does work. I've tried flashing TWRP through fastboot (fastboot flash recovery twrp...) and it said success however after clicking 'reboot to recovery', the phone once again just boots to the bootloader and I'm back at square one.
Thank you so much if anyone can help!

FYI, you can update TWRP using TWRP. Nothing wrong with that, I do it all the time. It's faster and easier to do so.
You might have an incompatibility between bootstack and TWRP.
So, please provide us more info.
ROM:
Bootstack used:
TWRP version:
What were you trying to do besides updating TWRP?:

Funny thing... I'm having the exact same problem.
I instaled TWRP (3.1.1-0-9c3b7e99) using the AxonToolkit 1.2.1.
Everything went smooth with the toolkit. I could get into TWRP and did some back-ups (as recommended), then wipe Dalvik/ART Cache, System, data, cache, and finally, try to install LineageOS 15.1.
I used the files:
- ZTE_A7LOSv1_UniversalBootStack.zip
- A2017U_OreoModem.zip
- lineage-15.1-20180810-UNOFFICIAL-axon7.zip
UniversalBoot and Modem were installed correctly, but I got an error when trying to install Lineage. I can't remeber the error number but it said something like: "this ROM is for device ailsa_ii_axon7 but this device is ."
Since then... my phone is in eternal loop and can only get into Fastboot. Can't access TWRP.
Thanks in advance to anyone willing to help me.

Don't mind... I have it back.
After many reboots, It only seems that this is working different with the Universal O bootloader. On the main screen, I tap the volumen button, choose "Recovery", reboot, press the power button on the main screen, press it again, the Linux Pinguin appears, press power button again, and then TWRP is back.
After that, I got to wipe and do the normal ROM installation process.

SM-T580 Softbricked, Currently on reboot loop, can't flash any stock firmware

Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:

abstractartemis said:
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
Click to expand...
Click to collapse
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.

ashyx said:
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
Click to expand...
Click to collapse
So just keep flashing it until i can boot to twrp recovery basically?

abstractartemis said:
So just keep flashing it until i can boot to twrp recovery basically?
Click to expand...
Click to collapse
What's stopping you boot to Download mode?

ashyx said:
What's stopping you boot to Download mode?
Click to expand...
Click to collapse
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.

abstractartemis said:
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
Click to expand...
Click to collapse
If you can flash twrp then not booting to twrp must be pilot error.
It MUST be done immediately after flashing in odin.

No TWRP although flash was successful

Hello,
I tried to flash my S8 with TWRP with Odin. OEM and Debugging is active. After I had some failed flashes, when I now boot into revocery (VolUp+Bixby+Power) there is a blue background with a yellow warning sign and a dead android guy and "no command" but after some seconds I get into recovery mode. Even though I made factory reset and wipe I still get the error everytime I boot into recovery. When I now go to bootloader, flash TWRP with Odin I get a succesfull-message from Odin. But when I boot into recovery afterwards there is still the Android Recovery and not TWRP.
I tried different Odin and TWRP Versions and deactivatet F.reset and autostart.
Can someone help me? According to google search the blue background with the dead android guy should be gone after factory reset and wipe but its still there.

crackhead131 said:
Hello,
I tried to flash my S8 with TWRP with Odin. OEM and Debugging is active. After I had some failed flashes, when I now boot into revocery (VolUp+Bixby+Power) there is a blue background with a yellow warning sign and a dead android guy and "no command" but after some seconds I get into recovery mode. Even though I made factory reset and wipe I still get the error everytime I boot into recovery. When I now go to bootloader, flash TWRP with Odin I get a succesfull-message from Odin. But when I boot into recovery afterwards there is still the Android Recovery and not TWRP.
I tried different Odin and TWRP Versions and deactivatet F.reset and autostart.
Can someone help me? According to google search the blue background with the dead android guy should be gone after factory reset and wipe but its still there.
Click to expand...
Click to collapse
Sounds like incorrect installation of TWRP.
Did you boot up into TWRP straight after installation? not system.
Note: - USB Debugging is not required.
- Just start up odin leave default settings - In options section you can untick Auto Reboot then flash TWRP then boot into TWRP manually before starting system.