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.
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.
Hi folks,
I have unlocked and s-offd my Voda HTC Chacha.. installed a WWE Rom but havent recieved any OTA since then.. I am on 1.19 and there is a 1.54 OTA out..
just checked the CID through adb and its set to Super CID 11111111 instead of generic HTC__001. Tried changing it but I get Command Error. Any idea or solution for this?
Also, Is this the reason why no OTA are showing up?
If no, please advise how can I update the phone via OTA
Many thanks
What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK
qzfive said:
What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK
Click to expand...
Click to collapse
Here are the full details mate:
Android 2.3.3
Software 1.19.206.2
Baseband 47.14.35.3030h_7.47.35.17
Kernel 2.6.35.10-g8db500e
cheers
Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.
qzfive said:
Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.
Click to expand...
Click to collapse
Fantastic mate, downloaded it as we speak..
not sure how it stayed on 1.19 as after I used XTC Clip, the logos and boot image were gone so I assumed I had a stock rom.. oh well.. everyday is a learning day..
I will let you know how I get on..
cheers for your help mate..
Update... Installed the 1.33 which then took the OTA update which is all good... However I still can't change the CID to HTC__001.. (currently set at 1111111)
Sent from my HTC Sensation Z710e using Tapatalk
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
I know but it doesn't help with OTA updates
Sent from my HTC Sensation Z710e using Tapatalk
ok, but..
ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
True, but it forces non-qwerty keyboard users to manually modify the layout in /system/usr/
as described here , because CID is taken into account on default layout.
Once you know the trick, it's OK, but really annoying to do every time you install a new ROM
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
hello i just changed my cid from HTC__203 to HTC__E11 (dutch), do i still receive ota updates and what about warranty does it affect it???
btw I live in the Netherlands and dit try to search but without any significant results.
edit: after a hardreset i see that i do get OTA updates from HTC so that part is ok.
Now just for the warranty part....
lexuz said:
hello i just changed my cid from HTC__203 to HTC__E11 (dutch), do i still receive ota updates and what about warranty does it affect it???
btw I live in the Netherlands and dit try to search but without any significant results.
edit: after a hardreset i see that i do get OTA updates from HTC so that part is ok.
Now just for the warranty part....
Click to expand...
Click to collapse
the ota works i just know that i don't know if it invalidates the warranty...but if you flash the right RUU (always do it before sending it to HTC) you will get your CID back
matt95 said:
the ota works i just know that i don't know if it invalidates the warranty...but if you flash the right RUU (always do it before sending it to HTC) you will get your CID back
Click to expand...
Click to collapse
Hi, how do i know witch ruu to use? (Old cid was htc__203)
Off topic: beautiful city u come from.
here you can find all the RUUs but you have to be registered and pay however you can find which is your RUU and google it
matt95 said:
here you can find all the RUUs but you have to be registered and pay however you can find which is your RUU and google it
Click to expand...
Click to collapse
If if download a ruu and then flash it, don't i keep de cid that i now have? I know that after a hardreset the cid stays the same.
I can confirm flashing a RUU NOT gives you your CID back.. I flashed 1.45 RUU and my CID is still 111111
Sent from my Pyramid-T using xda premium
BurnRubber90 said:
I can confirm flashing a RUU NOT gives you your CID back.. I flashed 1.45 RUU and my CID is still 111111
Sent from my Pyramid-T using xda premium
Click to expand...
Click to collapse
just like i thought, how the h#ll do i change my cid back to original?
If someone can confirm that Cid change doesn't affect warranty then this thread can be closed
If you want to change your Cid back just use the same process you used to change it, and if you don't know your Cid look here...
http://forum.xda-developers.com/showthread.php?t=1195475
Zylograth said:
If you want to change your Cid back just use the same process you used to change it, and if you don't know your Cid look here...
http://forum.xda-developers.com/showthread.php?t=1195475
Click to expand...
Click to collapse
I do know that thread but i'm still s-on and it seems that i can't change my cid back. ( i thought i saw someone else with the same problem in this forum.)
It seems i could only change it once with s-on.
hey guys,
I have a one s with the following info
cid = t-mob102
android version = 4.03
htc sense = 4.0
software number = 1.84.531.2 710RD (MoDaCo.one ir3)
i wanted to go back to stock rom, so ive downloaded a RUU, but it wasnt the right one.(says ERROR [130]: MODEL ID ERROR)
i wonder if anyone knows which ruu i should use to get back to my phones stock?
its kinnda urgent.
thanks in advance
m2afs said:
hey guys,
I have a one s with the following info
cid = t-mob102
android version = 4.03
htc sense = 4.0
software number = 1.84.531.2 710RD (MoDaCo.one ir3)
i wanted to go back to stock rom, so ive downloaded a RUU, but it wasnt the right one.(says ERROR [130]: MODEL ID ERROR)
i wonder if anyone knows which ruu i should use to get back to my phones stock?
its kinnda urgent.
thanks in advance
Click to expand...
Click to collapse
Goto http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
I think there are a few T Mobile RUUs there. On the second page there is
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501
which likely should work.
On the first page there is also an upgraded RUU for T Mobile
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04
If your OK with an upgrade go for that one. Just remember it may upgrade your bootloader and radio. If you wanted to flash older radios after that, you would have to go through a more complicated bootloader downgrade.
Those should work.
AKToronto
actually the ruu i have downloaded that says its the wrong model is exactly the following
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed
as Ive looked inside its ROM this ruu is for t-mob010 not for t-mob102. and i guess thats why it fails.
what now?
Ive realized my phone loses signal from time to time and after a research i found out that upgrading to that specific version will solve the problem, but right now i cant really get into it coz i don't know the exact RUU to use.
the process i tried to do this is
1.i tried the normal way
-boot into fastboot
-relock the bootloader
-reboot to fastboot again
-run the ruu
-got error 130
2.i tried without locking the bootloader
the same process
-got error 155
i dont know if im missing something here, im new to android and all the flashing stuffs, any help would be appreciated.
So, I've found out that T-MOB102 refers to T-Mobile Austria, and I should be looking for one with this signature x.xx.112.x.
Still I haven't found any with the signature for ONE S.
Any Suggestions?
still nothing on the TMA T-MOB102 T-Mobile Austria RUU.
I've tested every RUU in Here: filefactory.com/f/cf061f69b5bf7878/
None of them were mine, how is it possible that there's no RUU made for my phone type.
Should I Change my CID? Is It possible?
m2afs said:
still nothing on the TMA T-MOB102 T-Mobile Austria RUU.
I've tested every RUU in Here: filefactory.com/f/cf061f69b5bf7878/
None of them were mine, how is it possible that there's no RUU made for my phone type.
Should I Change my CID? Is It possible?
Click to expand...
Click to collapse
So I think you have two options. One is CID, or two is to keep trying to find that RUU.
1. There is a link to Super CID instructions in the dev forum at http://forum.xda-developers.com/show....php?t=1671643
-Do read a bit of the thread. You can still only flash a RUU that has a bootloader version equal or higher than what is on your phone.
2. If there is a RUU that you think exists that Football has not posted in his thread, than I suggest PM ing him. Thats how I was able to get the three Bell Mobility RUUs onto FileFactory. He was pretty helpful when I PMed him myself.
Cheers,
AKToronto
How Can I PM Football?
m2afs said:
How Can I PM Football?
Click to expand...
Click to collapse
Click on his name in any of his posts. Then click send message. I use PM to stand for private message.
AKToronto