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

[Q] n900w8 Won't boot into recovery mode

A few months ago I rooted my N900w8, installed custom recovery (cwm), and flashed Android L. Today I tried to update the recovery, planning on updating the ROM as well. But now no custom recovery works at all, even the one I had running before. When trying to boot into recovery it says booting recovery... like it should, and then the screen just goes blank, then the phone restarts. Sometimes getting stuck in a bootloop trying to boot to recovery, but usually just regularly booting and boots normally to Android L. So now I am unable to update my ROM because not a single custom recovery has worked and therefore I cant flash the .img files. Please Help!

Ryan_407 said:
A few months ago I rooted my N900w8, installed custom recovery (cwm), and flashed Android L. Today I tried to update the recovery, planning on updating the ROM as well. But now no custom recovery works at all, even the one I had running before. When trying to boot into recovery it says booting recovery... like it should, and then the screen just goes blank, then the phone restarts. Sometimes getting stuck in a bootloop trying to boot to recovery, but usually just regularly booting and boots normally to Android L. So now I am unable to update my ROM because not a single custom recovery has worked and therefore I cant flash the .img files. Please Help!
Click to expand...
Click to collapse
I had the same issue except when I try to load recovery it would "forward" itself to download mode.
This may work for you, try re-flashing the latest CWM update with Odin. Place your phone in download mode by powering it off and holding Volume Down + Home + Power. Press volume up to proceed.
1. Download and extract
2. Run Odin as Administrator (Download if you don't have already)
3. Select CMW file from your download folder and place it in the "AP" section.
4. Start
When finished, Reboot holding Volume UP + Menu + Power Button. Vola!
Let me know if this works for you.

MmoFanatic said:
I had the same issue except when I try to load recovery it would "forward" itself to download mode.
This may work for you, try re-flashing the latest CWM update with Odin. Place your phone in download mode by powering it off and holding Volume Down + Home + Power. Press volume up to proceed.
1. Download and extract
2. Run Odin as Administrator (Download if you don't have already)
3. Select CMW file from your download folder and place it in the "AP" section.
4. Start
When finished, Reboot holding Volume UP + Menu + Power Button. Vola!
Let me know if this works for you.
Click to expand...
Click to collapse
Yeah depending on which recovery I flash it'll either forward to download mode, get stuck in a boot loop trying to start recovery, or restart and load the ROM.
Unfortunately it still isn't working :/ I used the tool from this page (http://forum.xda-developers.com/showthread.php?t=2446269) to convert the .img to a flashable odin file. Used the proper Canadian touch recovery (also tried recovery without touch) from this page (https://www.clockworkmod.com/rommanager) and no luck. Tried to enter recovery mode, it says entering recovery mode, goes black for a few seconds, vibrates then restarts the phone in regular boot mode :/ Any more idea's?
Do I need to be flashing a recovery that supports Android 5.0.2 for it to work? Im so puzzled.

YES!! Finally I was able to get a TWRP 2.8.5.0 working. Downloaded latest version from the main TWRP site and flashed using ODIN, did not use the converting tool above, downloaded the TWRP as a .tar flashable file from their site. Thanks for the help!
Do I need to close this thread or anything? This is my first time posting on xda

Ryan_407 said:
YES!! Finally I was able to get a TWRP 2.8.5.0 working. Downloaded latest version from the main TWRP site and flashed using ODIN, did not use the converting tool above, downloaded the TWRP as a .tar flashable file from their site. Thanks for the help!
Do I need to close this thread or anything? This is my first time posting on xda
Click to expand...
Click to collapse
Congratulations on solving your own problem! ^_^
I just figured to share my part when i experienced the same issue. I feel like it has somehow corrupt itself after it finished flashing which results in an empty directory for the recovery mode.
Warm Regards,
MmoFanatic

OP2 soft bricked, can't access recovery, not recognized by laptop

Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.

If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac

CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.

AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.

justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.

Have flashed TWRP image using ODIN but it still boots into regular bootloader

I followed the forum instructions to flash TWRP onto my N910F Note 4 according to instructions: https://forum.xda-developers.com/showpost.php?p=55277852&postcount=3
All works fine. But when I reboot into the bootloader I still get the original bootloaded with the "Downloading Do not turn off target" notice.
On that tutorial it does say at the end that if the recovery hasn't changed then to uncheck the auto-reboot option. Did that, but same again.
What could I do?

Download mode is nothing to do with recovery.

You flashed a custom recovery, therefore you'll need to boot into recovery, not bootloader (download mode in Samsung phones). Power off your phone, then hold power, home and vol up to access the recovery you just flashed.
Sometimes the phone indeed overwrites the newly flashed custom recovery with the stock one, in such cases it usually helps to disable auto reboot in Odin (as you did), holding power+home+both volume buttons to force a reboot, then booting back to download mode and flashing the recovery one more time. Happy flashing!

[SOLVED] Can not install TWRP [#failed to open recovery] Help!

[ORIGINAL POST] - solution further down - (TLDR do not reboot into system after flashing recovery)
Hi,
I'm trying to install TWRP but when i've flashed PDA via ODIN and reboot into recovery, this is what i get. [see images] https://imgur.com/a/zfdvs
TWRP file from TWRP website: 'twrp-3.2.1-0-dream2lte.img.tar' for Samsung Galaxy S8+ (Exynos) (dream2lte)
As this did not work i tried to flash new BL and CP and then i retried to install TWRP, no luck.
Can you please help me! Thanks!
I also tried flashing TWRP (another version just to be safe) via heimdall, but that didnt work either. The enitire prosess is fine, but when i reboot into recovery i still get to the same page. [see images above]
[SOLUTION]
*Do not* boot into system after flashing recovery (TWRP), instead, make sure to boot directly into recovery.
Apparently Samsung Reinstalls recovery when you boot into system after flashing TWRP (or any other recovery for that matter). I do not know if it's like this for all Samsung devices or only the S8, but that's the way it is.
Credit from this article and comment section: https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/

I had the same problem and found instructions to press volume down + bixby + power and then start the Odin load. The load went fine but my phone locked up at the Samsung Logo screen. I tried getting back to the download mode but the screen went black. Now the phone will not power on at all. Exceedingly frustrating.

I've spent 2 hours trying to work out what did I do wrong (checking hashes, odin version, etc) and the simple solution was to boot into recovery right away after flashing via Odin. Thanks!

Hektor1154 said:
I've spent 2 hours trying to work out what did I do wrong (checking hashes, odin version, etc) and the simple solution was to boot into recovery right away after flashing via Odin. Thanks!
Click to expand...
Click to collapse
I've followed different procedures but basically use ODIN to push TWRP to my SP-580. After that, the tablet reboots. I disconnect the cable and power the tablet down. I then hold VOLUME DOWN and VOLUME UP and connect the cable again. But instead of going into recovery mode, it just shows me the percent charged dial. I can get no further than that and have done that at least 15 times. HELP???? Thank you!!