Develop Bugs

PLEASE HELP!! clockwork recovery won't boot to recovery

Not sure what i did...must have accidently hit something in ROM Manager.....
Phone boots up fine..but when i go to reboot into recovery my Splash screen flashed then just goes blank. After reflashing recovery the splash screen just starts flashing like crazy. I cannot get into recovery. Ive tried uninstalling and reinstalling rom manager, fixing permissions, reflashing the recovery but nothing seems to be working. I've tried finding an answer that works but i cannot find anything.

Update, i have the SLCD on my phone. I ended up rerooting the phone and flashing the additional package for the SLCD which seemed to correct the problem.
Hope this is helpful for anyone else who may have this problem.

I've been having problems with also, what is the "extra package" for SLCD?

http://jonsuh.com/2010/11/root-your-droid-incredible-how-to/
That link has the instructions. Alternatively you can use rom manager to flash a different recovery, meaning Aman-ra it works well with SLCD i have one. I hate to say this but i would strongly suggest not using Rom manager with SLCD until they have a fix with clockwork in a new build or they get the option to flash a differe CW recovery because when you open RM it tells you that you must install CW and when you accept it doest install it but its a version that does not play well with SLCD.
Ofcourse if I am wrong and anyone wants to interject I am new to this site and would'nt mind the the expertise

It's not a ROM Manager issue, and the fix for SLCD is pretty well documented on this and other forums. Problem really is what you're seeing in the news - fragmentation of the Android platform where you have multiple flavors running on multiple versions of hardware and no two are always the same - even in the same product lines.
Once you get Clockwork on, and the SLCD fix, ROM Manager works fine.

still having troubles
I have tried the method above as well as other methods of installation from the SD card, but the clockwork fix just goes blank once I select something and when I installed Amon_RA it completely froze up....Any suggestions?

captndisaster said:
I have tried the method above as well as other methods of installation from the SD card, but the clockwork fix just goes blank once I select something and when I installed Amon_RA it completely froze up....Any suggestions?
Click to expand...
Click to collapse
Use the trackball to select options, not the power button.

ClockworkMod Recovery not loading

Hi,
I hope this isn't a repeat, but I've searched here and Google to no avail. It may be I'm not searching the right things, because I'm not quite sure how to succinctly describe this problem.
I've rooted my DInc, with S-Off enabled. I'm running CyanogenMod 6.1 now, installed from ROM Manager, which is no version 3.0.0.7. I've got ClockworkMod 2.5.1.2 installed as well. When I first rooted my phone, etc. about a month ago, I made a nandroid backup, so I figure its time to make another one. Open ROM Manager, go to Make a New Backup, choose a file name, it reboots into Fastboot. If I then select "Reboot" by pressing the Power button, the phone boots back to Cyanogen and there is no (new) backup file in the clockworkmod/backup directory, where I expect it.
If I select "Bootloader" from the Fastboot menu, it takes me to the HBoot menu, with the options "Fastboot", "Recovery", etc. Then, an error message appears very quickly, about missing PB31IMG.zip files. I'm not sure about the exact text of the message since it disappears so quickly, but I've searched around and it seems to be because that file is missing from the root of my sd card (I checked on Windows, its not because the file is renamed to .zip.zip or something). Solutions such as formatting the sd card to FAT32 (it is, according to Windows) and reflashing ClockworkMod from ROM Manager do not help.
After the error message disappears, I am able to select "Recovery" from the HBoot menu, and the screen flashes the white with black text "HTC Incredible" startup screen before dropping me back into the Fastboot menu. At this point, I usually just give up and reboot and keep using the phone as normal.
Does anyone have any idea where the problem lies? Can someone link me to the proper PB31IMG.zip file for my phone/ROM/radio?
Radio: 2.15.00.07.28
HBOOT - 0.92.0000
Thanks!

Have you tried reflashing ClockworkMod from within ROM Manager?
Personally, I've never had this happen, sorry if reflashing doesn't help

dmbhaggis said:
Have you tried reflashing ClockworkMod from within ROM Manager?
Personally, I've never had this happen, sorry if reflashing doesn't help
Click to expand...
Click to collapse
Yeah, that's how I was reflashing ClockworkMod. Thanks anyways.

Try going into ROM Manager go all the way to the bottom to All clockworkmod recoveries and try flashing a different version of CWM Recovery...

jackbtha1 said:
Try going into ROM Manager go all the way to the bottom to All clockworkmod recoveries and try flashing a different version of CWM Recovery...
Click to expand...
Click to collapse
Flashing back to 2.5.1.1 appears to have worked...does anyone have any idea why 2.5.1.2 is apparently broken (probably just on my device)?
Thanks!

I've seen other people reporting problems with 2.5.1.1 & 2.5.1.2 on amoled devices. They've suggested going back to 2.5.0.5.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

my bad didnt see last part

darthbith said:
Hi,
I hope this isn't a repeat, but I've searched here and Google to no avail. It may be I'm not searching the right things, because I'm not quite sure how to succinctly describe this problem.
I've rooted my DInc, with S-Off enabled. I'm running CyanogenMod 6.1 now, installed from ROM Manager, which is no version 3.0.0.7. I've got ClockworkMod 2.5.1.2 installed as well. When I first rooted my phone, etc. about a month ago, I made a nandroid backup, so I figure its time to make another one. Open ROM Manager, go to Make a New Backup, choose a file name, it reboots into Fastboot. If I then select "Reboot" by pressing the Power button, the phone boots back to Cyanogen and there is no (new) backup file in the clockworkmod/backup directory, where I expect it.
If I select "Bootloader" from the Fastboot menu, it takes me to the HBoot menu, with the options "Fastboot", "Recovery", etc. Then, an error message appears very quickly, about missing PB31IMG.zip files. I'm not sure about the exact text of the message since it disappears so quickly, but I've searched around and it seems to be because that file is missing from the root of my sd card (I checked on Windows, its not because the file is renamed to .zip.zip or something). Solutions such as formatting the sd card to FAT32 (it is, according to Windows) and reflashing ClockworkMod from ROM Manager do not help.
After the error message disappears, I am able to select "Recovery" from the HBoot menu, and the screen flashes the white with black text "HTC Incredible" startup screen before dropping me back into the Fastboot menu. At this point, I usually just give up and reboot and keep using the phone as normal.
Does anyone have any idea where the problem lies? Can someone link me to the proper PB31IMG.zip file for my phone/ROM/radio?
Radio: 2.15.00.07.28
HBOOT - 0.92.0000
Thanks!
Click to expand...
Click to collapse
I have the exact same problem, except my hboot reports as 0.78 I believe. Either way, the hboot menu is as far as I can get. Any other selection causes continual reboots. This started happening after a spontaneous reboot while driving down the road. I wasn't even using the phone. I do have the latest Clockwork on it, but it really doesn't matter because I can't get to the Clockwork menu anyway. Just the fastboot menu.
It says that USB is enabled in the hboot menu, but with it plugged into my PC, it won't show up in Windows. It's obviously not far enough into the boot cycle to do that.
Any suggestions would be awesome. I see about a dozen other topics started complaining about similar issues. If I leave it sit on the hboot menu, it'll sit there forever and is stable, so I don't believe it's a phone issues. It's almost like, if it were a PC, the boot sector is messed up and it needs an fdisk /mbr. I understand, that doesn't work, I'm just pointing out that I believe the behavior to be the same.
Thanks to anyone that can help!

I guess that, with no way to get into Clockwork and no way to replace Clockwork, I'm kind of stuck. Replacing Clockwork was an idea, but I'm not sure how to do that since hboot is all that's available and I can't choose any options without it rebooting continually. Is there a way to just plug the phone in and reflash Clockwork from my laptop with a Windows app on the laptop?

hackules said:
I guess that, with no way to get into Clockwork and no way to replace Clockwork, I'm kind of stuck. Replacing Clockwork was an idea, but I'm not sure how to do that since hboot is all that's available and I can't choose any options without it rebooting continually. Is there a way to just plug the phone in and reflash Clockwork from my laptop with a Windows app on the laptop?
Click to expand...
Click to collapse
Do you have Rom Manager installed on your phone? If you do you can always use the last option to install a different version of Clockwork. Give that a try...

I can't get past the "hold down and power" menu. That works fine, but anything I pick reboots the phone. I can't get into the OS at all because it just continually power cycles after I choose from the boot menu. I re-flashed Clockwork and no luck and I've re-flashed the entire phone to stock, same thing. It IS stable and the recovery menu you though. I can jump around in the menu, turn USB on and off, etc, just not boot into anything. It's literally like a computer that needs fdisk /mbr as all of the data seems to be where it should be.

I would try to flash any custom and see if that gets the phone to boot normally.

I took the stock build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000 and zipped it as PB31IMG.zip and when it boots, it'll take the images and flash them. It flashes all of the images in the zip and it takes a little bit to do that. Then it goes back to the menu and I restart it and it goes into the cycle again...

Hmmm. I would have used the unrooting guide to go back to stock just to get the phone back up and running and then unroot it again. If you do go that route DO NOT apply the 7.28 radio again because you will brick you phone being that you already have that radio flashed on your phone. What custom ROM or Kernel were you running before all this happened? I would try flashing that again but clear the data and cache first and see if that gets the phone up again.

I'm currently running the latest Senseless Revolution ROM and did upgrade to the latest ROM manager, but haven't flashed anything yet so no problems........yet!
Should I downgrade to CW 2.5.1.2 anyways since it was a bit sluggish when checking for MDsum?
I've read about some people having crazy problems and others actually not reporting anything bad......so what is the verdict? I'm trying to prepare myself first rather than finding out when my phone is stuck

I seem to be having some of the same problems. I upgraded ClockworkMod to 3.0.0.5 and was able to successfully boot into recovery. I installed CM 7 nightly, then ended up restoring to a backup of CM 6.1.
Now I can't access recovery, when I try I get stuck at the white droid incredible screen. My phone can still boot up so I tried downgrading ClockworkMod to 2.5.1.4, but it says an error occurred while flashing the recovery.
any ideas?

nate23 said:
I seem to be having some of the same problems. I upgraded ClockworkMod to 3.0.0.5 and was able to successfully boot into recovery. I installed CM 7 nightly, then ended up restoring to a backup of CM 6.1.
Now I can't access recovery, when I try I get stuck at the white droid incredible screen. My phone can still boot up so I tried downgrading ClockworkMod to 2.5.1.4, but it says an error occurred while flashing the recovery.
any ideas?
Click to expand...
Click to collapse
Are you renaming recovery to PB31IMG.ZIP and updating through hboot?
Sent from my ADR6300 using XDA App

pete_kowalski83 said:
Are you renaming recovery to PB31IMG.ZIP and updating through hboot?
Click to expand...
Click to collapse
thanks, that fixed it!

[Q] Recovery missing ?

I am totally new to custom Rom's so please be kind!
I purchased a used Desire with Cyanogenmod-7.0.3 already in place. I wanted to use the ROM manager to install the new version, so i took the option to 'Flash Clockworkmod recovery 2.5.0.7' from ROM manager.
From ROM manager again it did a Backup of current ROM.. When i try view the 'Manage and restore backups' i can see nothing.
If i try access recovery from ROM manager, i get phone image with question mark and it reboots straight away.
If i use manual method using volume down - power and select 'recovery', i get screen with phone and exclamation mark? It have to select 'volume up' and power to reboot ok.(Android System recovery menu 2e) There is also a warning in yellow 'E:Cant open /cache/recovery/command'
Is this the recovery menu for me ? I noticed there is an option to ' Apply Sd card:update.zip' but no back up option
Everything works ok at the moment, so i am reluctant to flash the update from ROM manager as i suspect the Clockworkmod recovery is either not accessible or missing??
Details of phone are:
Bravo Unknown Ship S-ON
HBOOT- 0.75.0000
MI Crop-031d
Touch Panel--Synt0101
Radio-5.17.05.23
Mar 5 2010,21;12:15
Current software details are:
Cyanogen Mod 7.0.3
Baseband version 32.56.00.32U_5.17.05.23
Kernel version 2.6.37.4-cyanogenmod-82245-g7f230e8
Some help would be appreciated. I've tried searching but find the various responses a little confusing.
Also, i realise that modding may be more than i need/want. Is it easy enough to restore back to Stock (was T-Mobile originally)
All I want a nice stable daily use phone.
Thanks in advance for replies.

All you need to do is flash a new recovery since yours is non-existent or ill-functioning.
The best way of flashing recovery is through fastboot. In order for this to work your device needs to be S-OFF. You can do this by using the new Alpharev/Unrevoked tool.
Once you have S-OFF, you can use fastboot commander, to flash the recovery.
If you get into any trouble or need any further help just holla
EDIT: Sorry that won't work, I just noticed that you HBOOT Version is really old. You'd have to run a RUU to update it.. but for an inexperienced user I'd leave it for now, unless you really want to - PM me if you want help with it.

That's fantastic. I'll have a try this evening. Thanks

because your hboot is too old for revolutionary to work:
create a goldcard (THIS WILL FORMAT YOUR SDCARD), then put the attatched PB99IMG.zip in the root of your sd-card, and boot into Bootloader (power off, then hold volume down & power), it will prompt you if you'd like to update, press volume up, and it should go.
This *should* work, I tried it and it did.. might give it a go again to confirm it 100% lol.
If it doesn't work for some reason because you're S-ON, although it should since this is an official HTC Hboot (if it doesn't work because of a CID error, your goldcard doesn't work, and you need to try the goldcard process again just in case [some SD-cards don't work as a goldcard]) then you will need to run a RUU, either the correct one for your phone, or the latest WWE RUU (if your goldcard works)
Once you've done that just follow the process I posted above

[OFFICIAL RECOVERY THREAD] ClockworkMod Recovery 5.x

I've been hearing that there are issues with flashing Clockworkmod recovery to 5.x recently. Jeagoss (teamdouche member) and I tried to troubleshoot this today, and we may have a solution, and what we have learned.
First, we found that booting into recovery while USB is connected works every time.
Here is what he did to fix it randomly:
Flash 5.0.2.6 (via the alternate recoveries button).
Flash 5.0.2.0
5.0.2.0 should not boot fine every time.
Here is the fix I put into ROM Manager that sort of does the above.
1. First make sure you are on wifi.
2. Make sure you are on the latest ROM Manager.
3. Flash 5.0.2.0. The new flashing process will write zeroes your current recovery before flashing the new one.
This *should* fix it. Please let me know your results.
Koush
Messaging me on twitter or on Google+ is by far the easiest way to get a hold of me. I am quite active on those, but not so active on forums.
Twitter
@koush
Google+
https://plus.google.com/103583939320326217147/posts

Testing your workaround method now.
I can say with absolute certainty that it *DOES* lockup when connected to USB (albeit rare). Just a simple 'reboot recovery' via ADB gets me into recovery when that happens.
It happens far more often when not plugged in.
Thanks for everything you do for this community.
edit: Just tested your workaround.
- Connected to wifi
- USB/charger disconnected
- ROM Manager 4.5.0.1
- Flashed 5.0.2.0 (via RM)
So far I'm 3 for 3 getting into recovery without getting stuck at the bootsplash.
edit2: Booted into recovery from RM 5 times now, never stuck. Either I'm getting lucky or you fixed that ****.
edit3: Well, I'm sad to report that on the 7th reboot into recovery, I got stuck again. Anything I provide to help troubleshoot?

Do you remember if the 3.0.2.4 version had charge mode support? If not, that may be what is causing the problem.

Koush said:
Do you remember if the 3.0.2.4 version had charge mode support? If not, that may be what is causing the problem.
Click to expand...
Click to collapse
I'm pretty sure 3.0.2.4 had charge mode support (assuming that means the ability to charge the phone when it's off?)

Don't really have time to test now, but flashed the 5.0.2.6 recovery yesterday via fastboot (fastboot erase recovery, fastboot flash recovery) and upon selecting recovery from the bootloader menu it would not get to it.
Tried 3 or 4 'adb reboot recovery' while it was hanging on the splash screen before giving up and reflashing 3.0.2.4 (Which I'm pretty sure supports charging)
-Nipqer

Koush said:
Here is what he did to fix it randomly:
Flash 5.0.2.6 (via the alternate recoveries button).
Flash 5.0.2.0
5.0.2.0 should not boot fine every time.
Click to expand...
Click to collapse
Maybe I'm misunderstanding, but did you mean "should *now* boot fine every time" ?
Also, yes, 3.0.2.4 charges fine with the phone switched off, that's what I am currently running.

Ok,
Fed up with people crying:
" Recovery this, recovery that....."
download this http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vision.img
adb reboot bootloader
fastboot erase recovery
fastboot flash recovery recovery-clockwork-5.0.2.0-vision.img
And enjoy the magic ......

dixxa said:
Ok,
Fed up with people crying:
" Recovery this, recovery that....."
download this http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vision.img
adb reboot bootloader
fastboot erase recovery
fastboot flash recovery recovery-clockwork-5.0.2.0-vision.img
And enjoy the magic ......
Click to expand...
Click to collapse
If by "magic" you mean "sporadic HTC screen hang" then yes, it's magic.
Sent from my HTC Vision using XDA App

I think dixxa is trying to say that erasing the recovery via fastboot before flashing the new version is the fix (as opposed to simply overwriting it with a new version, like ROM manager does)

Man, people are mean to each other nowadays. Relax guys, it’s just a hick-up for now. I’m sure Koush and his team will solve it eventually.
If you can't stand the 5.x.x.x sporadic behavior, switch back to 3.0.2.4 or 4EXT Recovery(basically the same source code as Koush’s Recovery but reliable for now).
Go out and breath some fresh air. Look around you, there are other things to appreciate for.
And thank you, Koush for your work and commitment to the community.

tun4f1sh said:
I think dixxa is trying to say that erasing the recovery via fastboot before flashing the new version is the fix (as opposed to simply overwriting it with a new version, like ROM manager does)
Click to expand...
Click to collapse
That's it!
never got that htc splash screen after wiping completely the recovery and reflashing it.

tun4f1sh said:
Testing your workaround method now.
I can say with absolute certainty that it *DOES* lockup when connected to USB (albeit rare). Just a simple 'reboot recovery' via ADB gets me into recovery when that happens.
It happens far more often when not plugged in.
Thanks for everything you do for this community.
edit: Just tested your workaround.
- Connected to wifi
- USB/charger disconnected
- ROM Manager 4.5.0.1
- Flashed 5.0.2.0 (via RM)
So far I'm 3 for 3 getting into recovery without getting stuck at the bootsplash.
edit2: Booted into recovery from RM 5 times now, never stuck. Either I'm getting lucky or you fixed that ****.
edit3: Well, I'm sad to report that on the 7th reboot into recovery, I got stuck again. Anything I provide to help troubleshoot?
Click to expand...
Click to collapse
Yeah... it seems less probable of freezing now but still freezes

tun4f1sh said:
I think dixxa is trying to say that erasing the recovery via fastboot before flashing the new version is the fix (as opposed to simply overwriting it with a new version, like ROM manager does)
Click to expand...
Click to collapse
You can select the option in ROM manager to erase recovery before flashing FYI.

Thanks for the attention, I've give this a go as soon as I have a moment.

It's weird.. for entering recovery I actually only have a problem when I'm telling the phone to enter it while it's on (IE from reboot screen or from rom manager to do a backup/restore/flash a zip) but even when it freezes with ROM manager, I simply have to pull the battery, turn phone on with vol down, go into recovery, and it does whatever I had told it to do before... Don't know if that's the case with everyone or if I'm an odd exception, but yea.

noneabove said:
It's weird.. for entering recovery I actually only have a problem when I'm telling the phone to enter it while it's on (IE from reboot screen or from rom manager to do a backup/restore/flash a zip) but even when it freezes with ROM manager, I simply have to pull the battery, turn phone on with vol down, go into recovery, and it does whatever I had told it to do before... Don't know if that's the case with everyone or if I'm an odd exception, but yea.
Click to expand...
Click to collapse
Been reported a lot at this point. Take a gander around the forums. Also its not always simple for everyone to pull the battery. If you have an Otterbox then it can be a pain.

I decided to try this out last night, having been on 3.x all this time.
I flashed 5.0.2.6 and then 5.0.2.0. The first time I rebooted into recovery it worked, the second time it hung on the splash screen, and I went back to 3.x.
Then I tried flashing straight to 5.0.2.0 from 3.x, and I booted (from power off, no USB connected) into recovery fine at least 10 times. So it looks good to me so far.

steviewevie said:
I decided to try this out last night, having been on 3.x all this time.
I flashed 5.0.2.6 and then 5.0.2.0. The first time I rebooted into recovery it worked, the second time it hung on the splash screen, and I went back to 3.x.
Then I tried flashing straight to 5.0.2.0 from 3.x, and I booted (from power off, no USB connected) into recovery fine at least 10 times. So it looks good to me so far.
Click to expand...
Click to collapse
Yeah... I with the old 5.0.2.0 I was getting a freeze about 1/5 reboots into recovery... with this one I get them almost exactly half of the time 1/12... still happens though... this never happens in 3.0.2.4. I'm not sure that I am content with these sorts of freezes even at fairly low frequency.

I upgraded from 3.x to 5.0.2.0 through ROM Manager and it worked perfectly

is 5.0.2.6 unstable or something? why are we flashing from 3.x to 5.0.2.6, then to 5.0.2.0? why not go from 3.x to 5.0.2.0 or stay at 5.0.2.6?

[Q] HTC Desire GSM stuck in "fastboot"

Hello forum!
Yesterday when I found out that the new CWM Recovery Touch had been announced I just had to try it. Since I didnt wanna spend $ 2 for it, I was going to flash it in just as ive done with CM 7.1 and GAPPS. When i was going to enter the Recovery Mode via HBOOT (Power button and Volume up) I chose "Recovery" by pressing volume down and power. This resulted in a .5 second AlphaRev splashscreen flash and I didnt enter Recovery, I was stuck in Fastboot. Ive read many threads becuse I wanted the new feature, but that didnt resolve in any success. Im S-OFFd and im using the newest CWM Recovery (5.0.2.0) FYI. Ive tried to Hardreset, turn off and take out the battery and put it back in (and even use my charger during the HBOOT process) but no luck so far. This is why im turning to you guys becuse im kinda new to this things. I hope maybe someone have some experiance in this kind of errors and might help me, becuse I dont know what to do. Thank you in advance.
/ Kaoukan
Edit: Watched some videos, am I able to use the Unrevoked 3 tool again (since i rooted and flashed cwm at first with it) to "reflash" the recovery so it could work? Or am I going to brick my phone?

Check bortak's troubleshooting guide.
Sent from Sandvold's ICS using Transparent XDA App

Fix
Ive got this all fixed now, it seems that the CWM 5.x was still a beta and it messed up my recovery, a simple downgrade back to 2.5.0.7 made some magic and set my device back into recovery on demand.

Also have this problem on v5.006.
I'm trying to downgrade now.