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.

[SOLVED] Please help *Security Warning* in Hboot

Hi please could somebody help me, I have a Desire S which I got on contract from 02 with a 02 branded rom on there originally and hboot 0.98.0002.
I had S-off, 4ext recovery, upgraded to hboot 2.00.0002 and a custom rom installed.
I have flashed a offical RUU RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe
and now I am stuck in hboot and it says **security warning** hboot version 0.98.000
I tried to flash the above o2 RUU again but it says bootloader version error, So I tried RUU 1.28, 1.47 and 2.10 with a gold card in the phone but the same error all the time.
I have also extracted the rom.zip from each of these and put it onto the goldcard renamed to PG88IMG.zip but then this says MAIN VERSION OLDER and will not flash.
Now I am really stuck on what I need to do, do I need to flash a 0.98.0002 hboot? as at the momment I have 0.98.000, if so how can I do this?
I have lost 4ext recovery, and back to S-On.
If anyone has any ideas I would be really grateful.
Thank you in advance
Cheers
edit: I think the bootloader I currently have on the phone 0.98.000 is incorrect ? , it should be 0.98.0000 or 0.98.0002? . As the hboot is S-ON is there anyway I can flash a hboot through using adb, or does it have to be S-OFF, if so is there anyway I can S-OFF in bootloader or fastboot alone, as I can't do anything else.

I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.

amidabuddha said:
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
Click to expand...
Click to collapse
Hi thanks for your reply, I currently have 0.98.000 hboot on the phone now which is S-ON. My gold card seems to be working as it doesn't say any CID errors.
How can I tell if my device is bricked?
I can only get into hboot, and fastboot/stock recovery. The phone won't do anything else and I can't flash any rom as it says about the bootloader version, but on the bootloader it says **security warning** at the top. Is there anyway I can flash a newer hboot? or won't it let me as it is S-ON, if its S-ON will I be able to flash a hboot or even 4ext recovery to flash a rom?
If so how can I s-off just using bootloader and fastboot?
I thought goldcard is only to bypass the CID checks so you can flash a debranded RUU.

It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.

amidabuddha said:
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
Click to expand...
Click to collapse
Hi, I have done the fastboot commands you said and below are the numbers I got:
fastboot devices - serial number which came up is: HT15NTJ00403
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Thank you for your help with this

Try to put last rom.zip on sdcard with PG88IMG.zip name from version 2.10.401.8 RUU and maybe you will have new hboot 2.00.2002 and then have to unlock hboot from http://htcdev.com/.

first_damned said:
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Click to expand...
Click to collapse
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.

amidabuddha said:
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
Click to expand...
Click to collapse
Hi, I have tried RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe using the RUU on the laptop and tried extracting the rom.zip, renaming as PG88IMG.zip and flashing off sd card (goldcard), but the RUU said bootloader version error and flashing the PG88IMG.zip says main version older error.
There isn't a 2.10.401.4 version, but there is a
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed.exe
I would of thought the 2.10.401.8 should of worked?
also would I be able to flash a hboot being S-ON do you think?
I'm not sure how low my battery is also, If I plug it into the charger will it charge the phone on the bootloader do you know?
Thanks

All version info
INFOversion: 0.5
INFOversion-bootloader: 0.98.0000
INFOversion-baseband: 38.03.02.14_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 11.10.401.4
INFOserialno: HT15NTJ00403
INFOimei: 356708041449842
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: O2___001
INFObattery-status: good
INFObattery-voltage: 3851mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!

Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.

amidabuddha said:
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
Click to expand...
Click to collapse
Hi there, I have tried adb devices but it doesn't come up with my device which is strange. Maybe because my device is S-ON?
Do you think if I took it to a mobile repair shop and had it jtagged to restore original software would do the trick?
thanks

Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.

amidabuddha said:
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
Click to expand...
Click to collapse
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?

first_damned said:
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
Click to expand...
Click to collapse
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.

amidabuddha said:
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
Click to expand...
Click to collapse
I can't get adb to see the device, fastboot will do though but won't flash hboot, it says remote signature fail.
Looks like im going to have to send the phone off to be J Tagged. I have found a shop that does this for £24.99 and they know there stuff.
But if anyone has anymore ideas please let me know.
Thank you amidabuddha for your help, I will keep you updated on any progress.
Simon

You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium

poppy8x said:
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
Click to expand...
Click to collapse
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?

first_damned said:
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
Click to expand...
Click to collapse
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium

poppy8x said:
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?

first_damned said:
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
Click to expand...
Click to collapse
Yeah. All worked. Look at my sig.
A month ago, i had "sercurity warning" too (i run RUU 1.48). Gold card coudn't do anything. And then i s-off by xtc-clip (in 5 mins)
Sry for my english bad.
Sent from my HTC Desire S using xda premium

[Q] Variant System version - Unable to Update *solved*

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.

[S-ON after XTC Clip] + Super CID ( GSM+AMOLED ONLY )

This Guide will help you revert back to S-ON if you S-OFF with XTC Clip.
Confirmed working with and without SuperCID, With and without sim unlocked and i can confirm this method will work on ALL HTC devices supported with the old MTD.
This Guide runs the risk of bricking your device, Therefor i take no responsibility for your actions
Change CID on second post. im just ironing out some things then ill update the guide. Thanks.
S-ON :
1. Download RUU from here = DOWNLOAD
2. Run the RUU and get back to stock Rom ( make sure to enable usb debugging ( settings/applications/development )
3. Download SuperOneClick from here = SuperOneClick
4. Run it and select ZergRush then click root
5. Once rooted open up a CMD and CD into your adb folder
6. Once you are in your adb folder type adb devices and press enter
7. Now type adb shell and press enter ( you should now get a # sign in the terminal continue to step 8 )
8. Now type echo -e '[email protected]=7,1\r' > /dev/smd0 Your CMD window should now be back at the #
9. Your device is now S-ON with root to confirm reboot into bootloader and see it states S-ON
10. ENJOY !!!
If you don't currently have any ADB folder there is 1 attached below.
ADB FOLDER ( WITH HTC DRIVERS )
If this Guide helped you please dont forget to hit the thanks button. This was tested on GSM HTC Desire ONLY. i had stock CID HTC__001. I will try with super cid 2morrow and post a video. Thanks​

Change CID From super CID back to a CID of your Choice
Welcome to my CID Guide.
This is NOT for SLCD DEVICES !!!!!
This guide will help you change your Super CID ( 11111111 ) back to its original eg: HTC__001.
Please use this guide ONLY if you understand what your doing. I take no responsibility for broken devices.
ENG Hboot can be flashed over by ANY Hboot Nexus One or Bravo. All Hboots have been repartitioned and are exact same sizes as Alpharev Hboots. This is because everyone is already used to these sizes but if you wish for a custom size please PM me and ill re partition for you and email you the Hboot. These Hboots have extended fastboot commands for changing CID and Backup CID
Now lets get to is shall we
1. Download The ENG Hboot located at the attachments section ( bottom of this post )
2. Flash the ENG Hboot with fastboot flash hboot ENG_Hboot_7.01.1111_Desire.img
3. Reboot your HTC Desire into Bootloader mode fastboot reboot-bootloader
4. now whilst still in Fastboot open up a CMD ( windows only ) and CD to your fastboot folder and type fastboot devices.
5. If your device was located now type fastboot oem changeCid xxxxxx ( replace xxxxxx with whatever your CID is find a list below )
5a. Please make sure when running the fastboot oem changeCid command you let it Finish DO NOT UNPLUG UNTILL IT HAS FINISHED.
6. Now on your device reboot back into bootloader and type fastboot getvar all and look for your new CID number
7. Now that you have changed your CID you can either stay on this Hboot or flash back to Desire Hboot.
If you wish to change your backup CID ( Somtimes this can be empty ( if backup was not created )
Run this in fastboot fastboot oem writebcid HTC__001 ( or whatever you want it to be ) [ Replace HTC__001 with your CID ]
Stock CID Numbers below:
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: 11111111
These are the CID numbers i know. I know there is hundreds more and as i find out more and more ill add to the pile. Thanks
or you can use this XTC Clip firmware to gain super CID PB99diag.nbh can be downloaded below. Please get a EMPTY sdcard ( format it 1st ) place the PB99diag.nbh file on the root of the sdcard and reboot into bootloader and follow instructions to clean s58 data
Thanks for using my guide, All stuff used can be downloaded from the attachments below. including stock alpharev hboot.​

Re: [S-ON after XTC Clip] ( Tutorial ) Only GSM
So this ia basically getting s-on with the 2.3 RUU.

DigginGraves said:
So this ia basically getting s-on with the 2.3 RUU.
Click to expand...
Click to collapse
yes. but you can use ANY RUU you want. but MAKE SURE you run the RUU before you do this guide.

I posted this S-On long time ago. So it still working for everyone then?
But you've made a nice guide out of it.
How ever it only works for Wildfire, the other HTC's use a totally different MTD.

Super CID guide is now up on 2nd Post thanks
Guide is now up on 2nd Post thanks for all your support in the other thread

No problem.

[Q] unable to change cid on htc sensation xl

I have an HTC Sensation XL. I have unlocked the bootloader and s-off.
My current cid is HTC_038. I am unable to get a ruu reddymede rom for it.
I downloaded RUU_Runnymede_hTC_Asia_India_1.24.720.2_R_Radio_20.5102.30.0822_3822.11.10.30_M_release_232317_signed but the setup seems to have a problem. I cudnt find another version of RUU_Runnymede_hTC_Asia_India and therefore i decided to change my cid.
I used the commands 'fastboot oem writecid 11111111'
it showed me the following error
'... INFO[ERR] Command error !!!'
i am using a custom rom. i really want to install the RUU stock rom. Please help me.
The following details are displayed when i connect my phone in fastboot
RUNNYMEDE PVT SHIP S-OFF
HBOOT-6.25.4445
RADIO-3831.16.00.27_M
eMMC-boot