Related
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
Your CID should be 11111111, so you can unlock your bootloader again using the same unlock token from your first unlock. You will need HTC drivers installed.
to relock your bootloader,
Fastboot files http://www.mediafire.com/?4dx982z93w8z7wk
download and extract to desktop
open cmd and type cd Desktop
then cd foldername (the folder where fastboot is)
Boot into fast boot on your phone
then type fastboot oem lock
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
It will break root, but you can get that back with one of the original ways since you will still be on 1.85.
Sent from a slithery smooth phone!
Just flash another rom or wipe and reflash. Ruu will probably not help a random reboot.
Yeah same, I'd try a different ROM without going back to stock just to come to custom ROMs again.
WR
Sent from my One X
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
this has answers to all your questions http://forum.xda-developers.com/showpost.php?p=26669144&postcount=1
enjoy the read...
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!
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.
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Darkpikasso said:
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Click to expand...
Click to collapse
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
It's an at&t phone, the at&t CID is blocked by htcdev so you need to get SuperCID before being able to unlock the bootloader. Click the Everything Evita link in my signature and bookmark that thread, it's a resource thread that contains everything you'll ever need. Once you're in that thread navigate to the root section and find the 3.18 root method, this is the only method that'll work with your current firmware. Follow the instructions in that thread and then you can unlock your bootloader.
Once you have an unlocked bootloader you can install TWRP recovery which will allow you to root your stock ROM or install custom ROMs. If you need instructions on this click the How-To Guide For Beginners link in my signature, it's a thread I put together detailing some basic operations. If you have any questions feel free to ask in my Noob Friendly Q&A + General Help thread.
Sent from my One X using Tapatalk
You need to use the correct root method that corresponds to your firmware version in order to change your CID. Trying other methods you randomly Google around for is not going to work.
Use my Index thread, look under "ROOT" and find the method that matches your firmware number (3.18).
http://forum.xda-developers.com/showthread.php?t=1671237
There is not one-click method that works for firmware 3.18. Trying methods that don't match your firmware number is a waste of time.
Also, when asking for help, you need to be absolutely specific as to what you have tried, and what you haven't (including the result such as error messages, etc). If you don't give us specifics, it makes it even harder for us to help you.
Hasoon2000's all-in-one toolkit should work on 3.18. But if this is the one you tried, you haven't told us what happens when you try to use it.
To make it easier, here's the link to the 3.18 root method:
http://forum.xda-developers.com/showthread.php?t=2285086
You'll still want to bookmark the Everything Evita thread linked in my signature.
Sent from my One X using Tapatalk
Thank you everybody
When I try the all in one kit gave the error of waiting for the device, updated the adv drivers and still dosent show the CID change
In htcdev give me the MID not allowed error
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Darkpikasso said:
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Click to expand...
Click to collapse
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
ruffain said:
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Come on, you of all people shouldn't be giving attitude to this guy telling him he hasn't searched enough. You've asked me multiple questions that could have been answered if you had searched for the answer, including how to unlock your bootloader, that's kinda like the pot calling the kettle black.
It's easy for you to say unlocking the bootloader is an easy process once you've done it. The fact is that it isn't that simple for someone who is unaware that there are different methods for different firmware versions.
Sent from my One X using Tapatalk
redpoint73 said:
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
Click to expand...
Click to collapse
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Darkpikasso said:
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
Click to expand...
Click to collapse
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Roadrunner? I don't think such a method exists for this device. You can't get s-off without root, you can't get root without an unlocked bootloader, you can get an unlocked bootloader without SuperCID, the only way to get SuperCID on his firmware is to use the 3.18 root method. Hence the reason that's been stated over and over again in this thread. It's the only solution. Carrier unlocking has absolutely nothing to do with the bootloader unlock / root process.
Sent from my Evita
timmaaa said:
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Click to expand...
Click to collapse
Got it, first root and then unlock
Keep you update and thanks a lot for the help
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
timmaaa said:
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
Click to expand...
Click to collapse
Thanks everybody for the help but I can't get superCID
The htc dosent let him write and all the exploits to change it ether dosent find the device or dosent allow to write the commands
I really don't know what is the problem
I already install new drivers uninstall the ones from Samsung that I had and nothing
Not even my phone has the option to put it in charge only it has various opcitions but none of them are charge only
What do you mean by "all the exploits"? Which exploits have you tried? Did you try the 3.18 root method I gave you the link to?
Sent from my Evita
lemonfugu said:
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Click to expand...
Click to collapse
I got it....
I uninstall the drivers and install again there's were got the connection and unlocked but it says TEMPERED
Is that ok? Later in the afternoon I'm going to install custom recovery s-off and root
Yeah that's totally normal. I'd suggest you have a look at my How-To Guide For Beginners thread (link in my signature), it has some good instructions on your next steps.
Sent from my Evita
timmaaa said:
Roadrunner? I don't think such a method exists for this device.
Click to expand...
Click to collapse
Probably is referring to the Rumrunner s-off method. And yes, carrier (SIM) unlock has nothing to do with bootloader unlock and/or s-off. Probably just a coincidence that that person was able to bootloader unlock after doing SIM unlock.
Thank you very much for the help now I have it everydone unlock, custom recovery, root and s-off.
I was having problems with faceoff to s-off but nothing big
I already have install viperxl with beastmode kernel
Sent from my HTC One X using xda app-developers app