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
I installed CM10.2 without issue and all has been running smoothly, then I flashed gapps for 4.3 ever since then I am unable to boot into recovery. My phones volume keys are a bit hit and miss so I usually reboot into recovery via Android (in the reboot menu) however every time I try this the phone just reboots as normal and straight back into Android. I plugged the phone into my computer and ran 'adb reboot recovery' which again caused the phone just to reboot into Android again... Everything had been working fine before I installed gapps.... Any help?
When I go to put the official twrp on it doesn't stick after reboot. before reboot I can't flash anything either like magisk. Nothing shows inside the folders and after I reboot and go back to twrp it shows no command
Me too. I've flashed twrp-sanders and also twrp-potter. The phone will never boot into twrp recovery on its own. Also, when I fastboot boot recovery from PC, either version of TWRP loads splash screen but is frozen and requires a hard reset.
The phone is unlocked as it indicates this on boot up.
Only once after the first attempt of flashing twrp-sanders recovery did the phone boot into twrp recovery and I flashed Magisk from there. Since then, no dice
Any ideas or direction would be greatly appreciated. Thank you
Got it to finally work. I started over by flashing "twrp-sanders-r2.img".
Make sure the first thing you do after flashing the recovery is to push volume button until you see the recovery option. Then press power button to select it. It will take several seconds before you can interact with the program.
I made sure I had the magisk.zip ready to flash first thing I did.
If you don't go to recovery immediately after flashing the twrp, you'll have to start over.
I hope this helps
I recently installed twrp instructions and installed a custom ROM. Even since then the device boots normally into twrp recovery only. to boot into the rom, I have to boot through recovery, press power + volume dn and then it boots to the regular ROM. Should I start over on this or is there a way to change that preference so the device boots normally into the OS instead of twrp.
Sorry if this has been answered somewhere else already. I looked.
gnaneswarv said:
I recently installed twrp instructions and installed a custom ROM. Even since then the device boots normally into twrp recovery only. to boot into the rom, I have to boot through recovery, press power + volume dn and then it boots to the regular ROM. Should I start over on this or is there a way to change that preference so the device boots normally into the OS instead of twrp.
Sorry if this has been answered somewhere else already. I looked.
Click to expand...
Click to collapse
I am facing same issue. I don't have twrp or custom rom but stock recovery and stock rom. Everytime I boot or restart my phone it goes to recovery mode!! I couldn't find solution yet and its very annoying.
Try following the steps in this thread: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 Of course, ensure you have backups before erasing anything.
I am on the latest EU weekly rom rooted with Magisk. Everything was going fine. I decided to reboot my device because my Messenger's dark mode was loading weirdly again. As I rebooted, it went to recovery mode without me doing anything. I tried to reboot it again but it wen to recovery mode again. The unfortunate thing is it's not even booting completely to TWRP and just stuck on its logo.
What do I do to fix this?
Did you find a solution? the same happened to me today, rebooted the phone and it's now stuck in fastboot but i can access recovery