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
Related
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Sounds like you took a big step and should not have. Next why would you want to go to Verizon? you can not use 4g over there. i think there is a post here or on another android site on getting your phone out of a boot loop with no recovery. Search is your friend
http://lmgtfy.com/?q=stuck+in+boot+loop+without+recovery+android+evo
I found a solution to this exact problem.
Flintr said:
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Click to expand...
Click to collapse
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
marley183rd said:
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
Click to expand...
Click to collapse
i REALLY COULD USE YOUR HELP
need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I am experiencing the boot loop issue also. Really weird, all I have done is root via UnRevoked, use Rom Manager to install CM 6.1.2, and been running this ROM exclusively. I have never overclocked, or even installed or used any task killers in CM 6... I started noticing a couple weeks ago some odd force closes and sync issues with gmail that would come and go. Then, my phone would reboot every once in a while. Sometimes when I was using it, most of the time while it was just sitting on the counter. Then one day it just started the boot loop. Vibrate, white HTC Evo screen for a few seconds, then dark again, over and over. I can't boot into recovery, and have tried a bunch of recovery images (they unpack and update succeeds but attempting to boot to recovery just starts the loop again). I thought about unrooting and bringing the phone back to the store but the instructions I found for unrooting require me to at least get into recovery.... At the time I rooted (Sept '10) I had all the latest OTA... any advice for me to try?
S-OFF
HBOOT-2.10.0001
RADIO 2.15.00.11.19
I made a writeup
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54needed files.
Update
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Haha, I was able to fix my Evo (dont remember what I did) but I have since sold it.
dwreck_ said:
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Click to expand...
Click to collapse
Do you mind pointing me to the image you flashed? I just pulled the battery while flashing a radio, but i'm still booting haha.
You should find it fairly easy if you search Google for eng-pc36img.zip
Looks like the first link.
Sent from my Evo using XDA App
I wish I could, but honestly it's been so long that I dont have any idea.
Thanks cutthroat.
dwreck, at what point did you pull?
I've pulled it twice while it was updating Radio_V2, with the red bar about 1/3 of the way, and nothing about my phone seems to change.
Did you pull a little later? Or did you pull during Radio_Cust? That thing is hard to catch, it updates quickly.
My friend says it took him about a hundred times to fully brick his Evo. Just keep trying I suppose.
Sent from my Evo using XDA App
Sprint was backordered on Evo's. It might take me more than a week to get another one, and it's still 35 bucks. Cutthroat or dwreck, do either of you guys know if it would be safe for me to send my Evo into HTC? I did the battery pull (it took about 20 tries) and the phone doesn't turn on, no led or anything. Will htc know it's rooted regardless?
You should be fine to send it to HTC, my friend has gotten two replaced that exact way. He had no issues with them finding out his were rooted.
Sent from my Evo using XDA App
pthr3e said:
i REALLY COULD USE YOUR HELP
Click to expand...
Click to collapse
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I'd just like to take a sec to give props to cutthroat. His guide is GREAT if you've screwed up your NV files (unfortunately that wasn't my problem). Anyways I appreciate you helping me out even after that.
Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
Many of us are racking our brains trying to figure out what is causing this situation. Everyone who are experiencing this were using CM7, like you, and it happened to of nowhere and for no known reason. I don't think anyone has figured out a workaround, but I could be wrong. I haven't ready through the forums today regarding this issue. Just know that you are not alone, my friend....
Well, it doesn't look too hopeful from what I have seen so far, but thanks for the support. It's good to know that I am not alone.
If you can still access the bootloader, you should still be able to run an RUU through fastboot.
It happened to me, I was one of the first on the forum it happened to, in January. Was never able to fix it, you could spend a loonnngggg time, and get no results. If you search for my threads you can see the ones I started about the subject.
Long story short, I was never able to fix the problem or get S-On. However by doing a battery pull while flashing a rom with a different radio, during the radio installation, I bricked my phone to the point that it wouldn't even turn on. So thats basically your only way out that I know of. You'll have to perform the battery pull upwards 20 times probably before you get the phone to fully brick.
I'm on CM7 nightlies. What are the HW specs of those having these problems? I thought it was due to CWM but there have been some on RA experiencing this too. Just wondering if this is more specific to the newer HW builds/hboots or occurs with all phones.
My Evo is hardware version 003 for what it's worth.
Westibone said:
My Evo is hardware version 003 for what it's worth.
Click to expand...
Click to collapse
When you select recovery, what happens?
I had same issue in Jan after flashing miui.
tried the suggestions on this thread..but nothing worked:
http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html
Had to replace my phone...that seems to be the only way out of this.
This is the reason I have stayed away from CM for so long. I keep seeing these horror stories about bootlooping, etc. I know its awesome when its running, but when it comes to the point where bricking your phone on purpose is a good thing, something is wrong For those that it has happened to above, did you get your new one and go back to CM (or any other AOSP rom)?
teh roxxorz said:
When you select recovery, what happens?
Click to expand...
Click to collapse
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
My God, another one. It's weird these seem to be happening more and more...
Westibone said:
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Hopefully, your RUU will work. Others who have attempted to this this very thing still couldn't make it work. Me, k2buckley and others have yet to figure it out and believe me, we've tried everything within our experience range. A solution will be found, I have no doubt about that, but "when" is the question that I cannot answer.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
k2buckley said:
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
Click to expand...
Click to collapse
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Same Here
Wow, what a coincidence, this just happend to me last night. I had just finished installing and flashing the new, SavagedZen(MOD)-RC1-Evo4G, Rom. Went to bed and sometime during the night the phone got stuck on restarting on the EVO white screen and turning off and on continusly. I have tried all the efforts of putting the stock ROM back on and everything else mentioned in this thread, but to no avail. Like you said, cant get into recovery or anything, just keeps looping through startin and stopping.
With all that is said so far on this thread, it looks like a new phone is the only way to fix this.
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
By some awkward chance, have you tried a full wipe, and then flash a sense rom?
teh roxxorz said:
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Click to expand...
Click to collapse
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
k2buckley said:
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
Click to expand...
Click to collapse
I hope my case doesn't come back to haunt me. Seems like we got a T Virus of phone crashings going around...those already along their way [like you and I] are imune...the newer ones get sucked in. we haz to fix this soon-ishly.
Signed up for XDA because I got problems, and you guys seems to know everything when I need to use my googl-fu to solve a problem.
Have lurked for hours trying to figure this out. Nothing solves it.
Phone specs: Phone is babied, never dropped etc. Evo 4g on sprint, rooted unrevoked3 method, was running CM7 nightly95.
Have been running this for several days no issue, (since nightly95 came out.)
Was running a CM7 stable build before this. No issues.
And then the problem: Was just using my phone like normal at work it decided it wanted to reboot on me, once, restarts fine, and about an hour later reboots into a boot loop. It was on a charge cable to wall outlet, not pc when this happened, if that matters.
From the boot loop, just starts, vibrates, shows the htc evo screen maybe 10 seconds and reboots.
I can get into Hboot, (power + vol down) but can not get into recovery. if it's selected the boot looping starts again.
I have tried clearing storage, and flashing a couple PC36IMG.ZIP Since it seems to fix other peoples. Since the most I can figure out is putting the SD card into the computer and try loading files from Hboot.
Last one being this: http://forum.xda-developers.com/showthread.php?t=791019
Still boot looping, no recovery.
Any help is appreciated. But I am noob when it comes to command line adb stuff. Just so you know.
what PC36IMG are you trying to flash exactly?
try this one, its amon ra 2.3, its the one i have as a backup in case mine foks up, just take amonra out of the name so its only
PC36IMG.zip, then put in the root of your sd card, turn on phone while pressing volume down, to go into bootloader let the phone recognize it and select yes when asked to update, if thats gets your recovery up try wiping and restoring a backup
If all else fails, try the attached doc.
First, boot into the bootloader, look at the top of the screen and see if it still displays "S-OFF". If it does not, you need to re-root your device. If it displays "S-ON" then If you have a card reader, connect it to your PC or Mac and copy the contents of the SD card to your computer. Afterwards, re-format the card. Now copy a freshly downloaded rom and a freshly downloaded copy of the PC36IMG.zip file for amon-RA recovery version 2.3 to the root of your SD card (not in any folder). Re-insert the card in your EVO and boot to the bootloader. The PC36IMG.zip file *should* be automatically detected and you *should* be prompted to install it. Follow the prompts to install. Installation will take approximately 10 seconds. Afterwards, boot into your new recovery. Go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card. After that, flash the rom. Be patient during the initial boot process. You *should* be good to go afterwards.
posting & replying via the XDA Premium app.
HipKat said:
If all else fails, try the attached doc.
Click to expand...
Click to collapse
Tried this a bit ago.
Now it doesn't loop. But it's not any better.
It just boots, htc evo for a few seconds, and then vibrates approx 5 times and screen goes black and the top led flashes green.
Anybody else think this sounds like the bootloop of death? If so, there's no known fix. You can run the PC36IMG, but if that's what it is, you'll never get recovery or any rom to boot up.
I hope I'm wrong, though.
(from... Evo/MIUI/Tapatalk)
this sounds just like what happened to my phone. After spending hours on the forums and PM'ing back with a few people, I diagnosed it as the bootloop of death. Which sounds like exactly your going through....
no fix unfortunately...if your s on you can go back to sprint and get a brand new one. If not (like me) smash it pay the $100 deductible and get a refurb. Sucks I know.
For a more in depth thread search "boot loop + no recovery".
If I understand correctly, it's a problem with a partition size and was common with a certain Hardware version (0002?)
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me. I'm sorry for your luck, but it sounds like plainjane is right. I agree, you got the bootloop of death, and most likely won't recover from it. Do you you have insurance ?
Sent from my PC36100 using XDA App
k2buckley said:
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Well, After HipKat first suggestion I can get to s-on. I may try it again with a different RUU but I think it's dead too.
So, since it will be S-on, hopefully there is a new phone in my future, without any money out of pocket.
Thanks for the help guys. I'll let you know if anything fixes it, or what sprint says.
HipKat said:
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Click to expand...
Click to collapse
From what I remember reading about a month ago, when this seemed to be happening a lot, was that it was random.
Didn't start when you were trying to boot up, just suddenly, randomly, terrifyingly, and like death in the night....power off, and never to fully boot again. Just typing about it now kinda scares me like a hex. I hope to finish typing this sentance.
@ OP, really sorry about your luck, man. We all feel you.
Sent from my PC36100 using XDA Premium App
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
fergie716 said:
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
Click to expand...
Click to collapse
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
HipKat said:
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
Click to expand...
Click to collapse
Yea I was reading this happened a few days ago to a guy who was on Decks 2.3.4.. IDK I told my brother to just flash a radio and pull the battery while flashing to try and get a replacement.. But the whole thing freaked me out lol.. Feel bad cuz it could happen to anyone I suppose
Your lucky to get S-ON, I only read about one other person able to get S ON after bootlooping.....take it to the Sprint Store, they should give you a new one on the spot if they have stock, if not they order one overnight. Could have been way worse...
Right now it says s-off again. But acts likes it's on, can't erase anything through fastboot/adb.
Going to try to repeat the RUU install a few times to see if I can get it back to s-on then take it in.
I was one of the first 3 or so people to report about this on the forum - it happened to me over 4 months ago. Anyways, if you flash a PC36IMG-eng and pull the battery at exactly the right time, while the radio is updating your phone will completely brick - it won't even turn on. Then you can take your phone in and just tell sprint it wont turn on. Note, it took me over 20 battery pulls before it finally wouldn't turn on, but its your best option if you can't get S-ON.
Wow that's crazy. I've never heard of the bootloop of death.
Sent from my PC36100 using Tapatalk
Do a search for Boot loop white screen and you'll find a ton of threads/posts about it