Super cid: 11111111

Search This thread

shootind5nukes

Senior Member
May 23, 2010
341
196
This is not my work but I did not see it in the dev section so I thought this would be a perfect repost. I read this in the HTC one X thread and I followed it EXACTLY as wrote and it worked for the One S. I have the Tmo version.


http://xdaforums.com/showthread.php?p=26516911#post26516911

This is not my work.

My phone is only unlocked via HTCdev and is NOT s-off and it worked flawlessly.
 
Last edited:

shootind5nukes

Senior Member
May 23, 2010
341
196
travis@HighVoltage ~ $ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
shell@android:/ $ su
shell@android:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
shell@android:/ # exit
shell@android:/ $ exit
travis@HighVoltage ~ $ adb pull /sdcard/mmcblk0p4
12 KB/s (1024 bytes in 0.078s)
travis@HighVoltage ~ $ adb reboot-bootloader
travis@HighVoltage ~ $ fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.005s]
finished. total time: 0.005s
travis@HighVoltage ~ $ fastboot reboot
travis@HighVoltage ~ $ adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
8 KB/s (1024 bytes in 0.112s)
travis@HighVoltage ~ $ adb shell
shell@android:/ $ su
shell@android:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.365 secs (2805 bytes/sec)
shell@android:/ # exit
shell@android:/ $ exit
travis@HighVoltage ~ $ adb reboot-bootloader
travis@HighVoltage ~ $ fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.005s]
finished. total time: 0.005s
travis@HighVoltage ~ $ fastboot reboot
 
Last edited:

benjamin.j.goodwin

Inactive Recognized Developer
Aug 28, 2011
3,073
4,999
Northampton
Google Pixel 4 XL
travis@HighVoltage ~ $ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
shell@android:/ $ su
shell@android:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
shell@android:/ # exit
shell@android:/ $ exit
travis@HighVoltage ~ $ adb pull /sdcard/mmcblk0p4
12 KB/s (1024 bytes in 0.078s)
travis@HighVoltage ~ $ adb reboot-bootloader
travis@HighVoltage ~ $ fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.005s]
finished. total time: 0.005s
travis@HighVoltage ~ $ fastboot reboot
travis@HighVoltage ~ $ adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
8 KB/s (1024 bytes in 0.112s)
travis@HighVoltage ~ $ adb shell
shell@android:/ $ su
shell@android:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.365 secs (2805 bytes/sec)
shell@android:/ # exit
shell@android:/ $ exit
travis@HighVoltage ~ $ adb reboot-bootloader
travis@HighVoltage ~ $ fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.005s]
finished. total time: 0.005s
travis@HighVoltage ~ $ fastboot reboot

Hey mate, you tried flashing a different RUU using this?

Sent from my HTC One S using xda premium
 
  • Like
Reactions: kwtf

dc211

Senior Member
Jul 21, 2010
572
203
Awesome I knew when I saw the alternate method to flash a radio worked this wouldn't be far along. I'd expect we'll get a few more goodies from type of method soon.

Also, I knew it was great news when I saw the ATT One X specs. It's so close to the One S we'll be able to benefit from it's development for the entire life cycle of the One S

---------- Post added at 07:44 PM ---------- Previous post was at 07:15 PM ----------

This was quick and easy. My TMOUS phone is now 11111111. Just want to point out to others that you should stop at step 11.
 

jriv

Senior Member
Apr 13, 2010
1,810
187
Princeton,MN
Awesome I knew when I saw the alternate method to flash a radio worked this wouldn't be far along. I'd expect we'll get a few more goodies from type of method soon.

Also, I knew it was great news when I saw the ATT One X specs. It's so close to the One S we'll be able to benefit from it's development for the entire life cycle of the One S

---------- Post added at 07:44 PM ---------- Previous post was at 07:15 PM ----------

This was quick and easy. My TMOUS phone is now 11111111. Just want to point out to others that you should stop at step 11.

I agree I think the roms will be interchangeable just like the att and tmobile gs2 are interchangeable

sent from a guy living in a van down by the river
 

wardy

Senior Member
Jun 8, 2005
440
11
So you should be able to de brand this way . Just Change the CID to HTC__001 then flash lates RUU . Correct?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 62
    This is not my work but I did not see it in the dev section so I thought this would be a perfect repost. I read this in the HTC one X thread and I followed it EXACTLY as wrote and it worked for the One S. I have the Tmo version.


    http://xdaforums.com/showthread.php?p=26516911#post26516911

    This is not my work.

    My phone is only unlocked via HTCdev and is NOT s-off and it worked flawlessly.
    14
    travis@HighVoltage ~ $ adb shell
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    shell@android:/ $ su
    shell@android:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
    2+0 records in
    2+0 records out
    1024 bytes transferred in 0.002 secs (512000 bytes/sec)
    shell@android:/ # exit
    shell@android:/ $ exit
    travis@HighVoltage ~ $ adb pull /sdcard/mmcblk0p4
    12 KB/s (1024 bytes in 0.078s)
    travis@HighVoltage ~ $ adb reboot-bootloader
    travis@HighVoltage ~ $ fastboot oem readcid
    ...
    (bootloader) cid: T-MOB010
    OKAY [ 0.005s]
    finished. total time: 0.005s
    travis@HighVoltage ~ $ fastboot reboot
    travis@HighVoltage ~ $ adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
    8 KB/s (1024 bytes in 0.112s)
    travis@HighVoltage ~ $ adb shell
    shell@android:/ $ su
    shell@android:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
    2+0 records in
    2+0 records out
    1024 bytes transferred in 0.365 secs (2805 bytes/sec)
    shell@android:/ # exit
    shell@android:/ $ exit
    travis@HighVoltage ~ $ adb reboot-bootloader
    travis@HighVoltage ~ $ fastboot oem readcid
    ...
    (bootloader) cid: 11111111
    OKAY [ 0.005s]
    finished. total time: 0.005s
    travis@HighVoltage ~ $ fastboot reboot
    9
    no you don't so check it out before you do it. duh. I'm unlocked via htcdev but not s-off. Like I said it worked on my One S and you know the ONE s hasn't recieved s-off has it. Look into stuff a little better before you tare it down.
    5
    I am not sure if it is really an issue, i think it may just be, because i did not switch ROM after switching CID. The original CID was HTC__102 and the phone was from 1&1 (as most german HTC One S as it looks like).
    It might just be, the language Tables got messed up from changing the CID but not the actual ROM. Like, the first part of the language setting referring to what is in the ROM and the second part referring to what the CID suggests there should be in that field. e.g. like: German (united Kingdom), where the "German" field stems from what is in the ROM and the "(united Kingdom)" part is what the CID suggests should be in that table. Or: if it was a UK ROM, it would then probably read "English (united Kingdom)" because the same table would then contain a language matching the CID. The CID "HTC__001" is HTC WWE (no specific carrier), the CID "HTC__102" is HTC Germany (no specific Carrier) (Source), so the packaged languages might differ...
    Or something like it. Dunno.

    I put all the CID's into an Excel-Sheet for easy copy/paste or as a backup.
    Also i thought, if there is new CID's turning up, someone could add them, also, there is three CID's missing in the list. Maybe someone could complete it?
    3
    error [159] image error
    ruu 3.16

    i know i have supercid and relocked bootloader. used a tmo ruu no problem to downgrade my hboot. any pointers ?

    The newer ruus are encrypted to keep us from unpacking them and shuffling images around. The older hboots are unable to unpack the new ruu. You'll need hboot 2.15 in place to unpack and install the 3.16 ruu.

    Sent from my HTC PG09410 using Tapatalk 2