Hi All.
Quick question, I have rooted my sensation and s-off'ed, sweet.
Here is me question, what happens if our friends at HTC update the part that made the s-off possible? Will we get the updates or will only the users who did not tinker with the firmware get them?
Cheers folks.
HTC has stated that there new HTC-DEV site will be where you will be able to S-off your device, its not gonna come in an OTA push, IMO revolutionary has got us S-off, so who care what HTC has coming for S-off....its a little late, besides if you S-off with HTC they want to document who is S-offing their devices.......eff em and just enjoy your no strings attached S-off.
Number 1...It is never a good idea to take an OTA on your phone if you have it rooted.
Number 2...OTA's may contain patches to exploits that were used to obtain s-off.
Number 3...OTA's may or may not s-on your phone depending on how the devs obtained s-off in the first place.
Moral of the story is if you want to maintain root never OTA
i own a sensation device
if i use this revolutionary tool to s-off, recovery and root, is it possible to s-on later? (e.g. to give my phone to htc service to be in warranty)
If i just use the ruuxxxxxx.exe for my device to put the official rom , the phone will be s-on again? or is there any other way?
and wht about official OTA updates? how is going to be achieved?
There is a way to to gain s-on again but it's risky atm. Look for the guide in the stickies in the development forum.
You will not get an OTA on a rooted custom ROM.. end of story!!
So enjoy
emm_stra said:
i own a sensation device
if i use this revolutionary tool to s-off, recovery and root, is it possible to s-on later? (e.g. to give my phone to htc service to be in warranty)
If i just use the ruuxxxxxx.exe for my device to put the official rom , the phone will be s-on again? or is there any other way?
and wht about official OTA updates? how is going to be achieved?
Click to expand...
Click to collapse
Yes it is possible to make you device s-on again just be sure to follow everything to the letter and don't screw up. Also why would you want to. If anything permanently root it and stick with that.
HTC Sensation Stock Perm_Rooted 4.3.3
HTC Sensation Stock Perm_Rooted 4.3.3
Bobguy21 said:
Yes it is possible to make you device s-on again just be sure to follow everything to the letter and don't screw up. Also why would you want to. If anything permanently root it and stick with that.
HTC Sensation Stock Perm_Rooted 4.3.3
HTC Sensation Stock Perm_Rooted 4.3.3
Click to expand...
Click to collapse
thank you
what about the other questions???
Sorry it took so long you cannot update when rooted. Because of clockworkmod recovery. But just install a stock bases ROM the has the update like I did. hope this helps.
HTC Sensation LeeDroid 2.3.4 Perm_Rooted
Hi, will be revolutionary team work on the update? Or is some other easy way how to make the S-OFF?
HTC Desire S
S-ON
HBOOT 2.00.0002
See the thread to downgrade hboot. Then it will be easier
-------------------------------
Sent from my HTC Desire S
Yes, but if I want downgrade HBOOT, I must break my warranty with official HTCDev tool. I don't want break warranty. Is other way? Will revolutionary work on new version?
Revolutionary wont work unless you downgrade (for now)....
Revolutionary will break warranty aswell...
spajdo said:
Yes, but if I want downgrade HBOOT, I must break my warranty with official HTCDev tool. I don't want break warranty. Is other way? Will revolutionary work on new version?
Click to expand...
Click to collapse
If you want to S-off in the first place, you lose warranty.
If you don't want to lose warranty, why bother trying to S-off?
-------------------------------
Sent from my HTC Desire S
yes, revolutionary break warranty, but is here a thread to S-ON and unroot. And if I break warranty with HTCDev.... they (HTC) know that my device was S-OFF.
I want try CUSTOM ROM but If my phone will be broken I want apply waranty service.
i found a way to downgrade without using HTCDEV Unlock
see Desire S General Forum, there is a howto!!!
hi
sorry for noob question.... I've got a vodafone branded sensation... What exactly I risk if flash a ruu that it's not the correct one to return s-on??
If you're S-OFF without modifying your CID, it won't work, and it may possibliy brick your phone. If you're S-ON, it won't work.
Just flash the correct ruu, read the guides close if you're returning to S-ON, I've seen some people bricking their phones after running the ruu
xdviper said:
If you're S-OFF without modifying your CID, it won't work, and it may possibliy brick your phone. If you're S-ON, it won't work.
Just flash the correct ruu, read the guides close if you're returning to S-ON, I've seen some people bricking their phones after running the ruu
Click to expand...
Click to collapse
I'm s-off, without modifying CID... Which is my correct ruu? The one I had when bought the phone? The one I have now (I'm stock to vodafone last update)?
yo dude, sorry to butt in, but.. do you happen to be in australia?
hi..
i am all stranger to HTC world.. i have been using galaxy s, s2 and ace.. things were easier when it came to rooting and flashing custom roms.. or at least there was less terms.. 3 days ago i bougth Sensation XE and since then i have been reading every page but the more i read, the more i get cunfused...
so, what i want is basically trying new kernels, OCing, using apps like setcpu or titanium backup etc.. in order to do these rooting the device was enough with the galaxy devices.. but here there are lots of terms..
here is what i think i understand;
S-off= this means unlocking the NAND part to be re-writable i guess.. the funny part is; i want to root the device and i guess i have to S-off the device but it says in order to S-off the device you must have alredy rooted it? or i am wrong?
Hboot version=i think this is very important since we have to choose the methots according to this... mine is 1.27.0000
super CID= no idea what this is.. but i assume it has no important role on rooting..
and there is the bootloader unlock option= htcdev.com is doing it but they say if i do it my phone is out of warranty.. it is just a 3 day phone and i dont want to lose the warranty... and i also have read some post about it not being a complete unlock.. so any method other then offical HTC ones would be better for not losing the warranty (i am sure even if i lock it back when its necessary, HTC will still have the records of me unlocking my device and wont let me use the warranty) ..
and there is this guide on the development section, it is really helpfull but the date of it tells me it was before ice cream sandwich update and 1.27.0000 hboot version and some of the instructions confirms that... so i guess i need some other method to root my device ... (after everything i am not even sure if the rooting is excatly what i need)
long story for short; i am lost among the terms and instructions.. especially after i tried to S-off my device in order to root and learnt it needed to be rooted first in order to be S-off .....
so please help me with the terms and instructions..
thanks ..
Okay, root is not needed to s off.
S-off disables the security on your bootloader.
Supercid means you can flash any piece of software no matter what area or network it was intended for, as each one has a cid code that restricts the software to the network or countrys phone e.g. unbranded sensations cid is HTC__001 and Vodafone would be VODA__xx. Supercid changes your cid to 11111111 which means everything that is protected by any cid code will work on your phone.
Back to s-off, using revolutionary tool is pretty easy as long as you follow the instructions correctly but will not work on hboot 1.27 so it requires downgrading using an ruu or eng. Hboot 1.17 or finding another method to s off 1.27, once s off using revolutionary all you have to do is flash a custom recovery and then flash superuser and voila your rooted. But you can also s-off, install custom recovery, upgrade firmware to 1.27 and flash a prerooted custom Rom which obviously does the trick. Just make sure to keep a track of what firmware you are on and make sure it works with what your doing and the Rom you're using. Oh and htcdev unlock is not necessary as you can flash a firmware with a unlocked bootloader plus revolutionary also unlocks bootloader. And as far as warranty goes, once s off or bootloader is unlocked your warranty is VOID.
Hope this helps
Sent from my HTC Sensation XE with Beats Audio using xda premium
Fİnally! everything makes sense thanks a lot..
so the first step is to downgrade to a firmware which i can S-off and unlock, then to get back to pre-rooted version of my current firmware..
so i assume just like i can downgrade, S-off and unlock, i also can upgrade, S-on and lock back when i need the warranty?
Almost firmware contains the radio and Hboot etc, to obtain root you just first s off on the downgraded firmware, then upgrade to an unlocked firmware that is for ics. The firmware for ics is 3.32 which contains Hboot 1.27 but of course you cannot s off on this version of Hboot. Then flash a pre rooted ROM once you have gone back to ics firmware using a custom recovery. Once s off, you will not lose it when upgrading to a new firmware. But to s-on is risky but if you manage to do it without semi bricking your phone and then flash a locked bootloader HTC will never know you've voided your warranty as long as your on an unrooted Rom. I will pm you a great link for doing this and explaining as I know this is confusing. I won't post it here because its on another forum.
Sent from my HTC Sensation XE with Beats Audio using xda premium
this really explains everything.. its just like showing the entire map and also telling the route.. thank you very much, you are the best
No problem if you could hit the thanks button I would greatly appreciate it
Sent from my HTC Sensation XE with Beats Audio using xda premium
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.