yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I know its too late in your case. But if you are rooted, or want to root, never accept any OTA without doing the proper research.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Updated post #1. The 3.18 RUU was just posted on the HTC website (yesterday?).

The 3.18 RUU also appears to brick the phone, if you have SuperCID and S-on.
[AT&T, Rogers HTC One X, Telstra One XL] DvineLord:
it makes no sense that the ota/ruu would brick you phone since the ota/ruu check for supercid in the updater-script.

assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,

"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,

"77777777" , "88888888" , "99999999" ,

"CWS__001") == "t");
[AT&T, Rogers HTC One X, Telstra One XL] Megadoug13:
Yeah... Sadly I was the VERY first one to brick :( but I learned from that and luckily at&t will be replacing my phone
[AT&T, Rogers HTC One X, Telstra One XL] aaronDroid80:
bummer. I just got a HOX back in January (my first HTC phone), and I've been trying to research the whole unlocking, rooting, s-off stuff. I took the OTA when it rolled out, and I was just getting ready to start the process so that I could flash AOKP. Guess I'll have to wait a bit now. Thanks for the info.
[AT&T, Rogers HTC One X, Telstra One XL] nlsolja123:
WELL im bricked now, it would have been nice if this was in the ROM section of the htc one x forum......
[AT&T, Rogers HTC One X, Telstra One XL] eraste:
Its not allowed to be there per XDA rules. Its unfortunate you bricked your phone. I agree more education for newer users is needed. Everyone should check this section and the q&a before flashing anything just to see if anyone else is reporting issues. I for one am never first to try something new for this very reason!
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
That what I say.

Supercid has never bricked any of my phones either and they have taken all OTA's fine.

I am always at a loss to explain what it is that is causing bricks but it should not be supercid and many people update fine with supercid.

To me it always screams that supercid was a side effect of another unofficial modification that the user has done. It could be that they are skipping upgrades. Eg early 1.xx ROM and updated directly to 3.xx skipping the second 1.xx and 2.xx. Where supercid was only the users gateway in pulling that move off. Supercid alone should not be causing bricks, HTC designs updates to support supercid.

Then again apparently supercid is the only reproducible variation so far. I have not seen anyone claiming the OTA bricked and they did not have supercid. But is that simply because users that modify stuff are typically always on supercid and it is users that modify stuff that get bricks?
[AT&T, Rogers HTC One X, Telstra One XL] zounduser:
Re: [Public Service Announcement] Read before installing the AT&T Jellybean OTA or R

The jb ota is not rootable at the current moment. Correct?

Sent from my ADR6425LVW using Xparent Skyblue Tapatalk 2
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
Correct.
[AT&T, Rogers HTC One X, Telstra One XL] jerrycoffman45:
thats correct
[AT&T, Rogers HTC One X, Telstra One XL] uzair_rock:
So my phone got bricked as well, due to the very same reason. Is there any possible way I can get my pictures back i.e recover them, i had a lot of them and didnt back them :(...??
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
If you can unbrick via JET or jtag, I believe your sdcard data should still be there. Until you can boot up, however, there's no way to get to the files.
[AT&T, Rogers HTC One X, Telstra One XL] zounduser:
Re: [Public Service Announcement] Read before installing the AT&T Jellybean OTA or R

How did u brick exactly?

Sent from my ADR6425LVW using Xparent Skyblue Tapatalk 2
[AT&T, Rogers HTC One X, Telstra One XL] Megadoug13:
I regret updating so very much... I didn't come to realize that there was no exploit :(
[AT&T, Rogers HTC One X, Telstra One XL] Mister J:
At least you didn't permabrick (for now) like a lot of other people. You can also disable apps, which is similar to freezing them in Titanium Backup. Hang in there, I'm sure someone will find an exploit.
[AT&T, Rogers HTC One X, Telstra One XL] jabman13:
I was on the general jb discussion, and a dev has found a temporary root so it might not be long. If you want more info, just head over to that forum in att one x then the everything jb discussion.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I just read the last couple pages of that thread, and there is nothing that states that a temp root has been found, or even close.

If a dev finds temp root, we have root. There is no "it might not be long" if we have temp root. Temp root means we can change CID, which means we can unlock the bootloader and root. But temp root is the critical path here.
[AT&T, Rogers HTC One X, Telstra One XL] Megadoug13:
Actually.... I did I am on phone number 2 and if I had only read that s-off would save my butt... I would have went for it. Infact I didn't know I had supercid.
[AT&T, Rogers HTC One X, Telstra One XL] uzair_rock:
After installing the JB update from at&t :( but I got it unbricked through JTAG. Works great now!
[AT&T, Rogers HTC One X, Telstra One XL] calientecafe2001:
You will "brick" your phone for sure. There is no bootloader for the new OTA. I have seen post where people say have rooted with 4.1.1 but it's not possible at this point because you cannot unlock the bootloader.
[AT&T, Rogers HTC One X, Telstra One XL] jerrycoffman45:
i hope you miss typed there is a bootloader with the ota there is no exploit for jb yet
[AT&T, Rogers HTC One X, Telstra One XL] azraelpc2:
Bricked my OneX last week. Downloaded RUU from HTC website and ran that on a re-locked bootloader, but rooted and SuperCID. :( If only I had done the S-Off exploit as well. Alas. Such is the price of learning.

Sending off for JTAG fix (and S-Off) on Monday. Getting by with a Motorola Atrix HD until then.
[AT&T, Rogers HTC One X, Telstra One XL] jrlatta:
i sent my phone off for a jtag repair and requested for s-off for another $10, if they send my phone back s-off but with the 3.18 firmware what will i need to do to get it rooted and viper back on it again? i requested s-off so i wouldnt be screwed if they did upgrade it but im unsure of the rooting process with jellybean. i dont think i still have my unlock token saved on my computer anymore
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
If they can bring the phone back, and its still SuperCID, none of that even matters. Just unlock the bootloader via HTCDev.com again. And/or S-off yourself.
[AT&T, Rogers HTC One X, Telstra One XL] Herc08:
I remember when I first got the One X. I only got it to experiment on JB. But what I did not know, was that JB was only on the One X+ at the time. So I Google'ed, and Google'ed, and did some more Googling. All the news about the JB update coming to AT&T was rumor, and only escalated once the Rogers got theirs. So I was stock on ICS for a quite a while. Then that is when I discovered rooting. Not only did I learn so much more about my phone (such as the codename, yes call me stupid), but I was able to flash others roms as well.

My point is, why do we even care about installing the OTA, if we are already at this site? Why would people even consider upgrading to something new without checking to see if it is compatible. Just like iPhones. When iOS 6 came out, it was only on pre-A5 devices. Rule of thumb when dealing with mobile devices: NEVER UPGRADE UNTIL YOU DO RESEARCH!

With that said, I don't see why any rooted, with SuperCID would want to install this update. After all, it is just 4.1.1. There are plenty of roms that support 4.2.2. BUT, if you are the type who have to have Sense and JB, then ViperXL or Newts fully supports the best of both worlds.

Sorry about my rant, but I just cannot figure out why someone who rooted their phone, intentionally wants to do an official update.
[AT&T, Rogers HTC One X, Telstra One XL] Megadoug13:
Listen not everyone had root. My phone came and as soon as i clicked update i realized what i just did. Some people get their phones with the jelly bean update and they want custom roms. What are they to do?
[AT&T, Rogers HTC One X, Telstra One XL] wolverine9827:
My wife's came this way.

I can understand if I performed the OTA and screwed myself

but AT&T decided to pre-screw me on this one....

Never again will I get a motorola, htc, or any other phone that has a locked BL

Samsung all the way for me....

And of course now that I have my SGS2 Skyrocket all tricked out and screaming, my wife's OneX's is giving her fits so we'll be swapping phones! UG! I think we'll be returning the OneX... the damn things battery only lasts for about 4 hours!! Piece of junk! Damn, and HTC's used to be among the best!
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
This PSA is explicitly directed toward people who are thinking of installing the JB OTA or RUU, so its pretty apparent that Herc08 is thinking of those people. Not those that get JB out of the box.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Really not the appropriate place for this rant, as it has little or nothing to do with the OP.

Also, there is obviously some hardware defect or software glitch on your wife's phone. Which can happen with any manufacturer. I get 48 hours plus on my One X, no problem.
[AT&T, Rogers HTC One X, Telstra One XL] Herc08:
First off, i want to apologize if i offended you are anyone else. My rant went towards those who are rooted. In the OP if states, do not upgrade if you have Super cid but s on. So in this case, you are already rooted, so why upgrade?

It is the the same thing with iphones. When ios 6 came out, everyone was quick to update, and lost their jailbreak in the process.

Thank you.
[AT&T, Rogers HTC One X, Telstra One XL] jrlatta:
i thought everything on my phone was wiped out at the moment? so if it still has supercid and they upgrade it would it not just brick again? or would my previous s-off still remain also?
[AT&T, Rogers HTC One X, Telstra One XL] jbatacan:
Just a bummer that samsungs build quality isnt as solid feeling. Wish we could have motos build quality, htc design, and samsung/odin software. :good:
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I frankly don't know much about jtag, since I always read before doing anything to may phone, and therefore I've never had to do it. That is why I conditionally say "if" in my previous post. SuperCID survives a lot of things (including updating hboot), but don't know if it will still be intact in your case.

What do you mean "previous S-off"? If the phone was S-off, it shouldn't have bricked.
[AT&T, Rogers HTC One X, Telstra One XL] jrlatta:
My phone was s-off, I was running venom rom and installed a kernel out of the hub and when it was done it gave a bunch of errors and shut off , tried everything to revive it . Ubuntu wouldn't show any partitions and under my devices it was stuck in Qshub thing which everyone says it's bricked. I wasnt carelessly installing anything on my phone

---------- Post added at 10:14 AM ---------- Previous post was at 10:12 AM ----------

I thought the same thing about s-off and not being able to brick, apparently you can
[AT&T, Rogers HTC One X, Telstra One XL] Megadoug13:
It's called the HTC One lmao. Go buy one. I am
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
You said none of this before. I thought you were saying you bricked due to RUU or OTA.

As already mentioned, I really don't know much about jtag. But there are others here that do. I'd suggest posting the question in the Q&A section, where it will get more visibility.

At a minimum, the repair service should be able to tell you if they will give the phone back to you S-off or not, SuperCID or not, what firmware version, etc. As long as its s-off, you're fine. If its 3.18 and SuperCID, you are still ok. If its 3.18, S-on, and no SuperCID, you won't be able to root with the current methods.

That is not what I was trying to say. S-off doesn't mean you can't brick. Phones can simply stop working for any number of reasons. Or you can do something like flash the wrong radio and brick the phone. S-off or s-on, sometimes it doesn't make a difference.

What I was trying to say was RUU or OTA with S-on and you

will

brick. But if you are s-off, you shouldn't have bricked for

that particular reason

. But that is not what you were doing, anyway.
[AT&T, Rogers HTC One X, Telstra One XL] jrlatta:
oh ok, thanks, i requested s-off so i should be good if they do what i payed for. i just need to find the proper way to root again, your help is appreciated i guess i should have told my story from the beginning.
[AT&T, Rogers HTC One X, Telstra One XL] hx4700 Killer:
If you are S-Off just install TWRP 2.3.3.1 and then flash a root zip file by putting it on to your sdcard on the phone then boot to TWRP and flash the zip. I used this one: http://www.4shared.com/zip/6qQDRapA/CWM-SuperSU-v099.htm
[AT&T, Rogers HTC One X, Telstra One XL] jrlatta:
id like to install twrp and just install a new rom all together.. i didnt know it was as simple as just flashing recovery again
[AT&T, Rogers HTC One X, Telstra One XL] beemboy:
I have a One X I inherited from a colleague. It had TWRP with CM10 on it. I wanted to take it to stock AT&T JB ROM; I'll have to admit I wasn't aware of the S-OFF/S-ON thing. I read through forums and somehow did not find this page in my research. The instructions I found said to lock the bootloader and run the 2.2 RUU which succeeded, followed by the newer JB RUU. The latter also succeeded, and at the end of the flash it went into the dreaded DLOAD mode and now my phone looks bricked.

I understand I may be SOL. Exactly what are my options here? I find it hard to believe I have an expensive paperweight :-/

Thanks in advance!
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
Jtag. That's it, unfortunately.
[AT&T, Rogers HTC One X, Telstra One XL] hx4700 Killer:
I called HTC and sent it to warranty repair depot and they fixed it. I think once its dead like that even they can't tell locked/unlocked statuses. There are no partitions, nothing.
[AT&T, Rogers HTC One X, Telstra One XL] marcur12:
Well I wish I could have seen this post a few hours ago before I took the OTA update :(. I tried using this method (http://unlimited.io/qhsusbdload.htm) but no luck. I'm going to go to the AT&T store tomorrow and try to BS my way to a replacement phone. If that doesn't work, I'll call HTC and see if they can repair it for me at no cost. I can't afford to play $60 dollars for the jtag service even though it sounds nice :S.

edited: has anyone tried this method: http://xdaforums.com/showthread.php?t=1966850
[AT&T, Rogers HTC One X, Telstra One XL] jay_ntwr:
Redpoint, thanks for the PSA! I just had my One X screen fail (everything worked fine with the phone, just couldn't see anything on the screen) and AT&T gave me a new phone with 4.1.1, the 3.18 release. Last time was obviously easier to root but I'd rather install a custom ROM anyway and blow away the 3.18 release can I just use the HTC All-in-one kit to do that or will that brick me too? I'm a little confused if this only applies to phones that are being upgraded to 3.18 or if it applies to phones that are already 3.18 also.

EDIT: Sorry, it looks like there's nothing to do but wait for an exploit for the 3.18 release. I found that buried in the All-in-one kit thread.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
As you've already determined, there is currently no method to bypass the locked bootloader, or change CID (in order to unlock bootloader) on 3.18. So that means you can't flash any custom ROMs.

For X-factor and the All-in-one kit, root was the key (allowed changing to SuperCID, and therefore allowed bootloader to be unlocked). So since 3.18 can't be rooted, none of this is possible. There is also some talk that as of 3.18, the CID itself is write protected, so even with root, it can't be changed.
[AT&T, Rogers HTC One X, Telstra One XL] Megadoug13:
Hey thank you for listening to my words haha I'll post a picture of my hboot.... It makes me so mad
[AT&T, Rogers HTC One X, Telstra One XL] snb_android:
HOXL AT&T Phone bricked

I have HOXL AT&T phone with

Android 4.0.4

HBOOT-1.14.0002

RADIO-0.19as.32.09.11_2

OpenDSP-v29.1.0.45.0622

I rooted the phone with OneXRoot method. Installed twrp recovery, took backup and again relocked the phone.

Got the JB update for this phone from HTC US site (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio _0.24p.32.09.06_10.130.32.34_release_signed_With_P artial.exe) and installed it successfully. The installer said successfully updated the ROM and your phone will reboot. The phone actually turned off but never came back.

When connected to Linux PC I find the following log:

[ 990.879242] usb 1-2: new full speed USB device using ohci_hcd and address 4

[ 991.053131] usb 1-2: New USB device found, idVendor=05c6, idProduct=9008

[ 991.053145] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 991.053155] usb 1-2: Product: QHSUSB_DLOAD

[ 991.053163] usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM

[ 991.379469] qcserial 1-2:1.0: Qualcomm USB modem converter detected

[ 991.379771] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0

It is in QHSUSB_DLOAD mode.

Is it possible to recover this HOXL? Appreciate any kind of help on this. If this is not the right forum please suggest the appropriate forum with link, if possible.

Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] mkalbarc:
Just went through this with my phone "QHSUSB_DLOAD". If you don't care about saving anything on the sd card and are still under warranty I'd say send it in to htc for repair. After a day of them receiving the phone it was shipped back to me fixed. Just incredible turn around time. If there are things that you want to try and save that you never backed up then try the mobiletechvideos company. They were unable to fix my phone but it was worth a shot cuz I had photos I didn't want to lose. I only lost shipping cost and they refunded my money.
[AT&T, Rogers HTC One X, Telstra One XL] snb_android:
Thank you for the info friend. But I would like to try on my own. If there is some procedure which can help please suggest. (any urls, videos etc...)
[AT&T, Rogers HTC One X, Telstra One XL] myusernam3:
http://xdaforums.com/showthread.php?t=2283760

To those previously stuck on this OTA, enjoy your HTCDEV unlock.
[AT&T, Rogers HTC One X, Telstra One XL] anield:
RUU relock

I have AT&T phone with

Android 4.0.4

HBOOT-1.09.0000

RADIO-0.20os.32.09.10_2

OpenDSP-v28.1.0.32.0504

I rooted & unlocked bootloader (S-OFF & supercid) last year so I could run CleanROM 4.5.

Attempting to install 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe) so I can try out CleanROM 6.5 but keep getting 159 IMAGE ERROR.

After much searching it appears I need to relock bootloader before attempting 3.18 RUU.

"fastboot oem lock" seems to work initially (*** RELOCKED ***) but after a reboot it goes back to *** UNLOCKED ***. Do I need to go back to stock 1.85 for relock to stick? If so how?

I think I am close, but I don't want to wing it and end up bricked...
[AT&T, Rogers HTC One X, Telstra One XL] Egrier:
My phone is S-off and unlocked and I ran the 3.18 ruu just fine. Boot into bootloader and try it.
[AT&T, Rogers HTC One X, Telstra One XL] anield:
Thanks. I've been booting to bootloader before running RUU. Were you stock or custom when you updated to 3.18?
[AT&T, Rogers HTC One X, Telstra One XL] Egrier:
I was on a custom Rom but I kept having random reboots. When I updated to 3.18 using the ruu, that cured the reboot problem.
[AT&T, Rogers HTC One X, Telstra One XL] anield:
Ok tks, so I guess stock is not all that important. Maybe I'll try using a different PC to do the update.
[AT&T, Rogers HTC One X, Telstra One XL] Gjorge89:
Hi. I bricked my phone and send for jtag, and now looks like this

***LOCKED***

EVITA PVT SHIP S-OFF RL

CID-11111111

HBOOT-1.01.0000

RADIO-0.15.3201.09

OpenDSP-v16.1.0.32.0304

eMMC-boot

Mar 9 2012,16:44:40

so I want to ask if it can upgrade without to be bricked again, or what to do to prevent it from bricked again.. Th
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
You are S-off, so you are relatively safe from bricking from the update. At least, you will not brick from the SuperCID + S-on combination.
[AT&T, Rogers HTC One X, Telstra One XL] havenok:
Thanks for the post redpoint. I was just about to attempt to root my HTC OneX when I began reading your post to prepare. Its a shame some of us are stuck with the new update. It has been eating my battery like there is no tomorrow, leaving me with barely a few hours worth of time without constantly using the Task Killer. I don't suppose anyone else has heard any news concerning a possible root solution?
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
There is one on the first page of this forum.
[AT&T, Rogers HTC One X, Telstra One XL] havenok:
Yes but it uses linux command shells and I am unfortunately not a Linux user. This seems to be very much still in testing phase as while there are a few saying they got it working, there are just as many if not more commenting with issues. I posted here as it was the listing concerning the JB issues in the first place and hoping that someone had more news as to any JB roots beyond that. If that is it that's fine. It just seemed more appropriate to post here.
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
There are windows instructions a few pages in.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I haven't read the whole thread. But from what I have read (my time is very limited right now), my takeaway is that the method works. Some people are having issue. But that will always happen, for any root method.

By the way, the dev had posted the root method originally in the General forum on May 17, but subsequently re-posted it in Development on May 18, this time with "testing" caveat removed. I think he just never removed the "testing" label from the original post. If that makes you feel any better. lol

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

You can wait for the process to become a bit more refined, or for some things to be automated. But that thread is probably your best source of new information. Since somebody has already found a method, its unlikely another developer will taek the time and effort to discover a different one. At most, another dev might take the method and simplify/automate it.

I've updated the top post of this thread to include the root method.
[AT&T, Rogers HTC One X, Telstra One XL] myusernam3:
As far as I'm aware, my method hasn't resulted in any bricks although it admittedly needs some noob-proofing.

If you want to try it, go ahead. Nobody has broken anything yet. I'll help if something goes wrong.
[AT&T, Rogers HTC One X, Telstra One XL] mightyiam:
Getting my head around this

UPDATE: I'm working on it: Got SuperCID, got S-OFF.

Hi,

I currently have

*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.18a.32.09.01_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34

Running

CyanogenMod 10.1-20130309-NIGHTLY-evita

.

And I want to install the latest CyanogenMod nightlies, which are stated to require

I've jumped through a few hoops in the past with RUU's, various procedures and updates on various phones but this is getting too complex.

Can you please help me answering these questions?

What I should do before installing the required RUU

What RUU should I install

Blessings,

Shahar
[AT&T, Rogers HTC One X, Telstra One XL] exad:
You would first need to acquire S-OFF, otherwise you'll brick

Then download the RUU .exe file for your carrier and run it.

Most carries do not have a 3.18 RUU exe file. In that case download the latest version RUU exe file available and then either manually flash the OTA THROUGH STOCK RECOVERY NOT TWRP OR CWM. Or just download and install over the air.