Related
I posted this in the Official Radio Thread over in the dev section, but I don't want to steer that discussion off topic. Here's the gist:
I rooted my stock 2.2 Inc yesterday with Unrevoked 3.2, everything worked fine. I then loaded the 2.15.00.09.01 radio linked here, again, worked great. This morning I decided I was going to remove some bloatware (CityID, Skype, etc), so turned off the phone so I could boot into recovery. Went into HBoot, but realized I still had the PB31IMG.zip file from the radio update on my SD card. The HBoot was waiting at a "Do you want to update?" prompt, so I pulled the battery. That's when things turned to crap. I haven't been able to boot past the white logo screen since then. I can still boot into HBoot, but everything I select from there results in the same logo screen lockup.
UndergroundWire suggested:
Boot into Hboot. When it asks you if you want to apply the update, select NO (down volume I believe). Go Into recovery. Reboot Phone.
BE VERY CAREFUL NOT TO APPLY THE UPDATE AGAIN.
It happened to me before. I panicked and did the same thing like you before. It seems the phone had a hiccup and the only way to boot it normal is to go into hboot --> Recovery --> Reboot.
As long as you see any kind of screen, it's not bricked. Again be very careful not to apply the update twice.
Click to expand...
Click to collapse
Which I tried. I went into HBoot, selected No when asked if I want to update, then No when asked if I want to reboot. I then select Recovery, but I get the same results. White logo screen and nothing more. I remembered to press the power button to try to get into recover, did so at various stages, but no success.
So at this point, I'm dead in the water. Does anyone else have any suggestions? It seems that I can get into HBoot, but any option I select ends up hanging on the logo screen. Also, can anyone tell me, If I'm s-off, can I simply put the older radio's PB31IMG.zip on the sd card and apply it (to downgrade from this 2.15.00.09 radio), or do I need to do some prep work first?
Thank you.
Doc
Delete that radio from your SD . Do you have root? If you do restore your nandroid backup. If you did not look around and find a stock 31 to flash are you s off whats your software version?
Sent from my ADR6300 using XDA App
Don't jack with the radio anymore find a stock image to run from hboot and run the update . Just make sure the image is compatible with your radio version.
Sent from my ADR6300 using XDA App
Jonathan062 said:
Don't jack with the radio anymore find a stock image to run from hboot and run the update . Just make sure the image is compatible with your radio version.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
So I downloaded the 2.15.00.07 radio from the previous thread, installed it, and got the phone back!
Thanks a lot to everyone who helped me along, big sigh of relief ;-)
Incidentally, Yes, I was s-off with Froyo. And I couldn't do a nandroid restore because it would never boot far enough to get to that menu.
Thanks again!
Doc
Glad you got it fixed. Be super careful with radios! Congratulations.
Sent from my ADR6300 using XDA App
If there's a next time, don't panic and pull the battery again.
Just an FYI, all the radios in that thread are full images not incrementals. Flashing the same radio twice will not brick the device. That was only true for a leaked update a while back.
http://forum.xda-developers.com/showpost.php?p=8029185&postcount=99
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.
So I have rooted numerous Evos but never had this problem. It seems to be getting stuck on the White HTC screen. It will not go into recovery or boot to rom, but lets me use HBOOT. Any ideas guys?
Anything guys?...
Sent from my PC36100 using XDA App
On your computer, download a copy of the stock rom PC36IMG.zip, put it on the root of your sd card and load that through hboot....
Sent from my rooted evo using the xda app
Ok trying now...
what method did you use? i used the same method for my hardware 2 evo on my hardware 4 (before i knew that actually mattered) and that happened to me. i had to run the RUU to recover it
ps to Vandelay007: Seinfeld = greatest show in existence
Well it booted using the method above. But the main problem with the phone was before I tried to root, the phone was randomly restarting. So I'm gonna try to RUU and then try to root. Unless any one has a more efficient idea.
So I decided to RUU and same thing happened where it would not boot. Gonna try flashing the pc36img again.
pc36img worked and phone is booting up, but still having the problem with random restarts..... any ideas guys?
CEspaillat said:
pc36img worked and phone is booting up, but still having the problem with random restarts..... any ideas guys?
Click to expand...
Click to collapse
Have you ever over clocked.. i think setcpu can store a file on your sd card and cause problems.
No the phone was brought to me stock. They did the sprint update and the restart issues came then. No root. I was attempting to root in order to clear data, but didn't get to boot. Now after ruu, I had to use the 3.70 pc36img to get phone to boot. But it continues to reboot and after 3-4 reboots it will get stuck on white HTC screen. No idea where to start.....
CEspaillat said:
No the phone was brought to me stock. They did the sprint update and the restart issues came then. No root. I was attempting to root in order to clear data, but didn't get to boot. Now after ruu, I had to use the 3.70 pc36img to get phone to boot. But it continues to reboot and after 3-4 reboots it will get stuck on white HTC screen. No idea where to start.....
Click to expand...
Click to collapse
What hboot is it?
Sent from my PC36100 using XDA App
It started as .76 but now with ruu its 2.10
CEspaillat said:
pc36img worked and phone is booting up, but still having the problem with random restarts..... any ideas guys?
Click to expand...
Click to collapse
Dude numerous people have been having random reboot with their 4 month old evos like me. You should have it replaced. Load a ruu and return it. Because it will get worse as in as soon as it boots up.
Sent from my PC36100 using Tapatalk
CEspaillat said:
So I have rooted numerous Evos but never had this problem. It seems to be getting stuck on the White HTC screen. It will not go into recovery or boot to rom, but lets me use HBOOT. Any ideas guys?
Click to expand...
Click to collapse
This happened to my 002 randomly one night. Sucked...luckily I had warranty & I got a 004 new evo free. However, the new camera doesn't with with anything! So on every rom I flash without sense kernels I have no camera :/
So is there no way of fixing it?
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
I have an Evo with 0.76.2000 hboot that bootloops upon powering it on, even when going to recovery. I've tried flashing multiple PC36IMGs from hboot, but after "parsing", it just goes back to the hboot menu without installing the .zip.
I was running CM7 happily before this happened. The phone was sitting on the charger and it started bootlooping out of the blue. I haven't tried fastboot as of yet (I've never worked with fastboot because I've never had to), but the fact that all the usual fallback methods aren't working is bizarre.
Any help is appreciated. From what I've read on cases similar to mine, this isn't something that can be fixed, but maybe somebody has made it out of this predicament alive.
Question, does your phone get hotter than usual? I mean like around the lower bottom of the phone towards the charging port?
Sent from my PC36100 using xda premium
When I found it bootlooping on the charger, it was a bit warm, but not more than normal. I just tried flashing a recovery via hboot, and after a seemingly successful install, booting into recovery still gives me bootloops.
Just to clarify, when I say bootloop, I mean the white "HTC Evo" screen over and over - I don't make it to splash.
EDIT: After looking into it more, this looks to be unresolvable, so I'm going to put my efforts into getting S-on so I can take it to Sprint. I've tried several RUUs to no avail, so I'm still taking ideas.
Don't worry about getting S-On. All they're gonna do is try to power up, see it boot loops and be dome with it, in most cases. I really doubt they try to get into recovery, Hboot, etc.
And again, why do the mass majority, almost ALL of these cases come from people running CM 7?
HipKat said:
Don't worry about getting S-On. All they're gonna do is try to power up, see it boot loops and be dome with it, in most cases. I really doubt they try to get into recovery, Hboot, etc.
And again, why do the mass majority, almost ALL of these cases come from people running CM 7?
Click to expand...
Click to collapse
Had another case yesterday like this pulled the battery he was on cm7 and he lost recovery+ bootloop and ruu didn't help
Sent from my PC36100 using XDA App
With stuff like bootloops, they do tend to check for s-off. I had a similar bootlooping problem on a stock, never rooted Evo that I got as a replacement. When I took it into Sprint for a replacement, they checked hboot, tried to boot into recovery, etc.
I doubt you'll be able to get s-on. If you flash a radio through hboot then pull the battery during the installation then the phone won't boot again at all. Otherwise you may get stuck with paying the deductible to get a replacement if they wanna blame it on s-off.
Supersonic Evo 4G | MIUI | Tapatalk
I'm having difficulties flashing a radio, which didn't come as much of a surprise. About half the time, hboot doesn't even check the SD for a PC36IMG. Thanks for the suggestions, guys and gals, but I think the Evo has taken her last breath. I'll ensure she sees a proper burial.