About S=Off & superCID 11111111 - HTC ChaCha

this thread(http://forum.xda-developers.com/showthread.php?t=1257776) says:
You will need to have S=Off and superCID set to 11111111 using XTC Clip.
I was going to a mobile shop and i was bought "S-OFF", i have installed CWM and root, and new rom with RU.
but i don't know what is my CID (if i have s-off, i have super cid 11111111?)
can i install radio?
thanks!

You can use CIDGetter from market to check your CID number.

thanks! i have cid 1111111

Then you're ready for anything. You can flash 1.33 then update to 1.52 then install CWM then root.

Isnt supercid what goldcard gives temorarily? (It allowed me to flash 1.33 on o2 phone. Using ruu version.
can i somehow make use of my goldcard to flash to 1.52 ota? As it doesnt update on s-on which seems toi be cid related (on or off).
Any way to get it without s-off?
Sent from my HTC ChaCha A810e using XDA App

Related

[Q] do i have to do the cid thing?

hello.
i have sensation that is s-off and rooted.
now i want to unroot and i am confused.
i know that my phone came with 1.xx.401 firmware and i have same RUU.
now, do i really need to change to supercid?
RUU will remove revolutionary and CWM and i can do secureflag3 later, right?
i don't see the point in changig cids
thanx
The Super CID is needed to downgrade the HBOOT as Revolutionary changes it to a non-standard one. You can try it without Super CID but if it doesn't work then you'll need to use it. you can then change it back to your current one before running the S-ON command
i've done it without supercid with no problems!
my phone is now stock with s-on
thanx for help!
Wasn't sure if it would work or not, nice to know you don't need it for your own RUU

Downgrade / changing CID

Dear XDA members,
I have an HTC Senstion Vodafone branded with CID: VODAPE17. I cannot use the Europe ROM to downgrade my sensation because it says that the Customer I is wrong. In order the change my CID i have to be root. I have hboot 1.27.xxx. My other senstion also had hbot 1.27.xxx but that one is not branded, so i downgraded the software to get hboot 1.117.xx and use revolutionary to hack it. My Vodafone sensation wont downgrade and i cant unlock my bootloader. I tried the Vodafone UK rom but i still get the same error of i want to downgrade.
Does anyone know where i can find the vodafone rom with hboot 1.17.xxx and CID VODAPE17?
You can s-off and root using this tool and then you can change your cid and so on.

[GUIDE] Install official ICS update using GoldCard

Very Strange that by using this method, my device remains S-OFF and UNLOCKED (!!)
And here is the guide:
A- Preparation:
- Download RUU.exe file from htcdev.com. Run it (without connecting your Desire S to the PC), proceed to Next, Next... but do not exit this app. Open folder %TMP%, search for rom.zip file, copy it to another location and rename to PG88IMG.ZIP. Now you can exit RUU app.
- GoldCardTool, download it here.
- An SD card (>1GB recommended)
B- Step-by-step:
- Insert SD card to the phone, format it.
- Connect phone to PC in Disk drive mode, don't forget to enable USB Debugging = ON.
- Run GoldCardTool.exe, press Get CID button to get CID.
- Go to http://psas.revskills.de/?q=goldcard and enter CID, press Download Goldcard to get goldcard.img file.
- Get back to GoldCardTool.exe, press Load Goldcard.img to load the file goldcard.img.
- Press Patch MMC, your SD card is now ready for goldcard.
- Copy PG88IMG.ZIP file to SD card.
- Shutdown phone and boot it into bootloader.
- Phone will start update process automatically. Don't touch it unless you see "Press Power to restart".
After this step, mine is S-OFF and UNLOCKED. So I can flash custom recovery and root easily.
Leaving you device S-OFF and unlocked after RUU has nothing to do with Goldcard.
It happaned probably because you have Alpharev hboot. RUU is bypassing flashing the hboot because Alpharev hboot has bigger version, but it flashes the rest of the RUU.
It happened to one of my friends also and we didn't use Goldcard.
Sent from my HTC Desire S using xda premium
I have hboot 2.00.0002 SHIP S-OFF
Flashing an RUU doesn't change the S-OFF, never has (not on the Desire/Sensation anyway)
Sent from my HTC One X using xda premium
EddyOS said:
Flashing an RUU doesn't change the S-OFF, never has (not on the Desire/Sensation anyway)
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It means ICS update by using Goldcard is a good way to keep the hboot unchanged.
EddyOS said:
Flashing an RUU doesn't change the S-OFF, never has (not on the Desire/Sensation anyway)
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is not true, unless you have XTC-clip S-OFFed device.
My old Desire was S-ON when I bought it. I made it S-OFF using Alpharev's tool and every time I flashed any RUU (with Goldcard) it made it S-ON again.
My current Desire S is S-OFF with XTC-clip which means permanent S-OFF, now even after RUU I am still S-OFF, but with newer hboot.
When I flashed the RUU (without any Goldcard) on my friends Desire S, which has Alpharev hboot 7.0... all the images flashed successfully except BOOT which was "Bypassed", so the Alpharev's hboot was not overridden by RUU, and the rom booted successfully.
My guess it is because it has bigger version then the on in the RUU.
dmatik said:
This is not true, unless you have XTC-clip S-OFFed device.
My old Desire was S-ON when I bought it. I made it S-OFF using Alpharev's tool and every time I flashed any RUU (with Goldcard) it made it S-ON again.
My current Desire S is S-OFF with XTC-clip which means permanent S-OFF, now even after RUU I am still S-OFF, but with newer hboot.
When I flashed the RUU (without any Goldcard) on my friends Desire S, which has Alpharev hboot 7.0... all the images flashed successfully except BOOT which was "Bypassed", so the Alpharev's hboot was not overridden by RUU, and the rom booted successfully.
My guess it is because it has bigger version then the on in the RUU.
Click to expand...
Click to collapse
I have hboot 2.00.0002 SHIP S-OFF before and after goldcard, so it is not Alpharev hboot.
I have sent my phone to repair once, so I'm not sure if it was XTC-clip S-OFF or not.
vndnguyen said:
I have hboot 2.00.0002 SHIP S-OFF before and after goldcard, so it is not Alpharev hboot.
I have sent my phone to repair once, so I'm not sure if it was XTC-clip S-OFF or not.
Click to expand...
Click to collapse
Please, get your facts straight. This guide is wrong on so many levels. You are furtherly confusing people.
mirok said:
Please, get your facts straight. This guide is wrong on so many levels. You are furtherly confusing people.
Click to expand...
Click to collapse
hi mirok, i have said that it's very strange that my device remains s-off and unlocked after updating by goldcard.
however everyone can use this guide to update ICS beside other guides.

[Q] HOX AT&T Update

Hello, I have my HTC One X of AT&T unlocked by code through AT&T. It´s Rooted and it´s Bootloader is unlocked and also has the CWM Recovery installed. Never flashed any ROM, it still have the Original ICS ROM, it´s S-ON. Can I update it manually or would I be bricking it?
I was going to follow this tuto http://www.titularesandroid.com/2013/03/actualiza-tu-htc-one-x-at-jelly-bean.html?showComment=1364530268627#c3645276792953205699 but it says that it shouldn´t have "SuperCID and S-on" I don´t have SuperCID because I legally unlocked it, my doubt is about S-on, should I be S-off? If I have to, how do you do it? Thank you.
philohtc said:
Hello, I have my HTC One X of AT&T unlocked by code through AT&T. It´s Rooted and it´s Bootloader is unlocked and also has the CWM Recovery installed. Never flashed any ROM, it still have the Original ICS ROM, it´s S-ON. Can I update it manually or would I be bricking it?
I was going to follow this tuto http://www.titularesandroid.com/2013/03/actualiza-tu-htc-one-x-at-jelly-bean.html?showComment=1364530268627#c3645276792953205699 but it says that it shouldn´t have "SuperCID and S-on" I don´t have SuperCID because I legally unlocked it, my doubt is about S-on, should I be S-off? If I have to, how do you do it? Thank you.
Click to expand...
Click to collapse
I would S-OFF. I can explain the steps I took but it may have been a bit overkill. I had a 1.09 hboot so I didn't want to take any risks. I'm on Telus which is only up to 3.17. I'm not sure how 3.18 would go as I understand AT&T has put a mechanism for checking with AT&T over the network. Nevertheless.
- I downloaded the RUU for my phone which was in my case a TELUS RUU 1.91.661.4 and then I extracted the rom from the RUU and the Hboot from the ROM and I flashed the stock Hboot.
- I Booted into the bootloader/fastboot and then I changed my CID back to default, in my case TELUS001. (I don't think you need to do this with S-OFF but it takes less than a minute to do)
- Rebooted back to bootloader/fastboot and ran the RUU
- When the RUU was done I was on ICS.
- Re-Unlocked my bootloader (I'm not on AT&T so no need for Super CID for me, was just to get S-OFF)
- Flashed TWRP
- Boot back to rom to get OTA
- After OTA was done, Booted to TWRP to root stock then nandroid backup for good measure, then flash whatever
philohtc said:
I don´t have SuperCID because I legally unlocked it,
Click to expand...
Click to collapse
SuperCID has nothing to do with SIM unlock. SIM unlock of course allows you to use the phone with another carrier's SIM. CID and SuperCID relate to the HTC firmware such as RUUs and OTAs (typically only allows you to install software intended for your carrier version).
If your phone is the AT&T version, and its bootloader unlocked it must be SuperCID. Period.
SuperCID + OTA = brick
SuperCID + RUU = brick
That is, unless you have S-off. So do the facepalm s-off if you want to RUU or OTA.
Another approach is just flash a stock rooted Jellybean ROM, or a custom ROM based on the AT&T update, such as CleanROM 6. These can be found in the Development forum section.
Get SuperCid,S-off, you are already unlocked but when you get those just ruu to the current OTA and wallah.
so philohtc are you now s-off with jb update?
Not yet, but I'm not 100% sure yet, still having doubts. Because I remember when unlocking the bootloader the CID was all in 1. So how do I put the original CID ? My steps would be the following (Please correct me if I am wrong): 1st- Facepalm S-off 2nd- SuperCID? 3rd- Update through HTC Software Device?. Please give me all the warnings so I don´t brick my phone, thank you!
Boot to bootloader/fastboot.
Do fastboot oem readcid
This will tell you your Cid
If it's 11111111 or 22222222 then proceed to S-OFF.
If not, proceed to SuperCID then S-OFF
Once your S-OFF, Run the RUU
If you want to be anal like I was, after s-off, before running the ruu, you can change your Cid back to an at&t Cid using fastboot oem writecid xxxxxxxx where the X's are the default Cid. I don't know it for at&t by heart.
Sent from my One X using xda app-developers app
exad said:
If you want to be anal like I was, after s-off, before running the ruu, you can change your Cid back to an at&t Cid using fastboot oem writecid xxxxxxxx where the X's are the default Cid. I don't know it for at&t by heart.
Click to expand...
Click to collapse
CWS__001
Appreciate that, thanks bud
Sent from my One X using xda app-developers app

[Q] Need Help Getting SuperCID with MID/CID Mismatch

Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
helpful_onlooker said:
Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
Click to expand...
Click to collapse
AFAIU it all depends on the xxx after the 3.16. in the version of the firmware, which method is likely to work with your device.
helpful_onlooker said:
Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
Click to expand...
Click to collapse
I was able to change to supercid with the same config as you have ( 3.16.401.8 and origo cid HTC__001) so it should for you. If you'll manage to supercid just get s-off useing facepalm metod. Worked for me.
Sent from my HTC One S
if you got the xxxxxxx.9 it wont work indeed.
but on the xxxxxxxx.8 supercid/facepalm method should work, i did this myself back then.
since hboot didnt change going from .8 to .9, it might be possible to reflash the ruu to get back on .8 (as you did before i presume).
but if the ota going to .9 did change something permanent its a bust.
I believe the RUU I tried flashing was HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L...
-If I go the Facepalm route, I have to SuperCID. I can't because I am unable to change mmcblk0p4 (write-protection, I'm guessing. I did take the JB OTA from T-Mobile at one point...)
-If I go the Moonshine route, the device crashes when Moonshine tries the ADB test (reboot from bootloader). This happens using the ville_3.16.661.4 and ville_3.14.531.11 versions...
Possible solutions:
1. Downgrade hboot to an earlier version without write-protection on mmcblk0p4 so I can SuperCID -> Facepalm. I'm currently on hboot 2.15 - is this possible?
2. Flash a ROM of a firmware supported by Moonshine - anyone have that?
rialsolk pecans
UPDATE: I apologize for the double post, but I was able to S-OFF using Moonshine.
What I used:
ViperROM 2.1
TWRP 2.3.3.0
Windows 7 Pro x64
Moonshine - HTC One S Telus Windows 3.16.661.4
I currently have hboot 2.15. Thanks for looking!

Categories

Resources