yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Mardread:
Works well for me

I have been reading up on this thread and the developer's thread since H8 introduced 10.2 for us. I installed the first build and have been updating each time that a new build is released with no issues at all. I can consider myself one of the lucky ones I guess. I did run that EMMC Bugcheck to make sure my phone was not affected and it was not. So I am glad for that. Though that was a missed opportunity for me to get a new phone ;).

I have no real feedback to give other than I have been using it non-stop as my daily since its release. I have had the battery completely drained and recharged; use Dreamz nightly, as its my alarm clock; and have flashed updates easily. If I had to complain about one issue, its that on the second build, my phone dropped my Google account information, which was weird. I did do a clean install with the 9th's release because of that.

Thank you H8 for your work, it is greatly appreciated.
[AT&T, Rogers HTC One X, Telstra One XL] rammx:
Steps to install??

Anybody have some steps to install this rom for beginners?

My HTC ONE X AT&T have:

Unlock bootloader

Rootered

Super CID

Original Kernel

AT&T RUU Installed
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Boot into the bootloader and tell me what it says there, just the first few lines.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] dubbz82:
may want to wait it out for new build to be posted, however, as ftrim will be disabled in new build, and should (in theory anyways) prevent bricking problems.
[AT&T, Rogers HTC One X, Telstra One XL] rammx:
Here my bootloader:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You're s-on so you need to flash the boot.img manually.

Extract the boot.img from the ROM zip and put it in your fastboot folder on your PC.

Copy ROM zip into your phone, do a backup of your current system in recovery, then do a full wipe (cache/dalvik cache/factory reset/system) in recovery, then install ROM in recovery.

Reboot to bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen, open a command prompt from within your fastboot folder, then issue this fastboot command:

fastboot flash boot boot.img

Reboot your phone.

Enjoy.

PS. as dubbz82 suggested, you might want to wait for the next build to be released.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] rammx:
Hey timmaaa, it's not necessary change the kernel for this rom?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No, the ROM has its own kernel.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] thewaronerror:
JTAG isn't a panacea

Regarding the posts on the thread in the dev forum about JTAG repairs for bricked phones. The Samsung eMMC "superbrick" was not always repairable with JTAG because the eMMC on chip data structures were damaged and could not be repaired. Maybe the devs should reach out the the guys involved in the original superbrick investigation to see if there's a way to tell whether the eMMC is corrupted in a way that implies it was superbricked, otherwise disabling FITRIM may simply be a red herring, especially since maybe people who are bricking are saying their eMMCs were not known to be vulnerable to the superbrick.

http://xdaforums.com/showthread.php?p=31466182#post31466182
[AT&T, Rogers HTC One X, Telstra One XL] Missingbullet69:
Fixed the phone! I'm on a Stock ATT rom and all is well, thus far. The next step for me is to get rooted, attempt to S-OFF and then put CM on for test.

Thank you lauterm for helping me with the driver issue and to timmaaa for guidance on the steps to get my phone back to working order.:good:
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
Thewaronerror, h8 is already considering that trim is not respondsible. He came to that conclusion at the beginning. The next build will test, if it still fails cm would appear to have some other problem that potentially is affecting more than just our devices. The brick count across numerous devices right now is high.
[AT&T, Rogers HTC One X, Telstra One XL] 'busa:
The One X I'm using has dead capacitive buttons. Does this ROM have an option to turn on the Nav Bar on the screen?
[AT&T, Rogers HTC One X, Telstra One XL] averylowiq:
Some time last night my phone got bricked :(

The phone had 20130809 installed and was plugged into the wall charger. This morning I noticed the notification LED blinking but the phone never came out of sleep and the LED stopped working as well. Plugging in the charger again or pressing and holding the power button has no effect. Windows is reporting it as a QHSUSB_DLOAD device now.

I guess I missed the 20130814 update by a few hours.
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
That's pretty unlucky, man. The new one has supposedly fixed that.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Well, maybe I'll give this a spin. My phone is on it's last leg anyways and I have damage protection. No one with bricks yet?

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] xxnatanxx:
Do I need to downgrade my touch panel so I'm not stuck in a boot loop like cm 10.1?
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
No

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] phishie:
When the nightly comes out in the next day or two what's the best procedure to updating from the 8/14 build? Do you need to clear cach/data, factory reset and re-flash?
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
I'd give it a go. I was holding out on flashing any 4.2/4.3 until s2w worked, but honestly this is too good to pass up. Super smooth and better battery life than 4.2.
[AT&T, Rogers HTC One X, Telstra One XL] JCon0320:
quick question, what's not working on the latest build/s? I'm holding out a bit until nightlies start. I just want a heads up. thanks

Sent from my sexy One XL:

hboot 2.14

s-off, post 3.18 ruu, AT&T

rooted, unlocked, twrp 2.6
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
If I'm not mistaken, everything is working. In currently on the latest and haven't found anything that doesn't work.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] phishie:
I think they're working on "weak reception" / "data connection dropping" but it's a minor inconvenience, the ROM is fantastic.
[AT&T, Rogers HTC One X, Telstra One XL] Avikar:
How to root 4.3

Just flashed 4.3 and its not rooted how to root it??
[AT&T, Rogers HTC One X, Telstra One XL] Protogon:
EDIT: I found a way to fix root. Just download this: http://download.clockworkmod.com/superuser/superuser.zip

Or scan this:

Flash the zip in recovery, set the internal Superuser manager to allow all requests. You should now have proper root access.

Anyone know of a solution for the root access problems? I set Superuser to automatically allow new requests and I still can't get root access for any apps.

u0_a43@android:/ $ su
java.lang.SecurityException: Permission Denial: broadcast asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS
at android.os.Parcel.readException(Parcel.java:1431)
at android.os.Parcel.readException(Parcel.java:1385)
at android.app.ActivityManagerProxy.broadcastIntent(ActivityManagerNative.java:2242)
at com.android.commands.am.Am.sendBroadcast(Am.java:739)
at com.android.commands.am.Am.onRun(Am.java:244)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:75)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
Permission Denied
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
Am I crazy because root has been working for me for 24 hours with no problems.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Root is fine. They likely don't have it enabled.
[AT&T, Rogers HTC One X, Telstra One XL] Protogon:
No.

In the embedded Superuser app, I had Superuser Access set to Apps and ADB, and Automatic Response set to Automatically allow new requests, and it still wouldn't work. It was only after flashing the latest Superuser zip that I got root access. This is with the 8/14 build.
[AT&T, Rogers HTC One X, Telstra One XL] Sillymon:
Hey guys, I haven't been keeping up with the flashing game for a while. I was on vacation for a bit and ever since I got back there's been the myriad of problems with the CM ROMs, so I'm still on a 4.2.2 CM from mid July. Might be a stupid question, but do I need to do a full wipe (like if I am going to a completely new ROM), or can I just wipe cache/dalvik and flash the 4.3 over the old 4.2.2?

Thanks in advance.
[AT&T, Rogers HTC One X, Telstra One XL] lostassassin:
does this rom have focal? and if it does does it work?
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
It has it, and it works... Sort of. It's buggy.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
Can't wait for the new build to drop . been looking forward to running this for a while to test it out
[AT&T, Rogers HTC One X, Telstra One XL] Avikar:
Didn't help. Still can't get titanium backup working.
[AT&T, Rogers HTC One X, Telstra One XL] vanja_z:
Another root issue, tab and arrow keys dont work in adb root shell for me. Is anyone else experiencing this?
[AT&T, Rogers HTC One X, Telstra One XL] Protogon:
Did you try to install any other superuser apps? SuperSU or Superuser by ChainsDD? You should remove those apps before flashing.
[AT&T, Rogers HTC One X, Telstra One XL] NguyenHuu:
Hey guys,

I cannot connect to wifi. All the other phones are connecting fine in the house so I'm not sure the issue. I tried to search first but the search function is temporary disabled.Can anyone help? I upgraded from CM 10.1 this morning to the 10.2 build posted in the OP. Thanks.

EDIT: Wifi is working now after about 3 hours. not sure why it took so long to connect. hopefully it stays connected.
[AT&T, Rogers HTC One X, Telstra One XL] rdifrango:
I saw that in the 10.2/4.3 thread that h8 said nightlies are now on for 10.2, but when I looked the stamp on the nightlies is listed as 10.1 like the following:

cm-10.1-20130818-NIGHTLY-evita.zip

Which one is it?
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
They'll start tomorrow/tonight.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] xxrzdxx:
I think he meant it had essentially been put in the hopper. And will show up when the next day's nighties are available.
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
Just flashed & noticed they rearranged the settings a bit. Anyone know how to enable the 3 button overflow menu now? I can't seem to find it :(
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
+1 I can't find it either.

Sent from my evita
[AT&T, Rogers HTC One X, Telstra One XL] RevolutionHeKz:
can i just flash the updated roms over each other? or do i have to wipe system and everything in recovery then flash it?
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
CyanogenMod 11.0 is a free, community built distribution of Android 4.4 (KitKat) which greatly extends the capabilities of your phone.

This is the official Nightly Build of CM11.0 for the AT&T HTC One XL.

To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!​

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Installation Instructions (These are all required)

S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).

Update to 3.18 RUU or later.

Flash a custom recovery (TWRP/CWM with SELinux capabilities).

Download latest nightly from http://download.cyanogenmod.org/?device=evita.

Locate 4.4 Gapps via a quick Google search.

Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).

Reboot into recovery and install nightly and gapps.

List all Questions and Off-Topic discussions here

Changelog

You can find the latest Changelog here

Github

Huge thanks:

intervigil, deck, and mdmower - Great team to work with for the HTC MSM8960 device family.
[AT&T, Rogers HTC One X, Telstra One XL] 903tex:
WOW!!!
[AT&T, Rogers HTC One X, Telstra One XL] rohan32:
Kernel is by default compiled with GCC 4.7... so if you believe that has a performance benefit, then sure :)

Also in general 4.3 has seemed a bit smoother to me on this and other devices, but that just may be a placebo :)
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Work-a-holics...all of you guys...can't believe y'all got this done so fast!
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
Awesome!!! thanks for this. I feel like having a nexus device :)
[AT&T, Rogers HTC One X, Telstra One XL] rohan32:
P.S. If i might just pop in and say, a big reason why this was so quick was due to the 3.4 kernel that its running now. Told you guys the wait would be worth it :D
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
Deleted. My mistake..
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Please refer to the "Known Issues".
[AT&T, Rogers HTC One X, Telstra One XL] Z1cK:
Oh...sorry for that..:what: lol
[AT&T, Rogers HTC One X, Telstra One XL] Chrysis:
Will definitely try this once the MMS fix is merged! Love how quickly we can get updates now, you guys are amazing.
[AT&T, Rogers HTC One X, Telstra One XL] mayhem85:
This might be a very dumb question.

Can I dirty flash this over cm10.1 latest nightly?
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
I'd recommend you make nandroid and flash it clean. There's still alot of activity happening upstream. For instance I can't seem to get Superuser to grant apps root access and the code review shows Koush made some changes to that just a few hours ago. You'll want the backup just in case you need to go back.
[AT&T, Rogers HTC One X, Telstra One XL] gamon92:
Good joob! i wait.
[AT&T, Rogers HTC One X, Telstra One XL] brandontaz2k2:
+1.

Will be flashing tomorrow when the MMS/SMS fix is implemented.

Thank you CM team for all of your hard work! Can't wait to try the latest version of Android.
[AT&T, Rogers HTC One X, Telstra One XL] powduh09:
Flashed this last night to test, and I'm impressed at how quickly this came together... Patiently waiting until this reaches official nightlies... Good things to come...

Sent from my One X using Xparent BlueTapatalk 2
[AT&T, Rogers HTC One X, Telstra One XL] gmadrigal:
the problem with the Bluetooth was resolved...?

or will be resolve at any moment... ?
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Read the OP.
[AT&T, Rogers HTC One X, Telstra One XL] Vanillalite:
Is it safe to assume in terms of the camera problems that the devs will try and implement the new CM Focal app?
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Precisely, that is exactly why the 3 month dead period between cm-10.1 nightlies happened. So we could fast-forward and get ahead instead of always playing catch-up.
[AT&T, Rogers HTC One X, Telstra One XL] josepr0218:
Im running the 7/31 build since first day and don't have any isues. I have a lot of apps installed and the rom is so smooth like first day i installed. I wipe everything and then install using twrp 2.3.0.0

---------- Post added at 09:21 PM ---------- Previous post was at 09:20 PM ----------

I dont think is the trim
[AT&T, Rogers HTC One X, Telstra One XL] ClassicalGas:
Just throwing a thought out there, has anyone bricked/not-bricked removed the red text from the splash screen?
[AT&T, Rogers HTC One X, Telstra One XL] dubbz82:
What about reverting to S-On after installing this CM build?
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Huh...over on the Ville, a lot of folks just run a firmware.zip to install the required JB firmware and hboot without needing S-OFF or RUU.
[AT&T, Rogers HTC One X, Telstra One XL] pside15:
We can run JB on the Evita without needing s-off or running a RUU just not the newer 3.4 kernel. Something with the 3.4 kernel doesn't jive right on the Evita unless you run the newest RUU or happened to take that update OTA. Having s-off makes it easier to run the RUU so that's why it's recommended to obtain s-off first.
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
I have not bricked and I removed the red splash screen. I'm also s-off, 3.18 RUU, TWRP 2.6.0.0 and upgraded touchscreen. I saw random reboots early on with the 3.4 kernel (10.1) but they've mostly subsided. I can't recall the last one on 10.1 and haven't RR on 10.2. Currently I've gone back to 10.1 just to get the camera for an upcoming trip but 10.2 worked perfectly fine for me save for the known issues.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
I think it's the same situation, it's just flashing only the firmware seems safer and doesn't require S-OFF. The 3.4 kernel has some "unknown" firmware dependencies, so you extract the firmware.zip from the RUU and flash in fastboot. CM with 3.4 kernels just looks for hboot version at install to assure you should be at the correct firmware revision level.
[AT&T, Rogers HTC One X, Telstra One XL] pside15:
It's apparently different on the Ville. We don't have "firmware" to flash as far as I know. Unless you are just talking about flashing something to update the hboot. There's something in the 3.18 RUU for the Evita, other than the hboot update, that our phone needs to run the newer AOSP ROMs with the 3.4 kernel.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
The RUU should contain a firmware.zip that has updates for all the firmware partitions, including, most likely, the "something". Just a thought about the S-OFF and I'll bug on back to my own device thread.
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
Not true. It's just easier. When I came up from stock and went through all the steps to get super CID, unlock the bootloader, and s-off, I had to flash cm10.1 (with the 3.4 kernel) and fastboot boot.img before I could get s-off, because I needed to enable su for adb. It ran fine. You just need it if you don't want to manually flash the kernel (every day).
[AT&T, Rogers HTC One X, Telstra One XL] JBLogic:
I did not remove the red text and I bricked.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You are the exception to the rule though. Most people who hadn't upgraded to 3.18 couldn't get 3.4 kernels to boot.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
I guess I should have mentioned that I was coming from the stock 3.18 OTA/RUU. Sorry if that created any confusion.

But yes, those who did not do the RUU would have definitely had trouble.
[AT&T, Rogers HTC One X, Telstra One XL] josepr0218:
Im running perfectly and i don't RUU 3.18 complete firmware i only flash the 3.18 hboot in adb and then flash cm10.2
[AT&T, Rogers HTC One X, Telstra One XL] juicejuice:
IMHO the real problem in all this is that Qualcomm doesn't make available the tools to work with a chipset in QHSUSB_DLOAD mode. In theory these hard bricks should be recoverable by just downloading a new partition map and hboot+recovery image to the device.

I'm sure back at HTC they can just plug any device into a special box which forces QHSUSB_DLOAD mode regardless then resets the device to factory stock. Sigh.
[AT&T, Rogers HTC One X, Telstra One XL] fuybjeans:
Unfortunately, my phone just bricked as well. I followed all the steps on the OP, (RUU'd and all). Running ROM as-is, no tweaking, just installed a few apps. The ROM was running perfectly for 4 days without even a reboot. I was in my car with about 70% battery, charging, google mapping and streaming music...phone got really hot by the back camera and completely shut down.

Could have been the phone itself, I have no way of knowing. Phone has a lot of use. I re-Rom at least once a week, constantly streaming something (gym, work, car) and it's been dropped a few times.

The only things that leads me to believe it MIGHT be the ROM is because in 10.1, I twice had similar situation where the phone over-heated and went into a DEEP sleep. I thought it was bricked, however, I was able to bring it back to life by pressing/holding buttons for LONG periods of time. This time it is completely gone.

Whether it's the phone or the ROM, I take full responsibility. As much as I screw around with the phone, I surprised it took THIS long to brick it! :)

Anyway, I read other posts about bricks, and bricking is pretty serious, that's why I posted this. h8rift is my favorite dev and IF it is the ROM (again, I have no idea if it is) he'll figure it out. Unfortunately, I have to leave, the cheaply made Nexus 4 was my cheapest option to get me through until my contract it over in March.
[AT&T, Rogers HTC One X, Telstra One XL] JBLogic:
Does it show as QHSUSB_DLOAD in device manager?
[AT&T, Rogers HTC One X, Telstra One XL] jcjcc:
regarding intervigil's revert of "enable standalone power collapse" -- it seems that standalone power collapse was also disabled (a while ago!) on mako/nexus 4 because of similar issues:

https://android.googlesource.com/device/lge/mako/+/546e578579b678178095c95af8ba99b20894f86e

of course, mako has a different SOC, but "failure to wake on suspend" sounds like it might fix the sleep/charging death issue (which has happened to me 4-5 times today...)

I don't know if that patch will remedy the bricks for those who are on 10.2 though -- sorry! It would be wise for everyone to stay on 10.1 until this is ironed out.
[AT&T, Rogers HTC One X, Telstra One XL] fuybjeans:
No
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
That's basically what I said. I plan on releasing a build (hopefully today. im trying to vet it for other issues first) that contains that commit revert and we'll see.

Thanks, and sorry guys, I'm trying to figure out what i can do to keep this from happening.....but I have to agree that Qualcomm's proprietary revival tools should be public to fix these problems. Samsung d2 and jf users run into the same thing. if it bricks, it bricks. The Exynos are the only ones that allow the jig trick to get into download mode to Odin back to something else.
[AT&T, Rogers HTC One X, Telstra One XL] OwenRW:
I have this problem on CM10.1. If the battery gets too low (<2%) and either I turn off the device or the device powers itself off it won't power back on. When you plug it into a charger the charging lights blinks a couple of times and goes off.

Trying to power the device back on, nothing happens, holding the power button down I can 'reboot' the phone (i.e. the soft buttons flash and it 'restarts').

Plugging this into my Windows machine, the phone appears as an inaccessible removable drive. OSX doesn't acknowledge there is a device there (nothing listed in the attached USB devices).

The only way I have found to get the phone working again is to leave it on charge for a couple of hours, remove the SIM and 'restart' the phone a couple of times. (No idea why removing the SIM helps, but it does for me)

This is on an HTC One XL originally from T-Mobile UK now used on T-Mobile USA.
[AT&T, Rogers HTC One X, Telstra One XL] vaggolena:
I was looking at that phone too last night, or something cheaper, but even that right now is not feasible. My coworker will try to jtag it, but most likely I will try sending it in for a professional jtag. It is $50, and with very high reviews.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
does this point to official nighties possibly coming soon?

http://review.cyanogenmod.org/#/q/evita,n,z
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Users that are bricked in QSHSUSB_DLOAD mode from CyanogenMod 10.2, please go to IRC to channel #cyanogenmod-evita so we can gather information on this. The more of you and quicker we can get folks to get in there and provide information, the better.

you can use webchat.freenode.net if you do not have an IRC client. Please use your XDA handle as your nick so we can know who is who.

Thank you,

-h8