Develop Bugs

[Q] Tried to Unroot my phone, now stuck at white HTC screen.

Tried to unroot my HTC EVO now its stuck at htc screen. Even if i go into recovery mode it will just get stuck at screen. Im getting frustrated and i dont have warranty on phone. is the phone pretty much done for??

Try running an official RUU to unroot or if you can get into bootloader, you can download a stock PC36IMG file and load it that way.
Links found in this post

i did the pc36 file. it updated my phone, but still stuck at the evo screen. i go to press recovery then goes straight back to htc screen

What PC36IMG file did you use? The one for build 3.70?
The links I posted are for RUUs which are exe files. Connect the phone to the comp and run the RUU.exe file and it should do its thing if the phone can be recognized.

thanks ill try when i get my windows computer running. do you think my phone is bricked??

I'll be honest and say...I'm not an expert and I don't really know if your phone really is bricked or not but I sure hope it isn't! I've seen many threads where people post situations similar to yours and other XDA users say...as long as you can get into bootloader, then no it is not bricked. Just have to find a way to get a stock ROM loaded back on your phone and generally that's through running an RUU.

ok so just install RUU and let it do itz job? just wanna get the s-on somehow so i can take to sprint store.

so im trying to flash it to get the s-on right, but when i click on fastboot it says bootloader then when i press it it goes back to fAstboot. any ideas??

i cant get into bootloader!!

Can you try to download this PC36IMG file HERE. Says you need NAND unlock which you have, hopefully it can installed the rooted ROM with ClockworkMOD recovery, and once that's working try to unroot again. Otherwise...sorry, I'm not sure what else to tell you.
EDIT: How did you install the previous PC36IMG? When you hold VOL DOWN and POWER, do you get to the screen with the Android on skateboards at the bottom?

ok im gonna try it again. I just dont understand when i press fastboot then bootloader why it doesnt go to the black screen. so i can get on my sd card, thats what im not getting... so frustrating!!!

Ok, do you have a microSD card reader of some kind? As long as you can get the file onto the SDcard and once you restart holding VOL DOWN and POWER, it should automatically try to look for the PC36IMG.zip file if you wait for a quick minute or so.

yeah i do. slow computer its still downloading. the first time i did this. it updated and everything. It says do you want to reebot now i said yes. Comes back on and loads to HTC evo 4g screen and just stays there. No sprint boot up or nothing. I might have to use that RUU file if i find someone with a windows computer. I tried that RUU thing at home and it just said USB connection error. oh yeah if i press recovery it just goes to htc screen and thats it!!!

so i updated it. rebooted to htc evo 4g screen and stays there

try this and see if its your same issue forum.xda-developers.com/showthread.php?t=831915&highlight=bricked
and do a search in development with bricked as the header....
I think if you can get the zip on your sd card you should be ok. Not quite sure by what I have read if you have actually done that part as of yet
also this http://forum.xda-developers.com/showthread.php?t=880152
Good Luck

i did the RUU thing. updated, but phone still goes to htc evo 4g white screen and nothgin more

[Q] Boot Loop with No Recovery

So before everyone yells because of my inability to search the forum, please understand that not only have i searched this forum, but just about every other one. And if someone finds a thread with an answer to my question than i will admit defeat and have myself stoned and crucified.
I will greatly appreciate anyone's and everyone's help.
History in cliffnotes
Rooted with Unrevoked about a month ago, since then been running CM 6.
Have been happy with just using stock CM 6 and nothing else, haven't flashed any other kernels, radios, or for that matter roms.
Have always had problems with random reboots but didn't care.
Last night my phone appeared to have the desire to random reboot, and on start up got into a boot loop, just HTC splash boot loop. I can get into bootloader but if i try to go to recovery it is just more boot loops.
I'm running mac OS X however i eventually just tried running RUU on my roommates computer but to no avail, mostly, i think, because my phone can't boot into a state where its recognized by the program or sync, etc...
The real problem
As of now i've gone as far as basically completely unrooting, using a pc36img that i found through you guys here
So if you guys have any ideas, at this point, i'm completely willing to try them because, this was completely random that it happened, and i really am at a complete loss as to what to do besides buy a new phone.
i love you all in a masculine plutonic way. thanks.

well you could always re-root with unrevoked. all it needs is bootloader mode to root it and then once its done, flash a rooted rom on it, then proceed to unroot.
EDIT:
btw, i am a mac user too and unrevoked works great. if it fails, run it again. and no need to use an ruu, look up a thread in our development section titled shpped roms and they have pc36img versions of the ruu. you will be able to root with your mac and unroot all on the device. unrevoked has an s-on zip on their web page. to unroot it, flash the s-on zip then run the pc36img zip from the base of your sd card. thats all!
EDIT#2:
YOU CAN ALWAYS FLASH A RECOVERY VIA BOOTLOADER ALSO AND FLASH A ROM. LET ME KNOW WHICH RECOVERY YOU PREFFER, I GOT BOTH CLOCKWORKMOD AND RA.
EDIT#3: LOL, Sorry i didnt see that you mentioned a pc36img to unroot.

why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom

t3project said:
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
Click to expand...
Click to collapse
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!

Well since you can't get into recovery, we suggested to flash a recovery in pc36img.zip format in bootloader mode.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!

paulieb81 said:
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Click to expand...
Click to collapse
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader

t3project said:
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
Click to expand...
Click to collapse
If you read my message you will see that I DID flash a recovery, that same one you just linked, and it flashed ok, but when i restart and choose to enter the recovery the phone just reboots again!

Did you solve this?

Yes I did, I went back to the store and had them replace the phone. I could not get it to boot into recovery for some reason.

I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App

heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.

ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
Did they give you any problems about s-off being visible in the bootloader when you got your phone replaced? I'm to that point of taking it back with the EXACT same problem but I didn't know if it was an issue. (or is there any trick to get s-on back without being able to load into recovery i.e. a fastboot command?)

i was worried about the s-off as well because i also was unable to change that. all i could find for that was the s-on tool but since u cant actually flash anything, had to leave it s-off. i even tried a battery pull during the radio update on a pc36img so that they wouldnt be able to get to bootloader but i couldnt even brick it. i live more than 50 miles from a sprint store so they didnt make me drive to a sprint store. they sent me a replacement and i mailed my evo back. on the paperwork for the new phone they said i could still be charged 75 dollars for a recoverable phone and 125 for an unrecoverable phone. it was probably 2 weeks ago or so when i sent my old broken evo back and i havent been billed yet so i dont know what if anything they will charge. when i talked to the sprint tech on the phone i told him it was rooted because i knew they would see the s-off and i didnt want to get screwed when i sent them my broken phone and they said "u rooted, ur problem" but he said he would still replace it and he did.

k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm in the same boat buckley. I don't get it?! I did run cm for a couple days but I was always looking at my phone wondering if something was going to happen. Almost gave myself a panic attack so I just went back to sense, lol.

ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
And I just wanted to say, that although you've seen 5, and I've seen around 10, and that does suck, that the fact is, that this is an EXTREMELY low percentage of CM users that are experiencing this problem. With that noted, it's still enough for me to use a different rom, at least until someone can at least figure out what caused that to happen. I am just extremely curious, as to what the actual malfunction with the device is, when this sort of things happens. And why it seems to only be happening on CM. (at least from the reports I've seen around here)

Add me to the list of people with this problem. I think I'm going to try my chances at the Sprint store. They've been good to me so far.

k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It has nothing to do with CM. It is clearly a hardware problem. It has happened on other roms, but more likely to happen to someone using CM as it is the most used Rom.
Sent from my PC36100 using XDA Premium App

Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..

jkxklutz said:
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
Click to expand...
Click to collapse
If its anything like the evo you might want to try and wipe cache and dalvik cache when you get into recovery let it boot back up if that doesn't work try to fix permission if that doesn't work wipe battery stats when your phone is at 100% using battery calibration app and if none of that works do a full wipe and flash a new ROM or unroot and run the ruu of the stock ROM .
Sorry I know nothing about that phone so IDK if any of that will work for you just trying to help and those are pretty much the steps I would take.
Sent from my PC36100 using XDA App

Happened to me
Hey guys this happened to me and i was running cm and sense roms i have had alot of experience with this and its an actual glitch that causes the os to stack on each other and confuse the boot the only way to fix is to wipe the entire phone back to stock if that dosent work call sprint and they gladly replace ur phone due to manufacture defect its been happening to unrooted phones also from the updatesnot being installed properly phone needs to be wiped every time u do a new rom

[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] htc evo 4g huge problem help!!!!!!!!!!

PLEASE HELP ASAP i have a rooted evo and have had it rooted for a year now with no problems but today i flashed a new rom like i have done many times before and it was stuck on the htc evo 4g white screen for 30min so i pulled the battery and went into recovery and went to restore but none of my backups were there so i went to install and no files on sdcard so i pulled out the sd and hooked it up to my computer and all of my files were there so i got a new recovery zip and put it on my sd like so E:\PC36IMG and went back to hboot and pressed down arrow and it said
[1] RECOVERY
do you want to start update?
and i hit yes like an idiot and now it wont boot into recovery and it cant reboot and it gets stuck in a reboot cycle PLEASE HELP
UPDATE
i flashed a new ROM by using the PC36IMG and it booted up but i can only use it for 20-30 seconds before it randomly reboots and it does it over and over i got it to detect the sdcard by using fastboot commands but it still randomly reboots every 20-30seconds and i downloaded rom manager and installed its recovery but when i try to boot into recovery it just goes the the htc evo 4g (white screen) and just gets stuck in a reboot cycle untill i pull the battery. i have been researching this but i cant seem to find an answer so you guys are my last hope before i go to sprint and say i lost my phone and get a refurbished one for $100 which i dont have
SO PLEASE HELP ASAP

Have you tried running an RUU? It could be hardware failure.

teh roxxorz said:
Have you tried running an RUU? It could be hardware failure.
Click to expand...
Click to collapse
mabey but it reboots within 20-30seconds so i dont have enough time to run the ruu

mkeller96 said:
mabey but it reboots within 20-30seconds so i dont have enough time to run the ruu
Click to expand...
Click to collapse
You run ruus through fast boot and I'm curious check of your s-on
Sent from my PC36100 using XDA App

[Q] Phone Freezing At Droid Eye And AThen Bootloops

So i was running a miui rom and did a clean wipe to try and a new rom. I couldn't get past the boot screen of the rom so i figured it was just a bad download. so i went and unrooted the phone. i have Hboot .92 thew radio is 2.15.10.07.07. i have the phone to s-on. i downloaded and installed the stock verizon gingerbread rom by renaming it to th P whatever lol. the reboots gets to the incredible screen then goes the htc quetly brilliant screen then it does the droid sound and i get the red snapdragon logos. but when it get's to the droid eye after it circle goes back and forth once then freezes on the second one. it sits there for like 3 or 4 minutes and then it just reboots to the droid sound and snapdrogon screen then the droid eye and stops and just keeps repeating this. i am hoping someone on might have a cure for this. the only thing i can get into iss hboot. hoping it's not fried. thanks for your time. and sorry for the long post, just trying to be very detailed to get the right help.

scoobntaz1996 said:
So i was running a miui rom and did a clean wipe to try and a new rom. I couldn't get past the boot screen of the rom so i figured it was just a bad download. so i went and unrooted the phone. i have Hboot .92 thew radio is 2.15.10.07.07. i have the phone to s-on. i downloaded and installed the stock verizon gingerbread rom by renaming it to th P whatever lol. the reboots gets to the incredible screen then goes the htc quetly brilliant screen then it does the droid sound and i get the red snapdragon logos. but when it get's to the droid eye after it circle goes back and forth once then freezes on the second one. it sits there for like 3 or 4 minutes and then it just reboots to the droid sound and snapdrogon screen then the droid eye and stops and just keeps repeating this. i am hoping someone on might have a cure for this. the only thing i can get into iss hboot. hoping it's not fried. thanks for your time. and sorry for the long post, just trying to be very detailed to get the right help.
Click to expand...
Click to collapse
Have you tried doing a factory reset from hboot, and then reflashing the ruu (PB31IMG.zip file) thru hboot again. Also why did you go s-on, just makes it way harder to reroot or fix issues like these? The only reason anyone should ever go s-on is if you need to return it to verizon under warranty.

the reason for s-on is because i was selling it and the new owner just wanted it stock. they know nothing about rooting or any of this kinda stuff. i do believe i tried the factory reset but i will give it a go again.

so i believe i have found the problem. and doing some research it's my own fault. i am still on the .07.07 radio baseband and i found out that i should have downgraded before getting s-on. now i don't know if i can fix this problem or did i just ruin my phone. hoping for some good news. thanks

scoobntaz1996 said:
so i believe i have found the problem. and doing some research it's my own fault. i am still on the .07.07 radio baseband and i found out that i should have downgraded before getting s-on. now i don't know if i can fix this problem or did i just ruin my phone. hoping for some good news. thanks
Click to expand...
Click to collapse
Im pretty sure you have to downgrade the radio to get s-on. As in it wont work to get you s-on if your not on the right radio. Are you sure you didnt downgrade and doing the ruu just upgraded it again?
I would try doing the latest ruu.exe with a pc, instead of PB31IMG.zip.

i would love to but the pc will not read the phone because it just boot loops.

scoobntaz1996 said:
i would love to but the pc will not read the phone because it just boot loops.
Click to expand...
Click to collapse
Try flashing the PB31IMG.zip ruu with fastboot. androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html

do you happen to have a workable link for the adb and fastboot. the link on android forums is through megauploiad and is not a workable link.

scoobntaz1996 said:
do you happen to have a workable link for the adb and fastboot. the link on android forums is through megauploiad and is not a workable link.
Click to expand...
Click to collapse
Here ya go: http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip

phone is not recognized in hboot or fast boot. it says hboot usb and fastboot usb on my phone but when i go in the coomand prompt on my pc it doesn't show any devices.

scoobntaz1996 said:
phone is not recognized in hboot or fast boot. it says hboot usb and fastboot usb on my phone but when i go in the coomand prompt on my pc it doesn't show any devices.
Click to expand...
Click to collapse
Have you installed the phone drivers on your pc?

i have installed everything that i can to try and get this phone working. hboot comes comes up on the phone just fine and i can get to fastboot on the phone. when i go to recovery from fastboot it goes to the green triangle then it turns red. i do the volume and power to get to recovery but when it comes up i get a bunch of error messages. and am at a lost with this. all i know is i don't think it is bricked because i can get to hboot. when i try to install another pB file from hboot it either does not do anything or it tells me it failed because it was an older version. i am pretty sure it is a software problem i just can't figure it out.