I was wondering, if now that the CID exploit was found if there would be any attempt to unlock the bootloader without using the HTC site. (i ask cuz i see most questions like this not answered, but people routing others to current x-factor exploit which requires htcdev.)
dergezero said:
I was wondering, if now that the CID exploit was found if there would be any attempt to unlock the bootloader without using the HTC site. (i ask cuz i see most questions like this not answered, but people routing others to current x-factor exploit which requires htcdev.)
Click to expand...
Click to collapse
no. you need SU, and you can't get SU on 2.20 without an unlocked bootloader. You can only get superCID on 2.20 (from temp root)
Is there anyone out there still looking for a non-htcdev way to root? and does anyone know why the x-factor exploit cant be used to gain the temp root? is there a thread where this is discussed. i cant seem to find it.
You don't need to use x-factor because you are still superCID even after an RUU (I think, correct me if I'm wrong)
So all you have to do is re-unlock with htcdev
dergezero said:
Is there anyone out there still looking for a non-htcdev way to root? and does anyone know why the x-factor exploit cant be used to gain the temp root? is there a thread where this is discussed. i cant seem to find it.
Click to expand...
Click to collapse
Xfactor does give temp root.. it uses temp root to change your cid
Sent from my One X using xda app-developers app
There is currently no way to root on 2.20 firmware, without using HTCDev.com.
If you want to prevent HTC from having your IMEI (and possibly knowing that you unlocked your bootloader), then you can try this: http://forum.xda-developers.com/showthread.php?t=1734558
Still have to go thru HTCDev.com but spoofs the IMEI and SN.
Really not all that useful, as the bootloader will only read UNLOCKED or RELOCKED anyway (if returning for warranty purposes).
Related
There are so many threads pertaining to certain situations and I can't quite decipher what to do with my situation so I'm going to ask.
I'm on shipping stock (1.72) but rooted. I have yet to unlock my boot loader.
I am very interested in upgrading to 1.85, but only want to do so if I can do everything to be able to flash roms through cwm.
I see that you can and you can't root 1.85 so I'm not sure if I should upgrade. I'm ok with waiting for a root method. But if I am able to right now I want to go ahead.
Any help is appreciated.
I am in the same situation as you are. I am on 1.73 rooted and not unlocked yet. From what I understand you can unlocked the bootloader on 1.73 and upgrade to 1.85 and still be able to root. I can not understand properly either and would like some clarification before I move forward. Check this out...
Smile How To Root An AT&T HTC One X for 1.85
http://forum.xda-developers.com/showthread.php?t=1673935
After reading this I feel this is possible but would like confirmation. Thanks
Vocalshock said:
I am in the same situation as you are. I am on 1.73 rooted and not unlocked yet. From what I understand you can unlocked the bootloader on 1.73 and upgrade to 1.85 and still be able to root. I can not understand properly either and would like some clarification before I move forward. Check this out...
Smile How To Root An AT&T HTC One X for 1.85
http://forum.xda-developers.com/showthread.php?t=1673935
After reading this I feel this is possible but would like confirmation. Thanks
Click to expand...
Click to collapse
Yes, but isnt those directions out of order...cause dont you have to aquire root to unlock the bootloader?
Can someone help me out here? I've been trying to root my HOX running 2.20 and I have read many threads on how to root the HOX 2.20. But what I don't understand is that when I read a thread on rooting, it says to unlock the bootloader first. So I go to a thread on unlocking the bootloader because it can't be done through HTCDev. Those threads on unlocking the bootloader tell me I need to be rooted first. Nothing is making sense with all this.
iLToRReNT said:
Can someone help me out here? I've been trying to root my HOX running 2.20 and I have read many threads on how to root the HOX 2.20. But what I don't understand is that when I read a thread on rooting, it says to unlock the bootloader first. So I go to a thread on unlocking the bootloader because it can't be done through HTCDev. Those threads on unlocking the bootloader tell me I need to be rooted first. Nothing is making sense with all this.
Click to expand...
Click to collapse
your on 2.20 there is not working method to root in 2.20 atm and this is in the wrong section should be on Q&A
How do these even get to the dev section? Read the Q&A and general sections and all would be answered.
Lol yeah sorry just read a bit and you'll see 2.20 out of the box is a no go
IB4TL
Sent from my HTC One X using xda premium
Dude, based on your post history, you've had this phone for 2 months and you still haven't figured out this basic information???
On any other version of the One X besides the AT&T version, the carriers are allowing the bootloader to be unlocked. For those versions, you just go to HTCDev.com, unlock the bootloader. Then you can flash a custom recovery, and use that to flash a rooted ROM to obtain root.
The AT&T version is a different situation. AT&T is blocking the bootloader from being unlocked. Therefore, the only way to unlock the bootloader is to spoof the carrier ID (CID) and make it SuperCID (basically a "god mode" CID that bypasses the CID check). With SuperCID, you can use HTCDev.com to unlock the bootloader. Unfortunately, getting SuperCID requires root. So its a bit of a backwards situation from other versions (any version but AT&T). For them, its unlock bootloader then root. For AT&T, its root then unlock bootloader.
If you are looking at root guides that say unlock the bootloader, then root; you are looking at guides for other versions of the phone. Either Rogers, Telstra (other carrier versions of the Snapdragon S4 version), or worse, you are looking at guides for the international (Tegra3) version of the One X. Either way, stick to information that specifically for AT&T, or you may do irreparable damage to your phone.
For 2.20 firmware, no root method has yet been found. So you're stuck with no root and no unlocked bootloader until one of the following happens:
1) A root method is found
2) AT&T allows the bootloader to be unlocked via HTCDev.com
3) S-Off is acheived
Hi Guys
Sorry for asking the same old question again..
I just got my AT&t HTC One x from US shipped over to India by my cousin.
It is locked to AT&t and i am unable to use a local network sim in it
I know i need to root it and turn S-off in order to unlock it.
The phone is on Firmware 1.85? and i have tried the ways mentioned in xda to root it but i guess when i click "Check for updates" it doesn't work.
So my question is
Can i manually by connecting the phone to Computer,update firmware to 2.20 so that i can root it that way?
And is it possible to unlock the BOOTLOADER w/out rooting so that phone gets unlocked to other carriers?
please help me out guys i have tried everything to make it work.. thank you
Unlocking the bootloader/rooting/dancing in circles WILL NOT sim unlock the phone.
You will need to use an online sim unlocking service (usually about 20 bucks) to get the unlock code
Currently, S-Off has not been achieved for this phone. And as already mentioned, bootloader unlock will not get you SIM unlock, and no free hack/mod method currently exists. You either need to use a paid unlock service, or if your cousin is currently an AT&T account holder, he can ask AT&T for the SIM unlock code (he will need the IMEI number of the phone, and maybe other info).
If you want root and unlocked bootloader for other reasons (flashing custom ROMs and other mods) there is no reason to upgrade to 2.20. Root method exists for 1.85. You need to root, SuperCID, then unlock the bootloader. Then you can install a custom recovery and flash custom ROMs.
Upgrading to 2.20 is not recommended. The 2.20 RUU will upgrade your hboot, which plugs the holes by which kernels and radios can be flashed from recovery. You will have to flash the boot.img separately every time your flash a ROM. No benefit to updating to 2.20, and actually lose ability to do some things.
If you still want root and bootloader unlock, refer to my index for links to root methods, etc.: http://forum.xda-developers.com/showthread.php?t=1671237
And no, bootloader unlock is not possible without root (temp root in case of 2.20) on the AT&T One X.
area51avenger said:
Unlocking the bootloader/rooting/dancing in circles WILL NOT sim unlock the phone.
You will need to use an online sim unlocking service (usually about 20 bucks) to get the unlock code
Click to expand...
Click to collapse
Dancing in circles? ok got your point.
redpoint73 said:
Currently, S-Off has not been achieved for this phone. And as already mentioned, bootloader unlock will not get you SIM unlock, and no free hack/mod method currently exists. You either need to use a paid unlock service, or if your cousin is currently an AT&T account holder, he can ask AT&T for the SIM unlock code (he will need the IMEI number of the phone, and maybe other info).
If you want root and unlocked bootloader for other reasons (flashing custom ROMs and other mods) there is no reason to upgrade to 2.20. Root method exists for 1.85. You need to root, SuperCID, then unlock the bootloader. Then you can install a custom recovery and flash custom ROMs.
Upgrading to 2.20 is not recommended. The 2.20 RUU will upgrade your hboot, which plugs the holes by which kernels and radios can be flashed from recovery. You will have to flash the boot.img separately every time your flash a ROM. No benefit to updating to 2.20, and actually lose ability to do some things.
If you still want root and bootloader unlock, refer to my index for links to root methods, etc.: http://forum.xda-developers.com/showthread.php?t=1671237
And no, bootloader unlock is not possible without root (temp root in case of 2.20) on the AT&T One X.
Click to expand...
Click to collapse
Thank you for a detailed answer. The reason i though it would unlock the sim was cause i had used other htc phones earlier and when you root them the S-off was achieved so thats why.. anyhow.. thank you for enlightening my dumb bum.
You're not dumb. Just ignorant. Now you have been enlightened. You still have a great phone, you just might have to pay a little bit so you can unlock and use it
Sent from my HTC One X using xda app-developers app
area51avenger said:
You're not dumb. Just ignorant.
Click to expand...
Click to collapse
The word "ignorant" has always sounded like a pejorative word to me. But I had to look up the definition, figuring maybe I don't really know the literal meaning of the word. Which turned out to be the case. One of the definitions of ignorant is "Lacking knowledge, information, or awareness about something in particular" which seems to exactly fit this situation. I guess I gave myself the English lesson for the day!
Every phone is different, and HTC in particular is always changing around their security measures. So the OP is not dumb in any way, but was just missing some particular pieces of information.
I'm in the process of setting out how I'm going to do the full works on my Telstra HOXL (root-bootloader-soff).
My question is. Unlocking the bootloader without HTCdev. Can it be done?
No...why wouldn't you want to do it through HTC dev..that ensures nothing wrong can really happen
Early FW versions you could spoof htcdev so they didn't have your real imei and s/n.
For Telstra you need to have FW 1.81 if you want to try this. Be sure you read everything carefully and you're confident as many had issues with this process by not reading the instructions carefully.
It doesn't work on any later versions well not until you're already BL unlocked though so anything else you'll need to use htcdev to unlock, change your cid then S-Off which is a fairly simple process.
Good luck
Sent from my HTC One XL using xda premium
http://forum.xda-developers.com/showthread.php?t=1732980
You have to be able to root without unlocking for it to be practical. Use it as a guide to update a more current method. Links may be dead by now. I'll have to check
Sent from my SPH-L710 using Tapatalk 2
As the title states, what's the proper way to unlock a relocked boot loader? Using Firewater again doesn't do anything. I can't flash any .zip files without them instantly failing (even if the MD5 checksum is correct) which wasn't happening before i fast boot oem locked my M8.
Any ideas?
I'm assuming you're also s-off since this is the Verizon forum so you could change to super cid and then get an unlock code from htcdev.
cntryby429 said:
I'm assuming you're also s-off since this is the Verizon forum so you could change to super cid and then get an unlock code from htcdev.
Click to expand...
Click to collapse
Naturally, yes, I am s-off. I can get an unlock code from htcdev just by changing my cid? Like this? That could work.
Ew, I can't give you the details cause I don't know them. I vaguely recall that super cid is all ones but I was intending to give you enough info to Google on. You obviously did with your post but again, I THINK your super cid should be all ones to then you would be able to get an unlock code from htcdev. Sorry I can't be of more help.
cntryby429 said:
Ew, I can't give you the details cause I don't know them. I vaguely recall that super cid is all ones but I was intending to give you enough info to Google on. You obviously did with your post but again, I THINK your super cid should be all ones to then you would be able to get an unlock code from htcdev. Sorry I can't be of more help.
Click to expand...
Click to collapse
That's what that post says to do. I might as well try it, I'll write down my current cid and then test it out. Here's to not breaking anything :good:
Alright, changing the CID and unlocking using htcdev unlocked my boot loader perfectly, and now the rom I was trying to flash isn't just instantly failing! Thanks for your help!
One thing I don't know but would find out if I were you is if you should now change you cid back to what it was. I understand that some ROMs will check that and install the proper files based on it. It just might keep you from accidentally doing something you shouldn't.