yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Arkalos13:
i was running the Oct 11 build until nov 3rd without any problems, figured i should update it though. And that was probably the biggest mistake ever. I updated to nov 3 build, everything was running fine for 1 day, i was driving with the navigation on and bluetooth streaming music, when all of a sudden it froze.

It turned off, and didnt turn on for anything. I pulled over because i had no idea where to go (following the navi somewhere). I tried to flash back to oct 11.. and nothing, bootlooping, i tried wiping data and installing oct 11, nothing, wiped data again and installed nov 3 again nothing. Finally as a last attempt, i factory reset it thru the bootloader, and wiped everything.. i press power hoping it would turn on and it finally did, but i had already lost everything, everything from my sd card was wiped.

I dont know what the issue was, everything was working fine and i have never had any problems before with cyanogen until now.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You probably should have just run an RUU instead of doing a factory reset through bootloader.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Never do a factory reset through the bootloader. All that ends up is EVERYTHING is wiped, even sd. And there's no factory Rom to go to, so you'd need to send a Rom zip in twrp to fix it. In other words, a tedious mess
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
Both my old one and my wife's would get really hot and start acting really strangely when using nav for a long time. They were always fine after letting them cool off for a while though. It would work fine for quick trips under an hour, but anything that was a few hours in length would cause problems.

---------- Post added at 07:31 AM ---------- Previous post was at 07:30 AM ----------

That can be tricky on the side of a road with no PC. ;)
[AT&T, Rogers HTC One X, Telstra One XL] N.K.V.:
They got CM11 running in Evo 4G LTE.

Any chance of us getting CM11..??:fingers-crossed:
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
Good things come to those who wait.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
We have h8rift and intervigril...we will have it soon. By the way, look through the beta phase of 10.2 posts back in July...it'll show the bravery and risk of impatience
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
LOL you must be a glutton for punishment! AFAIK, CM10.2 has only just become stable/good.

FWIW, 108hrs uptime and still without a single reboot, F/C or issue of any kind on the 1106 build.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Yes!

People really need to stop asking "if we are going to get kitkat". We are obviously going to get it at some point just not tomorrow or the next day or the next day. Be patient people and remember, Do not ask the developer for release dates or "when's the next update coming?". We will get kitkat when kitkat comes out. Simple as that.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
Same thing happened to me on Friday (11/8/2013) I was sitting on my computer with my phone sitting next to me. It rebooted which I thought was weird and just kept rebooting to the HTC screen. Not even Cyanogen logo. I was able to get into recovery (TWRP) and noticed that everything was wiped. I mounted USB to check and it told me I needed to format the disk. Nothing was on there. Don't know what's up with this ROM. Gonna go beanstalk or something else till this gets fixed.
[AT&T, Rogers HTC One X, Telstra One XL] G4 Man2:
Beanstalk is still having bootloop issues and sometimes will stop booting all together. I've been running on codefireX and haven't been having any of these issues. Just a helpful tip.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
Thanks for the info. Downloading now.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Yes BeanStalk is not being built at the moment as the maintainers are working towards 4.4.

If I could just throw my .02 in here, I think the efforts that are now being put forth should be focused on kitkat from here on in. Not to say that 4.3 ROMs should cease development, so please don't take that the wrong way. If you think about it, kitkat will most likely be the last "new" Android OS that gets ported to this device. By the time the successor of kitkat comes out, I imagine a lot of people will have already moved on to another device. I may be out of line in saying this but that's just how I feel. And since 4.4 introduces a lot of brand new resource and power management features, I feel its best to try and dump the majority of the deving effort into that.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
If you look at the CM code review site, I think Ethan has mostly switched to CM11 commits. Between the SD card wiping here, bootloops here and Ville and other bugs, I think he's just hoping CM11 "fixes" stuff that doesn't seem fixable in 10.2

http://review.cyanogenmod.org/#/q/owner:%22Ethan%20Chen%22,n,z
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Sd wiping? Wtf? When did we have that? I'm so happy we're still supported officially though.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
There are 3 people in the last week here who have found their sd partition corrupted after a bootloop. Scroll up to comment from pollypocket just a few posts up.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Yea its weird how every other ROM is in some way, shape, or form based off of CM but do not have the catastrophic failures that just the CM base has had. I was running the 11/3 or 6 build (can't remember) and it was actually running pretty good until I flashed another ROM. The next day I read that people are getting their SD cards wiped. Idk about anyone else but I am going to treat this as "the last straw" for these 4.3 nightlies.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Contrary to popular belief, not all aosp ROMs are based off CM. For example, I believe CFX is built directly from aosp.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
You are correct. Cfx is about as AOSP as you can get. With that as an exception though, pretty much every other ROM is somehow based off CM. And no other aftermarket ROM for this device (to my knowledge at least) has experienced this many fatal issues.

With that being said I'm going to leave it at that. I am in no way disrespecting h8 in saying any of this as I know he and the team have been working their tail off to try and get this working right. I keep trying to rack my brain as to why such experienced and well-respected developers keep having such data a threatening issues but that is neither here nor there. God knows I couldn't do any better and I would never say I could. Unfortunately, the problem for me is i just cant muster up the courage to risk losing all of my data (including sdcard) at any given time. Just too many problems have plagued this particular ROM and although they eventually get taken care of (to an extent) new, fatal issues keep popping up.

This is all my opinion and like I said, I'm just going to leave it at that to avoid and further clutter and OT discussion.
[AT&T, Rogers HTC One X, Telstra One XL] llamas612:
Is the One XL really that old though? I don't think Android has been introducing features that are too powerful for our phone to handle. If anything, newer phones are simply overpowered. When 4.4 came out, I immediately heard about some devs supporting the Galaxy Nexus, which is even older than the One XL. If we don't get the version after 4.4, it will likely be due to lack of developer interest (which is honestly totally understandable for the reasons others have mentioned). I'm still really happy/surprised that there is so much development for this device, nevermind for future updates.
[AT&T, Rogers HTC One X, Telstra One XL] JoshX:
I've built CM11 for the my phone already, it boots and looks great! There are still some issues that need to be ironed out, such as SDcard not mounting, back button not working. It'll probably be ironed out in the next few weeks, just give it a little time.
[AT&T, Rogers HTC One X, Telstra One XL] mitchel0:
The sd card wiping bug is still present. I am running the 11/8 build and my sd card has been effected twice, once on this build and once on a previous. The only thing I notice that is missing from my sd card after this happens is that all of my wifi passwords and ssids are gone. This bug occured to my phone after I rebooted it from the power menu becuase the wifi would not connect.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
How did you fix the issue h8rift was talking about? The CPU1 overload that can't be killed?
[AT&T, Rogers HTC One X, Telstra One XL] JoshX:
That issue is kernel related, not specific to CM10.2 or 11. I assume it's still there, but I haven't left CM11 on the phone long, because SDcard won't mount. I think I figured out what the issue is, there are a lot of commits for other devices on how to get the sdcard mounted, but it's still not a daily driver.
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
actually I want to take a contrary position - all the bulk of the problem is around the kernel. at this juncture, being a long time developer myself, it would be an error to change the base framework.

that introduces yet more variables that may shadow the core problem of the kernel.

trust me - I m one of those who suffered 5 years worth of pictures get wiped out on the sdcard on a bootloop. you really DON'T want to go around playing with cm11 with *that* kernel.

the cutover should happen after kernel is stabilized - unless there is a patch at the kernel level that makes things bettee.
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
off topic. use dropbox photo sync and losing photos wont matter.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Although it would be a good counter-measure for the future, no one should EVER have to worry about their entire phone being wiped clean under ANY circumstances. We should also, as "consumers" to this ROM, not have to "prepare" to lose all of our data. And yes I know I know the disclaimer states all risks that we take to flash all these modifications to our phones but let's be reasonable. As soon as I hear about or experience losing my data in its entirety, you can bet your ass I'm steering clear of whatever might have caused it. That being this ROM in particular. In a perfect world everyone would have automatic backups synced to the cloud and never have to worry about losing their data forever, but alas!

Something needs to be done about this. What? I have no idea as I'm not a developer but as a user, this is pretty ridiculous to hear about never mind experience.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
I'm as frustrated as the next guy about the way these phones are running, but there's no stable or milestone release that does this, so you are taking known risks flashing nighties. You're just lucky CM isn't still hard bricking phones like it was a few months ago...
[AT&T, Rogers HTC One X, Telstra One XL] Vanillalite:
Why does today's nightly say this is the 1st build for this device and that's it when you click on the change log???
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Yes I understand we are taking risks, it just sucks and steers people away from trying it, resulting in less people testing, resulting in problems getting fixed at a slower rate. And you're right, thank ****ing god the brick bug is gone. *Knocks On Wood*
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
which actually reminds me - there are three people who had a sdcard wipe. I want to ask - did you guys have a single bootloop after that?

mine seemed to have stabilized after sdcard format.
[AT&T, Rogers HTC One X, Telstra One XL] mitchel0:
When my Sd card wipied I still had random reboots, also it wiped two more times.
[AT&T, Rogers HTC One X, Telstra One XL] Mexickano:
I've installed Beastmode Kernel and now my screen is on but black, omg, lol, what I need to do?
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
wrong kernel - I don't think beastmode works with cm. I strongly suggest going back to your older rom immediately.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Wow...... If you bothered to read the Beastmode thread, you would have realized that, that kernel is for sense based ROMs ONLY.

My suggestion to you would be to: Read first, then flash.
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
what are you using now,? this is scary
[AT&T, Rogers HTC One X, Telstra One XL] mitchel0:
I am still running the rom, I want to try to figure out why it happened. As far as I can tell, the only thing that wiped was my pictures and my wifi data like passwords and network names. All of my music and apps installed to my SD card seem to be still there, clean master shows that 60% of my SD card is still in use.
[AT&T, Rogers HTC One X, Telstra One XL] el_smurfo:
Out of curiosity, do you have a large number of files in your sdcard/LOST.DIR folder? I used to get a lot of file corruption, mostly pictures, when running stock Sense and the files were always stored away in LOST.DIR by the boot time file system checker.
[AT&T, Rogers HTC One X, Telstra One XL] ZeroCool11:
I got several bootloops then my SDcard was gone... as of right now i'm having lots of bootloops... i think that i will go back to stock...
[AT&T, Rogers HTC One X, Telstra One XL] mitchel0:
I checked my lost.dir and there are quite a few files, the file names are all numbers and there are no file extensions
[AT&T, Rogers HTC One X, Telstra One XL] xetrev:
lol really, you are running a rom not meant for the phone.

stick to stock if you cant risk data loss. there is a disclaimer on the front for a reason.

if you still want to cry about it take the precaution and store backups on your PC via TWRP. It's not that difficult and i would say you got caught being lazy.
[AT&T, Rogers HTC One X, Telstra One XL] Vanillalite:
So yesterday's and today's nightly both have no change logs when you click for the log.

What gives?
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Hmmmm. Well since you either did not read my post in its entirety, completely misunderstood what I was saying, or both let me explain this to you. First of all please refer to the above self-quoted excerpt from the post you are referring to. Thank you.

Second of all, this ROM has been plagued with the "brick bug", random reboots, bootloops, etc. The whole nine yards. Anything that could have gone wrong with a ROM, has gone wrong in this ROM. And being that you misinterpreted everything I said let me explain something else.

I have tried this particular ROM myself only 3 times. Once when it first came out which was a horrific experience. A second time about a month later, same experience and a third time which was recently. The most recent time was not as bad as the last two but I only ran it for a day if that and experienced reboots and bootloops but no wiping.

Basically what I'm saying is, this does and always has, had a terrible bug attached to every build since it came out. I can't think of a nightly that people did not have any problems with. Hell, some people have had to go all the way back to early September builds in order to get a halfway usable phone and even then it was a painful process.

Sure other ROMs have had their fair share of problems but now this data wiping "bug" has popped up and is wiping everyone's SD card. I personally just don't get it. Why is it that after all this time, **** still is like a pre-alpha build?

Technically, anything on xda other than a RUU is not "meant" for our phones. But none of us would be members here if we wanted what was "meant" for our phones. Obviously everyone should keep backups in the event a "just in case" situation occurs but now our SD cards aren't even safe to store our dam pictures and music on let alone backups.

I will refer to and end with this long winded rant with my previous statement when I say "let's be reasonable".
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
All I can say is whatever the devs did in the last month really sorted out this ROM. Not sure what versions people with faults are running but my experience has been:

20131020 bootloops and instability

20131021 simcard not detected so rolled back

20131026 bootloops and instability

20131106 booted first shot, haven't needed to touch it in 8 days and counting, currently at 201hrs uptime without a single fault

I consider 20131106 perfectly stable and see no need to do any further updates unless an amazing feature or exploit is discovered.
[AT&T, Rogers HTC One X, Telstra One XL] buradd:
I still use 8/31 nightly.. If it aint broke don't fix it ;) haven't flashed anything in almost three months now
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
Like I said before in the thread, I'm on the 9/11 build and it works great! Never had an issue, and the performance and battery life are both fantastic.
[AT&T, Rogers HTC One X, Telstra One XL] JBLogic:
getcm link in OP takes me to the play store for the cyanogen installer app but it says it's not compatible with my device.
[AT&T, Rogers HTC One X, Telstra One XL] zeifers:
Same with me. Kind of a pain in the but.
[AT&T, Rogers HTC One X, Telstra One XL] DeadlyPsycho:
Try http://download.cyanogenmod.org/?device=evita
[AT&T, Rogers HTC One X, Telstra One XL] G4 Man2:
Has anyone had problems with nightly 11/06? I've been wanting to get on CM for awhile now but this whole SD card wiping fiasco has managed to keep me at bay until now.
[AT&T, Rogers HTC One X, Telstra One XL] G4 Man2:
Well I gave in and flashed the latest nightly and its working perfectly so far. No reboots, bootloops, SD card wiping, perfect CyanogenMod.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
.... give it two days lol
[AT&T, Rogers HTC One X, Telstra One XL] G4 Man2:
Only took 10 hours ;) First time dealing with it so I didn't know how soon it would strike. Bootlooped and I wiped cache and dalvik and now it's back to normal. Ah, fun stuff.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
Lol it's going to happen again bro
[AT&T, Rogers HTC One X, Telstra One XL] G4 Man2:
I know but I'll fight it as long as I can! Is anyone actively working on this bug?
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
Yea, we have a few very talented devs working on this for our device... and all of them are confused lol
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Have you got a link to the specific build? Also are you on 2.14 Hboot? I had a major problem last month when it booted there was extreme lag and I had to force it into recovery... That was with hboot 2.15 tho
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I'm have a lot of trouble finding a download link for it, but it was:

10.2-20130911-NIGHTLY-evita

I'm on 2.14 hboot.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Quick correction: You're on the 2.14 firmware package, not just the hboot. It's this referring to it as the hboot that confuses people into thinking all they need to change to run this ROM is the hboot, when they actually need to run the RUU to get ALL components of the upgrade.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
If they haven't fixed it yet, which perfect build am I running lol.....
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
how long have you been on it?
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
Been on CM10.2 since the original brick issue was resolved, upgrade path that I could remember in an earlier post. But on that build since probably the day it was released.

Edit: LOL Totally missed what he was asking, edited the screen cap. ;)
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
still not going to trust it, the bug is still there you probably just didnt run into it yet..... how often do you use your phone?
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
Phone gets used all day every day. Youtube, Tapatalk etc. Music in the car via BT. Exchange email on push along with gmail and every other google service inc play music. Even had it running as a 4G Hotspot to my home wireless router in bridge mode as my broadband wasn't working over the weekend.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
thats the thing.... i DID lol maybe bad luck? what recoverys are you guys using?
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
So do you think me installing it using 2.6.3.0 (I think that's right to lazy to look) would cause an issue?
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
I did that's why I'm asking, so far I don't THINK 2.6.3.0 has caused an issue with flashing Roms
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I've seen 2.6.3 reported a few times as causing problems. TWRP 2.6 is the latest stable recovery with ZERO problems.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] DeadlyPsycho:
There has been a lot of negative posts here so let me add some positive notes:

I have been flashing the nightlies since they first appeared on get.cm, I usually skip a day and flash every other day. I am currently on today's nightly, Nov 17, and have yet not encountered the sdcard wipe bug. I am confident that it has not since I have folders on there dating to 2012.

I have however had the cpu core issue where it would crash during rom startup and reboot, but all I did was power off the phone manually by holding the power button and turning it on again.

I use my phone every day and usually reach 20-30% battery by night time. I flash the nightlies with the latest TWRP version, 2.6.3.0.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
Wait, so you only get the reboot bug when starting up but if it starts your fine?
[AT&T, Rogers HTC One X, Telstra One XL] DeadlyPsycho:
Yes and I have done manual reboots tons of times, very few of those have failed to start. If it does fail, just do the power off trick and voila, it works fine afterwards.
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
Fair enough, as long as it didn't reboot while you where using it out it was in idle I'll try it again
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
So I accidently formated the memory card anyway..... Moving along lol has anyone else noticed that some nightlys where skipped? Anyone know why?
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
So, anyone elses phone just randomly shut off? My phone will be in my pocket and then I'll go to check it and it's off?
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Just with my kernel or on stock CM as well?

If it doesn't happen on stock CM move this talk to our discussion in my thread.
[AT&T, Rogers HTC One X, Telstra One XL] dschroeter:
FWIW, I did the full RUU, am unlocked/rooted/s-off, TWRP 2.6.3 and hboot 2.14. I've been running nightlies pretty regularly through (don't hit me) CyanDelta. Today's (11/17) was the first in quite a while to breeze through the boot animation, startup and the app upgrade process on the first go.

My eyes glaze over reading the changelogs, but my personal experience is that at least the first boot experience has been solved and no RR in ~18 hours of uptime.

Thanks as always to the overworked devs.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
Are you running any kernels or mods?
[AT&T, Rogers HTC One X, Telstra One XL] dschroeter:
No, I'm not.
[AT&T, Rogers HTC One X, Telstra One XL] ZeroCool11:
so, pretty much this new CM10.2 is soooo unstable... i'm gonna give it a shot to this Beanstalk... it's CM based but they says that it doesn't have bootloops or anything... i hope not
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
A little kitkat love on H8's google+ page. Something to tide me over til my N5 gets here
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
I wonder how it is in terms of functionality? Wish I could test.
[AT&T, Rogers HTC One X, Telstra One XL] dschroeter:
Really awesome news about KitKat. Anyone else having the same good luck I am with the 11/17 build? Working on 58 hours of uptime here. Was the CPU issue resolved?
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
Very awesome news with that!

I circled h8 a long time ago on G+, did he share this picture with certain circles only? I can't see it looking at his G+.