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.
hi all....i recently bought a t mobile htc one s and i am planning on debranding it....i dont live in the US and i dont need any of t mobiles services....my plan is to debrand it and get stock htc rom on it...i dont plan on using the phone rooted, so i want to be able to get OTA updates and everything, basically i want it to be like stock european htc one s....i google and found this link http://forum.xda-developers.com/showthread.php?t=1674202
after i rooted my phone i followed the steps in the link and was able to change my cid to HTC__001 from T-MOB010. i downloaded the european 2.31 RUU from http://www.filecrop.com/Ruu-HTC-One-S.html and when i ran it i got error code 130....my model id (PJ4011000) is different from the one the RUU is meant for (PJ4010000). so i was unable to debrand. i googled on how to change the modelid and read somehwere that i had to modify my build.prop file....followed the steps in this link http://forum.xda-developers.com/showthread.php?t=1236732 and changed the model id to PJ4010000 from PJ4011000 wherever it appeared in the build.prop file and pushed it back onto the phone, but still the ruu is giving the same error code 130.
i couldnt find any more links to help so i am posting it here. anyone have any ideas ? thanks
p.s i installed the stock recovery and the stock boot using fastboot and relocked the boot loader before trying to install using ruu. and the 2.31 ruu is compatible with HTC__001
anand_s said:
hi all....i recently bought a t mobile htc one s and i am planning on debranding it....i dont live in the US and i dont need any of t mobiles services....my plan is to debrand it and get stock htc rom on it...i dont plan on using the phone rooted, so i want to be able to get OTA updates and everything, basically i want it to be like stock european htc one s....i google and found this link http://forum.xda-developers.com/showthread.php?t=1674202
after i rooted my phone i followed the steps in the link and was able to change my cid to HTC__001 from T-MOB010. i downloaded the european 2.31 RUU from http://www.filecrop.com/Ruu-HTC-One-S.html and when i ran it i got error code 130....my model id (PJ4011000) is different from the one the RUU is meant for (PJ4010000). so i was unable to debrand. i googled on how to change the modelid and read somehwere that i had to modify my build.prop file....followed the steps in this link http://forum.xda-developers.com/showthread.php?t=1236732 and changed the model id to PJ4010000 from PJ4011000 wherever it appeared in the build.prop file and pushed it back onto the phone, but still the ruu is giving the same error code 130.
i couldnt find any more links to help so i am posting it here. anyone have any ideas ? thanks
p.s i installed the stock recovery and the stock boot using fastboot and relocked the boot loader before trying to install using ruu. and the 2.31 ruu is compatible with HTC__001
Click to expand...
Click to collapse
Try it without installing the recovery and boot before the RUU. There is no need to do that. Just relock and run the RUU, it will restore the boot and recovery for you.
Sent from my HTC One S using xda app-developers app
Lemme know how it goes. Might do this as well
Sent from my HTC VLE_U using xda app-developers app
Same here. I am trying to debrand the T-Mobile US as well. Thanks.
Sent from my HTC VLE_U using xda app-developers app
troby86 said:
Try it without installing the recovery and boot before the RUU. There is no need to do that. Just relock and run the RUU, it will restore the boot and recovery for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
hmmm......i thought the model id is stored in the build.prop file, dont know how this can fix that....i heard the ruu checks for cid and the modelid...i am passing the cid check, its the model id where i get stuck....anyways will try it out and let you guys know....its my only phone currently so might be a few days
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Is debranding needed in order to flash custom ROM ?
No. You just need to root the phone to install custom rom.
Sent from my HTC VLE_U using xda app-developers app
Confused
roadhero said:
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Click to expand...
Click to collapse
I am a bit confused with the above update and the thread here . The OP in the thread claims that he was able to de-brand his TMOUS HOS without SuperCID of 11111111.
Can somebody please clear the confusion?
Also, after de-branding, does the WiFi work on HOS which was previously TMOUS branded?
roadhero said:
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Click to expand...
Click to collapse
hmmm....i wasnt able to flash the european RUU...as mentioned it gave me an error (code 130, model id not matching or something)....so forget OTA updates, even flashing the RUU was impossible with my current model id....i did consider going the super cid route but i heard that the jelly bean OTA update bricks phones with super cid...thats why i wanna get a more 'legitimate' cid like HTC__001....
chota_shivaji said:
I am a bit confused with the above update and the thread here . The OP in the thread claims that he was able to de-brand his TMOUS HOS without SuperCID of 11111111.
Can somebody please clear the confusion?
Also, after de-branding, does the WiFi work on HOS which was previously TMOUS branded?
Click to expand...
Click to collapse
yeah the OP in that thread was able to debrand....and i think he used the HTC__001 cid ...dont know what the model number of his phone is....i think it might be matching with the one in the european RUU (PJ4010000)....does anyone know of any unbranded RUU that supports the model id PJ4011000 ??
I was able to flash my htc one s T-Mobile us with RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655 using superCID 11111111 it work perfectly however it is impossible to install the OTA update JB_45_S_HTC_Europe_3.16.401.8.
yw2012 said:
No. You just need to root the phone to install custom rom.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
yw2012 thanks for your answer.
I suppose that no problem exists with this phone, a custom ROM could be flashed :
HTC One S
T-MOB101
HBOOT-1.14.0002
RADIO-1.09es.50.02.07_2
Android version : 4.0.4
HTC Sense version : 4.1
Software number : 2.38.111.10
Baseband version : 1.09es.50.02.07_2_10.09d.50.04L
Build number : 2.38.111.10 CL97613 release-keys
Bootloader unlocked
Rooted with SuperSU
ROM Stock
Well, I'd like to confirm that there's no way to flash a European RUU on USA T-Mobile device unless you Super-CID. There are also European T-Mobile branded phones, e.g. T-Mobile Germany. Those ones can be debranded using generic HTC__001 CID.
Small statistic report from fellow community (Not my own work):
1. HTC One S (Z520e) 1&1 Germany : CID: HTC__102 GER -> CID changed to 11111111 Super CID -> OTA --> OK!
2. HTC One S (Z520e) T-Mobile Germany : CID: T-MOB101 - TMD -> CID changed to HTC__102 GER -> OTA --> OK!
Few things you need to obey strictly when OTA to be safe, based on current brick reports:
1. Locked/relocked bootloader
2. Everything stock, no root, no custom recovery:
Code:
Radio: 1.06es.50.02.31_10.09a.50.04L
HBOOT: 1.14.0002
Recovery: Stock
ROM: Stock 2.31.401.5
3. CIDs:
Code:
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
4. FULLY CHARGED, CHARGING/SYNC CABLE DETACHED, leave the phone alone and let it apply the OTA update
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
roadhero said:
Well, I'd like to confirm that there's no way to flash a European RUU on USA T-Mobile device unless you Super-CID. There are also European T-Mobile branded phones, e.g. T-Mobile Germany. Those ones can be debranded using generic HTC__001 CID.
Small statistic report from fellow community (Not my own work):
1. HTC One S (Z520e) 1&1 Germany : CID: HTC__102 GER -> CID changed to 11111111 Super CID -> OTA --> OK!
2. HTC One S (Z520e) T-Mobile Germany : CID: T-MOB101 - TMD -> CID changed to HTC__102 GER -> OTA --> OK!
Few things you need to obey strictly when OTA to be safe, based on current brick reports:
1. Locked/relocked bootloader
2. Everything stock, no root, no custom recovery:
Code:
Radio: 1.06es.50.02.31_10.09a.50.04L
HBOOT: 1.14.0002
Recovery: Stock
ROM: Stock 2.31.401.5
3. CIDs:
Code:
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
4. FULLY CHARGED, CHARGING/SYNC CABLE DETACHED, leave the phone alone and let it apply the OTA update
Click to expand...
Click to collapse
Thanks a lot for the vital info. i never tried flashing the RUU using super cid. i will try.
some more things of concern. lets say i change my cid to super cid (11111111) and am able to flash the 2.31 european RUU
1) does wifi/cellular radio of the t mobile US one s work with the european RUU?
2) and lets say i follow all the steps you recommended before an OTA update, the jelly bean OTA update wont brick my phone? is this right ? is there anyone who has successfully updated to jelly bean while on super cid ?
yw2012 said:
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
sorry, i dont seem to get what you said. changing the cid will let you flash a different RUU but as people mentioned in this thread, you cant install an european RUU with generic cid like HTC__001 on a Tmobile US phone (cause of differing model id i presume). you can however install using super cid (i havent verified this myself and ofcourse i claim no responsibility ). but i dont know whether you can successfully update using OTA while on supercid
anand_s said:
Thanks a lot for the vital info. i never tried flashing the RUU using super cid. i will try.
some more things of concern. lets say i change my cid to super cid (11111111) and am able to flash the 2.31 european RUU
1) does wifi/cellular radio of the t mobile US one s work with the european RUU?
2) and lets say i follow all the steps you recommended before an OTA update, the jelly bean OTA update wont brick my phone? is this right ? is there anyone who has successfully updated to jelly bean while on super cid ?
sorry, i dont seem to get what you said. changing the cid will let you flash a different RUU but as people mentioned in this thread, you cant install an european RUU with generic cid like HTC__001 on a Tmobile US phone (cause of differing model id i presume). you can however install using super cid (i havent verified this myself and ofcourse i claim no responsibility ). but i dont know whether you can successfully update using OTA while on supercid
Click to expand...
Click to collapse
- I got the rom.zip from the RUU.exe.
- This .zip has a file called android-info.txt which mentions the "modelid: PJ4011000".
- I wonder if somehow you are able to edit this .zip and change modelid to match the current in phone, you might be able to do OTA update on HTC__001 unbranded phone from TMOUS.
As usual this is just a speculation with no real data to back it up. So use it on your own risk. I am not responsible to any damage this does to your phone :fingers-crossed:
yw2012 said:
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
No, you won't even be able to run a European RUU in this case.
anand_s,
to answer your questions,
1) wifi/cellular radio works like a charm with the european RUU.
2) you will receive a request to receive a European JB OTA, it will even download but it will give you a message that you have different software on the phone and it won't install, so everything's fine with that, you'll just have to run a European JB RUU if it becomes available.
And yes, you are right regarding everything else. There's OTA on SuperCID, but MIDs mismatch and it does not install, it does not break your phone either.
I personally have US T-mobile One S S4, have unlocked bootloader, SuperCID and running a european RUU 2.31.
starting Jan26 unlocking phones will be ilegal in US
for all you people from US, if you want to unlock and debrand your phone I strongly suggest doing it today; tomorrow it will be a crime
http://www.techspot.com/news/51439-...ne-will-become-a-crime-starting-saturday.html
wtf is that? you really have lots of control freak people walking freely on the streets, and even worse, they're writing laws . . .
chota_shivaji said:
- I got the rom.zip from the RUU.exe.
- This .zip has a file called android-info.txt which mentions the "modelid: PJ4011000".
- I wonder if somehow you are able to edit this .zip and change modelid to match the current in phone, you might be able to do OTA update on HTC__001 unbranded phone from TMOUS.
As usual this is just a speculation with no real data to back it up. So use it on your own risk. I am not responsible to any damage this does to your phone :fingers-crossed:
Click to expand...
Click to collapse
This does not work, unfortunately. I tried it (the RUU extracts everything well before actually flashing, so at the last 'Next' dialog, I unzipped rom.zip in the temp folder, changed the MID in android_info.txt from PJ4010000 to PJ4011000, saved, and zipped it again), but no luck. This time, the RUU process fails with Error 132 (Signature error) rather than Error 130 (model ID error).
This is with changing CID from T-MOB010 to HTC__001. I'm now trying 11111111.
Edit: Changing the CID to 11111111 works, so you can flash the European 2.31 RUU for model ID PJ4010000 to the T-Mobile (US) One S with model ID PJ4011000. I didn't dare update to the Jelly Bean OTA (it showed up as available) thanks to this thread.
jenesuispasbavard said:
This does not work, unfortunately. I tried it (the RUU extracts everything well before actually flashing, so at the last 'Next' dialog, I unzipped rom.zip in the temp folder, changed the MID in android_info.txt from PJ4010000 to PJ4011000, saved, and zipped it again), but no luck. This time, the RUU process fails with Error 132 (Signature error) rather than Error 130 (model ID error).
This is with changing CID from T-MOB010 to HTC__001. I'm now trying 11111111.
Edit: Changing the CID to 11111111 works, so you can flash the European 2.31 RUU for model ID PJ4010000 to the T-Mobile (US) One S with model ID PJ4011000. I didn't dare update to the Jelly Bean OTA (it showed up as available) thanks to this thread.
Click to expand...
Click to collapse
- First of all thanks for all the updates. Moreover thanks for the brick-after-jb-update-on-super-cid thread.
- I wonder does it makes sense to de-brand TMOUS to European version at this point of time, if we are not able to do JB update.
- I think this should be attempted when the RUU for European JB is available. Not sure thought if that will help.
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.
Hello,
I wanted to restore my Desire S (remove S-OFF, root and set up a stock rom).
So first I updated the HBOOT-Version to 2.00.0002. After flashing the HBOOT the information in Bootloader were changed to
###LOCKED###
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
In the second step I tried to install the stock RUU. For the installation I used "RUU_Saga_S_HTC_Europe_2.10.401.9".
But the installation failed with an error message, that the CID is wrong. I completely forgot, that the CID is VODAP102.
So then I tried to install the RUU "RUU_Saga_Vodafone_UK_1.32.161.1" but this failed, too.
I get the error message, that the current main-version on the Desire S is higher then the main-version of the ROM.
When I start my Desire it stuck on the HTC-Logo. I always tried to extract the rom.zip from the RUUs, rename it to PG88IMG.zip and install it from the Bootloader.
But after it checked the ROM I got the same errors (CID and main-version).
The next idea was to downgrade the HBOOT, so I reboot to bootloader.
In the bootloader I noticed, that I dont't get an ADB-connection. The command "adb devices" doesn't show my device. I have only a fastboot-connection.
The command "fastboot getvar all" show the following output:
version: 0.5
version-bootloader: 2.00.0002
version-baseband: 3822.10.08.04_M
version-cpld: None
version-microp: None
version-main: 2.10.401.9
serialno: ############
imei: ############
product: saga
platform: HBOOT-7230
modelid: PG8810000
cidnum: VODAP102
battery-status: good
battery-voltage: 4199mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ebd3df7d
hbootpreupdate: 12
gencheckpt: 0
Can someone help me, please?
I have no idea anymore how I can fix this.
(Sorry for my english)
It's simple, you need to find the correct RUU (both version-number-wise and CID-wise) and run that
Aquous said:
It's simple, you need to find the correct RUU (both version-number-wise and CID-wise) and run that
Click to expand...
Click to collapse
Yeah , but that problem is, that I only found the RUU_Saga_Vodafone_UK_1.32.161.1. I don't find a newer version.
Can someone help me, please?
I don't find a newer RUU and don't know what I can do else. I have no ideas more.
You can always use the ICS RUU, but keep in mind that ICS has bugs and that you will void your warranty.
You could also use a RUU with a different CID and use a goldcard.
When I use the ICS RUU, can I downgrade without HTC-Dev to a lower HBOOT-Version after the installation?
Depends the creation of a goldcard on the sd-card or the device? I tried to create a goldcard on another device, but the RUU-installation failed anyway.
Al-Caone said:
When I use the ICS RUU, can I downgrade without HTC-Dev to a lower HBOOT-Version after the installation?
Depends the creation of a goldcard on the sd-card or the device? I tried to create a goldcard on another device, but the RUU-installation failed anyway.
Click to expand...
Click to collapse
With the goldcard use the 2.10.401.9 RUU again. If the goldcard is correctly made you should have successful flash this time.
You can use it like this or use Zergrush or other temproot in order to lower the version and then flash the Vodaphone RUU to return to Stock if you need that specific version for some reason
Sent from my HTC Desire S
I made a goldcard, but the installation of the RUU failed anyway. I put my SD-Card in an other Desire S and tried to create a Goldcard. According the tool goldcard was made successfully. But when I try to install the RUU, I get a CID-error.
Does the creation of the goldcard depends on sd-card or device?
Al-Caone said:
Does the creation of the goldcard depends on sd-card or device?
Click to expand...
Click to collapse
There was a discussion here and I think it can depend on both.
Speaking from my experience when I bricked my DS I created the goldcard on my PC so it was not related to any device data.
Try to extract the Rom.zip from the .09 RUU, copy to the SD card and reboot to bootloader as you did before but with the goldcard this time
Sent from my HTC Desire S
Al-Caone said:
I wanted to restore my Desire S (remove S-OFF, root and set up a stock rom).
So first I updated the HBOOT-Version to 2.00.0002.
Click to expand...
Click to collapse
If this means you still have a custom recovery, that custom recovery should still have root and therefore you'll be able to misc_version from it, even if normal android is unbootable due to partition table changes from changing hboot versions.