yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] _PMaX_:
Just following on from the firmware/hboot questions:

I have been running Jrior's unofficial (and now official) Lollipop builds on hboot 2.14 since he started posting them on these forums. They are a little buggy but running well enough and of course nothing I wouldn't expect considering the circumstances. However as has been discussed above, it is recommended to upgrade to 2.18 (or I have also read a minimum of 2.15?) firmware/hboot to minimise any chances of unnecessary issues. I would be happy to do this but I am not sure if flashing the (AT&T?) firmware zips that are available on these forums is safe for me as I am on Telstra in Australia.

Based on this info, I guess my questions are: Are there any other Telstra users reading this forum that have any experience with flashing the AT&T firmware? Would I just need to flash a new radio after AT&T fw flash, or is it a bit more complicated than that? Do I just have to suck it up go the RUU->OTA route (I think this would only get me to 2.15 on Telstra anyway, considering the time cost/benefit I think I would prefer to continue on 2.14 tbh)?

I am also stuck on Windows 8.1 computer for now but happy to source a Win 7 comp for flashing if required...

P.S. Cheers Jrior for keeping this lumbering beast alive! :good:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Whether you're on the 2.18 or 2.15 firmware should make no difference, for all intents and purposes they're the same thing. So you could just flash the 2.15 package from my guide thread of you want to, just make sure you flash it twice so your radio updates as well.

I'm on Telstra too, it doesn't really matter if you have a non-Telstra radio on your device.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] howgeet:
Awesome ROM!! everything is smooth so far!!

No Wifi issues

Thanks a lot

Found issues:

Battery is draining rapidly.

Games which require high memory just crash with this rom.
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
Few questions..

- Do we need a custom kernel (or is there one available) to enable swipe 2 sleep/s2w for CM12? Trickster Mod isn't showing this option to enable.

- There doesn't appear to be a silent/mute option for ringer volume.. the lowest it goes when holding down the volume button is vibrate. Is there a way to create silent?

- Is there a recommended ROM Manager type of app to install for CM12? Specifically, something that will let you modify/customize the Status Bar icons? I used AOKP Project before with KK to do such things, is there something similar available?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No custom kernel exists for CM12 yet so that feature isn't available. Let them get the ROM nice and stable before worrying about extra features.

That's a feature of Lollipop. As far as I know you need to create a silent profile in order to actually have silent mode.

See point one.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] sephiroth2k:
Torched kernel is available for CM12, s2w and dt2w and all that good stuff :good:

Link
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
My apologies, I wasn't aware that Torched had been updated to Lollipop. I should know better, [MENTION=2836769]jrior001[/MENTION] is always on top of this stuff.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
You are the one who's sent PM's about this? I'm thinking you may have hardware issues or possibly just corruption preventing mount. I'd try the same RUU I recommended a few posts back and if that fails it may be time to look for new hardware.

Twrp is fine
[AT&T, Rogers HTC One X, Telstra One XL] gtfour88:
I know a Sense 7 marshmallow rom for Evita is close to an impossibility, but would we see CM 13 on Evita?

Sent using xda premium
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
For those of you still using this device and fed up with storage for apps(or lack of) in LP I've managed to work up something much more usable. Unfortunately it will require a full wipe and clean install. More details to follow when I get a new thread up later today.
[AT&T, Rogers HTC One X, Telstra One XL] josegalre:
new bootloader xD?
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
I wish!!!

Just a hacked up partition layout to make things usable again.

https://drive.google.com/file/d/0B7uXK7jfW17nckhEeHprWWNlWG8/view?usp=sharing
[AT&T, Rogers HTC One X, Telstra One XL] everyoneknowspatrick:
CM13 evita

Hello!:)

When will cm13 nightlies available for evita?

The project has already been closed or there is still hope?:(
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
There may still be some hope for an unofficial build on the evitaX style layout but there will be no official build for cm13 due to the storage space issues.

Also it won't come from me, I'm officially done here with Evita. Mine took a dive to a concrete floor and finally met its demise. The official 12.1 builds will continue a while longer, an my evitaX build will remain available for a good while as well but I will not be producing anything for Evita.

Thanks to everyone for the support, its been fun.
[AT&T, Rogers HTC One X, Telstra One XL] shsaifee:
Even mine met the same fate. But it was one of a kind device. I enjoyed owning it and I thank you whole heartedly for all the support all this time!

Cheers to your spirit and all the hard work in bringing the lollipop flavor to our evitas

Good luck for all your future endeavors!
[AT&T, Rogers HTC One X, Telstra One XL] Madcat8686:
Thanks jrior, for all the mods, roms, and help along the way, it's been awesome. This EvitaX is probably the last adventure I'll have with this phone. Unlike yours, mine works perfectly although I use it just as an alarm clock now. Sure wish you were over in the M8 forums. Take care!
[AT&T, Rogers HTC One X, Telstra One XL] Atsjne:
CM 12 No simcard

Dear Developers;

Currently my HTC evita is running on stock android 4.2.2

Here are my firmware details

*** TAMPERED ***

*** UNLOCKED ***

CID-11111111

EVITA_UTL PVT SHIP S-OFF RL

Hboot 2.10.0000

Radio 3.12.38.00.24

OpenDSP-v33.1.0.45.1128

eMMC-boot

Dec 21 2012,22:26:44:17318

The problem is when I flash the latest cm-12.1-20160227-NIGHTLY-evita I get no simcard and unknown baseband and no imei other than that everything works perfectly but when I go back to stock android 4.2.2 every thing returns normal and the device detects simcard again.

Here is a full dump of all partitions (including hboot and radio) from my htc evita with the partition table in readme.txt in zip (>60MB)

www <dot> dropbox <dot> com/s/qva27jpkq3apn14/htc_One_xl_Evita_utl_dump.zip?dl=0

hope someone solve this issue and make cm12 support hboot 2.10

i really love CM and i hate the stock htc rom so please help me and fix this issue

thanks in advance

kind regards
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
I'm not sure how you even flashed the ROM, there's an assert in place to prevent users with hboot less that 2.14 from even flashing cm11+. You need to update the device to newer hboot/fw package in order for cm12.1 to work properly.
[AT&T, Rogers HTC One X, Telstra One XL] Atsjne:
CM 12 No simcard

I tried to update the firmware to 2.15 once before and i faced another issue which is no service instead of no simcard

to install it i edited the updater-script

---------- Post added at 07:46 PM ---------- Previous post was at 07:37 PM ----------

So I need your help as a professional developer to try do something or guide to the cm12 to make it support my radio and hboot

your help is high appreciated
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
There are 2 full RUU packages available that will bring you up to the last releases by att & Telstra. Those are your best bets to get caught up on fw.

http://androidruu.com <-- hosts all the old HTC RUU files.

Keep in mind RUU requires windows and fastboot/adb access working. RUU will wipe everything from device so back up anything you want to keep.
[AT&T, Rogers HTC One X, Telstra One XL] Atsjne:
All RUUs are for UL versions and mine is UTL so if i used them i the phone will get bricked
[AT&T, Rogers HTC One X, Telstra One XL] badtlc:
Is there a place to get CM12 or 12.1 stable for the evita? I'm on CM11 but would like to upgrade and obviously the CM site no longer works. Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] d.j.byrne.51201:
downloads.cyanogenmod.org
[AT&T, Rogers HTC One X, Telstra One XL] badtlc:
That site is no longer there. I think they took it down back in december when CM closed shop.
[AT&T, Rogers HTC One X, Telstra One XL] d.j.byrne.51201:
Try this: http://web.archive.org/web/20170122015155/[url]https://download.cyanogenmod.org[/url]
[AT&T, Rogers HTC One X, Telstra One XL] xlvii:
I've uploaded it for you here.

You can check the file hash here.
[AT&T, Rogers HTC One X, Telstra One XL] instinctless:
since cyanogen is down, the dl isnt available. is there another source or mirror?
[AT&T, Rogers HTC One X, Telstra One XL] jerryspring:
Which twrps have selinux abilities? I tried 287,3.0,3.,3.22...all have bootloops after flashing
[AT&T, Rogers HTC One X, Telstra One XL] jerryspring:
Twrp 322 and updating with ruu and 5.18 zip worked! Thanks. Had to flush 3 times

---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------

New version? This ROM is dope!
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Lol yeah its like 2 weeks behind...I should update that.
[AT&T, Rogers HTC One X, Telstra One XL] sephiroth2k:
That'd be awesome, I'm using your kernel with today's build of Candy5 and all is well. Thanks for your efforts for our device!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I think everyone's grateful there's even a custom Lollipop kernel available :)

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] nikhil3737:
problem while installing CM 12

s- off

hboot 2.18

twrp 2.8.1.0

all works fine except it stuck in cynogenmod boot image ......

what to do now
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
How long did you wait? The first boot takes a really long time.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] nikhil3737:
around 2-3 minutes

the required configration is ok...???

what would be the problem...
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
You should be fine....but expect 20 mins to boot 5.0
[AT&T, Rogers HTC One X, Telstra One XL] nikhil3737:
one more problem is there.......

I have installed a CM 11 ROM in my HTC ONE XL (evita), initially it was good but after i installed greenify and xposed installer ....i m not able to search my sim network, then i again installed a new ROM of CM 11 AND Also tried MOKKE ROM then also i m facing the same problem,

whenever i go to manually search for network it says " ERROR WHILE SEARCHING NETWORK"

please suggest me any option

to solve the problem i update my hBOOT to 2.18 also then also it didnt work....suggest me
[AT&T, Rogers HTC One X, Telstra One XL] nikhil3737:
yes i did install CM12 but it doesn't have a supersu installed ....we have to install manually.....

how to root android 5.0 (CM 12 )..

please guide me
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Dev options, you have to enable root, its off by default
[AT&T, Rogers HTC One X, Telstra One XL] nikhil3737:
one more problem is there.......

I have installed a CM 11 ROM in my HTC ONE XL (evita), initially it was good but after i installed greenify and xposed installer ....i m not able to search my sim network, then i again installed a new ROM of CM 11 AND Also tried MOKKE ROM then also i m facing the same problem,

whenever i go to manually search for network it says " ERROR WHILE SEARCHING NETWORK"

please suggest me any option

to solve the problem i update my hBOOT to 2.18 also then also it didnt work....suggest me

the problem persist when i installed CM 12 ALSO

---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------

one more problem is there.......

I have installed a CM 11 ROM in my HTC ONE XL (evita), initially it was good but after i installed greenify and xposed installer ....i m not able to search my sim network, then i again installed a new ROM of CM 11 AND Also tried MOKKE ROM then also i m facing the same problem,

whenever i go to manually search for network it says " ERROR WHILE SEARCHING NETWORK"

please suggest me any option

to solve the problem i update my hBOOT to 2.18 also then also it didnt work....suggest me

THE PROBLEM WAS STILL THERE WHEN I INSTALLED CM 12 ALSO

KINDLY PLEASE SUGGEST SOMETHING
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
I heard yesterdays nightly had some data issues on some devices including Evita but I haven't looked into it. A nightly from a few days ago may work better till issues clear. You can Check APN and preferred network type in settings. I'm traveling today so there's not much else I can offer at the moment.
[AT&T, Rogers HTC One X, Telstra One XL] santhu7388:
htc one x evita

hello. am using this rom since from official update. everything was working fine. but some what it was bit lagging while opening and closing apps. and battery was draining heavily. is any one having this issue? is any solution for this? please guide me.
[AT&T, Rogers HTC One X, Telstra One XL] santhu7388:
htc one x evita

problem in changing a phone ringtone. only the device ringtones are working. while am setting ringtone from my filemanger it was accepting but not working. when i get a call a beep sound was ringing. is anyone having this issue.? please reply for solution.
[AT&T, Rogers HTC One X, Telstra One XL] nicolahaye:
I had this issue on a previous built of candy 5 (0.8.3 I believe) with the alarm ringtone. I haven't tried again since then.
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
I've had this since before the Evita went official with cm12. No idea of any way around it other than manually setting a custom tone for every single contact.
[AT&T, Rogers HTC One X, Telstra One XL] maxyor6040:
is this more stable than the Candy5? :confused:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That isn't a question you ask on XDA.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
Eventually, I have found a way to make my phone work with my Windows 8.1 PC in fastboot mode. The idea is to create a key in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags (I don't know why the forum software adds some spaces in the previous key name, but there aren't any in reality) with a specific name. The name must have exactly 12 characters and must be in the form vvvvpppprrrr, where v, p and r are hexadecimal digits and:

vvvv is the vendor ID number,

pppp is the product ID number and

rrrr is a revision number.

For example, in my case (an HTC One XL originating from Germany and made for O2), the key name is 0BB40FF00100 and chances are this name applies to all the Qualcomm based HTC One X. Once the key created, you should create a binary value called SkipBOSDescriptorQuery and set its data to 01 00 00 00.

References:

An article on Microsoft Windows USB Core Team Blog describing how to detect the vendor, product and revision ID numbers and how to create the necessary registry data: Why does my USB device work on Windows 8.0 but fail on Windows 8.1 with code 43? Please note in the article it is suggested to create SkipBOSDescriptorQuery as a DWORD value. I think something has changed since the date when the article has been written and now SkipBOSDescriptorQuery must be created as binary value.

A link to an updated version of Message Analyzer.

An article about making Rockchip devices visible on Windows 8.1. It saved my day by giving me the idea of making SkipBOSDescriptorQuery as binary value.

Now, I would like to ask a question about the 2.18 bootloader and the 1.35 radio version. Doesn't the bootloader contain the partition table? What's the impact of flashing it on a O2 Germany phone? You said the radio version doesn't matter if it's flashed on an Australian One XL or on a AT&T one. Isn't it supposed to contain the frequency bands? Are these pieces of information stored elsewhere?
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
I wish we could bookmark this single post, nice work hunting that down.

As for the hboot/partition table, I believe nothing ever changed on the different Evita versions as far as that goes so no issues there. The hardware modem on all Evita's should be the same bands, the radio image your carrier released likely has some minor tweaks the carrier made. Its possible the radio image specifically for you version may work slightly better in your country but they all should work.
[AT&T, Rogers HTC One X, Telstra One XL] colorprint:
NFC still not works :(
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
Lag issues, haven't really noticed anyway.

Massive battery drain, yes. And this is despite enabling Battery Saver, turning off all syncing, putting display on lowest setting, etc.

Compared to the KitKat rom I was on prior, CM12 is draining my battery approximately 3 times as fast. And on KK, I had syncing on for all my key apps.
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Loaded up today's build and threw my sim card in. I see we still have a data issue that's creeped in this week, NFC seems to be fine( i beamed stuff to my OPO) and im not seeing lag issues. I'll have to run this for a day or so to check on battery but only if we can squash the data bug.
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
Thanks so much for posting this, I'm hopeful it can eventually work for me.

Like jrior said, this topic really deserves its own thread/sticky. I hope you/jrior/others don't mind, but I have a question on the above process. I read both articles, including the updated workaround notes. In my case, the "0BB40FF00100" key already existed under my "usbflags" in regedit, so I simply created the new binary value for the key (attached below).

Unfortunately, when I'm in fastboot USB in bootloader and running adb, it still doesn't recognize my phone (I get the yellow triangle Windows warning that my computer doesn't recognize my usb device). To be sure, when I'm running adb and type 'adb devices', it doesn't list my Evita.

Can you tell if I've done anything wrong here? Sorry again to anyone for getting off topic of CM12.
[AT&T, Rogers HTC One X, Telstra One XL] santhu7388:
yes there is a lag issue. while opening apps am waiting for nearly 10sec to open that. and i turned off everything. but still battery was draining.
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
When the phone is in fastboot mode, then use the fastboot tool. Type fastboot devices to check the devices in fastboot mode plugged to your PC. adb is used when the phone has already booted in Android. About the yellow triangle, have you installed the fastboot mode drivers?
[AT&T, Rogers HTC One X, Telstra One XL] thewaronerror:
On one of my machines, a dword set to 1 worked on the other it didn't work until I changed it for the binary value you used. The one that worked with the dword has a new installation of windows 8.1, the other one I vaguely remember installing some related patch (I think the one that only fixed sony phones mentioned in the microsoft blog post). It may be that the older patch wants the value to be a binary while any system that got support for SkipBOSDescriptorQuery from windows update wants a dword.
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
Sorry. I meant to say in fastboot usb mode, it doesn't list my device with fastboot devices.

In adb (booted to android), adb works fine.. it lists my device and I can access it from my PC.

What specific fastboot mode drivers are you referring to? And where can they be found? I've searched everywhere for Evita fastboot drivers for W8.1 64bit machines and can't find anything.

I even found various XDA-referenced videos like the one below describing the install process where it mentions to install the Universal Naked Driver, but the only listed compatible HTC device for this driver is the HTC One, not Evita.

https://www.youtube.com/watch?v=afrvSGiMAtk
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
My W8.1 is up to date but making it a dword set to 1 didn't work either. Thanks anyway
[AT&T, Rogers HTC One X, Telstra One XL] AlxMAX:
The following requires a lot of patience. You are going to modify an INF file from Google's drivers then you will reboot your Windows machine in a mode where the installation of drivers without signature is not enforced.

Modify Google's USB drivers

download the drivers from here, extract the files somewhere.

edit android_winusb.inf. You should notice the INF file is organized in sections, each section beginning with [section_name]. Look for the section [Google.NTx86] and follow it up to the next section, which is [Google.NTamd64]. Add the following line right before [Google.NTamd64]:

%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FF0

Edit: type ENTER after the line to separate it from the beginning of the section. Then follow the [Google.NTamd64] section up to its end where the [USB_Install] section starts. Right before [USB_Install] add the same line as above. Edit: separate the line with an ENTER from the next section declaration.

Reboot your PC with the enforcement disabled. Have a look at this link. The page might nag you with an overlay box to send them your e-mail. Just dismiss it.

Install the drivers. Open the device manager and plug your phone in fastboot mode. After it appeared in the device manager, right-click on the device and update the drivers by pointing it to the directory with the INF file you have modified. The system asks for confirmation if you really want to install that driver which is not signed and choose to installit anyway. If you have any other driver to install, now it is the moment because the enforcement is back after a reboot.
[AT&T, Rogers HTC One X, Telstra One XL] droydr:
I downloaded the Google USB driver, extracted the files, and edited the INF file by adding that line in the two necessary places you mentioned. Does anything look wrong with my modifications? (see attached screenshot of INF file)

I rebooted by PC with signature enforcement disabled.

In fastboot mode, I tried installing the modified INF file and it keeps giving me the same error msg that it's not a compatible software driver for my device and to make sure it's designed to work with Windows x64 system. (see attached screenshot of error msg)

I've tried re-doing these exact same steps many times now and each time I'm running into the same error msg. In reading some comments from other users on that youtube video, it seems like this is a common problem when trying to install the driver.

EDIT: Nevermind. Just tried fastboot devices again and it's now recognized despite it appearing the driver wasn't getting installed. I guess somehow it went through despite the same error msg I was getting. Thanks again for the help!

Anyway, now that I have fastboot access, I went ahead and finally updated my firmware to the AT&T 5.18 version.

Eventhough I know my previous hboot 2.15 and 2.18 are essentially the same, I want to see if the poor battery life I've been getting on CM12 improves with the latest FW.
[AT&T, Rogers HTC One X, Telstra One XL] Digital_Cameltoe:
Amazed and delighted that the Evita is still being supported. The one x was my first android phone and I loved it to the end. On a Note 4 now and still running cm12 :).
[AT&T, Rogers HTC One X, Telstra One XL] vertycall:
I had also problems with win 8.1 and fastboot recognizing the device. For me the solution was applying a .reg file with the following content:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100]

"SkipBOSDescriptorQuery"=hex:01,00,00,00

credits to : dr3amsINdigital

Original source
[AT&T, Rogers HTC One X, Telstra One XL] colorprint:
can't connect any 2.4GHz wifi networks with last CM builds - authentification always fails :(

5GHz networks works fine.

Also NFC payments still not works with latest 18-Jan build...