Related
I am still on the stock ROM, but I am rooted with ClockworkMod recovery. Recently I followed the instructions in this thread to write SUPER CID to my phone.
In order to get OTA updates, I know I'll need to get back to the stock recovery, but do I need to do anything about my CID?
Yes you have to change you CID. SuperCID will not receive OTA updates
Sent from my HTC Sensation Z710e using XDA
Keupie said:
Yes you have to change you CID. SuperCID will not receive OTA updates
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
Thank you! Now for the obligatory n00b follow-up: Where can find what value to change it back to?
Doing some more reading and realizing that I need to flash a stock ROM from here to get back to my old CID.
However, my wife has exactly the same phone as I do without SUPER CID. If I can get her CID using ADB Tools, can I just write that value to my phone?
Or would restoring a nandroid backup from before writing SUPER CID return me to my original CID?
It depends on wich RUU you flashed, in wich region you are. For example: for Europe you can use HTC__001. I used HTC__E11, the dutch cid
Sent from my HTC Sensation Z710e using XDA
I dont think doing a back up or flashing a rom will change the cid, you have to do this through adb
Sent from my HTC Sensation Z710e using XDA
Keupie said:
It depends on wich RUU you flashed, in wich region you are. For example: for Europe you can use HTC__001. I used HTC__E11, the dutch cid
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
Is there a list of these somewhere, or would you happen to know the CID for TMOUS?
Alright, I found a list of CIDs in this thread.
Also, a few comments in I read that when you write SUPER CID, a backup of your old CID actually gets stored in your phone. You can access it by installing Terminal Emulator (from the market) and running the command: getprop ro.cid
For me, this confirmed that my CID was T-MOB010, which I have now written with ADB and am on my merry way.
RUU or a backup restore will not restore your CID as it's a separate setting. As you've found the thread I was going to suggest then you can find it there
This is why people should get ALL the information from their phone (original CID, RUU, etc) before flashing anything so they have it all to hand should they need it
EddyOS said:
RUU or a backup restore will not restore your CID as it's a separate setting. As you've found the thread I was going to suggest then you can find it there
This is why people should get ALL the information from their phone (original CID, RUU, etc) before flashing anything so they have it all to hand should they need it
Click to expand...
Click to collapse
Yes indeed. Live and learn!
Keupie said:
Yes you have to change you CID. SuperCID will not receive OTA updates
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
I SuperCID my phone a while back to 11111111 and I just reflashed stock rom back and was able to get OTA updates and was able to installed them too.
So Yes, you can have SuperCID and also get OTA
T-MOUS
I just got a AT&T HTC One X, and I never dealt with a HTC before (mostly Samsung). Right now the HTC is pure stock AT&T firmware 1.85. I need some helping guiding me what steps to take cause I'm confuse by it all. This is what I have so far from my research:
Step 1: RUU to 2.20? (not entirely sure on this)
Step 2: Use toolkit to get root
Step 3: Not sure which method to use but I need Supercid to 22222222 because HTCdev blocked AT&T and 11111111.
Step 4: Unlock Bootloader
Step 5: S-OFF, (is facepalm compatible with AT&T X?)
Step 6: Flash roms and have fun.
I appreciate any help and please tell me if I miss some steps.
deathsycthehe11 said:
I just got a AT&T HTC One X, and I never dealt with a HTC before (mostly Samsung). Right now the HTC is pure stock AT&T firmware 1.85. I need some helping guiding me what steps to take cause I'm confuse by it all. This is what I have so far from my research:
Step 1: RUU to 2.20? (not entirely sure on this)
Step 2: Use toolkit to get root
Step 3: Not sure which method to use but I need Supercid to 22222222 because HTCdev blocked AT&T and 11111111.
Step 4: Unlock Bootloader
Step 5: S-OFF, (is facepalm compatible with AT&T X?)
Step 6: Flash roms and have fun.
I appreciate any help and please tell me if I miss some steps.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1709296 <--- root method for 1.85 I would try that before RUUing up to 2.20
I would try 11111111 first since that's what SuperCID gives you be default. If that doesn't work, then I would fastboot oem writecid 22222222 You can only change CID once without S-OFF so make sure to enter it right.
Other than that, you seem to be on the right path.
S-OFF directions are in the onexl orig. android dev. section so yes, compatible.
Good Luck, don't brick.
exad said:
http://forum.xda-developers.com/showthread.php?t=1709296 <--- root method for 1.85 I would try that before RUUing up to 2.20
I would try 11111111 first since that's what SuperCID gives you be default. If that doesn't work, then I would fastboot oem writecid 22222222 You can only change CID once without S-OFF so make sure to enter it right.
Other than that, you seem to be on the right path.
S-OFF directions are in the onexl orig. android dev. section so yes, compatible.
Good Luck, don't brick.
Click to expand...
Click to collapse
The 1.85 root seems a bit more complicated than the toolkit for 2.20. Which SuperCid method should I use then?
Hexedit your Cid.
Sent from my One X using xda app-developers app
exad said:
Hexedit your Cid.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hey Exad, the day has come when I need to ask your advice on something. I'm gonna RUU up to 3.18 then downgrade my TS firmware so I can have a look at these new Carbon builds running the 3.4 kernel (which don't play nice with my current setup). So I need to gain SuperCID in order to s-off, having a Hong Kong issue phone on 1.85 never required me to have SuperCID in order to root. Anyway long story short, my question is: I should be able to just issue the following fastboot command in order to gain SuperCID right?
fastboot oem writecid 11111111
That should be fine yeah?
timmaaa said:
Hey Exad, the day has come when I need to ask your advice on something. I'm gonna RUU up to 3.18 then downgrade my TS firmware so I can have a look at these new Carbon builds running the 3.4 kernel (which don't play nice with my current setup). So I need to gain SuperCID in order to s-off, having a Hong Kong issue phone on 1.85 never required me to have SuperCID in order to root. Anyway long story short, my question is: I should be able to just issue the following fastboot command in order to gain SuperCID right?
fastboot oem writecid 11111111
That should be fine yeah?
Click to expand...
Click to collapse
No, only if you have already achieved s-off, you can change by "fastboot oem writecid" Have to hex edit it if not.
Sent from my HTC One
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
timmaaa said:
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
I think he meant BEFORE achieving s-off, you can change your cid ONCE. However, after gaining s-off, you can change ur cid as many as you want.
Sent from my HTC One
timmaaa said:
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
That should be correct
Sent from my HTC One X using Tapatalk 2
Thug_4_Life said:
I think he meant BEFORE achieving s-off, you can change your cid ONCE. However, after gaining s-off, you can change ur cid as many as you want.
Sent from my HTC One
Click to expand...
Click to collapse
Yeah and that's exactly what I want to do, and what I was asking. I need to change my CID once, to 11111111, so I can s-off.
Sent from my Evita using XDA Premium
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
timmaaa said:
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
Oops, I meant while s-on.
Sent from my Evita using XDA Premium
Yes. Unless you don't trust me haha
Sent from my HTC One
Thug_4_Life said:
Yes. Unless you don't trust me haha
Sent from my HTC One
Click to expand...
Click to collapse
No disrespect man, but you've contradicted yourself above. I prefer confirmation from someone like InflatedTitan or Exad, as I know without a shadow of a doubt they know what they're talking about.
Sent from my Evita using XDA Premium
timmaaa said:
No disrespect man, but you've contradicted yourself above. I prefer confirmation from someone like InflatedTitan or Exad, as I know without a shadow of a doubt they know what they're talking about.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
Good morning! ^_^
So, here's the scoop. After you Super CID, you can change your CID 1 time using fastboot oem writecid if you are S-ON
If you are S-OFF you can use that command as many times as you like.
If you have not already SuperCID'd and you are S-ON you would need to SuperCID first either by running the exploit script or hexiditing your CID manually.
I think that's what Thug_4_Life was trying to say too.
exad said:
Good morning! ^_^
So, here's the scoop. After you Super CID, you can change your CID 1 time using fastboot oem writecid if you are S-ON
If you are S-OFF you can use that command as many times as you like.
If you have not already SuperCID'd and you are S-ON you would need to SuperCID first either by running the exploit script or hexiditing your CID manually.
I think that's what Thug_4_Life was trying to say too.
Click to expand...
Click to collapse
Just one question that has been itching me for a long time. Is it correct that you can fastboot oem writecid while s-on? Until now, I believed that it was only after you gain s-off?
Sent from my HTC One
Thug_4_Life said:
Just one question that has been itching me for a long time. Is it correct that you can fastboot oem writecid while s-on? Until now, I believed that it was only after you gain s-off?
Sent from my HTC One
Click to expand...
Click to collapse
Only once if you've already SuperCID'd but not if you haven't already superCID'd
Thug_4_Life said:
No, only if you have already achieved s-off, you can change by "fastboot oem writecid" Have to hex edit it if not.
Sent from my HTC One
Click to expand...
Click to collapse
Exad will correct me if I'm wrong. But this was only true for ATT models. they weren't able to change cid, hence why it takes so long for ATT users so long to find an exploit then change cid.
That's why any other carriers are able to root no problem, there's far less restrictions. Beings he has one from hong Kong, I would imagine he can rewrite the cid because if this.
Personally I would give it a shot.
fastboot oem writecid 11111111
However beings we had a supercid script I don't know what happens if it doesn't write.. Fail I suppose
Sent from my HTC One X using Tapatalk 2
InflatedTitan said:
Exad will correct me if I'm wrong. But this was only true for ATT models. they weren't able to change cid, hence why it takes so long for ATT users so long to find an exploit then change cid.
That's why any other carriers are able to root no problem, there's far less restrictions. Beings he has one from hong Kong, I would imagine he can rewrite the cid because if this.
Personally I would give it a shot.
fastboot oem writecid 11111111
However beings we had a supercid script I don't know what happens if it doesn't write.. Fail I suppose
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
No, even non ATT phones follow the same restrictions, the only difference is HTCDev allows other carriers to unlock through HTCDev without having to SuperCID.
Since S-OFF requires CID to be 11111111 I wrote that Hex guide so we could change our CID to gain S-OFF too.
exad said:
No, even non ATT phones follow the same restrictions, the only difference is HTCDev allows other carriers to unlock through HTCDev without having to SuperCID.
Since S-OFF requires CID to be 11111111 I wrote that Hex guide so we could change our CID to gain S-OFF too.
Click to expand...
Click to collapse
Oh lol
Sent from my HTC One X using Tapatalk 2
So all in all, timmaaa must hex edit instead of fastboot oem writecid since he has yet to supercid, right?
Sent from my HTC One
Thug_4_Life said:
So all in all, timmaaa must hex edit instead of fastboot oem writecid since he has yet to supercid, right?
Sent from my HTC One
Click to expand...
Click to collapse
That's riiigggghhhttt! :laugh::good: <--- Good guy pose
so i am S - OFF and need to run a RUU (long Story)
so when i ran the RUU it said please download the right rom utility update
this is the one i ran http://bugsylawson.com/files/file/3...00528-10275008l-release-301814-signed-2-4exe/
and i changed my CID to HTC__001 and also i can change back to SuperCID 11111111
i heard you have to have a ruu which is lower than your HBOOT my HBOOT:2.13.0000
what shall i do please ould someone help thanks
Zaman-The-Man said:
so i am S - OFF and need to run a RUU (long Story)
so when i ran the RUU it said please download the right rom utility update
this is the one i ran http://bugsylawson.com/files/file/3...00528-10275008l-release-301814-signed-2-4exe/
and i changed my CID to HTC__001 and also i can change back to SuperCID 11111111
i heard you have to have a ruu which is lower than your HBOOT my HBOOT:2.13.0000
what shall i do please ould someone help thanks
Click to expand...
Click to collapse
Since you are Soff I don't think it matters what hboot it is. You just have to run the RUU that matches the CID. May want to double check, but that has been my experience. Once you are Soff it's easy to switch CID.
Sent from my HTC VLE_U using xda app-developers app
npiper05 said:
Since you are Soff I don't think it matters what hboot it is. You just have to run the RUU that matches the CID. May want to double check, but that has been my experience. Once you are Soff it's easy to switch CID.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
my cid is HTC__001 so shall i run the latest unbranded RUU could you link be to the latest unbranded RUU ? i dont trust my self
Zaman-The-Man said:
my cid is HTC__001 so shall i run the latest unbranded RUU could you link be to the latest unbranded RUU ? i dont trust my self
Click to expand...
Click to collapse
Sending you a PM now
I have been trying to run a RUU to unroot the phone before I bring it in for a repair. I keep getting the 155 error and I searched through google for help on the error. I have read a few post about it but nothing works. I tried to run it through fastboot as well and that does not work. My phone information while in bootloader is Evita pvt ship s-on rl hboot 1.09.0000 radio .17.32.09.12 and I am running cleanrom v 6.5 as my rom. Since my rom and boot.img is based of 3.18 I tried to run the ruu on 3.18. Im not sure if its because it is an older verdion of bootloader while im running a rom that is based off the 3.18. So I also tried to flash a older rom and run the ruu for 1.73 but that didnt work either. Im stumped and very frustrated so please I need your help.
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah for the 3.18 its http://bugsylawson.com/HTCFiles/Evi....24p.32.09.06_10.130.32.34_release_signed.exe
and for the 1.73 its http://www.ponack.net/designgears/b...73.502.2_2FE6772699D8596307CC997452BB8D25.exe
Also I read that in order to use the RUU correct I need to soff the phone, but then I cant upgrade the firmware to jellybean. Do you know if this is correct?
The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF
Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
exad said:
The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF
Click to expand...
Click to collapse
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?
cables2590 said:
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2156368
Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000
That is the right RUU for the AT&T version.
Is your phone stock or modded?
xoreg93 said:
Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000
Click to expand...
Click to collapse
If you have Super CID, do not run the RUU. It will brick your phone.
If you're not sure, type the following command into your command line:
fastboot oem
readcid
redpoint73 said:
That is the right RUU for the AT&T version.
Is your phone stock or modded?
Click to expand...
Click to collapse
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
If you have Super CID, do not run the RUU. It will brick your phone.
Click to expand...
Click to collapse
If the phone is s-on, yes that is right.
First of All Thanksss
yeahhhh its S-on
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
and no mine is not super cid ... so I will upgrade it. :highfive:
SuperCID just means that at&t phones were able to unlock via htcdev because the at&t CID was blocked. SuperCID + s-on + jb RUU = brick. This is because a CID check that occurs halfway through the RUU update doesn't allow the RUU to finish, therefore ending up with a partially completed RUU, which means a bricked phone.
Sent from my Evita
xoreg93 said:
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
Click to expand...
Click to collapse
What timmaaa mentioned is basically a bug. The RUU shoudn't run halfway like that, but for some reason on JB RUUs, it does (past RUUs were fine with SuperCID).
But also, what you said above is not true. SuperCID will not allow "any" RUU to work. It only bypasses CID check. Trying to run a RUU for an older hboot will fail version check. You need s-off to run "any" RUU.
thanksssss ALL Update Successful.....