Related
Hi all.
I have A HTC Sensation, on Orange (UK).
The handset was completely standard, untouched. I have followed the guide to unlock my bootloader using HTC dev.
It seemingly worked, and I held volume down and pressed power and verified that the text at the top said "UNLOCKED". great
When I booted the phone, it gave me the "fresh start" intro screens, which I followed through on.
Once completed, the phone loaded to the normal home screen, but now gets no signal. Its always 0 bars and "NO SERVICE" warning.
Only thing I have done is as above, so unsure what could have gone wrong?
Only thing I can think is that I chose the wrong "what phone do you have" option on HTCDev. I chose HTC Sensation (EU), as the phone is not on tmobile, and not vodafone, and IS european. However, tmobile and orange are now part of the same umbrella company, so perhaps something bad happened there?
Unsure what I should do next? Re-lock the bootloader? Any suggestions very gratefully welcomed! Thanks
Hmm.. that's really weird. Unlocking the bootloader doesn't affect your cell phone signals. I would run a RUU and see if that fixes the problem.
Here's the guide: http://forum.xda-developers.com/showthread.php?p=26541170
Follow steps 2&3.
Before you do, try taking out your sim and putting it back in. I highly doubt you put your sim in the wrong way, but I did this before (I don't think I'm the only idiot out there)
Sent from my HTC Sensation
Thanks. I'll follow that guide.
SIM card is in OK. Was I supposed to remove the SIM when I was unlocking the bootloader? I didn't do that.
Just waiting for the RUU file to download.
The guide says I need one with a higher or equal version to my main version. My main version is 3.x and the highest version I can find via the links in the guide are 1.x. Will this be ok?
I'm really not sure how the phone got this screwed up.If I did select the incorrect device type in HTCDev (i.e. I selected Sensation EU and should have selected Sensation Tmobile) would that possibly cause this problem?
Would it be worth re-locking, then unlocking using the tmobile device? Guessing I would be supplied with a different unlock_code.bin?
EDIT: Just checked and the tmobile device choice is actually for "tmobile USA", so looking like I chose the correct device after all.
RUU I had failed. As I say my version is 3.x and this was 1.x so I'm not surprised.
My exact version reads: 3.32.61.51
Can anyone suggest a RUU file that I can have a go with, or any other suggestions?
Bootloader is currently RELOCKED.
Thanks
Did you try this ruu?
http://www.shipped-roms.com/downloa...0U_10.51.9007.27_M3_release_198549_signed.exe
EDIT: try looking for your ruu here: http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
The general ROM section has 3.32 versions.
Sent from my HTC Sensation
Yes, I tried the first one you posted, which wouldnt work (too old presumably).
I will try one of the unbranded ones; but unsure if they are suitable as I have an Orange logo when I boot?
Thanks
Still waiting for the RUU to download, so will probably carry on looking at this in the morning now.
A little more info that might give someone an idea:
If i go into settings, and click on "Mobile settings" and go to choose carrier, the phone searches for carriers.
25% of the time it says "no network found"
75% of the time, it finds O2.
25% of the time it finds 3 or vodafone
It never finds orange. It seems it IS looking for networks though?
If I put the SIM card in my very old dumb-phone, it finds orange fairly quickly and connects.
Thanks for any help
There's another option. You can try to s-off your phone with ganeshp's guide and then flashing the 3.33 firmware which contains the newest radio and stuff.
Here's s-off guide without HTC dev unlock: http://forum.xda-developers.com/showthread.php?p=26280760
Here's the firmwares for sensation: http://forum.xda-developers.com/showthread.php?p=21711154
Sent from my HTC Sensation
AndroidSupporter318 said:
There's another option. You can try to s-off your phone with ganeshp's guide and then flashing the 3.33 firmware which contains the newest radio and stuff.
Here's s-off guide without HTC dev unlock: http://forum.xda-developers.com/showthread.php?p=26280760
Here's the firmwares for sensation: http://forum.xda-developers.com/showthread.php?p=21711154
Sent from my HTC Sensation
Click to expand...
Click to collapse
actuallly it is better to use auggie2k's guide because he has done htcdev unlock
But he relocked it... on the 5th post
Sent from my HTC Sensation
Hi guys
Thanks to you both for your suggestions.
This morning I unlocked the phone once more, and still had limited service. I then re-locked once again, and as soon as the phone booted it had full service, and has done ever since.
I have no idea what went wrong (they HTC Dev article is pretty straightforward, so I don't think I did anything wrong), and the action that I did above (unlock, relock) I must have done 5 times last night without any effect.
I am still determined to root the phone, so will probably end up with another broken handset soon But at least I will be doing it at the weekend this time, instead of midnight on a Thursday when I have to work at 7 the next day!
Thanks for all the help, I'm sure I'll be back with more questions (problems!) soon.
No problem! Glad to try to help
Sent from my HTC Sensation
Following this minor hiccup (still no idea why it happened) I've now got managed to:
Unlock
Root
Install recovery
Get SU
Get S-off
So thanks for all the help. I'm a complete beginner, but the guides on this site are great and really easy to follow.
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.
Hey Folks,
This is my first post in the Sensation forums, i've been reading topics for a few days, but I didn't find any solution to my problem and i'm starting to get annoyed by it.
I've obtained a HTC Sensation a few days ago, and as with my previous devices (Galaxy Gio, Optimus Black) I wanted to flash a custom rom on it. I happened to unlock the bootloader of my friends Sensation few weeks earlier, so i thought this was going to be a piece of cake.
Well it wasn't, I couldn't unlock the bootloader using HTCdev method because the phone is vodafone branded. I tried numerous things, i wasn't able to perform the juopeanutbro (?) trick, tried flashing a custom hboot through fastboot (JB_hboot.zip) in linux (gave me an error 42 "Remote: Custom id check failed" or something like that). And after a few days of trying and trying i'm getting tired of it.
So my question is, is there any option i missed to achieve S-OFF or unlock bootloader? I'd love to flash a custom rom on it because I don't like the 4.0.3 Firmware which the phone is running now.
Phone Details:
Android version: 4.0.3 (vodafone)
HBOOT:1.27.0000
Radio: 11.29A.3504.18_M
CID:VODAPE17
Did you select the Vodafone model there in list of HTC dev...
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
Ihttp://forum.xda-developers.com/showthread.php?t=1668276
If htc Dev method doesn't work for your phone, use the non htc Dev method. Follow everything on the screen, do not run out of battery power (that will probably brick your phone)
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Redjack77 said:
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Click to expand...
Click to collapse
has your motherboard been replaced?
what error did you have?
It's not that impossible, I did it in like 10 tries, there are YouTube videos timed exactly so you know when to connect and disconnect the wire. plus you can try as many time as it takes so you really can't go wrong... You know both method require the insulated wire right? It's just one requires the more accurate timing
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Redjack77 said:
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Click to expand...
Click to collapse
what does it say in the top?
juopunutbear or locked?
also i can't view the pics
can you post here in a post?
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://, because i can't include links in my posts as I have lest than 10 posts submitted.
But I actually have solved all my problems, because I knew juopeanutbear had unlocked bootloaders available on his website and in fastboot you are possible to flash these with the command "fastboot oem rebootRUU" wich put the device in RUU update mode, and then flash the unlocked HBOOT from juopeanutbear's website with the command "fastboot flash zip jb_hboot.zip.
Note (to people who might find this useful in the future): The devices sticked on showing a green loading bar in RUU update mode after entering the second command, on the command prompt it showed done, but the device didn't reboot or what. Just wait a while (to be sure) and enter command "fastboot reboot-bootloader"
Now my fastboot screen shows **Juopeanutbear** instead of ***locked*** and I've already managed to flash clockworkmod SUCCESFULLY!!!!!!!
Now I will replace CWM by 4ext and i'm good to go I guess, how I managed to get S-off will remain a secret for me, I assume I did do the wire-trick correctly after all, but didn't notice (you know,, spending a few nights behind your PC doesn't give you a clear state of mind
Redjack77 said:
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://,
Click to expand...
Click to collapse
you are right
i included also the h t t p : //
so you managed it yourself
crongats
now it is time for a custom rom
note: probably after achieving S-OFF you chose no for installing the jb hboot
Running Team Venom's Viper sense 5 rom and just like I expected I LOVE IT!!
HTC Sensation XE
Networked unlocked (was previously locked to O2)
I acquired the phone via courier and ordered through O2.co.uk
Android: 4.0.3
Software: 3.32.206.151
Sense: 3.6
PYRAMID PVT SHIP S-ON RL
HBOOT: 1.27.0000
Carrier ID: O2___001
Kernal: 3.0.16-gc764bfb
Baseband: 11.69A.3504.00U_11.23.3504.07_M2
Build: 3.32.206.151 CL348082-release keys
Using a Windows XP SP3 machine for running android SDK etc.
Hello!!
I have recently moved providers and wanted to install a non-O2 HTC 4.0.3 on my device.
I have no experience of rooting or anything beyond installing .apks not sourced from Google Play.
I went about reading through a ton of tutorials and learned that I needed to unlock my Bootloader, root/SU the device, make S-OFF, flash the recovery, and then I would be in a position to put another non-O2 ROM on.
I found this thread and as it seemed to be related to a respected XDA member, decided to follow it
http://www.flow-wolf.net/2012/09/how-to-root-your-htc-sensation-xe-4g.html
and got the bootloader unlocked.
After getting SU/Root (a prerequisite for using the Wire Trick) via this thread
http://forum.xda-developers.com/showthread.php?t=1632553
I began to work my way through http://www.flow-wolf.net/2012/09/how-to-s-off-htc-sensation-xe-4g.html to get S-OFF. However when running ControlBear.exe in ControlBearRelease_pyramid_ICS_WIN, I was getting a "unable to create secondary backup" error, or something very similar. Google led me to http://unlimited.io/jbtroubleshooting.htm "This is often caused by a Custom ROM or having HTC Sync installed on your PC."
So I uninstalled HTC Sync, went through the process again but the error persisted.
So I do not have a custom ROM installed as far as I know, but maybe the term "custom" refers to anything that is a modification of the installation that the device was shipped with. I honestly can't remember which Android version the phone was running when I got it.
My question is, it is worth me trying to roll back to whichever version was probably shipped with the device? If it is, where would I find exactly what I'm looking for? I read through this guide http://forum.xda-developers.com/showthread.php?t=1672425 but can't find any downloadable RUUs that have a CID of 001 in, and as I said, I'm not sure which version I would need to look for.
No one will die if I have to keep the O2 software on the phone, but as a last resort I am posting here in the hope that someone will point out the obvious/call me an ignorant n00b etc. but ultimately point me in the right direction
Thank you!
if you just want to flash custom rom then you can do it without S-OFF
see this thread
http://forum.xda-developers.com/showthread.php?t=1631861
note: by the way for the controlbear.exe use usb 2.0 ports not 3.0(it is more preferable the back one)
install htc drivers
uninstall htc sync as you said
enable usb debugging mode from settings
also you have the original stock rom(since you are on S-ON(i assume also LOCKED)
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).