yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
I just wanted to throw some ideas out there. Don't know how relevant this could be, but to those who's phones have bricked, 1) what version of recovery were you using? 2) did you have daydream enabled?

I've noticed that a lot of the bricks happened after flashing an update (though not immediately after), so I'm wondering if perhaps there's an issue with a certain version of recovery that is causing something to not get flashed properly. And to the other point, if deep sleep had something to do with it, daydream should prevent the phone from going into deep sleep (although I've seen on previous phones that charging the phone, even with the screen off, prevents deep sleep). Just a thought.

This is all making me a bit nervous. I'm on the 8/10 nightly of 10.1, and thankfully, I haven't had any issues, but now bricks are starting to pop up on 10.1 too.
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
Ohh I thought it was supposed to say something else . I thought that ROM hadn't been updated for like 6 months or so
[AT&T, Rogers HTC One X, Telstra One XL] powduh09:
Doesn't mean there isn't a plan for updating or work going on behind the scenes. Just wait... Patience is a virtue...
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
bricked last night..

It is real everyone, i was on the 0809 build.
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
Everyone, the apparent (and I'm willing to say apparent with the rash of issues we're seeing) fix for the brick bug was included in the 8/10 Nightly. If you're still running something older I'd say you're putting yourself doubly at risk.

Edit: I'm stupid, thought this was the 10.1 thread for second.
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
i was on 08092013 Build which is the latest.

8/10 does not exist.
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
0809 is the latest 10.2 build w/the fix.

I don't think it made it into a 10.1 build till the 10th though and that may have been what you were thinking about
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
It was what I was thinking about, sorry about that, shouldn't be replying at 7am before any coffee haha.

You guys are right, I need to pay attention to what thread I'm in, carry on.
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Happens to the all of us. With 5 cm threads going between the q&a and Corys old unofficial, it can catch ya sleeping for sure.
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
Was it plugged in charging overnight like most of the rest of us? Someone suggested the other day that people turn off their phones while they charge overnight. You'll more than likely have to send it off for JTAG, but it can't hurt to try the debrick thread first: http://xdaforums.com/showthread.php?t=1966850. It didn't work for me, but it might for you.

---------- Post added at 08:00 AM ---------- Previous post was at 07:44 AM ----------

I've never messed with daydream. It should have been set to whatever the default was. I was on TWRP 2.6.0. I bricked about 36 hours after flashing. That likely corresponds with the first time my phone would have tried to run trim per http://www.engadget.com/2013/07/30/android-4-3-supports-trim-improves-performance-on-nexus-devices/: "It also looks like Jelly Bean invokes TRIM maintenance once within a 24-hour window (after one hour of inactivity), and only if the battery is 80% full (30% when charging)."
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
It was charging and the battery was at like 90% when i put it on. Debrick thread didnt help.

It's under warranty so its getting sent back. I have been on 4.3 since H8 posted the first release and the app that checks your chipset said i was "sane".
[AT&T, Rogers HTC One X, Telstra One XL] tacitapproval:
Mine was not charging at the time, but it had been idle for some time in my pocket when I tried to wake it up, and discovered it was bricked. So, it could have been running trim. I was also on TWRP 2.6 and had been running cm10.2 for about a day. No daydream.
[AT&T, Rogers HTC One X, Telstra One XL] Koizuma:
So far for me on the last build running perfectly stable and no brick. The only thing I have seen was data dropped out once while I was in Houston under LTE.
[AT&T, Rogers HTC One X, Telstra One XL] angramenyu:
I still don't know why you guys are flashing this if you know the risk. I did flashed it the very first day this ROM came out, but only for a few hours because camera doesn't work. Just testing what's new and everything. I was lucky.

I do not have the easiness of getting a good replacement phone, so after learning about the bricks I stopped thinking about flashing until a REAL fix is in place. I suggest you guys do the same if you care for your HOX, like I do.
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
It's not as if they kept flashing the build they knew was bricking phones, they flashed the one they thought had the fix. Can't blame them for that...
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
While it is risky, it's their choice to flash this ROM if they want to, and who are you to tell them otherwise? You don't have the right. It's all part of the freedom of unlocking your Android device.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] dubbz82:
that and some are willing to accept this risk because they are under warranty, or have another device and are using the HOX as a spare device. Also no good way to find the real cause of the bricking if no one's using it, and thus no one will be able to fix it correctly. Someone has to take that risk.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
No i'll send it to AT&T..the phone doesn't turn on nor does the LED, so i gave up and decided to let AT&T send me another in 2 days.

I'm on TWRP 2.6 and daydream is never used on my phone

Its a little difficult going to this post often since i'm always used to accessing it through my phone :smiling:
[AT&T, Rogers HTC One X, Telstra One XL] angramenyu:
Wait, child. I'm not telling anyone not to flash it. I'm suggesting to those who don't have a warrant or the money to buy a replacement phone, like myself, to just wait for a fix.

Calm down. If you want to flash it and use it as your daily drive, go ahead.
[AT&T, Rogers HTC One X, Telstra One XL] zoltrix:
hahaha i love how you can not ever say anything other than "Good job everyone" on this website because anything that is not 100% positive is considered a wasteful comment and extremely rude
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Firstly, don't call me a child, I'm far from it. Secondly, you were suggesting that they don't flash the ROM, it's there in black and white. Like I said, it's their choice, let them do what they want to do with their own devices.

Sent from my Evita

---------- Post added at 03:25 AM ---------- Previous post was at 03:20 AM ----------

By the way, I haven't flashed this ROM, and won't be. My point wasn't to defend the ROM, because there's clearly something going on.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Can we take this elsewhere please...before the forum police show up
[AT&T, Rogers HTC One X, Telstra One XL] James.ptrsn:
Out of curiosity, if you're sending it to AT&T, how does that work with the warranty? Are you still in the year warranty period? Are you going to pay for a new phone, repairs, etc.? Does it matter that it died as highly customized as I'm sure it is?
[AT&T, Rogers HTC One X, Telstra One XL] dubbz82:
iirc, these bricks are likely caused from a hardware fault of some nature in the first place -- usually at&t won't bother to look into it very far, especially if the phone is just a dead weight, although there is a chance of being shot down and denied warranty because of rooting/s-off/etc, and it is mentioned, and you DO agree to it if you use HTC's unlocking service (with or without a spoofed cid).
[AT&T, Rogers HTC One X, Telstra One XL] kotchishm:
FWIW they did no checks when I took my HOX with a dead screen in. They gave me a replacement and didn't care. I was s-off, rooted, etc.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
yeah still in the one year warranty...Besides, once the phone's battery is dead, I don't think there is a chance of AT&T bothering to look beyond the point of "this sucka is dead, poor SOB...next!"

don't they send it to the OEM to fix it though? otherwise how would they have so many refurbs?
[AT&T, Rogers HTC One X, Telstra One XL] Pro75357:
reboot with logs

Ok so I just had a freeze in the middle of listening to music (via play music) using bluetooth audio. I thought it was going to brick, but luckily she came back, but it was weird. I held power so it would reboot, and it did. It took a lot longer to get past the bright white screen with red text and when the CM boot logo came it was spinning very slowly, reminding me of the reboots that I had on 10.1 (where it was slow as hell until another reboot) so I went ahead and started holding the power button again.

Right before it restarted the home screen flashed in to view- it was back to the original wallpaper and for some reason and said "SafeMode" in the bottom corner. before I could react it rebooted and came back normally- except the wallpaper is still the original.

I was at the gym, so I couldn't get logs immediately, but I just got them (~30 mins delayed). See attached.

I really hope this helps shed some light on what might be causing the brick issues, but I'm not betting on it.

Running the 8/9 10.2 nightly after a full wipe since the 9th.

Since I'm posting... Other than some minor wifi as well as LTE data outages and bluetooth skipping issues the is the first real bug I've encountered on cm 10.2. Battery life has been a MAJOR improvement for me on 4.3, and it is truly faster with more butter.
[AT&T, Rogers HTC One X, Telstra One XL] angramenyu:
See? This. You have to warn other people of the issue. It's not a matter of people wanting to flash this or not.

---------- Post added at 12:48 AM ---------- Previous post was at 12:44 AM ----------

Of course I was suggesting to people that can't afford to buy another smartphone not to flash it until a proper fix is in place! What is going on with u? It's a suggestion not an order. People can do whatever they want with their phones. You may not be a child but you keep acting like one.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
/Bickering.

Chill everyone. Please and thank you.

A few posts back the TRIM feature was mentioned. I think this needs to be looked into further.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
It would make sense, with the CM10.1 bricks being caused mostly by LagFix which did just that.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
I'm going to remove the download. We are having a very large discussion right now. It is not only our devices....there are many in CM that have started bricking with this update.

More to come.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Also, if everyone can't simmer down and quit bickering, I will lock this thread. I'm continually getting messages from users complaining about the bickering going on here. That stops directly after I finish this post.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Oh, and we just fixed camera too.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
http://review.cyanogenmod.org/#/c/47827/ was just merged. This completely disables fitrim. I will build it into a build in a bit (hopefully tonight, maybe tomorrow) and put this up with a huge red warning telling people to beware~~!

Seriously though, new insight from a lead in CM explained that trim runs at 80% or higher battery when idle (off the charger) and 30% or lower (on the charger) when idle. This is why alot of you "woke up" and found your devices wouldn't turn on. Or that you had a full charge, pulled it out of your pocket and it magically was bricked (greater than 80%, off charger and idle). It appears the amount of time it needed to be idle in those battery conditions was no less than 71 minutes (there's a math calculation in there...).

We have completely disabled FITRIM (the #if CONFIG_ENABLE_FITRIM does not exist, therefore its skipped over) so trim won't even run. We are coming up on the timeframe very quickly that nightlies for 10.2 will begin. I will have a build out for you to test out and if i stop seeing bricks, we'll go to nightlies (yay!). If i continue seeing bricks, the whole CM team (every maintainer and lead) will likely be in a giant discussion on what is happening.

In the meantime, people with bricks, go work with Zarboz and/or mobiletechvideos and have your phones unbricked. Zarboz is nice enough to work with you for a very low cost / free. But since mobiletechvideos charges something like $50 for a jtag, PLEASE donate if you work with Zarboz. Thank him for spending the $150-$200 on a riffbox and diligently working on phones for low cost / free just because you are a member of XDA. You can't beat that and I applaud him and plan on donating heavily to him shortly.

Thanks, and if you have any questions regarding the FITRIM disable, please join #cyanogenmod-evita (not for 10 seconds, get an IRC client and hang out dang it :) ) on Freenode and talk with your fellow evita owners and i'm on fairly often.

-h8rift
[AT&T, Rogers HTC One X, Telstra One XL] qiwu:
How to fix camera? how to hack the liboemcamera.so?
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
for the FITRIM, is that also what the other 10.2 unofficial builds are doing?

and awesome job with camera! hopefully Zarboz can help unbrick me
[AT&T, Rogers HTC One X, Telstra One XL] ethantarheels123:
Yea, ftrim is a built in feature in 4.3 and sort of emulates what lagfix does. Remember when people were getting bricks with lagfix on 10.1? I guess the cm team is trying and seeing if disabling the ftrim in 4.3 will fix the bricks.
[AT&T, Rogers HTC One X, Telstra One XL] Vanillalite:
Probably a stupid thought and/or already done, but I had a thought.

Has anyone cross referenced the bricks with AOKP to see if running that is also gonna give bricks seeing as the latest version of AOKP is based on the 3.4 kernel?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I haven't seen any bricks coming from AOKP so far. Same with Carbon. Not sure about RB.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ttcrew:
Rootbox isn't 4.3 based (yet) - therefore no bricks from Trim...
[AT&T, Rogers HTC One X, Telstra One XL] ccb101:
they were taking about the 3.4 kernel possibly being the issue
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Like the guy said above me, we're talking about the 3.4 kernel, not Android 4.3.

The bricks that happened on cm10.1 with the 3.4 kernel were caused by trim, via the lagfix app. So we're possibly looking at a 3.4/trim issue as opposed to an Android 4.3/trim issue.

We saw it less on cm10.1 because it was only happening to users who elected to use the lagfix app. As opposed to it being built into Android 4.3, which is why we're seeing it so much on this ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
I have seen no discussion of lagfix on the ville forum in reference to bricks. Are we sure it's a 100% correlation?
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Pretty sure. Many people reported it and we came to that conclusion a month or so ago.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
I will have a new build up when i get off work today (~8 hours from now). I'll let that run for about a few days - a week. If i hear no more bricks, I'll start nightlies for evita.

Those who are paranoid, if/when this makes it to nightlies, thats your cue that its "okay to flash" and not to worry. The others that will do what i do and run the next build on their evita anyways, thank you and we'll prove that we've fixed the problem and get this bad boy on nightlies!
[AT&T, Rogers HTC One X, Telstra One XL] fzurita:
I bricked on CM10.1 with 3.4 kernel on ville without ever using the lagfix.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
I'm not saying that people ONLY bricked with Lagfix, just many did.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Well, I was trying to say if there's not a 100% correlation, it's still probably pretty dangerous to flash unless you have a backup phone. I think this confirms my suspicion.
[AT&T, Rogers HTC One X, Telstra One XL] ThaSik1:
Correlation ≠ Causation my good sir, even if it is 100% (I'm a Psych Grad.). But I do agree that anyone who doesn't have a back up or isn't rolling in the moneys should stray away until the nightlies get the green light. Thanks H8/other devs for keeping my Gf's OneX relevant when HTC stopped working on it altogether! Hopefully the new build proves you guys are right and I can quit hearing bickering about an update from my old lady to the latest/greatest :p Thanks to all those who have tested so far as well and reported back to help get things worked out!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
HTC haven't stopped working on it altogether. Their updates do come very late, which is a great source of frustration, but if insider chatter is right we'll have an official update soon.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
You just made my point. There does not seem to be a direct causal or correlation relationship between fstrim and 10.1 bricks, but I will leave it at that and wait for the official nightlies to begin.
[AT&T, Rogers HTC One X, Telstra One XL] thewierdone:
AOKP bricks

I have been on AOKP ever since milestone 2. no lag and no bricks/random reboots and no overheating. I don't think its the 3.4 kernel. Maybe its just trim. Again I have been on cm10.1 ever since nightlys and never had any problems. I have flashed so many AOSP roms in the past week that if I were to have had a brick I wouldn't even be surprised.:eek:
[AT&T, Rogers HTC One X, Telstra One XL] rammx:
Link

Where is the Link to download 10.2 for HTC ONE X (at&t)?
[AT&T, Rogers HTC One X, Telstra One XL] nbunn:
There is not currently a good build. Wait until the next build is posted.
[AT&T, Rogers HTC One X, Telstra One XL] rammx:
Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] mikelebz:
AOKP milestone 2 is 3.4 kernel. Check the about phone settings.
[AT&T, Rogers HTC One X, Telstra One XL] pside15:
I think he was saying that he doesn't think it's the 3.4 kernel causing the bricks, not that the ROM wasn't using the 3.4 kernel.
[AT&T, Rogers HTC One X, Telstra One XL] mikelebz:
Ahhh sorry for the confusion
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
I will flash it for sure !! Thanks bro.
[AT&T, Rogers HTC One X, Telstra One XL] thewierdone:
its cool I should have stated myself better soorrry:D
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
Man, I'm inpatient about the incoming update. !!!:D
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
New build is up! 20130814. Enjoy and please report back over the next few days to see if this is ready to go to nightlies or not.
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
Link is broken..
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
derp.

fixed!
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
FYI, if your dock has a phone icon and you touch it and it says "app not installed", its just the shortcut has changed in the move to 4.3.

Fling the phone icon by long pressing it, toss it away, then go to the app drawer and drag the phone app back to your dock. just FYI.
[AT&T, Rogers HTC One X, Telstra One XL] gibosn6594:
Ha, get ready for a ton of "why doesn't my phone icon work" posts.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
It was posted on CyanogenMod's G+ post today, as it is a google-wide upgrade "kink". even happened with OTAs for nexus devices from google
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Lol. you guys are beating my server up :).
[AT&T, Rogers HTC One X, Telstra One XL] Nike1984:
Still seems to be broken for me.(http://h8.pwnz.org/downloads/cm-10.2-20130814-UNOFFICIAL-evita.zip) :(
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
I'm going to post a mirror on dev-host. should be ready in a few minutes and i'll post the mirror in the OP.

EDIT: Mirror is up!
[AT&T, Rogers HTC One X, Telstra One XL] dustinhayes93:
Everyone must be blownin this up. Can't get it to download. Great work h8 :D
[AT&T, Rogers HTC One X, Telstra One XL] Skyfallkavu:
Sorry, I think there may be a button mapping bug. I cant seem to get my button remap changes to keep. It always defaults back to opening the recent applications menu. If needed ill post a logcat, but this seems minor enough.

edit: i should mention, I was trying to remap my home button long press to opening the contextual menu.
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Seeing the same thing.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
Same here. Also, how do I enable the 3 dot menu?

Seems I answered my own question. Disable custom actions and the 3 dot menu shows up. Enable it and it's gone. Wtf?
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
I have no problem with remaped button
[AT&T, Rogers HTC One X, Telstra One XL] wagaf:
Great job h8, and the ROM profits from the 10.2 / 4.3 buzz at the right time to have many testers ! :good:

I was wondering if the TRIM bug was found or is it gonna be kept disabled ?

Thanks a lot anyway, will make a donation for sure.
[AT&T, Rogers HTC One X, Telstra One XL] ZeRo2o9:
glad issue is fixed now i can try the rom out
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Will be watching this for the next day or so before I go ahead and try it out. Can't risk the possibility of it self-bricking.
[AT&T, Rogers HTC One X, Telstra One XL] vanja_z:
Great news and a big thank you to H8 for all his hard work but just a reminder for everyone jumping on this build.

Brick reports started to trickle in 36 hours after the first 'fixed' build was posted. Since this build has only been up for a matter of hours it is by no means confirmed to not cause bricks as of right now. When it hopefully gets to a few days with no new brick reports _then_ it should be safe to run but at this stage you are all brick testers.
[AT&T, Rogers HTC One X, Telstra One XL] jabman13:
So what are the chances if I am s-off touchscreen downgraded 2.14 twrp 2.6 that I will brick my phone by flashing the newest build?
[AT&T, Rogers HTC One X, Telstra One XL] Skyfallkavu:
We're pretty sure its fixed, but you should probably upgrade your touchscreen to be safe anyway.

no promises though.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Yes, EVERYONE UPGRADE YOUR TP FIRMWARE!!!

That way we are all on the same page in the event that the bricks return and we need diagnostic info.

There is no set probability if you will brick or not. As Vanja_Z said, everyone who is hopping into this most recent build are brick-testers. And I applaud you guys for being the guinea pigs as I, myself do not have the balls to risk it. Kudos to everyone trying this out and of course kudos to H8 for being so patient and understanding throughout all of this :)
[AT&T, Rogers HTC One X, Telstra One XL] FSB:
I upgraded my TP firmware, loaded the ROM, was nice and smooth.

I could not get Titanium to recognize root, so have gone back to another ROM, I need all my backups.

Could note find Developer Options

Added - Did as suggested below now running like a dream
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Not placebo, fortunately. OpenGL ES 3.0 is also applied to the entire UI, not just when you launch graphics intensive games/videos. Device feels like it has so much butter now i want to rub it on some toast. :good:
[AT&T, Rogers HTC One X, Telstra One XL] rohan32:
Ah, I didn't know it is used throughout the UI as well. Very neat.

Someone might have to hire Paula Deen back so that she can use all the butter in 4.3.
[AT&T, Rogers HTC One X, Telstra One XL] brandontaz2k2:
Refreshing for MMS/SMS fix build, excited!!
[AT&T, Rogers HTC One X, Telstra One XL] phatboypat:
If we did she'd probably make us all wear aunt jemima outfits.
[AT&T, Rogers HTC One X, Telstra One XL] brandontaz2k2:
Lol. *patiently waits for 729 build*