Database Users

[Q] ClockworkMod Recovery 5.0.0.1 flashed from ROM manager failed. trying again

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.

[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

[D800] Stuck on LG boot logo

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...

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.

Factory reset after dirty flashing Oreo, now only boots into TWRP

So a while ago I had dirty flashed the Oreo update from this link: OREO open to give it a try and see if I could actually get away with a dirty installation. Phone was working ok but battery drain has been enormous, around 30-50% worse than with Android 7.1 especially on idle so I thought ok time to do a proper factory reset by wiping everything (Dalvik, cache, system).
Now, I selected Factory Reset from within the OS (not TWRP) but during the first reboot it booted into TWRP asking me for decryption password, I did a wipe so it forgot all about it but now it only boots into TWRP no matter if I do an Advanced Factory Reset wiping everything via TWRP's menu, phone starts, shows the LG logo for a couple of sec and then TWRP screen shows up.
I am thinking I should flash a stock Oreo recovery in order for the boot to the OS but not 100% sure if this will cause more trouble.

mclisme said:
So a while ago I had dirty flashed the Oreo update from this link: OREO open to give it a try and see if I could actually get away with a dirty installation. Phone was working ok but battery drain has been enormous, around 30-50% worse than with Android 7.1 especially on idle so I thought ok time to do a proper factory reset by wiping everything (Dalvik, cache, system).
Now, I selected Factory Reset from within the OS (not TWRP) but during the first reboot it booted into TWRP asking me for decryption password, I did a wipe so it forgot all about it but now it only boots into TWRP no matter if I do an Advanced Factory Reset wiping everything via TWRP's menu, phone starts, shows the LG logo for a couple of sec and then TWRP screen shows up.
I am thinking I should flash a stock Oreo recovery in order for the boot to the OS but not 100% sure if this will cause more trouble.
Click to expand...
Click to collapse
Flash the oreo update zip from westwood or zefie. You can find it in the rom and development section. Search for v20a

mprovi_15 said:
Flash the oreo update zip from westwood or zefie. You can find it in the rom and development section. Search for v20a
Click to expand...
Click to collapse
Thanks but being impatient, I tried flashing the stock recovery. This seemed to free the booting and reset process, phone showed the LG logo, then for 2 seconds "Deleting" then LG Logo again and I thought the factory reset was in progress. After like half an hour still stuck in LG logo I realized I've probably soft bricked it. Phone only starts and gets stuck in LG Logo. So I entered bootloader and re-flashed TWRP but unfortunately now I can't find a way to boot into recovery (the irony). Phone just starts and gets stuck in LG logo forever, only thing i can do is use Power+Vol down to reboot into bootloader but no way to boot into recovery or even shut it off. Any way to enter recovery at this state and flash the OREO zip?
I realize I should have just waited for instructions but coming from consecutive unlocked Nexus devices i thought the steps and processes would be similar...

Try to discharge the phone completely (to shut it off) and enter download mode (I don't know any other method to do it). With LG UP flash stock kdz from your model, if you search a bit you will find it. This should work. If it don't work I've seen a couple of posts with the same problem as yours, search for the solution there, but if you can enter download mode it should work LG UP.

mprovi_15 said:
Try to discharge the phone completely (to shut it off) and enter download mode (I don't know any other method to do it). With LG UP flash stock kdz from your model, if you search a bit you will find it. This should work. If it don't work I've seen a couple of posts with the same problem as yours, search for the solution there, but if you can enter download mode it should work LG UP.
Click to expand...
Click to collapse
Thanks for the quick reply. With a bit of Googling I found that you can use volume down to enter stock recovery. This confused me as when I did it I expected to see the TWRP welcome screen. Instead I saw the stock recovery screen which only gives you the option to do factory reset. I did it and then rebooted again into recovery and all of a sudden I saw the TWRP screen! I remember there is something weird with how TWRP sticks to the system or not, again very confusing compared to Nexus devices. Anyway, since I managed to enter Recovery I copied the OREO flashable zip to internal memory and flashed and phone booted fine, now I am waiting to set up a fresh 8.0 installation :good:

mclisme said:
Thanks for the quick reply. With a bit of Googling I found that you can use volume down to enter stock recovery. This confused me as when I did it I expected to see the TWRP welcome screen. Instead I saw the stock recovery screen which only gives you the option to do factory reset. I did it and then rebooted again into recovery and all of a sudden I saw the TWRP screen! I remember there is something weird with how TWRP sticks to the system or not, again very confusing compared to Nexus devices. Anyway, since I managed to enter Recovery I copied the OREO flashable zip to internal memory and flashed and phone booted fine, now I am waiting to set up a fresh 8.0 installation :good:
Click to expand...
Click to collapse
OREO flashable zip? I am searching it for a long time, where did you find it?