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

Search This thread
By:
Advanced…
N

ndpete

Member
Jun 7, 2011
9
16
Utah
Just thought I'd mention when I updated to the latest nightly I went into a bootloop as well. It looped about three times and then I held power button to try to boot to recovery or bootloader the CyanogenMod boot animation started up. Everything appears to fine now.

Updated with cyandiff which I just started playing with. Not sure if that has anything to do with it.

*EDIT: I tried a reboot and got stuck in the bootloop again. This time i couldn't get it to boot. Finally booted into recovery and dirty flash the last nightly again and it is working. I'm assuming this was an issue with cyandiff...

Sent from my One X using xda app-developers app
 
Last edited:
B

boomn

Senior Member
Feb 2, 2011
275
83
I just ran in to the long press hardware key bug after about a day and a half since I installed and booted the ROM. I got a copy of last_kmsg if it might be of any help with this

To add more detail: the long press action was activating immediately after a quick tap of a button. It did not appear to be thinking the button was stuck down or still pressed
 
Last edited:
T

tucanj

Member
Sep 11, 2012
30
4
Had a cool idea, what if the same way there is a quick pull down for settings (by pulling down on one side), you could pull down the multitasking shade from the other side? Just a thought. Running very smooth.
 
h8rift

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
tucanj said:
Had a cool idea, what if the same way there is a quick pull down for settings (by pulling down on one side), you could pull down the multitasking shade from the other side? Just a thought. Running very smooth.
Click to expand...
Click to collapse

tucanj, thats already there :).

go to Settings -> system -> Quick settings panel -> Quick Pulldown (set to left, right or off.)

It sets the left or right 1/5 of the screen as a quick panel pulldown.
 
P

philippe.bureau

Member
Aug 28, 2012
28
3
notification sound when downloading from play store

Hi,

does anyone else has this weird issue?

When I download from play store on mobile data or wifi, the notification sound keeps beeping until the download is finished.

I have the same issue with Navigation. every time data is downloaded for map update, the notification sounds is heard. It pretty much beeps all the time except when I am waiting at a red light.

If I set to vibrate the phone keeps vibrating as well.

Thanks
 
PUfelix85

PUfelix85

Senior Member
Jul 4, 2012
95
16
Osaka, Japan
Google Pixel 3
h8rift said:
Pre-requisites:
  • ADB setup and minor knowledge on how to use it. (See here if you do not have such knowledge)
  • Have an open command prompt or terminal window.

How to obtain a last_kmsg (helpful for catching kernel issues from last kernel boot-up such as bootloops)
Code: 
adb shell
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
exit
exit
adb pull /sdcard/last_kmsg.txt
Click to expand...
Click to collapse

Can this be done from the phone? Or do I need to do this just after the failed boot? Also if I restore and reboot will that over write the kmsg that I am looking for? Sorry for the dumb questions just looking to get you a kmsg to help solve my boot issue on the most recent nightly.

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

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
PUfelix85 said:
Can this be done from the phone? Or do I need to do this just after the failed boot? Also if I restore and reboot will that over write the kmsg that I am looking for? Sorry for the dumb questions just looking to get you a kmsg to help solve my boot issue on the most recent nightly.

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

you can do it from the phone but its much more of a hassle. last_kmsg is the kernel log from the last time kernel booted. make sure that the last kernel that was booted was the one that bootlooped.
 
B

bball606

Member
Feb 15, 2011
36
1
I'm also having the bootlooping issue. Wiped cache/dalvik and system, flashed 2/24 nightly and gapps, and doesn't get past splash. I tried flashing the boot.img in fastboot as well even though I'm s-off with no luck. Reverted to previous nightly now.

Hboot 1.14, S-Off, Rev B

I've attached my last_kmsg.txt from the bootloop. Hopefully it helps.
 

Attachments

  • last_kmsg.txt
    67.9 KB · Views: 9
h8rift

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
That kmsg is from a stock Sense ROM on Jellybean.

Its a 3.4 kernel and has /system write protection on in the last_kmsg.
 
B

bball606

Member
Feb 15, 2011
36
1
h8rift said:
That kmsg is from a stock Sense ROM on Jellybean.

Its a 3.4 kernel and has /system write protection on in the last_kmsg.
Click to expand...
Click to collapse

Hmm, I've never ran a Jellybean Sense ROM. I was on 2.20 firmware when I began flashing, and I've never flashed a Sense custom ROM. This was the correct last_kmsg as I pulled it from /proc in recovery right after bootloop. :confused:

I was however running the linaro kernel from this thread on the previous nightly: http://xdaforums.com/showthread.php?t=2068732, but even after flashing the rom and boot.img from the 2/24 nightly it bootlooped.
 
h8rift

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
bball606 said:
Hmm, I've never ran a Jellybean Sense ROM. I was on 2.20 firmware when I began flashing, and I've never flashed a Sense custom ROM. This was the correct last_kmsg as I pulled it from /proc in recovery right after bootloop. :confused:

I was however running the linaro kernel from this thread on the previous nightly: http://xdaforums.com/showthread.php?t=2068732, but even after flashing the rom and boot.img from the 2/24 nightly it bootlooped.
Click to expand...
Click to collapse

Must have been recovery then. new TWRP is built off of JB 3.4 kernel.

Try flashing rom, bootlooping, then go to hboot (not recovery) and flash a CM boot.img from a nightly or two ago via fastboot...then grab last_kmsg. I keep forgetting that recovery boots a kernel of its own...
 
PUfelix85

PUfelix85

Senior Member
Jul 4, 2012
95
16
Osaka, Japan
Google Pixel 3
h8rift,

I am trying to get the kmsg to you but it is huge and I cannot find a good method. and suggestions?

---------- Post added at 02:46 PM ---------- Previous post was at 02:38 PM ----------

PM sent. Thanks for your help.

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

doubleblack

Member
Dec 17, 2011
42
10
Hi h8,

For those of us on newer H-boot, would you be able to post a notification when we need to flash boot.img since we need to do this in fastboot? I think this may be cause of some (if not most) of the problems with boot loop...I am not having problems but am about to flash boot.img via fastboot so I remain kosher, but thought I'd mention this for future kernel changes.

Thanks!
 
h8rift

h8rift

Inactive Recognized Developer
Jun 29, 2010
1,875
9,760
doubleblack said:
Hi h8,

For those of us on newer H-boot, would you be able to post a notification when we need to flash boot.img since we need to do this in fastboot? I think this may be cause of some (if not most) of the problems with boot loop...I am not having problems but am about to flash boot.img via fastboot so I remain kosher, but thought I'd mention this for future kernel changes.

Thanks!
Click to expand...
Click to collapse

Well, we're always updating kernel. Best method for you to do is to flash it. If it bootloops, automatically go and fastboot flash the boot.img. Then begin further troubleshooting from there.
 
GuyIncognito721

GuyIncognito721

Senior Member
Mar 1, 2011
424
226
Oswego
doubleblack said:
Hi h8,

For those of us on newer H-boot, would you be able to post a notification when we need to flash boot.img since we need to do this in fastboot? I think this may be cause of some (if not most) of the problems with boot loop...I am not having problems but am about to flash boot.img via fastboot so I remain kosher, but thought I'd mention this for future kernel changes.

Thanks!
Click to expand...
Click to collapse

It would be easiest just to s-off and not worry about it.

Sent from my cm_tenderloin using xda app-developers app
 
  • Like
Reactions: edditnyc
D

doubleblack

Member
Dec 17, 2011
42
10
h8rift said:
Well, we're always updating kernel. Best method for you to do is to flash it. If it bootloops, automatically go and fastboot flash the boot.img. Then begin further troubleshooting from there.
Click to expand...
Click to collapse
Well, I understand...just giving an idea. Not everyone is having a problem, like I am having no boot loop problems after update via cyandelta - but after reading all the issues I decided I should be kosher in order to be proper tester in future. What if I have a problem 2 weeks from now and report an issue no one can reproduce and everyone thinks I'm crazy and it's all because I'm running an old kernel from 2 weeks ago? I understand your opinion, not trying to change it, just trying to give a second opinion to possibly ease future troubles.
 
B

bball606

Member
Feb 15, 2011
36
1
h8rift said:
Must have been recovery then. new TWRP is built off of JB 3.4 kernel.

Try flashing rom, bootlooping, then go to hboot (not recovery) and flash a CM boot.img from a nightly or two ago via fastboot...then grab last_kmsg. I keep forgetting that recovery boots a kernel of its own...
Click to expand...
Click to collapse

Yeah, I pulled it from recovery, my bad. Here's the one I pulled after bootlooping using latest nightly and then flashing boot.img from 2/22 nightly, which successfully booted.
https://www.dropbox.com/s/tqf4rcy9t8xjhjb/last_kmsg.txt
 
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