Database Info

[Q] Recovering to stock...which RUU for me?

I have an At&t HTC One X that I bought from a licensed store in Jersey.
I used a hex editior to change the CID so I could use HTCdev to unlock the bootloader (so my current CID is Roger001, which was not the original CID). Currently installed CleanROM 4.0.
Want to get back to stock to return phone...what information do I need to provide so that someone can tell me what RUU to use? In settings I see build number 1.85.502.3...hboot is 1.09.0000...radio is 0.17.32.09.12.

You can relock your bootloader then change your CID back to CWS__001 using the same hex hack method you used to make it a ROGERS CID then run the 1.85 RUU and your back to stock. One thing is your bootloader will still say relocked at the top but there is nothing you can do about that but hope they don't look at that and deny you.

Link to the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238

So I hack the CID back, lock the bootloader, and run the RUU mentioned and that's it? I figured my hboot version, radio version and all the rest of it would lead me to a different RUU than the one you pointed to...

When you RUU back to 1.85 it will flash everything to the 1.85 versions.

If I lock the bootloader, how do I change the CID back? When I hacked the CID and used ADB my phone was on with the ROM loaded and plugged in...If I lock the bootloader, I can only get into the hboot screen...can I still ADB push and pull from there?
And if I'm planning on flashing the 1.85 RUU, do I need to change the CID at all? Can't I just lock the bootloader, and then run the .exe?

Locked bootloader and then ran the 1.85 RUU you pointed me to...received error 131...back to Hboot with a locked bootloader...any suggestions? Y'all made it sound so simple...

Because you didn't change Cid. Error 131
You can still unlock then push a recovery then from that recovery put a rom on the phone and flash. Use twrp.

So from here...unlock bootloader...then push twrp recovery...at what point do I change the CID and run the RUU to get back to stock?

aram12 said:
So from here...unlock bootloader...then push twrp recovery...at what point do I change the CID and run the RUU to get back to stock?
Click to expand...
Click to collapse
after you have a rooted ROM on it and can access the proper partition with a hex editor to change the CID back after that you can relock bootloader and run RUU

This is why you get nexus, just flash stock images
Sent from my Galaxy Nexus using Tapatalk 2

Help getting back to stock

I'm planning on putting my phone fully back to stock. I just have a few questions that I can't find answers to, if anyone could help it would be greatly appreciated.
Background
S4 Version
HBoot: 1.06*
Bought the phone second hand, it was carrier unlocked and already rooted etc.*
The phone CID says orangeuk, but*I use 3UK Network.*I'm going to have to use SuperCID before I flash the ruu, because there is no orangeUK ruu available.
1.**Is the HTC_001 the best CID to use for ota's and ruu files?
2. When I re-lock bootloader and flash ruu, will I lose the carrier unlock?
Sent from my HTC One S using xda app-developers app

I dont have an answer for 1 but im pretty sure about 2 that carrier unlock wont go. Once you unlock it it stays unlocked

Right, this is my plan to get back to stock. If anyone has any better ideas please let me know!
1. Change radio 1.06es version to match ruu radio (read somewhere the ruu might not run if my radio is newer, currently 1.11)
2. Change CID to HTC__001 to run 2.31 WWE ruu.
3. Re-lock Bootloader
4. Run 2.31 WWE ruu
5. Update software via OTA to JB.
6. Carrier unlock phone if necessary using code created while rooted.
Questions
Do I have to flash stock recovery or will the ruu do that?
Can I run the 2.31 WWE ruu from hboot 1.06, or do I need to use 1.53 ruu as that has the same hboot?
I assume the OTA will also update my radio to 1.11?
Thanks

rosswhite said:
Right, this is my plan to get back to stock. If anyone has any better ideas please let me know!
1. Change radio 1.06es version to match ruu radio (read somewhere the ruu might not run if my radio is newer, currently 1.11)
2. Change CID to HTC__001 to run 2.31 WWE ruu.
3. Re-lock Bootloader
4. Run 2.31 WWE ruu
5. Update software via OTA to JB.
6. Carrier unlock phone if necessary using code created while rooted.
Questions
Do I have to flash stock recovery or will the ruu do that?
Can I run the 2.31 WWE ruu from hboot 1.06, or do I need to use 1.53 ruu as that has the same hboot?
I assume the OTA will also update my radio to 1.11?
Thanks
Click to expand...
Click to collapse
The RUU should update everything. Including the stock recovery, Hboot, and radio. I already Rooted the One S. Then unrooted. Then rooted again. The only thing i will mention....
Make sure you have the stock Boot.img first. Then use Fastboot to load the boot.img. then you can flash the RUU. Good luck

[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!

[Q] What RUU do I need?

Hi there.
What RUU do I need? On androidruu.com either the baseband or the bootloader version doesn't match.
CID: T-MOB010
Bootloader: 2.15.0000
Baseband: 1.13.50.05.31
Main: 3.14.531.17
Model-ID: PJ4011000
ComitNO-Bootloader: dirty-64bedd38
Right now I'm on (unofficial) Cyanogenmod 12.1 with TWRP. What are the steps to get back to stock? Relocking the bootloader, installing stock recovery and running the RUU.exe file?
Thank you.

gregor.samsa said:
Main: 3.14.531.17
Click to expand...
Click to collapse
Look for your current firmware version (highlighted in bold) in the RUU names. All RUU names contain the firmware version they're made for. If there is no RUU with that version you can try to find one with a higher version but the same SKU (the number I highlighted in red). If you aren't able to find a newer RUU, either, you might consider using Llabtoofer's RUU Service. Alternatively, you might want to get S-OFF with either Facepalm, Rumrunner or Moonshine so that you're able to flash older RUUs for your SKU, as well. Be aware that these old methods aren't as reliable as Sunshine (which gets used on newer HTC phones). You will most likely need to start several tries before one of them sets your phone S-OFF. I don't know whether Sunshine can be used on the One S, too.
gregor.samsa said:
What are the steps to get back to stock? Relocking the bootloader, installing stock recovery and running the RUU.exe file?
Click to expand...
Click to collapse
Only relocking is needed (and that only if your phone is S-ON). The stock recovery gets installed by the RUU.
Edit: Looks like there's a suitable RUU, here. Make sure that you read this post if the flashing fails due to error 171. In addition, you might want to boot your One S to fastboot USB mode before you execute the RUU. If I remember correctly, RUUs for the One S tend to fail if you don't do so.