Related
Hello all,
I purchased an HTC One X from AT&T after busting the screen on my GNex. I purchased the HTC One X from Ebay, LNIB and only a week old. However, because it's so new, my device has the latest OTA update applied. From my little bit of knowledge, this means that I can't root, install CWM, and of course install custom ROM's. However, booting into the recovery menu/hboot, my Hboot version shows as 1.84, and a few other pieces of info (IMEI, boot options, recovery). Does this mean that I can unlock my bootloader?Once I do that, I can dump sense. Can I unlock via HTCDEV? I have 3rd party insurance, so if I have a problem, I can just get a new device. What's the landscape for this phone?
We cant unlock bootloader on 2.20 so 2.21 might be out of the question also
Sent from my HTC One X using xda app-developers app
Ricksta said:
Hello all,
I purchased an HTC One X from AT&T after busting the screen on my GNex. I purchased the HTC One X from Ebay, LNIB and only a week old. However, because it's so new, my device has the latest OTA update applied. From my little bit of knowledge, this means that I can't root, install CWM, and of course install custom ROM's. However, booting into the recovery menu/hboot, my Hboot version shows as 1.84, and a few other pieces of info (IMEI, boot options, recovery). Does this mean that I can unlock my bootloader?Once I do that, I can dump sense. Can I unlock via HTCDEV? I have 3rd party insurance, so if I have a problem, I can just get a new device. What's the landscape for this phone?
Click to expand...
Click to collapse
Those numbers aren't AT&T official ROM release numbers. The latest hboot is 1.14 and the ROM is 2.20. Are you sure the bootloader is locked on the phone? Can you go into the bootloader and check it? Power down the phone then turn it on while holding volume down until you are in the bootloader. It will tell you if the bootloader is locked or if the phone has ever been unlocked (it will say tampered).
yup
Sent from my Desire HD using xda app-developers app
Could he already have the at&t software update?
Sent from my One X
I don't think the phone is an AT&T one x device at all. Maybe find a 2.21 with 1.84 hboot on internaional one x.
I'm thinking possible clone?
Sent from my VENOMized HoxL
Maybe clone but I think it is likely a HTC Raider 4g or HTC Inspire 4g and it is Android 2.2.1 not HTC build 2.21.
The one thing that is fairly certain is it is not a AT&T One X.
There is no AT&T One X 2.21 and there is no hboot 1.84. The version numbers do not match anything for evita phones.
I can't even re-unlock the bootloader for some reason either.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I mistakenly used the JBFW tool on my AT&T branded phone (CID: CWS__001) to change the CID to HTC__001, not realizing that my phone was still S-ON and the CID changing option was apparently for S-OFF only. I had root, I had the bootloader unlocked. Now I can't even get into recovery, and I think since my CID is apparently stuck as HTC__001, that the RUU for my phone's actual CID won't work. I should note that before I relocked the bootloader, I tried to change my CID back to the SuperCID but it would just freeze the phone. That's why I tried to relock it, hoping it would help. I thought I could just unlock it again, but it won't work. I can't flash anything via ADB, it all fails. This is the RUU I was trying to use:
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed.exe
and I got a Wrong Customer ID error.
Is there anything I can do to remedy this situation or am I at the warranty center's mercy? Thank you in advance for any help.
im in the same boat, hopefully we get some help here soon, ive got another phone on the way from the warranty center but they want the one i have now and if they see its been tampered there gonna send me a bill for the full price of the phone. wish i could help.
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Myrder said:
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Cingular is att.
If you see a ruu that says.Cingular,it will work
Sent from my HTC One XL using xda app-developers app
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
Myrder said:
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
---------- Post added at 03:18 PM ---------- Previous post was at 03:16 PM ----------
Cingular doesn't have an RUU for the people that have 2.20, I've looked.
Click to expand...
Click to collapse
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I stand corrected.
Myrder said:
I stand corrected.
Click to expand...
Click to collapse
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I have a nag for wanting to help people and it seems you do too. Lol.
Speaking of, I've been trying to keep up with that thread you have. How's that coming?
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Lmao, now that is a hard pickle to get yourself into!!!
If cid was changed to HTC_001 properly, go snag a new token off htcdev website........I'm not going to explain the rest
Sent from my HTC One XL using Tapatalk 2
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
8, I believe
First rfatmen
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
knyghtmayre said:
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
Click to expand...
Click to collapse
That's the spirit.
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Crappyvate said:
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Click to expand...
Click to collapse
well I know there is an RUU for it silly, I meant the naming convention isn't the same as previous RUU's
DvineLord said:
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Click to expand...
Click to collapse
I accidentally flashed recovery to boot portion. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
But now my phone boots and stays at twrp logo.
Even when I try to boot into recovery the same twrp logo nothing happens.
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?
Is there any way to unlock bootloader on at&t evita one x that has had the ota JB update?
Unfortunately, I did not root this phone prior to applying the update.
Any help/answers are obviously welcome.
I have tried going through the htcdev.com hack, but get the following error after entering my token id: Error Code: 160.Error Reason: MID Not Allowed.
tamanedalabe said:
Is there any way to unlock bootloader on at&t evita one x that has had the ota JB update?
Unfortunately, I did not root this phone prior to applying the update.
Any help/answers are obviously welcome.
I have tried going through the htcdev.com hack, but get the following error after entering my token id: Error Code: 160.Error Reason: MID Not Allowed.
Click to expand...
Click to collapse
At the moment there is not.
At the very least you need to be able to gain temp root access in order to change the CID to allow you unlock it through htcdev.
The error you get is because AT&T don't allow bootloader unlock through htcdev.
thejosh86 said:
At the moment there is not.
At the very least you need to be able to gain temp root access in order to change the CID to allow you unlock it through htcdev.
The error you get is because AT&T don't allow bootloader unlock through htcdev.
Click to expand...
Click to collapse
Is that something new that came with the ota update? I only ask because prior at&t evita one x's (2.20.502.7 ruu) had no issues with the htcdev unlock process
No it's been that way since the beginning.
With the 2.20 RUU there was an exploit so you could change your cid to another carrier or supercid which allowed you to unlock it through htcdev.
You still couldn't unlock it if it still had AT&T's cid on the device.
Sent from my HTC One X using xda premium
Has this been resolved? I'm following Hasoon 2000's guide to unlocking the bootloader on my htc one x (ATT) and there are many people who have had success and are posting on Hasoon's thread as recently as a few hours ago, so I'm assuming it is allowed now, but I'm still getting the error 160 code. I'd like to post directly on that thread but I'm a noob and don't have the minimum number of posts...
Any help appreciated
Bump
If you have the latest ota update, you will be unable to gain temp root. You have to change your CID to be able to unlock bootloader with HTC dev. Unless you were s-off, there is no way at this time to accomplish this.
Sent from my HTC One X using xda premium
the 3.18 update introduced system write protection so even with root, one cannot alter the CID unless one is S-OFF.
exad said:
the 3.18 update introduced system write protection so even with root, one cannot alter the CID unless one is S-OFF.
Click to expand...
Click to collapse
Any updates on this? Is there a way to change the CID on stock 3.18 update now?
averylowiq said:
Any updates on this? Is there a way to change the CID on stock 3.18 update now?
Click to expand...
Click to collapse
One word:
Search.
Sent from my Evita
timmaaa said:
One word:
Search.
Sent from my Evita
Click to expand...
Click to collapse
I tried but couldn't find anything useful.
averylowiq said:
I tried but couldn't find anything useful.
Click to expand...
Click to collapse
What exactly do you want to do?
Sent from my Evita
timmaaa said:
What exactly do you want to do?
Sent from my Evita
Click to expand...
Click to collapse
I want to be able to install nightly CM10.1 on an AT&T HTC One X. I just received this phone as a warranty replacement from AT&T and all my attempts to root this phone have been futile.
Which root method have you tried?
Sent from my Evita
sim unlock only , One x Att , Hboot 1.14
Is there a method to unlock just sim so i can use one x with different carrier ...please help
bratuha said:
Is there a method to unlock just sim so i can use one x with different carrier ...please help
Click to expand...
Click to collapse
There is no method to unlock the sim right now regardless of root, s-on, s-off, whatever. No one's cared to look for one. I would but I don't have another carrier sim to test with.
sim unlock only , One x Att , Hboot 1.14
exad said:
There is no method to unlock the sim right now regardless of root, s-on, s-off, whatever. No one's cared to look for one. I would but I don't have another carrier sim to test with.
Click to expand...
Click to collapse
So basicly one x can be used one on ATT network , iam i right ? and no way to use it on any other one ?
bratuha said:
So basicly one x can be used one on ATT network , iam i right ? and no way to use it on any other one ?
Click to expand...
Click to collapse
as of the moment, that's correct.
It can be used on whatever network it came from. Other carriers sell the evita too. You can always try contacting the Carrier and requesting the unlock code or buying an unlock code from an unlock service.
Sent from my One X using xda app-developers app
Unlock windows version HTC 3.18 ATT
timmaaa said:
What exactly do you want to do?
Sent from my Evita
Click to expand...
Click to collapse
I want to root my HTC One X on AT&T, with 3.18. I have also searched, and come up with nothing. So the "one word - search" is not helpful, why even post that? I can see it being helpful if you posted your search results on how to do it, but you didn't.
Thanks