Database Info

[Q] Supercid

i've been roaming the HTC One S forums a lot lately, and i've been seeing 'supercid'... i've tried researching on numerous websites but can't quite understand what it is? was wondering if anyone could explain what it is exactly and what it does... thanks

each One S has a CID number, This relates to which country / region the device is from. HTC__001 means HTC Generic Unbranded, As it left the factory, Now most carriers change this to make the phone run their branded software and to receive their branded OTA updates.
Example, Mine is VODAP100 - Which means i can only get updates from Vodafone, not HTC, If i change that to HTC__001 i can get updates from HTC and not Vodafone.
If you change it to 11111111 (superCID) then you will bypass the CID check It also allows you to flash ANY RUU from anywhere in the world allowing you to run, for instance, UK software on a US model or any combination for that matter.
So say there is a Firmware upgrade that is released in the US, It includes various bug fixes and is required to upgrade to a higher Android version, But your in Hong Kong and cannot get this update, You can change your CID and be able to flash this firmware (S-OFF maybe needed)

damn man thats as good of an explanation as am gonna find anywhere! thanks man! how do I change my phones CID btw? am on TMOUS ..thanks again
Sent from my HTC VLE_U

check this http://forum.xda-developers.com/showthread.php?t=1671643
Its not as confusing as it looks, Just simply copy and paste the adb commands

ahhh OK OK makes more sense ..I'll try it and thanks again for the help man
Sent from my HTC VLE_U

dr_rick13 said:
damn man thats as good of an explanation as am gonna find anywhere! thanks man! how do I change my phones CID btw? am on TMOUS ..thanks again
Sent from my HTC VLE_U
Click to expand...
Click to collapse
Hi I am on T-Mobile US model and I updated to 2.21 Euro. So if you have any questions, will try to help. Good Luck.

dr_rick13 said:
ahhh OK OK makes more sense ..I'll try it and thanks again for the help man
Sent from my HTC VLE_U
Click to expand...
Click to collapse
Be very careful a you can brick the device.
T-MobileUS HTC One S running Stock Rooted 2.21.

Charkatak said:
Hi I am on T-Mobile US model and I updated to 2.21 Euro. So if you have any questions, will try to help. Good Luck.
Click to expand...
Click to collapse
My phone t-mobile us, can you help me updated rom ship Euro?
Sent from my HTC One S using Tapatalk 2

[Q] HTC One S S4 Ville U Changing the CID

Hi,
I'm facing a problem.
I'm trying to change the TMUS T-MOB010 CID to super cid 11111111 or HTC__001 by following the below link.
http://forum.xda-developers.com/showthread.php?t=2155135
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
But by doing alll this process I the end when I check it is still T-MOB010.
Any body help please.
Thanks and Best Rergard's

adeebulrehman said:
Hi,
I'm facing a problem.
I'm trying to change the TMUS T-MOB010 CID to super cid 11111111 or HTC__001 by following the below link.
http://forum.xda-developers.com/showthread.php?t=2155135
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
But by doing alll this process I the end when I check it is still T-MOB010.
Any body help please.
Thanks and Best Rergard's
Click to expand...
Click to collapse
I'm having the same problem. I've followed the steps. Made sure I've modified position 214, but
Code:
fastboot oem get_identifier_token
always shows T-MOB010for me too
were you able to solve the problem?

whats your current softwareversion?
the latest jb tmob ota has been problematic for supercid

kearneyman said:
I'm having the same problem. I've followed the steps. Made sure I've modified position 214, but
Code:
fastboot oem get_identifier_token
always shows T-MOB010for me too
were you able to solve the problem?
Click to expand...
Click to collapse
I think that after doing OTA Update not possible for T-mobile Users or other also.

real187 said:
whats your current softwareversion?
the latest jb tmob ota has been problematic for supercid
Click to expand...
Click to collapse
Yes You are right after OTA update not possible to change CID.

real187 said:
whats your current softwareversion?
the latest jb tmob ota has been problematic for supercid
Click to expand...
Click to collapse
Why i'm not able to install stock T-mobile rom.

Whats the softwareversion?
Verstuurd van mijn One S met Tapatalk

adeebulrehman said:
Why i'm not able to install stock T-mobile rom.
Click to expand...
Click to collapse
You will need the RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2
the old one (RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed) will not work any more

kearneyman said:
You will need the RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2
the old one (RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed) will not work any more
Click to expand...
Click to collapse
Thanks

I am having the same problem. Were you able to find a solution?
Sent from my Nexus 7 using xda app-developers app

Jtag
Go to a Riff JTAG repair shop. Get boot of htc one s model no. PJ401100 flashed through jtag and also tell him to change CID to HTC__102 and now run European RUU in bootloader. Now u have European htc one s of model id PJ401100. Also u can update OTA to jellybean4.1 european version,all Tmobile gone. I did this 4 months ago. Costed Rs.1500 in India.

hschtc said:
Go to a Riff JTAG repair shop. Get boot of htc one s model no. PJ401100 flashed through jtag and also tell him to change CID to HTC__102 and now run European RUU in bootloader. Now u have European htc one s of model id PJ401100. Also u can update OTA to jellybean4.1 european version,all Tmobile gone. I did this 4 months ago. Costed Rs.1500 in India.
Click to expand...
Click to collapse
Got it for 1200/-

Offtopic - I have to admit that the stock ROM is the best ROM for One-S... Maybe it's just me but that;s what I realized. I've had a hard time getting back to stock and I won't change it again. Cyanogen for example had lots of bugs, poor battery, poor camera, saw aonly 2 GB of internal memory instead of 6, etc... In a few words, HTC did a great job with their ROMs, AND especially with this great phone

ntldr said:
Offtopic - I have to admit that the stock ROM is the best ROM for One-S... Maybe it's just me but that;s what I realized. I've had a hard time getting back to stock and I won't change it again. Cyanogen for example had lots of bugs, poor battery, poor camera, saw aonly 2 GB of internal memory instead of 6, etc... In a few words, HTC did a great job with their ROMs, AND especially with this great phone
Click to expand...
Click to collapse
+1

hschtc said:
Go to a Riff JTAG repair shop. Get boot of htc one s model no. PJ401100 flashed through jtag and also tell him to change CID to HTC__102 and now run European RUU in bootloader. Now u have European htc one s of model id PJ401100. Also u can update OTA to jellybean4.1 european version,all Tmobile gone. I did this 4 months ago. Costed Rs.1500 in India.
Click to expand...
Click to collapse
whr do u live bro.....Can i Get my One s Tmobile flashed through Riff JTAG at.HTC COSTOMER CARE...or i should search for some private shops.....

Boot Loop Problem :((

Hi
yesterday I unlocked and rooted my international version of one xl with all in one toolkit. after that I wiped all data with twrp and reboot but it said there is no OS
so I downloaded Viper Xl and flash it by twrp but it stucked in boot loop. I wipe the cache and dalvip but it couldn't help. I downloaded the cyanogen too but it stucked in the boot animation
please somebody help me with this, I just want my phone back
S-on
Hboot 2.10

Which phone do you have? The One X or the One XL?
Sent from my Evita

timmaaa said:
Which phone do you have? The One X or the One XL?
Sent from my Evita
Click to expand...
Click to collapse
I have one xl
evita_utl

First off verify in bootloader that you have an evita.
Hboot 2.10??
Hopefully you meant 2.14... If so the boot image from the viper Rom needs to be flashed via fastboot.
Fastboot flash boot boot.img
Unzip viper Rom on pc and copy boot.img to working adb folder flash and reboot. That should work
Sent from my HTC One XL using xda premium

See questions 11 and 23: http://forum.xda-developers.com/showthread.php?t=2136172
---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------
MURCIE'LAGO said:
Hi
after that I wiped all data with twrp and reboot but it said there is no OS
Click to expand...
Click to collapse
Why do people keep doing this, then are shocked there is no OS?
/system is where the current ROM/OS is stored. If you wipe it, then obviously you will have no OS.
But more more importantly: Don't wipe things if you don't know what they are.

timmaaa said:
Which phone do you have? The One X or the One XL?
Sent from my Evita
Click to expand...
Click to collapse
31ken31 said:
First off verify in bootloader that you have an evita.
Hboot 2.10??
Hopefully you meant 2.14... If so the boot image from the viper Rom needs to be flashed via fastboot.
Fastboot flash boot boot.img
Unzip viper Rom on pc and copy boot.img to working adb folder flash and reboot. That should work
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
that's one xl man, as I said it's the international version of at&t one x with dual core processor and 32gb memory ...
and hboot is 2.10 , believe me
ok I flash boot.img by fastboot and it's ok and my lovely one xl came back to life
thanks for help and support

MURCIE'LAGO said:
that's one xl man, as I said it's the international version of at&t one x with dual core processor and 32gb memory ...
and hboot is 2.10 , believe me
ok I flash boot.img by fastboot and it's ok and my lovely one xl came back to life
thanks for help and support
Click to expand...
Click to collapse
There is no international at&t, there's international quad OR at&t Dual
There is no 2.10 hboot for the dual either. 1.09,1.11,1.14,2.14 <-- Are all I've ever seen.
I would check bootloader to see what the device codename is just to be safe for future reference.

I did some research on this a few days ago. He has the Evita_UTL, which is another version of the dual-core found in the middle east (I'm guessing that's why he's referring to it as the "International" One XL).
The hboot versions are different from ours (I've only seen 2.10 so far), but one person had said that they had successfully loaded one of our ROMs onto one of these things.
Chances are it's safe, but I wouldn't want to risk it. There's very little information available about this model, and I'm not game enough to give advice on it.
Sent from my Evita

timmaaa said:
I did some research on this a few days ago. He has the Evita_UTL, which is another version of the dual-core found in the middle east (I'm guessing that's why he's referring to it as the "International" One XL).
The hboot versions are different from ours (I've only seen 2.10 so far), but one person had said that they had successfully loaded one of our ROMs onto one of these things.
Chances are it's safe, but I wouldn't want to risk it. There's very little information available about this model, and I'm not game enough to give advice on it.
Sent from my Evita
Click to expand...
Click to collapse
Thanks! Had no idea about this. Very good to know. I agree with the not risking our roms on it. there could be a key hardware difference.

exad said:
Thanks! Had no idea about this. Very good to know. I agree with the not risking our roms on it. there could be a key hardware difference.
Click to expand...
Click to collapse
The evita ul is actually the one x+
Check out link and look under variations
http://en.m.wikipedia.org/wiki/HTC_One_X
Sent from my HTC One XL using xda premium

The term "international version" means nothing at this point, and just a source of confusion. It was relevant in the first few months, when the dual core EVITA was only being offered in US and Canada, and the quad core ENDEAVORU was being sold in multiple countries. Now that the EVITA is available in so many countries (UK, Australia, Germany, Hong Kong, Singapore, and more), it can decidedly be considered "international". Sure, there is the "XL" designation (used for all the dual core EVITA versions outside of North America). But that just adds to the confusion.
Many folks here still use the term "international" to be synonymous to the ENDEAVORU. But its much less confusing to stick with the the code names (EVITA vs. ENDEAVORU) and get away from "international" and "not international" (non-international, un-international?).

31ken31 said:
The evita ul is actually the one x+
Check out link and look under variations
http://en.m.wikipedia.org/wiki/HTC_One_X
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
That's the Evitare UL, but this model is the Evita UTL.
Sent from my Evita
---------- Post added at 01:49 AM ---------- Previous post was at 01:44 AM ----------
redpoint73 said:
Sure, there is the "XL" designation (used for all the dual core EVITA versions outside of North America). But that just adds to the confusion.
Click to expand...
Click to collapse
I personally think it's the opposite, I think it's the "incorrect" branding used by North American carriers that's caused all the confusion. The model is known as the One XL everywhere in the world except for North America, where the carriers decided to screw with the model designation for marketing reasons.
Sent from my Evita

timmaaa said:
I personally think it's the opposite, I think it's the "incorrect" branding used by North American carriers that's caused all the confusion. The model is known as the One XL everywhere in the world except for North America, where the carriers decided to screw with the model designation for marketing reasons.
Click to expand...
Click to collapse
My point was that the usage of the names X and XL for the same device (EVITA) adds to the confusion, not that XL is "incorrect".

redpoint73 said:
My point was that the usage of the names X and XL for the same device (EVITA) adds to the confusion, not that XL is "incorrect".
Click to expand...
Click to collapse
Cool, I guess I misinterpreted what you said, sorry for the confusion.
Sent from my Evita

timmaaa said:
Cool, I guess I misinterpreted what you said, sorry for the confusion.
Sent from my Evita
Click to expand...
Click to collapse
Well, lets just all agree to call them evita and endeavor from here on out to avoid any confusion going forward.

exad said:
Well, lets just all agree to call them evita and endeavor from here on out to avoid any confusion going forward.
Click to expand...
Click to collapse
A while back, a user (forgot who) recommended using the code names (ENDEAVORU versus EVITA) in the two respective forum section titles, instead of the current naming convention (HTC One X versus AT&T, Rogers etc.). I thought this was a fantastic idea. But apparently the mods didn't agree, and nothing ever changed..

redpoint73 said:
A while back, a user (forgot who) recommended using the code names (ENDEAVORU versus EVITA) in the two respective forum section titles, instead of the current naming convention (HTC One X versus AT&T, Rogers etc.). I thought this was a fantastic idea. But apparently the mods didn't agree, and nothing ever changed..
Click to expand...
Click to collapse
I think it's a great idea too. Maybe the only problem with it is that your average n00b looking to root is most likely not aware of the code names? Therefore making it difficult for them to find the correct forum.
EDIT: in saying that, it's already difficult for em to find the correct forum with the current naming format.
Sent from my Evita

redpoint73 said:
A while back, a user (forgot who) recommended using the code names (ENDEAVORU versus EVITA) in the two respective forum section titles, instead of the current naming convention (HTC One X versus AT&T, Rogers etc.). I thought this was a fantastic idea. But apparently the mods didn't agree, and nothing ever changed..
Click to expand...
Click to collapse
It is a good idea. Would also force people to check there bootloader prior to doing anything which would prevent some bricking.
I will be sure to refer to them this way from here on out though if you guys do. Any Regular helpers on here who happen to see these posts, might be good to do the same.

exad said:
It is a good idea. Would also force people to check there bootloader prior to doing anything which would prevent some bricking.
I will be sure to refer to them this way from here on out though if you guys do. Any Regular helpers on here who happen to see these posts, might be good to do the same.
Click to expand...
Click to collapse
Gotcha, evita it is

Bricked? - No OS
I am in a similar situation. HTC One X Evita. Unlocked. HBoot 2.14. TWRP Recovery. No OS (yes it was wiped). I can see directories in TWRP. I can get to Bootloader and into Recovery. I was able to see /sdcard/ if I mounted it in TWRP. Now I haven't seen it for a few hours.
According to my son, he was able to copy (not adb sideload) CM10.1 onto /sdcard/ and tried to install it. After this it just bootlooped on the CM logo. He wiped it again (then bought a Nexus 4 haha). I left my company and want to use this phone as my daily dialer.
Is it bricked? How do I get anything onto the phone if the laptop won't recognize it to run Fastboot or ADB? Hopefully a point in the right direction will help. I have 24 tabs open of discussion that are similar but haven't helped.

[Q] How to determine carrier after changing CID?

Hi,
I've got SuperCID and now I wonder if there's a way to determine what carrier the device is.
This is in order to know which RUU I should install.
Code:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-22222222
HBOOT-1.11.0000
RADIO-0.18a.32.09.01_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
Thanks,
Shahar

I don't think there's a way.. Is there no carrier logo on the phone?
Sent from my One X using xda app-developers app

exad said:
I don't think there's a way.. Is there no carrier logo on the phone?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
There is no carrier logo. Just htc and beatsaudio. It was purchased in Canada. I guess that I should just leave it.
Or is there some way of knowing what my CID was before I changed it... Is it stored in some other place? Is it stored in some app that I have a backup of? Is it stored in some place by some procedure that I may have run in the past?

Can HTC tell from the IMEI, perhaps? Or other details? From the baseband?

mightyiam said:
Can HTC tell from the IMEI, perhaps? Or other details? From the baseband?
Click to expand...
Click to collapse
typically SuperCID changes the CID in /dev/block/mmcblk0p4 or /dev/block/mmcblk0p5 It's possible that it's still within one of those files if you pull them both and have a look with a hex editor. I think it's stored in another file too.. maybe mmcblk0p6?
I don't know if HTC can tell from the IMEI but they might.

Search in the forum the radio and hboot doesn't seem to me like official AT&T it looks like telus or rogers I'm almost sure that from that information (hboot and radio) u can know the last ruu that had been run on the phone therefore the company of it. Imei it's a good one too but instead of HTC try calling different companies. Carriers need imei don't think HTC does so why keep them. Good luck
Sent from my HTC One XL using xda premium

If all that was done is supercid and no changing of firmware files, this phones hboot/radio/dsp matches Telus 1.91.661.4.

Curious, say he had the Rog111, could he change it to Tel111 and then RUU with a Telus rom?
WR
Sent off my Black OneXL

WarRaven said:
Curious, say he had the Rog111, could he change it to Tel111 and then RUU with a Telus rom?
Click to expand...
Click to collapse
Changing ROGER001 to TELUS001 should be enough also those 2 devices share the same MID PJ8310000 which would also help to get past checks.
Devices from other regions with different MID's may fail if you only changed the CID.

I see, sounds doable.
I may do this with my other One XL.
WR
Sent off my Black OneXL

WarRaven said:
I see, sounds doable.
I may do this with my other One XL.
Click to expand...
Click to collapse
Most would just supercid and s-off. Then any RUU from any region will typically work.

K2_U RUU for ASIA_WWE(CID:HTC__044)

RUU_K2_U_ICS_40_hTC_Asia_WWE_1.17.707.8_Radio_0.12.40.00.06_10.45.40.11L_release_301510_signed.exe
I change my CID to HTC__044, RUU success, 4.1.2 update success.
Hope this RUU can help somebody who bought k2_u from china or etc....

thank you @snailpon
I'm currently mirroring this to help someone, I'll link this thread so they can also click thanks

will this work also for k2_ul?

No it's K2_U only
!#quote my post if you want to get my attention more quickly

You could always port it hahaha.... Seriously though... Don't
Although, today I will be taking a closer look at the partitions on each device to see which are actually universally compatible. And yes, my phone shall be the guniea pig if my findings bring confidence. If so, it may in some ways be possible to use these other variants - with modifications of course lol.
Sent from my C525c using XDA Premium 4 mobile app