Database Info

[Q] 1.85 update issue?

So updated to 1.85.
Bootloader says "relocked".
In order to root, I need to unlock the bootloader...
In order to get SuperCID, I need to my bootloader unlocked aswell...
And in order to unlock my bootloader I need to change my CID to 11111111 via This Thread
So, Where... Am I suppose to start?
Root = Need unlocked bootloader.
Change CID [script]= Need root.
Change CID [Manual way] = Need root.
So i'm stuck between;
root <-> CID
OR
CWM Recov <-> CID
Meaning, If I can get either my CID changed, CWM installed, or root everything will be fine.
Where do I begin.
---------
I'm starting all over from the beginning with this one because I usually know what i'm doing but I believe I missed something.

TKTAB911 said:
So updated to 1.85.
Bootloader says "relocked".
In order to root, I need to unlock the bootloader...
In order to get SuperCID, I need to my bootloader unlocked aswell...
And in order to unlock my bootloader I need to change my CID to 11111111 via This Thread
So, Where... Am I suppose to start?
Root = Need unlocked bootloader.
Change CID [script]= Need root.
Change CID [Manual way] = Need root.
So i'm stuck between;
root <-> CID
OR
CWM Recov <-> CID
Meaning, If I can get either my CID changed, CWM installed, or root everything will be fine.
Where do I begin.
Click to expand...
Click to collapse
unless you changed your CID prior to relocking it's still 11111111 just unlock again.

fastboot oem cid = cws_001
Or so it says.
http://forum.xda-developers.com/showthread.php?t=1676101
I'm here, On try 34. Still no luck.

TKTAB911 said:
fastboot oem cid = cws_001
Or so it says.
http://forum.xda-developers.com/showthread.php?t=1676101
I'm here, On try 34. Still no luck.
Click to expand...
Click to collapse
if it says cws__001 you can't unlock. the CID has to be the same as it was when you unlocked.

I had to relock in order to upgrade from 82 -> 85 RUU.
Otherwise it returned error 155 on the installer.
But seeing as how other people have had to try multiple times in order to get it to work I'm guessing I do aswell [already tried pushing my first unlock token, no luck].

TKTAB911 said:
I had to relock in order to upgrade from 82 -> 85 RUU.
Otherwise it returned error 155 on the installer.
But seeing as how other people have had to try multiple times in order to get it to work I'm guessing I do aswell [already tried pushing my first unlock token, no luck].
Click to expand...
Click to collapse
I understand that but in no part of the relock process do you have to change your CID back to cws__001.
are you sure it isn't 11111111?

According to "fastboot oem cid" adb command, yes it is CWS_001.

TKTAB911 said:
According to "fastboot oem cid" adb command, yes it is CWS_001.
Click to expand...
Click to collapse
Did you change the CID back to CWS__001 before relocking? If so, you didn't need to.
If you didn't, I'm not sure how that happened since the RUU installer doesn't touch the partition that the CID resides on.

I'm not even going to bother with it anymore. Not worth the trouble at this point. :b

If you still have the unlock_code.bin then you can unlock. Push it to the phone in fastboot and then when the screen goes black press volume down and then press power.

Tried it a dozen times. I believe the ID Token stayed the same on 73 but changes everytime you request it on the one i'm on.. 1.85, But I give up on the whole thing. Seems like I jumped a step or missed something because I'm pretty sure i'm stuck here till theres an exploit for 85 directly or another update comes out -- because I'm not going to pound away at getting new tokens all night and hoping one might unlock the bootloader.

[Q] Recovering to stock...which RUU for me?

I have an At&t HTC One X that I bought from a licensed store in Jersey.
I used a hex editior to change the CID so I could use HTCdev to unlock the bootloader (so my current CID is Roger001, which was not the original CID). Currently installed CleanROM 4.0.
Want to get back to stock to return phone...what information do I need to provide so that someone can tell me what RUU to use? In settings I see build number 1.85.502.3...hboot is 1.09.0000...radio is 0.17.32.09.12.

You can relock your bootloader then change your CID back to CWS__001 using the same hex hack method you used to make it a ROGERS CID then run the 1.85 RUU and your back to stock. One thing is your bootloader will still say relocked at the top but there is nothing you can do about that but hope they don't look at that and deny you.

Link to the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238

So I hack the CID back, lock the bootloader, and run the RUU mentioned and that's it? I figured my hboot version, radio version and all the rest of it would lead me to a different RUU than the one you pointed to...

When you RUU back to 1.85 it will flash everything to the 1.85 versions.

If I lock the bootloader, how do I change the CID back? When I hacked the CID and used ADB my phone was on with the ROM loaded and plugged in...If I lock the bootloader, I can only get into the hboot screen...can I still ADB push and pull from there?
And if I'm planning on flashing the 1.85 RUU, do I need to change the CID at all? Can't I just lock the bootloader, and then run the .exe?

Locked bootloader and then ran the 1.85 RUU you pointed me to...received error 131...back to Hboot with a locked bootloader...any suggestions? Y'all made it sound so simple...

Because you didn't change Cid. Error 131
You can still unlock then push a recovery then from that recovery put a rom on the phone and flash. Use twrp.

So from here...unlock bootloader...then push twrp recovery...at what point do I change the CID and run the RUU to get back to stock?

aram12 said:
So from here...unlock bootloader...then push twrp recovery...at what point do I change the CID and run the RUU to get back to stock?
Click to expand...
Click to collapse
after you have a rooted ROM on it and can access the proper partition with a hex editor to change the CID back after that you can relock bootloader and run RUU

This is why you get nexus, just flash stock images
Sent from my Galaxy Nexus using Tapatalk 2

supercid says 11111111 on 2.20 but cant unlock bootloader

i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help

saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.

saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.

get into bootloader manually volume down + power.

Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?

Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935

Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?

Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though

That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!

thanks everyone i solved my problem.dint except quick replies from you guys.

Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.

OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?

Without root you can't get super Cid

Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium

[Q] HOX AT&T Update

Hello, I have my HTC One X of AT&T unlocked by code through AT&T. It´s Rooted and it´s Bootloader is unlocked and also has the CWM Recovery installed. Never flashed any ROM, it still have the Original ICS ROM, it´s S-ON. Can I update it manually or would I be bricking it?
I was going to follow this tuto http://www.titularesandroid.com/2013/03/actualiza-tu-htc-one-x-at-jelly-bean.html?showComment=1364530268627#c3645276792953205699 but it says that it shouldn´t have "SuperCID and S-on" I don´t have SuperCID because I legally unlocked it, my doubt is about S-on, should I be S-off? If I have to, how do you do it? Thank you.

philohtc said:
Hello, I have my HTC One X of AT&T unlocked by code through AT&T. It´s Rooted and it´s Bootloader is unlocked and also has the CWM Recovery installed. Never flashed any ROM, it still have the Original ICS ROM, it´s S-ON. Can I update it manually or would I be bricking it?
I was going to follow this tuto http://www.titularesandroid.com/2013/03/actualiza-tu-htc-one-x-at-jelly-bean.html?showComment=1364530268627#c3645276792953205699 but it says that it shouldn´t have "SuperCID and S-on" I don´t have SuperCID because I legally unlocked it, my doubt is about S-on, should I be S-off? If I have to, how do you do it? Thank you.
Click to expand...
Click to collapse
I would S-OFF. I can explain the steps I took but it may have been a bit overkill. I had a 1.09 hboot so I didn't want to take any risks. I'm on Telus which is only up to 3.17. I'm not sure how 3.18 would go as I understand AT&T has put a mechanism for checking with AT&T over the network. Nevertheless.
- I downloaded the RUU for my phone which was in my case a TELUS RUU 1.91.661.4 and then I extracted the rom from the RUU and the Hboot from the ROM and I flashed the stock Hboot.
- I Booted into the bootloader/fastboot and then I changed my CID back to default, in my case TELUS001. (I don't think you need to do this with S-OFF but it takes less than a minute to do)
- Rebooted back to bootloader/fastboot and ran the RUU
- When the RUU was done I was on ICS.
- Re-Unlocked my bootloader (I'm not on AT&T so no need for Super CID for me, was just to get S-OFF)
- Flashed TWRP
- Boot back to rom to get OTA
- After OTA was done, Booted to TWRP to root stock then nandroid backup for good measure, then flash whatever

philohtc said:
I don´t have SuperCID because I legally unlocked it,
Click to expand...
Click to collapse
SuperCID has nothing to do with SIM unlock. SIM unlock of course allows you to use the phone with another carrier's SIM. CID and SuperCID relate to the HTC firmware such as RUUs and OTAs (typically only allows you to install software intended for your carrier version).
If your phone is the AT&T version, and its bootloader unlocked it must be SuperCID. Period.
SuperCID + OTA = brick
SuperCID + RUU = brick
That is, unless you have S-off. So do the facepalm s-off if you want to RUU or OTA.
Another approach is just flash a stock rooted Jellybean ROM, or a custom ROM based on the AT&T update, such as CleanROM 6. These can be found in the Development forum section.

Get SuperCid,S-off, you are already unlocked but when you get those just ruu to the current OTA and wallah.

so philohtc are you now s-off with jb update?

Not yet, but I'm not 100% sure yet, still having doubts. Because I remember when unlocking the bootloader the CID was all in 1. So how do I put the original CID ? My steps would be the following (Please correct me if I am wrong): 1st- Facepalm S-off 2nd- SuperCID? 3rd- Update through HTC Software Device?. Please give me all the warnings so I don´t brick my phone, thank you!

Boot to bootloader/fastboot.
Do fastboot oem readcid
This will tell you your Cid
If it's 11111111 or 22222222 then proceed to S-OFF.
If not, proceed to SuperCID then S-OFF
Once your S-OFF, Run the RUU
If you want to be anal like I was, after s-off, before running the ruu, you can change your Cid back to an at&t Cid using fastboot oem writecid xxxxxxxx where the X's are the default Cid. I don't know it for at&t by heart.
Sent from my One X using xda app-developers app

exad said:
If you want to be anal like I was, after s-off, before running the ruu, you can change your Cid back to an at&t Cid using fastboot oem writecid xxxxxxxx where the X's are the default Cid. I don't know it for at&t by heart.
Click to expand...
Click to collapse
CWS__001

Appreciate that, thanks bud
Sent from my One X using xda app-developers app

[Q] HTC ONE X ATT Messed up, Reboot loop

OK, tried to root my HTC One X, got the HTCDev unlock, but could never get an S-OFF on 5.18 firmware. Did have a CID unlock, so set it back to OEM Relock, and have tried to RUU the exact firmware back. It says its sucsessful but get a loop condition, White HTC, then a strange black screen, when I get back to Bootloader and tried again, same result. Any ideas, attached are pic. of strange screen and Bootloader

mbardsley said:
OK, tried to root my HTC One X, got the HTCDev unlock, but could never get an S-OFF on 5.18 firmware. Did have a CID unlock, so set it back to OEM Relock, and have tried to RUU the exact firmware back. It says its sucsessful but get a loop condition, White HTC, then a strange black screen, when I get back to Bootloader and tried again, same result. Any ideas, attached are pic. of strange screen and Bootloader
Click to expand...
Click to collapse
What were you trying to do in the first place? When you say CID unlock do you mean bootloader unlock? I think you're a bit confused about what you've been doing. Why did you relock the bootloader? What is your CID currently? Do not attempt to run the RUU again until we can confirm what your CID is, you could brick your phone.
Sent from a crappy Samsung because my Evita died

Confirmed CID is showing all 11111111, bootloader screen now says ***TAMPERED*** then ***UNLOCKED*** and still has S-ON, and this was a 5.18, which I think was my mistake for trying. Cannot run RUU utility, it wont complete, can get into TWRP recovery 2.6.0.0 but not able to flash, or anything. At this time would love to be able to just flash back to my stock.

Flash a Sense ROM, get s-off, run the RUU.
Sent from a crappy Samsung because my Evita died

THANKS! That did the trick, I knew I was close, but thought I had to get S-OFF before a flash of ROM.