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.
what are the benefits of doing super-CID (i.e. 11111111)
If i do superCID can I again restore to stock CID..
Please help
abhishek89 said:
what are the benefits of doing super-CID (i.e. 11111111)
If i do superCID can I again restore to stock CID..
Please help
Click to expand...
Click to collapse
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
So how do I install roms from different carriers
fatswaller4451 said:
So how do I install roms from different carriers
Click to expand...
Click to collapse
first you need to S-OFF then supercid
after that you can use any ruu.exe
Super Cid
rzr86 said:
first you need to S-OFF then supercid
after that you can use any ruu.exe
Click to expand...
Click to collapse
Hey thanks for your response
Ok so I have s-off and super Cid just a few more questions if u don't mind
1. can i install any ruu for any android phone or am I limited?
2. Will installing a ruu for another phone effect the way my current phone works
3. When installing a ruu.exe for another phone will I have to follow the same bootloader unlock method for that phone or my phone?
Sorry for the newbie questions but I have limited knowledge of super cid however I have been rooting for years now
I heard some bad things about super cid but have not had any issues thus far, the guide was very easy to follow and in fact just to make sure it was working I was able to ruu backwards
Thanks for your expertise you r awesome
fatswaller4451 said:
Hey thanks for your response
Ok so I have s-off and super Cid just a few more questions if u don't mind
1. can i install any ruu for any android phone or am I limited?
2. Will installing a ruu for another phone effect the way my current phone works
3. When installing a ruu.exe for another phone will I have to follow the same bootloader unlock method for that phone or my phone?
Sorry for the newbie questions but I have limited knowledge of super cid however I have been rooting for years now
I heard some bad things about super cid but have not had any issues thus far, the guide was very easy to follow and in fact just to make sure it was working I was able to ruu backwards
Thanks for your expertise you r awesome
Click to expand...
Click to collapse
1)with s-off and supercid you are not limited
2)it won't affect anything at all
But probably you will have some official updates from the specific carrier(if you have)
3)I think it depends from the carrier of the Ruu you have chosen
But actually there is no need to unlock the bootloader because you are on s-off
Edit:in second and third question what do you mean by another phone?
I assume you mean another carrier
If yes then yes
If you mean another device(for example Samsung)then absolutely no
Of course you can use any ruu but only from sensation's devices
Sent from my HTC Sensation using xda premium
super cid
rzr86 said:
1)with s-off and supercid you are not limited
2)it won't affect anything at all
But probably you will have some official updates from the specific carrier(if you have)
3)I think it depends from the carrier of the Ruu you have chosen
But actually there is no need to unlock the bootloader because you are on s-off
Edit:in second and third question what do you mean by another phone?
I assume you mean another carrier
If yes then yes
If you mean another device(for example Samsung)then absolutely no
Of course you can use any ruu but only from sensation's devices
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
So I have verified that I have super cid on my evo 4g lte by ruuing backward, however when I try flashing an htc one ruu i get an error message that its the wrong file, so i tried flashing an original evo 4g ruu and still get the same message
I am still s-off
relocked bootloader
super cid
hboot 2.0.9
latest firmware
am i missing something?
Thanks
fatswaller4451 said:
So I have verified that I have super cid on my evo 4g lte by ruuing backward, however when I try flashing an htc one ruu i get an error message that its the wrong file, so i tried flashing an original evo 4g ruu and still get the same message
I am still s-off
relocked bootloader
super cid
hboot 2.0.9
latest firmware
am i missing something?
Thanks
Click to expand...
Click to collapse
wait man man
for which device are we talking about?
not for sensation?
EVO 4g lte
Sent from my EVO using xda app-developers app
fatswaller4451 said:
EVO 4g lte
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
no maaaaannnnn
don't use any ruu for sensation to evo 4g
go to the evo 4g's thread and see there for ruu.exe files
this forum is only for sensation/xe/4g
i thought you were talking about sensation devices
Ok thanks for the info but I was talking about super cid and installing roms from different carrier's
Sent from my EVO using xda app-developers app
---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------
I was following a previous thread
Sent from my EVO using xda app-developers app
to reduce the confusion
NO- you cant/shouldn't flash another model phone's RUU on another
there is a high chance of bricking the device if you do that
Does SuperCID also network unlocks the phone?
There is a lot of confusion on the internet about SuperCID. I have HTC One S which is locked to T-Mobile and I want to get it network unlocked. the "strings -n 8 /dev/block/mmcblk0p6" method did not show unlock_code for my phone (though it has worked for some other people). While googling I found that doing SuperCID by changing mmcblk0p4 can also network unlock the phone. Please let me know if you have some idea. Thanks.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
Hi ,
Wanting to get rid of 3 uk junk and flash to normal UK RUU
Do we need super CID?
My bootloader is unlocked , can't download the RUU from from the Dev section as all the slots are gone , or when it seems to work it errors out .
Has anyone got the latest UK RUU file they can share with me and can someone confirm if I need Super CID to run RUU to unbrand
Thanks in Advance
Just flash Modaco or the Virtuous roms through recovery, these are unbranded and really good.
You will need to flash a Recovery image first though.
Hi and thanks
Yes , I understand this but I want to just unbrand through RUU then re-lock my bootloader.
Do we need Super CID ?
Ok can someone remind me if I need S-Off to change the CID , playing around with ADB at the moment
If Im honest mate, no idea what you mean by CID...
But if you want a new rom, all that needs to be done is unlock bootloader, flash recovery, flash rom.
Thats all anyone has done in the dev threads, and worked fine for me (coming from a retail, unbranded unit).
You can 'lock' the bootloader again, BUT it never goes back to its true original state. This is as HTC designed their unlocking/locking process to be (and is stated in their terms when you go to their site to unlock).
Edit: OK, just read up on it. Possibly then! Depends how annoying 3 are I suppose... Probably best to ask one of the devs
Edit 2: CHeck the following, may be of help (though its for the One X)
http://forum.xda-developers.com/showthread.php?t=1594262
http://android.modaco.com/topic/353106-debrand-one-x/
Edit 3: If you're applying a flashable zip, does the CID limitiation on RUUs even come into play?
Hi thanks ,
Yea what I want to achieve is this .
My CID is HG3____001 this will need to be changed to a CID that is HTC UK specific usually HTC_____001
To find out your CID in ADB
Fastboot Getvar CID
To get to a retail version from a branded version , what usually needed to happen was this .
Unlock bootloader , change CID to 11111111 via ADB
Run the specific UK RUU.exe
Change your CID to the HTC_____001 which is the usual default for UK unbranded devices .
re-lock your bootloader and then you should receive OTA updates from HTC instead of your network supplier which can take months
I can't remember if S-off was needed to do this. I have just checked revolution site and One s is not listed , will play around tonight though and see
Thanks for the help so far
Hi, I know what CID is - coming from the Sensation.
I dont think its possible to change CID without S-OFF, you cant use advanced ADB functions with S-ON
Until revolutionary or someone else makes tool for S-OFF, we will just have to stick with HTCDev, Its not the best, but it allows to flash recovery and ROMs so its better than nothing.
Im pretty sure there will be some progress in the next few weeks, Once the phone is available worldwide
Ahh ok , thanks , yea this phone is set S- on , so S-off will be needed sooner or later
yeah, as development develops and more rights are needed from the phone, S-0FF will eventually be a MUST.
I wish it was available already, I hate the fact that HTC know i have tampered with my HBOOT and voided my warranty.
Luckily enough, if i have a problem, my provider fixes / repairs the phone, Not HTC, So i might just get off lightly
I think HTC will know if you have tampered with the phone period if they wish to look that far into it .
Unless you fry your processor where you have set it too high etc then shouldn't be a problem. If you have a hardware problem such as your screen fails , battery etc then should be fine .
As you say though , if you brought it through a retail unit then that is where it is returned so in some respects is a bit easier as they will use a third party repairer acting for HTC .
well with the sensation it was possible to return everything back to stock, Including the bootloader and S-ON..
There was no way it could be diagnosed as being tampered with, If you did it properly..
But with HTCDev. youve already submitted a code (which i assume contains serial number) so all they have to do is check whether that device matches anything on their database of tampered devices. Thats why i dislike it so much..
But i need root for most of my apps so there was no workaround for me...
I see on the One X forum S-off is under way . Can't wait to get this baby to true stock.
Just did another Google search for S-Off on the S but nothing as yet .
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
I have custom recovery, updated HBOOT and running CM11.
Now its time to buy new phone and sell this one.
But how to downgrade this all and install official HTC Sense? (Not some custom Sense-based ROM).
As i imagine this i need to install windows and some HTC special apps, and somehow remove recovery...
You need to provide more details. Post your bootloader details please, as well as the original CID that came on the phone. Also, questions go in the q&a section, I'll ask for this to be moved there for you.
Transmitted via Bacon
timmaaa said:
You need to provide more details. Post your bootloader details please, as well as the original CID that came on the phone. Also, questions go in the q&a section, I'll ask for this to be moved there for you.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, sorry for wrong section.
Seems original CID is lost, it will not allow to install original firmware with fake one? Or just some warranty things?
Model: One XL
Bootloader screen:
itspers said:
Thanks, sorry for wrong section.
Seems original CID is lost, it will not allow to install original firmware with fake one? Or just some warranty things?
Model: One XL
Bootloader screen:
**image removed for security**
Click to expand...
Click to collapse
Edit that image out asap, it contains your IMEI, which should never be posted publicly.
Did you not make note of the original CID before changing it? You shouldn't sell a device with SuperCID unless the buyer specifically wants a modified device and understands the dangers. Is it an at&t model? Telstra? Rogers? Hong Kong?
Transmitted via Bacon
timmaaa said:
Edit that image out asap, it contains your IMEI, which should never be posted publicly.
Did you not make note of the original CID before changing it? You shouldn't sell a device with SuperCID unless the buyer specifically wants a modified device and understands the dangers. Is it an at&t model? Telstra? Rogers? Hong Kong?
Transmitted via Bacon
Click to expand...
Click to collapse
I made a note in txt file on desktop... And thought "need to save in in some googledoc or so.."
Its At&t american, ordered from ebay to Ukraine and than i bought it in local auction site 2 years ago. For this years i lost even charger, so will sell only phone without any documents and boxes.
I made all this HBOOT and CID changes just to get CM working, what dangers this can produce?
itspers said:
I made a note in txt file on desktop... And thought "need to save in in some googledoc or so.."
Its At&t american, ordered from ebay to Ukraine and than i bought it in local auction site 2 years ago. For this years i lost even charger, so will sell only phone without any documents and boxes.
I made all this HBOOT and CID changes just to get CM working, what dangers this can produce?
Click to expand...
Click to collapse
The danger is that to return the device to stock you need to return it to being s-on, and if we weren't able to work out what the original CID was it would remain as SuperCID. Here's where the danger is, running any RUU 4.1 or above while the phone is s-on and with SuperCID will brick the phone. But, if it's an at&t device then the original CID is CWS__001. Are you wanting to return the device to fully stock at&t specs?
Transmitted via Bacon
timmaaa said:
The danger is that to return the device to stock you need to return it to being s-on, and if we weren't able to work out what the original CID was it would remain as SuperCID. Here's where the danger is, running any RUU 4.1 or above while the phone is s-on and with SuperCID will brick the phone. But, if it's an at&t device then the original CID is CWS__001. Are you wanting to return the device to fully stock at&t specs?
Transmitted via Bacon
Click to expand...
Click to collapse
I want to return it in some condition where someone who will buy this phone will not break it by trying to update from preferences.
If i will leave it as is - i need to write full list of all this changes i made with bootloader and firmware when will be selling, cause somebody will think its not unlocked, or not rooted, will try to do something and get brick. But in same time if i will write some much info - will be hard to sell it, cause 90% of people never saw clean android here, they will think its something wrong.
This is main reason to flash original firmware.
But if i will only flash original rom - in some day buyer will try to update it via HTC and get error and call me, or in worst case get some brick...
So if it possible to revert everything - please tell me some list of things to do: CID, S-OFF etc. and where to read about them on forum.
itspers said:
I want to return it in some condition where someone who will buy this phone will not break it by trying to update from preferences.
If i will leave it as is - i need to write full list of all this changes i made with bootloader and firmware when will be selling, cause somebody will think its not unlocked, or not rooted, will try to do something and get brick. But in same time if i will write some much info - will be hard to sell it, cause 90% of people never saw clean android here, they will think its something wrong.
This is main reason to flash original firmware.
But if i will only flash original rom - in some day buyer will try to update it via HTC and get error and call me, or in worst case get some brick...
So if it possible to revert everything - please tell me some list of things to do: CID, S-OFF etc. and where to read about them on forum.
Click to expand...
Click to collapse
The first thing you need to do is backup whatever personal data (images, music, etc) you have on the device to your PC.
Next go into TWRP recovery and wipe data and sd card (internal storage).
Boot the phone and make sure all of your personal data is gone.
Next you want to run the at&t 5.18 RUU:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
After that you can return the device to the original CID:
Code:
fastboot oem writecid CWS__001
Then relock the bootloader:
Code:
fastboot oem lock
Then return the device to s-on:
Code:
fastboot oem writesecureflag 3
Now you have a fully stock device.
Transmitted via Bacon