yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] HipKat:
10??? Oooo-kay.

I'll tell ya what, after I eat, I'll scour the forums and see how many people I can find that have reported the problem on here.

BTW, out of the 250,000 CM users, how many even post here?

How many haven't posted here about the problem?
[EVO 4G General] mmegalodon:
Not trying to hit the panic button guys ... just the post panic thread button.

sent from my
[EVO 4G General] IMiLL102911:
You were the one that said you found 10 people with this problem.

We all take risks by rooting our phone and flashing roms no matter which rom it is.

Remember about a month or two ago people were screaming the sky is falling because myn's rom was supposedly bricking phones. Now it's cm. Next month it's going to be [insert rom here] and we're just going to repeat the cycle.
[EVO 4G General] trudat50:
It happened to me on CM7 RC2... got a new one from Sprint
[EVO 4G General] Circaflex:
if it is hardware related is there any sort of diagnostics program we can run to test memory blocks?
[EVO 4G General] k2buckley:
Ahh, thanks for clearing that up for me. I was unaware.

I agree that there's not a need for cm users to panic at all. There is no proof or evidence that cm has caused any of these people's issues. It just seems that they were all on cm, but that doesn't mean anything. I still would love to know what the actual failure in the phones are, and then what could be the cause for that type if failure.
[EVO 4G General] HipKat:
Where did I say I found 10 people?

I said I saw 6 threads Sunday and 4 yesterday.

And I'm not trying to start a panic, just make people aware that there seems to be a growing problem that they MAY want to do a little research on, before they caught by surprise, like a lot of others have.

I DID do a little surfing through the Q&A Forum, going back only as far as yesterday, and following a link to one thread on Android forums. I can search deeper, if you want, when I have more time.

buffnutz1 - http://xdaforums.com/showthread.php?t=1011991

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

Westibone - http://xdaforums.com/showpost.php?p=12412982&postcount=1

thanamesjames - http://xdaforums.com/showpost.php?p=12414044&postcount=5

Gandroid - http://xdaforums.com/showpost.php?p=12416981&postcount=9

boobaroo - http://xdaforums.com/showpost.php?p=12419651&postcount=17

k2buckley - http://xdaforums.com/showpost.php?p=12420268&postcount=22

scriptx - http://xdaforums.com/showpost.php?p=12433866&postcount=44

BRUTAL BROCK - http://xdaforums.com/showpost.php?p=12439395&postcount=73

BrashL - http://xdaforums.com/showpost.php?p=12443107&postcount=82

00mred00 - http://xdaforums.com/showpost.php?p=12443939&postcount=86

facemymusic - http://xdaforums.com/showpost.php?p=12447093&postcount=92

teh roxxorz - http://xdaforums.com/showpost.php?p=12495602&postcount=201

jander6442 - http://xdaforums.com/showpost.php?p=12495164&postcount=197

thebeast614 - http://xdaforums.com/showpost.php?p=12500547&postcount=223

losphn - http://xdaforums.com/showthread.php?t=1012907

jhonbra - http://xdaforums.com/showthread.php?t=1006215

soulassasin187 - http://xdaforums.com/showpost.php?p=12344359&postcount=14

itstheshoes220 - http://androidforums.com/evo-4g-all-things-root/275908-i-need-help-asap.html

Gandriod - http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html

bmwboy - http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html#post2208185

Does the rain have to actually be hitting the ground before you consider you may need an umbrella?
[EVO 4G General] DirtyShroomz:
No it just has to be raining in MY area before I use one :)
[EVO 4G General] SantinoInc:
For whatever it's worth I have been using CM since the 6.0 series and never had a problem that I didn't cause myself. I then went over to Shinzul's WiMAX CM and never had a problem. After that thread was closed down I made the transition to the CM7 Nightly builds and am yet to have a problem. That is a lot of flashing with a minimal amount of problems.

I am not a DEV and I don't claim to know all the ins and outs of the Android OS but if I had to put money on it I would say these BOOTLOOPS and BRICKS are probably due to user error. I hope I'm correct.
[EVO 4G General] k2buckley:
That's what one would think, but 99% of them reported that their phone had been running stable, and the looping started out of the blue, while the phone was sitting idle. It's odd, that's all. And I will also attest, again, that I never had any problems with CM during my experiences with it, other than whatever bugs were already noted.
[EVO 4G General] HipKat:
I'm not telling people not to use CM7.

It's your phones, do what you want.

I just know that I won't be going back to it until this is figured out.
[EVO 4G General] matt2053:
Its even happened on STOCK UNROOTED Evos.

This issue has NOTHING to do with CyanogenMod.
[EVO 4G General] driguez:
ID-10-T error
[EVO 4G General] atapia984:
Ingore post. Sorry.
[EVO 4G General] rockky:
OP...thanks better to at least be aware of this. I use Ultimate Droid Rom...a straight CM derivative and haven't had this issue...but do go back to CM at times and will stay on top of this now.
[EVO 4G General] remman:
This happened to me out of the blue about a month ago. I thought I was an isolated issue but with all of the recent topics, my interest has been piqued to say the least.
[EVO 4G General] aimbdd:
no.... dumb ass if you had read the posts earlier.
[EVO 4G General] HipKat:
Really?? How would stock unrooted have an issue getting into recovery?

And show me where it's happened, becasue I haven't seen it. Nor have I seen it on any Sense ROM.
[EVO 4G General] :
You must be a noob to blame it on CM rom.
[EVO 4G General] :
Stop trying to spread FUD. You posted all those links and yet you still opened this thread.

Nothing to see here, move along.
[EVO 4G General] cordell12:
Has anyone explored if the death bootloops could be SBC related? From my understanding the battery drops from 100% deliberately as the phone isnt built to handle peak charge (voltage) for a extended time period.

Just a thought...
[EVO 4G General] HipKat:
Yeah, I'm a real n00b :rolleyes:
[EVO 4G General] matt2053:
You do not have to be rooted to boot to recovery.

http://xdaforums.com/showthread.php?p=12484860#post12484860

Also at least one person i.know of was on Warm and had this issue.
[EVO 4G General] Lokifish Marz:
These reports of looping and bricking are both here and the CM forum. The source code has issues. As far as pushing CM7 goes, "but these go to eleven" isn't a valid argument.
[EVO 4G General] OneStepAhead:
if only 10 people have reported it, how could it be 99%? is one of them a 10th of a person?
[EVO 4G General] matt2053:
Could you clarify this statement please?
[EVO 4G General] ourprisonplanet:
Out of all the Evo's that I sell on a daily basis, I've had to make more insurance claims on them falling in toilets than bricking issues... Someone should look into the possiblity of toilet gnomes while they're at it... Maybe Steve Jobs is behind it...
[EVO 4G General] Lokifish Marz:
CM7 Fixes, Tweaks, and Work-Arounds!. These issues are also to be found in the CM forums. Androidx86 is having many of the same issues as well. Reported Gingerbread issues.
[EVO 4G General] HipKat:
You ever wonder how many of those were bricks before they "fell" into the toilet?
[EVO 4G General] ourprisonplanet:
Lol... I'm pretty sure they were dropping a few bricks before hand... ;)
[EVO 4G General] Khilbron:
I'm with the guy on the ID-10-T error. Looking over your "users with the problem"

bmwboy - new to rooting and flashing, when his problem happened

Gandroid - new to rooting and flashing, when his problem happened

itstheshoes220 - Reported this on a SENSE ROM (MYN's WARM) well that blows your ITS CM7 red flag out of the water.

soulassasin187 - Never reported his ROM, you are assuming its CM because of the thread is replied to, however you know people here lack the ability to post in proper threads.

jhonbra - new to rooting and flashing

losphn - True actual issue won't deny that, no explanation

thebeast614 - Only had this problem after flashing tiamat

jander6442 - Reported this on SENSE (MYN's WARM), and only had it after flashing a different kernel

teh roxxorz - openly stated that they aren't having the problem, and haven't had a reboot in forever, only posting in that thread to assist others

facemymusic - Only having random reboots every few days(not bricked), which can fall down to something that was done incorrectly during installation

00mred00 - modifys his roms before he flashes them onto his phone

BrashL - second one with an actual issue, no explanation, no history since december

BRUTAL BROCK - had bad flashes with the tiamat kernel, eventually bricked his phone.

scriptx - no history for a month, unable to determine possible problem, Resolved his own problem to his satisfaction

k2buckley - No problem, identified that a custom kernel didn't mesh with the phone, and resolved it

boobaroo - Third actual problem, from someone who has been working fine since launch

thanamesjames - Fourth actual problem from someone who knows his way around adb, and couldn't resolve it

Westibone - Fifth actual problem

buffnutz1 - nooter who is playing with a friends EVO, can be attributed to user error without knowledge of steps taken

In a nutshell, a whole 5 users of your "MASSIVE" list are actual issues, and frankly **** happens, the other 14 either Did not have a problem, flashed something bad, flashed something wrong, or just plain didn't know what they were doing. This is not an epidemic. CM7 is not bricking phones, this is happening on AOSP, and on Sense. Quit trying to raise a **** storm, before you assume, research someones post history to see what they did to their phone leading up to their reboot/brick.
[EVO 4G General] rstuckmaier:
Oh, and don't forget the fact that he doesn't even have an Evo right now because his got stolen so he's using a blackberry.

Thank you Khilbron, I wish I could click thanks more than once.

[/thread]
[EVO 4G General] HipKat:
First, I didn't say it was a massive epidemic, so don't put word in my mouth, second, thanks for reading further into those than I did, I just scanned, and copied pasted, since I was in a rush to get to my night job.

Your diligence is well received, sir :rolleyes:
[EVO 4G General] rstuckmaier:
The word of the day is "foot" and I believe you were the one who put the word in your mouth.

PS: I don't actually mean to be hostile, but that popped into my head and I couldn't resist.
[EVO 4G General] TonyArmstrong:
I fell victim to the hysteria surrounding this mess, uninstalled CM7N28 and flashed Myn's Warm.

Had it hiccup on me after installing a new kernel.

Thought to myself how much a douche I was to uninstall CM7 when I've not had a single stability-related issue, and realized that any of these non-HTC provided ROMs could potentially doom my phone to brick status.

Promptly restored my CM7N28 installation from Nandroid and my Evo feels brand new again.

Five (reported and verified) cases from over 250,000 installs is a 0.00002% failure rate -- just about double your chance of getting struck by lightning.

It's certainly devastating to those people who've experienced their phone becoming a paperweight, but I wouldn't call what we're seeing an epidemic.
[EVO 4G General] thanamesjames:
As someone who it actually happened to, I'll readily admit I've gone right back to CM7 on my replacement EVO. I also think that most likely its not a "widespread" issue, but it is still more prevelant than some in this thread make it out to be. Regardless, I still think the pros outweigh the risk.

As unethical as it may have been (and who knows, maybe it was a hardware issue?), permanently bricking my phone let me get a replacement for 35 bucks. Soo... not that big of a deal in the long run.
[EVO 4G General] HipKat:
Oops, it happened again

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

and again...

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

:rolleyes:
[EVO 4G General] cordell12:
Still all operator error? Something is happening and if it is a operator error it would be nice to know the exact cause.

Were all these death loops using SBC kernels?
[EVO 4G General] HipKat:
Those last two don't really say what the error is, do they...

Other than the first one was on MIUI.

I don't think it's the SBC that is causing that. I'm not a kernel expert, but I think I know enough to see that a charging style probably won't cause a bad block in memory or change a partition size, etc...

You know, people can say all they want to me for saying something about this, but I've been twqisting my 'droids in every direction possible for 2 years now, and I never have seen anything like this just start showing up, consistently, without seeing exactly what the error is, and I still think it needs to be paid attention too, not randomized in some uselss ratio of errors per user.

I wonder if that's what they said about the first Aids patients??

"Ehh, it's just a few out of millions of people...."
[EVO 4G General] cordell12:
Only reason I mention SBC is I read somewhere in a Droid blog about the battery level dropping from 100% so fast. It was wrote that the phones can not handle full charge voltage for an extended period of time. That could have been debunked by now though?

But the full voltage for an extended time period could be causing a burn out of some blocks, just a thought.
[EVO 4G General] badassdes:
My phone has the continue reboots no matter what ROM I install!! It started when I switched from CM7 to Myn’s RLS 5 since I needed to do the GPS fix. (I’ve been using CM since CM6 and nightlies with no problems until now. When I switched to Myn’s, I was using CM7 RC2, N#23, CM stock kernel).

While using Myn’s

my EVO started to have the reboots, always able to access recovery, but the reboots occurr constantly. So I did a full wipe, even using Calkulin’s Format all, I flashed CM7 RC3, RC4 same issue… flashed Kings GB R2, same issue, back to Myn’s and I still have the reboots.

What should I do? Should I unroot and root again? Is installing “RUU” means to unroot the phone? Please advise.
[EVO 4G General] Rippley05:
Look, we get it. You hate Cm. There is no reason to keep posting links to people with issues, especially one that doesn't fully explain his issue or tell us what he did.. OR even say what rom he was on.

I believe your last set of links proved it happens on sense roms too? We understand your "concern" (riiiight).. but let it go. It just makes you look bitter now..
[EVO 4G General] thanamesjames:
Dude why are you so testy? This has nothing to do with the guy hating on CM7. It has to do with raising attention to a legitimate problem that a growing number of people (myself included) are having. Then for whatever reason a number of users got on and told him he was making something out of nothing, and beat up on him. It's a problem that needs addressing and one that hopefully by drawing attention to it receives a solution.
[EVO 4G General] Rippley05:
The thread title suggests it's only a CM issue when the links he posted suggest otherwise. I'm all for finding out what the problem is, I just don't like placing the blame on something (regardless if its Cm, MIUI, Sense) when nothing is verified.

I follow a lot of these DEVs on Twitter and other places, and they get beat down for so many things, I even seen some of them stop developing because of it. It's just nasty to blame something or someone without being able to explain why their work is causing it.

I definitely think we need to draw attention to it, but if it is happening on other roms aside from CM, then this isn't the right way to bring it up.
[EVO 4G General] sftd:
Hey guys, I don't mean to alarm anyone, but I've developed a problem with my phone and I'm fairly sure CM7 is what is causing it. After having it installed in various forms for a few weeks now, I've developed a hairline crack directly in front of my power button. This crack wasn't there when I was running the stock Sense build that came with the handset. This unfortunately leads me to believe that there is no other option than CM being the cause of the crack. Again, I'm not trying to start a new fire or unnecessarily cause undue alarm, but I think people should be informed so that it doesn't happen to their phone as well.
[EVO 4G General] nined1talon:
Hahahaha :)
[EVO 4G General] HipKat:
First, I don't HATE CM. I ran it for a long time and loved it. I flashed the nightlies, did the testing, etc, and used a few CM ROM's, like Destroyer, SalvageMod, etc.

I only went back to Sense when I had a similar problem 2 times, both on CM Mods.

You wanted to talk about percentage of users, well users reporting the problem are almost 99% CM users. And since then, other variables have been added. Unrevoked seems to be a constant with people that have the problem, for one.

This isn't to bash CM, it's to show there MAY be a problem and that it should be looked into, instead of being callously brushed off.
[EVO 4G General] thanamesjames:
Point well made. It seems to me it's an AOSP thing, I haven't heard of any sense roms causing it. With that said, it seemed, at one time, that the common thread of everyone (including me) who had the problem was CM7. I don't think we should crucify the guy for pointing that out - whether he was right or wrong. It certainly looked like CM7 was linked to all the cases in some way for a while. But I agree, throwing the blame squarely on Cyanogen would be in poor taste - I certainly have nothing against the team, I love what they are doing enough to go right back to CM7 on my new Evo! But in all I think some on here should cut the OP some slack - I don't think his intention was dissing CM7, but raising some awareness.
[EVO 4G General] sftd:
Just to keep everyone up to date, I flashed back to a Sense rom (namely MikFroYo 4.6) and haven't noticed any new cracks in the phone, so I think that at least for the moment I am safe. This is disappointing to me to say the least, as I was thoroughly enjoying the CM experience, but I have no desire to continue to find hairline cracks in various places around my phone caused by my choice of rom.
[EVO 4G General] Rippley05:
I agree that it was a little harsh, but, he did post several links that he apparently had enough time to dig up but didn't have enough time to read himself to find out they weren't all what he made them out to be.

Those links showed it was not only a CM thing, it was fine... I didn't say anything. Then he shows up with 2 more links, one of which is a thread I posted a reply in. The guy said absolutely nothing about what rom he is using, what process he followed or anything.

We should definitely talk about this issue, and it appears to be more common on AOSP roms.. which fall to CM simply because that's the most popular by FAR. It would be much more appropriate to title things like that instead of actually calling CM out.

That said, I'll let it go because it isn't a big deal.. just a bit unfair.
[EVO 4G General] thanamesjames:
If its only AOSP roms, does that mean its also only gingerbread roms?
[EVO 4G General] HipKat:
Here's a new one, running CM... random reboot into the same problem

http://xdaforums.com/showthread.php?t=1016830
[EVO 4G General] boliviano3:
The fact that this one was on CM6, the last one you posted was on MIUI, & it's been reported on other Sense ROMs means that CM7 or CM for that matter isn't the culprit but that it's another issue altogether.
[EVO 4G General] Rippley05:
I see he rooted using unrevoked. Is that how they all rooted? Kinda doubtful that it would be a problem there, but couldn't hurt to check I guess.
[EVO 4G General] remman:
When it happened to me I was rooted using toast's method and also on the ENG bootloader. It is likely why I was able to at least get s-on.
[EVO 4G General] Rippley05:
Yea, that's what I did. Way back when there was a bounty to find root for one of the OTA's early on. Some "anonymous" user found root where we had to time a step with a flash video..
[EVO 4G General] mattykinsx:
Flashing a ROM just copies files to the /SYSTEM partition...and BOOT if there's a kernel.

Unless you're a, to be nice about this, ****ing moron, you can't brick a phone flashing a ROM.
[EVO 4G General] Shaihalud9:
Ive had CM twice now brick my phone, and I dont use RCs or Nightlies. Im using Stables releases. First time I was able to run the RUU and re-root... This time I cant even get into recovery.

The Sense roms Ive flashed have never done this, so there has to be something different about Cyanogen/AOSP roms.

Yes I used Unrevoked, and I am S-ON. I like CM, but Im probably never gonna flash it again. Ran into too many issues.
[EVO 4G General] sftd:
Man, I totally know what you mean, that's the same way I figured out CM caused the hairline fracture near my power button, at least you are getting some help with your issue, I haven't even got a single reply!
[EVO 4G General] mattykinsx:
People need to stop using the word brick.

It's only bricked when your device won't even power on anymore.

Run a RUU, and don't root again if you guys can't handle it.
[EVO 4G General] Rippley05:
I wish I could help you man, I really do.

Unfortunately, if you get it going again.. I suggest not rooting at all. It has been reported on Sense roms as well and the only way to be protected is just run it stock.
[EVO 4G General] Shaihalud9:
Running a RUU is not possible, I get error 170 over and over... I tried using one of the PC36IMGs, which flashed... but I still get endless boot cycles.

I dont know what to do anymore.

And it may as well be bricked, cuz I cant damn well use it.

And I can "handle" it. What I cant handle is a ROM rebooting randomly and throwing my phone into end less boot looping.
[EVO 4G General] mattykinsx:
Try a different RUU.

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

Or try a different USB cable.

A quick google search shows that error 170 is a connection error.

Listen, respectfully, flashing a ROM simply copies files to the system folder.

If it has a kernel then it copies to BOOT as well.

Think of it like this:

You have Windows, then you have your BIOS.

Installing Windows 7 when you had Windows XP is not going to affect your BIOS.

Your ROM/Kernel is Windows, your bootloader/radios/recovery is the BIOS.

That's the easiest way for you to think of it.
[EVO 4G General] gpz1100:
I'm not for or against CM, or any other rom, but this issue has become troublesome.

It would seem that something is getting corrupted during the rom's operation. Once this corruption occurs, recovery is no longer accessible. Reflashing it appears to complete successfully, but the phone is unable to enter it none the less.

I agree with one of the posters above, that it's likely due to memory corruption. Memory gets corrupted by having a particular location written to, over and over and over again to the point of the memory failing.

We need to try to find the commonalities, and then explore what may be causing this effect.

@dirty, if it's an operator error, how? Most of the failures i've read about are occurring from within fully functioning phones.

Edit: As for trying different RUU's. So long as the RUU is digitally signed, short of trying an older RUU, there shouldn't be any differences between them, regardless of where it came from.