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.
Is it possible to check was it brended before I did root,Super CID and debrending procedure and which operator / theritory
Imperatorpg said:
Is it possible to check was it brended before I did root,Super CID and debrending procedure and which operator / theritory
Click to expand...
Click to collapse
Sorry, not certain what you're asking here.
Is the phone currently Stock ?
Or has it been S-OFF'd, rooted, etc. and you want to get it back to have the Stock operator ROM ?
If you download "CID getter" from the market you can check a few things out. Mine for example through the app is:
Note: mine is S-OFF, FW 1.27.1100, SuperCID
[ro.aa.maincid]: [HTC__001]
[ro.carrier]: [VODA-UK]
[ro.cid]: [VODAP01] ------------------Original CID (not certain why it gives a different result to "adb getvar CID" which is "11111111").
If you run this app does it give the info you need ? Or are you after something else ?
gol_n_dal said:
Sorry, not certain what you're asking here.
Is the phone currently Stock ?
Or has it been S-OFF'd, rooted, etc. and you want to get it back to have the Stock operator ROM ?
If you download "CID getter" from the market you can check a few things out. Mine for example through the app is:
Note: mine is S-OFF, FW 1.27.1100, SuperCID
[ro.aa.maincid]: [HTC__001]
[ro.carrier]: [VODA-UK]
[ro.cid]: [VODAP01] ------------------Original CID (not certain why it gives a different result to "adb getvar CID" which is "11111111").
If you run this app does it give the info you need ? Or are you after something else ?
Click to expand...
Click to collapse
I rooted my phone and made Super CID, I downloaded CID getter and result is HTC_032. I think for East Europe. So, what I must do to make it totaly stock because I want to return it on waranty. Thanks.
You need to find out what software version was originally on the phone. This is why it's important to make a note of it before you go flashing new ROMs as if there's no RUU you're screwed
I made backup before I rooted phone. So I restore it and install Hboot 1.17 but I know that was 1.18 before. Fw is 1.50.401.1, Android 2.3.4, HTC Sense 3.0, kernel 2.6.35.13., radio 10.56.9035.00U_10.14.9035.01_M
Imperatorpg said:
I rooted my phone and made Super CID, I downloaded CID getter and result is HTC_032. I think for East Europe. So, what I must do to make it totaly stock because I want to return it on waranty. Thanks.
Click to expand...
Click to collapse
So is there still a problem if you restored your backup ?
If you scroll down the list what does it say for the examples I gave below?
[ro.aa.maincid]: [????????]
[ro.carrier]: [????????]
[ro.cid]: [????????]
gol_n_dal said:
[ro.aa.maincid]: [????????] ? - cant find
[ro.carrier]: [HTC-East Europe]
[ro.cid]: [HTC_032]
Click to expand...
Click to collapse
I did it today and testing if problem is gone.
still have problem with droping calls
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.
I am sorry, because this have probably been asked many times, but I have a little more specific question. I have HTC Sensation rooted, and S-OFF. Now I want to send it to the service under warranty, because I noticed there is a dust under my screen.
I know what I have to do, but I dont know which default rom should I choose, so they definitely would not suspect anything. Does it have to be carrier specific or just some random EU rom? I am from Slovenia, my carrier is Simobil (Vodafone).
Any help would be much appreciated. Thanks in advance.
you need to flash one based on your cid which kinda gives you carrier,country info
use this guide as reference
Thank you, i just read this, however I still dont know how to find the right ruu for my phone. There is no Simobil Slovenia on the ruu list. Any other way to find out which rom to flash? The thing is I dont really remember whether I changed my CID at some point or not, so I might not be able to see/find the correct one.
Thanks again.
Ok here is what I found out now:
If i check for CID via fastboot i get this: 11111111 (i remember now, i set this)
But if i check it via application CIDgetter i get this: HTC_032
Q: Is this HTC_032 the true default CID or it could be just the info of currently installed rom, which is Viper 1.3.5 ?
vrocipes said:
Ok here is what I found out now:
If i check for CID via fastboot i get this: 11111111 (i remember now, i set this)
But if i check it via application CIDgetter i get this: HTC_032
Q: Is this HTC_032 the true default CID or it could be just the info of currently installed rom, which is Viper 1.3.5 ?
Click to expand...
Click to collapse
Hi,
CIDGetter will show you your original CID.
When you check it via fastboot,you will get your ACTUAL CID.
If you are s-off,then , you should be able to run a European RUU and get back to stock.
Then, follow the guide ganesh gave you to s-on.
vrocipes said:
Ok here is what I found out now:
If i check for CID via fastboot i get this: 11111111 (i remember now, i set this)
But if i check it via application CIDgetter i get this: HTC_032
Q: Is this HTC_032 the true default CID or it could be just the info of currently installed rom, which is Viper 1.3.5 ?
Click to expand...
Click to collapse
the cid you got via fastboot is the current one you are having
and HTC_032 is the rom cid ..so if you are having stock rom ..it represents your actual cid
Thank you both for your answers. Hmm, so one of you think that CIDgetter gives you original cid, and one thinks it gives you the CID of current rom. If ganeshp is right, then I still dont know my original CID, as currently I have Viper S 1.3.5 rom :// If malybru is right then I have to flash rom with HTC_032 CID and not just any European rom? Again it is important, because I dont want to get rejected on my warranty...
Thanks again.
vrocipes said:
Thank you both for your answers. Hmm, so one of you think that CIDgetter gives you original cid, and one thinks it gives you the CID of current rom. If ganeshp is right, then I still dont know my original CID, as currently I have Viper S 1.3.5 rom :// If malybru is right then I have to flash rom with HTC_032 CID and not just any European rom? Again it is important, because I dont want to get rejected on my warranty...
Thanks again.
Click to expand...
Click to collapse
both of us (me and Malybru ) are saying the same thing
cid from fastboot ..gives you the actual/current cid you have right now
cid from cid getter ..will give you the rom cid (in case of viper it is HTC__032)
also based on your country ..i think the fitting RUU is indeed is of European Unbranded one (as malybru said )
if the phone is not linked to carrier (like contract phone ) then European unbranded is the right RUU
It has been bought through carrier contract, but they stopped locking them, but it could still be locked in case it was from old stock... I'll have to try that, so in case it is locked to the carrier, I need different rom? Im sorry for so many questions but im really lost in finding the right rom.
i'm not shore if this ok, but my ro.aa.maincid is HTC__001 and CID HTC__304 (the two of them extracted with CID Getter.apk), so is this possible?
alexskin said:
i'm not shore if this ok, but my ro.aa.maincid is HTC__001 and CID HTC__304 (the two of them extracted with CID Getter.apk), so is this possible?
Click to expand...
Click to collapse
It would be possible. When I use CID Getter from the play store I only see one on my phone.
Code:
ro.boot.cid 11111111
I don't see a line for
Code:
ro.aa.maincid
I can tell you that the CID is stored in a few partitions on your phone. P4 which you changed as well as P5 & P6. Currently my phone has p4 & p5 as 11111111 but p6 is T-MOB010. I never see T-MOB010 referenced in CID Getter or anywhere else. When most people do SuperCID they normally only do it at p4. I did mine on p5 also just in case but left p6 alone.
You have a very specific problem that I've only seen people mention when they receive their phones back after warranty repairs. My guess is that when HTC replaces the main board some kind of device identifiers aren't changed on the phones internal storage. This causes a mismatch that stops you from unlocking it. In your case something happened when you were downgrading your hboot.
I think you have a chance at getting your phone unlocked but you need to get root. Which is where you're stuck. At this point your best option would be to try and get someone else to get you the unlock_code.bin. By modifying this method
http://forum.xda-developers.com/showthread.php?t=1732980
We already tried it with the IMEI but it might need to go one step further and also replace the serial number and mac address.
dc211 said:
It would be possible. When I use CID Getter from the play store I only see one on my phone.
Code:
ro.boot.cid 11111111
I don't see a line for
Code:
ro.aa.maincid
I can tell you that the CID is stored in a few partitions on your phone. P4 which you changed as well as P5 & P6. Currently my phone has p4 & p5 as 11111111 but p6 is T-MOB010. I never see T-MOB010 referenced in CID Getter or anywhere else. When most people do SuperCID they normally only do it at p4. I did mine on p5 also just in case but left p6 alone.
You have a very specific problem that I've only seen people mention when they receive their phones back after warranty repairs. My guess is that when HTC replaces the main board some kind of device identifiers aren't changed on the phones internal storage. This causes a mismatch that stops you from unlocking it. In your case something happened when you were downgrading your hboot.
I think you have a chance at getting your phone unlocked but you need to get root. Which is where you're stuck. At this point your best option would be to try and get someone else to get you the unlock_code.bin. By modifying this method
http://forum.xda-developers.com/showthread.php?t=1732980
We already tried it with the IMEI but it might need to go one step further and also replace the serial number and mac address.
Click to expand...
Click to collapse
i don't see your line ), thing is that i change my cid to the free spain cid, and every time i try to change it with the oem command line, it fail. we could try changing the other 2 thing, if you want or when you have some spare time
alexskin said:
i don't see your line ), thing is that i change my cid to the free spain cid, and every time i try to change it with the oem command line, it fail. we could try changing the other 2 thing, if you want or when you have some spare time
Click to expand...
Click to collapse
You don't have root on your phone though do you?
Also you wouldn't be able to use "fastboot oem writecid" unless you had S-OFF. You would need to pull it from the phone hex edit it and push it back.
dc211 said:
You don't have root on your phone though do you?
Also you wouldn't be able to use "fastboot oem writecid" unless you had S-OFF. You would need to pull it from the phone hex edit it and push it back.
Click to expand...
Click to collapse
No, i don't. That's the bad part. When i changed it to the free spanish cid i used that command line and it worked, if the phone is relocked and has the stock recovery it will work. it fails after i run the script you gave me butt i don't know why