[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
The AT&T Jellybean OTA (firmare 3.18) is finally rolling out. If you plan to install it be aware of the following:
1) If you have SuperCID, installing the OTA may result in a brick. Its not completely clear yet exactly what the brick conditions are. People with SuperCID and S-off appear to be okay. Which makes sense, because the issue is with CID check, and by definition all security checks should be bypassed with S-off. Bottom line: It is not recommended to install the OTA if you have SuperCID, unless you first do S-off.
UPDATE (March 21, 2013): The 3.18 RUU was just posted on HTC's website. It appears to also brick the phone if you are SuperCID and S-on.
2) Nobody has yet posted that the X-factor root exploit works or not on the Jellybean OTA. HTC patched the previous root exploits with every other OTA to date (1.85 and 2.20), so its very possible that they have done the same with X-factor.
If this is the case (X-factor does not work), and you are not already bootloader unlocked and/or S-off, and you install the OTA, you will be stuck without root until a new exploit is discovered and posted. This happened with the 2.20 OTA, and many folks here were stuck without root for (I believe) 3+ months until X-factor came out. If you are not already rooted (bootloader unlocked, S-off, etc.) and think you may want to be, it is highly recommended you do so before installing the 3.18 OTA.
UPDATE (March 10, 2013): Its been confirmed that X-factor does not work to root on the 3.18 OTA. Root (unlock bootloader, S-off, etc.) before the OTA as warned above, or you're screwed.
UPDATE (May 17, 2013): A root method has been achieved for 3.18. See here:
http://forum.xda-developers.com/showthread.php?t=2285086
http://forum.xda-developers.com/showthread.php?t=2283760
3) OTA Rootkeeper seems to be working for some people, but its not clear. It didn't work on 2.20, so don't assume it does. If for some reason you are rooted but not bootloader unlocked or S-off (for instance, you are on 1.73 or 1.85 and used the corresponding root exploits), its recommended you unlock the bootloader and/or S-off before installing the OTA, to ensure you retain the ability to root.
4) Frankly, I don't personally recommend installing any OTA if you are rooted, on a custom ROM, etc. If you are rooted/bootloader unlocked, and want to try the stock AT&T Jellybean ROM, just flash the rooted stock ROM here (flashable in recovery). Better yet, the first custom ROM based on 3.18 is already posted here, with others sure to come.
Some people like to install the OTAs anyway. To each his own. Just be aware of the warnings as stated, do some more research, and plan accordingly.
5) Root and custom recovery interfere with downloading and installing the OTA. Your best bet to install the OTA is to return to stock to properly install the OTA, by relocking the bootloader (if unlocked) and running the RUU.
6) The situation is very fluid. The OTA is just starting to roll out, and not many people have installed it yet (nobody had posted that the tried X-factor, etc.). So some of this information may not be complete or totally accurate. As events unfold, and users post their experiences on this forum, I will try to update this post accordingly.
Cheers and good luck!
When i took the ota m'y bootloader hot upgraded to 2.14 would it ne a voir idea to downgrade?
Sent from my HTC One X using xda premium
slojko said:
When i took the ota m'y bootloader hot upgraded to 2.14 would it ne a voir idea to downgrade?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I was on 2.14 I could not flash radios. I am s-off so I just downgraded my hboot to 1.09 using Liam's thread. All good now - you may want to downgrade your touch panel firmware as well. It's easy enough.
How do you do downgrade the hboot and also does it matter which one you do first (touch panel or hboot)
Sent from my HTC One X using xda premium
Guess I'm just SOL
Redpoint it seems ex factor does not work for new 3.18 att ota.
Complaints http://forum.xda-developers.com/showthread.php?p=38925325here
Note 2 ftw
Thread stickied
Good write-up, thread stickied so hopefully will save some people.
slojko said:
How do you do downgrade the hboot and also does it matter which one you do first (touch panel or hboot)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2159863
But really, there is a search function and index for this sort of thing.
Lowers flag half way to all those who refuse to read and listen to advice, may you find peace in the afterlife
Sent from my HTC One X using xda premium
As long as you're s-off before you start, you're fine.
I re-locked, 2.20 ruu'd, flashed the ota, unlocked again, and flashed a rooted rom last night in about half an hour.
IMO every tutorial in this forum need to be updated with "First, s-off your phone." This would solve so many issues.
guess it was a bad idea to install the JB update on my warranty replacement HOX :laugh:
eldeeinc said:
guess it was a bad idea to install the JB update on my warranty replacement HOX :laugh:
Click to expand...
Click to collapse
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.
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.
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");
Yeah... Sadly I was the VERY first one to brick but I learned from that and luckily at&t will be replacing my phone
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.
WELL im bricked now, it would have been nice if this was in the ROM section of the htc one x forum......
nlsolja123 said:
WELL im bricked now, it would have been nice if this was in the ROM section of the htc one x forum......
Click to expand...
Click to collapse
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!
DvineLord said:
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");
Click to expand...
Click to collapse
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?
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
so i managed to solve my recovery problem. i finally got twrp 2712 onto my device.
bootloader is unlocked
recovery on
superuser on..
hboot 2.15 s-on
i dont remember dealing with supercid when i rooted my old htc incredible.. from what im reading it allows us to use other carrier roms on the device?? im on tmobile and comfortable with that.. is modifying the CID actually necessary? im not planning on receiving any ota's n such.. just want the ability to flash radio's if need be and roms.. If i can skip CId and go to s-off that'd be fine with me, unless its needed for something else.. Will Ibe able to s-off without CID modified? cracking this ****er has been a little bit more difficult the past few phones ive had to do.. thanks much for the help..
As a noob, I installed CM 11 in February without s-off or super-cid (was too afraid to brick my phone). CM works great without s-off, but you need to flash boot.IMG on every update via fastboot.
I did s-off with rumrunner recently without Super-CID. Read my post here: http://forum.xda-developers.com/showthread.php?p=56185478<br/>
so in moonshine i was getting nowhere.. i had no inclination that the Yes/No were case sensitive to be executed....
Currently in test 3, mhy 7th row of **********..
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).
I have an AT&T HOX running the original stock ICS 4.0.2 The phone is rooted, bootloader unlocked and has Supercid.
I would like to install one of the new Cyanogenmod ROMs that require HBoot version to be 2.14 or newer, but I'm having problems. I can't use an RUU to upgrade to 4.2.2 or whatever, because I'm supercid and will probably brick the phone. Facepalm/Rumrunner/Firewater/moonshine etc, S-Off tools do not work with this particular kernel for whatever reason, and I just get the "Please install an 'unsecure kernel" advice at the end of the attempt.
So, basically, I can't get S-Off because none of the tools work with my OS version, and I can't update my OS via the normal channels because of having supercid, and I can't upgrade my firmware because I'm not S-Off. Kind of a catch 22-22-22 situation.
I'm not even sure what question to ask at this point, so I'm open to any advice you guys are willing to offer in regard to upgrading to HBoot 2.14 to meet the requirements to install CM 11 on my phone. My current HBoot version is 1.14
**Edit** Current firmware - 2.20
Thanks in advance.
Maybe a solution
Well, I finally found a thread by someone with a similar situation. It looks like the procedures outlined by Heisenberg in his replies did the trick for that particular person, so I'm gonna give that a try I guess. I'm not sure how I missed that thread after all the searching I've done before now, but for anyone who might be interested:
http://forum.xda-developers.com/showthread.php?t=2218990
Thanks
Try to flash Kickdroid 5.0 as outlined in the other thread, then you should be able to get s-off.
Would somebody please advise me about the pro's and cons of changing my HBOOT version.
I can successfully root my phone via The Revolutionary method after downgrading using an earlier RUU etc.
What I am not clear about is whether I then need to flash an ENG HBOOT after this process .... which version.... why I should do this ?
If I have the "wrong" HBOOT installed will that prevent certain ROMs from running correctly ?
Do I need a specific "level" of HBOOT for a GB based ROM to run and another for an ICS based ROM
Choosing your HBOOT Version
I don't know absolutely everything about this, but since you've waited over a month with no replies, I'll tell you what I know. It should be enough to answer your question, if you're looking for something more advanced then you may need to keep looking!
The original HBOOT version is 0.98.00000, this is the HBOOT version that you need if you want to S-OFF your phone as the later version, 2.000.00002, blocks the vulnerability that allows the Revolutionary exploit to work. S-OFF unlocks root level access to the phone permanently, allowing you to flash new ROMs directly from the SD card without having to use ADB and USB Debugging to flash the boot image every time.
Basically, if you want S-OFF you may need to downgrade your HBOOT to 0.98.0000 if that's not the version you already have.
The phone originally shipped with Android Gingerbread 2.3, this can be upgraded to a certain point, beyond which, the newer version of HBOOT is required. I don't know which version is the crossover point but I'm sure a quick search of the forums will provide the answer, I'll leave that up to you (I think the main reason you haven't had any replies is that ALL this info is already available in the various guides in the forum, so people think you're being lazy not looking for it!).
So....
Unless you're trying to do something out of the ordinary, the most common approach is a follows;
Unlock bootloader on HTCDev.
Downgrade to HBOOT 0.98.00000 (f necessary).
Use Revolutionary to gain S-OFF.
Upgrade to HBOOT 2.000.00002 (not necessary for Android 2.3 but later versions require this)
Download and flash new ROMs directly from the SD card using custom recovery, such as TWRP or Clockworkmod.
I hope this helps, I do understand that it's not always easy piecing things together from multiple forum threads to learn about something new, but ALL the info you needed IS already available on here.
There are some excellent guides and tutorials here on XDA Developers, both official and unofficial. I would say if you don't already have a bit of knowledge then stick to the official guides and you can't go wrong.
Hint: Try searching the forum for [Guide]