Database Info

[Q] is it possible to have a root withour doing s-off?

Can i root my asian sensation and keep my phone s-off? If so, how?

Are you serious? Hurrp Durrp use the search.

of course not

S-off means writing to /system. Root requires write access to /system in order to get the app + 18056377243 binary.
So no.
Sent from my HTC Sensation 4G using XDA App

idan_mo said:
Can i root my asian sensation and keep my phone s-off? If so, how?
Click to expand...
Click to collapse
geoffcorey said:
S-off means writing to /system. Root requires write access to /system in order to get the app + 18056377243 binary.
So no.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Technically the answer is YES on the Sensation because you can use the HTC unlock method to install a custom recovery and flash Superuser to give your current Rom root access without going S-Off.
But using Revolutionary to S-Off your phone is the superior method to use and gives you more options in the future.

tpbklake said:
Technically the answer is YES on the Sensation because you can use the HTC unlock method to install a custom recovery and flash Superuser to give your current Rom root access without going S-Off.
But using Revolutionary to S-Off your phone is the superior method to use and gives you more options in the future.
Click to expand...
Click to collapse
Using the htc method still gets you to s-off, and then end goal the person doesn't want.
You cannot write to /system without some sort of s-off. And the htc way is one of the two ways to get s-off.
Sent from my HTC Sensation 4G using XDA App

geoffcorey said:
Using the htc method still gets you to s-off, and then end goal the person doesn't want.
You cannot write to /system without some sort of s-off. And the htc way is one of the two ways to get s-off.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Whatever dude. The HTC Unlock method unlocks the boot loader, but it still reports S-Off as indicated by several posts in this thread:
http://forum.xda-developers.com/showpost.php?p=16865964&postcount=71
When you boot into the unlocked boot loader, the boot loader commands have
special access to some of the partitions such as /system, but you are limited by what the commands can flash.

yup. the HTC method while gives you s-off doesn't allow you to root the phone or install a custom ROM.

I had read through the user guide at XDA, about the uninstall HTC SYNC. Uninstall HTC sync is on HTC phone or computer or both?
It is Rooting method for Samsung Galaxy S2 and HTC Sensation is different?

jordontin said:
I had read through the user guide at XDA, about the uninstall HTC SYNC. Uninstall HTC sync is on HTC phone or computer or both?
It is Rooting method for Samsung Galaxy S2 and HTC Sensation is different?
Click to expand...
Click to collapse
You only need to uninstall HTC Sync on your PC, not the phone.
Yes, the rooting process is different between SGS2 and HTC Sensation.

If i using Revolutionary tool to S-OFF and root the HTC Sensation, does it make changes on stock ROM, Kernel, driver (e.g 3G), etc?
It is Revolutionary tool compatible for all version of the HTC Sensation? Because i'm from Malaysia.
If my HTC Sensation got hardware problem need to claim warranty, can i unS-OFF and un-root it?

jordontin said:
If i using Revolutionary tool to S-OFF and root the HTC Sensation, does it make changes on stock ROM, Kernel, driver (e.g 3G), etc?
It is Revolutionary tool compatible for all version of the HTC Sensation? Because i'm from Malaysia.
If my HTC Sensation got hardware problem need to claim warranty, can i unS-OFF and un-root it?
Click to expand...
Click to collapse
Doesn't change anything, you just get access to write to /system and all that good stuff. Yes revolutionary is compatible to all sensations.
You can also revert to s-on per the same guide to s-off.
If its a hardware problem that has absolutely nothing to do with software(like volume rocker falling off) then I don't c y it should b a problem claiming warranty regardless if ur s-off/on.
Sent by my feau gee

I understand that HTC will release a new update for all HTC device to unlock the bootloader.
Recently i just got an software update fromHTC. Software number is "1.45.707.1" running Android 2.3.4. It is this software number already unlock the bootloader?
If the bootloader already unlock do i need to S-OFF in order to root my HTC Sensation?

What are the different in between S-OFF and unlock bootloader?

jordontin said:
I understand that HTC will release a new update for all HTC device to unlock the bootloader.
Recently i just got an software update fromHTC. Software number is "1.45.707.1" running Android 2.3.4. It is this software number already unlock the bootloader?
If the bootloader already unlock do i need to S-OFF in order to root my HTC Sensation?
Click to expand...
Click to collapse
The update itself doesn't automatically unlock the bootloader of all sensations...it only makes them compatible with HTC's unlock tool.
If you don't mind me asking, is there a reason that you seem to want to avoid the revolutionary unlock? It's generally regarded as the better method since its reversible and doesn't require you to reveal to HTC that you're unlocked.

I want root my HTC sensation on the safe way, so i need to do some research. Because i still new on rooting android device.
After S-OFF the bootloader, do i need to check compatible of baseband version and build number before i root the HTC sensation?
What i know is for Samsung Galaxy S2 need to check this.

jordontin said:
I want root my HTC sensation on the safe way, so i need to do some research. Because i still new on rooting android device.
After S-OFF the bootloader, do i need to check compatible of baseband version and build number before i root the HTC sensation?
What i know is for Samsung Galaxy S2 need to check this.
Click to expand...
Click to collapse
IMHO, revolutionary is the safer method to unlock since you can reverse it for warranty purposes. Supposedly HTC will honor hardware warranty issues even if you use the official unlock but I can't confirm that (they did with my nexus one though). Why risk getting denied though?
AFAIK, all current bootloaders, radios (basebands), and ROMs are compatible with each other in the sense that it will work. Some radios work better with some roms but no combination that I'm aware of will result in a brick. It's not like the G1 days where you had to make sure that your radio was compatible with your SPL and flashing them in the wrong order would make the device unbootable.

So I will have to s-off with Windows and then I can root with my Mac ? Sorry for sounding dumb...... Just still stuck in iPhone land lol htc sensation with 2.3.4
Sent from my HTC Sensation 4G using Forum Runner

You don't have to do anything to root unless you're going to stay on the stock rom. Custom roms are already rooted. To root a stock rom, you flash the root files from recovery, no pc needed.

moto211 said:
You don't have to do anything to root unless you're going to stay on the stock rom. Custom roms are already rooted. To root a stock rom, you flash the root files from recovery, no pc needed.
Click to expand...
Click to collapse
I would like to check out custom roms ..... I updated to 2.3.4 and that should be ok ?
Sent from my HTC Sensation 4G using Forum Runner

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!

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?

So has anyone heard of bricking while....

So has anyone heard of bricking while flashing a stock rom on an rooted locked device?
I pulled down the official HTC AT&T ROM for the ONE X (original) this afternoon (a few minutes ago) and flashed it via my laptop and the HTC cable that came with the phone. It went along just fine and at about 30% it started going slower on the amount of time between percent increases then sped up around 34-35 percent to complete.
When it was done I had a success message from the RUU installer and a device that would no longer power on. Version CID__001 again an AT&T HTC ONE X
I'm getting the dreaded QHSUSB message in windows now

Wait, you have a dual-core AT&T One X? And CID__001? Because that is a cid for the Tegra One X.

iElvis said:
Wait, you have a dual-core AT&T One X? And CID__001? Because that is a cid for the Tegra One X.
Click to expand...
Click to collapse
Released May 12 thish?! AT&T HTC ONE X

Which RUU?
SuperCID + S-on + 3.18 RUU = brick.

The at&t htc one x stock cid is cws__001
Sent from my HTC One X using xda premium

panda_mode said:
The at&t htc one x stock cid is cws__001
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This was the file name: RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe
I usually don't unlock etc... until I am out of warranty which I am not.

hx4700 Killer said:
This was the file name: RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe
I usually don't unlock etc... until I am out of warranty which I am not.
Click to expand...
Click to collapse
Oh okay. I'm not all knowledgable in this area either. I just know that the cid for my AT&T one x before I supercid is cws__001
Sent from my HTC One X using xda premium

panda_mode said:
Oh okay. I'm not all knowledgable in this area either. I just know that the cid for my AT&T one x before I supercid is cws__001
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It may have been CWS. Don't recall.
The only reason I even know what a "CID" is would be because I saw a list of devices for whom JB was available for and I had to know my CID to find out if I was eligible. I used the fastboot getvar cid to see what it was and It was either CID or CWS __001

hx4700 Killer said:
It may have been CWS. Don't recall.
The only reason I even know what a "CID" is would be because I saw a list of devices for whom JB was available for and I had to know my CID to find out if I was eligible. I used the fastboot getvar cid to see what it was and It was either CID or CWS __001
Click to expand...
Click to collapse
If you never modded the phone, its CWS__001.
There have been some isolated cases of people bricking on bone stock, never-modded phones when updating. It happens when something goes wrong in the middle of flashing the new firmware so that hboot or some other critical element gets corrupted.
You're due for a warranty return.

iElvis said:
If you never modded the phone, its CWS__001.
There have been some isolated cases of people bricking on bone stock, never-modded phones when updating. It happens when something goes wrong in the middle of flashing the new firmware so that hboot or some other critical element gets corrupted.
You're due for a warranty return.
Click to expand...
Click to collapse
Yeah, its in the mail to them already. The tech was nice on the phone but basically told me he had never heard of such a thing happening before so if I was sure it hadn't been modified then the warranty would be honored.

Languages, Radios, and Roms/RUU

Hey all,
Here's my situation. I just picked up a USA TMO HTC One S and will be sending it to a cousin in Greece.
Would there be any complications if I flash the generic EU RUU/rom (which one is the newest?!?) to the TMO HTC One S? I would try it, but I have no way of knowing how reception would be (if it works!) since I'm in the USA.
It's been a while since my Sensation died (had plenty of experience with that and the radios) and I'm currently used to how Sony does their radio (xperia ion right now).
Thanks!
edit: nm, I found a near stock clean TMO rom with the languages enabled, just going to use that one.

Which rom is it?
Sent from my SGH-T889 using Tapatalk 4

You can not run the European RUU on a stock TMobile HTC one S. You have to first unlock your bootloader, install custom recovery and root your phone. Download this guy's toolkit it is simply awesome
http://forum.xda-developers.com/showthread.php?t=1604677
Then you have to follow this guide to obtain SuperCID (a universal CID that lets you run any RUU, in your case the European one)
http://forum.xda-developers.com/showthread.php?t=1671643
Then download the RUU from androidruu.com and run it. Hope I helped