Develop Bugs

Trouble with ClockworkMod 3.0.0.3.

I flashed the most recent ClockworkMod to my phone using ROM manager so I could do a ROM backup, and now my phone will not go into recovery mode. When I get into the boot menu and try to go into recovery, it goes into the splash screen and stays there.
Has anyone else had this happen with ClockworkMod 3.0.0.3? It took my phone quite a while to boot after that, and it put me into panic mode for a good moment.
I'll be flashing Amon_RA now to do my backup/ROM flashing. The latest updates to ClockworkMod keep doing crazy, crazy things to my poor EVO. Has anyone else experienced this?

YES! I was flashing a rom earlier tonight with the latest clockwork from rom manager and it messed up everything. Tried a bunch of different things. Still hangs on splash screen. How long did you have to wait?

yes also nothing wanted to flash had to go back to clockwm.. 2.5.0 where everything was petfect lol
Sent from my PC36100 using XDA App

same here, went to flash a few zips and installations kept aborting. just flashed amon ra and no problems now. hopefully they fix whatever happened to clockworkmod before ppl go crazy lol

my evo is doing that as i type this, i will definitely be switching to amon ra (as soon as my evo stops freaking out) until it gets fixed.

Alfred F. Jones said:
I flashed the most recent ClockworkMod to my phone using ROM manager so I could do a ROM backup, and now my phone will not go into recovery mode. When I get into the boot menu and try to go into recovery, it goes into the splash screen and stays there.
Has anyone else had this happen with ClockworkMod 3.0.0.3? It took my phone quite a while to boot after that, and it put me into panic mode for a good moment.
I'll be flashing Amon_RA now to do my backup/ROM flashing. The latest updates to ClockworkMod keep doing crazy, crazy things to my poor EVO. Has anyone else experienced this?
Click to expand...
Click to collapse
same thing happened to me and I thought I bricked my phone-took a few hrs to sort out. very disappointing

how did you solve the issue? my phone is basically in a bricked state...

ricankng787 said:
how did you solve the issue? my phone is basically in a bricked state...
Click to expand...
Click to collapse
can you boot into HBOOT? if so flash back to an older version of ClockworkMod.

taintbad said:
can you boot into HBOOT? if so flash back to an older version of ClockworkMod.
Click to expand...
Click to collapse
yes I can boot into hboot, how would i push files onto the phone? and flash from there?

ricankng787 said:
yes I can boot into hboot, how would i push files onto the phone? and flash from there?
Click to expand...
Click to collapse
I used the ClockworkMod from unrevoked
http://unrevoked.com/rootwiki/doku.php/public/forever
place the appropriate file on the root of the sdcard using a card reader and boot into HBOOT.

I got out of it by crossing my fingers and doing a battery pull, then booting normally. Thankfully it worked, so I had the chance to use ROM Manager to flash Amon_RA, but I can't guarantee it would work for everyone's.

hope this helps some one I went to appmarket and romanager and uninstalled update then went to app to flash back to older version 2.5
Sent from my PC36100 using XDA App

I hope so too. At this point I'd probably recommend that everyone with trouble either go back to 2.5 or even suggest switching to Amon_RA... nothing but problems with 3.0. !

Stuck on boot screen! Help!

Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible

Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<

enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.

Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?

I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.

Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.

Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.

Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?

sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.

Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5

Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.

as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo

Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help

erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?

encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.

sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?

oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X

encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?

Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what

Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.

SOFT BRICK please help

Hey, I got a soft brick so I'm going to use the unroot method here but I just wanted to make sure it would work.
S-OFF, Hboot 2.1
Also, I'll still be able to root and go back to an old nandroid if this all works out, correct?

It should work. Yes, you will be able to re-root and restore a nandroid once you have completed everything again.
Might throw out your issue first, to see if someone can help you fix without having to go through all that work of unrooting and re-rooting again.

Let's hope so. I'm knocking on wood that I won't have to throw my EVO down some stairs and go get a new one.

Firstly, it is unclear (at least to me) what you mean by "soft brick". Secondly, the link you posted is to a thread that is outdated and was retired by the OP. Or did you mean this thread?
http://forum.xda-developers.com/showthread.php?t=838448
To answer your second question, with S-off you can just go into recovery, do a wipe and then restore your NAND back-up from there. Try just wiping the cache and dalvik cache before restoring. If your phone still gives you problems, you may need to do a full wipe and do a fresh install of your favorite rom.

Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?

tubazeppelin said:
Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?
Click to expand...
Click to collapse
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb. Worse case scenario would be to run the RUU and start over.

rugedraw said:
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb.
Click to expand...
Click to collapse
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.

tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would download Amon recovery and flash that via adb; I recommend staying away from clockwork - read about too many users running into issues with it, especially that 3.0.0.5 version.

tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would suggest using Amon Ra recovery. I like it better, and personally have had far less issues with it. Attatched is a PC36IMG of Amon Ra 2.3. Put it on the main directory of your SD card, name it exactly PC36IMG, and boot to bootloader, and select yes to update. That should flash Amon Ra's V2.3 recovery for you. If it's successful, see if it works. The only problem with this, that I see, is you wouldn't be able to restore your previous clockwork backups. However, if that did go successful, and you were able to boot into a rom, you could use ROM manager to flash clockwork back, then you could restore your backups. Hope you get it booted up.
EDIT: If you do end up needing to unroot, just remember that if you initially used unrevoked to root, or used unrevoked forever at any time, you're not going to be able to turn S on without having a custom recovery. Becase as far as I know, you need to flash the Unrevoked S on tool in recovery if you used unrevoked to begin with. Otherwise S is permanently off.

tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
Yea, try the recovery fix. If unsuccessful getting CW to flash, remember you can always try to flash Amor RA recovery just to be able to wipe and flash a working rom. Once you get the phone to boot, you can download ROM manager, flash clockwork and then restore to your CW NAND that is stored on your SD card. I've had to do this in the past.

Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that

tubazeppelin said:
Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that
Click to expand...
Click to collapse
Really not sure. That goes beyond my scope of trial and error knowledge.

Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.

tubazeppelin said:
Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.
Click to expand...
Click to collapse
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.

k2buckley said:
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.
Click to expand...
Click to collapse
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.

tubazeppelin said:
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.
Click to expand...
Click to collapse
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.

k2buckley said:
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.
Click to expand...
Click to collapse
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.

tubazeppelin said:
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.
Click to expand...
Click to collapse
Awesome. Thats the way to go, just manually flash everything using RA and you'll be good to go.

[Q] Bricked? (Boot stops after a couple of seconds)

I got a little problem here
I was playing Angry Birds today when everything just froze.. touching would do nothing.. side buttons/power button wouldn't do anything.. not even haptic feedback on the touch buttons or whatever.. This had happened to me before, and the phone would restart itself, blabla, everything would be cool again.
Not this time!!
I turn my phone on but the boot (HTC) screen will stay on for a few minutes.. then goes black, and then vibrates and starts again.
At first I thought this was a problem with my ROM (CM7 Stable), so I tried going to the bootloader menu. It came up, but was unresponsive. I try and try again but only some times will it actually be functional, and even then, when I try to go into recovery, the boot screen stays stuck.
How ****ed am I?

Lolfox said:
How ****ed am I?
Click to expand...
Click to collapse
Not much at all. If you can get to the white screen and to the boot loader, it can be fixed. Do you still have your recovery installed? Try holding the volume button down while booting and see if it goes into recovery. If so, you can restore the NAND back up you are supposed to have done. If it goes into a black screen with a red triangle, your recovery is gone and you have to reflash it via the boot loader by getting a flashable zip file on your SD card and naming it "PC36IMG.zip". (Make sure you do not add ".zip" to the end of the file name, or it will be named "PC36IMG.zip.zip" and will not be recognized by the boot loader.)
Amon RA recovery zip file can be downloaded here ready to go: http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
If you do not have a NAND back up, just try wiping the cache and dalvik cache and try booting again. If that doesn't work, you may need to reflash your rom as if it was a new install and start over.
Worse case scenario, run the latest RUU and start over from stock.
Edit: If you did create a NAND that you want to restore, and you created it with Clockwork recovery, you will need to flash that recovery and not the one I linked to you in order to restore it.

If you're able to flash amon RA via the bootloader, I suggest you then download and reflash the hboot from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.

dougjamal said:
If you're able to flash amon RA via the bootloader, I suggest you then download and reflash the hboot from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I can't flash the HBOOT, it says to reflash the kernel afterward but I'm on CM and don't have the flashable kernel on my sd card
Plus, after a little bit of being inside recovery, the phone blacks out and tries to boot. Something tells me it's some freak hardware issue...

[Q] Bricked?

My friend has an Incredible that I rooted with unrevoked and got s-off. It was acting up and rebooting and I was going to go up to his house and fix it but it freaked out before I could get there. It will not turn on or even boot into android at all. It boots up with the HTC Incredible screen and then shuts off and does this over and over again. I put it into recovery or hboot I am not quite sure what you call it (hold power and vol. down) and from there I try to wipe but it will just go back into the boot loop sequence again, if I try to get into recovery, it will do the same thing. What can I do to help him out? He is phoneless right now and we really need to get this fixed. It is s-off and I want to at least try and get it to s-on so I can load the stock ruu on to it, but how am I supposed to do that if I can boot into it and I can't get into clockwork. I tried renaming CWR to the PB3IMG and booting into hboot, but I can't install. Please help. Any suggestions? Thank you for the help.

you say you CAN get to clockwork? if so, can you try to install a rom from your sd card, don't wipe again, just try to install and see what happens? or is it not letting you do even that?

Sorry I cannot get into clockwork. I tried installing CWR through hboot, but was unsuccessful won't even get me to the screen to install. AUtomatically reboots and just goes from the white htc screen to black over and over again.

Anyone have any ideas.. Maybe just to get a-on.

You are not fixing the problem by wiping the phone. The boot loop is caused by a bad install of a ROM and only restoring a clean backup or running the pb31img file froom hboot will fix it.
Did you make a backup before all this happened? If you did then from hboot you should be able to get into recovery and restore the bacukp. In hboot recovery is the second menu option, select it by scrolling down the pressing the power button to start it. Then from recovery select backup/restore and then select restore and it should show you a list of your backups.
If you didn't make a backup then you need to put a copy of the PB31IMG file on the sdcard and then boot into hboot and it should automatically run the update. This will also unroot the phone so you will have to root it with unrevoked again. You also have to have teh correct PB31IMG file for the phone, amoled or slcd as they are not interchanageable and flashing the wrong one will lead to more harder to fix problems.
http://forum.xda-developers.com/showthread.php?t=786436
Above is a link on how to get back to stock, how to falsh the PB31IMG file from hboot is Part 2. I copied the relevant parts of it below assuming that you have s-off.
1. Make sure you're rooted with clockworkmod recovery.
2. Download the RUU for your phone, either amoled or slcd (don't have a link).
3. Push PB31IMG-3.21.605.1_RUU.zip to your SDCard, renaming it to "PB31IMG.zip" (no quotes)(delete any other PB31IMG.zip you might have on there before pushing).
4. Boot into HBOOT, and it should recognize the PB31IMG.zip. Start the update and go get a drink (it might reboot once or twice, don't worry about it).
5. When that's done, reboot and you're at 2.2 stock!

Try installing cwm twice, its the only way it works for me. As far I can tell your friends phone is fine. Try flashing cwm twice.as I.said b4. Then post.back see if.that works then we will.go.from there
Sent from my Hybrid using XDA Premium App

Thanks guys I will try this and post results. Thanks again.

I am having a somewhat simular problem.
I am unable to flash any other ROM. I can do a backup and restore that backup. But when I boot into recovery, wipe everything, then flash a new ROM, I reboot and my phone just sits on the white screen with HTC Incredible in black letters. I have left the phone like this for more than 30 minutes several times and nothing happens. Phone is not warm/hot after being on this long so I am not sure if it is doing anything at all.
I hate to think I am not able to flash any more ROMs.
I have done a search for my issue and this thread is the closest thing I have found.
Any ideas or help?
Thanks.

Romparoo said:
I am having a somewhat simular problem.
I am unable to flash any other ROM. I can do a backup and restore that backup. But when I boot into recovery, wipe everything, then flash a new ROM, I reboot and my phone just sits on the white screen with HTC Incredible in black letters. I have left the phone like this for more than 30 minutes several times and nothing happens. Phone is not warm/hot after being on this long so I am not sure if it is doing anything at all.
I hate to think I am not able to flash any more ROMs.
I have done a search for my issue and this thread is the closest thing I have found.
Any ideas or help?
Thanks.
Click to expand...
Click to collapse
Maybe its just the rom? try downloading another making sure the download is fully complete. Wipe Data/Cache/Dalvik and Format System for good measure and try again.

Romparoo said:
I am having a somewhat simular problem.
I am unable to flash any other ROM. I can do a backup and restore that backup. But when I boot into recovery, wipe everything, then flash a new ROM, I reboot and my phone just sits on the white screen with HTC Incredible in black letters. I have left the phone like this for more than 30 minutes several times and nothing happens. Phone is not warm/hot after being on this long so I am not sure if it is doing anything at all.
I hate to think I am not able to flash any more ROMs.
I have done a search for my issue and this thread is the closest thing I have found.
Any ideas or help?
Thanks.
Click to expand...
Click to collapse
Make sure that the kernel the rom your trying to load has is compatible with your phone. I know some will say that kernels dont matter so much, but there are certain kernels that simply dispise my phone. Try going into recovery and flashing a different kernel.

I am in a somewhat similar boat. I cannot get into Recovery. If I power up the phone normally, it does the boot looping. If I go into hboot, I can get it to go through the motions of flashing recovery, and although it appears to be successful, if I try to go into recovery, it basically boot loops, except for one version which puts a few black lines on the screen and THEN boots. So what is my best option, seeing as I cannot get into CWM?

refthemc said:
Maybe its just the rom? try downloading another making sure the download is fully complete. Wipe Data/Cache/Dalvik and Format System for good measure and try again.
Click to expand...
Click to collapse
Thanks, I had never done Format System before. Not sure if that is the reason it worked or the new ROM, but I was able to flash the ROM I wanted.

Couldn't find a quote button for one of the last post so I'll just paste it in.
I am in a somewhat similar boat. I cannot get into Recovery. If I power up the phone normally, it does the boot looping. If I go into hboot, I can get it to go through the motions of flashing recovery, and although it appears to be successful, if I try to go into recovery, it basically boot loops, except for one version which puts a few black lines on the screen and THEN boots. So what is my best option, seeing as I cannot get into CWM?
I am thinking that you might have to flash a copy of the recovery image file to get recovery to work again. I'm not sure where you get a copy, used to be at Koush's website. You would then rename it PB31IMG.zip and let hboot flash it. I've only had to reinstall recovery once before myself and that was on a Eris and used hboot through ADB on my pc so not sure if I told yout eh corect way to do it. Sure others will chime in to help.

kzoodroid said:
Couldn't find a quote button for one of the last post so I'll just paste it in.
I am in a somewhat similar boat. I cannot get into Recovery. If I power up the phone normally, it does the boot looping. If I go into hboot, I can get it to go through the motions of flashing recovery, and although it appears to be successful, if I try to go into recovery, it basically boot loops, except for one version which puts a few black lines on the screen and THEN boots. So what is my best option, seeing as I cannot get into CWM?
I am thinking that you might have to flash a copy of the recovery image file to get recovery to work again. I'm not sure where you get a copy, used to be at Koush's website. You would then rename it PB31IMG.zip and let hboot flash it. I've only had to reinstall recovery once before myself and that was on a Eris and used hboot through ADB on my pc so not sure if I told yout eh corect way to do it. Sure others will chime in to help.
Click to expand...
Click to collapse
DINC Recoveries: http://dougpiston.com/?page_id=85

kzoodroid said:
I am thinking that you might have to flash a copy of the recovery image file to get recovery to work again. I'm not sure where you get a copy, used to be at Koush's website. You would then rename it PB31IMG.zip and let hboot flash it. I've only had to reinstall recovery once before myself and that was on a Eris and used hboot through ADB on my pc so not sure if I told yout eh corect way to do it. Sure others will chime in to help.
Click to expand...
Click to collapse
I've tried dozens of times with several different recovery images - no go. It goes through the motions of installing the image, but nothing changes. It still won't go into recovery, but just starts boot-looping.

A couple of things to note...
With one of the recoveries flashed, I see Build and some other stuff at the bottom of the screen very briefly before it reboots again.
With 2.5.0.5, I see what looks like the messed up screen that you get when you have SLCD and load an incompatible recovery... but then it reboots quickly.

bradinc said:
A couple of things to note...
With one of the recoveries flashed, I see Build and some other stuff at the bottom of the screen very briefly before it reboots again.
With 2.5.0.5, I see what looks like the messed up screen that you get when you have SLCD and load an incompatible recovery... but then it reboots quickly.
Click to expand...
Click to collapse
I would think your only option left is to try and unroot the phone by flashing the RUU, method is in the ROM development section somewhere about getting back to stock 2.2. Then re-root your phone with unrevoked.

kzoodroid said:
I would think your only option left is to try and unroot the phone by flashing the RUU, method is in the ROM development section somewhere about getting back to stock 2.2. Then re-root your phone with unrevoked.
Click to expand...
Click to collapse
The main issue with that is the fact that the first step, setting S-on, involves using recovery.
Has anyone used the engineering hboot? I have SLCD, so I can't see what comes up on the screen. If I can find out exactly where it starts and how to get to fastboot in it, I can at least run fastboot commands from my PC and see what's up.

Ok, I loaded the engineering hboot and can run fastboot commands. I was able to flash backup images of system, userdata, recovery.. but nothing changes as far as trying to boot up. I reloaded the .92 hboot so I could see the screen, and I'm right back where I started. I'm hoping now that I can at least run fastboot commands that I can somehow recover, or at least get it to a state where I can return it.