Database Info

CID change with S-ON!

UPDATE: Apparently it is only possible to change the CID with S-ON if your current CID is SuperCID.
*issue closed*
I had used Revolutionary to de-brand my phone. First S-OFF, then SuperCID, then a stock unbranded ROM, then back to S-ON.
I wasn't getting the OTA to 2.3.4 here in The Netherlands, so I changed my CID to HTC__E11, which is the CID for an unbranded Sensation in The Netherlands. Lo and behold, I got the OTA immediately.
Interesting to note, I was able to change the CID using "fastboot oem writecid HTC__E11" with S-ON. Someone else was able to do exactly the same thing so it's confirmed to work.
Now that I have upgraded to 2.3.4 and have my CID set to HTC__E11, this no longer works for me. However I'm wondering if it *does* work for people still on 2.3.3, or if it only worked for me because I was already SuperCID. I wonder if others who are still on 2.3.3 are able to use "fastboot oem writecid 11111111" with S-ON (i.e. without using Revolutionary).
So, using adb tools on a stock ROM:
NOTE: If you test this you do so at your own risk.
0. download and unzip adb tools to a folder. make sure HTC Sync is not running (uninstall, or just exit/kill the application).
1. open command prompt and "cd" your adb folder
2. ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (ensure usb debugging is on settings).
3. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
4. enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
5. enter the command "fastboot oem writecid 11111111"
6. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
7. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
8. enter the command "fastboot reboot"
9. you should now be able to flash any stock ROM you like.
NOTE: Please DO NOT change your CID to HTC__E11 unless you are in The Netherlands. HTC__E11 is the CID for an unbranded Sensation in The Netherlands. If you are in a different country, check for the appropriate CID here: http://forum.xda-developers.com/showthread.php?t=1195475&page=3.

I've already de-branded my phone, but I wonder if others are able to using "fastboot oem writecid 11111111" without using Revolutionary.
Click to expand...
Click to collapse
Yes, I have. In fact I believe that method is in one of the tutorials here.
Here is a link that describes it: http://forum.xda-developers.com/showthread.php?t=1192300

kmdub said:
Yes, I have. In fact I believe that method is in one of the tutorials here.
Here is a link that describes it: http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
No, that tutorial uses Revolutionary first to go from S-ON to S-OFF before changing the CID. I was able to change my CID with S-ON.

so I'm changing my cid to 11111111?
not HTC__E11?

zahashingo123 said:
so I'm changing my cid to 11111111?
not HTC__E11?
Click to expand...
Click to collapse
11111111 is the SuperCID. HTC__E11 is the CID for unbranded Sensations in The Netherlands. If you don't use the SuperCID, you may want to refer to http://forum.xda-developers.com/showthread.php?t=1195475&page=3 for a list of CIDs.
I changed to the SuperCID using Revolutionary to first get S-OFF. Then I set S-ON. But even with S-ON, I was still able to change my CID (I changed it to HTC__E11 in order to receive the OTA to 2.3.4.).
So what I'm wondering is if people with 2.3.3 and S-ON are able to change their CID to the SuperCID 11111111, without first using Revolutionary to change to S-OFF.

Ok, I must have misunderstood your question. It seems as if you have clarified your question since your original post. I just thought you were asking if one could write the CID without Revolutionary. My bad. FYI, I have not tried what you are asking.
I changed to the SuperCID using Revolutionary to first get S-OFF. Then I set S-ON.
Click to expand...
Click to collapse
A statement like this, though, I don't really understand. Two questions come to mind: 1) How did you set S-ON? and 2) Were you able to confirm that you wrote a new CID with S-ON, or did you just not get an error message?

kmdub said:
Ok, I must have misunderstood your question. It seems as if you have clarified your question since your original post. I just thought you were asking if one could write the CID without Revolutionary. My bad. FYI, I have not tried what you are asking.
A statement like this, though, I don't really understand. Two questions come to mind: 1) How did you set S-ON? and 2) Were you able to confirm that you wrote a new CID with S-ON, or did you just not get an error message?
Click to expand...
Click to collapse
I set S-ON using the instructions on how to set S-ON here http://forum.xda-developers.com/showthread.php?t=1192300 and I confirmed it during reboot, the text "S-ON" was back on the boot screen.
I wrote the new CID with S-ON, then confirmed it by rebooting and running the command "fastboot getvar cid", which gave me the phone's CID, which indeed was the new CID I'd written. In addition, with the new CID (unbranded Dutch, instead of SuperCID), I immediately got the OTA to 2.3.4.

Someone need to test this with a stock phone!
Or try to set secureflag to 1 maybe its not really changed ...

xtcislove said:
Someone need to test this with a stock phone!
Click to expand...
Click to collapse
That's exactly what I'm asking people to do.
xtcislove said:
Or try to set secureflag to 1 maybe its not really changed ...
Click to expand...
Click to collapse
What's your problem, can't you read? I wrote already, the phone reports "S-ON" in the boot screen, and after a reboot, it still reports the new CID, and after setting the new CID, I got the Netherlands OTA immediately.

I tried it with stock s-on phone and it doesn't work.
Code:
C:\AndroidSDK\tools>fastboot oem writecid 11111111
...
(bootloader) pyramid_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.172s]
finished. total time: 0.172s
It still reports same cid.

supendal said:
I tried it with stock s-on phone and it doesn't work.
It still reports same cid.
Click to expand...
Click to collapse
Thanks for testing this - just to confirm, you tested with 2.3.3 and not 2.3.4, right?
If so, then it seems to imply that you can change the CID even with S-ON but only if you currently have SuperCID.

Then I have no idea. I would not think one could write a new CID with S-ON, regardless of the ROM. However, you have tried it and claim it works, so someone with more knowledge will have to explain why...lol
I notice in the tutorial it says "secureflag 3," which at least gives you S-ON displayed, and perhaps does set the security back on. I wonder what 0,1,and 2 do, though. Is it 0,1,2, or 3 on stock phone with S-ON?

sowen222 said:
Thanks for testing this - just to confirm, you tested with 2.3.3 and not 2.3.4, right?
Click to expand...
Click to collapse
Yes, tested on stock s-on phone and stock 2.3.3 rom. 2.3.4 Ota update is still not available here.

well i do also have s-on and managed to change cid to HTC__E11 with adb and also like the OP can't seem to change it back to what it was (stock sensation with 1.50...rom) does the cid mathers in terms of warranty and ota updates??? (i'm in the netherlands)
regards
edit:well OTA updates do work on my side but still no luck changing the CID again.

nobody here that can decifer this one??

I have a sendation xe with hboot 1.18 and s-on.
I used the commands to change CID from HTC__038 to HTC__001.
I still don't receive the OTA update on my phone though.
The phone was bought from Hong Kong but from using the CID Getter app it shows CID at the top as HTC__001 now but when you scroll through the data there are still reference to it being an indian phone.
I am looking to change it to stock Euro gingerbread with CID 001 so that I can receive the OTA ICS update.
I can't use revolutionary to change to S-OFF as always fails. I can't install the RUU for euro GB as it gives an error when I try to run it.
Not having any joy asking people for help so far either.

remove supercid??

Back when i first got my phone i did the supercid mod on my phone, everytime i flash a rom i have to do other things just because of it (larger mms, install wifi calling patch etc etc) my girlfriends sensation on the other hand is NOT supercid and she never has to do any of the additional patches i have to do.
So is there any way i can reverse the supercid mod on my phone?

Super CID has nothing to do with patch flashing, but if you want to return to stock cid just fallow the steps to get the super cid and replace "11111111" with your original cid.
If your phone was unbranded your cid should be "HTC__001"

_HTC_DHD_ said:
Super CID has nothing to do with patch flashing, but if you want to return to stock cid just fallow the steps to get the super cid and replace "11111111" with your original cid.
If your phone was unbranded your cid should be "HTC__001"
Click to expand...
Click to collapse
how do i know what my original cid would be?

Hello well if you you know how to use the adb command tool (black window with command line) you just type in "adb getvar cid" and it should show your original cid hope I could help
Edit: use while phone is connected with USB debugging on

I AM M07S said:
Hello well if you you know how to use the adb command tool (black window with command line) you just type in "adb getvar cid" and it should show your original cid hope I could help
Edit: use while phone is connected with USB debugging on
Click to expand...
Click to collapse
That is wrong. If you use that, i'll only show the CURRENT CID of the phone, which would be superCID in this case.
There's a CID database somewhere in the development section. Search for it. It has a comprehensive list of CIDs with your carriers name.

illuminarias said:
That is wrong. If you use that, i'll only show the CURRENT CID of the phone, which would be superCID in this case.
There's a CID database somewhere in the development section. Search for it. It has a comprehensive list of CIDs with your carriers name.
Click to expand...
Click to collapse
Oh well I'm sorry but last time I did this it gave me my original and I know this because I have changed it to SuperCID and last night infact I was playing with the adb commands and it gave me my original CID unless of course it has gone back to the original which in that case i am really sorry for being a noob to the android xda community (but im only 17)

If you are on T-Mobile US, then the CID is T-MOB010.
Sent from my HTC Sensation Coredroid 2.7

Try this...
Hi,
I had problems with WIFI calling not installing, so I decided to remove SuperCID. I followed the instructions in this post:
http://forum.cyanogenmod.com/topic/31756-wifi-calling-missing-you-have-supercid-here-is-a-solution/
I didn't use the file from the post, as it didn't work for me. I found another file and everything worked perfectly, I am attaching the new file.
Please be aware that this will get you ENG S-OFF.

cgjjaf said:
Hi,
I had problems with WIFI calling not installing, so I decided to remove SuperCID. I followed the instructions in this post:
http://forum.cyanogenmod.com/topic/31756-wifi-calling-missing-you-have-supercid-here-is-a-solution/
I didn't use the file from the post, as it didn't work for me. I found another file and everything worked perfectly, I am attaching the new file.
Please be aware that this will get you ENG S-OFF.
Click to expand...
Click to collapse
Thanks for the help, it's ****ing monday morning and i feel dumb, but what is ENG S-OFF?

I unlocked my phone using xda guide, at the moment I have super cid, if I reverse my cid back to original, will I loose my unlock?

raul602 said:
Thanks for the help, it's ****ing monday morning and i feel dumb, but what is ENG S-OFF?
Click to expand...
Click to collapse
engineering bootloader with security off..basically meaning you have read/write permissions for the system and can flash a custom rom..Since you changed your CID, you also should be S-OFF.
However, I don't think you fully understand what CID does, b/c I don't see how this would cause the issues your having. Super CID allows for you to flash a STOCK rom from another carrier, so you could flash an unbranded Sensation RUU or a TMo-US S4G RUU, or whatever, through bootloader. It allows to "debrand" your phone, meaning you're not stuck to your carrier specific rom. This is different than flashing a custom rom thru recovery, which your CID doesn't matter, bc custom roms are not carrier specific roms..
CID is basically just a variable that tells the RUU what carrier your phone is from and what rom can be flashed on it.
Now, to get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Hope that cleared things up some.
bakili said:
I unlocked my phone using xda guide, at the moment I have super cid, if I reverse my cid back to original, will I loose my unlock?
Click to expand...
Click to collapse
No it will not..CID is basically just a variable, you need to have S-OFF to change it, but changing it won't effect S-OFF or SIM unlock..

civicvx94 said:
engineering bootloader with security off..basically meaning you have read/write permissions for the system and can flash a custom rom..Since you changed your CID, you also should be S-OFF.
However, I don't think you fully understand what CID does, b/c I don't see how this would cause the issues your having. Super CID allows for you to flash a STOCK rom from another carrier, so you could flash an unbranded Sensation RUU or a TMo-US S4G RUU, or whatever, through bootloader. It allows to "debrand" your phone, meaning you're not stuck to your carrier specific rom. This is different than flashing a custom rom thru recovery, which your CID doesn't matter, bc custom roms are not carrier specific roms..
CID is basically just a variable that tells the RUU what carrier your phone is from and what rom can be flashed on it.
Now, to get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Hope that cleared things up some.
No it will not..CID is basically just a variable, you need to have S-OFF to change it, but changing it won't effect S-OFF or SIM unlock..
Click to expand...
Click to collapse
First of all, thank you very much for your response, I really didn't know exactly what it was till you explained it, THe reason i want to revert back to stock is simply because there are certain things that never seem to work on my phone that always work perfectly on my girlfriends phone, first one being WIFI(never gets installed and second being small mms pics, the ONLY difference between her and my phone is that i am superCID and she is not, i can get the patches and fix it but i don't really need supercid now that i understand it.
Seriously though, thank you!

No problem at all, glad to help! Hope you get things figured out..

[Q] Question for robocik

When I install hboot 1.20 on my sensation I got warning CID failed! press Power for restart. I can't install hboot 1.17. again CID failed! What to do?

randda said:
When I install hboot 1.20 on my sensation I got warning CID failed! press Power for restart. I can't install hboot 1.17. again CID failed! What to do?
Click to expand...
Click to collapse
Did you supercid before doing this?
You might know what I'm telling you already, if so, please simply ignore my message. In case you are wondering what supercid is and how to do it: it is setting the cid (carrrier ID) variable on your phone to the value 11111111 so that your cid becomes a superID. You can accomplish this very easily via ADB commands, but it is worth reading up on. For instance you'll probably want to write down your current cid in case you ever want to go back to a stock alike condition for your warranty.
Please search for +sensation +adb +supercid.

HorstDCC said:
Did you supercid before doing this?
You might know what I'm telling you already, if so, please simply ignore my message. In case you are wondering what supercid is and how to do it: it is setting the cid (carrrier ID) variable on your phone to the value 11111111 so that your cid becomes a superID. You can accomplish this very easily via ADB commands, but it is worth reading up on. For instance you'll probably want to write down your current cid in case you ever want to go back to a stock alike condition for your warranty.
Please search for +sensation +adb +supercid.
Click to expand...
Click to collapse
Step 4 in this thread
http://forum.xda-developers.com/showthread.php?t=1192300

Stock on fastboot oem writecid 11111111
<waiting for device>
Help!

Unable to re-unlock bootloader--HELP!

So I am ATT One X and was on Magnolia rom 1.82. I tried to upgrade to the latest RUU by re-locking the bootloader. Because I used the Rogers CID before to Unlock, I had to change the CID to SuperCID before upgrading.
After I changed from Rogers CID to SuperCID, relocked, upgraded to 1.85 RUU, I attempted to re-unlock via HTC-DEV. I went through all the steps and successfully received and unlock code and successfully flashed it.
HOWEVER!!!! The bootloader still says RELOCKED and I can't flash stuff.
I tried changing the CID back to ROGER001 and running the original unlock key but that failed to i went through HTCDEV with that CID and got the unlock code, successfully flashed it, but still had the RELOCKED bootloader.
Did I mess something up???? Please tell me i didn't....Any help is appreciated

b3nman said:
So I am ATT One X and was on Magnolia rom 1.82. I tried to upgrade to the latest RUU by re-locking the bootloader. Because I used the Rogers CID before to Unlock, I had to change the CID to SuperCID before upgrading.
After I changed from Rogers CID to SuperCID, relocked, upgraded to 1.85 RUU, I attempted to re-unlock via HTC-DEV. I went through all the steps and successfully received and unlock code and successfully flashed it.
HOWEVER!!!! The bootloader still says RELOCKED and I can't flash stuff.
I tried changing the CID back to ROGER001 and running the original unlock key but that failed to i went through HTCDEV with that CID and got the unlock code, successfully flashed it, but still had the RELOCKED bootloader.
Did I mess something up???? Please tell me i didn't....Any help is appreciated
Click to expand...
Click to collapse
Check for errors in the command prompt when you try to unlock. What does it say?

dimgl said:
Check for errors in the command prompt when you try to unlock. What does it say?
Click to expand...
Click to collapse
none whatsoever everything goes flawlessly. just when i reboot into the bootloader it says RELOCKED at the top.

Do you think its because i unlocked with the Rogers CID and then Re-unlocked with the Super CID?

I think some users reported having to attempt BL unlock multiple times on 1.85 before it worked. Pretty sure I read that on one of the bootloader unlock threads in Development (can't remember if it was the one-click SuperCID thread, or the "original" hex editor method thread).
Mine worked the first try on 1.85. I used the same bin file that unlocked 1.73.

redpoint73 said:
I think some users reported having to attempt BL unlock multiple times on 1.85 before it worked. Pretty sure I read that on one of the bootloader unlock threads in Development (can't remember if it was the one-click SuperCID thread, or the "original" hex editor method thread).
Mine worked the first try on 1.85. I used the same bin file that unlocked 1.73.
Click to expand...
Click to collapse
Thats the thing. I changed the CID from when i originally Unlocked it. Has anyone successfully done this?

SOLVED
I figured it out.
When you select power off or reset from the Power Menu, OR use the adb reboot command from command line, it doesn't really completely power off. So you have to actually hold the power button until it completely powers down and THEN start the bootloader for the the unlocked change to take effect. At least thats what happened with me. Your mileage may vary....

Make sure when you boot up to turn on usb debugging you also turn off fast boot (settings/power) its not the fast boot we're used to but its HTCs way of not completely powering off the phone to give a faster boot time. I personally had to run the unlock twice to get the bootloader to say unlocked instead of relocked.
Hope this helps.
Sent from my HTC One X using xda premium

Dear god, this thread should be a sticky. After 30 tries, I disable fastboot, power off completely using the power button and when I booted to the bootloader, it was unlocked.

[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