Database Info

[Q] RUU and HBOOT screen question

I have a sensation that was locked to orange, i S-Off'd and rooted, and un sim-locked but after the screen started playing up i decided to to unroot and S-On, in case of any warranty issues. When i S-On'd i flashed a stock HTC Europe ROM, if returning for repairs can i use this ROM or do i need to use the stock Orange ROM?
Also when device is in HBOOT, above Pyramid PVT Ship S-On RL it says ***LOCKED***, what does this mean? Does it mean it is not completely back to stock? I cannot see what it means as the device is no longer simlocked as it takes a Tmobile sim.
Thanks

gtcalder said:
I have a sensation that was locked to orange, i S-Off'd and rooted, and un sim-locked but after the screen started playing up i decided to to unroot and S-On, in case of any warranty issues. When i S-On'd i flashed a stock HTC Europe ROM, if returning for repairs can i use this ROM or do i need to use the stock Orange ROM?
Also when device is in HBOOT, above Pyramid PVT Ship S-On RL it says ***LOCKED***, what does this mean? Does it mean it is not completely back to stock? I cannot see what it means as the device is no longer simlocked as it takes a Tmobile sim.
Thanks
Click to expand...
Click to collapse
Actually it means that you are back to stock. I take you still have super cid as you flashed different ruu? That would be an instant giveaway that you've tampered with your phone if they happen to check it.

tinky1 said:
Actually it means that you are back to stock. I take you still have super cid as you flashed different ruu? That would be an instant giveaway that you've tampered with your phone if they happen to check it.
Click to expand...
Click to collapse
Yeah, i used supercid, i wasnt sure how to find the specific cid for the stock ROM, if i use the correct cid for that ROM will it remove any traces?
Thanks

Thing is now you can't change cid as you are s-on LOL. Keep looking for your original RUU, then s-off, change cid to original one and flash stock RUU.
Sent from my HTC Sensation Z710e using XDA App

CID
Can somebody explain how I can return my CID to default before I run the RUU for my region.
I know my CID was HTC__001 and I have checked the guide in the dev section but it just say to run the command
fasttboot oem writesecureflag 3 which I think turn S-on??

Yeah i understand i need to return to S-Off thats not the problem, how do i find the cid for the stock ROM? Orange UK 1.35.61.1

hope it helps
gtcalder said:
Yeah i understand i need to return to S-Off thats not the problem, how do i find the cid for the stock ROM? Orange UK 1.35.61.1
Click to expand...
Click to collapse
I found this list, hope it helps
http://forum.xda-developers.com/showthread.php?t=1195475&highlight=CID

Thanks a lot! Exactly what i needed, will be flashing stock Orange ROM pronto!
One other thing, If i have any trouble with my phone, as it is sim unlocked by myself, can they tell this even with S-On, Stock ROM and CID? I know that if you go in there they often ask for you phone number etc, (i could just get a free orange PAYG sim and stick it in if i ever have any trouble) and if i tell them it and its flags up as a Tmobile number will they refuse to repair as well (as they can tell it wouldve been unlocked)? Also the phone was off ebay and i have no proof of purchase, but its in an orange branded box and the phone has orange branding on the back, should this be legitimate proof?
Thanks

My phone was unbranded when I bought it so I can't answer your questions, sorry. I hope some one comes and helps.
Let me know if it works OK to get your CID back to your default, I need to do mine tonight but I'm a bit wary of doing it and the whole RUU process.
Sent from my HTC Sensation Z710e using XDA App

Ok i shall do, I hope someone can shed some light!
I have just S-Off'd and written the CID, seems no problem and i am just about to flash the ROM, i shall update you in a mo.
Just follow this guide and you should be fine!
Cheers
---------- Post added at 04:36 PM ---------- Previous post was at 04:09 PM ----------
Just finished flashing the ROM, everything seems ok, although i now need to edit APN settings as Im using a Tmobile sim and an Orange ROM. Good luck and let us know how you get on, it is reasonably straighforward!

All sorted no problems at all, I just restored stock ROM then changed my CID back to HTC__001 then I put s-on and viola back to stock phone.
Sucks when your used to custom ROMs
Nik
Sent from my HTC Sensation Z710e using XDA App

Guys when you buy an unlocked phone not bound to any carrier isnt the cid just 1111111 by default? Just curious coz i have one i need to send to rep.

nicolajkl said:
Guys when you buy an unlocked phone not bound to any carrier isnt the cid just 1111111 by default? Just curious coz i have one i need to send to rep.
Click to expand...
Click to collapse
Its HTC__001 ,the one you are looking for.
11111111 is SuperCID, if you send it back with that CID, they can tell you've been fiddling..

Are you completely sure HTC_001 is the unlocked cid in Denmark aswell? Coz there's a way to flash it back

niklfc83 said:
I found this list, hope it helps
http://forum.xda-developers.com/showthread.php?t=1195475&highlight=CID
Click to expand...
Click to collapse
Here's the link to the list of cid codes I posted in ages ago in this thread, my unlocked European sensation was HTC__001. I'm in the UK though.
Hope its useful to you
Nik
Sent from my HTC Sensation XE with Beats Audio using XDA App

Ok and that cid will work with the European ROM?
Sent from my HTC Sensation Z710e using XDA App
EDIT:
Okay so i tried with HTC__001 that wouldn't give me danish language, so i tried again with the Denmark cid and everything works now! Just sure hope thats the cid they use!
Thx for the help !
EDIT:
Once moar
You will need to flash the RUU with superCid, then change cid back to land code and then remove s-off
Nicolajkl

Command Error when changing CID

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

[Q] cid change and OTA updates???

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.

S-OFF and warranty

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.

Do I need a new mobile?

Do I need a new mobile? A question that I often imagine in the last days... What's the situation?
Here are the base informations of my HTC One S:
Original CID: O2___102
Actual CID: 11111111
Boootloader informations:
VLE PVT SHIP S-ON RL
HBOOT-2.13.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012, 15, 15:44:01:-1
The story
What happens. Because of the license mess with CyanogenMod I've tried different ROM's but all in all there where always a reason to change the ROM. After all I want to give Carbon a try but for this you have to upgrade the firmware and so the mess starts.
In fact o2 Germany is not able to deliver a proper RUU I've changed the CID to SuperCID (11111111) and tried to install the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4. This and all my other installations of different RUU's breaks with a signature error. Next step was to change the CID to HTC__102 but this didn't help anything.
Now I was thinking to go back to the root and install the first custom ROM I've used. So I want to give ViperROM a try. With this it was not able to get the WiFi up and running. Next step was to give TrickDroid 10 and ZenROM a chance. There was no problem with the installation and both of them where running. The problems here are that both of them are far away from a daily driver.
Today I saw that there are again official CyanogenMod nightlies and so I've thought to install the base ROM of so many custom ROM's. This installation breaks with the error message: "failed : getprop("ro.bootloader") == 2.15.000" So It seems that the newest bootloader is a basic requirement. The problem is now that I'm unable to get the newest hboot because of the RUU signature problem.
I don't know what to do anymore. RUU update does not working. S-OFF does not working. The firmware upgrade is not working. Do I have to use the One S as a paperweight?
So .. I'm really grateful and happy about every hint, every tip or solution.
Thanks a lot
Christian

Why is S-OFF not working and why did you changed your CID back to stock? You have to get S-OFF and SuperCID so follow this guide. Report back at which step you fail

Uwe303 said:
Why is S-OFF not working and why did you changed your CID back to stock? You have to get S-OFF and SuperCID so follow this guide. Report back at which step you fail
Click to expand...
Click to collapse
Good morning,
sorry for my late response. I was so frustrated that I went off yesterday evening.
I've tried different things with the CID:
changed the O2___102 to 11111111
changed the 11111111 to HTC__102
rollback to 11111111
The reason was that I had found the RUU instructions which stated that there could be potential problems with RUU installations and SuperCID.
Based on this thread the S-Off always stops at step 5. I get an error message that says: "FAILED (remote: 99 unknown fail)". I've already tried the different things. Switch off the phone, switch off the computer, useing the original HTC USB cable and so on. Nothing worked here.
Thanks a lot
Christian

Try updating the HTC drivers on your PC then try again. There's a thread somewhere around the One S forums.

After the soff, supercid is not needed anymore.
Have you tried o2 ruus from a different country?
Btw is the ruu erroring because of your MID? Whats yours? Pj4010000?
Sometimes if a ruu errors, directly retrying sometimes works.
Verstuurd van mijn HTC One S met Tapatalk

YES! It's again up and running
After some days of troubleshooting my One S ist up and running again
First was the tip of djsubtronic. I've checked the drivers on my PC. But I've already installed the latest one. Then I've made a clean, fresh new installation on my notebook. But nothing changed.
Then I've tried some other RUU's. But there where always the same error. So... after all I was already looking for a new mobile device and then I've made ​​a final attempt.
Cleaned storage from bootloader
Reset from bootloader
Installed TWRP recovery (2.5.0.0)
Format the sdcard from Windows
Nothing left on the sdcard
System reset from TWRP
System wipe from TWRP
Followed step by step and extreme exactly the instructions of the firmware update thread
The second try to manual update the hboot then was succsessful
After that I was able to install the latest CyanogenMod nightly
Thanks a lot for every tip. They took me to re-read everything again and then start again from scratch. After all I'm already S-On. I'm happy that my phone is running again, I just do not quite trust myself to tackle the topic...
Thanks again...
Christian

Nice to hear you have your phone up and running again.
I want to ask something.
I too, don't have JB RUU for my carrier of the device.
So will S-off and subsequently changing CID to something which has an RUU help? Will that RUU work?
My basic purpose is to go fully stock.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Nice to hear you have your phone up and running again.
I want to ask something.
I too, don't have JB RUU for my carrier of the device.
So will S-off and subsequently changing CID to something which has an RUU help? Will that RUU work?
My basic purpose is to go fully stock.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hi, if I understand this correct than yes. If you change the CID to a "non branded" CID. (SuperCID - 111111 or HTC - HTC__102) you should be able to install other RUU's for your device. I don't know why this didn't work for me but for normal this should work.
Christian

chmarx said:
Hi, if I understand this correct than yes. If you change the CID to a "non branded" CID. (SuperCID - 111111 or HTC - HTC__102) you should be able to install other RUU's for your device. I don't know why this didn't work for me but for normal this should work.
Christian
Click to expand...
Click to collapse
From what i have read and understood, yours must be a problem of MID. This is another requirement in addition to CID.
Sent from my Nexus 7 using Tapatalk HD