I have read various guides, and eventually taken the plunge to downgrade my bootloader.
htcDev Unlock
Goldcard
Install oldest RUU
S-OFF using revolutionary
Flash CWM recovery
Backup Stock 2.33 ROM with Sense
Install CM9
Feeling quite pleased with myself, even though you guys have really done all the hard work, I've just followed the steps!
What I can't find is this;
If I go back to the Stock ROM and updates are offered OTA, if I accept, will this, not only bring me back to 2.3.5 with Sense 3.0, but also change my bootloader back to 2.00.0002 Locked and S-ON ?
Unfortunately it will be *RELOCKED* and S-ON
Sent from my HTC Desire S
amidabuddha said:
Unfortunately it will be *RELOCKED* and S-ON
Click to expand...
Click to collapse
What he said. If you wanted to remain "locked" and not "relocked" - you should have avoided unlocking the bootloader, and should have used temp-root for misc_version.
Ok, what are the inplications of being 'RE-LOCKED'
Like CM9, but get the feeling development stalled, also certain apps won't work Nat West being one, though I suspect that is to do with their development.
Thinking about going back to Stock. If I do this via OTA, my bootloader will be upgraded back to 2.00.0002, 'RE-LOCKED' and S-ON, then wait for official OTA upgrade to ICS, which seems not to be happening as per HTC announcements. Even then I may have issues with apps that haven't been coded to deal with it.
If I am 'RE-LOCKED' can I not use htcDev again, or am I stuck with the Official bootloader etc and unable to load other ROMS, or can I just repeat the processes I have been through already?
I have also been reading about unlocking with an XTC Clip, where would I get this done, Is this a better solution? etc etc..
No issues with RELOCKED except that your warranty is gone.
If you have no warranty you can go for XTC Clip, since permanent S-OFF will give you more freedom in terms of modifications. Personally I consider flashing boot.img separately each time as annoying.
As per the unlock again, it should be possible, but I am not sure if this can be done by a fastboot command or the unlock token has to be flashed again.
Sent from my HTC Desire S
When I unlocked mine I remember reading somewhere that the token would need to be used again if the phone was re locked. So I kept it just in case
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!
hi everyone,
Sorry if I posted this in the wrong forum. I have the One X which I just rooted, unlocked BL and also did S-off just over the weekend as I was wanted to try some JB. Now my sim card slot failed, it keeps saying no sim card found. I tried my sim on a different phone and the sim works. Now I am trying to get back everything as close to stock(2.20) as possible, so that I can get a exchange with att/htc. I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ? I still have s-off, Is there anyway I can go back to s-on and reset my c-id ?
Thanks in advance.
Just to elaborate on my original message below, though I have s-off, and unlocked bootloader, I have not flashed any ROM. I just flashed the twrp recovery.
Now I have everything back to original but for the following
a) I am still S-off. Can I go S-On ?
b) bootloader says relocked, can I make it to say locked ?
c) can someone point me to the link for 2.20 RUU zip file ?
Thanks,
onex_001 said:
hi everyone,
Sorry if I posted this in the wrong forum. I have the One X which I just rooted, unlocked BL and also did S-off just over the weekend as I was wanted to try some JB. Now my sim card slot failed, it keeps saying no sim card found. I tried my sim on a different phone and the sim works. Now I am trying to get back everything as close to stock(2.20) as possible, so that I can get a exchange with att/htc. I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ? I still have s-off, Is there anyway I can go back to s-on and reset my c-id ?
Thanks in advance.
Click to expand...
Click to collapse
onex_001 said:
I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ?
Click to expand...
Click to collapse
No, you've got it backwards. Its intended to say RELOCKED (or UNLOCKED) once its been unlocked. It might be possible to change these flags, if you have S-Off. But such a thing has not been discovered yet. Nor has a method to S-on been discovered yet (or at least not that has been posted here).
Just relock and RUU. It will still say RELOCKED and S-Off, (otherwise stock). But AT&T doesn't seem to care about the bootloader being unlocked on this device. Many people have gotten warranty service from AT&T for phones that say RELOCKED. I think some folks have even warrantied devices UNLOCKED and running custom ROMs! Just make sure you go through AT&T, as HTC themselves are known to be much more strict about their warranty coverage.
---------- Post added at 04:46 PM ---------- Previous post was at 04:42 PM ----------
onex_001 said:
c) can someone point me to the link for 2.20 RUU zip file ?
Click to expand...
Click to collapse
Don't know why people ignore this, and make life so hard for themselves:
http://forum.xda-developers.com/showthread.php?t=1671237
You can also get it straight from HTC's support website.
Going back to S-on is simple fastboot command, but there's no reason to do it.
You can edit some of your bootloader text in various ways. Start with this thread:
http://forum.xda-developers.com/showthread.php?t=2156368
But don't try any of this unless you know what you're doing.
Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.
Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?
Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.
you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.
srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers
srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?
Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita
Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
Have you checked your APNs?
Sent from my Evita
srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.
It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers
Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.
Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.
Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......
So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.