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.
Related
After flashing my phone in Amon RA's recovery the phone will go to the black HTC screen and just stay there. Immediately after flashing I rebooted within recovery and the phone began to reboot, but then shut off. I had to remove the battery to get it to power on again, and it's just stuck at the HTC screen.
Tried to flash boot, recovery, and misc images, but on boot I get no space on device write error. Help?
When you flashed something did you wipe first?
Yes, I wiped, and have wiped the several times I have attempted to do it again.
Basically i desided i would give the Rom manger and Clock Work Recovery a try, So i downloaded the App from the market and installed it then used it to flash the recovery. However now when i try to boot into recovery it just hangs at the Vodafone Screen at boot up.
I tried to reflash RA Recovery however if i do it within the Rom Manager it does the same and hangs when trying to boot to recovery mode. I tried flashing it by the terminal but that did work either.
So does anyone know what i should do!
try flashing via fastboot
how do i use fastboot? when i boot to fast boot the only options i have are
HBoot Mode
Reset device
Restart to HBoot
Power down
OK i tried flashing using fastboot but i got an error 'FAILED (remote: signature verify fail)'
same problem
i got the saame problem as youu!
Damn rom manager killd my recovery , not even the clockwork recovery will boot up! which sucks because now im stuck on superbad 1.3, i want to go back to cynagoen !!!
can you go back to cupcake using the guide below then come back up from scratch
hxxp://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/
I have been able to fix my problem hope this helps for you to!
i downloaded Amon_RA's recovery and trying installing using the terminal method. I got memory errors saying i was out of memory etc. so i turned SWAP on with 128mb and then swappyness to 60 an tried again, and this time it worked!
Couldnt be complete luck but i would give it a try if i was you
What worked for me.
I had this same problem. I spent hours and hours trying everything under the sun. This happened to me on Cyanogen 5.0.7 DStest7. I notice a lot of people on the cyanogen forum claiming that's what they use. I purchased the pro version and installed clockwork recovery through the app. I tried a lot of things and they all failed. I tried droid explorer exe to flash the recovery, fastboot method, I tried reflashing clockwork, terminal with and with out memory managers running. Finally, I tried flashing the Amon 1.6.2 recovery 3 times in a row with the clockwork app. I did a reboot every time. The last one took and I uninstalled clockwork. I'll probably never change it.
it has only killed your recovery because you selected the wrong option, you must flash the first option (Ion/MyTouch 3G) this is the version for the vodafone 32B handset
I was also frustrated when i chose the HTC Magic option and it hanging on the red voda splash screen
Hope i helped
please somebody helps me with the recovery as well..
im using motorola milestone..
i rooted my phone using UNIVERSAL ANDROOT.. the rooting went fine... plus flashing the clockwork recovery via rom manager went fine.. but everytime i reboot into recovery the recovery triangle logo just blinks for a second and my phone reboots and comes back normally to the homescreen.. how to ablolish this problem?
Best Regards.
I too am experiencing this problem. Flashed CWM Recovery today, then later flashed amon ra. Got into amon ra and successfully did a nand backup, then left it for a few hours. Just now tried to boot into recovery and got the oem android recovery 2e. Wtf is that about??
I just got the new CWM recovery update through Rom Manager today, and it said it was successfully flashed, but the phone only hangs on the HTC logo when goingto recovery. I can still do fastboot and boot to Android tho, so I'm now gonna try to figure out how to get my recovery back before something bad happes xD
anyone have advice or know where I can download a standalone copy of CWM 5.0.0.1 for G2?
Wish me luck I'll keep updating as things progress
okipokey, solved my own issue. Just had to reflash back to an older recovery and try again a couple times before it stuck.
Time to test out the new recovery!
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Same here just reinstalled the new version and it worked second time round
must be a bug they havn't quite worked out. Next time I'll do a fastboot flash instead for a low build number.
First time I flashed I tried it from a battery pull through HBOOT and it still hung. Reflash to 3.5 and then back to 5.0 fixed it like you guys
epolaris said:
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Click to expand...
Click to collapse
try just reflashing version 5 I had the same problem,but rebooted the phone reflashed version 5 from the rom manager and now is all good
I just sent the dev a comment about it on his Google+
maybe he'll have a fix out soon
Nice one, seems a "double flash" fixes it have just tested 3 or 4 times,seems to be working
yessir, seems to me that if it's a bug its really minor. I can see this being a problem if someone accidentally screws up something on their phone right after flashing the recovery, but not very likely and they'd still be able to reflash through fastboot
Seemed to flash the new version ok. But then, when trying to boot into recovery for the first time, the phone hung on the HTC logo boot splash. Pulled battery, and booted into recovery ok after that.
that's interesting that some of you didn't hang after the battery pull while mine did. Maybe it depends which version we're upgrading from?
stuck at htc
hey i also had this problem and i can't get my g2 to boot up at all. It hangs at the htc screen. I don't know how to fix this issue as i was trying to restore a backup from recovery right after the update. i can't get into recovery or anything else...all i get is the htc screen. Any ideas how I can fix this?
Luis
Any sign of a changelog?
I have no idea how to get to a changelog...can you tell me how?
biglou421 said:
I have no idea how to get to a changelog...can you tell me how?
Click to expand...
Click to collapse
found this
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
So far no issues here while playing around.
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
biglou421 said:
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
Click to expand...
Click to collapse
can you get into the HBOOT?
pull the battery, put it back in, hold the volume down button and then hit the power button. you should come to a white screen with some options
In the case you want to update your recovery using fastboot method, heres what you'll need:
CWM 5.0.0.1 for G2 (Vision)
HTC Sync drivers
ADB fastboot from Android SDK
Make sure your phone is all the way off by pulling the battery. Get into the HBOOT by holding down the volume down button and then hitting the power. use the volume keys to navigate and the power button to select. Choose "FASTBOOT"
Rename the recovery that you downloaded from CWM to "recovery.img" and put it in your ADB and Fastboot folder
plug your phone into your computer and pull up a command line for your adb/tools/ or adb/platform-tools/ folder where you should have ADB and Fastboot.
under the command line type in:
fastboot devices
<list of devices>
If you do not see your device make sure the cable is plugged in and your drivers are installed. if still nothing try a different cable til you get it to be recognized by the computer.
Once it's recognized do:
fastboot flash recovery recovery.img
when its done:
reboot
I flashed through ROM manager. On suggestion, I checked the box for "erase recovery - recovery will be erased prior to flashing". On first reboot to recovery it sticks at HTC screen. Pulling battery and vol. up+power then entering recovery the 2nd time works just fine.
Hope this helps.
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
Greetings.
I am sure there is an answer on XDA but an hour of Googling has got me stumped. Please point me to the right answer.
Starting point
Rooted N900T, stock rom, stock recovery.
What I did
Installed ROM Manager
Told ROM Manager to install the latest CWM for my phone. Completed with no errors.
Tried to boot into recovery with the standard "hold power, vol down, and home" but I could never get into recovery. It would look like it would start to boot into recovery then it would reset and boot into the regular ROM.
Then I told ROM Manager to reboot me into recovery.
Then it went badly... I am stuck in a boot loop that continuously shows going into recovery, then samsung logo, then repeat.
I have pulled the battery, tried to go into download mode, tried connecting USB, tried Odin.
What I want is a working phone. I would like to back up the stock rom and go to CM12 nightlies but for now I will just take a working phone.
Please help,
David
think I found the answer at http://forum.xda-developers.com/showthread.php?t=2666432
At least I got out of the loop, not fixed but progress.
That worked, the only other piece of info you might need if someone else has this problem is that there is no PDA button on the latest version Odin, it is called AP