yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M7)] steelmoto:
I flashed both 4.2.2 and 4.3 and had no issues whatsoever...I am leaning towards what others here have been saying, that the phones effected were on the wrong side of the tolerance line...I had a HTC one x previous this and I noticed I couldn't undervolt at all or my phone would always have random reboots...while others with the same phone could undervolt all day long and have no issues...no phone is exactly the same...they all handle things slightly differently
[Sprint HTC One (M7)] vader860:
Perhaps the best thing at this point is to say unknown and flash at your own risk. Too many unknown variables to attempt to pinpoint the cause.

An OS would not in theory brick hardware assuming that there were physical hardware protections in place. For example if an OS bug causes continuous 100% utilization of cpu, the cpu may eventually overheat. If there is an independent hardware thermal sensor to shut everything off, then at least one would have some warning. Apparently though, these phones don't have thermal sensors to shut off automatically if overheating.
[Sprint HTC One (M7)] adamlee011:
Really? I never heard that. How bizarre. My evo shuts down when it gets hot. I hope there's at least thermal d working under under the hood.
[Sprint HTC One (M7)] SantinoInc:
I have run Slim 4.2 and Slim 4.3 each for a couple days with no I'll affects. I haven't heard about any recent issues of AOSP bricking phones.

I'll tell you guys what though: Sense just runs smoother for me overall. As nice as some of the AOSP Rom features are the rom just doesn't feel as smooth as Sense.
[Sprint HTC One (M7)] dandan2980:
It seems to have delay using recent apps on aosp but still a smooth experience. I am back on sense and I just install nova and freeze sense in TB. Also in cm10.2 thread in general there is talk that they are changing the way the hard ware keys are assigned. Ever notice that on aosp you have to long press for recents ugh. I believe that is what causes delay when using recents on aosp even when using the navbarb on Slim.

Hopefully on aosp the give us the the double tap home option. On the GE Rom it's butta butta.
[Sprint HTC One (M7)] SantinoInc:
I have my eye on the GE Rom but I'm not willing to sacrifice something as crucial as PHONE making ability. Once that gets squared away I'm definitely trying it.

Off topic have you ever tried that "Bareback" Rom. Think the dev goes by Il Duce or something like that? That is pretty much what I'm looking for...a stripped totally bear Sense Rom that still has fully functional core features.
[Sprint HTC One (M7)] dandan2980:
I am familier with Team D3rp. I ran the super jelly on the evo lte. I did use milestone1 release of bareback and ran it for a week was smoking fast. But I'm happy on Tranquilone right now digging all the customizing the Rom offers and nova is running so smooth plus the transparency is boss on this Rom
[Sprint HTC One (M7)] SantinoInc:
what is tranquilone?

Disregard...i found it. i see it's the only sense based rom in the original development section. i was always curious about that rom.
[Sprint HTC One (M7)] adamlee011:
It's a great rom. I personally prefer to use team venom's roms but I love tl's kernels and his are the kernels that are default on tranquil. I have to recommend it.
[Sprint HTC One (M7)] flimsy888:
Any updates on this?
[Sprint HTC One (M7)] adamlee011:
This thread sort of peetered out. I think most have been having success with recent aosp roms. I believe the solution may have coincided with the release of international kernel source. I know of many people running aosp. Use your best judgement.

I get by with a little help from my friends.
[Sprint HTC One (M7)] sauprankul:
That only works if your button lights are blinking when you hold power + vol or w/e.
[Sprint HTC One (M7)] Alex1123:
So no one using cwm got a bricked HTC one?
[Sprint HTC One (M7)] sauprankul:
So far, nope.
[Sprint HTC One (M7)] mswlogo:
Yeah and probably got a brand new phone rather than a repaired or refurbed one (stores don't generally have refurbs on hand). Well worth the $50.00
[Sprint HTC One (M7)] sauprankul:
Funny, I called the local Sprint store and they said they only deal with people who have insurance. I'm assuming you all had insurance, then.
[Sprint HTC One (M7)] Alex1123:
I basically got a brand new one I'm almost sure about it no dents scratches or anything screen was like new no dead pixels no gaps, nothing. perfect came with it's original wrapper thing when you get your HTC one and everything
[Sprint HTC One (M7)] SantinoInc:
I'll tell you guys another reason I'm not so hot on AOSP roms (besides the obvious brick issue) I don't like the fact the the AOSP devs don't even have this phone.

I would have more confidence in the Rom if I knew the dev had the same phone as myself and was running the rom he's posting. Just my .02
[Sprint HTC One (M7)] adamlee011:
Nobody yet? You sure? I haven't looked into it yet. I did read that paranoid android is planned officially for the one. Looking forward to that. In all fairness these guys know what they're doing and have testers who have the phone.
[Sprint HTC One (M7)] ewalk4866:
You are way wrong about that. Deck has the phone and he was the first to get aosp cm 10.1 for us and tmartin also has this phone and has a aosp rom out for it. I think you might need to go look again :)

Sent from my HTCONE
[Sprint HTC One (M7)] SantinoInc:
Ok, I stand corrected.
[Sprint HTC One (M7)] crusnik23:
I'm curious if anyone with just a stock rom but with twrp has had any problems. It would help to narrow down whether or not the issue lies with the aosp roms or with twrp itself. I'm currently running twrp with viper and haven't had any problems but if there is a possibility of twrp being the issue I will move to cwm just to avoid problems. I was pretty much waiting until the google edition of the phone came out to try a aosp rom anyways since that will give devs more information.
[Sprint HTC One (M7)] adamlee011:
I don't think so.
[Sprint HTC One (M7)] bboysmerf:
My phone bricked with a tw rom

I have twrp installed and was running Blue & Jazz V1.7 by: timberwolf671. Had the phone plugged in when I was sleeping. Woke up to the alarm on my phone going off. I went to disable the alarm and then my phone froze. I thought nothing of it and went to holding the power button to power cycle the phone. The phone goes black and then I got nothing. The charging led never came back on while on the charger. The phone will not turn on at all. I left the phone on the charger for an hour and still no led. Took it off the charger and tried to power on and still nothing. I have been trying all day to hold the power button for a long period of time and also plugging and unplugging the device from the charger...........I got bricked..... :(
[Sprint HTC One (M7)] dandan2980:
This is getting weird just random bricks. I recall the GS3 having an issue with I believe it was the mother board the phone would just randomly die and never turn on. Wonder if the One has a hardware issue that needs to be addressed.

http://m.androidauthority.com/galaxy-s3-sudden-death-mainboard-issue-141783/
[Sprint HTC One (M7)] sailio:
I've done it twice, only because it appeared to randomly restart but stuck on boot screen. Hardware reset didn't work. The lights stop flashing after a while. Let it die, charge it but couldn't turn it on right away and the led was blinking. When it turns solid I was able to boot. I just wiped cache/dalvik before I tried booting.
[Sprint HTC One (M7)] dandan2980:
My battery has died on me at least 10 times already on sense roms lol and I haven't had any problems thank god
[Sprint HTC One (M7)] crusnik23:
[/COLOR]

I am using twrp with viper rom and my phone has died a couple times but I haven't had any problems but if twrp is potentially an issue I will just switch to cwm
[Sprint HTC One (M7)] malexxran:
Wasn't twrp bricking OG HTC evos? Idk it I'm hesitant to use twrp.
[Sprint HTC One (M7)] crusnik23:
I used twrp on my evo 3d with no problems but if twrp has had past issues on htc before maybe there is a fix
[Sprint HTC One (M7)] adamlee011:
You know that's normal right? The light flashes until there's enough juice to run it. The phone runs I'd the battery only, not the wall power so when you run it completely dry, it does that. I'm wondering too if there's a hardware issue. I have 0 problems. I use twrp.
[Sprint HTC One (M7)] flex360:
if the LED is blinking when you hold the power button, just let the battery die

and twrp isnt bricking phones, if that was the case, then it would have been happening to sense roms as well

use your heads
[Sprint HTC One (M7)] Alex1123:
Well everyone who bricked was running twrp and cm10.1 I had zero issues with sense and twrp but I'm not taking anymore chances I just flashed cwm again and probably won't flash a cm10.1 rom until the aosp one is released
[Sprint HTC One (M7)] dandan2980:
This guy stats he was on sense I think it's hardware related
[Sprint HTC One (M7)] Alex1123:
Hmm strange then maybe it is hardware related unfortunately I think we'll probably have to wait for more people to report bricks until we can get a pretty good idea of what's going on
[Sprint HTC One (M7)] air23cpt:
I was on a CM10 from http://get.cm/?device=m7spr I was on CM 6/19/2013 and the phone started to get hot and I mean burning hot and it wouldn't charge I let it cool down Charged it over night then flashed the latest Viper rom via TWRP still was getting very hot and then the battery died now the phone doesn't respond to anything no PWR button no PWR+VOL- took it to sprint store the tech couldn't get the phone to respond either.
[Sprint HTC One (M7)] sauprankul:
So far, only the TWRP + Cm 10.1 combo is a problem. And I think it's only for Sprint. And there are many people (I'm sure) who fall under this criteria but have had no problems. Not to scare you or anything, but at least for me, there was no warning sign. The battery was full ish and the phone was in my pocket and it wasn't overheating or anything.

EDIT: Ok, so apparently, ONE person has had this problem with Sense + TWRP. See post #33. Hmmm...

EDIT: Apparently this is widespread in the Intl forums too. http://xdaforums.com/showthread.php?t=2295374
[Sprint HTC One (M7)] Kraizk:
Well taking an educated guess here then.... The commonality of these phones breaking when the user is "watching" has been the phone getting very hot. As many of you may know many HTC phones (and I am sure other brands but I have not used them) block charging when the device is hot. This is a safety precaution. What could theoretically be happening is that the device disables charging as a safeguard expecting the phone to cool off before the battery dies (or the standard recovery is still able to monitor the temperature). When the phone dies while hot this safety feature is not disabled so the phone "thinks" it is still very hot and refuses the charge resulting in the bricks some users have now. I do not know if this is a hardware or software issue though and lack the knowledge of chasing this further.... If anyone has some experience in looking into this I am sure the entire community would be grateful.

Additionally has anyone seen these issues reported on a non sprint variation of the device?
[Sprint HTC One (M7)] sauprankul:
Maybe my touch sense just turned off when my phone bricked, but I really don't think my phone was hot when it bricked. It might have been, but I severely doubt it was so hot as to disable charging.
[Sprint HTC One (M7)] bboysmerf:
My phone was not hot when it happened to me.....I had my phone freeze a bunch when plugged into a charger while waking it up...it started like a week ago...one instance I had to wait for the phone to die before I could unfreeze it...even holding the power button to soft reset did not work...that was before my phone bricked.....
[Sprint HTC One (M7)] xadidas4lifex:
yo if you brick your phone, your fault.

never once have I bricked any android device, that i own, by flashing AOSP.
[Sprint HTC One (M7)] :
Haha I thanked this post because the bottom line yeah you're right it is your own problem. But to say that there isn't some underlying cause could not exist is just ignorant. Congrats!
[Sprint HTC One (M7)] xadidas4lifex:
user errors are one helluva thing.
[Sprint HTC One (M7)] sauprankul:
Sorry if I read this wrong, but are you suggesting that these bricks were caused by user error?

Just to clarify, most of these happen completely randomly, while the phone is charging. Not while flashing, or overclocking or transferring files or anything. Just standing by. Please explain how this is user error.
[Sprint HTC One (M7)] Kraizk:
Yo dog I heard you like making useless comments. So I made a useless comment on your useless comment so I can not help while you not help.

But seriously. As a user who is NOT bricked I am concerned about the issues that could arise be it on the ROM end or the recovery end or even user error. Not a single person has "blamed" anyone but themselves for what ever happened. Instead the point is to try and see what exactly did happen. Seeing as flashing a new rom is simple on the One compared to other phones I'd be interested how the "user" screwed up this time. You're not helping.
[Sprint HTC One (M7)] SantinoInc:
Another one bites the dust fellas. This post is from AOSP PA:

XikkeN: My phone died last night. It got really, really hot on the charger. I unplugged it and turned it off. It never turned back on. It was 21 days old.

My guess is that there is something in running AOSP that causes the phone's hardware to malfunction. This is the most bizzare kind of bricking I have seen...and this is my 5th rooted phone. I have usually associated phones getting bricke
[Sprint HTC One (M7)] ticklemepinks:
what aosp roms are yawl running cuz not a single person running Deck's 10.1 rom has had an issue!!!
[Sprint HTC One (M7)] Alex1123:
I was running decks Rom and bricked I'm pretty sure everyone who was on cm10.1 was using his Rom actually so yeah and I had no issues as well it just never came back on randomly
[Sprint HTC One (M7)] tommason1968:
Yes it was a problem for the old evo. Is clockwork mod any good. On my old evo it didn't work very well at all
[Sprint HTC One (M7)] SantinoInc:
Idk why we are all assuming this is Recovery related. Nobody has reported the phone being bricked while doing anything in recovery. Is it possible that HTC did something to the phone that it can tell you are running a non stock based Rom and it conks out?
[Sprint HTC One (M7)] flex360:
it has to be the kernel
[Sprint HTC One (M7)] krazyflipj:
For those that bricked their phones, have you reached out to deck or anyone on the cm team about the issue? Maybe jump on IRC?
[Sprint HTC One (M7)] snowblind2142:
This is quite concerning.

I've been back and fourth between PAC,PA, domination, RootBox, viper & hyper in the last few days....

My question, all the bricks so far, are they all s-off?

If so, as I am s-off, I would of assumed locking would bring the device back to is least brick venerable state? No?

Or.... Lol, maybe tampering, ie. Re-locking might brick...

Also, one last question, was the only sense brick on 4.2.2? And did they have the day dream feature enabled? I nearly fried my phone enabling this.

Phone: M7 - HTC One

Rom: RootBox - build 26/6/2013

Bootloader: Unlocked & S-Off

Kernel: Stock RootBox kernel
[Sprint HTC One (M7)] basedboii:
after reading all these aosp horror stories, I am just going to hold off on flashing aosp. Maybe after the google version is released then I will then flash aosp.
[Sprint HTC One (M7)] Alex1123:
Mine wasn't s off and no day dream was enabled so idk about that and I believe the sense brick was on 4.1 and bricks seem to be random but most seem to have twrp in common well I don't think there has been a clockworkmod brick
[Sprint HTC One (M7)] sauprankul:
S-on for me. Which makes it all the more confusing. I remember disabling daydream on mine.
[Sprint HTC One (M7)] leadfoot99:
Wow i have never bricked any phone in my life, and have flashed several hundred roms on several devices. I wonder how many people flashed gsm roms on cdma phones and vise versa, because that will brick'em for sure. Just my 2 cent's worth.
[Sprint HTC One (M7)] xHausx:
All recoveries and kernels had issues when they changed the MTD block size, it wasn't anything specific to TWRP. Even the engineering bootloader wouldn't work on the new ones.
[Sprint HTC One (M7)] xHausx:
Can everyone whose had issues with their devices please include more information about your setup? Which version kernel you were using, hboot version, recovery, etc. The more the better.
[Sprint HTC One (M7)] snowblind2142:
Thanks for the response people.

Haven't pickled my head since the SGS series had the MCAP erase brick bug fiasco..

We need to make sure we keep a log of who, when, where, how and what they were running at the time so we can monitor it.

Ill be honest, wont stop me flashing the next Domination Rom Im watching out for ;) that thing is a beast.

Might "invest" in a back up just in case, lol

Must ask, as there is nothing left on the handset (well, as far as we can see so far thats recoverable)Would it still be covered by warranty/insurance? or because we have unlocked the boot loader through HTC website, would that be a auto FAIL... :silly:
[Sprint HTC One (M7)] Kraizk:
You want a cookie? I have not bricked a phone either but I am willing to help. I was going to write something like this again but instead I will save myself the time and just ask that you read this post http://xdaforums.com/showpost.php?p=42849461&postcount=54

Please do not post in here if you are not trying to contribute any assistance. If someone flashed a GSM rom on their CDMA phone it would not have worked at all. If you read the thread you will see that people had their phones working just fine until suddenly it did not. The simple fact they had reception should immediately tell you this did not happen.
[Sprint HTC One (M7)] Alex1123:
Device htc one sprint

Recovery twrp

kernel stock cm10.1 6/7

running cm10.1 nightly 6/7/13

S-on

Hboot don't remember

Hope it helps
[Sprint HTC One (M7)] :
My issue might be a variant, but it seems similar enough to post here. Device fails to wake from deep sleep, requiring a hard reset to turn back on again (using the SlimBeam AOSP-based ROM). I'll post more over in that thread (over in the Original Android Development section), but here's what I'm running.

ROM: SlimBean build 6

Kernel: 3.4.10-CM-g140211f

S-OFF

Stock hboot

TWRP Recovery
[Sprint HTC One (M7)] sauprankul:
Device: Sprint HTC One

ROM: Cyanogenmod 10.1 Nightly 6/12/13

Kernel: Standard CM

Recovery: TWRP

S-Off: No

The phone was in my pocket. It had a good amount of charge as far as I know, and the phone didn't feel hot.

No overclocking or task killers. Had set max freq to 1.5 Ghz and gov to conservative (though that was a while before the brick).
[Sprint HTC One (M7)] the.emilio:
All this talk made me download ROM Manager and flash CWM lol. Not gonna take a chance.. hope it gets fixed if it is recovery related. Thanks everyone for sharing their experiences. :D
[Sprint HTC One (M7)] :
If you don't run into issues, please let us know. Obviously a silly request, but it'll be nice to hear (although reverse confirmation isn't possible, so...yeah).
[Sprint HTC One (M7)] the.emilio:
Will do.
[Sprint HTC One (M7)] Ahanix:
I'll post if I see anything happens as well. Flashed CWM out of paranoia and have been running CM10 since the day deck upped it.

Honestly I have always liked CWM better, nice to have access to both the original and 0 file systems.

Can't handle going back to stock, so hopefully nothing happens.
[Sprint HTC One (M7)] Admiral Sir Manley Power:
Good to know. Thanks for this thread.
[Sprint HTC One (M7)] :
htc dev unlocked

rooted

s-on

twrp recovery

cm10.1 nightly 6/05

cm10.1 stock kernel

hboot i don't remember but it was which ever was straight out the box on release day.

i noticed the capacitive back button was slow to respond sometimes not responding at all. i was on a fairly early build, before s-off could even be achieved. also phone was on its normal cycle of charge overnight as i sleep,
[Sprint HTC One (M7)] :
I am more than a little confused as to how recovery interacts with the rest of the system in such a way as to cause these issues. Definitely the friendliness of Nexus devices has spoiled me some. If this is workable, do let us know! Admittedly though, I actually like many elements of Sense more than stock Android-- if only they flattened the gradients some!
[Sprint HTC One (M7)] Ahanix:
It's honestly kind of hard for me to understand how the recovery could even play a part in doing this, but from what I have read the only people to have this problem (So far) have been running TWRP. Is there any way this could be due to the phone having issues with the legacy and 4.2 (0) file system and TWRP's inability to see this? Probably not, but honestly that's the only difference I can see between CWM and TWRP at this time and I'm not a developer.
[Sprint HTC One (M7)] Kraizk:
Several other people have posted this is possibly a kernel issue and not a problem with TWRP
[Sprint HTC One (M7)] :
My immediate instinct was a kernel problem, but the number of people with CWM + AOSP posting about this issue seems to be ... well, not zero, but just about. It's certainly a confusing situation, and an awful one to test for (because ROMs/kernels/hardware/recovery can all interact with one another in strange ways from time to time, such as TWRP on my TF300T requiring a particular firmware version to avoid screen doubling).
[Sprint HTC One (M7)] Kraizk:
My question about this is if CWM is even used by a large number of users. I know most people have gone the way of TWRP as it offers more versatile options and is often available first on major phones.
[Sprint HTC One (M7)] SantinoInc:
I'm tending to agree with your theory. If I had to guess I would say that at least 8 of 10 rooted HTC ONE owners are using TWRP. Since there are PROBABLY so many more TWRP users than CWM users it makes it seem like there may be an issue with the recovery.

We need some really skilled DEVS to investigate this situation.
[Sprint HTC One (M7)] :
Based on what statistics? I personally started with CWM, and people who started with it may well elect to use it even if most root methods out there currently involve TWRP. Without statistics, this is a fairly meaningless discussion-- beyond the fact that TWRP is a common thread in reported case.
[Sprint HTC One (M7)] sauprankul:
By the way people.

HTC can tell if your phone was bootloader unlocked/tampered. Even if it's hard bricked. Like no blinking lights, charging LED or anything.

So now, HTC wants to charge me $200 to fix it. Damn. :eek::mad::crying:

Any suggestions people? I am currently trying to ask the techs how they got into bootloader. Probably if they can, I can too.

So, if they tell me how to get into the bootloader, should I be able to RUU it?

And I just realized. I didn't try booting the phone with the SIM tray out. Could that possibly be a solution?
[Sprint HTC One (M7)] CarbolDroid:
For what its worth I had the same thing happen to my Moto Photon 4g, running cm10 just totally bricked as described, really weird.

I'll be sticking to viper for a bit...
[Sprint HTC One (M7)] snowblind2142:
Surely they would know anyway because you had to send off for your unlock token? No?
[Sprint HTC One (M7)] sauprankul:
The guy specifically said "illegal" software. So, I'm sure he wouldn't have minded if it was only unlocked.
[Sprint HTC One (M7)] :
That's (likely) bull****. There's nothing in the law against running custom software. On the other hand, if you're using a Sense-based ROM it does trample on the EULA a bit.

In any event, I would be more willing to bet that they have a tool that lets them have access to internal storage. Could help you, might not. Either way, $200 is pretty steep.
[Sprint HTC One (M7)] adamlee011:
There's certainly nothing illegal about it. They don't have to fix it replace it, you still owe your carrier the money you're contracted under (if you are), but nothing illegal.