yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] mr.5106411:
Hey guys. I have a problem. Whenever I flash any ROM that is 4.3 based I get a "unable to flash error" in red in TWRP. I'm guessing this is because of the firmware as I have read elsewhere. But I want to be sure and that is the purpose of this post. Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What hboot are you on? And what TWRP version are you using?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] mr.5106411:
Thanks for the quick response. I am on hboot 1.09.0000. And I am on version 2.3.3.0 of TWRP.
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Yeah you need some upgrade before your ready for this. Instruction in the op will guide you. S-off, ruu to 3.18 and then you should be ready. There's a detailed guide in the first few pages of the cm 10.1 q&a thread that will help also.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok, you need to RUU up to 3.18 before you can flash this. You need to get s-off first though.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
As of yet that is the best advice I've seen. A good old power down seems to calm the issues for a while.
[AT&T, Rogers HTC One X, Telstra One XL] greategress:
"Just turn it off and back on." You make me feel like my parents asking for tech support. :laugh:

Thanks for reply!
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Totally agree! but for real there a reason that the first thing on the script at tech support. We really shouldn't have to do that all to often but it seems to work in this case.
[AT&T, Rogers HTC One X, Telstra One XL] waktasz:
I have the same issue with the play store not connecting. Also Pandora. Random reboots and freezes have started to crop up more and more since the 9/25 nightly.

I'm running the nightly from yesterday right now and it fixed the play store issues right away, but on my drive to work the phone rebooted itself a few times and since then Play is now not working again.
[AT&T, Rogers HTC One X, Telstra One XL] mr.5106411:
Thanks for the reply/help guys. Going to be doing the RUU as I am already S-OFF not a complete n00b lol.
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
Please also remember to upgrade to TWRP 2.6.X.

You can flash firmware 2.15 from the command line (instead of RUU) if you're on a non-Windows machine.
[AT&T, Rogers HTC One X, Telstra One XL] ethantarheels123:
the buttons settings in settings force closes on the newest nightly, coming from a completely clean flash, so I would hold off on 10/2 build if you want to remap your multitasking button.
[AT&T, Rogers HTC One X, Telstra One XL] tacitapproval:
This is true, but my previously remapped buttons continue to operate correctly. So, not a big problem for me.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Fix has already been committed for tomorrow.
[AT&T, Rogers HTC One X, Telstra One XL] 53l3c7a:
Anyone else's audio completely borked? Notifications, ringtones and alarms work. MP3 or Play Music won't play back anything.
[AT&T, Rogers HTC One X, Telstra One XL] d3thstalker:
Re-download, wike dalvik/cache, and re-flash. I had the same problem and a re-flash fixed it.
[AT&T, Rogers HTC One X, Telstra One XL] buradd:
has the delay been fixed yet when you press the unlock button and the screen takes a second or two to turn on?
[AT&T, Rogers HTC One X, Telstra One XL] 53l3c7a:
Hmmm... I dirty flashed the same .zip I had handy... No love. I'll re-download once I get home to my WiFi.
[AT&T, Rogers HTC One X, Telstra One XL] d3thstalker:
Delay time has been significantly reduced, at least for me. but it's not instantaneous as you expect.
[AT&T, Rogers HTC One X, Telstra One XL] 53l3c7a:
Headphones work... No speaker, though. Better than nothing.
[AT&T, Rogers HTC One X, Telstra One XL] G4 Man2:
Is wired tethering still not working?
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Correct, still not working
[AT&T, Rogers HTC One X, Telstra One XL] zoltrix:
So what was the last stable version? I've read nothing About but problems the past few weeks :'(
[AT&T, Rogers HTC One X, Telstra One XL] velvel:
Hm, sometimes I ask myself if we are all downloading the same files ;) Except stupid SMS when new voicemail is created from _@, things are running fine with 04/10 and 24/09 before that. I also find it is better to use shut down/power up than restart, as sometimes restart will result in freeze.
[AT&T, Rogers HTC One X, Telstra One XL] manup456:
20131003 works perfect for me very stable.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
boots up fine? i was thinking about porting PA 3.99 from the m7 to our device, so I'm trying to figure out if i should wait it out for some fixes to be merged or to go ahead anyway

S-OFF

Boot Unlocked (TAKE THAT AT&T!)

TWRP 2.6.3.0

Running something that will probably change in a day....
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Just a suggestion, cuz i never ported nothing, you'll likely have more success working from the evo 4g version. Porting works better coming from the same family.

Evo 4g pa3.99:

http://xdaforums.com/showthread.php?p=43830503
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
yup. just finished. i used the m7, but since i didn't have the device with me (long story), i'll need some EXTREMELY brave beta testers. The OP should be up either in an hour, or tomorrow
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
Unfortunately the biggest bane of my life. Really want this to work.

Anybody know how we can help fix this - pulling logcat just shows "Unable to switch on/off usb tethering".
[AT&T, Rogers HTC One X, Telstra One XL] dedon4christ5:
Hello Great Work!

Hello,

Please I want to flash the Nightly Build of CM10.2 on my HTC ONE XL, below is my phone's details, will it work ?

***UNLOCKED***

EVITA PVT SHIP S-OFF RL

CID - 1111111

HBOOT - 2.14.0000

RADIO - 0.24p.32.09.06

OpenDSP- v34.1.0.45.1219

eMMC - boot

Nov 26 2013 18:37:14:12895

My Phone Software information

Android version: 4.1.1

HTC Sence: 4+

Software Number

3.18.502.6 71ORD

HTC SDK API level

4.63

Build Number: 3.18.502.6

Please let me know if it will work, so i can flash it ASAP. and do you have any screen shot ?

await your response.

thanks.
[AT&T, Rogers HTC One X, Telstra One XL] philippe.bureau:
no reason not to work

I do not see why it would not work. Do you already have costom recovery like TWRP installed?
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
hey thanks for the suggestion - this ROM has been extremely stable and smooth for me. Probably will stick to it for quite some time.
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
When I tried this ROM a few days ago it rebooted the cm logo before first initial boot and lagged like crazy only the start-up screen. I want able to turn the screen off or get any touch responds on startup I have no idea why! I had to hard reboot into bootloader.. Anyone know whats up? Hboot 2.15 on TWRP 2.6.0.0

Edit: it was also a clean install wiped system, data, dalvik cache and cache
[AT&T, Rogers HTC One X, Telstra One XL] vang2k:
Usually when that happens I go back into my recovery and than use TWRP go advanced clean and clear out the cache/dalvik. Sometimes when you hold the power button the hard restart the phone it comes back on and boots faster.
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Cheers. Does everything respond after that? Never had such an issue till I flashed firmware 2.15
[AT&T, Rogers HTC One X, Telstra One XL] dedon4christ5:
Thanks for the response

Yes, I already have the TWRP installed, so please tell me what to do next
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Just install the ROM and appropriate gapps in recovery. Make sure you do a full wipe first.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] zoltrix:
Just curious as to why you dont use the wireless tether?
[AT&T, Rogers HTC One X, Telstra One XL] philippe.bureau:
just flash

as mentionned by others, do a full wipe of your phone, download the CM build you want, download appropriate google apps (Gapps) and install from recovery. Make sure to wipe all caches.

Regarding the CM build, you can chose between stable or nightlies. I am running nightlies and I am experiencing the following issues :

- Sometime upon reboot, the phone is frozen at unlock screen. you need to force a reboot by holding power button for about 10 sec.

- sometime after nightly upgrade, the application optimization is very slow. force a reboot same as first point.

- On phone calls with wired headset, the mic on the headset is not working, you need to speak on the mic on the phone.

- Wired headset button is not working during calls or while listening to music

- Sometime lose mobile signal for few seconds and it come back on its own.

Hope this helps
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
Power consumption and wireless interference. I have actually been told several times in clients offices to turn off my hotspot since it is interfering with theirs.

Usb tethering has been an extremely efficient way for me to work on the go.
[AT&T, Rogers HTC One X, Telstra One XL] mchun:
So I went all the way back to the 09/13 build and still having issues. The only temporary fix that I've found is wiping all the caches, data, android secure, and system. Then re-flashing everything but after an hour it's broken again. I'm going to see if running the RUU will fix it.

logcat https://www.dropbox.com/s/um6zr27uukekxj8/logcatnoaudio.txt

update:RUU failed too. It was stuck on "checking" for 45 min before I stopped it.
[AT&T, Rogers HTC One X, Telstra One XL] antennae:
Does anybody know anything regarding the random reboots/boot lockups that were introduced back around 9/19 or so? As far as I can tell they still occur (they do on my 9-28 install, haven't upgraded as it seems this is still a problem in October builds)...

Looking at the commits, the 3.4.62 kernel was pulled in on 9/19. Is this the culprit? I unpacked my 9/17 boot.img and kernel version is 3.4.60.

My last_kmsg doesn't show much, the kernel messages right before a boot lockup relate to loading USB drivers, but this may be meaningless. There is no mention of kernel panic.

[ 2.784709] [USB] enabling adb: adbd(parent:init): tgid=140
[ 2.784770] [USB] android_switch_function: android_switch_function: 131, before 129
[ 2.784892] [USB] android_switch_function: # mtp
[ 2.784922] [USB] android_switch_function: # adb
[ 2.784953] [USB] android_switch_function: # mass_storage
[ 2.784983] [USB] android_switch_function: android_switch_function: vendor_id=0xbb4, product_id=0xdfa
[ 2.785014] [USB] android_bind_enabled_functions: android_bind_enabled_functions bind name: mtp
[ 2.785045] init: no such service 'rmt_storage'
[ 2.785045] [USB] mtp_bind_config
[ 2.785075] ===========interface_id 0 mtp
[ 2.785197] [USB] android_bind_enabled_functions: android_bind_enabled_functions bind name: adb
[ 2.785228] adb_bind_config
[ 2.785228] ===========interface_id 1 adb
[ 2.785319] [USB] android_bind_enabled_functions: android_bind_enabled_functions bind name: mass_storage
[ 2.785350] ===========interface_id 2 mass_storage
[ 2.786540] [BATT][OC] start, BOOT_2_ONMODE_THRES_MV=3550
[ 2.786723] [BATT][OC] waiting for driver state ready
[ 2.786845] [BATT][OC] driver state =0
[ 2.790752] [DK] start, BOOT_UP_VOLTAGE=3550
[ 2.791301] [DK] Start PowerKey detection...[ 16.126995] Restarting system with command 'oem-88'.
[ 16.127147] [K] Restarting Linux version 3.4.10-g240d4d5 (root@abm030) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Dec 3 19:54:09 CST 2012
[ 16.127147]

Here's a question, why does my kmsg show Linux version 3.4.10?

Anyways, just trying to get some conversation going since I haven't seen any troubleshooting on these issues since they started happening. I realize the devs are probably busy on newer devices.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
My device has behaved since the 2nd of October, after a few commits about power and frequency.
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Best guess u booted to recovery and then rebooted and grabbed the logs...last_kmsg shows results from your last boot attempt, whether it was ROM or recovery. Recovery kernel is an older 3.4.10 kernel.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
Anyone got an October build rinning?
[AT&T, Rogers HTC One X, Telstra One XL] antennae:
Sure, makes sense. I didn't think it booted into recovery after locking up but who knows. Thanks for pointing that out.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
So I'm using the 10/9 nightly and everything has been working good all day until I for home then the phone went into a boot loop. I got the phone into recovery and then wiped cache and dev cache and then it stopped. Can anyone give me an explanation as to why this happened? I haven't installed anything or altered anything in the ROM at all
[AT&T, Rogers HTC One X, Telstra One XL] anawong:
Similar as what i have before.

I am not using 10/9 nightly, but i tried different nightly after 9/19 and have similar random boot when home, and the phone is in boot-loop/hang there.

I also mentioned that in the Q&A thread

http://xdaforums.com/showpost.php?p=46242258&postcount=531
[AT&T, Rogers HTC One X, Telstra One XL] kjablonski:
I am running the 10-1 nightly of 10.2 and have been running into this issue since running CM10.1, say july ish. When I have my hotspot on, my phone will random reboot and get stuck on the CM logo. I then have to long press the power button until it reboots, then it will get stuck on my lock screen. One more longpress of the power button will get everything back to normal. I have attached my last_kmsg log and can provide more logs if requested. I'm not sure what to grep for in the logcat to look for the hotspot info.
[AT&T, Rogers HTC One X, Telstra One XL] antennae:
Okay, so I upgraded to 10/09 thinking the random boot/boot loop/boot lockup issue may have been solved...but just watched my phone reboot while it was sitting on my desk, get to the lock screen, and then completely lock up. After holding power to reboot I was able to get it all the way up again and pulled last_kmsg. As some had surmised before, there is definitely a problem with bringing the second core up. First I see:

[ 42.667450] CPU1: failed to boot: -38

and then the following repeats every ~150 milliseconds until I hold the power to force reboot:

[ 43.186113] _cpu_up: attempt to bring up CPU 1 failed
[ 43.191728] ------------[ cut here ]------------
[ 43.195727] WARNING: at /opt/jenkins/android/workspace/android/jellybean/kernel/htc/msm8960/arch/arm/mach-msm/acpuclock-krait.c:998 acpuclk_cpu_callback+0xac/0xf0()
[ 43.210468] Modules linked in: prima_wlan(C)
[ 43.214649] [<c00141b4>] (unwind_backtrace+0x0/0xe0) from [<c0077020>] (warn_slowpath_common+0x4c/0x64)
[ 43.224141] [<c0077020>] (warn_slowpath_common+0x4c/0x64) from [<c0077050>] (warn_slowpath_null+0x18/0x1c)
[ 43.233786] [<c0077050>] (warn_slowpath_null+0x18/0x1c) from [<c071af1c>] (acpuclk_cpu_callback+0xac/0xf0)
[ 43.243430] [<c071af1c>] (acpuclk_cpu_callback+0xac/0xf0) from [<c0730d7c>] (notifier_call_chain+0x5c/0x9c)
[ 43.253380] [<c0730d7c>] (notifier_call_chain+0x5c/0x9c) from [<c0078f64>] (__cpu_notify+0x28/0x40)
[ 43.262871] [<c0078f64>] (__cpu_notify+0x28/0x40) from [<c071b81c>] (_cpu_up+0x70/0x118)
[ 43.270441] [<c071b81c>] (_cpu_up+0x70/0x118) from [<c071b928>] (cpu_up+0x64/0x84)
[ 43.277704] [<c071b928>] (cpu_up+0x64/0x84) from [<c0702400>] (store_online+0x48/0x78)
[ 43.285579] [<c0702400>] (store_online+0x48/0x78) from [<c0376318>] (dev_attr_store+0x18/0x24)
[ 43.294338] [<c0376318>] (dev_attr_store+0x18/0x24) from [<c0188938>] (sysfs_write_file+0x100/0x148)
[ 43.303250] [<c0188938>] (sysfs_write_file+0x100/0x148) from [<c0137e40>] (vfs_write+0xa8/0x130)
[ 43.312345] [<c0137e40>] (vfs_write+0xa8/0x130) from [<c0138090>] (sys_write+0x34/0x68)
[ 43.320219] [<c0138090>] (sys_write+0x34/0x68) from [<c000da20>] (ret_fast_syscall+0x0/0x30)
[ 43.328521] ---[ end trace bfc5852670d2b507 ]---

Whatever issue this is with CPU1 failure happening randomly since 9/19 nightlies or so seems to still be there. It doesn't happen all that often but if you don't catch it, the phone will sit there locked up and drain itself dead unless you force a reboot.

As I was questioning before, maybe this has something to do with the 3.4.62 kernel, since the issue seems to line up with this commit. Perhaps I can try flashing the 3.4.60 boot.img from 9/17.

Any msm8960 kernel developers still hanging around? Any ideas?
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Intervigil pointed out the CPU1 thing several weeks ago, then went poof off to OppoLand. A few kernel guys working on Ville have been testing some stuff...haven't had bootloops running a 3.4.65 based kernel yet...
[AT&T, Rogers HTC One X, Telstra One XL] 24ky:
I know im gonna sound stupid, but is the brick bug fixed?
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Yes, however for some users it has been replaced with a rather annoying reboot bug :)
[AT&T, Rogers HTC One X, Telstra One XL] 24ky:
Okay thank you.... Last time I checked the brick bug was present... And I finally wanna go back to using AOSP like I did on my incredible days..
[AT&T, Rogers HTC One X, Telstra One XL] manup456:
I would give it a go because that reboot bug has not been present for me at all. I tried every rom but can't stay to long before I nandroid back to CM and I'm on yesterday's nightly without a single reboot . This has just been so silky smooth and keeps getting better. My best cm experience to date.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
So is this why on the last nightly my phone would randomly go into a bootloop at times and only work after I wiped cache?
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
While it's rebooting hold pwr and volume to get to recovery. Then actually power it down before turning it back on. Seems to help rather than having to wipe cache.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
Am I the only one that doesmt see a changelog?
[AT&T, Rogers HTC One X, Telstra One XL] DeadlyPsycho:
http://10.2.cmxlog.com/?device=evita
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
The whole group is at the big android bbq
[AT&T, Rogers HTC One X, Telstra One XL] manup456:
I know they did some ui cleanup on the torch app, but it still won't stay on when screen is off only strobe works with screen off is this intended to be this way or is it a bug.
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
Torch does the same on 10.1.3. It used to work fine in the nightlies and I think even in the rc's. Don't know what changed, but it's been like that for a little while.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
Does anyone know how to stop the random reboots in this rom?
[AT&T, Rogers HTC One X, Telstra One XL] Clark008:
10/11 Build

10/11 Nightly Build is running fine so far, no reboot or lock up issue. Now at Android 4.3.1 with 3.4.62 kernel.

Go flash and join us on the bleeding edge. =)
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
I just did but when I used reboot from the power menu and then the phone went into a bootloop
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Haven't had a reboot in a week, but I've noticed that while in call the touch screen in still active. So I've been torching and airplane moding like crazy.
[AT&T, Rogers HTC One X, Telstra One XL] llambkin:
I have had that since 10.0, well with my bluetooth headset anyways, not with handset calls. In my case I take my phone out of my pocket to make calls. Its just habit for me now, I dont know if they fixed it.
[AT&T, Rogers HTC One X, Telstra One XL] amccue:
I'm on 10/11 too. No reboot issue like I was having. The unlock delay is just barely there, but for me it's negligible.
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
Ok, maybe this is something different, but I see that happen sometimes, and I'm still on 10.1.3. I've been meaning to ask if anybody has seen this on 10.2, but just never got around to it. I'm only asking this here since you mentioned something similar. Every now and then, I'll take the phone away from my ear (during a call), and daydream is active. I have daydream set to only turn on when the phone is plugged in, and it's never been plugged on when this happens. Has anybody seen this before (on 10.1.3), and if so, does it still happen on 10.2?
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Just a heads up but the Q&A should be posted in the correct thread for better results. I've been noticing quite a few of these posts lately
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
ever sense ive installed this 10/14 nightly my phone has just been messed up, it wont boot..... cant mount sdcard or data.... then the one time it did and i tried to flash a rom my phone restarted....... like why am i having issues with recovery now? im done with this rom......
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
With all due respect, most everything you flash will be a derivative of CM in some way, shape, or form. In other words, you're going to have a hard time "escaping" CM. Best bet would be to start from scratch with a RUU. I've been seeing a few instances of recovery problems. Either reflash recovery or like I mentioned above, RUU and start from scratch. Afterwards, flash a previous nightly and are how it goes.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
None of that worked, had to keep trying to wipe in recovery until it worked then got viper xl installed...... I'll just wait until 10.2 stable is out..... Nightlys creep me out now
[AT&T, Rogers HTC One X, Telstra One XL] OwenRW:
I'll preface this by saying I don't have a logcat of the problem, but thought it was worth at least noting it:

Yesterday I did a 'clean' install of the latest nightly (10/14) and on initial boot, it spent 2-3 minutes on the CM logo then rebooted.

This got to the initial CM Account screen pretty quick (~15 seconds), but once their it was like running through treacle. Every screen tap took minutes to respond and I eventually got fed up and held down the power to turn the device off.

After restarting it, everything seemed fine and was working OK until I 'dirty' flashed the 10/16 nightly this morning.
[AT&T, Rogers HTC One X, Telstra One XL] Arrow44:
Sounds like all of your problems are recovery based, not one thing to do with the ROM. Maybe your over reacting and pressing buttons too fast or didn't wipe properly or something. I've done the same thing so don't get butt hurt but try changing your twrp version to 2.3.3.0 because anything higher has got a little funk to it.
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
This is in the issue tracker no? If not I'll add it, it's starting to annoy the heck out of me...
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Yeah if you don't mind adding it that'd be great.
[AT&T, Rogers HTC One X, Telstra One XL] amccue:
I'm actually guessing this has a lot to do with all the kernel work they did on the 10/14 build
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
FTFY :)

But I don't have the issue anymore oddly enough. I started the entry & decided to upgrade to the latest nightly (10/16 as of this post) so the logcat would be on the most recent build. I did that, tested the issue and after 20 tests it seems to be gone. If you're still having the issue you can post it here...

http://code.google.com/p/cm9-msm8960/issues/entry

The template is easy enough to fill out. You'll have to run the logcat though since I obviously can't do it, sorry.