yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] pside15:
So I'm back again with a couple of questions. Just because I had a One XL previously everyone thinks I have all the answers, which clearly isn't 100% true. I think I know the answer to my question but wanted to check here since [MENTION=4153349]timmaaa[/MENTION] does have all the answers. :p

Anyway, a friend just got a One XL and it's buggy as crap. It's running a really old version of Viper ROM I think. He doesn't care about ROMs or anything so I just want to get him on whatever the newest AT&T stock was. I checked the bootloader, which is unlocked, and it somehow still has 1.09.0000 HBOOT. It's also still S-ON. I thought the CID should be listed there but it wasn't for some reason. Been a while since I had this phone so I might be wrong.

My plan was to make sure he has superCID, since it's clearly rooted already, and get s-off. Then just run the latest RUU after that? I just wasn't 100% positive if I needed to do anything else since it's still on the 1.09 HBOOT?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The CID is only listed on the bootloader when the device is s-off. If it's the at&t model it's almost definitely SuperCID but you should check:

fastboot oem readcid

So get s-off first via Rumrunner (you'll probably need to flash Kickdroid 5.0 to achieve that though), then you can run whatever RUU you want.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] pside15:
Thanks for the reply. Well, I'm positive it's the AT&T model. I found out that my co-worker/friend got this phone from a mutual friend and I was the person who unlocked the bootloader on it originally. I should have known then that it has SuperCID since the bootloader is unlocked on the 1.09 hboot. I'll definitely double check it to be on the safe side. I'm also about 99% positive that it still has the original ROM that I installed on it. Which I think was one of the very first Viper builds and hasn't been updated since. I wasn't familiar with Rumrunner before I read the whole thread on it. I had pretty much decided to use Facepalm since I found my old One XL folder(after my post from earlier) with everything already there and my notes stating that I was on the same 1.09 hboot when I used it on my own One XL forever ago. Then I saw your post suggesting Rumrunner so I read up on it to see if it had any additional benefits. It clearly does, but since it's already rooted and ROM'd with SuperCID it shouldn't technically matter which one I use, right? Sorry for the rambling and my likely redundant questions. I've been up for entirely too long and want to be positive I didn't overlook something because of my lack of sleep.

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
If you definitely already have SuperCID, you can use Facepalm or Rumrunner, if not you can only use Rumrunner.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] pside15:
Thanks, that's exactly what I thought. I'll definitely double check it but I'm almost positive it is since it's an AT&T model that was HTC Dev unlocked.

Man, I forgot about how much all this locked bootloader crap sucks.

Thanks again for the assistance. I may not miss all the s-off, locked bootloader stuff but I miss the One XL forums. By far the best section of XDA that I've been a part of.
[AT&T, Rogers HTC One X, Telstra One XL] natgear2510:
I got a AT&T HTC One X complete stock it had 4.1.1 "318"/ hboot 2.14.0000 on it. I have followed the guide got s-off, unlocked, rooted. I flashed TWRP 2.8.0.1 then Viper XL 4.2 & everything is running fine! My 2-day problem is trying to update the Firmware / hboot to 2.18.0000. When I flashboot flash the firmware.zip I get error 92 then the phone reboots to OEM then I immediately flash again. Then I get error 99. I hold the volume & power down force reboot to fastboot the Reboot OEM & try again, error 99. I have tried different cables, uninstalled & reinstalled drivers, etc. I am running Windows 7 x64. Does anyone have any idea what I am doing wrong? My personal direction I am thinking is downgrading back to 4.1.1 stock deodex rooted (so I don't have a firmware /ROM mismatch) OR try to install ElementalX kernel (unsecured non write protected kernel) & try again on current ROM. I also read somewhere that I may need to install an earlier version of TWRP 2.6.0.0? I know I am missing something but not sure what! Any help will be appreciated! I am almost brain dead on a idiotic problem!!!! all I want to do is update firmware!!!! [emoji16]
[AT&T, Rogers HTC One X, Telstra One XL] natgear2510:
Here is my hboot. Thx!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Is that image of your bootloader current? According to that you don't have s-off.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] natgear2510:
Yes! What is the best method from where I am at to achieve s-off? Do I need to start from the beginning again?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
http://Rumrunner.us

You'll probably need to flash the Kickdroid 5.0 ROM first, it has the best success rate.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] mikehd1959:
I'll go out on a limb and say that your phone is still s-on and that is the issue with flashing firmware.
[AT&T, Rogers HTC One X, Telstra One XL] natgear2510:
Thx for all the help & suggestions. I installed Kickdroid 5.0 & ran rummrunner. This kept giving me a fatal error. So I tried sucessfully using Facepalm S-Off method. Then flashed the 2.18 firmware. http://xdaforums.com/showthread.php?t=2155071
[AT&T, Rogers HTC One X, Telstra One XL] Nalin12:
Unresponsive Touchscreen

I have lost the touch screen response of my phone. It was running unofficial cm12 when it happened, the phone was charging at that time while i was using the phone at that time.

It first hanged in the middle of the thing and when i restarted the phone the touch screen was not responding to my touch. All buttons are working absolutely fine but screen is not responding at all.

Phone is working as i can boot into recovery, bootloader screen using buttons. Also i have also tried running a RUU just to check if it was issue with the rom but it's not responding even after RUU.

Now the funny thing is that screen starts responding to my touch on it's own when it wish to.

When I randomly pick the phone and unlocks the device it starts responding for few minutes and the capacitive buttons then start flashing and then it stop responding.

Also it only responds until the capacitive touch buttons lights and the after using for 5 minutes or so the button starts to flash and then it becomes unresponsive again.

Had it happened to anyone else ? I am without the phone atm :(
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It's a bit hard to say what's happened, you could have a loose digitizer cable connection, that'd explain why it works sometimes and doesn't work at other times.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] Nalin12:
That's exactly what i think the problem is, will try to get it repaired locally here.
[AT&T, Rogers HTC One X, Telstra One XL] kanishkaprasad:
htc one x at&t

hey guys im sorry im off the this thread ! and now i maninly needs help from some one !! and here is what happened !! i plugged my original HTC wall chager into 2230 v AC while it was conected to the phone ! and as i plugged the screen went off !1 and i held up the power button adn there after i didnt see the phone charging not even the red light ! and i just smelled the usb port in the charger ! it gave me a fried smell ! and now i think my charging system is fried up ! but im not sure !

when i plug it to computer it say "the power adapter you connected does not support ............................. etc "

what shal i doo !!

can i get the reapair manula of HTC one x at&t

please help me some how !!

it would be a great help for me !!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
So the phone doesn't turn on at all? I think you'll need to have it repaired by a professional.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] mikehd1959:
Notification LED dead?

Hi all,

I ran the *#*#3424#*#* sequence to activate the test mode on the phone to see if the notification LED can work. I haven't seen it light up once. It failed all tests (green, orange, red). Is there any software method to wake the LED up or is it dead? I've tried light flow app from the store with no positive results either.

If indeed the LED is dead, are there any apps that can flash the LEDs behind the home/back/running apps buttons for notification? I'll search for this but thought I'd toss it out there for a recommendation if it exists.

thanks again,

mikehd
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Some kernels have a feature called Button Light Notification (BLN), which is what you're looking for. What ROM are you on?

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] mikehd1959:
I have it on Kickdroid 5.2 with its kernel.

thanks,

mikehd

---------- Post added at 06:41 AM ---------- Previous post was at 06:32 AM ----------

Perhaps this one: ElementalX-8.3.2
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yep, that's the only kernel that's compatible with your ROM and it has that feature.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] kanishkaprasad:
no the phone turn on but wont charge !!! ? all other function are working on the phone
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok, how many different charging sources and cables have you tried?

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] kanishkaprasad:
first i tried the usb from ma Pc it wont charge ! then another samsung charger no luck !! then a apple charger !! no luck !!

ive checked the cable too !! i connected it to my galaxy note its working fine ! and i did viseversa
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You most likely have a faulty usb port on your phone, you'll need to have it inspected and repaired by a professional.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] planetdroid33:
Hey Tim,

This morning i woke up with my phone off and would not charge. I tried many solutions on xda with no good results so far so maybe someone else with more experience can help. I was able to get candykat pushed to phone and my phone was back to charging and everything worked fine. Do to hard times my friend needs my help so i am going to donate the phone to him. I want to ruu back to stock 4.2.2 as i have many of times in the past with no problems, but the ruu fails. The ruu starts fine in fastboot but when it gets to bootloader to install it fails.

( ERROR i receive---(171) usb connection error

The ROM Update utility cannot connect to your android phone. Please check that theusb cable is connected properly between the pc and your android phone.)

Phone details are=

unlocked

evita-soff

cid-11111111

hboot 2.18.0000

Boot Loader Unlocked

Twrp Installed

Edit:::::::Using 2.0 port

Tried Locking Bootloader to no avail. Tried stock recovery also to no avail. Three different oem data cables 2 pcs no luck. All custom roms working great but cannot install from RUU. Any suggestions greatly appreciated......
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Don't worry about unlocking the bootloader or installing the stock recovery, neither are necessary. Ate you using a usb 2.0 or 3.0 port?

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] planetdroid33:
I am using 2.0
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Do you have HTC Sync Manager installed on your PC?

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] planetdroid33:
Edit::::I uninstalled it on this computer have it on other pc both no go.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
How many different RUU's have you tried? And exactly which ones are they?
[AT&T, Rogers HTC One X, Telstra One XL] planetdroid33:
HTC_One_X_RUU_5.18.502.1 Same one i have always used from htc site. this is only one i have ever used
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It might be worth trying a different RUU. You could try the 3.18 one:

http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
[AT&T, Rogers HTC One X, Telstra One XL] planetdroid33:
Ill give it a try. Just heads up that server is DOA...
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Try this one:

http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
[AT&T, Rogers HTC One X, Telstra One XL] planetdroid33:
Good link but no go on ruu as well. Dont know what part of world your in but i dont want to keep you up any later. I really appreciate all your time you took with me though. It is greatly appreciated. Thank you very much...
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm in Australia, it's pretty early here. There's something interfering with your usb connection, whichever PC has HTC Sync Manager installed, uninstall it. Other than that, if you have any other phone drivers or software installed I'd get rid of that too. These problems can be quite perplexing and frustrating, and are very difficult to troubleshoot.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] planetdroid33:
I will look into it and if i get it figured out i will post here what i did. Thank you again for all your help.

:good:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It would indeed appear that the phone hasn't been updated or modified at all, but appearances can be deceiving. So first thing we need to do is check the CID, I'm assuming that you have adb/fastboot already installed on your PC so this part should be a breeze. Put your phone into fastboot mode, connect to your PC, and issue this command:

fastboot oem readcid

It's most likely the stock CID (CWS__001), but you never know. If it is the stock CID we'll need to get SuperCID (11111111) on the device in order to unlock the bootloader because the at&t CID is blocked from having the bootloader unlocked at htcdev. Herein lies the problem. The exploit that is used to get SuperCID for your specific firmware no longer exists, so here's what I'm suggesting:

1. Run the 3.18 RUU, this will update your firmware so you can use a SuperCID exploit that is still available. You'll find the 3.18 RUU here:

http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe

If your CID is anything other than CWS__001

do not

run the RUU on your device, it will brick it. This is due to a bug, basically s-on + SuperCID + jb RUU = brick. Once you have s-off this will not be a problem though.

2. Now that you have newer firmware you can use a newer exploit to get SuperCID, you'll find full instructions in my guide thread here:

http://xdaforums.com/showthread.php?t=2593382

(Section 1 specifically)

Confirm your new CID with this fastboot command:

fastboot oem readcid

It should now be 11111111.

3. Now that you have SuperCID you can head over to htcdev.com and unlock your bootloader.

4. Once you have an unlocked bootloader you can use fastboot to install TWRP recovery on your device. Again, instructions can be found in my guide thread that I linked to above.

5. Once you have TWRP installed you should make a nandroid backup of your current setup, refer to guide thread.

6. Next you need to temporarily install the Kickdroid 5.0 ROM, this is only because getting s-off via Rumrunner s-off has the highest success rate while Kickdroid is installed. Find Kickdroid here:

http://xdaforums.com/showthread.php?t=2400766

7. Now you can get s-off, go to the Rumrunner site and follow the instructions there:

http://Rumrunner.us

8. Now that you have s-off you need to update your firmware using the 2.15 firmware package. Download and instructions in my guide thread.

9. Now you can flash whatever Evita ROM you want to your device.

Seems like a lot of work but unfortunately there's no way around it. Feel free to ask any further questions if you have any.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] Tinyguy:
I'm having trouble trying to get TWRP recovery to stick and boot.

I was trying to flash 4.4.4 PAC-man RC1, using TWRP, but apparently it was not compatible, and It wouldn't install ( i got errors every time). Luckily I had the 4.2.2 AOKP rom in my SD, and that flashed successfully. However after that I was unable to boot back into the recovery.

I can't boot into recovery, it tries to load it, but goes back into the regular Htc boot logo, and boots into my rom.

I have tried multiple ways of flashing the recovery.img, and I tried different versions of TWRP.

At&t Htc One X

EVITA PVT SHIP S-ON RL

HBOOT - 1.09.0000

RADIO-0.16.32.09.01_3

OpenDSP-v25.1.0.32.0405

eMMC-boot

Apr 2 2012, 21:08:24

My ROM:

4.2.2

aokp evita nightly 2013-06-06

Kernel:

3.0.80-00019-g4e39f19
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The reason the PACman ROM failed (and also why attempting to flash any other recent ROM would fail) is because your firmware is very outdated. So once we've sorted out your recovery problem you've got some work ahead of you to update your firmware. You should read the Evita FAQ thread that's at top of q&a section.

Instead of saying "I have tried multiple ways of flashing the recovery.img, and I tried different versions of TWRP", you need to be more specific, because saying that is essentially saying nothing at all. I need to do know exactly which methods you've used to flash the recovery, I need to know exactly what the results of using those methods were, I need to know exactly which versions of TWRP you've attempted to flash (the full filenames).

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] schadenfreude2250:
Infinite reboots on One XL

Happy New Year! My first post, and it looks like the first post to this thread for 2015.

I'm hoping someone can help me out. I have a One XL (ATT imported to Australia). All was pretty fine until today - I had CID-1111111, it was rooted, and ViperXL was installed. The annoyance was that it occasionally lost the cellular signal and sometimes (rarely) rebooted. I had to go and mess with it.

Today these minor annoyances got the better of me so I set out to update the ROM. To do this I needed to update HBOOT (the Cyanogenmod Wiki recommended to 2.18 - even though the stable releases don't work without a hack of the updater-script). Anyway, HBOOT 2.18.0000 is what I have now along with S-OFF.

All was fine to that point. I then set out to install a Cyanogenmod ROM. I chose the RC2 ROM 10.1.3-RC2. I flashed it using clockwork recovery 6.0.3.1 after allowing HBOOT 2.18.0000 to be recognised without the "ERROR 7" issue by modifying the updater-script and re-zipping the ROM. Flashing this rom resulted in infinite reboots of the phone. I tried Cyanogenmod 11 and got "ERROR 0" and I couldn't identify why so I gave up on that avenue.

I remembered when I first started working with the phone that boot.img needed to be flashed using fastboot. Forums I've read indicated that this was needed because of S-ON so I didn't think it would help but couldn't imagine how it would hurt so I gave it a try. No luck. Infinite reboots.

Reading further, TWRP seemed to be the preferred recovery for this phone so I set out to flash that instead. None would flash correctly - the HTC logo would appear followed by a black screen. I thought maybe the latest clockwork recovery would be the go so I flashed 6.0.4.8. Same deal as TWRP: HTC logo followed by black screen. Re-flashing 6.0.3.1 got me back to what I thought was stable ground but a new issue appeared. clockwork couldn't mount the /sdcard partition.

I mounted the phone on my linux box and re-formatted the /sdcard partition as fat32 using parted. This hasn't helped. I can write to the /sdcard when I mount it on the linux box but I can't flash ROMs from there because /sdcard won't mount in clockwork recovery.

Sideloading seemed the next best option so I sideloaded ViperXL, thinking that at least I'd get some sleep tonight if I got back to what I had before. Sideloading of ViperXL gives me:

adb sideload ViperXL_4.2.0.zip

* failed to write data 'protocol fault (no status)' *

In contrast, doing the same thing (sideloading) with cm-10.1.3-RC2.zip works fine - but results in the perpetually rebooting phone.

I'm out of ideas. I don't know how to get over the /sdcard mounting issue if it works fine when mounted as a USB device. I don't know how to manage the rebooting phone issue if flashing boot.img isn't the remedy. I don't know why only one version of one recovery image works. I don't know if any of this is related to S-OFF or the HBOOT upgrade. Finally, I don't know why I get "Error 0" when I try to flash a legitimate ROM from Cyanogenmod (among others).

Any and all advice welcome.
[AT&T, Rogers HTC One X, Telstra One XL] DanGeorges:
No OS installed

Hello,

I made an error and erased the System (OS) when giving my ATT One XL to my son. He wanted a clean slate (including nothing on the SD card)

I didn't realize that this would wipe the OS as well (never did THAT before).

I have S-OFF, Super CID, unlocked bootlader, TWRP recovery installed, etc.

How can I get a file copied to the SD card (ROM)? I don't seem to be able to do that.

I was able to fastboot the Firmware from Turge's 4.2.2 ROM, but I don't believe that's enough to run an OS...I have the Turge ROM zip file, but am unable to get that to my phone.

I searched the forums, but it seems that all the solutions depended on having the ROM file on the SD card, which I can't do.

Any help is greatly appreciated!

Thank you!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Firstly, did you only update your hboot to 2.18 or did you update your firmware? Exactly what method did you use? It's the firmware that is meant to be updated, not just the hboot.

Next, what's the exact full filename of the cyanogenmod ROM that you attempted to flash?

At the start of your post you mention the catalyst for all of this being the signal loss and random reboots that you experienced on Viper. Had you read through some of the Viper thread or the Evita FAQ thread you would have seen that all you needed to do was update your firmware, this would have taken 30 seconds, and you probably wouldn't be in the mess you're in now.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Just boot into TWRP recovery, connect to your PC or usb OTG drive, and copy the ROM zip to the phone.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] DanGeorges:
Hi Timmaaa,

That's my problem - I can't seem to find a way to copy the file to the phone via TWRP.

I've tried mounting the data, USB drive, etc, but no luck seeing the phone.

Everywhere I've read indicates that TWRP should be able to have an ADB mode. I've yet to get it to work.

I'm using TWRP 2.7.0.8.

Thanks, and happy new year!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Update TWRP to the latest version, which should have MTP enabled so it should mount as a drive automatically.

Transmitted via Bacon
[AT&T, Rogers HTC One X, Telstra One XL] DanGeorges:
Thanks Timmaaa.

I'll try that.

Dan

---------- Post added at 09:52 PM ---------- Previous post was at 09:14 PM ----------

Thank you Timmaaa,

That worked! I'm back up and running!