yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
If we can get camera and these "bricked" issues figured out and understood (it could be poor behavior, could be that the device is trying to load recovery once battery drains to zero and try to charge which could cause it to act "bricked" until you let it charge for quite a bit and try to reboot, or a plethora of other things) we will be ready for nightlies.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Still don't have any bricked users in the channel, don't be shy please. we're trying to figure out how this happened.
[AT&T, Rogers HTC One X, Telstra One XL] JBLogic:
I'll be able to pop in later, working atm.
[AT&T, Rogers HTC One X, Telstra One XL] aqtrans:
If still needed, I'll hop in once I get home around 11pm CST tonight. :)
[AT&T, Rogers HTC One X, Telstra One XL] vaggolena:
I just joined the room.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
I put up a new build (08062013) that has the revert to power collapse commit and working bluetooth up in the OP.

I am off work tomorrow so I will be able to field questions tonight. Wasn't feeling well last night so I wasn't up late enough to catch any of you on IRC. If you are able, please join #cyanogenmod-evita on Freenode tonight after 6pm CST and we'll gather some information up and put it together to see if we can locate what may have caused your devices to brick (the few of you that it affected).

Again, I'm not sure if this ROM is to blame, but either way, I am very sorry for the users whose devices bricked. I hope that you are able to get them jtagged or replaced in some fashion. If not, I hope you upgrade to a newer android device (HTC or not) and enjoy the CyanogenMod experience on said phone.

Thanks all,

-h8
[AT&T, Rogers HTC One X, Telstra One XL] zipsnet:
Hey h8rift,

I have 1 or 2 guys over the Ville forum with the same problem as well with a build I made, pretty much using same sources as you guys ! So most definitely is not your rom but it might be something in common between both roms or the way the were flashed ! or something around that. I'll try to join you guys after 6pm CST to see if we can find out how it happened!

Thanks

-Z
[AT&T, Rogers HTC One X, Telstra One XL] danielgek:
in my opinion has to be with the kernel because is almost the same for them .. i will be there too i think ;)
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
I'm downloading this now. Is there any data that I can record now about my phone that might be useful to narrowing this down later if I do happen to brick? I'll be sure to grab all the details from the bootloader screen, but is there anything else?
[AT&T, Rogers HTC One X, Telstra One XL] Koizuma:
So far been running this for about 45 minutes or so now and it's working great so far.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
yup. no power collapse anymore!

by the way, can someone explain to me why was that commit merged before on the unofficial 10.2? what purpose was it supposed to have?
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Power collapse aka deep sleep. Which as you'd imagine, saves battery life. As we're in an alpha state, some of these things don't work like they should. I'd imagine it'll get merged again when the bugs are worked out.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
I'm either crazy and insane or insane crazy because I'm back to where it all started... LOL
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
It's after 6pm CST...where are the people who bricked? Go here https://webchat.freenode.net/ and sign into #cyanogenmod-evita channel. Remember to use your XDA name.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
based on the chat, should everyone, who hasn't already, upgrade their touchpanel?
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
There's really no reason you should have the downgraded firmware at this point any way. All the ROMs that have been made in the last few months can use the upgraded firmware.
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Right but there may still be some early adopters who were told to downgrade in the OP. Every brick seems to occur while plugged in and likely in deep sleep but all the reports came from ppl who still had the downgraded tp.
[AT&T, Rogers HTC One X, Telstra One XL] Franklee99:
How do we tell which touch panel fw we have?
[AT&T, Rogers HTC One X, Telstra One XL] mikelebz:
you would have had to physically go through the steps detailed in this thread: http://xdaforums.com/showthread.php?t=2159863

if you are unsure or don't remember, you can always re-flash the upgraded FW as detailed in that thread as well.
[AT&T, Rogers HTC One X, Telstra One XL] aydun:
Well, my phone finally bricked, as of this morning :P (last build, not the latest one out now)

If you needed info still, I was on upgraded TP. The last two nights I didn't have my phone on charge since I'd been charging it during the day whilst using it. However, last night I did have it on charge. Whether that's coincidence or not though..

Anyways, now have CM on my new HTC One and loving it!
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
Glad to hear you were in a position to replace it easily and quickly, but that's a little worrying that the older build bricked with the upgraded TP firmware, because I was hoping that was the root of the problem and it would be easily avoided.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Attention everyone:

Thanks to intervigil and the data you all provided us, we were able to figure out that the HTC One XL uses Samsung EMMC chips. If you never owned a Samsung SGS2 or later or have never read the horror stories from Samsung devices until recently, you will have inevitably heard of the "EMMC Brick Bug".

Apparently, some revisions of the EMMC chip of our devices *are* susceptible to the brick bug. To check for yourself, download the EMMC Brick Bug app from the play store, give it root privileges and it will tell you if you are susceptible or not and what FwRev you are on.

The Great News:

We've already committed the fix to keep the EMMC from bricking even if you *are* susceptible to the kernel. I'm going to create a build and put it up shortly that will negate any more worry, paranoia, or bricks on these devices. This was also backported to CM-10.1 nightlies which was also susceptible to the brick bug. HTC's stock ROMs already had a check for this. When we built the 3.4 kernel from scratch, we did not have such checks in place. We do now. To those who HAVE bricked, I apologize but also thank you for helping us narrow down this possibly catastrophic problem for all other users. I hope you are all able to get your phones jtagged and then you will be able to safely re-flash CM or other AOSP roms (which use our code, so same thing could happen).

Thanks again, and I will have a build up in a few hours with this bug fix in it. You will *not* need to check the EMMC Brick Bug app with the new builds going forward. If you decide to flash the build that is up right now PLEASE check the EMMC Brick Bug app.

Thank you,

-h8
[AT&T, Rogers HTC One X, Telstra One XL] ethantarheels123:
So the emmc brick bug app can be used even on non cm ROMs?

Edit: just ran it on magiorom. It works and I have a no brick chip!
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Yes, but all AOSP roms are built off of CM, so when they update, they will get the fix as well.

HTC's code in stock ROMs already had the protection in place. We didn't since we had built 3.4 kernel from scratch. Our old 3.0 kernel did have the protection in place since it was built off of the HTC stock kernel.
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
So this is why I've been able to get out of QHSUSB_DLOAD every time with no problems...
[AT&T, Rogers HTC One X, Telstra One XL] 'busa:
So it says my EMMC is "sane". I just can't wait any longer. I can go ahead and flash the build that's up right now?

How come other 3.4 based ROMs didn't brick any phones until CM 10.2?
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
At your own risk, but yes :)

Others didn't because fstrim was added in Android 4.3
[AT&T, Rogers HTC One X, Telstra One XL] dustinhayes93:
You guys are great. Thanks for your time and hard work on all of this!
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
New build is up. Everyone should update to this build ASAP to make sure you are protected.

Thank you,

-h8
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Nice detective work everyone!
[AT&T, Rogers HTC One X, Telstra One XL] kewlguru:
Thanks a lot H8! Great to see you guys coming together and finding the root cause of the issue.

BTW for those of who did brick it, and unable to get it working, any tips?

The instructions from the unbrick thread didnt work out.

thanks,
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
No. Fstrim simply exposed the Samsung EMMC brick bug on certain revisions. We added code to protect those revisions from getting bricked. So now everyone is safe to use CM-10.2 without worrying about it bricking.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
I'm working on something. Was yours bricked due to cm-10.2?
[AT&T, Rogers HTC One X, Telstra One XL] kewlguru:
Yes. I was on the 1st build put out by you.

I had no issues for about a week. Then friday last, boom the device bricked.

Anyways, i have already sent it to JTAG repair.

I was curious though if any way existed to bring it back.

The bummer about the whole thing is I am stuck with a iPhone as a replacement! :mad:

Thanks a lot for all the work you do
[AT&T, Rogers HTC One X, Telstra One XL] Franklee99:
Quick! Someone help this poor man! :)

But seriously, good luck with finding a fix guys.
[AT&T, Rogers HTC One X, Telstra One XL] 'busa:
Just checking in to report that everything is working beautifully on today's build! :)
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
The link in the OP isn't working for me. Any mirrors?

After 10 attempts finally got it to work. Also there's an issue with Spotify & the DSP force closing. If after this new build the problem persists I'll be back with a logcat...
[AT&T, Rogers HTC One X, Telstra One XL] aqtrans:
Glad to hear you guys found the problem and already got a resolution whipped up. Great work! :cool:

My One X was bricked by 10.2, and I already bought and received an HTC One from the Play Store to replace my bricked One X, but if you ever need a guinea pig to try some fix, feel free to shoot me a PM, as my One X is currently sitting in a drawer just waiting to be poked and prodded :)
[AT&T, Rogers HTC One X, Telstra One XL] aritrea:
Great to here. Kind of a software fix? Really looking forward to whatever you try :)

Btw my device is a bricked ville, feel free to pm me if you want me to test anything
[AT&T, Rogers HTC One X, Telstra One XL] vanja_z:
Hey all, can I get an MD5 for cm-10.2-20130809-UNOFFICIAL-evita.zip?

mine is de3b22a406fec1fc0a486dbe06275999
[AT&T, Rogers HTC One X, Telstra One XL] anawong:
The same.

de3b22a406fec1fc0a486dbe06275999
[AT&T, Rogers HTC One X, Telstra One XL] Koizuma:
So far the update 08/09/13 is nice and smooth
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
Having data issues on the new build.
[AT&T, Rogers HTC One X, Telstra One XL] SebringTech:
Can't wait to give this a shot but I can't live without my camera lol glad to see the bricking issue was found and resolved.
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Check you access point name in Wireless & network settings. It should be set to AT&T LTE, not Wap.cingular.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's not very productive at all. Give more detail.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] thewierdone:
B-U-T-T-E-R

ahhhhhhhhlllllllll hail the buttery goodness that is cm10.2!!! cant wait till camera is functioning! this is going to be awesome!
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
Suhweet! It says I have a "sane chip" on my replacement. Thanks for all your hard work h8!
[AT&T, Rogers HTC One X, Telstra One XL] mwa3aan:
Battery life is excellent. Very very smooth. Looking forward to camera and nightlies.

Well done on tracking down the brick bug.

Thanks H8 and team!!
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
grey bar on data and cycling airplane mode does not work.

apn settings are correct.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Flash boot.img correctly? That's not a normal bug... Maybe your local network is down
[AT&T, Rogers HTC One X, Telstra One XL] ethantarheels123:
So buttery smooth! Great job h8! Is the screen on delay gonna be permanent? Or is it just a little niggle that will get fixed later on?
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Little niggle. I'm sure intervigil week squash that down the line. H8 said m7 has the same delay, maybe a touch faster.
[AT&T, Rogers HTC One X, Telstra One XL] vanja_z:
I have been getting poor mobile data since the 3.4 kernel, also on this build. Most people have been saying to toggle airplane mode and I do this perhaps 5 - 10 times a day when I have 0 bars reception and want to surf the net.

Yes, I've checked APN settings and they are fine.

I am on Optus Australia.

Wifi is fine.

LTE off performs slightly better.

Tried other radios to no effect, stock 10.2 clean flash currently.

EDIT:

I've also had more than one person say "I've been trying to call you all day" when my phones been on all day.
[AT&T, Rogers HTC One X, Telstra One XL] tacitapproval:
Bad news for me and a heads-up. My phone is bricked. This happened while running the 8/9 build and after a brick bug check declared my memory "sane."

It was not charging at the time, unlike some others. Computer sees it as QHSUSB_DLOAD like the others though.

Please let me know if there is anything I can do to help troubleshoot this.
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Been happening for months. Pre 3.4 also. Toggling airplane is only solution I know.
[AT&T, Rogers HTC One X, Telstra One XL] Skyfallkavu:
Just wonder, were you on the upgraded or downgraded touch firmware?
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
leave it on the charger for 30-40 minutes then power cycle.
[AT&T, Rogers HTC One X, Telstra One XL] tacitapproval:
Upgraded.

---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------

I wish it were that easy to revive, but alas... I have also tried holding power and volume down for forever, in case anyone is wondering this as well.
[AT&T, Rogers HTC One X, Telstra One XL] jcjcc:
I wish this problem received the same urgency as the eMMC brick bug did. It's not dangerous, but it also makes our phones unusable while we're running CM. That may sound like an exaggeration, but what's a smartphone that sometimes doesn't receive calls (and you don't even know!) and can't use cell data (toggling airplane mode takes a good 30 secs -- basically unusable for email or a quick google search).
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Pretty sure its only a data drop, so calls still work. Unfortunately, the logs don't seem to show anything useful (data just disappears) and Intervigil doesn't have the problem himself, so it hasn't been worked on. Some build prop edits helped me, but I generally leave my phone on 2g so I don't get the dropouts at all (they seem to happen in low signal areas when switching bands)
[AT&T, Rogers HTC One X, Telstra One XL] graemegb:
I think this is a hardware issue caused by the sim tray being loose. I used to have this problem and all I did was put a piece of electrical tape on the non-contact side of the sim card. I did this about a month ago and haven't had any drops since!
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
That helps a little (done the same trick) but I'd say 3-4 times a day I look at the phone when email goes quiet and lo and behold... Data is down. Airplane mode fixes it but this has been going on quite some time and is nothing new to the 3.4kernel or 10.2.

---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------

I drive an ever changing route for work every day (~200miles). I think it has to do with "handoffs" from tower to tower.
[AT&T, Rogers HTC One X, Telstra One XL] radjan:
Agree with venelar. Even after toggling, it still drops once I change cities, which is really annoying
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Happens in tower handoffs and band switches on the same tower. Does it sitting right on my desk in a very low signal area.
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
NOTE: I'm not asking for help. I know all the things to try. I have my old Atrix 4G to use in the mean time.

Bricked; shows up as Qualcomm HS-USB QDLoader 9008 (COM3) in Win 8.1 x64. I was running the 20130809 build from a completely clean install. I wiped everything including SDCard before installing. I had copied about 3GB of music to it yesterday at around 5pm. It was on the charger overnight. It wouldn't turn on this morning. I was on the upgraded TP version. I did that before flashing the 20130809 build. My eMMC version is MAG2GA. The Got Brickbug? app said that it was unknown. My bootloader looked like this:

*** UNLOCKED ***

EVITA PVT SHIP S-OFF RL

CID-11111111

HBOOT-2.14.0000

RADIO-0.24p.32.09.06

OpenDSP-v34.1.0.45.1219

eMMC-boot

Nov 26 2012,18:37:14:-1

If it's helpful, I also have a nandroid of 10.1 (probably 20130807 nightly) from right before I flashed 10.2 and a nandroid of 10.2 from right after flashing the ROM and installing all my apps.
[AT&T, Rogers HTC One X, Telstra One XL] Crappyvate:
Are you guys all in an LTE area ? I used to have the same issue and ever since I turned LTE off I don't experience the data drop anymore. I'm in an area with LTE but the signal is not solid and it seemed to happen every time the band switched from LTE to 3G.
[AT&T, Rogers HTC One X, Telstra One XL] vanja_z:
Thats the second brick since the fix. I seriously think it would be a good idea to put a large warning in the OP.

Before some cool guy jumps in, no the standard "thermonuclear war"/"I will laugh at you" warning is not sufficient since it is just a throwaway line that appears on every single ROM on this site be it a stable official release with minimal changes from stock or an alpha build known to cause bricks like this.

And for goodness sake please don't take this the wrong way , I just think we should be trying to help people who may not be aware of the real risks.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I think at this point, that sounds like a good idea. I hope nobody takes it in the wrong way either.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
I bricked last night. I woke up this morning and the screen wouldn't turn on and the LED was off. I'm using the 08092013 build with the upgraded tp.

The phone was simply on, no WiFi, no data, and no apps running out of ordinary

Any suggestions on what to do? (and i agree about changing the OP because some noob will brick and point fingers)
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
The first step is to hook it up to a computer and see what it shows up as. If it shows up as QHSUSB_DLOAD or Qualcomm HS-USB QDLoader, then it's properly bricked and you'll likely need to send it off for JTAG. Make sure you try holding the power button for a full minute also. That has worked for a couple people (not me).
[AT&T, Rogers HTC One X, Telstra One XL] mikel.canovas:
Those that bricked, did you have the emmc bug? I know it was fixed. Just asking
[AT&T, Rogers HTC One X, Telstra One XL] tacitapproval:
Sorry to hear about your two phones, but at least this confirms what happened to me. I am sending mine off to Mobiletechvideos for revival. Fingers crossed...
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
The Got Brickbug? app said my MAG2GA eMMC was unknown and therefore probably ok, if that's what you mean.
[AT&T, Rogers HTC One X, Telstra One XL] tacitapproval:
Mine was declared "sane," so caution with relying on this may be warranted.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Technically, wouldn't all of the one xl's return "Sane" in that emmc brick bug app? Did HTC change chips somewhere down the line or am I missing something here? I think the fact that these bricks are still occurring means this "Brick Bug" is not actually the problem. I agree with the recent posts in that a HUGE warning should be posted so that this does not happen as regularly as it has been.
[AT&T, Rogers HTC One X, Telstra One XL] angramenyu:
This deserves some major attention. People's phones are getting bricked here and on the 10.1. I think this threat should be closed, and a resolution one should be opened until devs find out what's going on.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Maybe not go that far. If people are aware of the risk, they should be allowed to flash the ROM. Also, I know there have been a few cases of bricks on 10.1 but I believe they're just the random ones that occur on this phone on any ROM.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yeah it might be one step too far. But you have to admit there has been a spate of bricks coming from this ROM (10.1 & 10.2) in the last little while, more than any other ROM by far.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Oh yeah, I can't ignore that, but if someone REALLY wants to flash it, I believe they should have the option to but I agree there should be proper warning.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
i tried holding it for a minute and it didn't work. its in DLOAD. and my phone was "sane"

the worst part of this is the replacement phone waiting: iPhone 4.....:crying:
[AT&T, Rogers HTC One X, Telstra One XL] jeffcojake:
Can anyone tell me how to turn off the the thing where it automatically locks after 10 seconds of not touching the phone? I have been looking in the settings for a while now...
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
settings/display/sleep

though if you read the posts above, you might not be so eager for it to go to sleep :crying:
[AT&T, Rogers HTC One X, Telstra One XL] jeffcojake:
I am not eager for it to go asleep. That is why I want it off. I am eager for it NOT to sleep every 10 seconds
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
That's still better than no replacement phone. Are you going to send if off for JTAG service? That's a lot cheaper than a new phone.
[AT&T, Rogers HTC One X, Telstra One XL] jcjcc:
Sometimes it goes into "Emergency Calls Only" with no service whatsoever. This might be 2 separate issues (#1 SIM card loose causes everything to drop, and #2 unrelated data-only drops). I just taped over the back of my SIM last night, we'll see how it goes.

Yes, that's exactly the same situation as mine. I have maybe 0-1 bars of LTE at home.
[AT&T, Rogers HTC One X, Telstra One XL] powduh09:
Hate to say it guys, but there must be some difference in hardware or something. I've been running the 8/9 build since it was uploaded just about, and I've let my phone die, sleep, all kinds of different scenarios, before charging and well read my signature...

Sent from my Nocturnal'd One X
[AT&T, Rogers HTC One X, Telstra One XL] JBLogic:
Completely agree, most people pay no attention to the little warning, because for the most part bad stuff doesn't happen. This ROM however has racked up a good kill count on devices. An extra noticeable warning should be in place. No disrespect to anyone. Id just hate to see more bricks. Good news is that business must be booming for mobiletechvideos lol.
[AT&T, Rogers HTC One X, Telstra One XL] James.ptrsn:
I've been posting in the 10.1 forum about getting bricked from upgrading from 8/10 to 8/12. I don't know if the issue is related, but if you need a test device for whatever fix you are trying to cook up I may be able to lend a hand.
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
what signature>?
[AT&T, Rogers HTC One X, Telstra One XL] powduh09:
Sorry, I'm on mobile. Thought my Sig would show. It says " sent from my Nocturnal'd One X"
[AT&T, Rogers HTC One X, Telstra One XL] utdps:
I'm loving how smooth this ROM is and how long the battery is lasting but I can't chance a brick so I'm going to switch back to something for a little while until this gets stable.