Related
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!
Will at&t ruu 2.20.502.7 will work on supercid 1111111 at&t hox to get back to stock?
I am having at&t htc one x bootloader with :
**** tampered ****
**** unlocked ****
evita pvt shp s-on rl
hboot-1.09.0000
radio-0.19as.32.09.09_l
opendsp-v28.1.0.32.0504
emmc-boot
apr 2 2012,21:08:24
installed twrp 2.2.0 recovery and stock rooted rom 2.23707.2 asia generic.
Now the problem is, i am facing the mobile signal(not wifi) dropping issues and i have to revert back to at&t stock rom, i have downloaded the official at&t ruu 2.20.502.2.....exe,
but i am concerned with the doubt that will the ruu will work 100% on supercid 111111 without any problem after relocking the bootloder or do i have to revert back the stock at&t cid, and if yes then what is the procedure to revert back the stock at&t cid???????
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
gunnyman said:
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
Click to expand...
Click to collapse
thanks for the help,appreciable. But i don't want to flash just the radio, coz i already did that, but it did not solve my problem. So the question still continues..Can i run Ruu with the current supercid 111111 or do i have to revert it back to stock???
SORRY FOR BAD ENGLISH. ITS NOT MY FAMILIAR LANGUAGE.
You don't have to change cid to flash the ruu just relock the bootloader
gunnyman said:
you don't have to change cid to flash the ruu just relock the bootloader
Click to expand...
Click to collapse
thanks for the help,
Are you already on 2.20? If not, why not run 1.85 RUU?
thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
good question.
thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
Doesn't look like the op is on 2.20, the hboot for 2.20 is 1.14.0002.
Absolutely Right, i am not on 2.20,
Sent from my HTC One XL using xda app-developers app
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
hemsmaverick said:
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
Click to expand...
Click to collapse
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
gunnyman said:
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
Click to expand...
Click to collapse
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
hemsmaverick said:
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
Click to expand...
Click to collapse
won't work because RUU's include a signature check and if you alter the files in any way, that signature check will fail.
gunnyman said:
won't work because ruu's include a signature check and if you alter the files in any way, that signature check will fail.
Click to expand...
Click to collapse
ok, well as per ur earlier suggestion, i have flash the radio incl ril files from at&t 1.85, asia 2.23, currently on a o2 2.29.
But signal dropping solution has not been resolved.
I have dropped the plan of running ruu and will install custom rom tn special edition 3.6
can u suggest me the best radio for better mobile signals? (i am from india -region asia)
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
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Hydromea said:
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Click to expand...
Click to collapse
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROMs using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
exad said:
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROM using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
Click to expand...
Click to collapse
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Hydromea said:
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Click to expand...
Click to collapse
Yes, I did find Viper and clean rom both ran much better than they did previously.
I'm sorry, I don't know about the 3.18 OTA... Hopefully someone else here can shed more light?
Theoretically, Since you're S-OFF, you should be able to update just fine. I haven't seen anyone actually do it yet though. I would test if I could.
I didn't relock I just ruu'd and after the process was done I just pushed twrp to my phone in fastboot and flashed viper. Only took a few mins top
Sent from my Elemental Venomized S-off HTC One XL
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Hydromea said:
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Click to expand...
Click to collapse
I used the ruu for 3.18 and haven't regretted it yet. My battery life has gotten much better.
Sent from my Elemental Venomized S-off HTC One XL
OTA just downloads through the phone. IE: Go to settings about phone, check for updates and it updates. You don't have to do anything else, it prompts you and updates for you.
If there was already a 3.18 RUU that would be the fastest way. Telus is slow with releasing RUU's so I had to use ICS myself. Neither way should give you trouble.
Here's to hoping my phone doesn't brick. Running the RUU as we speak (bootloader unlocked, s-off, super-cid)...
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
Did you use the 3.18 RUU?
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
If you're hellbent on TWRP 2.2.2.0, downgrade the touchscreen firmware.
Hydromea said:
Did you use the 3.18 RUU?
Click to expand...
Click to collapse
Yeah I did. Maybe I'll look into downgrading the touchscreen firmware.
Sent from my HTC One X
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Hydromea said:
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Click to expand...
Click to collapse
yes you will here is how
http://forum.xda-developers.com/showthread.php?t=2159863
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Hydromea said:
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Click to expand...
Click to collapse
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
jerrycoffman45 said:
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
Click to expand...
Click to collapse
What he said lol
Sent from my Elemental Venomized S-off HTC One XL
this is all great info i would like to thank all of you
does this go for the rogers model as well?
babarnard said:
this is all great info i would like to thank all of you
does this go for the rogers model as well?
Click to expand...
Click to collapse
Yes.
Just an update. I successfully ruu'd to 3.18, downgraded hboot to 1.09, downgraded the touchscreen firmware, installed twrp 2.2.2.0 and all is well.
I'm sort of back where I started but maybe something good has come of it.
Sent from my HTC One X
can i flash RUU 2.20 if my bootloader is relocked and S-on and tampered ?
slytidar said:
can i flash RUU 2.20 if my bootloader is relocked and S-on and tampered ?
Click to expand...
Click to collapse
If you change your CID back to CWS_001, theoretically, you should not brick running the 2.20 RUU, I'm not sure what will happen if you were to upgrade to 3.18 at any point. Probably brick in that case.
Safest way to RUU is to S-OFF first.
exad said:
If you change your CID back to CWS_001, theoretically, you should not brick running the 2.20 RUU, I'm not sure what will happen if you were to upgrade to 3.18 at any point. Probably brick in that case.
Safest way to RUU is to S-OFF first.
Click to expand...
Click to collapse
i cant s ooff as i can only go to bootloader menu
or if there is any way to do it while in the bootloader menu
slytidar said:
i cant s ooff as i can only go to bootloader menu
or if there is any way to do it while in the bootloader menu
Click to expand...
Click to collapse
There is no way to S-OFF without a ROM.
So your choices are
Unlock, flash recovery, flash rom, fastboot flash boot.img, S-OFF, RUU.
Or
Fastboot writecid CWS__001, RUU 2.20, Never upgrade for fear of bricking.
exad said:
There is no way to S-OFF without a ROM.
So your choices are
Unlock, flash recovery, flash rom, fastboot flash boot.img, S-OFF, RUU.
Or
Fastboot writecid CWS__001, RUU 2.20, Never upgrade for fear of bricking.
Click to expand...
Click to collapse
shall i try the last one ?
"Fastboot writecid CWS__001"?
slytidar said:
shall i try the last one ?
"Fastboot writecid CWS__001"?
Click to expand...
Click to collapse
Do whichever one you want. Just remember without S-OFF, I'm pretty sure you will not be able to upgrade to 3.18+ without bricking.
fixed it bt flashing a stock boot.img
thanks
exad said:
If you change your CID back to CWS_001, theoretically, you should not brick running the 2.20 RUU, I'm not sure what will happen if you were to upgrade to 3.18 at any point. Probably brick in that case.
Safest way to RUU is to S-OFF first.
Click to expand...
Click to collapse
2.20 RUU will run with SuperCID, bootloader locked and S-on. With the 3.18 RUU, you will brick under those conditions.