Hi,
If I check in fastboot I get CID 11111111 which I set myself during the setup of a custom ROM.
If I check with CID Getter application I get HTC__E11 my original CID.
Which one should I trust?
Also, anybody know if having a super CID would void the warranty? have to return my phone for repair so cleaning it up. All is different now is the CID.
Thanks a lot for your help!
saf_ro said:
Hi,
If I check in fastboot I get CID 11111111 which I set myself during the setup of a custom ROM.
If I check with CID Getter application I get HTC__E11 my original CID.
Which one should I trust?
Also, anybody know if having a super CID would void the warranty? have to return my phone for repair so cleaning it up. All is different now is the CID.
Thanks a lot for your help!
Click to expand...
Click to collapse
I would trust the one that you get it fastboot as the one you get from CID getter is the one that is in the build.prop of your ROM.
S-OFFing would void your warranty. You need S-OFF to set SuperCID so there. Connect the dots
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
saf_ro said:
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
Click to expand...
Click to collapse
YES! I meant S-OFF. That was embarrassing
I think you can just write CID just like how you SuperCID'd but writing proper CID instead of 11111111. I haven't done it myself so I can't help you there.
Just go to viper's thread here. He has instructions for S-ONing
http://forum.xda-developers.com/showthread.php?t=1192300
saf_ro said:
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
Click to expand...
Click to collapse
I think what you are searching for is
fastboot oem writecid ............ (Your cid)
Be sure to flash a proper ruu first, or you might end up bricking your device turning s on
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
dgenx210 said:
YES! I meant S-OFF. That was embarrassing
I think you can just write CID just like how you SuperCID'd but writing proper CID instead of 11111111. I haven't done it myself so I can't help you there.
Just go to viper's thread here. He has instructions for S-ONing
http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
yep, already got it working.
I guess in my case the writecid was not working because I was back to S-ON and no root anymore
So, I flashed again the 1.50.401.1 ROM WITHOUT accepting the update, S-off, root, change the CID, flash the 1.50.401.1 again, change back to S-ON with the writesecureflag 3. Device can go now to repair.
Thanks for the help, great forum and info sources!
Related
I want to S-ON my sensation to return for an exchange. What i don't understand is the adb fastboot oem writecid 11111111 command being used to put s-on back. Current Tmobile usa CID is T-MOB010. Can someone explain to me why i need to use the 11111111 instead of the tmobile T-MOB010?
Will it really make the CID 11111111?
You are right to be confused.
I don't know why you would want to SuperCID your phone if you have the correct RUU and CID for your device, the guides have made a mistake here.
I assume it is for people who don't know what RUU they should use for their phone, and/or have SuperCID'ed their phone and not bothered to write down their stock CID. That is there fault in a way, they should really take note of their stock CID for warranty purposes. But then it is risky for them to send in their phones or warranty repair because they could have installed the wrong RUU for their device, and in addition if the HTC engineers somehow check the CID to find it is 11111111 then they know the phone has been tampered with. But thats only if HTC bother to check all this, and even so they might not care. But it still is risky.
Anyway you know which RUU to use, and you have your Stock CID. You don't need to take any risks. You can properly return your phone back to stock.
Go ahead and use it.
fastboot oem writecid T-MOB010
Install the RUU AFTER you return to your stock CID. That way you cannot accidently install the wrong RUU.
Just so you know, 11111111 is SuperCID, this allows you to install any signed RUU without regional restrictions. You don't need or want this if you want to return your phone to stock.
prank1 said:
You are right to be confused.
I don't know why you would want to SuperCID your phone if you have the correct RUU and CID for your device, the guides have made a mistake here.
I assume it is for people who don't know what RUU they should use for their phone, and/or have SuperCID'ed their phone and not bothered to write down their stock CID. That is there fault in a way, they should really take note of their stock CID for warranty purposes. But then it is risky for them to send in their phones or warranty repair because they could have installed the wrong RUU for their device, and in addition if the HTC engineers somehow check the CID to find it is 11111111 then they know the phone has been tampered with. But thats only if HTC bother to check all this, and even so they might not care. But it still is risky.
Anyway you know which RUU to use, and you have your Stock CID. You don't need to take any risks. You can properly return your phone back to stock.
Go ahead and use it.
fastboot oem writecid T-MOB010
Install the RUU AFTER you return to your stock CID. That way you cannot accidently install the wrong RUU.
Just so you know, 11111111 is SuperCID, this allows you to install any signed RUU without regional restrictions. You don't need or want this if you want to return your phone to stock.
Click to expand...
Click to collapse
Exactly why i am asking. If they run diagnostics and see 11111111 they would know it has been tampered with.
So to understand you correctly. I should follow the instruction....
instead of 11111111 i should
fastboot oem writecid T-MOB010
then run the RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
Is this correct.
Yup that'll work, but remember, you will still need to preform the procedure to get your device back to S-ON, or changing the cid won't make one bit of difference as far as warranty replacement.
cenwesi said:
Exactly why i am asking. If they run diagnostics and see 11111111 they would know it has been tampered with.
So to understand you correctly. I should follow the instruction....
instead of 11111111 i should
fastboot oem writecid T-MOB010
then run the RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
Is this correct.
Click to expand...
Click to collapse
Yup
Just remember, simply flashing the ruu will NOT revert you to S-ON. You will have a stock S-OFF device.
Behold_this said:
Yup that'll work, but remember, you will still need to preform the procedure to get your device back to S-ON, or changing the cid won't make one bit of difference as far as warranty replacement.
Click to expand...
Click to collapse
So after all that procedure the last step to get s-ON is:
Type in ADB "adb reboot-bootloader" and then Type in ADB "fastboot oem writesecureflag 3" and Type "fastboot reboot-bootloader"
correct?
prank1 said:
You are right to be confused.
I don't know why you would want to SuperCID your phone if you have the correct RUU and CID for your device, the guides have made a mistake here.
I assume it is for people who don't know what RUU they should use for their phone, and/or have SuperCID'ed their phone and not bothered to write down their stock CID. That is there fault in a way, they should really take note of their stock CID for warranty purposes. But then it is risky for them to send in their phones or warranty repair because they could have installed the wrong RUU for their device, and in addition if the HTC engineers somehow check the CID to find it is 11111111 then they know the phone has been tampered with. But thats only if HTC bother to check all this, and even so they might not care. But it still is risky.
Anyway you know which RUU to use, and you have your Stock CID. You don't need to take any risks. You can properly return your phone back to stock.
Go ahead and use it.
fastboot oem writecid T-MOB010
Install the RUU AFTER you return to your stock CID. That way you cannot accidently install the wrong RUU.
Just so you know, 11111111 is SuperCID, this allows you to install any signed RUU without regional restrictions. You don't need or want this if you want to return your phone to stock.
Click to expand...
Click to collapse
Fixed My S-ON Thread
Hey guys
If I'm not wrong SuperCID is the manufacturer code, which prevents me to flash any Custom ROM and staying on Stock ROM, right?
So, if I didn't do SuperCID and still on Stock ROM, can I use RUU to return back to S-ON? If yes, will it install even if the RUU isn't the right one for the device?
Thank you
Super CID means you can flash ANY RUU you decide to try
So if I didn't do the SuperCID, if I choose the wrong RUU, it will not get flashaed or will it continue and I'll end up with a brick?
Edit: I found this: "If they don't have SuperCID, they'll get 'ERROR[131]: CUSTOMER ID ERROR' if they try to flash the wrong RUU and it will stop without flashing anything to the phone." Can anybody confirm that it's right?
Thank you
That is correct. With your normal CID you can only flash RUUs that are for your phone. WIth Super CID you can flash any RUU that takes your fancy
Are there any downsides from using SuperCID?
WTFD4V1D said:
Are there any downsides from using SuperCID?
Click to expand...
Click to collapse
I would also like to know this
Sent from my HTC Sensation 4G using XDA App
Others have reported that with super CID, they were not getting the updates from htc, but some said that they still received official updates from htc even with super CID. There are no real downsides to superCID as far as I know except maybe when you return it for warranty purposes, but you can always put your original CID back. Just take note of your original CID before you super CID.
The alternative to SuperCID is to flash the ENG hboot after you're s-off. The ENG hboot will disregard a CID mismatch.
Guys,
Noob question: do I have to be rooted to get superCIDed?
I didn't create any SuperCID when unlocking bootloader with Revolutionary... If that bad? Can i get that again?
brusko1972 said:
Others have reported that with super CID, they were not getting the updates from htc, but some said that they still received official updates from htc even with super CID. There are no real downsides to superCID as far as I know except maybe when you return it for warranty purposes, but you can always put your original CID back. Just take note of your original CID before you super CID.
Click to expand...
Click to collapse
I got a update from HTC, didn't istall it though.
Yes, i have SuperCid
EddyOS said:
Super CID means you can flash ANY RUU you decide to try
Click to expand...
Click to collapse
Thank you guy, you answered to my question!
Hi all,
I feel like I have looked everywhere and cannot find an answer for this. I have an at&t one x that is rooted and unlocked with a custom rom, however I somehow changed my cid from supercid 11111111 to htc__001. Is it possible to get supercid 11111111 back or at least wsc__001 so I can run the correct ruu on it.
Thank you in advance for any ideas or help
Just do s off then it will bypass cid... But I think you can do fastboot oem write cid 11111111( don't know how many ones there are)
ziolko said:
Hi all,
I feel like I have looked everywhere and cannot find an answer for this. I have an at&t one x that is rooted and unlocked with a custom rom, however I somehow changed my cid from supercid 11111111 to htc__001. Is it possible to get supercid 11111111 back or at least wsc__001 so I can run the correct ruu on it.
Thank you in advance for any ideas or help
Click to expand...
Click to collapse
fastboot eom writecid "htc__001" or whatever you want it to be minus quotations while in fastboot.
---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------
a box of kittens said:
Just do s off then it will bypass cid... But I think you can do fastboot oem write cid 11111111( don't know how many ones there are)
Click to expand...
Click to collapse
there's 8 characters in the CID
You can change the CID the old "manual" method: http://forum.xda-developers.com/showthread.php?t=1671396
Or if you do S-off, you can just change the CID with a fastboot command.
Sounds like you were one of the folks that changed to the quad core CID so you can flash a ROM from that phone. Scary.
redpoint73 said:
You can change the CID the old "manual" method: http://forum.xda-developers.com/showthread.php?t=1671396
Or if you do S-off, you can just change the CID with a fastboot command.
Sounds like you were one of the folks that changed to the quad core CID so you can flash a ROM from that phone. Scary.
Click to expand...
Click to collapse
I will try the manual fix, thank you!
I did not read everything I should have in the beginning. I was trying to run a ruu back to stock and did not know I could have done that with supercid ( which I had at the time) and thought I had to change the cid back to original and mistakenly thought HTC__001 was correct. After I realized WSC__001 was actually the correct original cid and now i can't change back in fastboot without errors. I got to comfortable and got ahead of myself.......
CWS__001
Sent from my HTC One X using xda app-developers app
redpoint73 said:
You can change the CID the old "manual" method: http://forum.xda-developers.com/showthread.php?t=1671396
Or if you do S-off, you can just change the CID with a fastboot command.
Sounds like you were one of the folks that changed to the quad core CID so you can flash a ROM from that phone. Scary.
Click to expand...
Click to collapse
You don't need S-off to use the fastboot command to change it from what I understand you just need to have Super CID.
exad said:
You don't need S-off to use the fastboot command to change it from what I understand you just need to have Super CID.
Click to expand...
Click to collapse
Right but without s-off, you can only do it once, away from SuperCID. After that, you're stuck.
OP has neither s-off nor SuperCID, which means he needs the exploit.
Back at SuperCID 11111111, thank you everyone.
ziolko said:
Back at SuperCID 11111111, thank you everyone.
Click to expand...
Click to collapse
Go s-off before you do anything else. You'll thank me later.
iElvis said:
Go s-off before you do anything else. You'll thank me later.
Click to expand...
Click to collapse
S-OFF achieved , now how do I get Jelly bean or another recommended rom?
ziolko said:
S-OFF achieved , now how do I get Jelly bean or another recommended rom?
Click to expand...
Click to collapse
Just load and flash. Once you're s-off, you can flash whatever you want.
iElvis said:
Just load and flash. Once you're s-off, you can flash whatever you want.
Click to expand...
Click to collapse
Well.. anything intended for your device!!!! -_- You're gonna brick noobs talking like that lol
Went with ViperXL 3.2.6 and love it! Thanks to all who helped!
I have been trying to run a RUU to unroot the phone before I bring it in for a repair. I keep getting the 155 error and I searched through google for help on the error. I have read a few post about it but nothing works. I tried to run it through fastboot as well and that does not work. My phone information while in bootloader is Evita pvt ship s-on rl hboot 1.09.0000 radio .17.32.09.12 and I am running cleanrom v 6.5 as my rom. Since my rom and boot.img is based of 3.18 I tried to run the ruu on 3.18. Im not sure if its because it is an older verdion of bootloader while im running a rom that is based off the 3.18. So I also tried to flash a older rom and run the ruu for 1.73 but that didnt work either. Im stumped and very frustrated so please I need your help.
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah for the 3.18 its http://bugsylawson.com/HTCFiles/Evi....24p.32.09.06_10.130.32.34_release_signed.exe
and for the 1.73 its http://www.ponack.net/designgears/b...73.502.2_2FE6772699D8596307CC997452BB8D25.exe
Also I read that in order to use the RUU correct I need to soff the phone, but then I cant upgrade the firmware to jellybean. Do you know if this is correct?
The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF
Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
exad said:
The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF
Click to expand...
Click to collapse
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?
cables2590 said:
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2156368
hello to all . i have a simple question... i don't have a stock sense rom accepted for Moonshine.. so in the case i want to do S-OFF i have to use rumrunner... but the only thing to i try S-OFF its to have the possibility to have SuperCID and use any RUU... so here come my questions:
1-. i don't find a thread to have SuperCID on villeC2.. so its impossible? can't use fastboot write cid 11111111 ?
2-. my model is pj40210, not the universal pj40200 this matter? can i run a ruu for pj40200 on my phone? can damage?
thats all. thanks
xiaolvmu said:
Aha, to find the stock ROM, you can go to http://www.androidruu.com. I always download VilleC2 RUU there.
S-Off is doesn't need supercid. Also, VilleC2 has a strange security lock and we can never write CID (even change the mmcblk0p13. Don't try it, too dangerous. I've tried to get supercid but failed).
The model seems doesn't matter.
Click to expand...
Click to collapse
thanks for response . the problem is, for ,my CID (BSTAR301) don't exist a ruu . just have my nandroid backup
xiaolvmu said:
That means your CID doesn't have a RUU for download? You can Change your CID. I'll post a tutorial on One S forum
Click to expand...
Click to collapse
exactly my CID doesn't have a RUU for download! how i can change my CID? please make a tutorial i don't need do it because i'm using your rom hehehehe.... but.... just in case.....
xiaolvmu said:
OK... @JavierG123
I already found an existing tutorial:
http://forum.xda-developers.com/showthread.php?p=26516911
The only difference is, VilleC2 can't use 11111111. You can change it to HTC__044 (Asia Version)
Then, in this download page : http://androidruu.com/?developer=VilleC2
Download this: RUU_VILLEC2_U_ICS_40_S_hTC_Asia_WWE_2.15.707.101_Radio_16.21.20.02U_16.09.20.11_M2_release_289564_signed.exe
Then you can flash the pure RUU
ps: The Hex Editor on Windows is a paid software, so I'll give a cracked version
https://www.dropbox.com/s/ath1t92jrs4lm78/Hex Editor for changing CID.zip?dl=0
Click to expand...
Click to collapse
thanks a lot xiaolvmu! i just find FOR FIRST TIME!!! I SEARCHING THIS FOR A VERY LONG TIME!!! a OTA for my BSTAR301.. but i don't now how to for example... back to stock with a ota... in the case i need a use a full ruu i use that post, thanks for the help. i dont know that... our ville don't support super cid but yes other cid xd... this htc people... god...