Database Info

[Q] S-off, root, unlock question

Ive rooted and have got s-off on my sensation and did this in order to unlock it, i must be honest i am a complete noob and didnt understand half of what this actually did. can anyone enlighten me? lol
Back to my main question, if i install s-on and unroot, will the phone remain unlocked? or will it simply go back to its original state?
thanks for any help
edit: typo

Not to sound funny but if you didn't know what you were doing then you shouldn't have done it in the first place.
Having said that, what do you mean when you say you 'unlocked' it?

S-off means that you have removed the Protected NAND safety protection, allowing you to flash custom and unsigned software on the device
Root means that some applications will now be allowed to do things that they were no supposed to do.
Sent from my HTC Sensation Z710e using XDA App

unlocked as in not sim locked

I'm not 100% sure but I'd imagine once done it's permanent

apologies, for the first post, i understood what happens when you root and s-off i just did not understand exactly waht you gain ie. what does it allow you to do with apps and why, the sole reason i did it was to enable myself to unlock the phone and save a few hundred pound as it was i gift from someone who did not use it, instead of selling and going throught he hassle of a new one i thought i would unlock it instead.
I have now however got back to S on and Unrooted (scared of warranty issues) and PRESTO the phone is still unlocked! (apologies if you already knew this worked, i had inferred that nobody knew hence the no reply to my question)
Thanks
---------- Post added at 07:58 PM ---------- Previous post was at 07:20 PM ----------
Also guys do i need to be rooted in order to flash the ROM, i'd like to use the T-Mobile one as it says its compatible in Pyramid, i dont need S-Off do i?

To flash any ROM, stock (different from your current one) or custom, you need S-OFF
S-OFF doesn't SIM unlock it either - that's something separate altogether

EddyOS said:
To flash any ROM, stock (different from your current one) or custom, you need S-OFF
S-OFF doesn't SIM unlock it either - that's something separate altogether
Click to expand...
Click to collapse
Ok thanks a lot, how do i know which one of these http://forum.xda-developers.com/showthread.php?t=1074559 to use? As there are multiple for HTC Europe

What ROM do you have on your phone at present? Was it branded when you got it?
Go to Settings>About phone>Software information and post your software version

Any one put Rogers from into AT&T?

Anyone tried this yet? I know the boot loader is locked. But since rogers from is official as well. That should work right? Any one has directions on how to do it?
Just run the exe? Any Mac versions?

Please don't post in the development section with this kind of stuff. Thread moved.

In answer to your question, no it won't work. Model numbers between at&t and rogers differ slightly and the ruu looks for model id to verify that it is right to flash. This is by design and is good so that some moron can't flash a vivid RUU on a HOX or flash int'l ruu on an at&t
Sent from my HTC One X using Tapatalk 2

Thanks. I am a noob when it comes to htc. For xperia s. We can load other similar roms with no root or bootloadet unlock. So the only way to load rogers onto att is to wait for bootloader unlock then? Can anyone verify this?

hexproject said:
Thanks. I am a noob when it comes to htc. For xperia s. We can load other similar roms with no root or bootloadet unlock. So the only way to load rogers onto att is to wait for bootloader unlock then? Can anyone verify this?
Click to expand...
Click to collapse
Nothing to verify. This has been HTC's model for quite some time.
Sent from my HTC One X using Tapatalk 2

So only way is bootloader unlocked and then flash with official rogers rom if you are on att? So thats why everyone is all pissed about att version not having bootloader unlocked. Thanks for your info.

hexproject said:
So only way is bootloader unlocked and then flash with official rogers rom if you are on att? So thats why everyone is all pissed about att version not having bootloader unlocked. Thanks for your info.
Click to expand...
Click to collapse
Unlock bootloader
Flash cwm recovery (don't have one yet)
Flash rom
Profit
Sent from my HTC One X using Tapatalk 2

Are the bootloaders between Rogers and AT&T different? I know that when you try to unlock the bootloader, it gives you a string of numbers that you enter prior to unlocking the bootloader. If the bootloaders are the same, then theoretically us AT&T users ought to be able to use a string of numbers from a Rogers phone just to make the tool happy. Right?

mikelebz said:
Are the bootloaders between Rogers and AT&T different? I know that when you try to unlock the bootloader, it gives you a string of numbers that you enter prior to unlocking the bootloader. If the bootloaders are the same, then theoretically us AT&T users ought to be able to use a string of numbers from a Rogers phone just to make the tool happy. Right?
Click to expand...
Click to collapse
Nope. Its a hash of some sort. Its different everytime you run the command.
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Unlock bootloader
Flash cwm recovery (don't have one yet)
Flash rom
Profit
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I dont want custon rom just yet, Just rogers official rom to work on att . Do i still need cwm? No one has tried putting the rogers zip file in the root and update that way?.. You can download all the official rom from the development section. Iatt is in exe and rogers is in zip file...

hexproject said:
I dont want custon rom just yet, Just rogers official rom to work on att . Do i still need cwm? No one has tried putting the rogers zip file in the root and update that way?.. You can download all the official rom from the development section. Iatt is in exe and rogers is in zip file...
Click to expand...
Click to collapse
you're spinnin your wheels here mate.
i KNOW how it works with RUUs and the zip files they produce....i have been around for at least a few months with a few HTC devices.....
JUST having root DOES NOT mean that you can miraculously flash any file you want
unlocking the bootloader would allow you to modify the rom zip that is produced by the RUU and fastboot flash it, but you will not be able to flash the radio that comes with it, essentially all you could flash is /system and /boot
you dont think that every possibility was attempted while working on the Vivid? this aint my first rodeo.....

Pirateghost said:
you're spinnin your wheels here mate.
i KNOW how it works with RUUs and the zip files they produce....i have been around for at least a few months with a few HTC devices.....
JUST having root DOES NOT mean that you can miraculously flash any file you want
unlocking the bootloader would allow you to modify the rom zip that is produced by the RUU and fastboot flash it, but you will not be able to flash the radio that comes with it, essentially all you could flash is /system and /boot
you dont think that every possibility was attempted while working on the Vivid? this aint my first rodeo.....
Click to expand...
Click to collapse
These RUU files are funny. Way back in WM days, with the HP 6315 (htc built) I was the guy that hex edited the RUU executable to bypass the model check. I had/have VERY little programming experience but it only took me a few hours to figure it out. I wonder if this method is still feasible..........

beaups said:
These RUU files are funny. Way back in WM days, with the HP 6315 (htc built) I was the guy that hex edited the RUU executable to bypass the model check. I had/have VERY little programming experience but it only took me a few hours to figure it out. I wonder if this method is still feasible..........
Click to expand...
Click to collapse
have a crack at it, but the zip file actually contains the signature and the model check, not the exe.
if you can modify the zip file without changing the signature, then by all means, please do....
or someone could just unlock the bootloader and it wouldnt matter if the zip is signed or not, just need to edit the checks and remove the hboot, recovery, radio, adsp, etc from the zip

That would be cool. I came from sony and samsung and this is my first time with HTC. So thanks for all these info. A great help with people who just want to use stock roms from other carrier.

hexproject said:
That would be cool. I came from sony and samsung and this is my first time with HTC. So thanks for all these info. A great help with people who just want to use stock roms from other carrier.
Click to expand...
Click to collapse
after unlocking bootloader, and getting a recovery installed, you can run stock rom from any other carrier, just from a CWM version
I like having several stock rooted roms in CWM format, so I tend to knock em out as soon as I can....and get them into your hands

Pirateghost said:
have a crack at it, but the zip file actually contains the signature and the model check, not the exe.
if you can modify the zip file without changing the signature, then by all means, please do....
or someone could just unlock the bootloader and it wouldnt matter if the zip is signed or not, just need to edit the checks and remove the hboot, recovery, radio, adsp, etc from the zip
Click to expand...
Click to collapse
My skills are rusty. But back when I was dealing with the WM RUU I bypassed both the model check and also the CRC check right in the executable. Granted these security measures have come a LONG way since then, but sometimes people overlook the obvious, you know?

If the phone gets S-OFF you can set SuperCID and flash away.

Applying RUUs on Unlocked 1.14/2.22 AT&T One X

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!

[Q] going back to stock

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.

Brand New HTC One X AT&T build 3.18 -- WANTING ROOT/UNLOCK/S-OFF

Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.

Bubbled said:
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
Click to expand...
Click to collapse
Unfortunately the answers are no and no. JB is decent even on fully stock AT&T, you will just have to look the other way when scrolling through your app tray

I don't think the current root methods allow for the 3.18 build to gain root. Might be in the 2.20 boat all over again until someone can find a definite procedure.

soooooooooooooooooooooo lame. my rezound had viper rez rom and it was based off one x jb but had all the tweaks and stuff so right now its like a major downgrade lol
guess i'll cry and wait for the HTC One to come out later this month, since i only grabbed the one x cause it was literally 11 cents at walmart with a 14 day return and my rezound is acting up and randomly restarting/tanking battery!
sigh
thanks for the info though Groovy

Bubbled said:
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Click to expand...
Click to collapse
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...

lightflier said:
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
Click to expand...
Click to collapse
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2

iElvis said:
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OK...

I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure

juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Sent from my Nexus 7 using xda premium

panda_mode said:
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Click to expand...
Click to collapse
Damn that's annoying! If that were me I would sell my AT&T phone and with the cash buy an overseas One XL model with 32GB

juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).

redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Sent from my VENOMized HoxL

area51avenger said:
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Click to expand...
Click to collapse
I suppose it doesn't hurt to try. Otherwise, I'd just take the phone back, if root/S-off, etc. is important to the OP. I assume 11 cents is a subsidized price. So no point in using up an upgrade on a phone that can't be modded, if he wants to get the HTC One when its released.
OP may also check to see if the store has any older stock with 2.20 firmware (or any previous firmware version except 3.18). Phones with 3.18 out of the box must be very new, so I wouldn't be surprised if they had some older stock also.

I returned the one x today. will be looking into the t-mobile version of the HTC One which they told me comes out friday the 22nd. being a new phone i know i wont be able to do any mods or anything for a while, but that won't take long with the awesome Devs we have here! All the other models of the One X were sold out, and im guessing that someone realized that the new firmware was Out of Box so picked em all up. only had 2-3 stores with one each so its possible. now all the new stores have the new firmware no big deal, i'd prefer an HTC DNA anyways, but we'll see what the One is all about.

redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.

Techinstein said:
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Click to expand...
Click to collapse
Yes, the CID for AT&T is cws_001 on all of the previous firmware versions, as well. This hasn't changed. cws__001 is blocked on HTCDev.com.

So i have the key for my past bootloader unlock can i use it?
Enviado desde mi HTC One X usando Tapatalk 2

coldrazor said:
So i have the key for my past bootloader unlock can i use it?
Click to expand...
Click to collapse
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.

redpoint73 said:
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.

exad said:
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
Click to expand...
Click to collapse
Really? Kinda negates part of the purpose of having S-off, doesn't it?