Database Info

No bootloader, rom or recovery s-on locked bootloader hboot 1.18.0000

Hi people i am stuck on splash screen with No bootloader, rom or recovery s-on locked bootloader hboot 1.18.0000
Any ideas???

ave you:
Pulled the battery, replaced it - pressed and help the powerbutton and volume down button, released the power button, got the screen with 3 androids?
If so you can then reflash the stock RUU and get back up in no time

I only get the splash screen inless i put in and unplug usb cable then i just get the hboot version ect.....
I can do a few fast boot commands but with the hboot 1.18.0000 i dont get advanced ones so screwed there. The ruu's have wrong bootloader error.
Im pretty screwed really!

what do you mean by "ruu's have wrong bootloader error"? If that stuff still works.. you should be able to fix it easily. I'm banking on the assumption that you're running the wrong RUU's and don't have SuperCID hence the "bootloader errors" (which I have no idea what that is!)

It comes up with error wrong bootloader error. I think its something to to do with the hboot version. I have tried every single ruu for the sensation.

any1 got any ideas as its still screwed x

What software version were you on before you tried to root/S-OFF?

i was on miui and had s-off unlocked and it was rooted. i am now s-on ***relocked*** and hboot 1.18.000 with no rom or recovery and with usb cable in its stuck on splash screen.

I mean what was your original ROM that was on it when you first got the phone? Without that it's hard to suggest an RUU to use

cant remember but i have ttied every ruu on shippedroms.com
i have supercid still by the way

You are not able to S-off thru revolutionary?

I have had this fone stuck like this since jan surely someone must know a way??
If hboot 1.18.000 supported advanced fastboot commands i could just put a recovery on it and then go from there. Sadly i cant and i cant find a way to send a hboot 1.17 while on 1.18 to the fone???

No it looks for adb devices. I only have fastboot.

Dunno if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0000
(bootloader) version-baseband: 11.15.3504.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.401.1
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3989mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 9d24123f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.494s

So connecting in fastboot to the PC and running the RUU doesn't work? Have you tried the PG58IMG.zip method of flashing an RUU?

Yes mate i have ttried that as well :-( wen i unplug the usb cable i just get to the hboot screen and the only thing it says is ruu where the recovery option used to be.
:-( I think its dead and needs stamping on!

Someone must have an idea???
Im using a ****ty fone that only calls and sends txts plus onlu holds a few messages so i cnstntly have to clear my inbox :-(

Please help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

OK, lets see if i can help at all.
Lets get the basics sorted, what phone, what rom - original and before problem, what CID - original, which country / network, was it locked / branded...?
Then what steps did you do to end up messed up as you are? You say you had s-off and unlocked? Did you try to s-on, do a bad flash, update firmware, pee on the phone / give it to your dog...?

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0000
(bootloader) version-baseband: 11.15.3504.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.401.1
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3989mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 9d24123f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.494s
Standered htc sensation
I cant remember the original rom it came with but i have tried every shipped rom so far.
I used revolutionary to gain s-off and root it and was running miui and everything was fine for months then all of a sudden it restarted into bootloop :-( this was in december. Then i cant remember exactly wot i did but i lost recovery so was unable to flash new rom like that so i decided to flash a shipped rom.
The ruu failed so i put s-on and retried but it still failed. Then i noticed the new bootloader unlocker had just came out so unlocked it but soon relocked it.
This has now left me with a relocked bootloader s-on and no recovery at all.
I am on hboot 1.18.0000 so cant do advanced fastboot commands,
Cant use adb on it only fastboot so i think i maybe SCREWED!!!
Anymore info mate???
Thanks in advanced for trying mate

[Q] No Recovery, Security Warning, can't unlock bootloader

Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!

masev said:
Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!
Click to expand...
Click to collapse
Given that this has been covered many times, you would be better off listing EXACTLY what you have tried and the results you get so that people can have a better chance to help you. However, the answers are all out there and you simply need to read and make sure that you understand what you are doing and why.

I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !

masev said:
I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !
Click to expand...
Click to collapse
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140

SimonTS said:
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140
Click to expand...
Click to collapse
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks

masev said:
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks
Click to expand...
Click to collapse
RUU to a higher version.

Had the same problem with a branded phone. Problem is - you need a higher RUU. In my case there was no higher branded RUU.
I've made a gold card and flashed a unbranded higher RUU (latest ICS), and that makes the phone work again.
But without HTC-dev unlock we now can't get root! So if you can't find a higher RUU with your brand you may can't bring it to service with the new unbranded software on it.
Gesendet von meinem HTC Desire S mit Tapatalk 2

[Q] HTC One S soft bricked. Fastboot but no recovery, Need help reverting to stock

I soft bricked a friend's (yikes, I know) Telus HTC One S trying to install CM10.0.
I have abandoned the installation now and would be happy to be able to just reflash stock.
Here's my status:
I can get to fastboot.
I have the following fastboot screen:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.17.31501S.10_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 20 2012,15:14:18
I attempted to follow a procedure to flash a stock RUU, and it demanded relocking the bootloader so now it's relocked.
I can no longer boot it into recovery since relocking.
Now, when I attempt to install the RUU that I downloaded (RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe) while in fastboot USB mode, the RUU software executes but fails at the first step with Error 170: USB Connection Error.
I am now at a loss. Any help much appreciated.

You need to recheck correct drivers , usb cable, and usb 2.0 ports only.
Sent from my HTC One S using Tapatalk 4 Beta

Extracting the update on windows, copying it to a mac and using openruu there worked.
I don't know how people put up with Windows 8 on a Surface. It gave me a lot of trouble today.

You have to use a real computer/laptop. Surface is not real computer - it is piss poor imitation. I got Gateway laptop with win8 and have no problems.

i had this too how i fixed it i unlocked the bootloader and the security warning tag went away and i flashed recovery and flashed a romi havent found a way to go back to stock after getting the security warning.

HTC One S 1.5Ghz Soft Bricked to!
I have the same issue. Mine is also ''Tampered'' and ''Relocked''. And nothing I do works
What I done so far!
Before tampering with the cellphone I took backup .img files of my ROM. I even took a manual ''Copy everything on the cellphone to my PC'' in case this would happen. So....
I have installed Universal ADB Drivers, JDK for Java, Android Studio bundle, The HTC One Toolkit - Squabbi - 3.1.2 version. Not that it done any good so far.
The BIG problem is that the cellphone can't mount it's memory card. So I can't put any ROMS, FLASH FILES, .zips or anything on it. I failed at forcing data into the ''data'' folder to.
And when I try to flash a file directly using ''Fastboot'' the device hangs at ''Sending'' request. Other problems when working with the ''ADB commands'' gives me the ''Device not found'' response.
I downloaded the RUU for my device as a .zip as there's no existing .exe version to be found. With no luck flashing it I might say. Due to the constant hanging when the file is ''Sending''.
( This is the RUU I downloaded: OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50. 05.28_10.27.50.08L_release_301852xf01hejl416oev96. zip )
And for 2 days with applying fix after fix and trial and error I'm coming nowhere! I'm thinking on formatting the whole cellphone and copy my ''manual copy of my cellphone'' into the formatted cellphone drive.
In the bootloader this information can be seen:
*** TAMPERED ***
*** RELOCKED *** (Along the lines of guides this happen. No idea how though
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
My cellphone has: Philz touch 5 CWM Base version 6.0,3,2 on it.
NOW! This is what actually works on my cellphone:
1. I can get into BootLoader on my HTC One S!
2. I can get into Fastboot on my HTC One S!
3. The Fastboot on my HTC One S recognizes as ''Fastboot USB'' on when I plug it into my computer.
4. My computer recognizes the cellphone as a ''removable disk''. And using the command ''Fastboot Devices'' in CMD lets me see the ''SH32HW401164'' number. Using the command ''Fastboot getvar all'' gives me this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4150mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
----
My plan was to flash this ROM into my phone if the stock one still showed issues: http://forum.xda-developers.com/show....php?t=2531065
This being said and again: My HTC One S is NOT flashed with a custom ROM! It has the same ROM it came with, all though, it has been unlocked -> Rooted -> Relocked. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum

HTC-One-User said:
I have the same issue. Mine is also ''Tampered'' and ''Relocked''. And nothing I do works
What I done so far!
Before tampering with the cellphone I took backup .img files of my ROM. I even took a manual ''Copy everything on the cellphone to my PC'' in case this would happen. So....
I have installed Universal ADB Drivers, JDK for Java, Android Studio bundle, The HTC One Toolkit - Squabbi - 3.1.2 version. Not that it done any good so far.
The BIG problem is that the cellphone can't mount it's memory card. So I can't put any ROMS, FLASH FILES, .zips or anything on it. I failed at forcing data into the ''data'' folder to.
And when I try to flash a file directly using ''Fastboot'' the device hangs at ''Sending'' request. Other problems when working with the ''ADB commands'' gives me the ''Device not found'' response.
I downloaded the RUU for my device as a .zip as there's no existing .exe version to be found. With no luck flashing it I might say. Due to the constant hanging when the file is ''Sending''.
( This is the RUU I downloaded: OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50. 05.28_10.27.50.08L_release_301852xf01hejl416oev96. zip )
And for 2 days with applying fix after fix and trial and error I'm coming nowhere! I'm thinking on formatting the whole cellphone and copy my ''manual copy of my cellphone'' into the formatted cellphone drive.
In the bootloader this information can be seen:
*** TAMPERED ***
*** RELOCKED *** (Along the lines of guides this happen. No idea how though
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
My cellphone has: Philz touch 5 CWM Base version 6.0,3,2 on it.
NOW! This is what actually works on my cellphone:
1. I can get into BootLoader on my HTC One S!
2. I can get into Fastboot on my HTC One S!
3. The Fastboot on my HTC One S recognizes as ''Fastboot USB'' on when I plug it into my computer.
4. My computer recognizes the cellphone as a ''removable disk''. And using the command ''Fastboot Devices'' in CMD lets me see the ''SH32HW401164'' number. Using the command ''Fastboot getvar all'' gives me this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4150mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
----
My plan was to flash this ROM into my phone if the stock one still showed issues: http://forum.xda-developers.com/show....php?t=2531065
This being said and again: My HTC One S is NOT flashed with a custom ROM! It has the same ROM it came with, all though, it has been unlocked -> Rooted -> Relocked. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum
Click to expand...
Click to collapse
I managed to UNLOCK it again. Then used this guide to fix the SD card error: http://forum.xda-developers.com/showthread.php?t=2086156 Afterwards I downloaded the VIperROM 3.2.0.zip and put it on my SD card. Then flashed like normal and now the phone has ROM and works Thanks for the fantastic support to this forum!

Phone won't boot up

HI Guys
So my mate's phone won't boot up and I'd really appreciate some assistance. The last thing I did was unlock the phone via htcdev. But that's all I could do. Now I can't flash a recovery (I've tried a few) because I get an IMAGE UPDATE ERROR. I've also received a "SIGNATURE VERIFY FAIL" error.
Also, adb won't recognise my device but fastboot does.
What I'm trying to do is install a custom rom because my mate was complaining that his phone was slow and a bit laggy. I sold the phone to him in the first place so I've taken it upon myself to fix it.
Thanks guys, let me know if you need any further info.
CJ

First of all, we need some information about your phone.
I need : what kind(k2u, k2ul and so on)
Then what you have already done.
Then the other things (best of all you copy all information from your boot loader)
Edit: okay skript point 2 xD
Kreumadragon

Thanks for getting back to me.
Here's the information you've requested.
UNLOCKED
K2_ul PVT SHIP S-ON RL
HBOOT-2.21.0000
Radio-1.18.40a.00.05
openDSP-v13.2.0268.0620
OS-3.12.980.10
eMMC-boot 1024MB
Jul 2014
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.12.980.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2BWTP01724
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8015000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.100s
Let me know if you need any further information.

With regards to what I have already done, I tried to flash TWRP recovery but I got an image update error.

Mhh do you flash the right TWRP?
And use fastboot flash recovery *recovery name*?
Do you have any data's to loose?
Kreumadragon

yeah I flashed a few different TWRPs and none of them worked.. if there is a specific one and if you have a link, I could try again?
nope i don't need any data to lose. I have removed the sd card. Thanks again.

Anyone? Still having no luck with this phone.

Please test (if you want) the cwm recovery. Link:
http://forum.xda-developers.com/showthread.php?p=37075457
If this doesn't work flash a ruu and try again
Kreumadragon

There is no RUU out which will work and also the cwm is outdated.
How did you flash recovery?
Use the one i recommended in my index thread. This should work on your hboot.

An other option is to get s off and flash it via pl**img.zip isn't it?
Kreumadragon

You need a working OS for S-off. Not sure if that is working here.

@Old
You have s off, haven't you?
And I get s off with hboot 2.21
Kreumadragon

I don't have One SV anymore.
Rumrunner works on hboot 2.21.

He says that he didn't have data's to loose
theoretically you can create an ........IMG.zip file with all files a ruu use, only the recovery is changed? Think I can make one but first want to read what you think(old)
Kreumadragon

As long as he is S-on you don't need to make anything.
Right now he can only flash signed firmware by HTC this way.

Okay, thx I don't know
Actually no ruu for any kind of k2ul?
Kreumadragon

Only one. And you must be S-off or on ICS to use that.

@CJ_
Do you have test old.s method?
If this doesn't work, you probably need SOff.
Kreumadragon

Hi old.splatterhand, to answer your question, I flashed the latest TWRP recovery (2.8. something) but I got the following IMAGE UPDATE ERROR. Will try the ones in your index and report back.
Thanks for your help guys.

Will try it now... If that doesn't work, how do I get S-Off when I can't do anything with the phone?

[Completed] Chicken & Egg problem un-soft-bricking HTC One S

Hi Guys
I'm working on reviving a soft-bricked HTC One S (tmobile, I suspect S4)
I am unable to install any android ROM that I have been able to find, because HBOOT is still version 1.14, and they all require a higher version
TL;DR;
I think I just need a ROM that will install on a HTC ONE S (ville) for HBOOT version 1.14
I'm using an OSX machine, so I don't have the ability to run RUU.exe files. (is there a way to do this?) Attempts at flashing wiht RUU.zip have uniformly failed.
My attempts to upgrade HBOOT via the firmware upgrades with "fastboot flash zip <file>" have not had any luck, I suspect because the phone
is still S-ON (More or less following this instruction set http://forum.xda-developers.com/showthread.php?p=39216236#post39216236 )
My attempts at to remove S-ON using this explanation ( http://forum.xda-developers.com/showthread.php?t=2155135 ) haven't had much for potentially one of two reasons:
Possible reason #1) Step 6 calls for a "fastboot oem boot", which then tries to boot, but there is no working android install. I tried working around this by calling "fastboot oem gotohboot" instead and then booting into recovery (TWRP).
possible reason #2) adb shell doesn't seem to have access to su for me. ("adb shell su" returns "/sbin/sh: su: not found"). I have been assuming that this is the actual problem. I am assuming that this is because I don't have superuser access.
The SuperBoot package doesn't seem to work ( I grabbed it from here http://loadbalancing.modaco.com/download.php?file=r1-ville-superboot.zip referred by http://www.android.gs/root-htc-one-s/ ). I *think* it doesn't work because there is no android version to boot into.
So in short it seems that:
Android requires higher HBOOT requires S-OFF requires Superuser requires Android
Thanks so much for any direction or help, or even just commiseration!
For reference at the moment it is/has:
unlocked
HBoot 1.14 and fastboot is working well, and behaves as expected.
S-On
TWRP (working, and able to access with ADB)
No Working android install
CID: 1111111
Here is a dump of "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.13.50.05.25
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.531.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24NW401635
(bootloader) imei: 359902041820139
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8be28a51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

XDA Visitor said:
Hi Guys
I'm working on reviving a soft-bricked HTC One S (tmobile, I suspect S4)
I am unable to install any android ROM that I have been able to find, because HBOOT is still version 1.14, and they all require a higher version
TL;DR;
I think I just need a ROM that will install on a HTC ONE S (ville) for HBOOT version 1.14
I'm using an OSX machine, so I don't have the ability to run RUU.exe files. (is there a way to do this?) Attempts at flashing wiht RUU.zip have uniformly failed.
My attempts to upgrade HBOOT via the firmware upgrades with "fastboot flash zip <file>" have not had any luck, I suspect because the phone
is still S-ON (More or less following this instruction set http://forum.xda-developers.com/showthread.php?p=39216236#post39216236 )
My attempts at to remove S-ON using this explanation ( http://forum.xda-developers.com/showthread.php?t=2155135 ) haven't had much for potentially one of two reasons:
Possible reason #1) Step 6 calls for a "fastboot oem boot", which then tries to boot, but there is no working android install. I tried working around this by calling "fastboot oem gotohboot" instead and then booting into recovery (TWRP).
possible reason #2) adb shell doesn't seem to have access to su for me. ("adb shell su" returns "/sbin/sh: su: not found"). I have been assuming that this is the actual problem. I am assuming that this is because I don't have superuser access.
The SuperBoot package doesn't seem to work ( I grabbed it from here http://loadbalancing.modaco.com/download.php?file=r1-ville-superboot.zip referred by http://www.android.gs/root-htc-one-s/ ). I *think* it doesn't work because there is no android version to boot into.
So in short it seems that:
Android requires higher HBOOT requires S-OFF requires Superuser requires Android
Thanks so much for any direction or help, or even just commiseration!
For reference at the moment it is/has:
unlocked
HBoot 1.14 and fastboot is working well, and behaves as expected.
S-On
TWRP (working, and able to access with ADB)
No Working android install
CID: 1111111
Here is a dump of "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.13.50.05.25
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.531.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24NW401635
(bootloader) imei: 359902041820139
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8be28a51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
I found some guide how to unbrick your device:
[HOW-TO] Unbrick Your Android Phone (HTC ONE S) by fabiane79
[TUT] Downgrade/Unbrick Ville S4 by mirGantrophy
[HOW-TO] Fix soft brick & error mounting sdcard by cannondale0815
[TUT] Unbrick Your HTC One S [TUT] by immortal_warrior
Hopefully one of them can help in your case.
If not, please register on xda and ask in the One S Q&A, Help & Troubleshooting forum.
Good luck !

Thread closed. Thank you!