Database Info

how to S-ON HTC wildfire after revolutionary!

HI everyone. i have started this thread as i didnt know what to do when i first had to send my wildfire back for repairs. first download the attatched zip. unzip to desktop and make sure u have got the drivers for your bootloader interface already installed. to do this you will need just two things. the zip you have just downloaded and the HBOOT which i included inside the ziped file. once extracted run the java file named S-ON.jar and plug your phone in and turn on fastboot. once connected make sure you click on check connection. once you have done that you should see your serial number appear. okay your ready to go. look for the first tab and click on it. then click on HBOOT/SPL. locate the HBOOT file you inzipped with the S-ON tool and then click it. once done just click on flash HBOOT/SPL. once done you will see it says FLASH HBOOT/SPL/SUCCESS. thanks for takuing time to look at my GUIDE and i hope it helps you. just remember one thing only flash the new HBOOT after you have installed the RUU which is android 2.1 update 1 so you can root again.

thanks for posting this, gonna try it now since I have to send my wildfire in for repair..

no problem if you have any trouble let me know and ill help you gain s-on

Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular

kaefert said:
Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular
Click to expand...
Click to collapse
this will not work with xtc clip i have 1 other way tho. please try this.
go into you start menu click RUN the type cmd in the dialog box. when you have the cmd up type C:\fastboot>fastboot oem mb 9C068490 1 30 then it will say okay. then open the s-on tool then try to flash the HBOOT. let me know if you have anymore problems. but this way shud work for you
they will not accept it as they just have to go into the HBOOT menu and they will be able to see it is s-off. and they will send it back as it is and wont carrie out any sort of repairs on it as you have hacked the phone and comprimised the security software

hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed

kaefert said:
hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed
Click to expand...
Click to collapse
okay no worries. if they wont repair it. then get back to me and ill cook somthing up and get you back to s-on. this is the trouble when gaining s-off with a xtc clip. its a pain to get back to s-on again lol but good luck anyways

Thanks for the moral support, I hope they will repair it...
Well back then I had no chance, my Wildfire was delivered to me with hboot 1.01.001 back in the time where there was no software S-OFF method for 1.01.001 and up, so I found myself a shop that had an XTC-Clip and invested 10€ on him

Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again

kaefert said:
Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again
Click to expand...
Click to collapse
Great news for you mate im glad they sorted it out for you. and your very lucky as they sent mine back twice for being s-off lol.

lol, where are you from? and where did they send your device? Im from austria and they sent my device to slovakia and they gave me a slovenian report of what they did so I had to use google translate to understand it

[Q Solved] Still ****LOCKED**** after rom update?

I'm using Android Revolution HD ICS ROM from mike since a couple of days,
but i noticed that i'm stil ***locked*** in de Boot menu.
I want to flash my radio, but this is not working now.
What do i need to do to get in in -revolution- ? If you know what i mean.
I think that i've forgot a step while updating the rom...
screen shows:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2

There have been many people with the same issue. Please do some research, educate.
All that means is fastboot commands aren't going to work, most people rarely use them so you'll be fine.

Oke thanks, but do you know what i need to do to get it fixed?
(for my education)

Well you can flash a new update with the revolutionary bootloader. Kohr-Ah has a tidy selection with everything you could need located at http://forum.xda-developers.com/showthread.php?t=1459767
Head over to the second post and find the section that matches your carrier/CID. Download the 3.24 Unlocked version for your CID and put it on the root of your SD. Now, reboot your phone while holding volume down. The bootloader will detect the PG58IMG file and ask if you want to perform the update. Hit volume up, and it'll update a few things. Then, it'll reboot back into the new bootloader and update the rest. After that, make sure you have an ICS based rom (preferably one built from the 3.24 base, and you're all set. Be sure to delete the PG58IMG after updating, because the bootloader will pick it up every time and refuse to do anything else until it's gone.
Edit: However, I forgot to mention, it really depends on what you mean by "fixed", because you can currently run any rom and do most anything even with a locked bootloader. However, since it is a ten minute fix, I suppose it's worth doing.

tbeelen said:
Oke thanks, but do you know what i need to do to get it fixed?
(for my education)
Click to expand...
Click to collapse
You dont need to fix it you r soff so u can flash any Rom. If you want to unlock bootloader then u can get it done by htcdev.
Sent from my HTC Sensation Z710e using xda premium

Going back to S-on for RMA

HI guys,
Had a quick search on my phone and couldn't find anything in this section, do forgive me if there's already a thread that explains this.
Basically, my phone keeps randomly rebooting, and sometimes only boots to them shut itself down again, no matter what rom, radio or hboot it's on, so I decided that I'm going to have to take it back to o2 as it's still under warranty.
The only problem is, I'm rooted and want to return to s-on. I've Google'd how to do this on the Sensation and found that you can do it via the ruu, but this can sometimes brick your device, is there any easy way to do this with clockwork installed etc?
If it helps, I'm running 4.03, latest radio and latest hboot, the baseband version states this: 11.76A_3504.00P.11.24A.3504.11_M
Thanks in advanced,
Dan

DanielF50 said:
HI guys,
Had a quick search on my phone and couldn't find anything in this section, do forgive me if there's already a thread that explains this.
Basically, my phone keeps randomly rebooting, and sometimes only boots to them shut itself down again, no matter what rom, radio or hboot it's on, so I decided that I'm going to have to take it back to o2 as it's still under warranty.
The only problem is, I'm rooted and want to return to s-on. I've Google'd how to do this on the Sensation and found that you can do it via the ruu, but this can sometimes brick your device, is there any easy way to do this with clockwork installed etc?
If it helps, I'm running 4.03, latest radio and latest hboot, the baseband version states this: 11.76A_3504.00P.11.24A.3504.11_M
Thanks in advanced,
Dan
Click to expand...
Click to collapse
Follow these steps:
1. Flash an RUU - It doesnt matter which one but I would recommend the latest 3.33.401.6 RUU - WARNING: THIS STEP MUST BE DONE, FAILURE TO DO THIS STEP WILL RESULT IN A BRICKED DEVICE!
2. Once the RUU has done its thing, boot into bootloader, connect to pc, go to fastboot usb mode and type the following command:
fastboot oem writesecureflag 3
All done

To add on the post above me, if the RUU.exe is unable to find your device, install the "Universal_Naked_Driver_0.7" drivers. Worked for me.

Jonny said:
Follow these steps:
1. Flash an RUU - It doesnt matter which one but I would recommend the latest 3.33.401.6 RUU - WARNING: THIS STEP MUST BE DONE, FAILURE TO DO THIS STEP WILL RESULT IN A BRICKED DEVICE!
2. Once the RUU has done its thing, boot into bootloader, connect to pc, go to fastboot usb mode and type the following command:
fastboot oem writesecureflag 3
All done
Click to expand...
Click to collapse
1.RUU corresponding to his device must be chosen for rma purposes.. Otherwise they won't accept it.. They will check the main-version too which varies for each RUU
Also running RUU as a exe ( not manually flashing) will never result in a brick.. In case something is failed.. It's completely reverted
DanielF50 find the exact RUU as per your Cid and mid
The below guide is the best one.. Which will help you in finding the right RUU and flashing instructions
http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my pyramid.. Through blazing fast sonic waves

ganeshp said:
1.RUU corresponding to his device must be chosen for rma purposes.. Otherwise they won't accept it.. They will check the main-version too which varies for each RUU
Also running RUU as a exe ( not manually flashing) will never result in a brick.. In case something is failed.. It's completely reverted
DanielF50 find the exact RUU as per your Cid and mid
The below guide is the best one.. Which will help you in finding the right RUU and flashing instructions
http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I have the same problem, my phone keeps on rebooting every time. Where did you find the original HTC rom?

anielk77 said:
I have the same problem, my phone keeps on rebooting every time. Where did you find the original HTC rom?
Click to expand...
Click to collapse
where??
ive given a link already ..which will help you in finding the right RUU ..just read read read the guide

Hi guys, thanks for all the replies!
I flashed the RRU but flashed one of the latests ones, and now I can't root to restore my settings etc with Titanium Backup
Anyone know of a temporary root on 1.27, without having to use HTC dev, so that I don't void my warranty?

DanielF50 said:
Hi guys, thanks for all the replies!
I flashed the RRU but flashed one of the latests ones, and now I can't root to restore my settings etc with Titanium Backup
Anyone know of a temporary root on 1.27, without having to use HTC dev, so that I don't void my warranty?
Click to expand...
Click to collapse
arent you going to RMA it?
anyways if you are already SOFF ..you can use my one click root tool from my soff guide (link in my signature)

ganeshp said:
arent you going to RMA it?
anyways if you are already SOFF ..you can use my one click root tool from my soff guide (link in my signature)
Click to expand...
Click to collapse
I am, but I wanted to restore my settings so I can use it for a few days before I take it in, as work has got in the way lol.
I S-On'd after restoring the RUU as I didn't know revolutionary didn't work n 1.27, obviously not up to speed with this stuff anymore :silly:

DanielF50 said:
I am, but I wanted to restore my settings so I can use it for a few days before I take it in, as work has got in the way lol.
I S-On'd after restoring the RUU as I didn't know revolutionary didn't work n 1.27, obviously not up to speed with this stuff anymore :silly:
Click to expand...
Click to collapse
If SON Then rooting process is difficult. If you want to avoid htc-dev. As you need to soff again.. That too juopunutbear (wire trick)... You should have done SON just when you return the device..
Sent from my pyramid.. Through blazing fast sonic waves

ganeshp said:
If SON Then rooting process is difficult. If you want to avoid htc-dev. As you need to soff again.. That too juopunutbear (wire trick)... You should have done SON just when you return the device..
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I've tried the wire trick too, can't seem to get it to work, so completely given up, whenever the wire trick supposedly works my phone actually turns itself off

DanielF50 said:
I've tried the wire trick too, can't seem to get it to work, so completely given up, whenever the wire trick supposedly works my phone actually turns itself off
Click to expand...
Click to collapse
Wire trick for soff without htc-dev is but hard.. Check the troubleshoot point #3 for tips, tricks
Also the phone switching off means.. The pause you gave is too high..
Try this
0.5 sec tap - 1.5 sec pause - 0.5 sec tap
Sent from my pyramid.. Through blazing fast sonic waves

Thanks mate, got it rooted and s-off'd now
Any way to S-ON and Unroot again without wiping now!? lol.
Was thinking, flashing certain images through fastboot should do that shouldn't they?

[Q] HTC Sensation totally stock in boot loop

Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.

theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya

AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).

astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s

jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.

astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.

AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.

If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.

astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.

jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb

rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible

Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work

Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.

theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.

theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it

rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.

I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io

Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?

HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.

theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++

[Q] Help!! Purchased Dev phone and accidently locked it

Sorry for flooding this Forum with something basic as this but as a mere mortal I don't possess the mental capacity nor stamina to crash course my way in to this whole developers battleground.
I got a HTC ONE S that had been unlocked( I think) and when stupid me tried to do a system update (uncustomed to the way of the android as a convert apple-noob:silly I updated the phone with some kind of CID package which immediately sent the HTC in to the dreadded:
"This build is for development purposes only 20second loop of doom"
so after hours of studying this ancient language of boots, CID, builds, and alien laungage mumbo I havn't even been able to get the USB fastboot to work.
thusly I admit defeat and beg and plead to ye ascent beings only know as developers to make a complete noob-proof course of action how to tackle this peculiar problem.
so can anyone please make a step by step guid of what to download, how to install, where to get it and what to do That'd beeee swell.:highfive:
also I'll be going away so may not answer until sunday

any takers on helping me solve this riddle?

Welcome to the world of bricking and screwing up. This is not like Apple jailbreaking where you press one button on a website and it works.
This is pain and suffering. I would try and run an RUU to get the phone to stock. There are tons of threads on how to run an RUU. If the phone is not S-OFF, you will have to relock boot loader to run the RUU.

808phone said:
Welcome to the world of bricking and screwing up. This is not like Apple jailbreaking where you press one button on a website and it works.
This is pain and suffering. I would try and run an RUU to get the phone to stock. There are tons of threads on how to run an RUU. If the phone is not S-OFF, you will have to relock boot loader to run the RUU.
Click to expand...
Click to collapse
alright cheers, pretty sure it's S-ON and despite not knowing anything you just said at least it's something.
I also assume I'll need USB fastboot for this so I guess I'll start by trying to get that working

Anyone else care to explain the steps to take in greater detail? This was not a failed attempt at jailbreaking it was purely accidental so I have no experience doing this
Edit: I might add I suck at searching through forums aswell (especially when I don't know what I'm looking for) so maybe just a link to the proper threads would help me loads

LuckyXII said:
Anyone else care to explain the steps to take in greater detail? This was not a failed attempt at jailbreaking it was purely accidental so I have no experience doing this
Edit: I might add I suck at searching through forums aswell (especially when I don't know what I'm looking for) so maybe just a link to the proper threads would help me loads
Click to expand...
Click to collapse
To get back to stock, you run an RUU (ROM update utility). Here is a thread:
http://forum.xda-developers.com/showthread.php?t=2678700
I guess it's similar to running iTunes and pressing the restore button - but more involved.

not sure if I have a custom recovery but either way I couldn't flash the recovery.img and the RUU I ran didn't work (it was the same RUU that was installed on the phone)
Phone is S-ON
hboot 2.15.0000
open dps v31.1.0.45.0815
eMMc-boot
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4

LuckyXII said:
not sure if I have a custom recovery but either way I couldn't flash the recovery.img and the RUU I ran didn't work (it was the same RUU that was installed on the phone)
Phone is S-ON
hboot 2.15.0000
open dps v31.1.0.45.0815
eMMc-boot
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
Click to expand...
Click to collapse
Did you relock the boot loader before running RUU?

808phone said:
Did you relock the boot loader before running RUU?
Click to expand...
Click to collapse
I followed the steps but can't say I remember seeing "relocking boot loader" I will have to check this out further in the morning

LuckyXII said:
I followed the steps but can't say I remember seeing "relocking boot loader" I will have to check this out further in the morning
Click to expand...
Click to collapse
OK, then check this link out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html

808phone said:
OK, then check this link out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Click to expand...
Click to collapse
cannot open "Unlock_code.bin" :/
tried everything... changing the directive in cmd to match the location of the bin file but nothing works
adb can't find my device but fastboot can which could be why the RUU nor unlocking bootloader won't work and to get adb to work I need to enable USB debugging which can't be done while the phone is looping (unless some1 knows the right command line)

I am retarded
since I got this phone second hand I didn't know what had been done with it other than what I installed to cause my problems...
one of the things that had been done previously was unlocking bootloader.. hence the very obvious "Unlocked" in the boot menu.... sooo unlocking an unlocked bootloader was kinda redundant
tried oem locking the boot b4 but missed to specify where the files where (C:adb), lock worked and RUU installed without a hing!
thanks for your help if I knew what I was doing your instructions would have worked perfectly!

Alright!!!!!! Well, you are set!
So..... now that's it's back to stock. Are you going to use it as-is? Or are you planning to try a custom ROM again?
Try booting into the boot loader by shutting off the phone, then pressing volume down while pressing power. If it doesn't go to boot loader, then press and hold power for something like 10 seconds until the phone shuts off, then press volume down, and power again. Keep holding volume down until you get the boot loader menu.
Write down what it says about your HBOOT and whether you are S-OFF or S-ON.
DO NOT CHOOSE ANY COMMANDS FOR NOW
Press and hold power until the phone turns off again when you are done. Then press power again to turn the phone on again after a few seconds to use your phone regularly.

808phone said:
Alright!!!!!! Well, you are set!
So..... now that's it's back to stock. Are you going to use it as-is? Or are you planning to try a custom ROM again?
Try booting into the boot loader by shutting off the phone, then pressing volume down while pressing power. If it doesn't go to boot loader, then press and hold power for something like 10 seconds until the phone shuts off, then press volume down, and power again. Keep holding volume down until you get the boot loader menu.
Write down what it says about your HBOOT and whether you are S-OFF or S-ON.
DO NOT CHOOSE ANY COMMANDS FOR NOW
Press and hold power until the phone turns off again when you are done. Then press power again to turn the phone on again after a few seconds to use your phone regularly.
Click to expand...
Click to collapse
well if I were to try something now that I've already started walking down the path it'd probably be kitkat...
http://forum.xda-developers.com/showthread.php?t=2183023
note sure if I'm ready though

LuckyXII said:
well if I were to try something now that I've already started walking down the path it'd probably be kitkat...
http://forum.xda-developers.com/showthread.php?t=2183023
note sure if I'm ready though
Click to expand...
Click to collapse
OK take your time and when you are ready, PM me. I really do suggest CandyKat if you go for a custom ROM. It is the best ROM I have used on the ONE S. CM11 was ok for me, but for some reason CandyKat is just running so much better.

808phone said:
OK take your time and when you are ready, PM me. I really do suggest CandyKat if you go for a custom ROM. It is the best ROM I have used on the ONE S. CM11 was ok for me, but for some reason CandyKat is just running so much better.
Click to expand...
Click to collapse
Alright I will look in to it! Thank you for all the help wouldn't have done it without you