Develop Bugs

[Q] REALLY could use some help. Seem to be bricked... HELP?

Okay so first off, let me just thank everyone who's willing to contribute to helping my issue ahead of time. I highly respect this community, and everything that everyone has done towards making android what it has become.
ANYWAY - I'm completely screwed, or so it seems. I cannot boot into anything, no ROM, no recovery. I've tried replacing the PC36IMG.zip on the root of my SD card. I've even downloaded the "RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe", and tried to start over completely, but even that did not work.
Whenever I try to restart my phone, or enter recovery from the HBOOT menu, I get a constant boot loop of the EVO white screen. Over and over, that's all it does. On my HBOOT menu I am showing:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I don't know what other options I have in order to restore my phone. Everything was working fine. I was running MIUI 12.3, with the stable CFS kernel. I woke up this morning, phone worked normally, then decided to randomly reboot. After that, it was over. I couldn't reboot into recovery, or simply reboot the phone.
If anyone can help out, it's greatly appreciated.

I'm not much help for that, but try this file:http://db.tt/AQItwCr
It's clock work mod recovery. If you can boot into hboot, you can flash that. Although, I'm assuming your rooted because you flashed mui*. So its pointless if your not rooted. Let me know what happens.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

Rydah805 said:
I'm not much help for that, but try this file:http://db.tt/AQItwCr
It's clock work mod recovery. If you can boot into hboot, you can flash that. Although, I'm assuming your rooted because you flashed mui*. So its pointless if your not rooted. Let me know what happens.
Click to expand...
Click to collapse
I placed the .zip file on my SD card, and boot my phone into the HBOOT menu. It loaded the file, then put me back at the menu. I attempted to enter recovery > same issue. I'm placed at the white EVO 4G screen, and it keeps boot looping...

xxjuicymintxx said:
I placed the .zip file on my SD card, and boot my phone into the HBOOT menu. It loaded the file, then put me back at the menu. I attempted to enter recovery > same issue. I'm placed at the white EVO 4G screen, and it keeps boot looping...
Click to expand...
Click to collapse
Pretty fukkin weird. It shouldn't even boot up, it should just go into recovery.
What recovery were you running before?
Sent From My HTC Evo 4G Using Tapa Talk Pro!

Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.

mizzos4 said:
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
Click to expand...
Click to collapse
This is true. I didn't even think of that. You will need to reroot after that. Can somebody post a link for this guy? We can help each other out.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

mizzos4 said:
Once you RUU back to stock, you should be able to reboot into the phone. Don't go into recovery because you don't have a recovery anymore. If the phone doesn't boot up into Sense, then the RUU you grabbed is corrupt and you need to re-download or grab from somewhere else. Your hboot is now showing S-ON because you basically unrooted your phone so there wouldn't be any recovery.
Click to expand...
Click to collapse
I just ran it again, and the install process completes. Everything seems to go smoothly. The phone reboots, and you see the HTC EVO 4G white screen, but then it just goes black, restarts, and repeats.
I'm still unsure as to why I can't seem to boot into anything. Don't know what caused this. I do a lot of reading in these forums, and I've never heard of anything like this. Did quite a bit of googling, trying to read up on others that might've 'bricked' their phone, etc.

Also, the RUU file that I used, I gained from this thread:
http://forum.xda-developers.com/showthread.php?t=840843

Try running the RUU a second time. Same thing happened to me with one of my EVOs, and I had to run the RUU twice to get it to work.

_MetalHead_ said:
Try running the RUU a second time. Same thing happened to me with one of my EVOs, and I had to run the RUU twice to get it to work.
Click to expand...
Click to collapse
I've tried this as well, with no success.

xxjuicymintxx said:
I've tried this as well, with no success.
Click to expand...
Click to collapse
Sucks.... ;(
Sent From My HTC Evo 4G Using Tapa Talk Pro!

Welp.... do you have TEP? If you file your claim with them tonight you should have your replacement by tomorrow.

_MetalHead_ said:
Welp.... do you have TEP? If you file your claim with them tonight you should have your replacement by tomorrow.
Click to expand...
Click to collapse
Haha, I'm not sure actually. I'm on a friends plan.
But, there's gotta be a way to get past the problem I'm having, with THIS Evo.
Shouldn't be a need to order a new one.
Hopefully someone in these forums can figure out a solution.

xxjuicymintxx said:
Okay so first off, let me just thank everyone who's willing to contribute to helping my issue ahead of time. I highly respect this community, and everything that everyone has done towards making android what it has become.
ANYWAY - I'm completely screwed, or so it seems. I cannot boot into anything, no ROM, no recovery. I've tried replacing the PC36IMG.zip on the root of my SD card. I've even downloaded the "RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe", and tried to start over completely, but even that did not work.
Whenever I try to restart my phone, or enter recovery from the HBOOT menu, I get a constant boot loop of the EVO white screen. Over and over, that's all it does. On my HBOOT menu I am showing:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I don't know what other options I have in order to restore my phone. Everything was working fine. I was running MIUI 12.3, with the stable CFS kernel. I woke up this morning, phone worked normally, then decided to randomly reboot. After that, it was over. I couldn't reboot into recovery, or simply reboot the phone.
If anyone can help out, it's greatly appreciated.
Click to expand...
Click to collapse
You were using an AOSP ROM with the new hboot? Didn't you have to use the HTC kernel?

xxjuicymintxx said:
Haha, I'm not sure actually. I'm on a friends plan.
But, there's gotta be a way to get past the problem I'm having, with THIS Evo.
Shouldn't be a need to order a new one.
Hopefully someone in these forums can figure out a solution.
Click to expand...
Click to collapse
I wish I could be of more help. Good luck and godspeed.

xHausx said:
You were using an AOSP ROM with the new hboot? Didn't you have to use the HTC kernel?
Click to expand...
Click to collapse
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!

xxjuicymintxx said:
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
Click to expand...
Click to collapse
I think you screwed yourself by updating hboot. Haus* is working on an easy 2.02 hboot root.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

xxjuicymintxx said:
Yes, I was using MIUI 12.3, which is AOSP based. I don't think I had the new hboot until sometime after this problem started. One of the PC36IMG.zip's that I put on the root of my SD I believe was from somewhere in the new HBOOT Root thread on this forum, but I can't remember 100%.
Prior to that, I had the old HBOOT, I'm quite sure. I've never had a problem until. I've flashed plenty of ROMS, and recovery has always booted for me. MIUI wasn't giving me any issues, until earlier today. Randomly, POOF...it restarted...only, it boot looped. Didn't think it'd effect my recovery, though. I've had boot loop issues with other ROM's before, and have just booted into recovery, and solved the problem from there.
Who knows what happened to me earlier, or why, but it really is a pain. It's hard not having a phone. Especially when you've been blessed with an Evo!
Click to expand...
Click to collapse
That's what it was, the 2.02 hboot is not compatible with older phones and vice versa. Is your NAND still unlocked? (shows S-OFF) If so you may be able to do something with it.

xHausx said:
That's what it was, the 2.02 hboot is not compatible with older phones and vice versa. Is your NAND still unlocked? (shows S-OFF) If so you may be able to do something with it.
Click to expand...
Click to collapse
No, it's not unlocked. It' showing S-ON.
&& this problem occurred BEFORE I was even running the hboot 2.02 --
I don't remember exactly what I had before, I believe it was the .76 hboot.
Everything was working perfectly fine.
I had just installed MIUI 12.3 a day earlier. Used it fine. Had everything set up the way I liked it. Went to sleep, woke up, phone still worked fine. Then it randomly reboot, and this problem started there.
The hboot 2.2 was only applied, I believe, when I put a PC36IMG.zip on my SD card root, that I had read about in a reply from someone on the 2.02 hboot thread.
Now it seems that I have only further screwed myself, apparently? idk.
I've tried running the latest RUU stock, to restore my phone to normal. NO luck.
Tried running it twice in a row, as per advice of someone earlier -- still no luck.
Endless reboots, no matter what. Yet, I can still get into the hboot menu. that's about it.
There's BOUND to be a way to fix this...
I can load PC36IMG.zip's ....but nothing else.
is there something that someone can package for me to revert back?
I have no idea, hence the reason I'm here.
HELP!
[and big thanks, of course!!]

Same thing happened to me. Lost recovery, and couldn't boot into rom. Just rebooted on splash screen over and over. Couldn't pull a logcat. Tried flashing recovery through fastboot, through bootloader, flashed renamed roms, the pc36img that I originally used from toasts 2part, etc. Nothing failed or threw errors. Only change I noted was that it reverted my custom splash screen to stock. Last ditch effort I ran an RUU with the phone in bootloader, which took a few tries but successfully "updated." Still couldn't boot into the OS. RUU restored me from engineering s-off back to ship s-on and I replaced it via warranty, $35 new phone on the spot.
Good luck, hope you manage to find something that works for you. After fastboot flashing failed I jumped on here and google hoping to find a fix, and searched for a week to no avail.

Need help stuck on a Reboot.

Ok here goes. I went to sprint and got my phone changed. Hardware(3) Started rooting my phone from ota 3.29 using the autoscript method without no avail. This is not my first time rooting and what hapened to my phone is strange. Kept on reading and found that unrevoked method 3.31 which had the latest ota 3.70. Update my phone which was not rooted previously to ota 3.70. Now i have a endless reboot it start ups and every 7 minutes its reboots automaticaly. I can access bootloader so i tried using fastboot usb to use with an officiall Ruu with succes. But still have the same problem. So i went and used clear storage and used the phones factory reset but the problem persits. Dont know what else to do. One thing i dont know much about android but when iam in bootloader an doesnt reboot. Can i do a diference using this acces point?. Any help is apreciated please. Thank you.

Let me get this straight. You have the newest update from Sprint?Have you try to flashing a rom as a PCM36img.zip?

It wont recognize my sd card or sync with my computer. Thanks for the reply.

So this happened before you tried unrevoked? Just right after you took the 3.70 OTA? If so, I would take it back, it seems like certain Evos are plagued with random reboots.
Sent from my PC36100 using XDA App

Thanks man. I'll take it back tomorrow. Guess i root another day jajaja. Take care.

can you get into boot loader?

[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] Post Skyraider 4.0 Flash, now stuck on splash screen loop.

I have had my phone rooted for about a month now. I was running CM7 and things were fine and dandy. Decided that I wanted to try a different ROM. Downloaded and installed Skyraider 4.0 today. It seemed to be working fine. It was nice to have some sense back on my phone. Out of nowhere the phone reboots. Now I am left with a phone that cycle reboots and will not even get to the boot animation. Just the HTC Incredible white splash screen...black screen....vibrate....HTC Incredible white splash screen...cycle and cycle and cycle. I am able to get to the hboot screen by pressing the volume down button. From the hboot I tried to get into recovery mode but it goes back to the splash screen cycling.
I tried to reflash a stock ROM back onto the phone through hboot and it said that it was succesful. On restarting though, it went right back to the splash screen cycling.
Any help would be GREATLY appreciated! I have searched and searched and am still stuck cycling with on the splash screen.

So you used the PB31IMG.zip that restores the phone to stock? And you can get into hboot but it wont boot into recovery from there? I'm not really sure what else to suggest, there may be some things that can be done with adb but I haven't ever gotten that far, I'm sorry. Typically the RUU is successful in getting people out of bootloops or other tough spots.
Sent from my ADR6300 using XDA App

k_nivesout said:
So you used the PB31IMG.zip that restores the phone to stock? And you can get into hboot but it wont boot into recovery from there? I'm not really sure what else to suggest, there may be some things that can be done with adb but I haven't ever gotten that far, I'm sorry. Typically the RUU is successful in getting people out of bootloops or other tough spots.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
k_nivesout
Exactly. I used the PB31Img.zip. Hboot cycled through and said that it was successful. I excitedly rebooted thinking that all of my dreams had come true. But I was none-the-better with the cycling issues. I used Doug Piston's method to get the phone to stock.
I am still in S-Off. Would it help to get the phone back to S-On before reflashing to stock or would this make a difference?

I could be wrong but I don't think S-ON would really effect anything as far as flashing the stock rom. How long have you let it try to boot up? And you can't get into recovery from hboot? It sounds like it could be a hardware issue but it seems really strange that it would just quit working like that.
Sent from my ADR6300 using XDA App

I didn't think that S-On/Off would make a difference but I'm desperate for an answer. I have let it cycle through the splash screen....phone turning off....splash screen 20-30 times before realizing that it wasn't getting anywhere. I am able to get to the hboot screen, but unable to get into recovery. I've flashed three different versions of clockwork to see if that might be the issue but no luck there.
I believe that my warranty may have ran out on the phone so I don't know what to do next.

It seems weird that you can get into hboot but not recovery. I'm really not sure what it could be, I wish I could think of something that would fix it.. I was thinking there was a tiny chance that maybe you just weren't giving it enough time to boot but if its looping that many times, its not gonna do it. Have you flashed any radios or anything else that could have possible messed something up? Is your hboot version the latest (.92)? Tried flashing the stock radio (7.28)? I'm really not sure if any of this could help, I'm just trying to think of anything you might be able to try since you can only get into hboot..
Sent from my ADR6300 using XDA App

Never flashed any different radios. I went from stock to CM7 to Skyraider. Hboot version .92. The radio was flashed to stock when I used Doug Piston's PB31IMG.
So now, the configuration of the phone is:
INCREDIBLEXC XC SHIP S-OFF
HBOOT 0.92
MICROP 0417
TOUCH PANEL ATMEL224_16ab
RADIO - 2.15.00.07.28
Jul 23 2010, 18:06:51
I believe that I was successful in flashing the 2.5.1.2 ClockworkMod Recovery onto the phone. I previously had 3.0.0.8 or whatever ROM manager flashed onto the phone for me.
Nothing that I have done has made any difference on getting through the splash screen onto the boot animation.

Everything looks correct as far as stock settings go. I really can't think of anything else to try as my knowledge is limited to things you can do in recovery or in hboot and you've already done everything that I can think of to fix it. The only other thing I can think of is trying some things in ADB, but its been so long since I've used it I couldn't help with it. I'm assuming you've tried all the options in hboot, I think there's a data wipe/factory reset option? I'm sorry, I can't think of anything else, wish there was something I could do! If you got the phone from Verizon, you should have a one year warranty. The incredible came out like 13 months ago so I would think it would still be under warranty?
Sent from my ADR6300 using XDA App

I had the same problem months ago and i used a card reader to read my sd card and install a fresh rom in the root directory of the sd card. Reinstalled the card and flashed the new rom , make sure to erase any previous rom as it was pobably corrupt.
Sent from my PC36100 using XDA Premium App

[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