Database Users

Single Vibrate Bootloop

Hey guys, I'm temporarily coming over here from the Inc2 section to help out a friend with the OG Inc. He was originally running CM7... Out of nowhere, his phone decided not to boot up one day and is now stuck in a loop.
What happens is that the phone splashes the "htc incredible" image, goes black, vibrates once, splashes it again, and the process repeats. Now, the strangest part is that I can enter HBOOT but not recovery. What happens is it will load recovery, show the Clockwork menu for about two seconds, then immediately shut off and bootloop again.
I've already tried flashing the stock IMG file through HBOOT - the only change that I can see is that now when I select either "Factory Reset" or "Reboot Recovery" it shows stock recovery for 2 seconds before bootlooping again.
Any thoughts?

skafan2 said:
Hey guys, I'm temporarily coming over here from the Inc2 section to help out a friend with the OG Inc. He was originally running CM7... Out of nowhere, his phone decided not to boot up one day and is now stuck in a loop.
What happens is that the phone splashes the "htc incredible" image, goes black, vibrates once, splashes it again, and the process repeats. Now, the strangest part is that I can enter HBOOT but not recovery. What happens is it will load recovery, show the Clockwork menu for about two seconds, then immediately shut off and bootloop again.
I've already tried flashing the stock IMG file through HBOOT - the only change that I can see is that now when I select either "Factory Reset" or "Reboot Recovery" it shows stock recovery for 2 seconds before bootlooping again.
Any thoughts?
Click to expand...
Click to collapse
If your s-off i would back uo your sdcard and then format it fat32. Then flash cwm recovery thru hboot. If cw works after flashing i would wipe everything and then resore a known working nandroid or flash a fresh rom.

Alright, thanks, I'll give that a try and get back as to whether that works.

[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] Strange Rooting Problem

A friend of mine with a Google Nexus 4 attempted to root on 4.4:
"The unlocking of the bootloader went without a hitch, and I downloaded the CWM non-touch from here:http://www.clockworkmod.com/rommanager, in the "Nexus 4" row, and "Download Recovery" column, named "6.0.4.3". I placed the file on the desktop, flashed it onto the phone, and booted into it using the volume keys and the power button to select "Recovery mode" on the bootloader screen. From there, I wanted to reboot the phone, so I clicked the first option, the "reboot system now" selection. I received the message "ROM may Flash stock recovery on boot. Fix? THIS CAN NOT BE UNDONE.", and not wanted to do anything to mess up the installation, clicked the "*****Go Back*****" option. And then I received another message saying, "Root access is missing. Root device? THIS CAN NOT BE UNDONE." Again, I clicked the "*****Go Back*****" option, not wanting to mess up the recovery. It suddenly booted into the stock ROM, showing the Google screen with a little unlock symbol at the bottom. Then it moved on to the Kit Kat boot sequence, the one with the 4 different colored circles and all that. I waited for it to boot back into the stock ROM, but it stayed on that screen, a bootloop. I then proceeded to hold the power button to turn it off. I booted it again, and it bootlooped again. So I went back to CWM and wiped the data/factory reset, wiped the cache partition, and went into advanced and wiped the dalvik cache. Then I rebooted it once more, and it bootlooped once again. So now I've turned it off, and am attempting to find a solution to fix this. As a last resort, I can always unroot it and wipe the data again. But I would prefer to not to have to re-unlock and re-flash the phone, unless there is no other option. During this entire period, the phone was connected by USB cable to the computer, up until I wiped the data and caches, where I unplugged it, and allowed it to boot."
*****So overall, after installing CWM, the phone was put into a bootloop. factory reset was done, as well as wiped cache partition and dalvik cache*****
is there a way to get the device rooted, without using the traditional unroot method? I feel as if the error (if any) was simple, therefore there should be a simple solution. Thanks!

XT1575 Reset Loop

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!

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"