yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] masulembo:
TWRP
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
What I would do in a case like this is start from scratch.

Run the RUU again and then let it boot. Copy the ROM and gapps to the phone. Then fastboot flash recovery. reboot into recovery and flash the ROM and gapps.

I'm curious at this point how you were able to flash the ROM without a working recovery.
[AT&T, Rogers HTC One X, Telstra One XL] masulembo:
the process may be you are doing something wrong

1-fastboot flash recovery recovery.img,,, so what I have is in the folder

2-fastboot erase cahe

tell me if you have to do something else?
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Amazing job h8. Quick thing: does anyone else have a lag when exiting out of the app drawer by using the home button. I mean hit app drawer. Once in drawer, then hit home button?
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
just clean flashed the latest build, superuser not working here.

tried titanium, and root explorer.

(love how fast and smooth this rom feels though)

edit; tried setting superuser response to auto yes, still no luck
[AT&T, Rogers HTC One X, Telstra One XL] phatboypat:
Stock camera and focal are not working for me.
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
straight from the op:

Known Issues:

Bluetooth will not turn on.

Camera isn't functioning
[AT&T, Rogers HTC One X, Telstra One XL] brandontaz2k2:
Have you read the OP?
[AT&T, Rogers HTC One X, Telstra One XL] phatboypat:
Not since the update.

Charming as ever guys. :thumbup:
[AT&T, Rogers HTC One X, Telstra One XL] jwhood:
Just flashed works great except for bugs mentioned in op!!
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
I definitely wasn't rude about that.

Even though its common knowledge to read the op (especially before posting bugs)

:eek:
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
This fixed it...
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
I tried this to fix the camera but I couldn't install the apk. Not sure why

http://xdaforums.com/showthread.php?t=2293287
[AT&T, Rogers HTC One X, Telstra One XL] lauterm:
For those that use TB, this fixes it on the new Nexus 7. Does it work here too?

Copied from http://xdaforums.com/showthread.php?p=44168654

Titanium backup Users

1. In tb go to menu>preferences>backup folder location

2. Navigate to storage/emulated/legacy

3. Select your Backup folder and Select "Use the current folder"

4. Then it will ask you to move backup to that folder.... Select that

5. Restart app and restore.
[AT&T, Rogers HTC One X, Telstra One XL] venelar:
Good to know!
[AT&T, Rogers HTC One X, Telstra One XL] dustinhayes93:
False alarm. Its working better.. Last night I disconnected and reconnect 10 times in a row perfectly. This morning it was back like to connecting randomly
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
roflmao. Don't use that...it has nothing to do with the issue we're having with camera. its not an apk issue, its the camera HAL / gralloc.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
We don't use emulated storage, so doubtful that directory will work.

You *should* try /storage/sdcard0/0/ though.
[AT&T, Rogers HTC One X, Telstra One XL] pOLLYpOCKET:
I wiped everything and installed cleaned. No data or superuser issues.
[AT&T, Rogers HTC One X, Telstra One XL] tfngwena:
I see what everyone means about this being buttery. Great work to have it out this fast.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Bluetooth is fixed now :). Last thing is camera. Gonna see if its something i can knock out tonight or i'll have you guys a build with bluetooth tonight/tomorrow.
[AT&T, Rogers HTC One X, Telstra One XL] thewierdone:
tried it too

i tried it too but it didnt work. installed loaded up gave it superuser access but no luck hopefully with the bluetooth working well see a new build that is almost as good as the 10.1 builds.:victory:
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
Our camera issues won't be solved with an app that reboots the camera on the Galaxy S3.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I need the whole filename. And where you downloaded it from.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] masulembo:
I did so as said, but lost the recovery, then came a triangle

and the phone will restart and went up, then went back to install the recovery bootloader mode

and try to go but then the screen stayed black and climbed into recovery mode, then change the RUU for 2.20 and it does not know where the problem is.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Please post the full filename of the recovery and where you downloaded it from. It's very possible you're flashing the wrong one. I'm trying to help you but if you don't answer the questions you're making it hard.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] masulembo:
This is the name,openrecovery-twrp-2.6.0.0-evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Can you post the text from the command prompt after a failed attempt at flashing?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] masulembo:
what did you change the name to recovery.img

now giving me an error, but always close the command and open a new

please forgive my English is not very good.
[AT&T, Rogers HTC One X, Telstra One XL] zeifers:
looks like its fixed, there was an update in the 11.3 build that fixed the boot problem with the dual core. i have installed and rebooted 5 times with no problem. no auto reboot, no slow moving unlock screen and no taking forever for the apps to optimize.
[AT&T, Rogers HTC One X, Telstra One XL] ul49:
I'm definitely getting reboots and all the other problems you mentioned on 11.3. This is the first version of 10.2 I've installed.

Have yet to get past 'Android is upgrading'
[AT&T, Rogers HTC One X, Telstra One XL] DarkisFever:
Agreed. Woke up this morning to find my phone in a boot look for some reason. Upgraded to 11-3 and everything appears normal again.
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
There's a few small anomalies going on with the 11/3 build. For example cycling through the app drawer quickly or typing quickly it shows slight signs of trying to catch up (lag). Other then that, I haven't had any major problems such as random reboots or bootloops as of yet. Will test it more throughout the day but as of right now things seem swell.
[AT&T, Rogers HTC One X, Telstra One XL] zoltrix:
I too woke up with my phone sitting frozen on the bootup animation

Seeing this made me jump to 11/3

CM has been fairly unusable for a while, so if i can last a day without a reboot - ill take it
[AT&T, Rogers HTC One X, Telstra One XL] jthmz:
Same here, ive been having random reboots since friday. Gonna flash 11/3 now.
[AT&T, Rogers HTC One X, Telstra One XL] Wonton Soup:
You do know that does absolutely nothing except spoofs your hboot version and gets rid of the red text right?
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
Correct. Making the text say whatever you want is not the goal here. The idea is to actually be on the correct hboot.

Why oh why is it so dam hard to just follow the instructions people? If you choose not the follow the directions, then don't you dare come in here asking for help when the proverbial **** hits the fan.

With all due respect, refrain from posting anything other than what the directions say as to avoid confusion with new people coming into this thread. The last thing anyone wants is to help a bunch of people with spoofed hboots that are clueless as to why their device does not work properly.
[AT&T, Rogers HTC One X, Telstra One XL] Aegwyn11:
Not quite. What he provides are modified hboots that have the red text removed. You install the modified one over your existing one, but you can also use the hboots he provides to actually change your hboot version.

If it simply spoofed it, my hboot would still really be 1.14 and I don't think CM 10.2 would work very well.....

---------- Post added at 01:45 PM ---------- Previous post was at 01:39 PM ----------

BTW, the reason I did it the way that I did it is because I couldn't get the RUU to work (I've been s-off/unlocked for so long, I forgot that RUU's won't work without relocking). So much for following the directions being the confusionless path.
[AT&T, Rogers HTC One X, Telstra One XL] masulembo:
hi thanks for help, I was able to install the recovery, the first thing the Toolkit TWRP recovery file was damaged, and the second when he tried to install it fastboot command within lA WAS THIS FOLDER NAMING THE ARCHIVOrecovery. IMG, was THE BIGGEST PROBLEM THERE

Thanks for all your help you were in the desert

thanks
[AT&T, Rogers HTC One X, Telstra One XL] exad:
The hboot file alone changes virtually nothing though, you do not get ANY of the firmware files so it is as though you are just spoofing your hboot version.

Lastly, you do not need to relock your bootloader to RUU when s-off. You need only run the ruu with your phone plugged in -_-

And furthermore.. *sigh*
[AT&T, Rogers HTC One X, Telstra One XL] Aegwyn11:
For some other reason evidently, the RUU one the first page of this post couldn't find my phone when I tried it. No idea why. Don't know. Don't care.

I'll delete my previous post since evidently I was wrong in my understanding. Apologies for any confusion I might have caused.

Thanks for treating me like a piece of dogsh.. for trying to be helpful and making a mistake. Really makes me feel like this is a great forum. I'll try to refrain from spreading my idiocy around this thread any more.

(done responding)
[AT&T, Rogers HTC One X, Telstra One XL] Bhogan123:
All we are asking and have been asking since the dawn of time is for people to read directions. Obviously not everyone's phone is identical and not everyone is in the same boat as far as problems go. The directions work just fine if you have all of your ducks aligned. If you were to encounter a problem while trying to follow said directions, asking for help would be fine and most likely resolved within a few minutes.

I would like to apologize though as I re-read my post and on top of it sounding a tad harsh, its seems as though all of that may look to be directed at you specifically and I did not mean to convey it that way. We are not here to run people away, its just that most people see the download links in the first post, download them, run into problems, and then post their issues without consulting the rest of the thread or even bothering to read the instructions in the first place. Repeat that about 200 times and you get the majority of this thread sadly....
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I can't be the only one that's noticed that this ROM and thread have gone to complete **** in the time since CM went commercial/h8rift disappeared. It's sad to see really, but I am looking forward to finding anything that isn't CM-based that I still like until I can switch phones to something better. It'd be one thing if the move to commercialization drove out h8 like it did many other devs and we got a new/temporary maintainer in here, but that didn't happen. We're supposed to just follow a changelog and install zips without being able to have any kind of interaction with the developer? **** that.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
Ethan has been the main brain behind support for for our device basically since the start. He is still the main guy and is actively making commits to the Evita device tree.

He is more active in the One S forums but like h8rift, Ethan does not post often.

One S, One XL and all other similar devices have been suffering with kernel issues since CM 10.2 came out. Updating to AT&T 3.18 reduced the issues but they were always still there. Something deep down in the bottom of the kernel aint right and it hasn't been right since moving to CM10.2 which predates commercialization.

Whatever isnt right just takes a slight change to be tickled the right or wrong way. Eg changing to AT&T 3.18 vs changes to 3.4.66 kernel vs 3rd party kernels vs ROMs.

The kernel problems have been well reported for all effected devices and the devs like Ethan are more than aware that the kernel has never really been all that stable.

Your options:

-Go back to a stable release, that is why they have that name

-Try another kernel, Eg Torched seems to tickle the problem much less often.

-Help by supplying logcats

-Help by supplying a patch to fix the problem

-Wait for someone else to fix it, if they can ever work out what the problem is
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
Not to disagree with anything you're saying, but I found myself with the 9/11 (as in Sept 11th) Nightly, running the stock kernel, and it has worked beautifully since then. Every newer build I've tried has had issues. This was just after features started getting pulled and I could tell something was going on, and right around then, h8 disappeared from the thread. I do know Ethan commits most of our stuff, but having a developer in this thread is kind of the point, right?

Like I said, I settled on the above, sometimes trying out kernels for kicks, but I have none of the huge amount of issues I've read about with newer builds, it's just falling out of date and with so many issues in newer builds, it's frustrating that we have to rely on power users (thanks to you, timmaaa, and others for doing what you can) instead of someone touching the code.
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Hi guys! Not dead and not ceasing development. I'm now also working on the HTC One VX and the HTC One Mini (and now 4.4 dropped!).

I have been veeeeeeerrry busy juggling this with life so I have had zero forum onteraction. In about two or three months.

I am actually able to post this because I'm waiting for my to go Mexican food (yum!).

4.4 will be heading to these phones, but we are still working on the massively chronic cpu1 up/down (causing your crashes and reboots) first. Its also why we decided to not go with an M1 build for this series.

*Please* post issues to Jira.CyanogenMod.org and of course specify your device and any other data along with it if you have issues. This will continue to be the location for CM version releases I work on, but I just don't have the time or bandwidth to read 5 different forum areas development threads to find issues.

I only assume the chatter in here is each of you helping each other out, which is huge! (We are all a community after all!)

Also joining and leaving an idle session in #cm-htc on freenode via IRC is a great way to get ahold of me for quick questions.

Last thing before my food gets here...CyanogenMod Inc. has had zero impact on my work in a negative light., so I do not have any harsh feelings at all about it. I actually am given better insight and support do to it.

Everyone has their opinion, so I am just letting you know mine ad a CM developer/maintainer. I love my work, so I hope you continue to as well!

Wrapping up:

* jira.CyanogenMod.org for issues

* #cm-htc on irc.freenode.net to get ahold of me.

Thank you all!

-h8
[AT&T, Rogers HTC One X, Telstra One XL] icu64:
I see that your still online and I don't wanna take to much of your time so I'll be short. Are there any builds that don't have the cpu issue?
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Umm...not that I can re-call unfortunately. I'm literally juggling between devices.

Also, Ethan *has* been doing alot of committing towards the s4 msm8960s devices (evita is AT&T's s4) because the s4 msm8960s are all common for the most part now. All 4 carrier devices are having the cpu1 up/down issue, so the issue lies in the kernel.

Here's another positive about Ethan working @ the Inc. He gets to work all day on devices and bigger issues like this! He's been working on this one for months. They've reached out to HTC and haven't gotten an answer on what "magic voodoo" they do to make this NOT happen on cpu1 up/down.

Be patient, we're diligently working to resolve this.
[AT&T, Rogers HTC One X, Telstra One XL] Cryptecks:
I'm just really glad to see some sign of an "official" word from someone about the whole thing. Looking back (I've had a full day in my office/with coffee) on my post from earlier, it perhaps comes off a bit too negative. I was simply vocalizing my frustrations with the apparent lack of real progress, but all of my fears have been delayed by finally hearing from h8! So in short, glad to know that the device isn't being forgotten, glad to know that the move to CM-Inc. didn't drive a wedge between anyone in our device tree, and mostly glad to hear that we'll eventually get some 4.4 to play with!

Thanks so much h8 and Ethan, and sorry to you both for posting my doubts in a confrontational way.
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
can someone explain the cpu1 up/down issue? Hard time understanding it. All I get is that its a kernel issue (which is the biggest concern every time we have a new version)
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Nah, you're cool man. I would've freaked out as a user ( I was there too remember? :P ) and not had the developer speak for nearly 2 months. *None* of the HTC "squad" has ill-will against the CM Inc as far as I can tell and we're still tearing up devices. The problem is there is one of us for each carrier basically for every HTC phone since this device. Soooooo we're a bit stretched thin lol :).
[AT&T, Rogers HTC One X, Telstra One XL] h8rift:
Trying not to get to technical, but basically your device is running on cpu0 alone until cpu1 is needed. When cpu1 is needed, (be it a game, multiple apps open, etc), mpdecision launches and cpu1 comes up to assist with some heavy lifting. The problem is that in most cases (not all) cpu1 can't turn back off so log/kernel message constantly is trying to turn cpu1 off until logs fill up so hard that the device nearly immediately becomes inoperable and the device soft-reboots. Problem is, to get cpu0 / cpu1 back into a normal state requires a hard-reboot. So some folks experience back-to-back-to-back-to-back soft-reboots that dont seem to go away until they reboot their device using the power button (hard reboot).

Its a nasty thing that has all of us scratching our heads. Ethan specifically has worked on it for several months digging through power management and other things. He's actually even able to run a single command from a prompt in order to cause the device to immediately re-produce the crash. the problem is the location of the problem is not something even close to easy to find. This also actually affects a handful of Samsung D2 (SGS3) devices if i recall as well. once the problem is located, it will be fixed and we'll all probably pop a bottle of champagne. :D

Besides that nasty issue, there realistically is actually less reason to NOT move this device forward now than there was going to 4.3. 4.4 KitKat (as I'm sure most of you have read) has brought in tons of power and memory management features, reducing the 1GB of RAM requirement from ICS back down to 512MB of RAM! hence, this device should actually run a bit peppier than it does now.

But back to the point. Its a nasty bug. No one likes it. Everyone is looking for it. We think HTC has some 'magic' somewhere to cover up the problem. Now hopefully the rumors of Jewel (Evo 4G LTE) getting official 4.3 are true and we can get some 4.3 kernel source....we might be able to locate what that magic is (supposedly HTC US President tweeted by end of this year). So we'll do our normal thing where we get this guy to the next version of Android...but expect it to struggle with this reboot issue until we can "find the HTC magic" stuff.

Thanks for asking!

-h8
[AT&T, Rogers HTC One X, Telstra One XL] pandasa123:
Oh I get it. We need an off switch for cpu1. Hmm....a custom script written specifically for selinux needed?
[AT&T, Rogers HTC One X, Telstra One XL] ZeroCool11:
I Just installed cm-10.2-20131106-NIGHTLY-evita and i can't get it to work... it just sits there rebooting... i deleted EVERYTHING (Dalvik, Cache, System, SDCard,Security) and then copied the file again and gapps... then when i install the rom it gets stuck in bootlogo then when it loads after 2 seconds it reboots itself... does anyone have the same problem???

I Just checked with another rom... it seems that it's not getting the IMEI so it reboots itself... i just did a fastboot getvar all and it shows the imei correctly... so how can i make CM10.2 to get the IMEI correctly???
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
Is there any help that you might need from us - generation of logs, trying to reproduce edge cases, etc? Some of us are mildly competent and might be able to help.
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
Was on something from a week or 2 ago, no idea what but went straight to the 1106 nightly yesterday. Rebooted from recovery and came up first shot. Phone was idle on the charge for 12hrs then unplugged and light usage for the past 8hrs. No issues noticed yet. Will hold off any further updates and see how many days I can go without an issue.

Good to hear the devs are working hard in the background. :good:
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
Does that occur on the stock HTC firmware too?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You mean software? As in the stock ROM/kernel? No it doesn't.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
Yes, stock ROM, stock kernel. Maybe it has something to do with that topology code. I've tried to merge several changes from flar2's Elemental kernel to the stock kernel sources. Something like the topology code, the freezer, the memcopy routines, the neon optimized AES and SH1 routines. After that, the phone started to reboot, especially when loading and unloading the prima_wlan module. It may very well have nothing in common.
[AT&T, Rogers HTC One X, Telstra One XL] wagaf:
Awesome awesome awesome !

Amazing to read that H8 :laugh: I really had a warm feeling seeing your posts.

Just as a suggestion:

As an Android app dev I'm always shocked by the huge amount of messages per second in the logcat and I was wondering if it wouldn't be better for end-users to disable all kind system logs with a switch in the dev options to enable them (maybe enabled by default in nightlies). I believe it could significantly reduce the power consumption and improve responsiveness, in all normal cases but also especially if a thing goes wrong and causes many errors (and many things can go wrong).
[AT&T, Rogers HTC One X, Telstra One XL] sandys1:
Just want to put out a quick warning - yesterday the ROM bootlooped (on 26/10) and wiped out my sdcard and all my pics. Now, I'm an advanced user and I used netcat and adb port forwarding to pull out the "dd" image of the whole phone partition. Ran photorec and testdisk on it and still nothing recovered. It was not simply a case of partition header corruption - this wiped and blanked it out entirely.

This is the first time such a thing has happened and is very scary.

I'm s-off, 2.15 hboot, twrp 2.6.1
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
60 hrs uptime on 1106 build, zero problems. Will be leaving it alone now!
[AT&T, Rogers HTC One X, Telstra One XL] ZeroCool11:
It happened to me the same, bootloop and then the sd card partition was gone :(