CyanogenMod 11.0 for AT&T HTC One XL - evita

Search This thread
By:
Advanced…
h8rift

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
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+!​
Code: 
#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)
  1. S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
  2. Update to 3.18 RUU or later.
  3. Flash a custom recovery (TWRP/CWM with SELinux capabilities).
  4. Download latest nightly from http://download.cyanogenmod.org/?device=evita.
  5. Locate 4.4 Gapps via a quick Google search.
  6. Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
  7. Reboot into recovery and install nightly and gapps.

List all Questions and Off-Topic discussions here

Changelog

Huge thanks:
intervigil, deck, and mdmower - Great team to work with for the HTC MSM8960 device family.
 
Last edited:
  • Like
Reactions: allthingsdroid, sanimagus, androm3da and 151 others
jrior001

jrior001

Senior Member
Aug 12, 2010
3,200
8,681
Va Beach
Work-a-holics...all of you guys...can't believe y'all got this done so fast!

Sent from my HTC One X using Tapatalk 2
 
Chrysis

Chrysis

Senior Member
Jun 18, 2012
150
11
Reno, NV
Will definitely try this once the MMS fix is merged! Love how quickly we can get updates now, you guys are amazing.

Sent from my S-Off, turbo injected AT&T HTC One X (evita), running AOKP 4.2.2 & using XDA Premium
 
mayhem85

mayhem85

Senior Member
Jul 26, 2012
185
51
This might be a very dumb question.

Can I dirty flash this over cm10.1 latest nightly?

Sent from my One X using xda app-developers app
 
edditnyc

edditnyc

Senior Member
Jun 29, 2012
638
296
New York
www.eddit.net
mayhem85 said:
This might be a very dumb question.

Can I dirty flash this over cm10.1 latest nightly?

Sent from my One X using xda app-developers app
Click to expand...
Click to collapse

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.
 
B

brandontaz2k2

Senior Member
Jul 30, 2012
78
10
Chrysis said:
Will definitely try this once the MMS fix is merged! Love how quickly we can get updates now, you guys are amazing.

Sent from my S-Off, turbo injected AT&T HTC One X (evita), running AOKP 4.2.2 & using XDA Premium
Click to expand...
Click to collapse

+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.
 
powduh09

powduh09

Senior Member
Feb 17, 2011
1,270
704
Dallas, NC
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
 
Vanillalite

Vanillalite

Senior Member
Sep 14, 2010
157
26
Is it safe to assume in terms of the camera problems that the devs will try and implement the new CM Focal app?

Sent from my One X using xda app-developers app
 
h8rift

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
rohan32 said:
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
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: JayDream, For1n, Silellak and 12 others
You must log in or register to reply here.

Similar threads

h8rift
[ROM][4.1.2] CyanogenMod 10 for HTC One XL
Replies
8K
Views
2M
exad
exad
h8rift
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
Replies
4K
Views
773K
TonyStark R.I.P.
TonyStark R.I.P.
kennethpenn
  • Locked
[ROOT] One Click HTC One X (AT&T/Rogers/Others) (Win/Mac/Linux)
Replies
870
Views
773K
orangekid
orangekid
grankin01
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Replies
1K
Views
596K
liquidx
liquidx
B
  • Sticky
[S-Off] Facepalm S-Off for HTC One XL
Replies
1K
Views
327K
M
mtz.1372

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 154
    h8rift
    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+!​
    Code: 
    #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)
    1. S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
    2. Update to 3.18 RUU or later.
    3. Flash a custom recovery (TWRP/CWM with SELinux capabilities).
    4. Download latest nightly from http://download.cyanogenmod.org/?device=evita.
    5. Locate 4.4 Gapps via a quick Google search.
    6. Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
    7. Reboot into recovery and install nightly and gapps.

    List all Questions and Off-Topic discussions here

    Changelog

    Huge thanks:
    intervigil, deck, and mdmower - Great team to work with for the HTC MSM8960 device family.
    View
    54
    h8rift
    h8rift
    New build up.

    No im not having issues, just wanted to try to get Bluetooth fixed before releasing the next build....but for now it only has the SMS/MMS fix in it.

    the HTC One is pretty much done so focus is going back to this family again. I've been rolling my face on the keyboard trying to get bluetooth to work. I'm still working on it.

    Thanks,
    -h8
    View
    51
    h8rift
    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
    View
    50
    h8rift
    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
    View
    48
    h8rift
    h8rift
    ..
    View

New posts