Develop Bugs

[Q] I need help

Early this morning, I rooted my Droid Incredible using the Unrevoked 3 method. After doing so, I completely forgot to create a nandroid backup and went ahead to install a custom ROM (Cyanogen Mod). Now here's the issue. I want to get back to the Stock 2.2 sense. I tried to unroot my droid, but nothing seems to be working. Can someone please help?

You need to flash a stock rom back before unrooting.

Where can I get a stock ROM. I think I just bricked it now because it won't even boot Cyanogen Mod. It's stuck at the HTC Incredible white screen.

Do you know what type of screen you're using? Slcd or amoled ? Each method has a different way of unrooting. Just in a Google search engine type in who to unroot Droid incredible, and then the what screen it is. You can potentially brick your phone if you use the amoled method on a slcd one.
With the amolcd screen it's as simple as finding the right file, hence doing the search engine. When you get the file, all you have to do is just place it in the root of your phone, and turn off your phone and press and hold the power button and the volume button at the same time.
With slcd you have to do it different way. Assuming you haven't messed with the radio, if you did, you have to flash a 07.28 radio. But assuming you didn't touch that, you have to flash something that puts s-on. Ans then after that you have to put a file into the root of your SD card and then flash appropriately.
Now I did this multiple times, rooting and unrooting, and for some reason there's always so
Something drawing me back into rooting and flashing a new rom. There's no greater satisfaction than knowing you can do anything with your phone. But it's entirely your choice.
Oh yeah, to figure out what screen you have go to settings then about phone then hardware information and 002 is amoled and 003 is slcd. Google is your best friend after you figure out what screen you have. Good luck!
Sent from my Incredible using XDA App

You haven't officially bricked it until you can't power it on at all. Try taking out the battery and then holding the power button and volume down. If you can access the white boot screen where it gives you a choice of accessing recovery there is still plenty of hope. Don't freak out you haven't bricked your phone
Sent from my Incredible using XDA App

I can't load anything. The farthest I can go is to ClockWord Recovery, and when I try to reboot the phone, it's stuck on HTC Incredible. That being said, I can't check what screen type I have. However, before it was bricked, I did flash a file to make S- on. And, when I tried degrading my firmware, nothing happened. :/

OK first off the name of the first that you flash should start with a "p" I don't exactly remember the exact file name. Make sure you have s-on, I'm sure you do. And then put that p something file into the root of your SD card. root as in, it isn't in any folder.
Now when you flash this, you don't do it in clockwork recovery, you do it through hboot I believe. Hboot is the white screen when you hold on the power button and volume down. It should automatically read the p something file. And it'll ask you if you want to update. Say yes and then just let it install
Sent from my Incredible using XDA App

PB31IMG, I attempted to Flash it in HBOOT, but it didn't work. Now, I can't even connect my Droid to my computer.
I'm screwed.

Sorry for the double post, but I just followed some whacked-out tutorial that told me to format everything via Clockworkmod Recovery...now when I boot my phone, it goes straight to HBOOT and won't do anything...

OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App

lazysleepyboi said:
OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.

Can't remember exactly how to tell but know you can tell by the model #under the battery on the phone.
Sent from my ADR6300 using Tapatalk

If you could get to clockwork u should be able to flash a rom if your sd wont mount use a card reader and plug directly into your comp
Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
HTC Incredible 2.3.1

Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader

lazysleepyboi said:
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader
Click to expand...
Click to collapse
That's the exact tutorial that I followed, but it didn't work.

Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
ok can you tell me how you flashed the included file? did you put it into the root of the SD card?

For now i would get a rom on your sd so your phone will boot up and do a nand backup so you at least have a working phone when i get home ill try and help you out
Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
HTC Incredible 2.3.1

Ok if you have a card reader for you SD card load it in and open you card on your PC. You need to make sure that the sd card is in FAT32 format otherwise when you try to load the PB31IMG file it wont read it. To check this go to my computer, find the removable drive for the SD card right click and go to properties, you should see what format its in. If it's FAT format copy everything from your sdcard to a folder on your PC, go back and right click on the removable drive and format the card to FAT32. Then of course copy everything back to your card. Then try the PB31IMG file again in hboot.
I would personally just go in recovery and wipe to factory, then choose the option to install zip from card and install the rom or which ever rom you want so the phone loads again. Good luck!

For now, I'm going to flash a new rom and hopefully I can fully boot my Droid again. Afterwards, I'll try to flash that file again. BUT, the first time I did it, I put it in the root of my SD card and booted HBOOT and nothing happened.
EDIT: This ROM is going to take close to 30 minute to download , so I guess I'll be back in 30 minutes; don't leave me please.

do you have a sd card reader? if you do, pop out your sd card and make sure it's format is FAT32, nothing will happen if it isnt FAT32

[Q] Possible Bricked Phone

My phone is stuck at the white Evo splash screen. This happenned after I performed the autoroot procedure located at: http://forum.xda-developers.com/showthread.php?t=838448
I have tried all kinds of ways to bring it back with no success. I downloaded shipped roms 3.30 and 3.70 (3.70) is what my phone originally was. The RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe will not run on my windows 7 machine I assume it's corrupted and I have downloaded it from two different sources. The RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe runs but it always tells me that my battery is below 30% even though I plug the phone in to the charger and after a few minutes the LED turns green. Then I tried downloading the 3.70 rom as a zip file, named it pc36100.zip, put it in the root of my sd card, then I went into recovery mode and I told it to start the update. It looks like it works but I get a message at the end that says "partition update fail!" and then it asks me to reboot and I'm right back at the endless white evo splash screen. I even tried to load several times using the evo-recovery where I was able to pick which image I wanted to phone to update but it fails with a symlink error of some sort.
I'm stuck. Any help would be appreciated here.
Thanks

Try PC36IMG from here http://forum.xda-developers.com/showpost.php?p=8097472&postcount=1

deeztech said:
My phone is stuck at the white Evo splash screen. This happenned after I performed the autoroot procedure located at: http://forum.xda-developers.com/showthread.php?t=838448
I have tried all kinds of ways to bring it back with no success. I downloaded shipped roms 3.30 and 3.70 (3.70) is what my phone originally was. The RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe will not run on my windows 7 machine I assume it's corrupted and I have downloaded it from two different sources. The RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe runs but it always tells me that my battery is below 30% even though I plug the phone in to the charger and after a few minutes the LED turns green. Then I tried downloading the 3.70 rom as a zip file, named it pc36100.zip, put it in the root of my sd card, then I went into recovery mode and I told it to start the update. It looks like it works but I get a message at the end that says "partition update fail!" and then it asks me to reboot and I'm right back at the endless white evo splash screen. I even tried to load several times using the evo-recovery where I was able to pick which image I wanted to phone to update but it fails with a symlink error of some sort.
I'm stuck. Any help would be appreciated here.
Thanks
Click to expand...
Click to collapse
I would also try running the RUU and PC36IMG a couple more times, maybe download them from a different source. Do you have HTC sync installed on your computer? I believe it's needed to use the RUU. So if you pull your battery out, reinsert it, then plug your Evo into a wall charger, the light goes steady green after a few minutes? Strange, I'd try a different RUU. Did you download from here? http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu . I haven't experienced problems like this before (fortunately) but I've also read about people needing to format their SD card before it would work, using the PC36IMG. Not sure why, but possibly something corrupted on the SD card? Did the auto root give you any sort of errors or anything? Or did it just appear to work, and then this happened?
Also, you could try running the RUU from fastboot mode. Boot to the bootloader, select 'fastboot', and then try the RUU

HTC Sync is indeed needed for the RUU in .exe form.
Boot into hboot by holding down the volume down button while turning on your phone. I believe you choose hboot USB and then run the RUU exe.

k2buckley said:
I would also try running the RUU and PC36IMG a couple more times, maybe download them from a different source. Do you have HTC sync installed on your computer? I believe it's needed to use the RUU. So if you pull your battery out, reinsert it, then plug your Evo into a wall charger, the light goes steady green after a few minutes? Strange, I'd try a different RUU. Did you download from here? http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu . I haven't experienced problems like this before (fortunately) but I've also read about people needing to format their SD card before it would work, using the PC36IMG. Not sure why, but possibly something corrupted on the SD card? Did the auto root give you any sort of errors or anything? Or did it just appear to work, and then this happened?
Also, you could try running the RUU from fastboot mode. Boot to the bootloader, select 'fastboot', and then try the RUU
Click to expand...
Click to collapse
The fastboot method worked! Awesome. So, in the hboot menu, it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?

deeztech said:
it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
Click to expand...
Click to collapse
Correct. You can copy any ROM (suggesting nandroid backup first) to SD card and flash it

deeztech said:
The fastboot method worked! Awesome. So, in the hboot menu, it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
Click to expand...
Click to collapse
Sweet, I'm glad it worked for you. So it says you're S off, even after running the RUU? I've never used the Autoroot method, but it must flash unrevoked forever, somewhere in the process. Well, if it says you're S off, I believe the only thing you're missing before you can flash anything is a custom recovery, which you most likely do not have, after running RUU. I believe that since you're s off, you can just flash a custom recovery from the bootloader, and then flash a rom. You could also use ROM manager to flash a recovery, you'd just need to download and install the Super User app, I believe. I think that should work for you? I've never tried to just flash a recovery from a stock ROM, right after an RUU, but if you're s off, i dont see why you can't do that. Download the PC36IMG I attatch here, make sure its named PC36IMG, put it on the main directory of your sd card, boot to the bootloader. Let it scan and ask you to update. Select volume up for yes. After that's done, you should have custom Amon Ra V2.3 recovery. From there, you 'should' be able to flash ROMs. good luck.
Edit: wouldn't let me upload the PC36IMG for some reason. Instead, click this link to download. http://db.tt/7jGH2CA

erik077 said:
Try PC36IMG from here http://forum.xda-developers.com/showpost.php?p=8097472&postcount=1
Click to expand...
Click to collapse
Uhh no. That PC36IMG.zip is waaay outdated. You know they are all different, right? Just because it's a PC36IMG.zip does NOT mean it's the same file as the next one.

I used that one in two situations...
1. when my friend phone was bricked
2. when did unroot
both times that file worked for me

erik077 said:
I used that one in two situations...
1. when my friend phone was bricked
2. when did unroot
both times that file worked for me
Click to expand...
Click to collapse
I did as you suggested and installed the custom recovery. Worked beautifully! I was able to install the MIUI rom and it's a beautiful thing. Thanks a lot for all your help.

Np, that's why we here
Sent from my PC36100 using XDA App

help!!!!
im stuck on step 8 my phone is showing the red triangle with the ! the DOS promt says...
waiting for the phone...
found the phone connected as 'recovery'
setting up a temporary recovery...
**daemon still not runningerror: cannot connect to daemon
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
what do i do?

[Q] Bricked if I cannot reach recovery?

Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!

Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.

Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk

Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]

Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone

Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk

popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon

hope that helps

@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk

popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.

popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.

Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.

That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk

You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked

I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad

Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.

Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.

I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.

popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?

[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.

[Q] I'm Stuck in Bootloader.....Help

Today I was flashing a new Rom (the GingerSense Leak to be specific) and when I was in Rom Manager I decided to update my recover from 2.5.0.7 to 3.0.0.5 (not sure if either of these numbers are right). When I finally rebooted into what I thought was recovery my phone sent me to the bootloader menu. Which normally isn't a big deal and it means that the recovery version didn't take. This time when I selected reboot it rebooted back into the bootloader menu. Now I can't get anywhere, no recovery and no way to reboot the phone.
Am I F$%#ed?
I did do a search and no one has quite had the same problem I am having.
Thank you for the help in advance.

Stalte said:
Today I was flashing a new Rom (the GingerSense Leak to be specific) and when I was in Rom Manager I decided to update my recover from 2.5.0.7 to 3.0.0.5 (not sure if either of these numbers are right). When I finally rebooted into what I thought was recovery my phone sent me to the bootloader menu. Which normally isn't a big deal and it means that the recovery version didn't take. This time when I selected reboot it rebooted back into the bootloader menu. Now I can't get anywhere, no recovery and no way to reboot the phone.
Am I F$%#ed?
I did do a search and no one has quite had the same problem I am having.
Thank you for the help in advance.
Click to expand...
Click to collapse
Try running an RUU.

Not sure how advanced of a user you are, but you can try and check if your phone is recognized via USB while in the bootloader and try pushing the recovery on via ADB. That way, you can just restore a good NAND instead of having to start over.

Stalte said:
Today I was flashing a new Rom (the GingerSense Leak to be specific) and when I was in Rom Manager I decided to update my recover from 2.5.0.7 to 3.0.0.5 (not sure if either of these numbers are right). When I finally rebooted into what I thought was recovery my phone sent me to the bootloader menu. Which normally isn't a big deal and it means that the recovery version didn't take. This time when I selected reboot it rebooted back into the bootloader menu. Now I can't get anywhere, no recovery and no way to reboot the phone.
Am I F$%#ed?
I did do a search and no one has quite had the same problem I am having.
Thank you for the help in advance.
Click to expand...
Click to collapse
Does your bootloader show Ship S On or Ship S off? If it's S off still, you can probably just flash a PC36IMG of a recovery, using the bootloader. That looks like what teh roxxor attatched, based on the file size of the PC36IMG he attatched. If you're not S off anymore, I'd suggest running an RUU to flash you back to stock, and then start over from that point.

k2buckley said:
Does your bootloader show Ship S On or Ship S off? If it's S off still, you can probably just flash a PC36IMG of a recovery, using the bootloader.
Click to expand...
Click to collapse
That would be much easier than what I suggested. lol I don't know why I didn't think of that.

k2buckley said:
Does your bootloader show Ship S On or Ship S off? If it's S off still, you can probably just flash a PC36IMG of a recovery, using the bootloader. That looks like what teh roxxor attatched, based on the file size of the PC36IMG he attatched. If you're not S off anymore, I'd suggest running an RUU to flash you back to stock, and then start over from that point.
Click to expand...
Click to collapse
Yep its still of I'm pushing the PC36IMG to my phone now thank you very much

Stalte said:
Yep its still of I'm using the PC36IMG to my phone now thank you very much
Click to expand...
Click to collapse
Sweet, glad you got it back up and rollin'

after like 4 hours of trying I can not get it my adb to recognize my phone. What now.....
PS: I can get it to recognize my phone in fastboot

Stalte said:
after like 4 hours of trying I can not get it my adb to recognize my phone. What now.....
PS: I can get it to recognize my phone in fastboot
Click to expand...
Click to collapse
So where are you at exactly? Did you get the recovery flashed earlier, and your phone is back up and running? And now you're just trying to get ADB to work, and you're having trouble..? OR, are you still stuck, and never got the phone back online earlier?
Do you get an error when you try to use adb, or is it just not seeing the device?

k2buckley said:
So where are you at exactly? Did you get the recovery flashed earlier, and your phone is back up and running? And now you're just trying to get ADB to work, and you're having trouble..? OR, are you still stuck, and never got the phone back online earlier?
Do you get an error when you try to use adb, or is it just not seeing the device?
Click to expand...
Click to collapse
Im still in bootloader I have done everything I can think of. Its not seeing the device.
c:\android-sdk\tools>adb devices
List of devices attached
^^^^NO DEVICES LISTED^^^^^.......SIGH.....
c:\android-sdk\tools>fastboot devices
HT12THL02230 fastboot

My 12 year old little brother solved it for me, He told me to take out my micro sd card put it in my computer and than drag and drop the PC36IMG on the sd card than booted. SUCCESS!!!!!!!!!!!!!
Thanks Everyone!!

Stalte said:
My 12 year old little brother solved it for me, He told me to take out my micro sd card put it in my computer and than drag and drop the PC36IMG on the sd card than booted. SUCCESS!!!!!!!!!!!!!
Thanks Everyone!!
Click to expand...
Click to collapse
Haha, I was confused on what you were trying to use adb for. Were you just trying to push the .zip to your sd card? The reason it wasn't working is because you were in the bootloader. ADB only recognizes if the phone is in recovery, or booted into the OS. That's why it wouldn't see adb for ya. And yes, now that you have the PC36IMG on your sd card, you should just be able to apply that using the bootloader, and then you should be able to get up and running again.

[Q] Did I brick it?

I think I may have bricked my Incredible...I pulled it out to put some games on it for my daughter to play. It had the latest OTA (2.3.4) and I wanted to root it. Played around with various methods to root and nothing worked. Downgraded to 2.2, and now it boot loops. If I have it plugged in, it will boot, but if unplugged it just loops. It won't install recovery from HBOOT, so I don't know what to do. Any suggestions? Thanks!

riot1031 said:
I think I may have bricked my Incredible...I pulled it out to put some games on it for my daughter to play. It had the latest OTA (2.3.4) and I wanted to root it. Played around with various methods to root and nothing worked. Downgraded to 2.2, and now it boot loops. If I have it plugged in, it will boot, but if unplugged it just loops. It won't install recovery from HBOOT, so I don't know what to do. Any suggestions? Thanks!
Click to expand...
Click to collapse
Ok so your definitley on 2.2 now?
S-on or off?
Radio version?
Hboot version?
Does the phone vibrate 5 times when trying to power on?

Software version shows 2.2
S-ON
Radio Version not sure how to check
HBOOT .92
Does not vibrate 5 times.
Thank you very much for the help!!

I had the same issue with not booting unless plugged in. I also had 5 vibes though with it.
Just from hearing that, read through the 5 vibes sticky and see what you can do.
Sent from my ADR6300 using XDA App

Tried the 5 vibrates fix, can't flash the stock rom in HBOOT and the RUU says there is a USB connection error.

Radio (baseband) version is at the top of hboot. If you have the 2.15.00.07.28 radio i would plug the phone into the pc so it boots, and then try using unrevoked to get root and s-off.
The ruu exe probably gave that error because you dont have htc sync installed which gives you the right drivers for the ruu. Im not sure why you cant get a PB31IMG.zip ruu to flash thru hboot. Does it give any errors?

cmlusco said:
Radio (baseband) version is at the top of hboot. If you have the 2.15.00.07.28 radio i would plug the phone into the pc so it boots, and then try using unrevoked to get root and s-off.
The ruu exe probably gave that error because you dont have htc sync installed which gives you the right drivers for the ruu. Im not sure why you cant get a PB31IMG.zip ruu to flash thru hboot. Does it give any errors?
Click to expand...
Click to collapse
I do have the 2.15.00.07.28 radio, but the USB doesn't seem to be working because unrevoked doesn't see the phone. I tried with HTC Sync installed and it still didn't work. I don't get any errors, it just won't install the PB31IMG file. I really do appreciate the help, I want to get this thing working again!!

riot1031 said:
I do have the 2.15.00.07.28 radio, but the USB doesn't seem to be working because unrevoked doesn't see the phone. I tried with HTC Sync installed and it still didn't work. I don't get any errors, it just won't install the PB31IMG file. I really do appreciate the help, I want to get this thing working again!!
Click to expand...
Click to collapse
In the phones settings do you have usb debuging checked (on) and fastboot unchecked (off). If your on 2.2 there will not be a fastboot option.
Also the drivers for unrevoked are different than the drivers for the ruu. You can get the unrevoked drivers from the unrevoked site, and the ruu drivers from htc sync. Note that to install one set of drivers, you need to uninstall the other ones first.
Also when trying the ruu thru hboot, the file must be named exactly PB31IMG.zip, and be on the root of your sdcard (in no folders).
Does hboot find the file, parse it (progress bar on the right) and then abort, or does it not find it at all?

Yes and yes.
Installed the Unrevoked drivers, but still no luck.
It finds the file and ignores it.

riot1031 said:
Yes and yes.
Installed the Unrevoked drivers, but still no luck.
It finds the file and ignores it.
Click to expand...
Click to collapse
I would copy all the files of your sd to your pc, and then format the sdcard fat32 with windows. Then copy your files back to the sdcard and download a fresh copy of the PB31IMG.zip you can get it here http://pvillecomp.com/?page_id=22, you will want the froyo one not the gingerbread. Then try flashing it thru hboot again. You said you also couldnt flash cwm thru hboot. This makes me think there is an error on your sdcard, or your doing something wrong with the PB31IMG files. If your s-off you should be able to flash an ruu or recovery thru hboot.
Not trying to call you a noob or anything but you might want to check this out http://pvillecomp.com/?page_id=79.

cmlusco said:
I would copy all the files of your sd to your pc, and then format the sdcard fat32 with windows. Then copy your files back to the sdcard and download a fresh copy of the PB31IMG.zip you can get it here http://pvillecomp.com/?page_id=22, you will want the froyo one not the gingerbread. Then try flashing it thru hboot again. You said you also couldnt flash cwm thru hboot. This makes me think there is an error on your sdcard, or your doing something wrong with the PB31IMG files. If your s-off you should be able to flash an ruu or recovery thru hboot.
Not trying to call you a noob or anything but you might want to check this out http://pvillecomp.com/?page_id=79.
Click to expand...
Click to collapse
LOL, no offense taken! This is the only phone I've had trouble with. I've owned 2 Incredibles, a DROID 3, a BIONIC, and now two Rezounds. Never had an issue rooting/flashing/etc. til now. I've formatted the sdcard a few times now, and I've tried three different sdcards. I think this phone just hates me. I have two other Incredibles sitting here, I may bite the bullet and give her one of those. I'm not s-off, could that be the problem?
Edit: It let me flash the stock froyo image in HBOOT, but I'm still in the same place. Unrevoked doesn't see the phone.

riot1031 said:
LOL, no offense taken! This is the only phone I've had trouble with. I've owned 2 Incredibles, a DROID 3, a BIONIC, and now two Rezounds. Never had an issue rooting/flashing/etc. til now. I've formatted the sdcard a few times now, and I've tried three different sdcards. I think this phone just hates me. I have two other Incredibles sitting here, I may bite the bullet and give her one of those. I'm not s-off, could that be the problem?
Edit: It let me flash the stock froyo image in HBOOT, but I'm still in the same place. Unrevoked doesn't see the phone.
Click to expand...
Click to collapse
On your pc with the phone plugged in go to device manager. At the top does it say android phone, and when you expand it android adb interface or composite interface?
Other than that im not sure what the issue could be. Now that the 2.2 ruu flashed, does it still bootloop? Mabey the cable or the usb port? Do other phones work with the cable, both charging and data?

I had the issue with not booting unless plugged in also. However, I was getting the 5 vibes.
Follow the 5 vibes of death tutorial up until it says your USB should be fixed and go from there. Which is a problem you're having if I'm understanding correctly.
That's my suggestion.
Sent from my ADR6300 using XDA App

I finally threw in the towel and grabbed another Incredible from my drawer of phones. This one rooted just fine and she's playing with it as I write this. Is there a way to take a nandroid backup from the working phone and get it onto the non-working phone somehow?