yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] deviouskater:
For knowledge.

What were your fastboot commands you did?

What was the command to wipe data for bootloader. Edit I just read it again. I haven't check is there an option to wipe data from bootloader
[EVO 4G Q&A, Help & Troubleshooting] thebeast614:
The only command I remember using is the 'fastboot flash' command...and yea the bootloader has an option to wipe data

Sent from my nightly EVO
[EVO 4G Q&A, Help & Troubleshooting] deviouskater:
I'm not surevif your having the same problem as ppl here. Could it be easy as clearing data (storage) in bootloader. Has anybody tried clearing there storage. .76 bootloader has clear storage option I'm not sure if others do
[EVO 4G Q&A, Help & Troubleshooting] NasTraDooMis:
After running the pc36img, there was still no recovery available to me so what i did was uninstal rom manager and re download it from the market. Still no recovery, so i flashed amond ra in rom manager, still nada, re-flashed clockwork and nada, and then re-flashed amond ra once again and then recovery appeared for me.
[EVO 4G Q&A, Help & Troubleshooting] boobaroo:
Your problem is not the same as everyone elses here on this thread. We can not even boot up to be able to start the phone. You were able to acces the market and all good things. We cannot. So your problem was only with recovery, ours is with the whole phone.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
We've been talking about the S on tool and various ways to possibly flash it in the last few pages....The problem with these guys, that i think you missed, is that they cannot get to recovery. No recovery. No rom. THE ONLY part of the phone that they CAN access is the bootloader/fastboot. THAT is it. There is no booting. There is no recovery. There is only HTC EVO 4G splash screen and bootloder. That's all their Evo's will do. Nothing thus far has gotten them out of this. Tried reflashing recovery, numerous times, of all versions. Tried RUU's, PC36IMG's of RUU's. They tried downgrading the bootloader to the Eng.76 and ran an RUU. Still just splash screen. Still S off. Since the Unrevoked S on tool needs to be flashed in recovery, and not the bootloader, these guys are SOL as far as that goes. The only thing they haven't tried yet, is lowetax's suggestion of using fastboot commands to erase the recovery, and then try reflashing it. I'm waiting to see if someone reports back the results of that.
[EVO 4G Q&A, Help & Troubleshooting] thebeast614:
No this was my exact problem...and that's what fixed it for me...I'm not saying it'll fix it for everyone but maybe it will help find the proper solution...trust me I don't think there's any way it could be as simple clearing the phones memory and rebooting but it didn't boot into recovery until right after I did that...and I was checking every time I did something...one thing I know is that this is definitely something strange that seems to be happening to cm7 users but not when anything is being done to the phone

Sent from my nightly EVO
[EVO 4G Q&A, Help & Troubleshooting] lowetax:
the clear storage and reformatting the sd card are two other variables,

but want to hear if BrashL can access the evo via fastboot,

and fastboot erase recovery and fastboot flash it ...
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
BrashL reformatted the SD card already, and he tried to boot without the SD card in. I had instructed him to try that in a PM. I don't recall if he specifically tried to clear storage using the bootloader, but there's another guy I'm helping through a PM session that tried that and had no success. The strange thing about him (the guy I'm currently helping in a PM), he is stock, and had never been rooted. This also happened to him out of the blue. His phone bootloops, but on the boot animation, not the splash screen. RUU isn't working, neither is PC36IMG. Clear storage didn't work for him. He's tried numerous PC36IMG's, RUU's. No success yet. And since he's S on, not rooted, and never had been rooted, there's no attempting to flash a ROM in recovery. He's on the most updated 2.10 bootloader. What fastboot options does he have?

Here's his thread (Soulassassin, at POST#14): http://xdaforums.com/showthread.php?p=12484860#post12484860
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
I understand that. The point of my post was that I was lucky enough that flashing recovery in hboot actually worked for me, the first time. The 2nd, I had to run RUU to get it back, again, lucky for me it worked.

For some reason, it seems like the problem is spreading, almost like a virus.

The othger thing I should say is that before I dide anything, I puleld my sdcard, popped it into my old moment, mounted it to the computer, copied everything to my computer, then reformatted it in the Moment, added the pc36img's I needed and put it back before I did anything else.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
More partial progress. I was able to access the device in fast boot, and first thing was to erase every partition but misc and wimax. After that I used fastboot to flash Amon Ra.

Now here's the semi-progress. If I boot it normally it doesn't loop anymore, but instead goes straight to fastboot (NOT the bootloader). If I choose recovery in the bootloader then I just hang on the White HTC screen but don't loop, I have to pull the battery. Next steps?
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I'm not sure of the next step> I was hoping that would get you to recovery. Everything appeared to flash okay though, without any errors? When you say you erased 'every partition but misc and wimax', does that mean that you erased your boot partition too? If so, that's probably why it's just jumping back to fastboot when you try to boot it up. Maybe try lowetax's steps a second time, try erasing and flashing the recovery again? If that still doesn't work, then maybe use fastboot to erase everything again, and then try to use fastboot to flash an RUU, perhaps?
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
So I actually realized I had flashed the wrong recovery and that's what caused the hang. When I went back to a working recovery I got the same white screen reboot, but this time once it reboot it went back to fastboot and stayed.

What it tells me is that when I'm flashing a new recovery it's actually recognizing it as OK(otherwise it would freeze) but then it reboots for some reason. Same goes for the system files, which is why erasing them gets me straight to fastboot instead of loading to the point of loop.

In short, my phone is passing some "checks" to get the point where it resets. What it means, I have no idea.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
What do you mean by "flashed the wrong recovery", and also "when I went back to a working recovery..." You got a working recovery?? Or am I misunderstanding you? Slightly confused here.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
It was a version of Amon Ra I'd used to root a HTC Hero. When I went and got a version from an EVO thread, it went back to rebooting.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Oh I gotchya. So your basically in the same situation then? Maybe wipe with fastboot again then try RUU once more. Maybe also try to flash a different version of Ar, or try to flash clockwork?
[EVO 4G Q&A, Help & Troubleshooting] remman:
I had the same exact problem. Unfortunately I have nothing to contribute other than to say I was using CM7 nightlies. I was on a 003 hw rooted via toast's method. Sounds like I was lucky to get S-on and took my phone for an exchange.

One variable I do not see mentioned is overclocking. I was overclocked when it happened, using the smartass governor in savage-zen kernel. I know for a regular pc when oc is too high you can corrupt system data...does the same apply here?
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
Honestly I think I've tried everything at this point. I give up. There are only so many things you can do from fastboot and I've done them all. Not sure what to do with the phone but I don't have time to waste on this at the moment.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Pretty much take it in and get it replaced.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
And now either my phone is dead or my battery is dead. Got a flashing orange light, then it kept turning off, then it wouldn't turn on, and now I don't get a light when I plug it in. I read that sometimes it takes time to start charging if it's totally dead so who knows...
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Unfortunately, I agree with you. There's nothing more that I know of for you try. You've exhausted everything man. I'd take it Sprint the way it is, and see if you get lucky. Maybe anonymously call a couple Sprint store's in your area, and ask if they care about phones being rooted. Some do. Some don't.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Yea, you're battery's most likely dead. Maybe you got lucky and it is totally dead though. If they can't turn it on, they can't see if it's s on or s off anyways. But it's probably a dead battery, and they'd put a fresh one in anyways if you brought it in, most lkely. It's time for you to go to Sprint dude.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
Well, thanks anyways for your help guys, I really appreciate it. I was hoping we could come up with something if not for me then for those that will follow. Oh well, hazards of the pastime I guess.

Thanks Again
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
No problem man, though we were unsuccessful.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
You're welcome. It's too bad that no one here was able to come up with a solution, but unfortunately I don't think there is a solution. If there was, then surely one of the dozens of things you tried would've worked. It must be hardware related, in my opinion. I would have loved to find a solution, but for now it appears useless to try any further.
[EVO 4G Q&A, Help & Troubleshooting] Redneck Trash:
I'm just tossing this at the wall to see if it sticks. I really don't know much about adb but is it something that might work? Is it worth trying? Has anyone tried?
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
adb can't detect the phone until after the boot animation starts, or if the phone's in recovery. These guys had neither. Just stuck at splash screen, before the boot animation starts. So no adb. no recovery, no adb. Fastboot would recognize the phone from the bootloader, but nothing was able to be accomplished. This thread went 25 pages, which is nuts. I believe every single option, and even some pretty out of the norm and creative ideas were tried, and failed.
[EVO 4G Q&A, Help & Troubleshooting] Redneck Trash:
Thanks for the explanation.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
You're welcome man.
[EVO 4G Q&A, Help & Troubleshooting] Westibone:
I was not overclocked but was HW 003 using CM7 nightly.
[EVO 4G Q&A, Help & Troubleshooting] blazin-asian:
i just read through all 26 pages and no solution =(

i tried all the RUU and PC36IMG.zips in this thread, adb wont detect my device, and fastboot gives me the following error when trying to erase/flash recovery:

FAILED <remote: not allowed>

i also have S-OFF from unrevoked forever, HBOOT: 0.79, and a 001 release device.

the only difference is i was running the Destroyer ROM which is based off of CM7, no custom kernel, and no overclock either.

it killed my 8gb sd card and now im pretty much going to take it to the sprint store for replacement tomorrow. freakin awesome.

add one more to the list of victims. i shouldve just stayed on warm 2.2 =(
[EVO 4G Q&A, Help & Troubleshooting] scottspa74:
Scariest...thread.......EVER. My condolences to the victims, and to the medics.

I just read this entire thread, and didn't this happen to someone on Sense, AND someone totally stock (i.e. no root) ? And so its not CM7 related as some seem to suggest. Just wanted to mention that, as I've seen it suggested.

I'd be curious to know how things go at Sprint for those who have to take it in.

Sorry to all.
[EVO 4G Q&A, Help & Troubleshooting] snowboarda42:
I wonder if UnRooting back to stock, then reRooting with Toast's method would be a good idea at this point. Mostly as a "just in case" since you can get S-On once this has happened.
[EVO 4G Q&A, Help & Troubleshooting] Rem3Dy:
Did you even read any of the posts in this thread? Thanks for your 2 cents. L O L
[EVO 4G Q&A, Help & Troubleshooting] ageesm:
Your input is certainly appreciated, but the problem goes far deeper than this. If it was just this simple we wouldn't have a thread this long of back and forth with what to try next...:(.
[EVO 4G Q&A, Help & Troubleshooting] blazin-asian:
not that easy. i spent literally hours trying different RUUs and recoveries, but nothing will take. i rooted with unrevoked and unrevoked forever so my S is staying OFF no matter what i do. i am taking it to the sprint store tomorrow and hopefully get a replacement.

no offense, but i will be staying away from CM roms for a bit because i have had nothing but issues with CM6 and CM7.
[EVO 4G Q&A, Help & Troubleshooting] ageesm:
I know a seemingly common denominator here is CM, but there was at least one person who was on a Sense rom and another who I think was stock. I still am highly skeptical that CM is the *CAUSE*, it could certainly play a role in it, but it can't be the sole reason. The issue would be much much more prevalent than it currently is if CM was causing this much problem.

That said I left CM and still haven't gone back, I am sure I will at some point and can understand people being weary (as I am)...just my 2 cents.
[EVO 4G Q&A, Help & Troubleshooting] blazin-asian:
yep. i read through EVERY post in this thread and it looks like everyone is on CM7 with a 003/004 EVO. i was using "Destroyer" (how ironic) which is based off CM7 on a 001 EVO.
[EVO 4G Q&A, Help & Troubleshooting] NasTraDooMis:
LoL, it definatly "Destroyed" our evo's 4 sure ! Your description is to a T like mine. I was able to get back to normal after 3 straight days of work on it . Hit up "dougjamal", he helped me get mine working. It may or may not work for you. Perhaps i can PM you me and hims pms to try and help U out. Need his permission first B4 hand. lemme know what he says :)
[EVO 4G Q&A, Help & Troubleshooting] snowboarda42:
Woops, I meant as a preventative. My phone is fine, just wondering in case it dies if it would be better with toast method already done. Although I am on hardware 002, all these are 003, & 004 I see.

Sent from my hand with XDA Premium installed
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
I think he was talking about people without the problem, that rooted with UnrEVOked, since that seems to be a common denominator, as a preventive measure.
[EVO 4G Q&A, Help & Troubleshooting] Greenfieldan:
Can someone give a link to Toast's most recent root method?
[EVO 4G Q&A, Help & Troubleshooting] snowboarda42:
Will recovery still work if you have s-on? I'm thinking about flashing the unrevoked-forever-son.zip but leaving it rooted with cm7, just as a preventative measure in case I get the bootloop o' death.

Sent from my hand with XDA Premium installed
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
Unrevoked forever is one of the common denominators with this problem, it seems, in most cases.

Not to say it's the casue, but it can't be ruled out
[EVO 4G Q&A, Help & Troubleshooting] 100proof:
Just an update on my situation. It never got fixed (obviously), but the Sprint store was clueless to the problem an done employee even took it around showing all of the others. It still listed s-off , even though I'm positive that the store I went to was clueless of what that meant, but they sent away for a new phone for me no questions asked.

p.s. I never used any of the unrevoked methods and ended up with the same problem if that helps anyone narrow anything down.
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
No, it happened to someone who used Toast's method for S-OFF, which allows you to get back to S-ON if you flash an RUU. I'm on an 0004, been through RC2, RC3, and now RC4. Everything's fine with me. I ran Unrevoked.
[EVO 4G Q&A, Help & Troubleshooting] blazin-asian:
i went to the sprint store today and the technician didnt even check the bootloader. in fact, 2 employees claimed similar problems then said mine was worse haha. they are currently backordered up to a week so im using a Sanyo SCP-3810 as a replacement

what a piece of crap....
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Thats good to hear. I hope the other guys in your situation encounter similar situations
[EVO 4G Q&A, Help & Troubleshooting] marcusva79:
So what does everyone say? AOSP roms safe? Wouldnt mind giving RC4 a Go.
[EVO 4G Q&A, Help & Troubleshooting] jander6442:
I was using warms 2p2 when my problem occured... I was also using the accelerated kernel for the full hdmi app. One sprint sales man stated that there

was a hardware component that had a solid state countdown on flashes. I called BS, but this guy sounded pretty knowledgable. He insisted that the device was only able to do a certain predetermined flashing limit then loop

in order to protect the unit from damage. If this is true I can't say I flashed any thing more than 50x's. Don't know I still call BS.
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
I can't buy into that limited number of flashes thing.

Wanna take a guess at how many times a DEV building a new ROM has flashed his phone?

A HELL of a lot more times than the end user has....
[EVO 4G Q&A, Help & Troubleshooting] dougjamal:
+1......Heck, I, too, have wiped and flashed my EVO more times than that. The thing that cannot be explained is this. The overall number of people who have experienced the bootlooping issues while using CM7 is minute in comparison to the total number of CM7 users and that is comforting, to say the least. Furthermore, some of those people are not known to be flashaholics like many of us are so does that mean that their flashable limit is less than ours? Sorry, but I'm not convinced.

Posting & replying via the XDA Premium app
[EVO 4G Q&A, Help & Troubleshooting] jayharper08:
I'm with dougjamal on this one. I have flashed atleast 100+ times various things. I stayed on CM for about a week and honestly missed the sense so I went back.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
I can also confirm that there's no "flashing limit." Though its happened to a few people, it can be considered isolated compared to the number of CM7 users.
[EVO 4G Q&A, Help & Troubleshooting] marcusva79:
I agree with all of you peeps in here. I would consider myself a flasholic! I flash something different every other day. I have tried CM, Mik, Myn, Koni and currently on DECK RC7. Still I see others excited commits trying different roms and I get the urge to try something new. IF this flash limit was true devs and pretty much everyone in here would screwed brewed and tattooed.
[EVO 4G Q&A, Help & Troubleshooting] ageesm:
You kind of have to decide for yourself...I personally think it is just some coincidental hardware failure. Plenty of roms, both Sense and AOSP, that are really phenomenal.

Well any flash memory has limited number of writes before it 'dies' to say they added an arbitrary limit is ludicrous to me (so I am with you). What is the real point? If flash memory has a limited number anyway, what does setting your own to prevent damage actually prevent?

Typically this number of writes is far longer than how long we would own the device though, also not a set number, just an estimate that would vary for each component...
[EVO 4G Q&A, Help & Troubleshooting] lowetax:
had you used CM prior to myn's ?

restore anything that had been backed up while on CM ?

just curious

so many of us have flashed our buttskys off

that doesn't seem right
[EVO 4G Q&A, Help & Troubleshooting] sunny_syed:
ok so i had this problem and i was on stock rom with the root method forever on my phone kept saying S-off no matter what i did so i was like screw it i took it to the sprint store guy had no idea what was going on and said he would replace the phone for 35 bucks so now i have a brand new evo =]
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
I don't think it's a hardware problem as the issue lies in the the boot up process, at a point when the OS is supposed to start loading.

I HAD begun to think it was Unrevoked Forever that may play a part in it, but I seen one case where the guy used Toast's method.

(So glad I used Unrevoked 3, btw, just in case)
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I personally do think it's a hardware issue. If it was software related, then the RUU should've cleared it up, since it replaces all of the software on the phone, and starts it fresh (in theory). I don't see what else it could be, other than hardware. I honestly would've thought that an RUU would fix it if it was a software problem.
[EVO 4G Q&A, Help & Troubleshooting] jander6442:
Yes I had numerous times... using clockwork mod been reading that it has been problematic in some of the cache wipes. Still as I said in earlier post all I was doing was changing notification

ringtones in sounds settings and screen went loopy and never went back. Only problem I ever have had in my short flashing career. I still have that unit.
[EVO 4G Q&A, Help & Troubleshooting] CrazedBoricua:
I too had this same problem but I was running cm6 wimax alpha 2... I flashed stock ruin and got s-on but still looping. I returned it to sprint got a brand new phone
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
You know, after I posted that I got to thnking that it may not be either. Now, I'm not so schooled on the really technical stuff, but you could be right.

I also thought it could be a partition issue in the internal memory, but 1), how would that change just by using the phone, becasue none of thses happened after a fresh flash, I don't think. It all seems to be during normal use, or a random reboot, or even a user rebooting his device.

Although, like on the Moment, if you say, over wrote the partition where the boot image is by uploading an image larger than 128k, you would brick your phone and the sysmptoms would be the same; bootlooping on the spalsh screen, no recovery access. (Actually, that was the work around to get a new device from Sprint that you couldn't reflash to stock: Upload an oversized boot image, bricking it, then go to Sprint with the bricked phone)

I haven't seen any cases where anyone was doing that type of thing though, when it happened.
[EVO 4G Q&A, Help & Troubleshooting] RileyGrant:
Well in that case can anyone make a pc36img of calkulins format all?
[EVO 4G Q&A, Help & Troubleshooting] awesomeindeed:
Did they give you a new one on the spot? My local stores won't give me one from their own stock, and they're all currently on backorder for replacements. So for the past few days and until they come in, I'm stuck without a phone and they won't issue me a loaner. Pretty crappy.
[EVO 4G Q&A, Help & Troubleshooting] tizzleh:
You try doing through ADB?
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
ADB won't work. You have to be past the boot image to get to adb.

People have tried.
[EVO 4G Q&A, Help & Troubleshooting] jeffm922:
after reading all 30 pages, i have a few comments, and a few questions. first question, how do i check my hardware version from an AOSP rom? currenty running destroyer rom. and also how to check hboot version.

All in all, I agree with this bieng a hardware issue, especially since i read a few posts about people having the same issue on sense roms, as well as stock(never rooted) i don't blame unrevoked forever, or any cm6 or cm7 builds, most likely just because they are common roms lots of people run them, I am wondering how often this actually happens, if htc had a bad batch of evo's, im guessing multiple people have had the same issue, we just aren't hearing about it because a lot of those people have probably never even heard or tried rooting there phones, so i'm guessing plenty of stock evo's have had this problem, and the owners just took it to sprint, without posting here.

ill try to keep it short, pretty unfortunate that this has happened! i appoogize to all that its happened Sorry for the long post!