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 recently just picked up a nexus 4 and i'm trying to get a custom ROM on it. I updated it to 4.3 and that was fine. Went to install custom recovery and every since it will not boot! I've reverted to factory 4.3 using fastboot, and relocked it and locked it but still will not boot. It gets stuck at the X logo. Left it for an hour and won't get past it. If i install a custom recovery, it'll boot into the custom recovery no problem, but won't install root as it can't mount the SD card. I can get to fastboot mode no problem and flash stuff in fastboot but will never boot up. I'm puzzled as to what to do. I'm going to try 4.2.2 factory image here shortly and see if i can get it to take. I forgot to enable USB debugging so i think thats why i can't get custom recoveries to work. I tried pushing a ROM using ADB push but it wouldn't get there. Maybe it did as it said it did on the computer but the recovery won't read the memory. Any ideas as to what to do
UPDATE: Ok after flashing stock 4.2.2 from fastboot it boots.
UPDATE: turns out just having USB debugging was the culprit of everything. So make sure USB debugging is enabled before starting the whole process!
I had CM11 M6 installed. I wanted to flash this kernel called Furnace. I used the AOSP version, not sure if I should've used stock. Before I flashed it, I tried to wipe the cache. It was taking about 5 minutes so I force rebooted it. After I did that, my phone would be on the LG boot screen for about 3 minutes (before it was about 5 seconds) then I would see the CM boot screen. Overnight I tried wiping the cache again. When I woke up, I was on the lock screen. I flashed Furnace and then I was stuck on the LG boot screen. I went back into recovery and tried resetting to factory or whatever it's called and it took awhile to format /cache but it eventually did. Still, I was stuck on the LG boot screen. For some reason I thought installing a new recovery would help (I had CWM before). I pushed a TWRP recovery file for my device to my phone. I then put this command in the adb shell: dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery (recoveryfilename.img was replaced with what it was named). I rebooted into recovery from the old recovery, and on the top left it said secure booting error. I tried restarting and booting into recovery, no luck. Now I'm not really sure how to flash a new recovery because I can't get into recovery. I'm pretty sure to fix my booting problems I need to reflash CM, which will flash CM's kernel...?
Also, when I try to use fastboot commands on my computer, I get ERROR: could not get pipe properties
Can I use adb while it's in this boot state? Please help!
By the way, I'm using a mac
Edit: Looked around on the Furnace Kernel thread, I guess I used a too new version of the kernel for CM11...
Edit: Found this: http://forum.xda-developers.com/showthread.php?t=2582142, gonna try it out soon...
Hi
Yesterday, my phone suddenly crashed and turned off and restarted. My phone has been rooted and unlocked for about 6 months now with no issues and I did not do anything to it last night to change that.
Now, I am stuck between the "Google" logo boot and the "Your device cannot be checked for corruption." I can get into the bootloader and the device is shown on fastboot, but not adb. I have tried flashing the Stock img and it seems to work, but then it doesn't change anything.
If anyone could offer advice/insight that would be much appreciated! Thank you
Have you tried fastboot format data, fastboot format userdata and lastly fastboot format cache?
I had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
I would flash TWRP and try wiping all including internal. Sounds like one of the partions is corrupted. You could do it with fastboot in bootloader mode but not sure of the commands.
teunnk said:
I had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
Click to expand...
Click to collapse
You're probably not used to the stock recovery. The no command droid is normal. Watch this video, and see if you can get to recovery or bootloader.