Database Info

SuperCID?

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!

[Q] Return to full stock

So, I have done a lot of research and I am hung up on one bit.
I have the stock RUU file on my PC.
I also have superCID . I am rooted with S-OFF
Think i used Revolutionary etc. Currently using ARHD 6.8.0
I want to return to Full Stock with S-ON. I looked at this guide: http://forum.xda-developers.com/showthread.php?t=1192300
But it doesn't say if I need to change my CID back to VODAP001 before or after (Or at all) I flash the Stock RUU. <hope that makes sense?
Could anyone help me?
I basically have the RUU. and need to know about the CID. Does it need to be changed?
Thanks

Just seen this actually
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.

pike0 said:
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
Click to expand...
Click to collapse
Hi,
If you are returning your phone for warranty purposes,you need to return your SuperCID to normal.
This should be done after running your RUU,but before going back to s-on.
Look HERE for more information.

pike0 said:
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
Click to expand...
Click to collapse
you can flash any ruu when you have supercid(that means S-OFF also)
this guide will help you more
http://forum.xda-developers.com/showthread.php?t=1672425
but read carefully about returning to S-ON

rzr86 said:
you can flash any ruu when you have supercid(that means S-OFF also)
this guide will help you more
http://forum.xda-developers.com/showthread.php?t=1672425
but read carefully about returning to S-ON
Click to expand...
Click to collapse
Cool, well the RUU I have will need the VODAP001 *** (I think it's that, will check before I attempt lol)
So I flash the RUU then I can use this:
Code:
fastboot oem writecid ******* Replacing the *'s with the CID I need.
Once done, can then return to S-ON

pike0 said:
Cool, well the RUU I have will need the VODAP001 *** (I think it's that, will check before I attempt lol)
So I flash the RUU then I can use this:
Code:
fastboot oem writecid ******* Replacing the *'s with the CID I need.
Once done, can then return to S-ON
Click to expand...
Click to collapse
also about S-ON read carefully what it is saying about bootloader
your bootloader must be LOCKED, RELOCKED or UNLOCKED otherwise don't do S-ON

rzr86 said:
also about S-ON read carefully what it is saying about bootloader
your bootloader must be LOCKED, RELOCKED or UNLOCKED otherwise don't do S-ON
Click to expand...
Click to collapse
Was just about to post. Successfully flashed the RUU and changed CID to VODAP001, phone boots and works fine!!!
But in bootloader it doesn't mention, locked, unlocked or relocked.
Previously to the Update, it said ***LOCKED***
Now I got just this:
Pyramid PVT Ship S-OFF RL
HBOOT-1.17.0006
RADIO-10.11.9007.09_M2
eMMC-boot
What do I need to do to S-ON???
Thanks

pike0 said:
Was just about to post. Successfully flashed the RUU and changed CID to VODAP001, phone boots and works fine!!!
But in bootloader it doesn't mention, locked, unlocked or relocked.
Previously to the Update, it said ***LOCKED***
Now I got just this:
Pyramid PVT Ship S-OFF RL
HBOOT-1.17.0006
RADIO-10.11.9007.09_M2
eMMC-boot
What do I need to do to S-ON???
Thanks
Click to expand...
Click to collapse
if your bootloader says locked now(as you are mentioning) then you can continue with S-ON
edit:what to do for S-ON?
from the same guide it has a tutorial for it
but i think it is a simple command and then you are done

rzr86 said:
if your bootloader says locked now(as you are mentioning) then you can continue with S-ON
edit:what to do for S-ON?
from the same guide it has a tutorial for it
but i think it is a simple command and then you are done
Click to expand...
Click to collapse
Sorry, I actually mean, before I restored the RUU it said locked. Now it doesnt mention anything.
It no longer says that, or unlocked / relocked.
So I haven't proceeded with the S-ON command.

pike0 said:
Sorry, I actually mean, before I restored the RUU it said locked. Now it doesnt mention anything.
It no longer says that, or unlocked / relocked.
So I haven't proceeded with the S-ON command.
Click to expand...
Click to collapse
hmm,
i don't know about that
it is better to ask for that in the ruu thread
someone will know

rzr86 said:
hmm,
i don't know about that
it is better to ask for that in the ruu thread
someone will know
Click to expand...
Click to collapse
Say I still have S-OFF but everything else is back to stock. What steps would I need to take to root, custom recovery & ROM again?
Thanks

pike0 said:
Say I still have S-OFF but everything else is back to stock. What steps would I need to take to root, custom recovery & ROM again?
Thanks
Click to expand...
Click to collapse
Hi,
Flash recovery of choice.
Flash root.
Flash custom ROM.

malybru said:
Hi,
Flash recovery of choice.
Flash root.
Flash custom ROM.
Click to expand...
Click to collapse
Recovery is the PMG...zip is that correct?
Thanks for all the help

pike0 said:
Recovery is the PMG...zip is that correct?
Thanks for all the help
Click to expand...
Click to collapse
Hi,
Look HERE
2. Flashing a recovery
4A. Flashing Root

malybru said:
Hi,
Look HERE
2. Flashing a recovery
4A. Flashing Root
Click to expand...
Click to collapse
Many thanks! Would it make a difference if my phone is already S-OFF??

pike0 said:
Many thanks! Would it make a difference if my phone is already S-OFF??
Click to expand...
Click to collapse
Hi,
No.
If you ran a RUU,then,everything would have returned to stock.
S-off is not affected.
So,to get back up and running,you will need to do all these things again.

[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] RUU won't work

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

Stuck bootloader after RUU

Ok, guys, i think that i made a big mistake, i was helping to restore to stock the HTC evita of a friend. We download the latest RUU from att, relocked and run. the problem was, that we didnt check it if there was super cid. and it have it. BUT, usually if there is a brick i cant enter to bootloader right? I can enter in bootloader, and show
Relocked
EVITA PVT SHIP S-ON RL
HBOOT- 2.18.0000
RADIO-1.35a.32.45.27
OPENDSP-v33.1.0.45.1127
eMMC-boot
Dec 3 2013,17,10,01:1
The phone has supecid: (bootloader) cid: 11111111
I know that usually is a brick, but i can enter the bootloader (i did a clearstorage but still bootloop) I dont want to make it worse. so any advice to fix it? I was thinking about unlocking again bootloader but probably it cause a brick? I read that the brick is unlocked bootloader + supercid +s-on, but the bootloader was relocket so maybe that save the device?. Any advice would be great

lorddavid said:
Ok, guys, i think that i made a big mistake, i was helping to restore to stock the HTC evita of a friend. We download the latest RUU from att, relocked and run. the problem was, that we didnt check it if there was super cid. and it have it. BUT, usually if there is a brick i cant enter to bootloader right? I can enter in bootloader, and show
Relocked
EVITA PVT SHIP S-ON RL
HBOOT- 2.18.0000
RADIO-1.35a.32.45.27
OPENDSP-v33.1.0.45.1127
eMMC-boot
Dec 3 2013,17,10,01:1
The phone has supecid: (bootloader) cid: 11111111
I know that usually is a brick, but i can enter the bootloader (i did a clearstorage but still bootloop) I dont want to make it worse. so any advice to fix it? I was thinking about unlocking again bootloader but probably it cause a brick? I read that the brick is unlocked bootloader + supercid +s-on, but the bootloader was relocket so maybe that save the device?. Any advice would be great
Click to expand...
Click to collapse
I think you need to unlock your bootloader and get S-off to proceed with RUU because you have superCid.

sathish804 said:
I think you need to unlock your bootloader and get S-off to proceed with RUU because you have superCid.
Click to expand...
Click to collapse
yes, the problem is that i cant load a rom, I mean, its bootloop. If i unlock bootloader and flash a recovery will be ok? I mean, i fear that unlocking bootloader brick my phone because I ran RUU with supercid

Unlock the bootloader again, flash TWRP recovery again, flash a custom ROM, get s-off, then you can run any RUU you want.
Sent from my Evita

ok, i unlock the bootloader, I'm trying to enter hboot again because the volumebutton ihave little damage. thanks If something happen i will report back.
PD: S-off can i do it with an aosp rom? Or need a sense rom?

It shouldn't really matter, I've done it on both.
Facepalm S-off
Sent from my Evita

Doesn't the Evita need to be s off to run a ruu, and with a locked bootloader?
Sent from my One X using Tapatalk

marknoll said:
Doesn't the Evita need to be s off to run a ruu, and with a locked bootloader?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
No, but running any jb+ RUU with s-on and SuperCID causes a brick. Plus, if you have SuperCID, you need s-off to bypass the CID check that stops the RUU from running.
Sent from my Evita

timmaaa said:
No, but running any jb+ RUU with s-on and SuperCID causes a brick. Plus, if you have SuperCID, you need s-off to bypass the CID check that stops the RUU from running.
Sent from my Evita
Click to expand...
Click to collapse
Uff, finally, but TWPR is weird, flash a lot in splash screen :/ but after a while works. I was thinking that i had a brick because i was s-on and supercid. I had a aosp rom, so right now I will do s off. Thanks so much
PD: Right know is in the boot screen of PAC ROM. The hboot doesnt matter for an aosp rom right?

You probably need to read the Evita FAQ thread in my signature.
Sent from my Evita

timmaaa said:
You probably need to read the Evita FAQ thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
yes i did, is not the first time that i install a custom rom in a htc, i flash the boot.img and everything, but had some weird problems, I will try philz recovery now (TWPR sometimes flash a lot in the splash screen, or freeze or just works normal). and i will download another rom just to be sure.
Ok, its finnish, thanks so much. First the RUU close with an error, but i tried in another account of my pc and works (the same error was before when everything start, is funny, maybe thats save my phone from a brick because I was s-on with supercid :/ )
Thanks so much again for the help