Normally booting my phone will go to TWRP, along with selecting 'Start' or 'Recovery Mode' in the bootloader. However, selecting 'BP Tools' in the bootloader boots to the normal system. This has been consistent across several ROMs. Does anyone know why this would happen or how to return it to normal behavior?
https://forum.xda-developers.com/showpost.php?p=74109609&postcount=65
Just fixed this problem yesterday myself. Check out this thread but specifically this post, OP
Related
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
After messing up a rom flash somehow (phone was stuck on a gray screen after logo), I used the stock recovery factory reset function, but after doing so my phone is stuck in an 'erase loop'. The phone alternates between the "Erasing..." screen (with the little droid) and the "Bootloader Unlocked" screen.
I can enter the main menu for recovery mode, but if I try to go into the actual recovery mode (where you can wipe and install from sd/adb) the loop starts up again. I haven't seen this issue mentioned many other places, but the one forum I did find (for a different phone) just said to wait it out (20+ hours).
I was wondering if anyone else had ever encountered this, or if anyone had any suggestions for me.
TCZaro said:
After messing up a rom flash somehow (phone was stuck on a gray screen after logo), I used the stock recovery factory reset function, but after doing so my phone is stuck in an 'erase loop'. The phone alternates between the "Erasing..." screen (with the little droid) and the "Bootloader Unlocked" screen.
I can enter the main menu for recovery mode, but if I try to go into the actual recovery mode (where you can wipe and install from sd/adb) the loop starts up again. I haven't seen this issue mentioned many other places, but the one forum I did find (for a different phone) just said to wait it out (20+ hours).
I was wondering if anyone else had ever encountered this, or if anyone had any suggestions for me.
Click to expand...
Click to collapse
Try flashing TWRP recovery image using fastboot. I presume you have bootloader unlock otherwise you wouldn't ended up in this mess in first place.
First reboot your phone into the bootloader (POWER+VOL-) from here you can connect your phone to PC and issue fastboot commands.
Code:
fastboot flash recovery /path/to/TWRP.img
After that don't reboot the phone , just select from the already present bootloader the Recovery option... And from there try to factory reset !
If that doesn't work, and the phone doesn't boot (bootloops), you might have the /system partition messed up. At this stage get your hand on the latest Stock Firmware for your phone and flash all the system chunks (no data will be lost, but might need to wipe cache after if you get too many Force Closed)
That is for sure if you want to have stock, you could also try and flash using TWRP a custom ROM, that by itself will restore your system partition ( wipe system before flashing to be sure, by going into wipe -> Advanced -> tick System and the two Cache options and Wipe)
Hope I was clear, ask if you need more step-through details!
Thank you very much, flashing TWRP worked!
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
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.
Hi, I've got a soft bricked S8. I've tried to flash stock firmware but with one, O2 it stuck on erasing at 32% and with another stopped at 24% with no command. When it boots into recovery, I get a whole list of messages at the bottom of the screen. The first one is, "#fail to open recovery_cause(No such file or directory)#" I've googled for hours and not really got anywhere. Recovery doesn't work. It's there but buttons are unresponsive sometimes. Download mode works and shows FRP lock ON and OEM lock ON. I am sure this has something to do with it but it's outside of my knowledge range. I've attached a picture of the recovery screen. Any ideas would be appreciated.
I'm new to these threads so I can't work out how to attach a .jpg of the recovery faults. Any advice would be appreciated
Same issue here
I know this is an old thread, but did you find a solution?
On an unlocked J6, after flashing the stock rom, although I can open recovery, I get the same message. The options I tried (both reboot options, both wipe options, power off) work. I went ahead and installed twrp through odin, which passed, but when I boot into recovery, it boots into samsung recovery (with the same message) and not twrp.
I'm guessing the twrp problem is related to the error message.