Develop Bugs

Rooted DINC, can't get past recovery?

Just rooted my new DINC, got into the main screen. Went into Clockwork and flashed a nandroid from a different device. Now I cant even get back into CWM. If I hold down and power I get hboot, but anything after that gives me 5 vibrations and blinking green lights. wtf?>

I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?

DroidHam said:
I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?
Click to expand...
Click to collapse
not really that i know of
best bet is to ruu back to stock and start over
EDIT: first link i sent wont help you
http://d01.megashares.com/index.php?d01=CHoQD3B
put this on your sdcard, rename to PB31IMG.ZIP
boot into hboot, when it asks to apply the update, say yes
give that a shot
for future reference, nandroids from phones are not interchangeable

I dont know how to use ADB, and that tutorial assumes you can run zips via recovery, which I cant...

Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock

DroidHam said:
Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock
Click to expand...
Click to collapse
yea sorry, use the new link and destructions instructions i posted, should get ya running

damn, that link wont start the download

Do you have a micro sd card reader that you can put into your pc or laptop? You need to get that PB31IMG on the root of your card. Then get into hboot to flash.
Sent from my ADR6300 using XDA App

Yea, I put it onto the root, applied the PB31IMG and rebooted. Same fcking problem. WTF?!?!

DroidHam,
try pulling the battery, wait around 10 minutes, put the battery in and boot the phone. Yes, it is very important to wait for that long.
Post your results if it booted or not, i had the same issue.
Also let me know if this is a refurbished phone.

ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?

Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App

DroidHam said:
Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I noticed you mentioned that while powering on you say you are holding down...down is diagnostic mode, you should be holding up to get to recovery.

After applying the ruu. Try re rooting
Sent from my ADR6300 using XDA App

How do I root if i can't get past hboot??!
Sent from my LogicPD Zoom2 using XDA App

I attempted to root a new Incredible for a friend and had the same thing happen a few days ago. I was able to create a nandroid backup via CWM recovery, and then flashed CM 6.1. CM then bootlooped when trying to boot for the first time. After this point I was unable to get into recovery. The screen would just go blank and would vibrate multiple times. At one point I did manage to succesfully get into CWM recovery without the screen going blank, but then recovery would not recognize the SD card. I restarted and was never able to get back into recovery.
I then attempted to flash a PB31IMG.ZIP from HBOOT that was supposed to restore it to factory state. At this point the phone when blank in the middle of flashing and would not do anything other than vibrate when I would attempt to power it on.
I told them the phone just inexplicably died and they exchanged it at the Verizon store. Everything went perfect with the replacement phone. I figured what happened was a one time thing, but after reading this I would definately be hesitant to root anyone elses Incredible.

Do all phones have hboot?? I don't wanna get screwed. But this was sent was Asurion.... i really need to fix this. There must be a way please!!!
Sent from my LogicPD Zoom2 using XDA App

Just got off work... do the battery pull, wait 10 min, then the start phone see what happens.
I'm not sure at what point you are with the RUU image at this point so take out your sd card just to be safe.
You are getting into the Qualcomm diagnostic mode, which is basically 5 buzzes and then the green light keeps flashing green correct?
I will be on and off for the next few hours to see your results.
DroidHam said:
ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?
Click to expand...
Click to collapse

5 vibrate = defective usb plug/phone... time for nother refurb. theres a couple posts on it, happened to me.

I don't know much.. but I'm pretty sure this thread is in the wrong section. Mods should move this to Q&A or General...

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

I cant believe it!!!

Ok! So i was running fresh 3.5 on my evo 4g and everything was running great. I decided that I wanted to add a battery percent on the battery indicator. I download a zip file that would allow me to do that...I put it on the root of my sd. I tried flashing it with clockwork mod 3.0 but it didnt let me cuz it came up with an error saying to update my binary and script. So i googled on how to bypass that error and it said to use the ra recovery(the other recovery program,i think thats what its called ) so i flashed ra with rom manager. I rebooted my evo and went into recovery and flashed the zip file then a couple of minutes later it said it was complete(no errors came up during the flashing process). I rebooted my evo after the flashing was done. This is where it starts getting weird! I turned my phone back on and after the white screen a black screen came up and didnt go away. After about a minute the phone vibrated about 4 times and the indicator light started flashing green. I couldnt power down so I had to take out the battery. I turned it back on and it booted up to the fresh boot logo. It tried to reboot itself about 3 times and without success the black screen came up and vibrated with flashing green light. Took the battery out for an hour then I booted it to the boot menu, went into recovery to try to delete the zip file and all it did was give me the black screen, vibrated and flashing green lights. I checked to see if s-off was still engaged and it wasnt. S-on was showing. I think some how that zip file made that happen. I have a nandroid backup. I dont have recovery and s-on is engaged. What should I do? This is the file that I flashed( smooth-sense_evo1.0.2_batteryonly ) Sorry if Iam posting this in the wrong section. Any help would be appreciated. Thanks

Holy Wall-O-Text Batman!
But getting to your issue:
You enabled security again. Flash the stock RUU found in the most up-to-date unrooting guides and go back to stock. Re-root again using Unrevoked and then flash again. Mind you, you will be starting over more or less.
The reason why I'm telling you to unroot and then root again is that you want to get rid of that funky flash. Its the safest way possible.

So I need to unroot first (even though it says s-on)
Then root again with unrevoked
Then flash stock ruu

Flashing the RUU should unroot for you. It will undo any mods except for s-off from unrevoked.

Still no luck.
This is what i have done.
Ive tried rooting again using unrevoked 3 but it doesnt pick up my evo when i plug in my phone. It does come up in my device manager but its not assigned a drive letter. Yes i did enable hboot usb. Yes my drivers are installed right.
Ive tried different ruu's but they wont detect my evo. Ive tried different stock PC36IMG's and they will update with no errors but when it reboots into the the screen with green arrows and a phone it vibrates 4 times then turn off.
Can you guys be more specific on the steps that in need to do. Thanks once again.
Info:
HBoot 2.10
Radio 2.15

I feel your pain, same thing happened to me after months of successful evo hackery. Was very difficult to convey to people the extent of random roadblocks preventing all the supposed fixes. I followed every suggestion, maybe 200 separate tries at a workaround, but in the end I had to trade it in for a refurb.

To flying low,
I still have faith especially with everybody helping me out. I know theres a workaround cuz i still have hboot up and running even tho i lost recovery and rom.

Can i use unrevoked when iam in hboot? Cuz thats the only option i have.(i think)

calishooter said:
To flying low,
I still have faith especially with everybody helping me out. I know theres a workaround cuz i still have hboot up and running even tho i lost recovery and rom.
Click to expand...
Click to collapse
you need to flash the RUU in hboot or run the RUU in Windows...it doesnt matter whether it says s-on or not all it will do is restore the phone back to its shipped factory settings and unroot you

What you do:
Find and download the latest RUU. I Think this is it: http://shipped-roms.com/shipped/Sup...51.1_Radio_2.05.00.06.10_release_CL195459.exe (download should start automatically)
name it PC36IMG.zip
Place it on the root of your sd card (root of sd card = no in any folders, just put it on there).
Boot into bootloader (power off, hold volume down and turn power on to get there)
it'll ask if you wanna parse update, hit volume up for yes.
basically, this will flash the stock rom back onto your phone. Since you're s-on already, this will complete a full unroot. Then simply re-root your phone like you did the first time and you're back in the game

Ok i will try flashing the ruu from the link that you gave me.
Thanx. Will report back soon.

I tried the link but its a .exe file not a zip. So I converted it to a zip file using winrar. I renamed it PC36IMG and put it on the root of my sd. Ran it and it just got to the checking part and it stoped checking. I did it 2 times with same result.I also formated my sd card to fat32.

calishooter said:
I tried the link but its a .exe file not a zip. So I converted it to a zip file using winrar. I renamed it PC36IMG and put it on the root of my sd. Ran it and it just got to the checking part and it stoped checking. I did it 2 times with same result.I also formated my sd card to fat32.
Click to expand...
Click to collapse
If you want to run the ruu in PC36IMG form, you need the right file.
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip < Rename to PC36IMG, then flash in the bootloader.
The ruu.exe is meant to be run from a computer, with the phone booted into the bootloader, and mounted to the pc in fastboot.

Yes i agree tech roxxorz. I was just doing what he told me. Ive tried RUU.exe before but it wont recognize my evo niether does my computer and iam in hboot usb mode. I will try your link and repot back.

calishooter said:
Yes i agree tech roxxorz. I was just doing what he told me. Ive tried RUU.exe before but it wont recognize my evo niether does my computer and iam in hboot usb mode. I will try your link and repot back.
Click to expand...
Click to collapse
Well you can't do it in hboot usb. You have to select fastboot, connect to the pc, and when it shows up as fastboot usb in blue on the phone, then you run the ruu.exe.
Though either method will work.

So when I click on fastboot on my evo, what do i click on next to run RUU.exe cuz I only have reboot or power down options.

calishooter said:
So when I click on fastboot on my evo, what do i click on next to run RUU.exe cuz I only have reboot or power down options.
Click to expand...
Click to collapse
Turn the phone off. While turning the phone off, hold vol+down till you see a white screen with androids skateboarding [bootloader] From there, after it scan, navigate to fastboot with the volume keys, press the power button to select, then connect to the PC via usb cable. When it says 'fastboot usb' in blue, run the ruu exe on the pc.

OK got it. Will report back soon.

Aye aye cappy.

I did what you wrote. The ruu.exe gave me an error 170-usb connection error. I booted into the bootloader by holding down the power button and volume down why the evo is turned off. It scaned the sd card, I selected fastboot and plugged in my usb cable. It said fastboot usb highlighted in red.

[Q] Phone won't boot, can't get into recovery.

I've been looking through threads for hours and have tried a lot of what has been suggested. At first it just started randomly bootlooping ( white htc screen, restart). I then tried some guide on a thread that had me ADB then RUU, once that was all done It got to the white htc evo screen, turned black then vibrated 5 times and the green light started to flash. I can't get into the recovery menu, I click it and it just goes straight to white htc screen. I've flashed multiple PC36IMG's with different recoveries, with no luck.
My fuse is burnin low...
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-1.39.00.04.26
APR 14 2010, 15:41:34

*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..

IxHaku said:
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
Click to expand...
Click to collapse
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there

What rom were you running? Some users have had a bootloop of death, no coming out of it, on CM7. I think it has happened on other AOSP roms as well, but you mainly see it on CM7 - probably because of the larger user base.
I have yet to see a solution for it, I think everyone else had to report it lost and pay the $100 deductible through insurance. The only hope is to keep running RUUs and hopefully one will stick.
(from... Evo/MIUI/Tapatalk)

Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though

IxHaku said:
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
Click to expand...
Click to collapse
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.

teh roxxorz said:
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
Click to expand...
Click to collapse
Does it matter which RUU I use? (2.1,2.2)

reverepats said:
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
Click to expand...
Click to collapse
Exactly! Do not worry about flashing a RUU at this time. Click on amon RA in my signature to download the PC36IMG.zip for amon RA and place it on the root of your SD card. Remove any other file with that name. Boot onto the bootloader (simultaneously press the DOWN volume & power button until your device starts) and then follow the prompts to install. Installation should take no more than 10 seconds. Afterwards, enter your new recovery, connect your device to your computer, select the USB-MS option and then copy the contents of your SD card onto a folder on your computer. After that, select the USB-MS option again to disengage. Now go to the wipe menu and wipe EVERYTHING it. When you're done, download a fresh copy of the rom you want to flash and flash it or copy a nandroid backup to your SD card and restore it. Be patient, either way, with the initial bootup.
pecking & swyping from my EVO 4G (XDA Premium)

Alright so I tried everything I could... So I took it into a sprint store. Told the guy this happened when doing the most recent update. Right there he went into the bootloader menu, I thought I was screwed... but he didn't say anything about the S-OFF. Eventually I came back and they ordered me another one.. probably a refurb. He said it was going to be free, and I don't have insurance. Guess I got lucky.
Thanks everyone for the input.

Incredible won't boot into CM7 or Recovery

I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?

This is a known issue. This happened to my phone and 2 subsequent replacements before I got one that it didn't happen to.
I'd call Verizon or take it in - hopefully you're still in your warranty.

thumpernc24 said:
I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?
Click to expand...
Click to collapse
If you can get into hboot. you should be able to RUU to stock and re root.

synisterwolf said:
If you can get into hboot. you should be able to RUU to stock and re root.
Click to expand...
Click to collapse
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?

thumpernc24 said:
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?
Click to expand...
Click to collapse
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on

synisterwolf said:
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on
Click to expand...
Click to collapse
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!

In order to get s-on you will need a custom recovery installed and then use the s-on tool provided by unrevoked. So you will need to flash a custom recovery thru hboot and then flash the s-on tool thru recovery, and then ruu either thru hboot with a PB31IMG.zip, or with a ruu.exe with your pc. You can get the recovery image and ruus from here http://www.pvillecomp.com. You can get the s-on tool from the unrevoked forever site.

thumpernc24 said:
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!
Click to expand...
Click to collapse
same way you got it off.
unrevoked.com has this info see link below. i also quoted the area you need to look but read it all please.
http://unrevoked.com/rootwiki/doku.php/public/forever
Installation Instructions
To install unrevoked forever on your phone, perform the following steps.
If your phone does not already have a custom recovery, use unrevoked3 to root your phone.
The installation process cannot take place if the phone does not have a custom recovery installed.
Download the most recent ''unrevoked-forever.zip'' to a temporary location on your computer.
The update can be installed like any custom .zip file. Simply flash it from your custom recovery. Both Amon_RA and Clockworkmod Recoveries support custom .zip installs from the sdcard.
Either select the option to install a .zip from your SD card, or apply it as an update.zip as follows:
Place the update.zip file into the root of your SD card. You can do this with adb with the command: adb push unrevoked-forever.zip /sdcard/update.zip
Reboot your phone into recovery mode. You can do this by removing your phone's battery, holding down the VOLUME DOWN button, and inserting the battery; at the menu, press VOLUME DOWN to highlight recovery, then press POWER to select it.
Did you read the important safety information above?
Do so now before continuing.
Select apply sdcard:update.zip from the menu.
Press VOLUME DOWN until Yes is highlighted, then select it.
Review the output to determine if there were any errors.
If messages beginning in E: appear, stop! If possible, join IRC for support.
Restart the phone normally, then reboot the phone into the bootloader. This can be done by holding VOLUME DOWN while powering the system up. Observe at the top that S-OFF appears.
Optional, but recommended: show your support (and your S-OFF bootloader) by flashing a custom splash screen!
"How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update."
---------- Post added at 12:10 PM ---------- Previous post was at 12:01 PM ----------
i also found this video for you. i hope it helps.
http://androidforums.com/incredible...ideo-howto-unroot-incredible-downgrading.html

I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say

thumpernc24 said:
I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say
Click to expand...
Click to collapse
So you can get into hboot and your s-off, but you cant get clockwork recovery to flash as a PB31IMG.zip? What does it say when it auto searches for the file? You say you cant get into recovery, what exactly happens when you select recovery in hboot?

Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!

thumpernc24 said:
Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!
Click to expand...
Click to collapse
Well if they cant get into hboot they cant check if you are rooted so your good to go. once it gets to factory they just plug it into a machine and it reflashes everything so they dont check it.

as I said before - when I select recovery it does the same thing as when i tried to normal boot (well now the recovery option isn't even there anymore)
But what it did was go to the white HTC Incredible screen and then just start rebooting over and over....

similar problem
i flashed the new cyanogen 7.1.0 stable earlier today and did a complete wipe. 3g wouldn't work no matter what i tried. suddenly, the phone is now in a boot loop (just rebooted on it's own). I get one vibrate, the white "HTC Incredible" screen and it reboots, rinse, repeat. I do have access to hboot (0.92).
I have attempted to flash what appears to be every available option for recoveries including clockwork, RA, and stock. it says everything installs fine and i reboot. still unable to access recovery in any way, just starts the same boot loop.
attempted RUU both via PC and .zip extraction. PC method says i'm not connected via usb despite proper drivers and phone recognition by window 7 and .zip acts as if everything applies appropriately then produces the same boot loop.
I have tried everything I can find over the last 6 hours of searching various forums. Anyone have an idea on a potential fix or a way to get s-on without being able to access recovery?
I'm about to exercise my insurance plan and put this phone under my tires and slowly back up...all replies are greatly appreciated