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.
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.
HI ALL
I HAVE SUPER CID 11111111
AND MY OTA UPDATE FOR ICS IS FOR HTC__622
SO I AM NOT ABLE TO UPDATE IT FROM BOOTLOADER
I HAVE BULID 1.77.708.104
S-OFF
CAN ANY ONE TELL HOW TO CHANGE ME DEVICE CID NO. TO HTC__622
SO I CAN GO ON WITH THE UPDATE
THANKS IS ADVANCE
Code:
fastboot oem writecid HTC__622
I am running elegancia 2.1.0 and I don't think this is a problem but when I run cid getter it comes back with tmob010. If I go into adb and run getvar it returnd cid 11111111. I think it is just cid getter that is not working correctly...any thoughts?
dssturk said:
I am running elegancia 2.1.0 and I don't think this is a problem but when I run cid getter it comes back with tmob010. If I go into adb and run getvar it returnd cid 11111111. I think it is just cid getter that is not working correctly...any thoughts?
Click to expand...
Click to collapse
Hi,
CID Getter will show you your original CID.
The fastboot one will show if you have supercid ( 11111111 )
Nothing unusual there.
Hey guys,
today I wanted to debrand my HTC Sensation z710a from Bell Mobility (Canada) to an unbranded version.
Some weeks ago I set my bootloader to S-OFF with revolutionary.
To perform this all, I used this tutorial:
http://www.htcinside.de/htc-sensation-branding-entfernen-so-gehts/
based on: http://forum.xda-developers.com/showthread.php?t=1193033 (Method 1)
To change the CID I did this:
Download the adb tools from here
Extract them to C:\adb
start cmd as an administrator
adb devices (to check if the phone is connected)
adb reboot-bootloader
fastboot getvar cid (I got BM___001)
fastboot oem writecid HTC__001 (for unbranded EU)
fastboot reboot-bootloader
fastboot getvar cid (I got HTC__001)
After that I pick up the desired RUU:
RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed.exe
I connected the phone to my computer (charge only, no USB debugging) and ran the setup.
The first conspicuity:
During the progress (sending) it aborts with an ERROR [130] : MODEL-ID-ERROR
I cant explain why, because the set CID is available in the android_info.txt
So I changed the CID to superCID (11111111) as the following:
start cmd as an administrator
adb devices (to check if the phone is connected)
adb reboot-bootloader
fastboot getvar cid (I got HTC__001)
fastboot oem writecid 11111111 (superCID)
fastboot reboot-bootloader
fastboot getvar cid (I got 11111111)
After that the flash progress was successful and I set the CID back to HTC__001
I set up my phone with minimal settings (wifi, google account sync) and checked for new updates (ota).
It looks because I got this:
But after verifying I got this:
I try to fix this with this:
- reboot my phone -> same
- set the CID to HTC__102 (unbranded Germany) -> same
- set the CID to superCID -> I got a small update: Make more space application
- after downloading and installing this small update, there are no more updates available
This is curious too:
I downloaded the app "terminal emulator" and ran the command "getprop ro.cid" to readout the set CID.
With set superCID -> it shows BM___001 (thats the original branded cid)
If I have the CID HTC__001 or HTC__102 it shows the correct cid in the output, but with supercid, it shows the branded cid.
My question now is why the OTA update error message appear?
The output of "fastboot getvar cid) bootloader show the correct CID (HTC__001 or HTC__102) and I used an appropriate RUU where the CIDs are included in android_info.txt
And why cant I flash the RUU with HTC__001 or HTC__102 ?
All I want is to:
- debrand my HTC Sensation (with branding from Bell Mobility) -> done?
- have an unbranded cid (HTC__001 or HTC__102) -> done?
- have an unbranded RUU -> done
- get OTA updates and install them successfully -> fail
I would be very happy if someone can help me (quick)
Kind regards
@@RON
EDIT: Do I have to change the MID? -> "fastboot getvar mid" shows "PG5811000"
The android_info.txt contains this:
Code:
modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__032
cidnum: HTC__102
cidnum: HTC__Y13
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__N34
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__016
mainver: 1.50.401.1
hbootpreupdate:12
DelCache:1
So its different ... I think, this is the key reason.
In my optinion, it works with superCID, because a set superCID ignores the MID and CID. So die flash progress of the RUU works, but the update will fail, because the MID is different
My idea would be to edit the MID of my HTC Sensation or is this a bad idea?
Short summary for MID:
modelname=z710e -> MID=PG8513000 -> HTC Sensation (Europe)
modelname=z710a -> MID=PG8511000 -> HTC Sensation (4G) (America/Australia)
modelname=z711e -> MID=PG8511001 -> HTC Sensation XE (Europe)
Yesterday I edited my question a lot, so maybe its a bit confising
I have an HTC Sensation 4G (z710a) with branding and would like to put an unbranded RUU (unbranded Europe) on it.
I changed the CID from BM___001 to HTC__001, but its obviously not enough, because my model id (MID) is different to the ROM.
MID=PG8513000 -> HTC Sensation (Europe) -> listed in android_info.txt
MID=PG8511000 -> HTC Sensation (4G) (America/Australia) -> my MID, not listed in android_info.txt
My current question is, if there would be a problem, if I change the MID of my phone?
(I would use the command "fastboot oem writemid PG8513000")
I guess that if:
- I change the MID in android_info.txt in RUU, I could flash the RUU without superCID -> but cant install OTA updates, because MID is different to OTA
or:
- I change the MID on my phone, I could flash the RUU without superCID, too -> get and install OTA updates, because CID and MID are matching with the update (the way I prefer)
Am I correct?
Well guys, changing the MID requires the ENG HBOOT.
I found it here:
http://forum.xda-developers.com/showthread.php?p=32448846
After flashing ENG HBOOT, I was able to run this command:
fastboot oem writemid PG8513000
So I changed my MID and now I have an European HTC Sensation z710e instead of z710a (for America/Australia)
After that I was able to flash the RUU (without superCID, because CID and MID matches):
RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035 .00U_10.14.9035.01_M_release_223042_signed.exe
For testing I flashed an older version of Gingerbread to verify the OTA update ability and it works fine :victory:
As a result I converted my z710a to z710e to use an unbranded HTC stock RUU including OTA updates
Looking for ENG HBOOT ??? -> look at this attachment
@@RON said:
Well guys, changing the MID requires the ENG HBOOT.
I found it here:
http://forum.xda-developers.com/showthread.php?p=32448846
After flashing ENG HBOOT, I was able to run this command:
fastboot oem writemid PG8513000
So I changed my MID and now I have an European HTC Sensation z710e instead of z710a (for America/Australia)
After that I was able to flash the RUU (without superCID, because CID and MID matches):
RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035 .00U_10.14.9035.01_M_release_223042_signed.exe
For testing I flashed an older version of Gingerbread to verify the OTA update ability and it works fine :victory:
As a result I converted my z710a to z710e to use an unbranded HTC stock RUU including OTA updates
Click to expand...
Click to collapse
Thanks a lot @@RON.. Your splendid idea inspired me to do the same with my Asian HTC Amaze. I changed the mid to that of tmobile amaze and was able to successfully overcome the 'variant system' notification and update the firmware.