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] Can't get adb to work!

Heeelp
I tried to install Cataclysm ROM, and then it went into some sort of installer, after that I tried to reboot, but TWRP said it didn't have any OS?? So i tried to boot it up anyway? but nothing, just stucked on Google Logo. After that I tried to boot into TRWP agian. But then TWRP says "Mount Decrypt Data" and then i have to enter a password?? but i removed my pattern lock before flashing. Because i made a Nandroid and i read i had to remove the password before making a backup. But then i just press cancel. Then it says " Unmodified System Partition" "Swipe to Allow Modifications" and i do that. Now i have nothing on my SD card?? Then i thought i could flash stock through Fastboot/ADB, but now it won't see my device in ADB? I have updated my drivers, both by Google and Intel (Read they helped someone else) But nothing? so i cant retutn to stock and can't boot up.
Please help, highly appreciated
Some how i got i to reboot by an ADB command and then i could flash factory imgs and return to stock.

That very same thing happened to me the 1st time I tried to install Cataclysm. Somehow my SD card got wiped.
I had to start from scratch with the factory image.
I don't know what happened but I have since successfully installed Cataclysm.

Phone only boots with factory mode. I did something wrong.

I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.

ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this

Not booting into TWRP

Hey everyone,
I decided to root my lg g6 and got a fickle. After unlocking the device and flashing TWRP I tried to boot into it (''adb reboot recovery'' command) and it deleted all data and then twrp shows on screen for a split second and almost instantly boots normally into android so I set it up while still being unable to access twrp and any of it's functions. Does anyone have any idea what could be the problem?
P.S. Of it helps: before that i had a problem that every time I tried to use the ''adb reboot recovery'' command the console said ''no devices/emulators found''. After a couple tries I wanted to check whether the phone was connected just to make sure (''adb devices'') and after that it worked and I ran into the problem above.
Thanks for all the answers

When you first unlock BL and flash recovery you have to manually enter recovery mode.
Hold power and vol down till it turns off. Hold same buttons again until you see lg logo. Release power and press and hold again.
Then ask you to wipe etc hit yes both times and it will boot to twrp.

I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)

Ulrih said:
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Click to expand...
Click to collapse
You have to flash TWRP recovery and when it complete then use the button combo to boot into twrp, otherwise it will boot and restore the recovery.
flash twrp
button combo to twrp
done

Yes I've done that but the problem still exist.
btw thanks for the help

Maybe try fastboot flash recovery recovery.img

Try the all-in-one tool on this forum

By the way, I am running into the same issue.. I have a LG G6 US997,.. I have tried installing TWRP unofficial ones so many times and every time i manually try to access the recovery.. the phone simply wipes all my data to default

Hello,
I have the same problem. Did anyone figure out how to solve it? I'd highly appreciate any help.
If I try to boot into recovery, it asks me to factory reset, i hit yes twice and then the phone just goes on to boot normally. The data is not wiped but I can't get into TWRP.
If I enter "fastboot reboot recovery" after flashing TWRP it returns "fastboot: usage: unknown reboot target recovery"

[Mediatek] Moto E4 won't load into recovery or boot

Hey,
I have a moto e4 flashed with dotOS and TWRP, it ran out of battery yesterday, and on reboot refused to boot into the OS. My first reflex was to try booting into recovery, i managed to get into fastboot, but when i try to enter recovery it freezes on the TWRP splash screen.
I tried to reflash it, and although fastboot reports a successful reflash, It still freezes at the splash screen. I also tried to use the fastboot boot command to boot the recovery directly from memory, unsuccessfully.
For information, exact model number is XT1762.
If anyone has any ideas or experience with this issue i'd really appreciate some help !
Thanks

jman6495 said:
Hey,
I have a moto e4 flashed with dotOS and TWRP, it ran out of battery yesterday, and on reboot refused to boot into the OS. My first reflex was to try booting into recovery, i managed to get into fastboot, but when i try to enter recovery it freezes on the TWRP splash screen.
I tried to reflash it, and although fastboot reports a successful reflash, It still freezes at the splash screen. I also tried to use the fastboot boot command to boot the recovery directly from memory, unsuccessfully.
For information, exact model number is XT1762.
If anyone has any ideas or experience with this issue i'd really appreciate some help !
Thanks
Click to expand...
Click to collapse
You need to repair your /data
Caution All your Data will be lost. Get a Backup first of all!
1) Go to wipe option in twrp.
2) Select Advanced wipe
3) Tick on to Data and Select Repair or Change file system option.
4) Click on Change file system.
Most of the rom support ext4. but in this time it gave some error.
5) Change the data system to exFAT option and re change option to EXT4.
6) That"s it bro :good::good::good:
JOIN IN OUR TELEGRAM GROUP FOR MORE SUPPORTS AND NEW CUSTOM ROM LINKS.