yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] facemymusic:
I've been having a couple of random reboots since flashing CM7. At first it started happening every time I played Words With Friends, so then I just uninstalled it. But now it's happening at least once every 2-3 days, always randomly. And it always freezes for a good minute or so before rebooting. I haven't gotten stuck yet, but I'm scared... I'm not experienced enough to get myself out if it gets stuck. :/

CM7 RC2, 0003, clockwork

Is this just an evo problem?
[EVO 4G Q&A, Help & Troubleshooting] jayharper08:
Settings>about phone>hardware information :)

Sent from "The EVO" using XDA Premium
[EVO 4G Q&A, Help & Troubleshooting] Greenfieldan:
Thanks...All this time and I've never known how to officially check that. :)

Edit: I don't have that in settings>about phone :\
[EVO 4G Q&A, Help & Troubleshooting] facemymusic:
Yeah I don't either, weird. I just remember from way back when I first got my Evo in the summer.
[EVO 4G Q&A, Help & Troubleshooting] matt2053:
Its only there on sense. Its also on the boot menu.
[EVO 4G Q&A, Help & Troubleshooting] RileyGrant:
This seems to be the case for a large amount of AOSP roms? Which begs the question, what kernel were you all running when this happened? Stock, savaged zen or what?
[EVO 4G Q&A, Help & Troubleshooting] jayharper08:
Wow this is an interesting and scary thread.

Sent from "The EVO" using XDA Premium
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
:mad:

Interesting. How do I review the log from the format.all script. I would like to see the results of that. I'm gonna see if I can research that right now. This thread still has me perplexed, really it does.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
There must be a way to check with ADB, if you're on an AOSP rom. I'm just not sure. I know that entering "adb shell getprop ro.build.description" will get you your current ROM build, but I'm not sure how to check the Hardware version, or if you even can.
[EVO 4G Q&A, Help & Troubleshooting] facemymusic:
I have whichever kernel comes w/ CM7 (I guess that would be stock?); I've never flashed a custom kernel.

But I don't know what AOSP means either lol

Edit: I just had a reboot again while in the middle of a phone call, while another call coming in on the other line. Both my mother & boyfriend will not be happy about this lol

Edit 2: make that twice, this time while trying to answer the incoming call. :(
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
AOSP = Android Open Source Project, which basically means it doesn't have a third-party, proprietary skin over it (Sense in this case, or for example Touchwiz or Motoblur). This also means that system apps are the stock ones (ie not the HTC Browser or HTC Dialer, etc). It means plain, vanilla Android.
[EVO 4G Q&A, Help & Troubleshooting] cctaylor410:
CM is not dangerous. There is a very large user base and because of this more problems are brought to light that may otherwise be dismissed . They could possibly be coincidental hardware failures. Hopefully you figure it out good luck.
[EVO 4G Q&A, Help & Troubleshooting] jander6442:
I was running w2p2 using the latest kernal that abregans put out for the hdmi pootang whatever he called it IIRC.:cool:
[EVO 4G Q&A, Help & Troubleshooting] :
Reading through these posts, very glad I went back to a Sense Rom. GPS was pretty awful on CM7 RC2, so I had to switch back. Good thing it decided to fail when I was close to my destination. Was able to use GPS to get to it before Maps app froze again.

It's a shame, since I was really enjoying ASOP roms. After about a week of using CM7, I realized that stock was totally the way to go. It's so much more responsive and incredibly fast. I'm hopeful that CM7 RC3 will iron out all these issues. For now, I'm back to Myn's amazing rom. I'd go to CM6.1, but since 4G is starting to become more available in my area, I'll stick with Sense for a while.
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
Exact same experience here.
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
Don't mean to double post, but to the OP, did you install an app called Applanet before this happened? I'm hearing that's what happened for a lot of the people who this happened to.

http://www.applanet.net/
[EVO 4G Q&A, Help & Troubleshooting] dougjamal:
I'm sure in and of itself, CM isn't dangerous, however, we cannot ignore what these users are experiencing especially when many of them are experienced CM users. Could it be coincidental hardware failure? Sure. Is it likely? I doubt it, but that's just my personal opinion and until the problem is solved, hesitation and doubt will remain over CM, especially from new users.

Posting & replying via the XDA Premium app
[EVO 4G Q&A, Help & Troubleshooting] Ep3n3wp:
Natradoomis

Product F(red)

I think it might be that applanet...

This was from a couple pages back and was over looked...

Hope that helps
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Interesting, I remember some of the people saying that they used that. I wonder what kind of virus it would take to do something like this anyways though. Is it even possible to have a virus of sorts, on an android platform, cause that kind of damage?
[EVO 4G Q&A, Help & Troubleshooting] Redneck Trash:
Haven't there been some issues lately with Clockwork Recovery? Think it had to do with not correctly wiping the cache. Could that or something else with Clockwork be an underlying issue?
[EVO 4G Q&A, Help & Troubleshooting] RileyGrant:
No, its happened on amon and and clockwork, personally I think its a bug in aosp gb thats causing the recovery to destroy itself and take the nand with it.
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
Nope, and even if it was, it wouldn't permanently damage the phone like this.

Sent from my PC36100
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I was also entertaining the idea that it could be a Gingerbread issue. Maybe Gingerbread eats Evo's.
[EVO 4G Q&A, Help & Troubleshooting] ModXMV:
Some thoughts that come to mind after reading the 12 pages of this thread:

A) The app planet and/or virus ideas seem promising.

B) Could this be a bad batch of NAND memory?

C) Could this be a bad batch of RAM?

I have had hard drives fail literally within 5 minutes of each other and their serial #s were 1 off from each other.

What's interesting is that this doesn't seem specific to CM7 as people with Sense ROMs are having this issue.

One question that doesn't seem to be being answered is if this is occurring on any other phones.

Very interesting thread though. Also scary.
[EVO 4G Q&A, Help & Troubleshooting] ModXMV:
Also did you guys run the Format All ZIP before flashing or did you just do a wipe from recovery?
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
It's either A or B. I think it's more B. I think HTC knew they had bad hardware and that's why they switched to larger NAND chips on their newer revisions (late 0003s and 0004s). Also the people on Sense that this has happened to were previously on CM7. I have an 0004 and I was running CM7 until yesterday when I went back to Myn's as a precaution. I hadn't had any reboots or anything before.

Sent from my PC36100
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
Larger chips? Please explain?
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/50253-psa-rooting-help-info-asking-help-updated-1-24-11-a-13.html

There's a command to tell you in terminal emulator which size you have if you're not sure. Ill look around for it.

Sent from my PC36100
[EVO 4G Q&A, Help & Troubleshooting] Westibone:
No, I had never installed Applanet at any time.

Also, in response to someone's previous comment, one of the first things I tried was re-flashing the Amon Ra Recovery by putting the PC36IMG on the root of my SD card and letting the phone detect in in the bootloader.

From what I understand, I was fortunate in having rooted long ago last August (using Toast's method), meaning that I was still using the .76 engineering hboot version. This allowed me to get S-ON back by flashing the latest sprint RUU in PC36IMG format. Thus I was able to take the phone in and get a replacement with no questions asked. I have never used unrevoked forever.

Also, I did want to say that the possibility of bricking your phone is a risk that you accept the moment you decide to root it. I would never blame the Cyanogen team for any of this. They do an amazing job, especially considering that they are doing all of this just for fun and with a small team.

I am looking forward to going back to CM7 once it reaches a final release, as it was by far the best experience I've had on my Evo to date.
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
Fred, I think you're referring to the erase blocksize. I wouldn't call it a larger chip in that sense. It's likely cheaper to manufacture, but results in more overhead during writing, since instead of 20000 (hex) bytes needing to be erased, now it's 40000 (hex). 128Kbytes vs 256Kbytes.
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
Sorry, I guess I typed it wrong. You're right. But there's also the susceptibility of the chips themselves. It's like the difference between cheap RAM and expensive, but "sturdy" RAM in a PC. Why else would they suddenly change chips?
[EVO 4G Q&A, Help & Troubleshooting] chefdave12118:
This thread is scaring the **** out of me! Cyans tweets aren't comforting either! Please don't hit my thanks button.... I dont want my 003 cm7 xda app thinking too much. :)
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I knew you hadn't used Unrevoked Forever! Otherwise you would've been stuck S-off! I'm on the .93 bootloader, which I believe is still downgradeable. Maybe Ill roll back to the Eng .76 bootloader, just in case I can't get to recovery some day. Maybe an RUU would get me to S-on, in an emergency situation. That's a good idea...

And I agree with you about Cyan team not being responsible. It is clearly posted in every single ROM thread, that you the user, are the only one responsible for anything that happens to your phone. Everyone knows (should know) the risks involved, and that sometimes things are completely unpredictable. I would still love to know what bug/glitch/problem is causing this issue, however.
[EVO 4G Q&A, Help & Troubleshooting] mmegalodon:
Kidding me? Feel like a total bad ass living on the edge. :coolbluefacewithsunglasses

sent from my
[EVO 4G Q&A, Help & Troubleshooting] thanamesjames:
I never installed applanet.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
Never installed Applanet either, don't even know what it is. I was messing around again last night and ran the oldest RUU.exe I could find, and it appears to have gotten me to hboot .93. Is it possible to go back further from here to .76 and then get S-On back?
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I'm not sure if that'd be possible. It might work. The .76Eng bootloader is always S off.(wouldn't require the S on tool to get s on I don't think, just need to flash a different bootloader*i think*) That's how it's built, S off. So, if you were able to get to the .76Eng bootloader, that's permanently S off, and then successfully run an RUU, where it would then flash the bootloader that comes with the RUU, which will be S on, it may just work. It's just a matter of if you can successfully flash the eng .76 bootloader, and then successfully run an RUU. Give it a shot. Here's a link to where to download the Eng bootloader. Good luck, let us know!

http://xdaforums.com/showthread.php?t=715485

Edit, and I'm pretty sure that .93 is downgradeable. The only ones that arent is 2.02 and 2.10
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
What's bizarre then is that I was on hboot 2.02, ran the newest RUU which took me up to 2.10, then ran the oldest one on www.shippedroms.com and I'm showing .93. Is this even possible?

Edit: The one weird thing I did is run the img file from the old 2.10 downgrade thread (I'll post a link when I find it) It was supposed to be a binary of .76 labeled as 2.10 or something. It didn't work when I ran it, but maybe that's why I was able to get to .93?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
I tried it with someone else, but let me know how it goes, and yes, the .93 is downgradable. :eek:
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
That is strange. I didn't think it was possible to downgrade the 2.02 or 2.10 bootloader, but If you did that odd stuff trying to downgrade boottloaders, then who knows what could've happened. I've skimmed through that thread a couple times a while back. I stayed away, lol. But I've never upgraded my bootloader, I've been on .93 since I bought the phone. I could've sworn at one point it was .97, but I never changed it, so I must be going crazy.

No success when you tried? What happened with it?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
That was the one isolated case where I got this nasty situation fixed, so I hope it works for this guy.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
Gives me hope, I'll try it tonight.
[EVO 4G Q&A, Help & Troubleshooting] marcusva79:
From what i was reading in this thread and the one in android forums, this is pretty tricky. I also got that from what I was reading is that everyone had been using unrevoked to root their evo. I hope this is not causing the rebooting issue. I was using CM7 yesterday and switched once Fred had mentioned this thread.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Well i do hope it does work. :)
[EVO 4G Q&A, Help & Troubleshooting] boobaroo:
It says to flash this .76 eng bootloader. How do you flash it if you cant get into recovery. That seems to be the major problem with this, you cant get inot recovery or even start your phone.

I have not installed applenet or anything different when flashing new Roms, all I ever do is restore the Apps I have, either via MyBackUo pro or Titanium. and I have been flashing and trying new ones since I purchased my EVO 7 months ago and not had one problem until this happened.

I have tried everything in this thread and other threads, but have not found an answer yet. I reported my Evo lost and am awaiting a new replacement, so I will keep this EVO to tinker with and hope find a solution to help others.

I'm not sure if that'd be possible. It might work. The .76Eng bootloader is always S off.(wouldn't require the S on tool to get s on I don't think, just need to flash a different bootloader*i think*) That's how it's built, S off. So, if you were able to get to the .76Eng bootloader, that's permanently S off, and then successfully run an RUU, where it would then flash the bootloader that comes with the RUU, which will be S on, it may just work. It's just a matter of if you can successfully flash the eng .76 bootloader, and then successfully run an RUU. Give it a shot. Here's a link to where to download the Eng bootloader. Good luck, let us know!
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
If you look inside the HBoot_0.76.2000.zip file, there's another hboot.zip inside. I believe you can rename that to PC36IMG.zip and flash that from the bootloader.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
I think I have a pcimg36 version of the Eng bootloader, that's what I'm gonna try.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
That would definitely be the only way this could work. Hopefully it works for you.
[EVO 4G Q&A, Help & Troubleshooting] boobaroo:
Nope, no luck with that.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Ah, good to know. Is there anything else that needs to be done, other than just renaming it? I thought teh roxx was telling me last week, that there needed to be a specific file within a PC36IMG for it to flash.

EDIT: just checked, it was the android-info.txt he was saying had to be included within the PC36IMG, which it already is. I downloaded the Hboot_0.76.2000.zip and opened it up, then opened up the hboot.zip, and within that was the android-info.txt. So it looks like just renaming it should work, in theory.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
what happened when you tried it? And what steps did you take?
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
I think there's a step being missed.

When I downgraded my 2.10 hboot, i followed the instructions in this thread http://xdaforums.com/showthread.php?t=883548

I think the way it works is, a newer hboot won't let you downgrade directly. But will let you flash what it believes tobe the same version.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
The problem with that tutorial for us is that Step 2 is impossible since we can't get into recovery, but doing step one and then running an old RUU.exe seems to have done something.
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
Agreed, BUT, the file being flashed thru the boot loader is hboot .76, which should support the engineering commands. Only difference is some text has been modified to make it appear as 2.10. From a functional stand point it should work as .76 does.

Below is a comparison of the two. Note the difference is only in the text labels.

-=}fc a\hboot_0.76.2000.img hboot_2.10.0001.img
Comparing files A\hboot_0.76.2000.img and HBOOT_2.10.0001.IMG
***** A\hboot_0.76.2000.img

Ω0.76.2000

***** HBOOT_2.10.0001.IMG

Ω2.10.0001

*****
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
So just to get this straight. The first file that I was able to run actually did downgrade my hboot. Since I didn't run the next file (the normal .76 hboot), my phone sat with the "hacked" hboot file until I ran an official RUU, which then "upgraded" my to .93. In theory, I should still be able to now flash the normal .76 hboot provided I can get a working .img file. Correct?

Edit: And furthermore, once I'm on the .76 Eng boot, I should be able to run the current 3.70 RUU.exe and get back to S-On?
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
This PC36IMG I've attatched is the .76 Eng hboot. I downloaded Hboot_0.76.2000.zip, opened it, copied out the hboot.zip that was within, renamed it to PC36IMG, and here it is. Since Brash has hboot.93 right now, he should be able to try flashing this in the bootloader, right? If that succeeds, then he could try his RUU and maybe get lucky, to get s back on? Yay? Nay?
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
That's the theory man, put it to the test. See what happens. You have nothing to lose at this point, maybe it'll even make a complete brick for ya, haha.
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
Yes

In theory, yes. I think part of it has to do with modifying the android-info.txt file so that flashing from the bootloader works. But more importantly, i'm not sure if the existing boot loader will permit a downgrade.
[EVO 4G Q&A, Help & Troubleshooting] boobaroo:
Tried this and the one I renamed myself and it keeps saying no image seen when I try to reboot into bootloader.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
Win-Win. Which means it will do neither:mad:
[EVO 4G Q&A, Help & Troubleshooting] Product F(RED):
If you have a late 0003 or an 0004 with a 40000 byte erase size, it's dangerous to downgrade to 0.76 because that bootloader can't handle the new partition sizes that don't exist on the older hardware revisions.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Hmm. Was it named exactly PC36IMG? all caps? Main directory of your sd card? You didn't add a .zip to it, did ya? Windows hides the file extension, so if you added a .zip, it'd be PC36IMG.zip.zip. Be sure of all that stuff, then maybe try again? If not, maybe gpz is right, and you need to edit the android-info.txt, which i'd have no clue how to do.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
? I don't follow.
[EVO 4G Q&A, Help & Troubleshooting] boobaroo:
Yep, checked all that and tried different ones and it just wont take any.
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
@BrashL,

Have you tried to flash a recovery through the bootloader (PC36IMG.zip) ?
[EVO 4G Q&A, Help & Troubleshooting] boobaroo:
I have tried this with many different recoveries and RUU's and have yet to find a soultion.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
At this point, I think the solution is one of the following: 1) Use your Asurion Insurance if you have it, and pony up the 100 bucks for the deductible(since you're s off still) 2) Take a gamble, and take it to sprint with S-off, and see if you get lucky or not (never know, but that's a risk of red flagging your account) 3) Find a way to intentionally and permanently brick it, so the device will not even power on. Then take it to sprint, and since it won't power up, they won't know it's S off. That's probably what I'd try. Chop up a USB cable, get access to a couple of the wires in there, and connect them to a 9v battery. (if you try this, please remove your battery from your Evo, to reduce the risk of danger). I've never done anything lke taht, so have no clue what will actually happen, however I'm inclined to believe that 9v DC to the innards of an Evo will most lkely fry the thing....
[EVO 4G Q&A, Help & Troubleshooting] thomo5000:
Dude, that's plain unethical. You are NOT covered by warranty any more and you know it. Defrauding your carrier is only going to make them demand even harder to root phones from the manufacturers.

Look, it sucks and nobody is suggesting otherwise - but you knew the risk when you flashed the phone. Nobody held a gun to your head. Now you are talking about shafting this very community instead of taking responsibility for your actions.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Haha. I won't even respond any further than a chuckle. And watch your language on the forum.
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
OK, maybe some progress here...maybe. Flashed the .76 hboot k2 posted and it actually worked! I'm now sitting with a .76.2 hboot AND I'm no longer stuck in a reboot cycle because it boots directly into the bootloader. My plan is to try and run the official 3.70 RUU exe file now, but I'll wait for feedback in case anyone can think of anything else to run given this new development.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
If you wanted to, you could try running a PC36IMG of a recovery image, like AmonRa 2.3, and see if you can get recovery back. If so. Bad ass. If not, I'd run the ruu

Edit: now that I think about it, maybe just run the ruu and see if it gives you s on, or maybe it'll even work. I'm scared that flashing a recovery may send you to loop land again....I really don't know for sure...
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
Well, no love. Ruu ran fine, random reboots are still in effect, and still S-Off. Crazy. If I go back to .76 any ideas?
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Damn man, I was really hoping you'd report back with better news, at least S-on. Did you end up just running the RUU, or did you try flashing recovery first? I'm pretty much out of ideas at this point. I was really hoping that running the RUU while on the engineering bootloader would at least get you back to a bootloader with S-0n, so you could then take it in without worries. Other than trying run the RUU's, and repeating all your steps again, and hoping to get lucky with it, I'm honestly out of ideas on this one. You have tried everything that I know, and had no success. You're hardware must be toasted in one way or another. Unless you went back to the .76 engineering bootloader(so you can run fastboot commands) and maybe someone else with fastboot knowledge could suggest trying something from fastboot. Aside from running the RUU from fastboot commands, which you've already tried, I know no more about fastboot than that, unfortunately. You're situation has me thoroughly perplexed man.
[EVO 4G Q&A, Help & Troubleshooting] Rydah:
I didn't bother reading, but flash recovery via bootloader.
[EVO 4G Q&A, Help & Troubleshooting] ageesm:
Well then you should have :p. No worries, but the problem appears to go deeper than that and unfortunately it isn't as simple as it would seem...
[EVO 4G Q&A, Help & Troubleshooting] RileyGrant:
Anyone tried the "fastboot flash_image" command?..
[EVO 4G Q&A, Help & Troubleshooting] BrashL:
Instructions?
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
fastboot recovery [filename.ext of recovery image]