[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL

Search This thread
By:
Advanced…
gravewormx

gravewormx

Senior Member
Oct 15, 2009
268
57
Los Angeles
Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL

llamas612 said:
I have TitatniumBackup, but i don't use it for restoring my apps because the free version doesn't allow for the automatic installation of apps. You literally have to sit and hit install on every app.

And i know i know, the solution is just to buy the program, I guess i'm just super cheap in that regard.
Click to expand...
Click to collapse

Or you could always try ROM Toolbox Pro, it usually goes on sale and it does a bunch of other stuff :)

Sent from my One X using Tapatalk 2
 
  • Like
Reactions: AbstractMind87
L

llamas612

Member
Sep 17, 2012
28
2
uToTMeH8 said:
I managed to grab Go Backup before they made a paid version of the app and butchered it. Flash this in recovery. It will batch backup/restore apps & data, sms, mms, launcher layout, wifi passwords and more. Press the back button when the splash screen about the paid version pops up.
Click to expand...
Click to collapse

Wow, thanks a lot. I'll have to give that a try later.
 
blacklistedcard

blacklistedcard

Senior Member
Dec 30, 2010
885
174
Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL

Has anyone figured out how to get the camera working when the command line fix and the factory flash does not work?

Sent from my One X using xda app-developers app
 
ken bentley

ken bentley

Senior Member
Nov 2, 2011
221
34
Tasmania
For those people experiencing battery drain,I just checked cpu states on on demand the phone was never going into deep sleep, changed to powersave and now I am getting deepsleep.
Ok maybe I have missed something power save does not stick reverts back to on demand.
 
Last edited:
X

xetrev

Senior Member
Jul 30, 2010
225
39
[ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL

ken bentley said:
For those people experiencing battery drain,I just checked cpu states on on demand the phone was never going into deep sleep, changed to powersave and now I am getting deepsleep.
Ok maybe I have missed something power save does not stick reverts back to on demand.
Click to expand...
Click to collapse

I just wrote off the battery drain as a defect.

Messing with the performance tabbed caused all kinds of other issues for me.

I reflashed after wiping /system, with no luck
 
exad

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
I tried flashing this from viper 3.1. Reflashed stock kernel, Wiped system cache and dalvik and did a factory reset. Checksum matches and yet I keep freezing up at HTC screen. Anyone know what I'm missing here?? I'm at a loss.
 
K

kcchen

Senior Member
Mar 7, 2005
450
43
exad said:
I tried flashing this from viper 3.1. Reflashed stock kernel, Wiped system cache and dalvik and did a factory reset. Checksum matches and yet I keep freezing up at HTC screen. Anyone know what I'm missing here?? I'm at a loss.
Click to expand...
Click to collapse

Funny thing, I had the same experiences last night upgrading from the viper 3.1 ROM also. I was "stuck" at the HTC screen with no way of getting into the bootloader... I know your horror.

My remedy was to use adb to get into the bootloader {adb reboot-bootloader). From there I was able to use fastboot to flash the stock recovery, factory data reset whjich reformat and preps the sd card. Onve this was done, use TWRP to mount the phone as a USB drive and transfer the CM10.1 ROM. The followed the normal process to finish flashing through TWRP.

There is a great video from Team Nocturnal that walks through the process and provides the recovery images. I'll update the thread with links, but they can be found on yhr HOX forum.

Hope this helps.
 
exad

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
kcchen said:
Funny thing, I had the same experiences last night upgrading from the viper 3.1 ROM also. I was "stuck" at the HTC screen with no way of getting into the bootloader... I know your horror.

My remedy was to use adb to get into the bootloader {adb reboot-bootloader). From there I was able to use fastboot to flash the stock recovery, factory data reset whjich reformat and preps the sd card. Onve this was done, use TWRP to mount the phone as a USB drive and transfer the CM10.1 ROM. The followed the normal process to finish flashing through TWRP.

There is a great video from Team Nocturnal that walks through the process and provides the recovery images. I'll update the thread with links, but they can be found on yhr HOX forum.

Hope this helps.
Click to expand...
Click to collapse

I'm able to get into recovery by holding down power and volume down. tried reflashing, no change I will try flashing stock rom first I guess and reflashing twrp. See what happens. Thanks for the info.
 
subarudroid

subarudroid

Senior Member
Jun 18, 2011
1,545
677
SL,UT
Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL

exad said:
I tried flashing this from viper 3.1. Reflashed stock kernel, Wiped system cache and dalvik and did a factory reset. Checksum matches and yet I keep freezing up at HTC screen. Anyone know what I'm missing here?? I'm at a loss.
Click to expand...
Click to collapse

Reflashed stock kernel? :confused: or the boot.img from this rom?

Sent from my HOX w/CM10.1 :)
 
buradd

buradd

Senior Member
Apr 9, 2011
365
44
Orange, CA
Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL

Has anyone else had complaints about multiple texts being sent from just one message? I sent one text today and my friend got blown up 5 times exactly with the same message

Sent from my One X using xda premium
 
J

johnwayne007

Senior Member
Nov 25, 2008
336
209
127.0.0.1
Samsung Galaxy S22 Ultra
subarudroid said:
Reflashed stock kernel? :confused: or the boot.img from this rom?

Sent from my HOX w/CM10.1 :)
Click to expand...
Click to collapse

So just to see if i could also replicate this problem, i was using Viper Rom 3.1 and elementalx kernel (2.1), wiped all the partitions in twrp and installed CM10.1, and i can confirm that this happens. I then using fastboot flashed the boot.img out of the rom zip (CM10.1) and now instead of rebooting it just sits at the white ONE screen when the phone turns on. I reflashed the rom and gapps and still had the same non-boot issue. I restored my NAND backup and Viper booted just fine. Kinda weird...
 
Last edited:
Saenzscene

Saenzscene

Senior Member
Jun 30, 2011
379
78
El Paso
Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL

buradd said:
Has anyone else had complaints about multiple texts being sent from just one message? I sent one text today and my friend got blown up 5 times exactly with the same message

Sent from my One X using xda premium
Click to expand...
Click to collapse

Yeah I do. People say I text them twice.
 
Vanillalite

Vanillalite

Senior Member
Sep 14, 2010
157
26
Biggest text issue I have is it seems like i can't send pics to multiple recipients at once. Yet if I just send the pic individually to each person it goes through,
 
rdxhd

rdxhd

Senior Member
Jun 14, 2012
231
35
This might sound pretty dumb but I wonder if others have the same issue. I've been having issues with multitasking/ram and I wonder if I loaded something wrong. I cleared all my apps and had about 220 MB free. I loaded browser, google translate, tapatalk without any reloading but as soon as I load new app all my other apps start to reload. I had not notice this before in other AOSP ROMs so that's why I am asking. I think the ROM is amazing so I am inclined to think that is something I did wrong. Thanks!

**EDIT: I found my issue. I have an app that was being cached and using a ton of memory and was pushing other apps out. Sorry for question.
 
Last edited:
exad

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
johnwayne007 said:
So just to see if i could also replicate this problem, i was using Viper Rom 3.1 and elementalx kernel (2.1), wiped all the partitions in twrp and installed CM10.1, and i can confirm that this happens. I then using fastboot flashed the boot.img out of the rom zip (CM10.1) and now instead of rebooting it just sits at the white ONE screen when the phone turns on. I reflashed the rom and gapps and still had the same non-boot issue. I restored my NAND backup and Viper booted just fine. Kinda weird...
Click to expand...
Click to collapse

Yessir. I messed things up even more now and can't mount sd -_- about to flash stock recovery then reflash twrp. Should get things going.. then reflash this rom.. all should work after I think.. Will post with whatever happens..
On a side note I wish there was a download of just stock recoveries as downloading RUUs takes FOREVER -_-
 
Last edited:
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
Scott
  • Locked
[ROM][12/13/13] - CleanROM 7.0R2 -★| Android 4.2.2! | Sense 5! | Clean! | Stable! |★-
Replies
12K
Views
2M
Scott
Scott
Turge
  • Poll
[ROM][SEP 22] Team Venom ViperXL 4.2.0 | Sense 5 | Venom Tweaks | OTA Updates
Replies
19K
Views
2M
T
Tmobilefan906
h8rift
CyanogenMod 11.0 for AT&T HTC One XL - evita
Replies
2K
Views
447K
jrior001
jrior001
kennethpenn
  • Locked
[ROOT] One Click HTC One X (AT&T/Rogers/Others) (Win/Mac/Linux)
Replies
870
Views
773K
orangekid
orangekid

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 188
    h8rift
    h8rift
    CyanogenMod 10 is a free, community built distribution of Android 4.2.2 (Jelly Bean) which greatly extends the capabilities of your phone.

    This is the official Nightly Build of CM10.1 for the AT&T HTC One X / 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
    3. Flash a custom recovery (TWRP/CWM)
    4. Download latest Nightly
    5. Download and flash GAPPS

    Nightlies return! Keep an eye on http://get.cm/?device=evita

    List all Questions and Off-Topic discussions here

    Changelog

    Huge thanks:
    intervigil, xkonni, toastcfh, deck and rohan32 - Great team to work with for the HTC MSM8960 device family.
    View
    98
    h8rift
    h8rift
    TonyStark said:
    @h8rift please check PM

    Thread has been cleaned out. While I realize Development has slowed, I have created an OT thread in the General section HERE For all to decompress ;)


    Lets try to stick with CM talk here.

    Thank you
    Click to expand...
    Click to collapse

    Thanks Tony, and sorry for the very late reply to your PM. You did what I would have asked :).

    Development is still going on for this device, but we're trying to work on m7 (HTC One) and this family and get them merged so they always stay up to date with eachother. Its a fun, but daunting task...so please bear with me :). Once we get this kernel cleaned up it *does* have working HDMI and no refresh lines too. So basically, it will be near perfect and solid for this device. Just need some time as alot of us have had work stuff, personal stuff, (and myself) medical stuff going on.

    We still love our S4 8960 devices, so they aren't forgotten :). We're learning alot about things we can fix here from what we are learning about the m7, so its a great experience for us and for you, the user. So kick back and relax and I will definitely put a noticable post up when nightlies return to normal and we move on to the other kernel which drops the lib that got us DMCA'ed.

    Thanks everyone,
    -h8
    View
    89
    h8rift
    h8rift
    I believe everyone is correct and a status update is required at this point. This was my first CM device to maintain and I have a deep love and respect for it.

    We just merged up our 3.4 stuff to CyanogenMod and each of the four devices in the family have a few leftover issues before we start nightlies again.

    Here's the scoop on our phone on 3.4 at this moment:

    All features work except:
    *720p/1080p video
    *random reboots
    *increased battery drain over 3.0 kernel as it is not optimized or has a stale process chewing battery. Its nothing catastrophic, but noticeable.

    Issue-by-issue:
    #1: this is broken on all four devices at the moment and as all of you remember from cm9, cm10, cm-10.1 w/3.0 kernel....we do camera last. Stability first, features second, polish third.

    #2 I bricked my Evita while fixing this issue so it could be released in an alpha status to you all. Luckily, XsMagical has been very very kind and offered to donate me a new motherboard ($150) to revive my device. It should be in the mail coming my way on Monday. We believe we found the fix, I just need to validate.

    #3 this issue will be addressed after reboots and camera are up. Hell it could be the camera or reboots causing it. That's why we polish last.

    **Sidenote: in 6-8 months I will most likely get whatever new htc device is out there and maintain it too if its on at&t. Why? Because our 4 (now 6) man squad are all CM has for HTC development officially. Period. There's nearly 10 people on the GS3 and GS4 series of phones just by themselves. No one wants or loves htc devices more than us so damn right I will do my hardest to maintain as much and as many as I can. Every new device I encounter the mire I learn how to fix up the others. We figured out HDMI out for this device by working on the HTC One, for example. We are also looking at merging kernels so that yes, thus device will be continually carried through new versions of android as well as the newer devices.

    Some Evita users moved to the HTC One already and I was already there having their back. I would feel more appreciative that you get an easy-going, hard working person like me to give up all this time to work on devices knowing dang well that if you upgrade to another AT&T HTC device, you can expect me along with it. I feel I am dependable and actually listen to complaints, kudos, and feedback and respond appropriately, while other developers might not really care to respond to anything. My PM box fills up daily with questions and queries about how to build android from source for random devices like Huawei, or older devices like the HTC Flyer tablet. I literally work 45 hours a week at work, then put in another 5 hours minimum every night (or 10-15 on weekends). If you have been wondering what I have done with my 25 hours on android this week it has been trying to find a way to un-brick my Evita before that motherboard arrives so I can get to work this weekend. Rohan has been helping out a lot since my device died but he is very busy at the moment.

    Last but not least. As soon as I can confirm the random reboots every 5-10 minutes are gone and it is a stable phone (I'm talking voice and data, because phone call availability is #1 priority...I mean...its a phone for crying out loud...), I will be blowing this thread up with test builds to see if we catch other bugs.

    But I would rather see you on a stable build from March than an unstable build today and something happens to a family member and you don't get the phone call. Or maybe you get hurt badly and your phone reboots in mid-dial.

    That's what I think about. That's why there are no test builds yet. Be patient, I want to see everyone excited again once this is released again. Lord knows I could use a few hours break by having all the devices on nightlies so I can work out bugs!

    Sorry for the length, but that's what's on my mind after I read the last few posts so I wanted you to know *everything* that is going on.

    Thanks,
    -h8





    Sent from my One using xda app-developers app
    View
    81
    h8rift
    h8rift
    Little update for you guys, the remaining issues are almost done for the 3.4 kernel. the permanent black screen unless USB is plugged in is gone now. We are now dealing with a screen on / off delay of a half a second and getting camera working again :).

    Sit tight, eat some popcorn, you will enjoy the update when its available (then nightlies will start up again shortly after, bc we wont need the file that got us DMCA'ed). This also sets us up for quick updates to the next version of android since we're mostly CAF, with minor HTC bits needed to run the vendor-specific hardware.
    View
    77
    h8rift
    h8rift
    Desertman123 said:
    H8 is never late, nor is he early. He arrives precisely when he means to.

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

    We're making major headway on our 3.4 kernel. No tearing and such, super smooth. Only problem right now is Camera, screen on/off delay, and if you dont have a USB cable plugged in, after about 10-15 seconds, the screen will not turn back on until you plug a usb cable back in. Otherwise its pretty much fully CAF code :).

    Sorry haven't been around, we took a break for about a week, we'll still waiting on our vendor repo to come back. That break did us well, we're making major progress now.

    There is no "giving up", its just "how long will it take". We are going to miss M3 but are trying to be ready for cm-10.1 stable. We'll just have to see.

    Thanks guys!
    -h8rift
    View

New posts