Related
[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
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Bubbled said:
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
Click to expand...
Click to collapse
Unfortunately the answers are no and no. JB is decent even on fully stock AT&T, you will just have to look the other way when scrolling through your app tray
I don't think the current root methods allow for the 3.18 build to gain root. Might be in the 2.20 boat all over again until someone can find a definite procedure.
soooooooooooooooooooooo lame. my rezound had viper rez rom and it was based off one x jb but had all the tweaks and stuff so right now its like a major downgrade lol
guess i'll cry and wait for the HTC One to come out later this month, since i only grabbed the one x cause it was literally 11 cents at walmart with a 14 day return and my rezound is acting up and randomly restarting/tanking battery!
sigh
thanks for the info though Groovy
Bubbled said:
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Click to expand...
Click to collapse
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
lightflier said:
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
Click to expand...
Click to collapse
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
iElvis said:
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OK...
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Sent from my Nexus 7 using xda premium
panda_mode said:
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Click to expand...
Click to collapse
Damn that's annoying! If that were me I would sell my AT&T phone and with the cash buy an overseas One XL model with 32GB
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Sent from my VENOMized HoxL
area51avenger said:
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Click to expand...
Click to collapse
I suppose it doesn't hurt to try. Otherwise, I'd just take the phone back, if root/S-off, etc. is important to the OP. I assume 11 cents is a subsidized price. So no point in using up an upgrade on a phone that can't be modded, if he wants to get the HTC One when its released.
OP may also check to see if the store has any older stock with 2.20 firmware (or any previous firmware version except 3.18). Phones with 3.18 out of the box must be very new, so I wouldn't be surprised if they had some older stock also.
I returned the one x today. will be looking into the t-mobile version of the HTC One which they told me comes out friday the 22nd. being a new phone i know i wont be able to do any mods or anything for a while, but that won't take long with the awesome Devs we have here! All the other models of the One X were sold out, and im guessing that someone realized that the new firmware was Out of Box so picked em all up. only had 2-3 stores with one each so its possible. now all the new stores have the new firmware no big deal, i'd prefer an HTC DNA anyways, but we'll see what the One is all about.
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Techinstein said:
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Click to expand...
Click to collapse
Yes, the CID for AT&T is cws_001 on all of the previous firmware versions, as well. This hasn't changed. cws__001 is blocked on HTCDev.com.
So i have the key for my past bootloader unlock can i use it?
Enviado desde mi HTC One X usando Tapatalk 2
coldrazor said:
So i have the key for my past bootloader unlock can i use it?
Click to expand...
Click to collapse
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
redpoint73 said:
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
exad said:
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
Click to expand...
Click to collapse
Really? Kinda negates part of the purpose of having S-off, doesn't it?
Sorry to ask but I was waiting to get the HTC one but with the delay I decided to pick up a new hox in the meantime...does anyone know what firmware the newer devices ship with? I'm not too concerned with flashing roms at this time, but I will want root...thanks....sorry coming from Samsung phones, rooting and flashing seemed too easy....I'm really getting lost on all the *s-off* stuff
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Sorry to ask but I was waiting to get the HTC one but with the delay I decided to pick up a new hox in the meantime...does anyone know what firmware the newer devices ship with? I'm not too concerned with flashing roms at this time, but I will want root...thanks
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Really depends on what they had in stock some ship still with 1.85 kinda just luck of the draw on what you get.
ronnie498 said:
Really depends on what they had in stock some ship still with 1.85 kinda just luck of the draw on what you get.
Click to expand...
Click to collapse
Well the last one I got back in October that I sold had I think 2.20...at that time there was no root...if I've been searching the forums correctly u can root 2.20 now correct?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit
Have a look at this thread
ronnie498 said:
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit
Have a look at this thread
Click to expand...
Click to collapse
Sweet...so I'm guessing 2.20 is the most recent firmware then...
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Sweet...so I'm guessing 2.20 is the most recent firmware then...
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
The lastest is 3.14 but if you have not ran the OTA then you will have one of the others
Sorry one last question that I'm a bit confused on...if I update it to jelly bean once I get it...can I still root?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Sorry one last question that I'm a bit confused on...if I update it to jelly bean once I get it...can I still root?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
DON'T DO ANYTHING YET!
Latest firmware for AT&T is 3.18, which comes with the JB 4.1 Sense update. This firmware is not rooted, so if you were lucky enough to get an older HOX (2.20 or 1.85 firmware, neither of which is Jelly Bean), then you can root it, which you must do before you take the OTA update (in which case there's no reason to take it afterwards anyways). :good:
jeffwyeh said:
DON'T DO ANYTHING YET!
Latest firmware for AT&T is 3.18, which comes with the JB 4.1 Sense update. This firmware is not rooted, so if you were lucky enough to get an older HOX (2.20 or 1.85 firmware, neither of which is Jelly Bean), then you can root it, which you must do before you take the OTA update (in which case there's no reason to take it afterwards anyways). :good:
Click to expand...
Click to collapse
Gotcha that's what I wanted to know....well hopefully I won't get the 3.18...should know on Tuesday....so if its 2.20 or less then I root and once I ota to jb the root will stay....now should this all pan out this way and down the line I want to try some rooms out, can I unlock the boot loader even if I updated to jb? Honestly I don't mind staying on ics if need be
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Gotcha that's what I wanted to know....well hopefully I won't get the 3.18...should know on Tuesday....so if its 2.20 or less then I root and once I ota to jb the root will stay....now should this all pan out this way and down the line I want to try some rooms out, can I unlock the boot loader even if I updated to jb? Honestly I don't mind staying on ics if need be
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
On 2.20, you can use the X-Factor root exploit or hasoon's all-in-one kit. Afaik, perm root requires you to unlock your bootloader, which in turn requires SuperCID (country ID? carrier ID? I can't remember). If you try to run the OTA with superCID, it will fail and entirely brick your phone.
However, with an unlocked bootloader, you can install a custom recovery and flash the updated ROM manually with no problems.
jeffwyeh said:
On 2.20, you can use the X-Factor root exploit or hasoon's all-in-one kit. Afaik, perm root requires you to unlock your bootloader, which in turn requires SuperCID (country ID? carrier ID? I can't remember). If you try to run the OTA with superCID, it will fail and entirely brick your phone.
However, with an unlocked bootloader, you can install a custom recovery and flash the updated ROM manually with no problems.
Click to expand...
Click to collapse
Not quite. You can still lose root if you update to a newer firmware. You need to s-off after rooting and unlocking. It's s-on + supercid + 3.18 that causes the brick.
To OP:
Assuming you get a 2.20 phone, you should run the toolkit to root, supercid, and unlock, then s-off (link to thread is in my sig). A lot of people have gotten bricked by upgrading to 3.18 because they didn't think they needed s-off.
Once you're s-off, you can never lose root because it turns off all security restrictions on your phone.
iElvis said:
Not quite. You can still lose root if you update to a newer firmware. You need to s-off after rooting and unlocking. It's s-on + supercid + 3.18 that causes the brick.
To OP:
Assuming you get a 2.20 phone, you should run the toolkit to root, supercid, and unlock, then s-off (link to thread is in my sig). A lot of people have gotten bricked by upgrading to 3.18 because they didn't think they needed s-off.
Once you're s-off, you can never lose root because it turns off all security restrictions on your phone.
Click to expand...
Click to collapse
Not to derail the thread, but for my own knowledge, is it possible to get into a permanently rooted state without supercid?
jeffwyeh said:
Not to derail the thread, but for my own knowledge, is it possible to get into a permanently rooted state without supercid?
Click to expand...
Click to collapse
You need supercid to get s-off, but after that, you can return to stock cid without issues. With s-off, you can change your cid to whatever you want.
iElvis said:
You need supercid to get s-off, but after that, you can return to stock cid without issues. With s-off, you can change your cid to whatever you want.
Click to expand...
Click to collapse
Last question for now, I promise, and I'll return the thread to it's rightful owner. Are there any advantages to going back to stock cid, outside of wanting the take the OTA update without bricking?
jeffwyeh said:
Last question for now, I promise, and I'll return the thread to it's rightful owner. Are there any advantages to going back to stock cid, outside of wanting the take the OTA update without bricking?
Click to expand...
Click to collapse
Once you're s-off, I don't think it makes a difference, unless you lost your unlock token and need another one. Then you've got to assign 22222222 as your cid (supercid no longer works on htcdev).
Ok so I got my package from UPS....opened it and noticed the tamper seal was already broken....since it was sold as a new unit that seal should have been sealed....i call ATT and and going to go to a store to swap it out for another one...good thing too cause the one I got had the 3.18 firmware so I couldn't root....here's to hoping I luck out on the next one
ok so lucked out and got a 2.20....anyways i unlocked the bootloader and rooted...i'm attempting s-off...not successful yet....but phone is trying to update....i turned off all data to the phone temp...how do i stop the phone from downloading the update??? i don't wanna brick it...can i let it update once i get s-off?
lunercrab said:
ok so lucked out and got a 2.20....anyways i unlocked the bootloader and rooted...i'm attempting s-off...not successful yet....but phone is trying to update....i turned off all data to the phone temp...how do i stop the phone from downloading the update??? i don't wanna brick it...can i let it update once i get s-off?
Click to expand...
Click to collapse
Just keep declining the update. It won't force it for a few days.
iElvis said:
Just keep declining the update. It won't force it for a few days.
Click to expand...
Click to collapse
yeah but it shows system update downloading inside the notification window....how do i stop that...i mean will it download and install if i let it continue?
3.18
I just bought a new One X from a local AT&T store and it has firmware 3.18 with JB 4.1.1. It's the greatest phone I've ever had. Sucks that I can't root it though. I've been trying to think of ways to unlock the bootloader, but I guess it's the encryption that's the real deal.
I was thinking about trying the xfactor exploit just for kicks, although I read that they killed that with 3.18, not to mention the CID block on HTCdev.
Okay, So I'm fairly new to all this. I've made several (unsuccessful) attempts at rooting my AT&T HOX, but I finally think I know where I went wrong.
In the past, I had tried unlocking the bootloader without having SuperCID access. (So yes, I currently have s-on..) Mainly due to the fact that I didn't know I needed sim access to root.
Because of these past issues, I have done the ATT OTA update.. From what I have read in other posts, correct me if I'm wrong, there is currently no way to gain SuperCID with the 5.18 update..
Other than waiting, is there any way I could go about rooting my phone? Is it possible to reset to factory settings, and go back to Original software?
Please help. Would eventually love to get rid of all the ATT and HTC crap on my phone.. (can't stand sense 5..)
Android version - 4.2.2
HTC Sense version - 5.0
Software number 5.18.502.1
Evita PUT SHIP S-ON RL
HBOOT - 2.18.0000
Radio - 1.35a.32.45.27
OpenDSP-v33.1.0.45.1128
eMMC-boot
Because you've taken the latest at&t update there is no way at all to get SuperCID so you can unlock your bootloader. You'll have to wait and see whether a dev deems it worth his time to find a crack, but I wouldn't hold your breathe if I was you. Probably should have done your research before taking the update.
Sent from my Evita
tsunami560 said:
Okay, So I'm fairly new to all this. I've made several (unsuccessful) attempts at rooting my AT&T HOX, but I finally think I know where I went wrong.
In the past, I had tried unlocking the bootloader without having SuperCID access. (So yes, I currently have s-on..) Mainly due to the fact that I didn't know I needed sim access to root.
Because of these past issues, I have done the ATT OTA update.. From what I have read in other posts, correct me if I'm wrong, there is currently no way to gain SuperCID with the 5.18 update..
Other than waiting, is there any way I could go about rooting my phone? Is it possible to reset to factory settings, and go back to Original software?
Please help. Would eventually love to get rid of all the ATT and HTC crap on my phone.. (can't stand sense 5..)
Android version - 4.2.2
HTC Sense version - 5.0
Software number 5.18.502.1
Evita PUT SHIP S-ON RL
HBOOT - 2.18.0000
Radio - 1.35a.32.45.27
OpenDSP-v33.1.0.45.1128
eMMC-boot
Click to expand...
Click to collapse
1. I'm not are of a root for this new firmware (as Timmaaa has stated).
2. I'm not sure why you chose to get the OTA update if you can't stand HTC and Sense. Any time you grab an update from A&T, you're risking not being able to root
3. I recommend you purchase a Google phone and root/mod it as much as you want. No more HTC, No More ATT, No more Sense.
DanGeorges said:
1. I'm not are of a root for this new firmware (as Timmaaa has stated).
2. I'm not sure why you chose to get the OTA update if you can't stand HTC and Sense. Any time you grab an update from A&T, you're risking not being able to root
3. I recommend you purchase a Google phone and root/mod it as much as you want. No more HTC, No More ATT, No more Sense.
Click to expand...
Click to collapse
Hey Dan,
Thanks for the reply. I got the OTA because I like new. I didn't really think about it when I did it, so yea, it was a dumb mistake on my part.
I only got HTC, because it was my introduction to Android. I now have a rooted N7, and I love it. I would also love to get an N5, however, it's a good chunk of money I don't have currently, which is why I will be rooting my HOX once a root is available.
So, is anyone aware of a way to roll back an OTA update? Or is my best bet waiting for a 5.18 exploit?
Like I said, there is absolutely no way for you to get root unless someone releases an exploit.
Sent from my Evita
tsunami560 said:
So, is anyone aware of a way to roll back an OTA update? Or is my best bet waiting for a 5.18 exploit?
Click to expand...
Click to collapse
If such a thing were possible, than a new exploit would not be necessary, and we would have told you about it already.
You can't "rollback" or revert to previous Android versions unless already rooted, s-off, etc.
So I just got my U11 today (from Ebay) . It is an Unlocked US variant on the latest Nougat firmware, but it is asking me to update to 2.31.617.2 (and then I presume it will offer .3). Does Sunshine work for those two Oreo versions?
If I might also ask, since it seems that most all of the U11 variantsare being updated several months behind now, is there any major reason to go S-off or supercid if I plan on using this US phone in the US on T-mobile? I recall doing both via Sunshine on my M7 so I could change it to a Google phone and get some of the latest updates without the carrier interference. That doesn't seem to be an option now, so is there something else I'm missing if I stay S-on with my current cid and mid? I'm thinking about just unlocking the bootloader and likely rooting. Thanks for any advice.
vettejock99 said:
So I just got my U11 today (from Ebay) . It is an Unlocked US variant on the latest Nougat firmware, but it is asking me to update to 2.31.617.2 (and then I presume it will offer .3). Does Sunshine work for those two Oreo versions?
If I might also ask, since it seems that most all of the U11 variantsare being updated several months behind now, is there any major reason to go S-off or supercid if I plan on using this US phone in the US on T-mobile? I recall doing both via Sunshine on my M7 so I could change it to a Google phone and get some of the latest updates without the carrier interference. That doesn't seem to be an option now, so is there something else I'm missing if I stay S-on with my current cid and mid? I'm thinking about just unlocking the bootloader and likely rooting. Thanks for any advice.
Click to expand...
Click to collapse
I would up date to Oreo then root and install one of the many roms, I did go the s off route but basically settled back on Oreo. There is plenty of variations to keep you busy. I currently run Leedroid, Kiriskura-EAS kernal with Elemental to tweak and it runs great. Just my 2 cents!
hammered58 said:
I would up date to Oreo then root and install one of the many roms, I did go the s off route but basically settled back on Oreo. There is plenty of variations to keep you busy. I currently run Leedroid, Kiriskura-EAS kernal with Elemental to tweak and it runs great. Just my 2 cents!
Click to expand...
Click to collapse
Thank you. I'd been leaning that way overnight and it sounds like a great plan.