Related
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Hi,
This is a SENSATION forum.
malybru said:
Hi,
This is a SENSATION forum.
Click to expand...
Click to collapse
Yes I noticed it i already asked the moderation if they could move the thread to the Desire S section.
I need to find this out to? I dont want to root my Desire S, I just want to changde CID so i could put unbranded software to it...?
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
doghous said:
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
Click to expand...
Click to collapse
Yes I know that works I have a Goldcard. The thing here is that I would like the phone to be completely unbranded without the need os special cards so in case i want to sell it or send it to warranty it won't be noticed that i changed something there. So if there is a way to re write de CID it would be good.
Well i actually successfully installed the unbranded european ROM 1.28.401.1 using the gold card. But now i can't receive OTA updates. Is there a way to get it to work?
Why don't you run the European RUU 2.10 version (RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed) from the following link:
http://forum.xda-developers.com/showthread.php?t=1002506
That's what I did
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Skanob said:
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Click to expand...
Click to collapse
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
smash_07 said:
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
Click to expand...
Click to collapse
The goldcard does not alter the CID. It just tells the bootloader to ignore the CID check when running a RUU.
One way to alter the CID is to XTC clip the phone.
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
smash_07 said:
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
Click to expand...
Click to collapse
My reply to this post of yours is already a hint.
Use search PLEASE.
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
chuaniyang said:
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
Click to expand...
Click to collapse
Well it's still gonna show relocked if that's what your talking about bcuz you unlocked it then relocked so it isn't gonna show tampered with unlocked at the bottom that's only for the first time you unlock it that it says tampered with unlocked at the bottom, but if you unlock it again it's just gonna say relocked not unlocked. Hopefully this answers your question.
Sent from my samsung galaxy player
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
chuaniyang said:
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
Click to expand...
Click to collapse
Yea that is strange but I don't think it would be considered a problem unless you have the phone stuck in Bootloop or something strange is going on with the phone like apps.not working or battery draining fast. I can see what your worried about and it is strange but I wouldn't worry too much about it but you should look up somewhere in the forums about that but I wouldn't know much about the international version I'm on the US version. Good luck with your problem
Sent from my samsung galaxy player
I checked this thread
http://forum.xda-developers.com/showthread.php?t=1671643
seems I need to wait someone can S-OFF this device
superCID can install any RUU, but can't unlock, root, install custom ROM without S-OFF
I've managed to change my cid and install a new Rom then unlock it and root so it's possible
Sent from my HTC One S using Tapatalk 2
the other reason maybe user just can unlock/relock limited times. ?
does any one change CID and unlock/relock over 3 times ?
I've relocked about 4 time's now changed cid once
Sent from my HTC One S using Tapatalk 2
My default cid is HTC_203, i changed to HTC__102, HTC__001 and 11111111.
Everytime cid changed, I will lock/unlock again. When changed to 11111111, I can't unlock anymore.
Sent from my HTC VLE_U using xda app-developers app
Mate, the CID is in the partition that gets summarized together with the other partitions when calculating the Unlock Token.
So, if you change this or any other relevant partition by for example changing the CID, you will invalidate your old unlock token.
After changing CID, please re-lock bootloader, then go "fastboot oem get_identifier_token" and go to HTC-Dev and unlock again.
After that, you can proceed with everything else as usual.
If you cannot unlock with CID 11111111 this is NOT normal. Everyone else can.
So either you did something wrong in the above process or you somehow half-bricked your phone.
Yes, everytime I changed cid, I got a new unlock code. if not, fastboot will give me error message during unlock process.
I think my situation is not normal, and I'm trying to find out why then fix it. Now, I still can install any RUU , if they have the same HBOOT version.
Sent from my HTC VLE_U using xda app-developers app
I'd guess it's a half brick because if you can't unlock something is wrong. There is no unlock counter because no-one has had it yet. I've unlocked about four or five times now too and don't have that problem. You should consider sending it in for repair. As long as there's no S-OFF you'll have no chance to force an unlock I guess. If the security is as complex as on the HOX, it's likely the situation couldn't even be resolved by a jtag programmer or such.
sent from the tip of my finger
Thanks, no one have the same question as me. I will try to call HTC service.
CID 11111111 Issue
Hello there,
I want to install an older RUU (actually installed is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed )
my intention is to downgrade the Basbeand Version with this Procedure to get rid of this "HomeButton-Jumparound-Whatever" Issue which occures when i am in GSM (2G) Mode.
when i get this phone brandnew there was no Problem, just after updating to 1.78 this ****** began.
When i changed my CID from HTC__102 to 11111111 the first time everything went fine and i was able to install every RUU
Now i tried to change my Radio to an older Version by install an older RUU, but it won't work no more, i allways get an Error 140 or 131.
if there is another method to change the radio version, I'd appreciate any council
relock Bootloader, turn off virus scanners, run ruu as admistrator, I've done of course
I would be grateful for any help
ERROR 140 : bootloader error
ERROR 131 : cid error
are you install T-MOBILE 1.84 RUU ?
this will chane HBOOT version from 1.08 to 1.09
if you can unlock, try to find some way change your HBOOT version back to 1.08.
then you can insall RUU_Ville_U_HTC_Europe_1.78.401.2.
RUU_Ville_U_HTC_Europe_1.78.401.2 can be installed only with the other it does not work
i've got HBOOT 1.13.000 (shown in bootloader)
i just want to downgrade the Radio..
edit: when try to install RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed
or
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed
i get Error 155
we have some thing different. but you are lucky then me. I just can install T-MOBILE 1.84 RUU, if I try to install another version. always got HBOOT version error
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-main: 1.84.531.2
(bootloader) commitno-bootloader: e964c535
The HTC srevice center(tw) call back. they say they find some motherboard error on my device.
I don't think change cid and unlock will cause it happen.
Hello everyone. I've been following XDA since I first laid hands on a Nexus One. Thanks to all of you, I've been able to hack, mod, customize, etc. with only a few close calls. My ATT One X has proven to be a little more tricky and unforgiving. Long story short, I'm stuck in fast boot with an incorrectly changed CID (HTC_621) and a relocked bootloader. I was hoping to get another unlock token from HTC but I think they've abandoned the link. My only other hope was to edit the CID of the "android-info" file in the rom.zip of the RUU, but WinRAR says corrupt archive error when I change the text file. WinZIP won't even open the package--says its invalid. Bottom line, I've exhausted all resources as far as recovering from bad flashes and boot loop. My problem is that damn CID. Any bright ideas guys?
Official ROM zips are signed.
The signature makes the zip non standard so some apps wont open them and most everything else will not modify the file.
Even if you could modify you would make the signature invalid so it would not flash unless you had s-off.
By "Abandoned link" do you mean HTC will not send you an unlock token because the CID is invalid?
Have you tried your previous unlock token?
Without getting a valid unlock token I am unsure if what you can do.
Just out of curiosity, what were you trying to do exactly and what CID is that?
he was probably trying to flash the international jelly bean =)
redpoint73 said:
Just out of curiosity, what were you trying to do exactly and what CID is that?
Click to expand...
Click to collapse
It's an Endeavour CID for HTC Asia in Taiwan. And we wonder why HTC locks bootloaders and write-protects system partitions.
To the OP: This would not have worked anyway because you were trying to install software for a completely different phone.
Your original unlock token should still work. Trying unplugging and powering off your phone, rebooting your computer, and try flashing it again.
I thought unlock tokens were locked to the current CID?
If you change CID you need a new unlock token?
That is how my phone worked
twistedddx said:
I thought unlock tokens were locked to the current CID?
If you change CID you need a new unlock token?
That is how my phone worked
Click to expand...
Click to collapse
It's worth a shot. If it doesn't work, I don't see any way out. He can't run the RUU, he can't boot up, and he can't unlock. There might be some low-level fix via Linux. Try the unbricking Evita thread.
I'm sending my phone to T-Mobile and getting a new one via handset warranty. The volume buttons broke off and I can't handle the reboots anymore so T-Mobile said I can get a new one. They told me that I have to return it to completely stock though or else I will be charge $98.
I'm currently running HyperSensation. How do I go about returning it completely to stock so I don't get stuck with this charge?
ImHuge07 said:
I'm sending my phone to T-Mobile and getting a new one via handset warranty. The volume buttons broke off and I can't handle the reboots anymore so T-Mobile said I can get a new one. They told me that I have to return it to completely stock though or else I will be charge $98.
I'm currently running HyperSensation. How do I go about returning it completely to stock so I don't get stuck with this charge?
Click to expand...
Click to collapse
Hi,
Run a RUU.
Look HERE
malybru said:
Hi,
Run a RUU.
Look HERE
Click to expand...
Click to collapse
Thanks!
I did super cid when I rooted. Will I need to change that back to its normal value before sending it in? How do I find which value to change it to?
ImHuge07 said:
Thanks!
I did super cid when I rooted. Will I need to change that back to its normal value before sending it in? How do I find which value to change it to?
Click to expand...
Click to collapse
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
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 of the 11111111. 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.
Yours is likely to be
T_MOB010
malybru said:
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
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 of the 11111111. 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.
Yours is likely to be
T_MOB010
Click to expand...
Click to collapse
Ah thank you. I have no idea if I need to get S-ON or supercid back to normal or not. I have the handset protection plan so they sent me a new one and I'm sending mine in and the rep at the store said make sure there is no trace of rooting or they will charge me $100. I don't know if that just means the RUU or if they will check for S-ON or supercid. Does anyone know?
Another question. If I can't figure out how to get it back to stock then should I just brick it and send it back? Will they be able to tell that it bricked due to rooting?
ImHuge07 said:
Ah thank you. I have no idea if I need to get S-ON or supercid back to normal or not. I have the handset protection plan so they sent me a new one and I'm sending mine in and the rep at the store said make sure there is no trace of rooting or they will charge me $100. I don't know if that just means the RUU or if they will check for S-ON or supercid. Does anyone know?
Click to expand...
Click to collapse
Hi,
What the rep said ,means you have to remove supercid and return to s-on.
This has all been explained in the threads I gave you.
ImHuge07 said:
Another question. If I can't figure out how to get it back to stock then should I just brick it and send it back? Will they be able to tell that it bricked due to rooting?
Click to expand...
Click to collapse
Hi,
If during the process of returning it to stock,the phone gets bricked,then,they could not tell what has happened.
malybru said:
Hi,
What the rep said ,means you have to remove supercid and return to s-on.
This has all been explained in the threads I gave you.
Hi,
If during the process of returning it to stock,the phone gets bricked,then,they could not tell what has happened.
Click to expand...
Click to collapse
Perfect.
Do I have to change the radio at all do you think? Or is it included in the RUU? And what about the kernel? I assume that's in the RUU as well?
malybru said:
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
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 of the 11111111. 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.
Yours is likely to be
T_MOB010
Click to expand...
Click to collapse
Last question, and thank you very much for the help so far.
Right now I have supercid so should I change back to T_MOBO10 first before doing all the steps on the RUU up there or can I do it after?
And also how do I tell if my boot loader is locked or not? Following the instructions on the RUU I'm S-OFF but I'm not sure if the bootloader is locked or not. I don't see unlocked anywhere so should I assume its locked?
ImHuge07 said:
Perfect.
Do I have to change the radio at all do you think? Or is it included in the RUU? And what about the kernel? I assume that's in the RUU as well?
Click to expand...
Click to collapse
Hi,
Radio and kernel are included in the RUU
ImHuge07 said:
Last question, and thank you very much for the help so far.
Right now I have supercid so should I change back to T_MOBO10 first before doing all the steps on the RUU up there or can I do it after?
And also how do I tell if my boot loader is locked or not? Following the instructions on the RUU I'm S-OFF but I'm not sure if the bootloader is locked or not. I don't see unlocked anywhere so should I assume its locked?
Click to expand...
Click to collapse
Hi,
I would change the cid,run the RUU,and then s-on.
Hello I'm about to send my phone for a repairs to HTC. I'm currently rooted, tampered, s-on and with custom CID 111...
Any suggestions what I need to do? I mean I'll lock the bootloader and install stock RUU but is it enough? Or nothing will help they'll know that it was rooted?
Your bootloader will still show RELOCKED... The only way would be S-OFF.
And don't forget to replace the CID.
nor-ric said:
Your bootloader will still show RELOCKED... The only way would be S-OFF.
And don't forget to replace the CID.
Click to expand...
Click to collapse
So first of all I need to S-OFF and only then replace CID to stock?
Because to S-OFF it says "you must have supercid"
Exactly!
nor-ric said:
And don't forget to replace the CID.
Click to expand...
Click to collapse
But what do I change it to? Because unfortunately I don't remember my original CID
Because it used to say H3G (network code) and now I installed some european RUU
Is (was) your phone branded? Also, which country are you from?
nor-ric said:
Is (was) your phone branded? Also, which country are you from?
Click to expand...
Click to collapse
United Kingdom, if you mean was it bought from network provider then yes it's branded.
P.S. some people told me to do: fastboot oem writecid, is it correct, will it change it?
cikoleko said:
United Kingdom, if you mean was it bought from network provider then yes it's branded.
P.S. some people told me to do: fastboot oem writecid, is it correct, will it change it?
Click to expand...
Click to collapse
Yes, it's correct. I suggest that you use Hasoon's All In One Toolkit, though: it helps a lot automating things (avoiding command line) if you are not very familiar with these things. You can find it in the development subforum.
The point is writing the correct CID. Do you remember if your software was customized by your carrier (e.g. with carrier-related apps)? Do you have your carrier name physically printed on the phone? Not all phones sold by carriers are branded: for example, I bought it from H3G but it's unbranded.
If this wasn't the case, I would go with the generic UK CID (if exists), or with the international CID (that is HTC__001).
nor-ric said:
Yes, it's correct. I suggest that you use Hasoon's All In One Toolkit, though: it helps a lot automating things (avoiding command line) if you are not very familiar with these things. You can find it in the development subforum.
The point is writing the correct CID. Do you remember if your software was customized by your carrier (e.g. with carrier-related apps)? Do you have your carrier name physically printed on the phone? Not all phones sold by carriers are branded: for example, I bought it from H3G but it's unbranded.
If this wasn't the case, I would go with the generic UK CID (if exists), or with the international CID (that is HTC__001).
Click to expand...
Click to collapse
Phone is on contract and yes it had carrier apps but on the phone there is no signatures it just looks standard. But now I installed htcs european ruu so probably it doesn't matter.
So I've changed it to HTC__001.
P.S. my bootloader says: unlocked, do I need to lock it or it doesn't matter for a warranty?
I agree, about the cid matter.
About the bootloader, that's the most important part: you need to make it say "LOCKED", otherwise.they will probably deny your warranty. The issue is, if you now lock the bootloader it will say RELOCKED, so they'll know that you've actually unlocked. You need to s-off and then get back the LOCKED label. There's a walkthrough about it, you will easily find it.
Yes thanks for the help I found out how to change it
cikoleko said:
Yes thanks for the help I found out how to change it
Click to expand...
Click to collapse
If you now go back to s-on (it shouldn't be necessary for warranty but who knows...) be sure to use a ruu first.
And whenever you need to thank someone's posts, use the thanks button!