Problem with two CID's - HTC Sensation

I have a sensation thats giving me two CID numbers.
If i use fastboot commands i get 11111111.
If i use CID getter i get VODAP001.
Phone is s-off, rooted and unlocked.
How can i get these the same?
The phone is downloading an ICS update but not installing it.

I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?

goatee84 said:
I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?
Click to expand...
Click to collapse
More accurately... Your correct CID is the one you get through:
Code:
fastboot getvar cid
If I use adb shell command:
Code:
getprop ro.cid
Then I get my original CID "T-MOB010"...
To the OP:
Go to your directory where adb and fastboot are, and type the following:
Code:
adb reboot bootloader
wait for bootloader to boot
Code:
fastboot oem writecid VODAP001
wait for it to flash
Code:
fastboot reboot-bootloader
wait for bootloader to boot
Code:
fastboot getvar cid
verify that the output is "VODAP001"
Code:
fastboot reboot
wait for device to reboot and you should be able to install your update if you're on an unaltered stock ROM...

Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.

If you apply SuperCID, your phone has 2 CIDs:
the actual CID, which is 11111111
and the backup CID, which is a backup of the
cid the phone was before(shipped).
The backup CID is stored in the misc partition,
and i havent tried yet, but there are following fastboot cmds:
fastboot oem erasebcid
fastboot oem readbcid
fastboot oem writebcid
I think theyre the appropriate cmds for handling the bcid.
After deleting the backup CID the only CID left is the (main) CID.
BTT: If you want to apply a ICS RUU, I think you have to change your CID back
to stock, because the RUU checks for a T-Mob phone, which your phone isnt if
you have SuperCID ;D
After the RUU, you can SuperCID again.
Edit:
Have not read the first time:
If you want to install a T-Mobile RUU on a Vodaphone Device,
you have to set one of the following CIDs, matching the RUU best:
TMA: T-MOB102
TMCZ: T-MOB004
TMD: T-MOB101
TMH: T-MOB007
TMHR: T-MOB006
TMMK: T-MOBL11
TMNL: T-MOB003
TMSK: T-MOB008
TMUK: T-MOB005
TMUS: T-MOB010
Greetz
criestr

ann-dr01d said:
Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.
Click to expand...
Click to collapse
Your stock ROM must be unaltered... Restore those apps if you still have them.

Related

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] How to check CID?

Help me in checking my stock CID..
abhishek89 said:
Help me in checking my stock CID..
Click to expand...
Click to collapse
You can use either of the following methods:
fastboot getvar cid
OR
download CIDgetter from the market
EDIT: The fastboot method will work if you have rewritten your CID, e.g. SuperCID. CIDgetter seems to read from a different place and returns your original CID even if you have written SuperCID to the phone.
If you NANDroid'd your Stock ROM, you can find your original CID in your build.prop

help finding correct RUU

My desire s hboot ver is 2.00.002 S-on and CID HTC__044 i just flashed CM7 few days ago and i want to go back on stock but backup is not working i think bcoz i changed boot.img for cm7 so i tried flashing RUU-Saga-S-hTC-Asia-WWE-2.15.707.2 and RUU_Saga_hTC_Asia_WWE_1.48.707.1 but both of these are not working can someone plz tell me which RUU i actualy need or what shld i do?
smartkiller84 said:
My desire s hboot ver is 2.00.002 S-on and CID HTC__044 i just flashed CM7 few days ago and i want to go back on stock but backup is not working i think bcoz i changed boot.img for cm7 so i tried flashing RUU-Saga-S-hTC-Asia-WWE-2.15.707.2 and RUU_Saga_hTC_Asia_WWE_1.48.707.1 but both of these are not working can someone plz tell me which RUU i actualy need or what shld i do?
Click to expand...
Click to collapse
CID HTC__044 means your phone is Asia WWE, so you have used the correct RUU.
may be you need to re-lock bootloader to run RUU
lock by command: fastboot oem lock
vndnguyen said:
CID HTC__044 means your phone is Asia WWE, so you have used the correct RUU.
may be you need to re-lock bootloader to run RUU
lock by command: fastboot oem lock
Click to expand...
Click to collapse
i did but still not working
so your hboot is S-OFF?
please post detailed information about your hboot
i did the same and i want to go back to official desire s ics update and i have tried so many ways but nothin works
if you manage to go back to official ics update let me know how
check out the link below worked for me, good luck!!!
http://forum.xda-developers.com/showthread.php?p=32950671#post32950671
Go into settings and and check your software number ...then from that you will be able to get your correct ruu
Maybe this will help:
Install Android SDK on your PC if not already done.
Then download this hboot.img : http://forum.xda-developers.com/attachment.php?attachmentid=666821&d=1311709396
and the correct RUU.
Then connect your phone to your pc and switch to load only mode and enable USB-Debugging.
Move the downloaded hboot.img to the root directory of your SD-Card.
Now open the command prompt and press after each line enter to execute the command.
cd/
cd C:\Program Files\Android\android-sdk\platform-tools [Path to your installed android-sdk]
adb devices
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
now restart the bootloader and follow the instructions to install the RUU.
Your phone should be locked and back to stock rom
I hope I helped you.

[Q] Trouble getting S-Off & SuperCID

Hey, I have a Rogers HTC One X and I've installed ViperXL 4.2 and recently it's been turning off the Data and i've been getting random restarts. I read around and it seems the problem is the radio and the way to fix it is to get S-Off. I followed a few tutorials and they've all ended in errors.
It seems like my phone has the Original CID, yet I can't change it even though the bootloader is unlocked.
I followed this Tut :http://forum.xda-developers.com/showthread.php?t=2155071
Tried this method for CID :http://forum.xda-developers.com/showthread.php?t=2212737
Any Ideas?
Try Rumrunner s-off instead, you don't need SuperCID for that.
Http://Rumrunner.us
Once you have s-off you can easily change your CID with a fastboot command:
Code:
fastboot oem writecid 11111111
Then you'll be able to flash the 2.15 firmware package.
Sent from my Evita.
timmaaa said:
Try Rumrunner s-off instead, you don't need SuperCID for that.
Http://Rumrunner.us
Once you have s-off you can easily change your CID with a fastboot command:
Code:
fastboot oem writecid 11111111
Then you'll be able to flash the 2.15 firmware package.
Sent from my Evita.
Click to expand...
Click to collapse
Awww yeah! Thanks dude!!!!

Categories

Resources