HTC One S Ville that rec'd OTA JB update
Unlocked bootloader, flashed recovery, rooted, installed custom ROM.
Wanted to go back to stock.
Re-locked bootloader
Tried RUU for Bell, got carrier ID error
Tried RUU 1.7 for Rogers (learned about CID and it is Rogers001 on my phone) - failed with unknown error (now realize because it is older hboot)
Managed to get back to a custom ROM. Want to know if it is possible to install Bell RUU (Bell is my carrier) - ie can I defeat/fool the CID in some way? since newer Rogers RUU looks like it won't be happening...
Thanks!
where did you get the rogers RUU from? Do you have a link?
twokidsandaphone said:
HTC One S Ville that rec'd OTA JB update
Unlocked bootloader, flashed recovery, rooted, installed custom ROM.
Wanted to go back to stock.
Re-locked bootloader
Tried RUU for Bell, got carrier ID error
Tried RUU 1.7 for Rogers (learned about CID and it is Rogers001 on my phone) - failed with unknown error (now realize because it is older hboot)
Managed to get back to a custom ROM. Want to know if it is possible to install Bell RUU (Bell is my carrier) - ie can I defeat/fool the CID in some way? since newer Rogers RUU looks like it won't be happening...
Thanks!
Click to expand...
Click to collapse
You going have to wait for the JB RUU or downgrade the Hboot.
Related
Hey guys. I have the latest 1.50.401.1 European stock ROM with stock recovery and all (S-ON, CID HTC__001). I installed this a while ago from the lastest European RUU 1.50.401.1 without any issues. I bought the phone at 2nd hand from a guy who installed some custom ROM on it so I flashed that RUU to return to stock (not T-Mobile stock ROM though, which was originally on the phone).
Now I'm trying to install RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69. 3504.00U_11.22.3504.07_M_release_246089_signed.exe which is the lastest ICS RUU I think and the installer comes up with an error about my model ID. MID is PG5810000 (Sensation 4G - TMobile).
Also, I received the OTA after I went back to S-ON and fiddled with the CID yesterday (after running the first RUU a while ago it seems S-OFF didn't go away, not sure if it was supposed to in the first place). The CID is now HTC__001. Not sure what is was originally though. Anyway, I got the ICS OTA and tried to install, but after downloading it aborted the installation with the attached error.
Any ideas? I've been told that I need MID to be PG5813000 to install the ICS RUU, but why did the GB RUU work in the first place?
I want to install either the OTA (would be better) or the RUU, so if anyone has anything to say, I appreciate it.
Thanks!
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
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
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,
My A9 originally has CID TELST001 and MID 2PQ910000 (S-off and unlocked bootloader). I followed this guide (https://forum.xda-developers.com/one-a9/development/s-off-convert-to-htc-usa-unlocked-1-12-t3271861) to convert it to US model (CID: BS_US001 and MID: 2PQ912000)
I stopped at step 3, just go back to stock with RUU which I downloaded from HTC website (and I did lock bootloader when running RUU while keeping CID and MID as US model). However, the red text regarding to development purpose keeps appearing when I reboot the phone. Is it related to s-off status? From what I have read so far, as long as the kernel is stock then the red message should be gone. However, in my case, restoring via stock RUU does not erase the red message
Would someone please let me know if I did something wrong with RUU process? Cheers
As long as kernel,system and recovery is all stock the message should disappear... There is no reason to relock bootloader if s-off when running an ruu. Did you revert back to telstra ruu or use the unlocked developer ruu? Possible if ran ruu for telstra and kept unlocked cid/mid,maybe cause of your issue... Not sure though... Could be wrong...
Wonders_Never_Cease said:
As long as kernel,system and recovery is all stock the message should disappear... There is no reason to relock bootloader if s-off when running an ruu. Did you revert back to telstra ruu or use the unlocked developer ruu? Possible if ran ruu for telstra and kept unlocked cid/mid,maybe cause of your issue... Not sure though... Could be wrong...
Click to expand...
Click to collapse
I ran unlocked/developer RUU actually, since Telstra does not release RUU for A9. I guess this is the problem. Even with official firmware, if original CID does not match the firmware, it will trigger the red message. I have no idea how to test this theory until I get ahold of TELST001 RUU (which is unfortunately impossible atm)
Change cid/mid to Developer/Unlocked and rerun Developer RUU, If you have run the RUU the firmware is converted to Developer/Unlocked...If converted you really do not need anything from Telstra on the phone...If you have CID 11111111...Change to one below...If you have twrp installed... Replace with stock recovery
MID: 2PQ912000
CID: BS_US001