yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] tone3400:
ok so i had this same problem it kept sending me network msgs from sprint saying i was not registered or something of the sort. i actually got past everything by doing the root process over and over and reloading the rom i think it was cyanogen 6 i went for months no problem. Until tonight now the one thing i want to share with you guys. Well first iam a rookie but ....if you can get to you homepage and it stays on for a minutes even 30 seconds....go and turn off everything having to do with the network .......3g and all of that stuff

if you turn on airplane mode it will stay on and you can re add recovery and stuff that might have messed up i did it . Did the whole unrevoked thing again had a recovery up again. Added sprint lovers because i could not activate my phone with the ## number series they give you ......this second time around ...but if you can get your networks off and 3g gps as well maybe you guys can do something...or figure out how to stop this problem i just wanted to share sorry if i was all over the place with my info....also sorry if some one else mentioned this thanks
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Well, I would like to say I am still uncertain of this issue. I successfully flashed CM7 Nightly 37 on a brand new, out of the box evo, hw 0004, rooted with unrevoked just now.
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
I also have an 0004, nothing has happened to me yet. Been to CM7 and back. 0004s and late 0003s have double the erase block size (40000) so I guess maybe HTC caught on before we did and revised their hardware?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Well never had an issue on my stolen 0003, but a lot of people here had issues on 0003 as well, so I'm not sure.
[EVO 4G Q&A, Help & Troubleshooting] EndlessDissent:
Well, the good news for CM fans is, this problem is not confined to CM7. It may still be a Gingerbread issue, though. It has now happened to someone running Gingerbread MIUI.

The first(?) MIUI fatality: http://www.miui-dev.com/forums/show...d-GB-Fresh-Start&p=50855&viewfull=1#post50855
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Its the first I've heard of it. Though, at least we were right in that it wasn't CM7. So peeps, its safe to flash CM7.
[EVO 4G Q&A, Help & Troubleshooting] cordell12:
Not to cause any panic but MiUi is CM7 (in a nutshell) :)
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Basically, yes, but I still think its a hardware problem, because like I said, I followed the normal rules, rooted, ect, and no bootlooping to start or random reboots for me.
[EVO 4G Q&A, Help & Troubleshooting] EndlessDissent:
Well, yes, but other phones don't seem to have this problem, and the MIUI that's ported to Evo is from the Nexus 1, and like I said, other phones, including the N1, don't have the death loop problem, which means that, while it CAN be CM7-related, if it were, the problem would be spread across multiple phones, not isolated to the Evo.
[EVO 4G Q&A, Help & Troubleshooting] 22350:
I wonder if there is a way to isolate the manufacture dates of the devices that are failing?

We might discover that all the devices were built within a week of each other.

P
[EVO 4G Q&A, Help & Troubleshooting] nc_carol:
My co-worker was thrilled to get his new EVO after seeing mine for so long now. He asked about rooting it, but I told him wait a month or two, get to know your phone (coming from a crackberry) and learn more about it, then we'll talk about it. Last week when I get to work he hands me his phone and begs me to fix it. He's never had anything but stock sense, never downloaded anything off market. Phone was completely done! The first time I turned it on, it tried to boot up, but just cut off within 30 seconds. After that, wouldn't even turn on, even plugged in. Tried my battery- same. Completely bricked, no explanation. HW 004. Got a new phone from Sprint without issue. Of course, they had no idea why it happened. I imagine this kind of thing happens on sense just like any ROM, just with stock sense, the owners probably aren't on xda posting about it too much.
[EVO 4G Q&A, Help & Troubleshooting] chinoapple:
What rom was it? And at what point did you pulled the battery during the radio update?

Thanks
[EVO 4G Q&A, Help & Troubleshooting] sile2001:
Got another dead Evo to add to the stack. :\ Mine was a 002 revision, with the Toast root method and the 0.76ENG bootloader and Amon-Ra recovery.

It had been running fine on various ROMs until I flashed Warm 2P2. At that point, I started getting the occasional loss of data (such as contact list), and occasional sudden reboots that would go into a loop until I pulled the battery. To get it to boot again, I would have to go to recovery and wipe cache and dalvik-cache.

Then last week, I flashed the stable release of CM7. It was running fine for a few days, but then I started getting random FCs in previously-stable apps and random reboots (occasionally looping, would boot after pulling battery). Today, it suddenly rebooted while it was completely idle, and went to the perma-boot-loop state others have noted in the thread (recovery boot-loops too).

I tried re-flashing Amon-Ra and also tried CWM, but to no avail. I don't know if others experienced this, but I couldn't get the RUU flash app to even recognize the phone. I would have liked to have had the time to dig deeper, but my phone is critical for work, so I found a 3.30.651.2 PC36IMG image, and flashed it with the bootloader to get back to S-ON (note that the boot-loop persisted after the flash). Sprint swapped it out and I've now got an 004 revision. I want to try CM7 again, but I'm a bit gun-shy now (even though I know it's not their fault).
[EVO 4G Q&A, Help & Troubleshooting] Greenfieldan:
So, a good friend of mines Motorola Devour has this same thing. Splash screen...reboot....splash screen....reboot. He has not rooted his phone, or even considered rooting his phone. Any thoughts?
[EVO 4G Q&A, Help & Troubleshooting] Vesperian:
I recently got a replacement phone after this very issue knocked out my CM7 set. I now have a gone from a hardware 003 to a 004 phone. I put Myn's Warm on since I'm gun-shy of Gingerbread until the problem is found.

Someone mentioned earlier in the post about the newer hardware versions having double the block size as the potential issue behind it all. Is that still a valid theory?
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
That was me, but what I originally thought was that the 0004's double block size was a saving grace.
[EVO 4G Q&A, Help & Troubleshooting] Vesperian:
Still, that would be some comfort to those of us who got 0004s when we returned our equipment. If only it were validated (not to disparage you, of course).

I've come to expect such great sleuthing from the devs here that I almost wish it were a bigger issue so it would garner more attention. Almost.
[EVO 4G Q&A, Help & Troubleshooting] Pivo187:
So what roms are safe? Is sprint lover roms safe?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
They roms are safe; some evos had a memory mishap apparently; you'll be fine on sprint lovers.
[EVO 4G Q&A, Help & Troubleshooting] Pivo187:
What about Destroyer V2 or the CM7 roms? BTW does sprint lovers allow tethering & is CPU OCed at all on SLovers Rom?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Both roms are fine to flash. Sprint lovers will let you tether, but you can flash a custom kernel that would allow you to overclock; personally don't know as I have never run that rom.
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
It's not specific to any ROM, although in the beginning, my self and some other suspected it was CM7 issue, so all ROMs are pretty much safe.

One thing I'm wondering, and I need to go back and read more, how many people that have had this problem use ROM Manager?
[EVO 4G Q&A, Help & Troubleshooting] Vesperian:
I used it when I installed CM7. Ironically, it was the first time I had used Rom Manager to install a ROM. I'm back with good 'ole Amon Ra now, and think that it just might be safe for me to try CM7 again. *fidgets nervously*
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
You'll be fine to re-install CM7.
[EVO 4G Q&A, Help & Troubleshooting] norkoastal:
Having similar issues as OP w/access to Recovery..

After flashing many, many nightlies... I drifted off into CM7 world.. Post RC1 flashing and quickly jumping back into the nightly bandwagon, I started to notice the phone would reboot itself at random times under load (usually browser or Pulse app). This initial boot loop triggers a second and third bootloop until I battery pull or it stops on its own..

Ive switched Recoveries and ROMs (Sense to AOSP), but cant seem to shake the occassional bootloop. HW003, PRL 01115, kernal 2.6.32.17 #15. On a side note I have a Nook color on the same nightlies W/o any bootloop issues.

On rooted stock at the moment, but fear there is something still within the memory that is tripping the phone to bootloop under load (browser clicks/app open). Ive cleared all memory (Philly finest wipe tool) and updated radio PRL to no avail..

Are you guys swapping phones in store (sprint insurance) or via mail through Assurion?

Thoughts?
[EVO 4G Q&A, Help & Troubleshooting] koechelr:
same boat

Middle of the day yesterday my phone went into this boot loop. I was running cm7 with savagedzen kernel

Here is the device info i can gather from fastboot commander:

STARTING PRINT OF DEVICE INFO.

-----------------------------------.

Radio version: 2.15.00.11.19.

SPL/hboot version: 2.10.0001.

product: supersonic.

mid: pc3610000.

security: off.

build-mode: ship.

I tried wiping recovery from fastboot commander unsuccessfully; same for flashing a new recovery from commander.

I can wipe cache and data succesfully....

looking hopeless at this point.

Just noticed the Sprint Online store is sold out of Evo's - maybe an indication of the issue spreading?
[EVO 4G Q&A, Help & Troubleshooting] cobirch2:
Correct me if im wrong, but wouldnt a dev be using an emulator to test not-yet-polished builds of their roms? I would assume only finished and proven roms would actually get flashed to the phone. That being said, im sure devs are flashing more than the average user, i just doubt that a dev is flashing every potential build to their phone.

As for the flashing limit, no i cant imagine that there is a pre determined number of times you can write to NAND. But it is called Read Only Memory for a reason. NAND is meant to be read from not written to. It can be written to obviously, but repeatedly writting to NAND memories can and will eventually damage your memory and cause bad blocks. If bad blocks build up to the point that your boot/recovery/system/data/cache partitions have less available memory than the files that need to fit on them your phone isnt going to boot, and your not going to be able to fix it no matter what you flash.

Its like certain parts of a car. The manufacturer might tell you that your head gasket will only last 200,000 miles. That doesnt mean that right when you hit 200,000 miles your head gasket is going to fail, but the closer you get to 200,000 the better the chances of it failing.

Just because there was no flash immediately before these phones failed does not mean its not a hardware issue, probably caused by bad blocks. Your phone is constantly reading from the system and data partitions millions of times a second, especially from the data partition. Every time data is written thousands of cells are charged and discharged, which is eventually going to cause a small portions of those cells to fail. Whose to say one unfortunate write to data didnt ruin one block too many and cause the whole phone to become unusable?
[EVO 4G Q&A, Help & Troubleshooting] goldenmonkey1:
This happened to my phone today. Was sitting at work, and all of a sudden out of nowhere it just starts boot looping. Wasn't doing anything to it, hard hardly used the phone all day and it just started. No way to seemingly fix it.

Was on CM7 final, stock ROM, upgraded radios but .93 HBoot, 0002 hardware (preordered it before launch). Not sure how I rooted it, it was so long ago...

Going to try flashing via a PC36IMG, and also flashing a RUU, and even maybe lowetax's method of deleting the recovery and re flashing it (http://xdaforums.com/showpost.php?p=12480454&postcount=179)... But it seems like the outlook is bleak.

If I can't get it to S-ON, is it even worth taking into a Sprint store? Isn't the likely outcome of that them seeing that it's been rooted and flagging my account?
[EVO 4G Q&A, Help & Troubleshooting] goldenmonkey1:
Damn... When flashing the RUU, it 'worked' (as far as the flash goes), but still bootloops.

Of course, this also (accidentally) upgrade me to hboot 2.10, so I can't even try to downgrade to .76 like I was planning to.

Not like it would have helped I guess.
[EVO 4G Q&A, Help & Troubleshooting] goldenmonkey1:
In trying to do this, fastboot devices brings up nothing. While fastboot erase recovery brings up a 'waiting for device' prompt which never moves.

Fastboot USB is highlighted, yes, and I am in the proper directory.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I could be wrong, but I don't think those fastboot commands will work unless you're on the ENG .76 bootloader. Since you're on the 2.10 bootloader, most likely the commands will be useless. Some people were able to eventually achieve S on by running the RUU a handful of times, but I believe those people were already on the .76 hboot.

As far as taking it in to a sprint store with it being S off, it's hit or miss. The possibilitly of your account being flagged does indeed exist. It depends on the tech that you deal with. Some of them might ignore that it's S off, and treat it as a normal situation. Others might tell you to bring it back once it's S on, then they'll deal with it. Others may just red flag your account and leave it at that. I've seen reports of all of the above. Do you happen to have insurance or anything of the such?
[EVO 4G Q&A, Help & Troubleshooting] goldenmonkey1:
Ah, you're right - those commands were for the guy who was on .76. Annoyed the RUU put 2.10 on, but it was a longshot anyway...

No insurance or anything, phone bought in June, so I'd assume I'm SOL in that regard. Unless I try the idea of flashing a different radio and battery pulling until it bricks further.

What does it mean to have a 'flagged' account anyway? Is there really any harm in it, other than them knowing I've rooted my phone? Talked to a friend who used to work for sprint, he suggested as long as it doesn't boot up to the CM7 screen, I'd probably be ok in store...
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
Flagged account means (and btw I don't work for Sprint) that either there's been fraudulent activity in the past, or in terms of the phone, which I think is what you're asking, it's been tampered/damaged beyond what would be acceptable under warranty. I'm assuming when you get a new phone, that flag goes away (for the tamper/damage, not fraud).
[EVO 4G Q&A, Help & Troubleshooting] norkoastal:
Is there a target Bootloader/Recovery we should be flashing to for stock trade-ins, or is any S-On bootloader screen acceptable? I'm in a weird state with my phone as I still have anon Recovery loaded but cant seem to flash any other bootloader versions (to match the stock RUU zip I want to install).

Am I safe to swap in this state?
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
As long as you're s on, it should not matter what version the hboot is. Although it'd seem more 'normal' if it was up to date. Also, i wouldnt want to take it in with a custom recovery. Are you able to flash an ruu?
[EVO 4G Q&A, Help & Troubleshooting] norkoastal:
I think that is my next step.. I might re-root then run a RUU so I wont run into any S-on issues blocking the update.
[EVO 4G Q&A, Help & Troubleshooting] goldenmonkey1:
After flashing this:

PC36IMG_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.71_003_release_147044-signed.zip

Instead of a boot loop, it goes to the white screen, then vibrates 5 times and stops... hm. Still no recovery access or anything like that though. edit: yup, does this on the most recent flash too... so, no longer a boot loop. Not sure how this affects if sprint will help me out in store.
[EVO 4G Q&A, Help & Troubleshooting] jeetjshah:
mine pooped out on Tuesday while trying to do a Titanium Backup. Sprint mailed me a new one today... wondering if i should go back to rooting/ROM loading. I liked CM7 but after this, I'm kinda scared.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Seems you had a bad luck of the draw, but you shouldn't let it deter you; now you're more prepared to handle issues.
[EVO 4G Q&A, Help & Troubleshooting] Vesperian:
What kind of phone did you get? My crapped out while running CM7 and I got a replacement with hardware 0004 from Asperion. I was hesitant at first, too, but I'm back on CM7 (7.0.2.1, actually, for the GPS fix) and I haven't even had one random reboot, much less a bootloop.
[EVO 4G Q&A, Help & Troubleshooting] jeetjshah:
being new, how would i check which hardware version I have? I just got my new evo in from Asperion and already rooted it, couldn't resist.

EDIT:

Its Hardware Version 0002.
[EVO 4G Q&A, Help & Troubleshooting] Vesperian:
Hmm. I'm not sure, then. There was speculation floating around that the increased block size in the phones with late hardware 003 or 004 provided a kind of safeguard from getting bricked (I have no idea what that means except it gives the phone more room to push data around inside itself). As I have yet to hear anyone give a definitive answer on what the core problem is, though, I can't say. The good news is that it still seems to be a minority of users.

I've always thought Myn's ROM was pretty sexy if you're still anxious about CM7.
[EVO 4G Q&A, Help & Troubleshooting] ment99:
No idea what hardware version I have (is there a way to tell in the battery compartment or from the bootloader?)

I used unRevoked Forever to root the phone, initially put DECKS Rom on the phone but wiped it and changed to the latest CM7 Stable.

Just like everyone else, I was not doing anything on the phone when it decided to restart itself and go into a boot loop. Thankfully I found this thread so I can stop wasting (more) time on trying to fix it.

I have insurance but I think I will just walk it into the store and tell them it isn't working. If all else fails, I will call the insurance company and get a replacement that way.

I initially went to the IRC channel and asked for help...someone joked that I should smash it on the ground and get a new phone...who knew he was right ;)
[EVO 4G Q&A, Help & Troubleshooting] ment99:
I was unable to get the phone to S-ON. Took it to the store and told them that it kept rebooting over and over. They looked at it and were unable to flash it so they ended up giving me a replacement phone. I don't know if they even looked at the bootloader, but whatever.

I would think that they get a low amount of rooted phones in the service center so they don't care and probably don't even look.

I now know my new phone is revision 0004 ;)
[EVO 4G Q&A, Help & Troubleshooting] LancerEVA06:
Yup... I've replicated this on another EVO that was an insurance refurb that was going back anyway. I found, in my testing, it's related to WiMAX and CM7. Everytime it would reboot, 4G was either on, or had been on since the previous boot. (Mind you, 4G without a Signal, or a very weak one) If I caught the boot loop in time, it would boot fine. But once I left it rebooting for 20 minutes... game over, infinite cycles.
[EVO 4G Q&A, Help & Troubleshooting] Rydah:
Not sure if has been mentioned, but download a recovery in pc36img.zip format, use a card reader or other device to transfer it to the root of your SD. Boot into bootloader and hit vol up, and it will flash recovery back on.
[EVO 4G Q&A, Help & Troubleshooting] LancerEVA06:
Yes, it will successfully flash, but will still continue to boot loop. I've tried deleting all partitions via fastboot and reloading all kinds of PC36IMG.zip files. I did get a difference when I loaded up the launch day zip. Instead of a boot loop it would show the splash screen, screen turn black, vibrate 5 times, and the green charged light would flash.
[EVO 4G Q&A, Help & Troubleshooting] BRUTAL BROCK:
hate to rebump this, got a new evo, but still have my old one that this happened to.

seems like this was never resolved? just effected a small minority of users.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
That about sums it up. Unfortunately, no fix was found for the few users that this problem affected. The best shot was to get s on and take it to sprint if you're still in warranty.
[EVO 4G Q&A, Help & Troubleshooting] ar4senal:
Hey guys-

This problem just recently happened to me...

I read through the whole post trying all the things that were reccomended with no luck at all.

I finally bit the bullet and took it into Sprint with "S OFF". The girl who was looking at my phone never even noticed. She was about to give me a brand new one, when she noticed the watermark on my battery was tripped! :eek: So i have to either get this one working (dont think its possible) or pay the $100 deducitble for a refurb. Although the tech who was in the back, did tell me that he has amassed quite a few odds and ends for evos and epics (screens speakers, etc.) and that if i ever needed anything to bring it to him directly for a fix.

Also in a seperate thread i started before being referred to this one a guy posted these steps up, saying it had worked for a friend. Anyone tried these?

http://www.mediafire.com/download.php?9zc41jsfs7sm1qf

Thanks!
[EVO 4G Q&A, Help & Troubleshooting] Scorpius268:
I had cm7 and also had the boot problem but this worked for me:

I took the battery off the phone for about 5-10 mins, then I re-boot into the recovery mode and it didn't re-boot or took me to the crazy boot loop, I had a copy of Mikfroyo 4.62 in my SD card so I decided to flash it and after that the phone started no problem, I might be one of the lucky ones but for now I'm staying away from CM7.

P.s As soon as I got my phone on Mikfroyo I had problems with force closing but that was because I didn't wipe any data at all, so I did the wipe and now my phone is back to awesome :)
[EVO 4G Q&A, Help & Troubleshooting] matt2053:
Sounds more like a recovery problem than anything. But I could be wrong, tis a mystery.

Personally CM has been as stable as stock for me.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I know it. It's so strange. I haven't used CM in a bit, but I have been using other Gingerbread Roms, such as Salvage, Evervolv, and I tried the new Savaged Zen last night. I have never had a hiccup of any sort with my phone (knocking on wood) on any rom I've ever used. I've had a couple random reboots in the past, but that was before I figured out that my phone absolutely hates BFS kernels with HAVs for some reason. Since I figured that out, my phone is always flawless (again, knocking on wood). I would really like to know what the heck is causing these random 'reboot bricks' out of the blue. There must be a common denominator.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
I completely agee with you...haven't had a reboot in I don't know HOW long [forbidding]. I want to place it in the hypothesized ball bark of a flashing issue/ download....
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I was thinking that too. The odd thing is, that it's happened to people using CWM and AR. I don't know what to think about it, really. I was thinking possibly the recovery partition got corrupt somehow, but some other guy was speculating that it was an issue with the Wimax partition. I'm not sure. That's above my knowledge, I'm speculating at this point.