SuperCID Guide

Search This thread

fkofilee

Senior Member
I Am Not Responsible For Breaking Your Device, Take Your Own Risks ^__^

Hi Folks

Please Follow Below;

To Set SuperCID Or Change Any CID For That Fact;

1. Check you are S-OFF; Follow Moonshine OR Revolutionaries Guide.
2. Reboot Into Bootloader & Check You Are Fastboot USB
3. Type As Below

Code:
fastboot oem writecid 11111111

(Or whatever CID you want to have from the list in the second post)

4. Reboot Into Bootloader Again & Check You Are Fastboot USB
5. Check You Have Your Chosen CID;

Code:
fastboot getvar cid

(This Should Confirm The CID you chose from the list in the second post)

6. Reboot Back To Android By Typing

Code:
fastboot reboot

Files attached in post should anyone be a bit lost :)
 

Attachments

  • Tools.zip
    252.7 KB · Views: 2,617

fkofilee

Senior Member
CID List

Description CID
ALL 11111111
BM BM___001
Bouygues-Telecom BOUYG201
Brightstar-SPA BSTAR301
Entel BSTAR306
Tigo BSTAR307
Movistar BSTAR308
Brightstar-PTB BSTAR502
Chunghwa-Taiwan CHT__601
ATT CWS__001
CA_Dave DAVE_001
DCM DOCOM801
DOPOD DOPOD701
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-UK H3G__001
H3G-ROI H3G__003
H3G-AT H3G__106
H3G-Italy H3G__402
H3G-DAN H3G__F05
H3G-SWE H3G__G04
HTC-WWE HTC__001
VODA-Africa-South HTC__016
HTC-Australia HTC__023
HTC-EastEurope HTC__032
HTC-Asia-SEA HTC__037
AirTel-India HTC__038
HTC-India HTC__038
HTC-Asia-SEA-WWE HTC__044
HTC-Tesco HTC__052
HTC Israel HTC__K18
HTC-GER HTC__102
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-FRA-NRJ HTC__249
HTC-SPA HTC__304
HTC-ITA HTC__405
HTC-PTG HTC__506
TWM-TW HTC__621
Asia-HK-CHT HTC__622
HTC-Russia HTC__A07
HTC-Poland HTC__B25
HTC-Czech HTC__C24
HTC-Dutch HTC__E11
HTC-BE HTC__E41
HTC-Denmark HTC__F08
HTC-Sweden HTC__G09
HTC-Norway HTC__H10
HTC-GCC (Gulf Cooperation) HTC__J15
HTC-Turkey HTC__M27
HTC-ELL HTC__N34
HTC-Nor HTC__Y13
Open-Channel HTCCN701
CT HTCCN702
CU HTCCN703
Hutch-Australia HUTCH001
O2-UK O2___001
O2-DE O2___102
Optus-Australia OPTUS001
ORANGE-UK ORANG001
ORANGE-SK ORANG006
ORANGE-PO ORANG008
ORANGE-BE ORANG012
ORANGE-CH-GER ORANG104
ORANGE-AT ORANG113
ORANGE-French ORANG202
ORANGE-CH-FRA ORANG203
ORANGE-ES ORANG309
ORANGE-PL ORANGB10
Rogers ROGER001
SKT_KR SKT__901
SMC-Voda-HK SMCVD001
HTC-Singapore HTC__044
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMNL T-MOB003
TMCZ T-MOB004
TMUK T-MOB005
TMHR T-MOB006
TMH T-MOB007
TMSK T-MOB008
Era T-MOB009
TMUS T-MOB010
TMD T-MOB101
TMA T-MOB102
TMMK T-MOBL11
CA_Videotron VIDEO001
VIRGIN-UK VIRGI001
VODA-UK VODAP001
VODA-Greece VODAP006
VODA-Swisscom-WWE VODAP015
VODA-Ireland VODAP019
VODA-Australia VODAP021
VODA-New-Zealand VODAP022
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-Germany VODAP102
VODA-Swisscom-DE VODAP110
VODA-Mobilkom VODAP120
VODA-DE VODAP129
VODA-SFR VODAP203
VODA-Swisscom-FR VODAP212
VODA-Spain VODAP304
VODA-Italy VODAP405
VODA-Swisscom-IT VODAP416
VODA-MTS-RUS VODAPA30
VODA-Portugal VODAPD18
VODA-Netherland VODAPE17
VODA-TR VODAPM27
HTC Australia HTC__039
 
Last edited:

wzu7

Senior Member
Apr 13, 2011
1,065
214
Google Earth
Mine is CID-HTC_044
It's for HTC-Asia-SEA-WWE HTC__044 or HTC-Singapore HTC__044 ?
My RUU before using HTC-Asia-SEA-WWE ! !?
 

dryspuri

Senior Member
Oct 15, 2009
743
86
Chennai
Good Guide, I have a question though, now we have s-off and supercid, can we put any cid on our phone for eg my phone came with H3G__001, can I put command for changing it to HTC__001
 

he_stheone64

Senior Member
Aug 1, 2008
5,033
10,991
Düsseldorf
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.

Try yourself in adb with:

adb shell getprop "ro.cid"

So old CID still hides in one of these...

PHP:
179        0   30535680 mmcblk0
 179        1        128 mmcblk0p1
 179        2        256 mmcblk0p2
 179        3     130671 mmcblk0p3
 179        4          1 mmcblk0p4
 179        5         16 mmcblk0p5
 179        6        256 mmcblk0p6
 179        7      15577 mmcblk0p7
 179        8        256 mmcblk0p8
 179        9       1024 mmcblk0p9
 179       10        256 mmcblk0p10
 179       11       2048 mmcblk0p11
 179       12       2080 mmcblk0p12
 179       13       5120 mmcblk0p13
 179       14       1024 mmcblk0p14
 179       15       1024 mmcblk0p15
 179       16      61441 mmcblk0p16
 179       17       8190 mmcblk0p17
 179       18      32768 mmcblk0p18
 179       19       1022 mmcblk0p19
 179       20       4096 mmcblk0p20
 179       21       4096 mmcblk0p21
 179       22      20480 mmcblk0p22
 179       23          4 mmcblk0p23
 179       24        256 mmcblk0p24
 179       25         16 mmcblk0p25
 179       26       1280 mmcblk0p26
 179       27         64 mmcblk0p27
 179       28       1024 mmcblk0p28
 179       29      98727 mmcblk0p29
 179       30      54270 mmcblk0p30
 179       31      76800 mmcblk0p31
 179       32      98303 mmcblk0p32
 179       33      16384 mmcblk0p33
 179       34      16383 mmcblk0p34
 179       35    1900543 mmcblk0p35
 179       36     655359 mmcblk0p36
 179       37   27262976 mmcblk0p37
 
Last edited:

fkofilee

Senior Member
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.

Try yourself in adb with:

adb shell getprop "ro.cid"

So old CID still hides in one of these...

PHP:
179        0   30535680 mmcblk0
 179        1        128 mmcblk0p1
 179        2        256 mmcblk0p2
 179        3     130671 mmcblk0p3
 179        4          1 mmcblk0p4
 179        5         16 mmcblk0p5
 179        6        256 mmcblk0p6
 179        7      15577 mmcblk0p7
 179        8        256 mmcblk0p8
 179        9       1024 mmcblk0p9
 179       10        256 mmcblk0p10
 179       11       2048 mmcblk0p11
 179       12       2080 mmcblk0p12
 179       13       5120 mmcblk0p13
 179       14       1024 mmcblk0p14
 179       15       1024 mmcblk0p15
 179       16      61441 mmcblk0p16
 179       17       8190 mmcblk0p17
 179       18      32768 mmcblk0p18
 179       19       1022 mmcblk0p19
 179       20       4096 mmcblk0p20
 179       21       4096 mmcblk0p21
 179       22      20480 mmcblk0p22
 179       23          4 mmcblk0p23
 179       24        256 mmcblk0p24
 179       25         16 mmcblk0p25
 179       26       1280 mmcblk0p26
 179       27         64 mmcblk0p27
 179       28       1024 mmcblk0p28
 179       29      98727 mmcblk0p29
 179       30      54270 mmcblk0p30
 179       31      76800 mmcblk0p31
 179       32      98303 mmcblk0p32
 179       33      16384 mmcblk0p33
 179       34      16383 mmcblk0p34
 179       35    1900543 mmcblk0p35
 179       36     655359 mmcblk0p36
 179       37   27262976 mmcblk0p37

Well fella you're wrong on that one ^__^

Just done it and it came back "11111111"
However you are right and it has been an issue before :/
 

Attachments

  • Screenshot_1.jpg
    Screenshot_1.jpg
    45 KB · Views: 1,225

gianton

Inactive Recognized Contributor
Feb 5, 2009
12,021
9,953
Thessaloniki
Xiaomi Mi Mix 2S
Xiaomi Mi 9
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.

Try yourself in adb with:

adb shell getprop "ro.cid"

So old CID still hides in one of these...

PHP:
179        0   30535680 mmcblk0
 179        1        128 mmcblk0p1
 179        2        256 mmcblk0p2
 179        3     130671 mmcblk0p3
 179        4          1 mmcblk0p4
 179        5         16 mmcblk0p5
 179        6        256 mmcblk0p6
 179        7      15577 mmcblk0p7
 179        8        256 mmcblk0p8
 179        9       1024 mmcblk0p9
 179       10        256 mmcblk0p10
 179       11       2048 mmcblk0p11
 179       12       2080 mmcblk0p12
 179       13       5120 mmcblk0p13
 179       14       1024 mmcblk0p14
 179       15       1024 mmcblk0p15
 179       16      61441 mmcblk0p16
 179       17       8190 mmcblk0p17
 179       18      32768 mmcblk0p18
 179       19       1022 mmcblk0p19
 179       20       4096 mmcblk0p20
 179       21       4096 mmcblk0p21
 179       22      20480 mmcblk0p22
 179       23          4 mmcblk0p23
 179       24        256 mmcblk0p24
 179       25         16 mmcblk0p25
 179       26       1280 mmcblk0p26
 179       27         64 mmcblk0p27
 179       28       1024 mmcblk0p28
 179       29      98727 mmcblk0p29
 179       30      54270 mmcblk0p30
 179       31      76800 mmcblk0p31
 179       32      98303 mmcblk0p32
 179       33      16384 mmcblk0p33
 179       34      16383 mmcblk0p34
 179       35    1900543 mmcblk0p35
 179       36     655359 mmcblk0p36
 179       37   27262976 mmcblk0p37

Yes I did what you said and it shows my old CID. Maybe this file stayed there and after a ROM update will go away.
 

RubyRhod62

Senior Member
Jan 21, 2011
101
15
Arras
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.

Try yourself in adb with:

adb shell getprop "ro.cid"

So old CID still hides in one of these...

PHP:
179        0   30535680 mmcblk0
 179        1        128 mmcblk0p1
 179        2        256 mmcblk0p2
 179        3     130671 mmcblk0p3
 179        4          1 mmcblk0p4
 179        5         16 mmcblk0p5
 179        6        256 mmcblk0p6
 179        7      15577 mmcblk0p7
 179        8        256 mmcblk0p8
 179        9       1024 mmcblk0p9
 179       10        256 mmcblk0p10
 179       11       2048 mmcblk0p11
 179       12       2080 mmcblk0p12
 179       13       5120 mmcblk0p13
 179       14       1024 mmcblk0p14
 179       15       1024 mmcblk0p15
 179       16      61441 mmcblk0p16
 179       17       8190 mmcblk0p17
 179       18      32768 mmcblk0p18
 179       19       1022 mmcblk0p19
 179       20       4096 mmcblk0p20
 179       21       4096 mmcblk0p21
 179       22      20480 mmcblk0p22
 179       23          4 mmcblk0p23
 179       24        256 mmcblk0p24
 179       25         16 mmcblk0p25
 179       26       1280 mmcblk0p26
 179       27         64 mmcblk0p27
 179       28       1024 mmcblk0p28
 179       29      98727 mmcblk0p29
 179       30      54270 mmcblk0p30
 179       31      76800 mmcblk0p31
 179       32      98303 mmcblk0p32
 179       33      16384 mmcblk0p33
 179       34      16383 mmcblk0p34
 179       35    1900543 mmcblk0p35
 179       36     655359 mmcblk0p36
 179       37   27262976 mmcblk0p37

I did what you say, but before being S-OFF and super-cid-ed, i was with HTC__203 CID.

Now verified in fastboot and with your method, both are giving me the same result CID 11111111.

I've to say that i'm on ARHD10.1. Does it affect the manner to obtain the SUPER-CID?...Really don't know.
 

ross_ctr

Senior Member
Jul 12, 2010
98
7
Heathfield
Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.

Try yourself in adb with:

adb shell getprop "ro.cid"

So old CID still hides in one of these...

PHP:
179        0   30535680 mmcblk0
 179        1        128 mmcblk0p1
 179        2        256 mmcblk0p2
 179        3     130671 mmcblk0p3
 179        4          1 mmcblk0p4
 179        5         16 mmcblk0p5
 179        6        256 mmcblk0p6
 179        7      15577 mmcblk0p7
 179        8        256 mmcblk0p8
 179        9       1024 mmcblk0p9
 179       10        256 mmcblk0p10
 179       11       2048 mmcblk0p11
 179       12       2080 mmcblk0p12
 179       13       5120 mmcblk0p13
 179       14       1024 mmcblk0p14
 179       15       1024 mmcblk0p15
 179       16      61441 mmcblk0p16
 179       17       8190 mmcblk0p17
 179       18      32768 mmcblk0p18
 179       19       1022 mmcblk0p19
 179       20       4096 mmcblk0p20
 179       21       4096 mmcblk0p21
 179       22      20480 mmcblk0p22
 179       23          4 mmcblk0p23
 179       24        256 mmcblk0p24
 179       25         16 mmcblk0p25
 179       26       1280 mmcblk0p26
 179       27         64 mmcblk0p27
 179       28       1024 mmcblk0p28
 179       29      98727 mmcblk0p29
 179       30      54270 mmcblk0p30
 179       31      76800 mmcblk0p31
 179       32      98303 mmcblk0p32
 179       33      16384 mmcblk0p33
 179       34      16383 mmcblk0p34
 179       35    1900543 mmcblk0p35
 179       36     655359 mmcblk0p36
 179       37   27262976 mmcblk0p37

Mine is saying original CID too, O2___001
 

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    Supercid guide

    Don`t want to ruin the Super CID party, but whether we have trie Super CID or not, remains to be seen. It`s true, that both by hex editing the partition or fastboot command now we get Super CID in fastboot, but what is interesting, that when double checking via adb in live system with adb shell getprop "ro.cid", you will still get your original CID. So it seems CID is stored in 2 different locations now and that fastboot forcing the new CID does not fully finish the task.

    Try yourself in adb with:

    adb shell getprop "ro.cid"

    You do this at your own risk!!! This could turn your new phone into a very expensive paperweight!!! If you don't know how to do it or are uncomfortable DON'T DO IT!!!

    You need ADB and an understanding of how to use it and have a rooted device. You will also need a hex editor like HxD.

    FIRST ONE is to do this here: Change CID

    1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.

    2. Type "su" and hit enter. You now have root privileges.

    3. Next type "dd if=/dev/block/mmcblk0p19 of=/sdcard/mmcblk0p19" and hit enter. This will dump the partition to your sdcard.

    4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.

    5. type "adb pull /sdcard/mmcblk0p19" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!

    6. Open the file (mmcblk0p19) with your hex editor.

    7. Look for offset 00000000 and you should see your CID (see picture).

    8. Change CID to 11111111 and save the file as mmcblk0p19MOD. This will give you SuperCID as well. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!

    9. Now go back to your command prompt and type "adb push mmcblk0p19MOD /sdcard/mmcblk0p19MOD" and hit enter.

    10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.

    11. Type "dd if=/sdcard/mmcblk0p19MOD of=/dev/block/mmcblk0p19" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".

    12. Next type "fastboot reboot" and hit enter. After the phone rebooted open command line and type "adb adb shell getprop ro.cid" and you
    can see the supercid (see picture).
    24
    I Am Not Responsible For Breaking Your Device, Take Your Own Risks ^__^

    Hi Folks

    Please Follow Below;

    To Set SuperCID Or Change Any CID For That Fact;

    1. Check you are S-OFF; Follow Moonshine OR Revolutionaries Guide.
    2. Reboot Into Bootloader & Check You Are Fastboot USB
    3. Type As Below

    Code:
    fastboot oem writecid 11111111

    (Or whatever CID you want to have from the list in the second post)

    4. Reboot Into Bootloader Again & Check You Are Fastboot USB
    5. Check You Have Your Chosen CID;

    Code:
    fastboot getvar cid

    (This Should Confirm The CID you chose from the list in the second post)

    6. Reboot Back To Android By Typing

    Code:
    fastboot reboot

    Files attached in post should anyone be a bit lost :)
    14
    CID List

    Description CID
    ALL 11111111
    BM BM___001
    Bouygues-Telecom BOUYG201
    Brightstar-SPA BSTAR301
    Entel BSTAR306
    Tigo BSTAR307
    Movistar BSTAR308
    Brightstar-PTB BSTAR502
    Chunghwa-Taiwan CHT__601
    ATT CWS__001
    CA_Dave DAVE_001
    DCM DOCOM801
    DOPOD DOPOD701
    Fastweb-IT FASTW401
    GOOGLE GOOGL001
    H3G-UK H3G__001
    H3G-ROI H3G__003
    H3G-AT H3G__106
    H3G-Italy H3G__402
    H3G-DAN H3G__F05
    H3G-SWE H3G__G04
    HTC-WWE HTC__001
    VODA-Africa-South HTC__016
    HTC-Australia HTC__023
    HTC-EastEurope HTC__032
    HTC-Asia-SEA HTC__037
    AirTel-India HTC__038
    HTC-India HTC__038
    HTC-Asia-SEA-WWE HTC__044
    HTC-Tesco HTC__052
    HTC Israel HTC__K18
    HTC-GER HTC__102
    HTC-FRA HTC__203
    HTC-FRA-Bouygues HTC__247
    HTC-FRA-NRJ HTC__249
    HTC-SPA HTC__304
    HTC-ITA HTC__405
    HTC-PTG HTC__506
    TWM-TW HTC__621
    Asia-HK-CHT HTC__622
    HTC-Russia HTC__A07
    HTC-Poland HTC__B25
    HTC-Czech HTC__C24
    HTC-Dutch HTC__E11
    HTC-BE HTC__E41
    HTC-Denmark HTC__F08
    HTC-Sweden HTC__G09
    HTC-Norway HTC__H10
    HTC-GCC (Gulf Cooperation) HTC__J15
    HTC-Turkey HTC__M27
    HTC-ELL HTC__N34
    HTC-Nor HTC__Y13
    Open-Channel HTCCN701
    CT HTCCN702
    CU HTCCN703
    Hutch-Australia HUTCH001
    O2-UK O2___001
    O2-DE O2___102
    Optus-Australia OPTUS001
    ORANGE-UK ORANG001
    ORANGE-SK ORANG006
    ORANGE-PO ORANG008
    ORANGE-BE ORANG012
    ORANGE-CH-GER ORANG104
    ORANGE-AT ORANG113
    ORANGE-French ORANG202
    ORANGE-CH-FRA ORANG203
    ORANGE-ES ORANG309
    ORANGE-PL ORANGB10
    Rogers ROGER001
    SKT_KR SKT__901
    SMC-Voda-HK SMCVD001
    HTC-Singapore HTC__044
    TELEF-Spain TELEF301
    Telstra TELST001
    TELUS TELUS001
    TIM-Italy TIM__401
    TMNL T-MOB003
    TMCZ T-MOB004
    TMUK T-MOB005
    TMHR T-MOB006
    TMH T-MOB007
    TMSK T-MOB008
    Era T-MOB009
    TMUS T-MOB010
    TMD T-MOB101
    TMA T-MOB102
    TMMK T-MOBL11
    CA_Videotron VIDEO001
    VIRGIN-UK VIRGI001
    VODA-UK VODAP001
    VODA-Greece VODAP006
    VODA-Swisscom-WWE VODAP015
    VODA-Ireland VODAP019
    VODA-Australia VODAP021
    VODA-New-Zealand VODAP022
    VODA-Proximus VODAP024
    VODA-SA VODAP026
    VODA-Germany VODAP102
    VODA-Swisscom-DE VODAP110
    VODA-Mobilkom VODAP120
    VODA-DE VODAP129
    VODA-SFR VODAP203
    VODA-Swisscom-FR VODAP212
    VODA-Spain VODAP304
    VODA-Italy VODAP405
    VODA-Swisscom-IT VODAP416
    VODA-MTS-RUS VODAPA30
    VODA-Portugal VODAPD18
    VODA-Netherland VODAPE17
    VODA-TR VODAPM27
    HTC Australia HTC__039
    4
    That has nothing to do with the S-Off method, HTC just stores CID info now in 2 partitions compared to previous devices, where it`s only been in one (usually in mmcblk0p4). So the OEM writecid only changes CID info in mmcblk0p4, but on ONE it`s also stored in mmcblk0p19.

    Whether both methods are required is easy to test, we only need someone who only changed mmcblk0p4 so far, willing to flash a RUU, that does not match his original CID. If it flashes fine, then we dont need the extra hex edit of mmcblk0p19. If it does not, the tester needs to hex edit mmcblk0p19 and try to flash the RUU again. Did not follow the thread yesterday, maybe thats done by now anyway.

    I have an AT&T branded One 64GB with original CID of CWS__001. I did revone s-off method, fastboot write CID of 11111111, then sucessfully flashed the 1.29.1540.16 developer edition ruu. I did not do any hex edit.
    4
    This method worked. I did it all from terminal emulator. After reboot I even had the international data icons.
    View attachment 2027790

    Sent from my HTC One using Tapatalk 2

    It looks like that CID is used for only data icons. Well maybe other things too but it doesn't have anything to do with changing firmware. I have an ATT One and used the command oem write cid 11111111 and i just successfully installed the dev edition ruu. When checking CID via cidgetter or getprop "ro.cid" command i still get the att CWS__001 cid. So actually there is no need to risk bricking your phone by hex editing unless you want different data icons. I think a flash-able zip with the correct icons would be way safer :rolleyes:

    AGAIN i successfully installed different firmware while having two different CIDs... No need to hex edit and change your cid if you are only looking to change firmware!