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.
Related
Hey guys,
I am an amateur in all these stuff. I recently picked up at&t one x white unlocked from US running 4.0.3
I wanted to update my phone but i guess i am afraid if my phone gets locked . Moreover i cannot even update it through settings as it says not able to connect to AT&T server.
Please help me regarding custom ROMS , updates Rooting etc and steps to follow.
Links to Threads that can help will be awesome.
Hoping you guys will help a new member
Thanks
Ankit
trojan_virus said:
Hey guys,
I am an amateur in all these stuff. I recently picked up at&t one x white unlocked from US running 4.0.3
I wanted to update my phone but i guess i am afraid if my phone gets locked . Moreover i cannot even update it through settings as it says not able to connect to AT&T server.
Please help me regarding custom ROMS , updates Rooting etc and steps to follow.
Links to Threads that can help will be awesome.
Hoping you guys will help a new member
Thanks
Ankit
Click to expand...
Click to collapse
1) you mean Sim - unlocked right? In that case it won't get locked even if you update the phone software.
2)First and important step is using the search function and I known its very hard for you but once in a while try using the search function, trust me you won't get tired
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
trojan_virus said:
Links to Threads that can help will be awesome.
Click to expand...
Click to collapse
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=1671237
And don't update. The newest 2.20 version firmware is not currently rootable. And hope you don't already have 2.20 on the phone.
redpoint73 said:
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=1671237
And don't update. The newest 2.20 version firmware is not currently rootable. And hope you don't already have 2.20 on the phone.
Click to expand...
Click to collapse
Thanks for correcting... I learned how to provide better reply
Sent from my HTC One X using xda premium
a little help guys...
I also have an unlocked HOX. I tried updating the software manually by downloading the AT&T ROM Update from the HTC website but got an error and now i'm stuck on a white screen that says:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT.1.09.0000
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
RUU
Update Fail!
* I did a factory reset and now passed that white screen...does anyone know what the problem was? is my phone rooted?
y2janz said:
a little help guys...
I also have an unlocked HOX. I tried updating the software manually by downloading the AT&T ROM Update from the HTC website but got an error and now i'm stuck on a white screen that says:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT.1.09.0000
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
RUU
Update Fail!
* I did a factory reset and now passed that white screen...does anyone know what the problem was? is my phone rooted?
Click to expand...
Click to collapse
You cannot run an RUU on a boot loader unlocked phone. relock it first.
gunnyman said:
You cannot run an RUU on a boot loader unlocked phone. relock it first.
Click to expand...
Click to collapse
Thanks. Unfortunately I don't know how to do that. I guess I'll hold off 4.0.4 for now...
You need to read some more, before running things willy-nilly without the proper research.
I would advise against running the 2.20 RUU. As I already mentioned, it updates the hboot, which robs you of the ability to flash kernels and radios. There is no upside to it, since you can flash the ROM in other ways. Your phone is bootloader unlocked, and has full ability to flash kernels and radios. These are all good things. Don't take a step backward by flashing the 2.20 RUU.
If all you want is to update the ROM to 2.20, just flash the pre-rooted ROM (which will not replace the hboot): http://forum.xda-developers.com/showthread.php?t=1812459
But in fact, these are more recent versions:
http://forum.xda-developers.com/showthread.php?t=1789059
http://forum.xda-developers.com/showthread.php?t=1838135
Ya know, you guys CAN extract the rom.zip from 2.2x ruu and pull each image and flash them individually to get the 2.2x updates and keep your unlocked 1.09 hboot intact. That way you dont have to do the kernal flashing and what not. It will be fully updated, sbl's, radio everything.:beer:
18th.abn said:
Ya know, you guys CAN extract the rom.zip from 2.2x ruu and pull each image and flash them individually to get the 2.2x updates and keep your unlocked 1.09 hboot intact. That way you dont have to do the kernal flashing and what not. It will be fully updated, sbl's, radio everything.:beer:
Click to expand...
Click to collapse
how I wish I had done this.
Thanks a lot guys. I should have done some research. I bought this phone second hand thinking "unlocked" meant I could use it on other networks --didn't know the previous owner meant he unlocked the bootloader...hahaha...I guess i'll do some research to relock it.
y2janz said:
I guess i'll do some research to relock it.
Click to expand...
Click to collapse
Didn't read a thing I typed, apparently.
No need to relock it. Just run one of the stock rooted or custom ROMs in Development. Flash a new radio if you want.
I'm sorry, i really don't know how to do any of those stuff...
I just got the phone a couple of days ago and i am still waiting on my t-mobile non-gba micro sim that i ordered online, now im really not sure anymore if its unlocked to other networks...
I won't know til that sim card gets here, but in the mean time i'll do some reading on all those stuff you mentioned =)
I went to the HTC site and did a manual update, but I dont have sense 4.1. anyone know if the ATT version will get it?
plz help
I have a at&t one x I bought last night that is unlocked and I am using on telus.
The phone isn't rooted and is running on android 4.0.3 and HTC sence 4.0
When I try to update it nothing happens. My brother has the same phone thro telus and has received updates. I have went to settings about phoneat&t updates but when I search it does not do nothing .
An AT&T phone won't get the updates unless it's on their network it seems. Just download the ruu
Sent from my VENOMized HoxL
Bump. I unlocked my Rogers One X a while back, because I am planning on selling it. Since that time though, I have run an RUU on it. I no longer have another carrier's SIM card to test, so I just want to know if the unlock is permanent , or if it gets relocked when an RUU or factory reset is run.
The SIM unlock is permanent and will survive any RUU or factory reset.
Sent from my Evita
Just a heads up, HTCDEV unlocking no longer works with supercid. Changing cid to 22222222 does work. Thanks BEAUPS for already confirming that (Hes a beast)
Seeing that the chances of the hox exploits getting updated are pretty slim heres a easy fix to get people unlocked
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token as usual using htcdev
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.
18th.abn said:
Just a heads up. Changing cid to 22222222 works. Thanks BEAUPS for testing/confirming that.
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token.
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.
Click to expand...
Click to collapse
They just started blocking it? I just Unlocked my Bootloader last Sunday with 11111111 just fine
Re: HtcDev wesite Blocking Supercid FIX
Great work
Sent from my SPH-L710 using Tapatalk 2
Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD
does this mean updating to jb sense with 22222222 will no longer brick phone like with supercid?
Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?
twistedddx said:
Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?
Click to expand...
Click to collapse
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed but at the end of the process the phone doesn't boot an was locked in QHSUSB_DLOAD and at this time when you're locked in this mod by OTA update with superCID you can't rewrite partitions with the topic "unbricking evita".
My only solution was mobiletechvideos.com who fixed it very well
mik93250 said:
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed
Click to expand...
Click to collapse
What ruu did you apply? Was the phone modified in any other way than supercid? Eg was the hboot downgraded? Previous unlocked bootloader? Current unlocked bootloader?
What was the full state of the phone prior to accepting ota.
How was the ota applied? Did you simply check for updates and accept then follow prompts. Or installed via fastboot?
I have upgraded 2 hk one xl's with supercid to 3.17 via ota without issue. One was previously hong Kong ruu then wiped and had singtel stock Rom flashed then accepted singtel 3.17 ota. Could not use singtel ruu as Hong Kong ruu was newer and already installed. Hboot downgrade and software version tinkering still did not allow singtel ruu. I could only reinstall honk Kong ruu.
The other via o2 ruu and o2 3.17.
There seems to be some differences in the protections in hboot. Downgrading my phones hboot to 1.09 did not make flashing radio and boot from recovery functional again. It did not let me install older ruu's. My devices, one that has had every mod and flash done to it and the other very very little, both seem super hboot protected now!
The similar theme is both devices have been through all 4 generation of ota's. Following different ota and ruu paths but have now got the same outcome.
Maybe it relates to when supercid was applied even. Both my devices had supercid applied at hboot 1.09.
Damn HTC and ATT! They are bent on making this difficult. My next phone will be Nexus, enough of this crap!
We've had worse patches to overcome on the Evita, atleast its a simple solution for the time being. I do agree tho. I moved on from htc for the time being.
Sent from my SPH-L710 using Tapatalk 2
iElvis said:
Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
done moved over to the nexus 4 myself
Great to know, although I already have mine unlocked.
CheesyNutz said:
done moved over to the nexus 4 myself
Click to expand...
Click to collapse
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?
Viper4713 said:
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 7 using Tapatalk HD
Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL
CheesyNutz said:
Yes
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the Info, I guess my next phone later on will be a Nexus Phone
area51avenger said:
Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
LTE is not in my area so in would have no idea
Sent from my Nexus 7 using Tapatalk HD
I can't believe at&t would be this petty... Or that HTC would go along with it. I'm glad I unlocked my boot loader when I did.
Sent from my Nexus 7 using xda premium
Just tested.
Hong Kong One XL running 3.17.707.1.
Supercid 11111111
Just went through http://htcdev.com unlock process and got an unlock token 100% fine.
Again there is nothing wrong with Supercid, at least not in general. It works with htcdev.com and does not brick phones.
Someone needs to check if it is just AT&T phones that are struggling with supercid or if something else is upsetting things.
It is not supercid on its own, supercid(11111111) works fine!
HTC/AT&T might be actively checking for modified AT&T phones that are getting unlock tokens via root exploits and changing cid.
Non at&t phones don't need supercid, so this only affects at&t phones. All the other carriers phones will unlock with out messing with the cid number.
Sent from my Nexus 7 using xda premium
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?
Hello all. Quick question about running the 2.20 RUU -- I seem to recall, around the time that the 3.14 OTA update came out for the AT&T Version of the One XL a lot of folks were hard-bricking their phones that were previously rooted on a separate JB ROMs..perhaps something with the Super CID? I did not investigate this much because I wasn't ever interested in taking the 3.14 OTA but my question is: Can I safely run the 2.20 RUU on hboot 1.14 S-OFF; I am currently running a JB ROM right now. Sorry for the question but I can't seem to find the threads that explained why users were getting hard bricks from the OTA -- I'm about to wipe my phone and give it to someone else and I would hate to hard-brick it and the phone be no longer usable
TheEmpyre said:
Hello all. Quick question about running the 2.20 RUU -- I seem to recall, around the time that the 3.14 OTA update came out for the AT&T Version of the One XL a lot of folks were hard-bricking their phones that were previously rooted on a separate JB ROMs. I did not investigate this much because I wasn't ever interested in taking the 3.14 OTA but my question is: Can I safely run the 2.20 RUU on hboot 1.14 S-OFF; I am currently running a JB ROM right now. Sorry for the question but I can't seem to find the threads that explained why users were getting hard bricks from the OTA -- I'm about to wipe my phone and give it to someone else and I would hate to hard-brick it and the phone be no longer usable
Click to expand...
Click to collapse
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
exad said:
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
Click to expand...
Click to collapse
Thanks for the reply. Wow thats great, I remember last time I RUU I had to fastboot oem lock and then run it and flash the unlock token again which was pain in the a$$.
Thanks again for the clarification -- added [Solved]
exad said:
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
Click to expand...
Click to collapse
Just to clarify --- can I also run the 3.14 OTA if I am S-OFF without Brick?
TheEmpyre said:
Just to clarify --- can I also run the 3.14 OTA if I am S-OFF without Brick?
Click to expand...
Click to collapse
That's right.
Unfortunately for me, I was s-on and supercid when I took the OTA. Hard bricked my phone and I had to have it replaced lol.
marcur12 said:
Unfortunately for me, I was s-on and supercid when I took the OTA. Hard bricked my phone and I had to have it replaced lol.
Click to expand...
Click to collapse
Yeah I just vaguely remember seeing some unfortunate threads after the OTA came out and so I just thought I would check. Bummer about your device sorry
Sent from my HTC One using Tapatalk 2
TheEmpyre said:
Yeah I just vaguely remember seeing some unfortunate threads after the OTA came out and so I just thought I would check. Bummer about your device sorry
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Fun fact: Running the 2.20 RUU down from a 3.17 based ROM removes the "TAMPERED" tag from the bootloader. At least on hboot 1.14 and S-OFF
TheEmpyre said:
Fun fact: Running the 2.20 RUU down from a 3.17 based ROM removes the "TAMPERED" tag from the bootloader. At least on hboot 1.14 and S-OFF
Click to expand...
Click to collapse
Running any RUU should remove that Tampered text which is documented in the modding your bootloader screen thread.
I have extracted and decrypted the att ruu for the htc one mini. Just so if anyone needs something out of it and doesnt want to flash the entire ruu
https://mega.co.nz/#!aQRUTaaJ!MkdTchfndvrpKTlHqcW4xgGKGr1s2d8Vqy9LqOv6SAY
hope it helps lemme know if link works. my mega screws up sometimes.
It's possible to unroot phone by this. I have s-off, Htc One Mini, UK T-mobile version, but I want back to s-on with unrooted phone to get my warranty again.
unlimited_pl said:
It's possible to unroot phone by this. I have s-off, Htc One Mini, UK T-mobile version, but I want back to s-on with unrooted phone to get my warranty again.
Click to expand...
Click to collapse
Flashing the at&t ruu must be risky. They are different version. The ruu is the 1.32.502.3. But I have flash magio rom before and use the ruu to get back to the stock version. You should not s-off if you ever think about going back to stock to get warranty. The closest to stock for your phone is using revone to lock your bootloader and going back to s-on. As someone has mentioned, doing those is not 100% true. If you are returning the phone to your carrier to get a replacement then just make sure to get rid of your superuser and lock the bootloader. You can also try to s-on back but it's too risky.
abzboi said:
Flashing the at&t ruu must be risky. They are different version. The ruu is the 1.32.502.3. But I have flash magio rom before and use the ruu to get back to the stock version. You should not s-off if you ever think about going back to stock to get warranty. The closest to stock for your phone is using revone to lock your bootloader and going back to s-on. As someone has mentioned, doing those is not 100% true. If you are returning the phone to your carrier to get a replacement then just make sure to get rid of your superuser and lock the bootloader. You can also try to s-on back but it's too risky.
Click to expand...
Click to collapse
ive used the ruu many times.lol its not risky at all.
abzboi said:
Flashing the at&t ruu must be risky. They are different version. The ruu is the 1.32.502.3. But I have flash magio rom before and use the ruu to get back to the stock version. You should not s-off if you ever think about going back to stock to get warranty. The closest to stock for your phone is using revone to lock your bootloader and going back to s-on. As someone has mentioned, doing those is not 100% true. If you are returning the phone to your carrier to get a replacement then just make sure to get rid of your superuser and lock the bootloader. You can also try to s-on back but it's too risky.
Click to expand...
Click to collapse
ive got two phones replaced already if you need warrany...brick the bastard solid so you have a dead black screen. play dumb like it just happened on the charger overnight.lol
Where can I find stock ruu for htc one mini?
If you're trying to return it for warranty then just brick your phone. Don't flash the AT&T ruu because when they check it will show AT&T suff in there and they will know about it. Unless it bricks don't flash it unless your phone is the AT&T version.
4.4.2 came out for at&t yesterday. Can you download it and extract it maybe?
cmvienneau said:
ive got two phones replaced already if you need warrany...brick the bastard solid so you have a dead black screen. play dumb like it just happened on the charger overnight.lol
Click to expand...
Click to collapse
Whats the best way to do this? .. My battery is really screwed ... operating extremely hot .. I htink I need to return for a warranty. Even when the phone has been off for 2 hours the back still has heat in it!
abzboi said:
4.4.2 came out for at&t yesterday. Can you download it and extract it maybe?
Click to expand...
Click to collapse
+1
in indonesia not getting update.my phone still jb 4.2.2 and never get update via ota.so sad
Sent from my HTC One mini using XDA Premium 4 mobile app
dalfshiro said:
+1
in indonesia not getting update.my phone still jb 4.2.2 and never get update via ota.so sad
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you root or s-off the phone? If yes, then I can help you get 4.4.2 ota update.
abzboi said:
Did you root or s-off the phone? If yes, then I can help you get 4.4.2 ota update.
Click to expand...
Click to collapse
i am not sure my phone rooted or not, couse i am buying from another people. but i have checked witch root checker and said not root. and i can confiirm my phone still locked and s-on. please help me
dalfshiro said:
i am not sure my phone rooted or not, couse i am buying from another people. but i have checked witch root checker and said not root. and i can confiirm my phone still locked and s-on. please help me
Click to expand...
Click to collapse
Try changing the date of the phone to the next day and check for update. If not, tell me what android version you're on and I'll help you update your phone to 4.4.2 via ota.
abzboi said:
Try changing the date of the phone to the next day and check for update. If not, tell me what android version you're on and I'll help you update your phone to 4.4.2 via ota.
Click to expand...
Click to collapse
I have changed my date to the next month.but still no update.my phone jb 4.2.2 software number 1.24.502.3
I am not using t mobile sim card.but using another sim card cause i am in indonesia.maybe thats the problem?pleasr help.thanks
Sent from my HTC One mini using XDA Premium 4 mobile app
dalfshiro said:
I have changed my date to the next month.but still no update.my phone jb 4.2.2 software number 1.24.502.3
I am not using t mobile sim card.but using another sim card cause i am in indonesia.maybe thats the problem?pleasr help.thanks
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Download this ruu and backup before you run it. If you bootloader is unlocked, lock it using fastboot oem lock. Link : http://dl3.htc.com/application/RUU_M...3_signed_2.exe
abzboi said:
Download this ruu and backup before you run it. If you bootloader is unlocked, lock it using fastboot oem lock. Link : http://dl3.htc.com/application/RUU_M...3_signed_2.exe
Click to expand...
Click to collapse
are you sure tahts the correct link?
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
dalfshiro said:
are you sure tahts the correct link?
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Click to expand...
Click to collapse
It's in this thread http://forum.xda-developers.com/showthread.php?t=2546757
abzboi said:
It's in this thread http://forum.xda-developers.com/showthread.php?t=2546757
Click to expand...
Click to collapse
can you give me step by step to install this RUU?need to s-on s-off?
dalfshiro said:
can you give me step by step to install this RUU?need to s-on s-off?
Click to expand...
Click to collapse
Just turn your phone into bootloader and fastboot then run the ruu and your done.
abzboi said:
Just turn your phone into bootloader and fastboot then run the ruu and your done.
Click to expand...
Click to collapse
i have installed htc sync manager on PC.but my phone wont detected fastboot.
edited : windows 8.1 cant detect htc usb driver