Database Info

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

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.

[Q] Defining RUU

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

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

[Q] Telstra One XL Help.....

I was wondering if someone could help me? ... I recently acquired a Telstra Htc One XL and am having troubles trying to update.
Current stats
android 4.1.1
sense 4+
software 3.17.841.2
EVITA PVT SHIP S-OFF RL
*****locked*****
CID-11111111
HBOOT 2.14.0000
RADIO- 0.23a.32.09.29
I'm 99.9% sure most testra one xl's are up to 4.2.2 with sense 5 which is i think two updates in front of mine
can anyone shed some light on my situation?

When you say you're having trouble updating what exactly do you mean?
Sent from my Evita

When i "Check for Updates" it tell me that there are no more updates.... when Im sure there are another two...

Are you in Australia?
Sent from my Evita

Sure am ... Good old city of churches" Adelaide" ..

timmaaa said:
Are you in Australia?
Sent from my Evita
Click to expand...
Click to collapse
His profile says he is

Yeah, but still needed to check. Have you thought about re-unlocking your bootloader? It's been modified in the past which might have something to do with your update problem. If you unlock your bootloader you'll be able to install a custom recovery and then you can install whatever ROM you like. We have the stock Telstra Sense 5 Android 4.2.2 ROM in our development section. We also have a few other Sense 5 ROMs to choose from, ranging from stock to tweaked.
Sent from my Evita

The thing is that it hasnt been messed with.I got the phone from a HTC rep that i know ... he had it in his draw for over six months ...I just wanted the stock update but maybe rooting might be the easier way

It definitely has been messed with, phones that are s-off and have SuperCID don't come out of the factory like that. Somewhere along the way someone has done those alterations to the device.
There is just one problem I've realised, your phone has a SuperCID of 11111111 which has been blocked by htcdev. You're s-off though so you can actually change that as many times as you like using fastboot. If you want to unlock your phone you'll need to change it to 22222222 using the following fastboot command:
Code:
fastboot oem writecid 22222222
You can then check the new CID by using this command:
Code:
fastboot oem readcid
Once that's done you can go to htcdev and go through with the unlock bootloader process.
In order to do the above process you will need to install adb/fastboot and HTC drivers.
Sent from my Evita

No problem ... thanks for that ....I have rooted my one x before HTC_023 fairly basic but my mate swears that the phone came straight from HTC as a Tell us what you think before we send you more kind of thing .. Cheers for the info ...
Actually one more thing ... is it possible to do a RUU update with this to 4.2.2?

There is no RUU for 4.2.2, the only way is to run an earlier RUU and take OTA updates to get there. Since you can't get the OTA I guess that isn't an option though.
Sent from my Evita

grekojim said:
Sure am ... Good old city of churches" Adelaide" ..
Click to expand...
Click to collapse
Within 30 minutes drive from me no doubt
Supercid and s-off from factory or not still means you are off the official path.
Things I might do:
fastboot oem writecid TELST001
Then try the OTA again
or
RUU back to 1.89.841.9 as a RUU exists for that, then ota forwards to 5.06.841.1
or
Unlock bootloader
Flash Turges 5.08 firmware zip and then take one of the Sense 5 ROMs. There is a stock Telstra ROM even.
PS nag the HTC rep for a more recent RUU, eg 2.40.841.4, 3.17.841.2, 3.17.841.9 or 5.06.841.1 and share with us
---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------
timmaaa said:
Once that's done you can go to htcdev and go through with the unlock bootloader process.
Click to expand...
Click to collapse
He has s-off does he need a token or even need to unlock at all?

I have often wondered the same thing, but I've been assuming that in order to flash TWRP recovery you need an unlocked bootloader.
It's nice to see a few Aussies on here by the way, I'm in Melbourne myself.
Sent from my Evita

great ... trying the cid thing first ...

My phone from an att employee came s-off and with a locked boot loader as well. It just looks like that's how HTC and att do it.
Sent from my HTC One XL

Alright cid change didnt work ..now to find the 1.89.841.9 RUU

Click the link in my signature, from there you'll find a link to the HTC RUU thread.
Sent from my Evita

RUU links all changed and the index doesnt keep good track of the current RUU sites.
Try:
http://www.androidruu.com/?developer=Evita
http://www.androidruu.com/getdownlo...09.01_10.93a.32.20L_release_266699_signed.exe

Thank you heaps .....

Just in case .. i got the unlock code from htc deV But when my cid was 11111111 .....would that matter if i use that code now that my cis is telst001?