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
Related
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
Hi Guys,
Decided to put a new rom on my daughters HTC ONE X (my old phone), and right royally stuffed it up.
Was going to put a new hboot on as the one I had I thought was old, but now I've wiped the recover (TWRP) and can't seem to get it back. Phone was Telstra.
Details as follows:
C:\htc\Data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.89.841.9
(bootloader) serialno: HT26NW30xxxx
(bootloader) imei: 35222xxx80506xxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Have tried for two days on/off to get it to load a recovery, but no luck.
any help really appreciated..
jnrdavo said:
Hi Guys,
Decided to put a new rom on my daughters HTC ONE X (my old phone), and right royally stuffed it up.
Was going to put a new hboot on as the one I had I thought was old, but now I've wiped the recover (TWRP) and can't seem to get it back. Phone was Telstra.
Details as follows:
C:\htc\Data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.89.841.9
(bootloader) serialno: HT26NW30xxxx
(bootloader) imei: 35222xxx80506xxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Have tried for two days on/off to get it to load a recovery, but no luck.
any help really appreciated..
Click to expand...
Click to collapse
Place the recovery.img in you folder where your adb is located, reboot your phone into bootloader and select fastboot. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery "recoveryfilename.img" In this command line make sure to rename recoveryfilename to which match the name of the the version you are using
example: fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
after it has finished reboot
More information required. Please post your bootloader details (I'm mostly interested in the top line where it says tampered/locked/unlocked/relocked), what ROM you flashed, what recovery you flashed, and the method used to flash both.
PS. Questions go in the q&a section. I've asked for this to be moved for you.
[EDIT] What venomtester has said above is the correct procedure, but we still need the info I've requested to troubleshoot effectively.
Sent from my Evita
Thanks all for your help. Sorry for putting in the wrong forum. Here is the boot screen:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0-.23a.32.09.29
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
What have I tried, lots (to be honest). I started to use Hasoon2000 v2.5 great utility (ONE X), I have tried the flash FactoryRUU, tried CWM, TWRP, but still no luck.
Not sure if the hboot version is causing all the problem, but tried to update that, unsuccessfully (probably to do with s-off).
good news is I can talk to the phone with fastboot, get back results etc.. Just tried to flash openrecovery-twrp-2.4.0.0-endeavoru.img, it seems to flash ok with fastboot, but when I reboot to recovery, I can see the brown bar at the top right of the screen run twice, but then nothing else happens, just sits on the white 'HTC quitely brilliant, this build is for' ... screen.
jnrdavo said:
Just tried to flash openrecovery-twrp-2.4.0.0-endeavoru.img,
Click to expand...
Click to collapse
That's your problem right there. You tried to flash TWRP for the ENDEAVORU (quad core version) when your phone is the EVITA (dual core).
redpoint73 said:
That's your problem right there. You tried to flash TWRP for the ENDEAVORU (quad core version) when your phone is the EVITA (dual core).
Click to expand...
Click to collapse
Thanks mate for pointing me in the right direction. I'll try the right file
I really should stop doing this kind of work at 5:00am in the morning!
just a quick question, if I download the correct twrp, should I just have to fastboot it and overwrite what I have done, or do I need to do anything prior before flashing the correct one?
jnrdavo said:
just a quick question, if I download the correct twrp, should I just have to fastboot it and overwrite what I have done, or do I need to do anything prior before flashing the correct one?
Click to expand...
Click to collapse
I'd try to flash it over fastboot, and see what happens.
jnrdavo said:
just a quick question, if I download the correct twrp, should I just have to fastboot it and overwrite what I have done, or do I need to do anything prior before flashing the correct one?
Click to expand...
Click to collapse
Just make sure after flashing the correct recovery you also give this command:
fastboot erase cache
Sent from my Evita
timmaaa said:
Just make sure after flashing the correct recovery you also give this command:
fastboot erase cache
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys, all working well now!
I'm trying to get my father's phone ruu'ed to 3.14 tmo.
I rooted his phone and unlocked through htc dev a long time ago.
He is currently running cm10 w/ hboot 1.09 and radio 0.16.31501s.
S-on w/ tmo CID.
I used faceplam S-off on my phone and lost 3g/4g. I do not want this to happen to his phone.
So what I'am asking is what do i have to do to get his tmo HTC ONE S safely onto the JB 3.14 from htc/tmo?
When i try to ruu using the 3.14 i get ERROR [159]: IMAGE ERROR. It says i have the wrong image and to download the correct one. Its the same one i used on my phone repeatably.
Any help would be great. Really afraid of borking his phone.
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4132mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
billydroid said:
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
Click to expand...
Click to collapse
tmobile U.S.
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
to relock
while phone is in bootloader >fastboot USB
fastboot folder, shift right click open command window
from command window type
fastboot oem lock
(also heard but haven't tried because I'm S-Off that you can run RUU.exe from fastboot USB without relocking bootloader)
Edit: to answer the bootloader question. Yes you can ruu a different hboot as long as it is a higher hboot. (s-off no matter)
I got it. I had to re-lock and run ruu 1.84 rc2 first. Then it let me ruu 3.14.
Sent from my HTC VLE_U using Tapatalk
Hi everyone.
I'm trying to get back on stock (S4), but I can't find any RUU that matches my hboot and radio.
this is the result of fastboot getvar all:
Code:
(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: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4005mV
(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
I tried several S4 RUUs, european ones gave me error 131, Vodafone UK gave error 155 (the cellphone was bought in Italy).
What I did before executing the RUU exe(s) was just locking the bootloader. I think that probably installing ROMs in the time (the cellphone belongs to a friend of mine, so I don't know what was installed before) may have somewhat changed hboot (and/or radio) version, and now I can't find a RUU matching mine. Now i can only access the bootloader (I think the previous custom recovery is gone). I managed to access recovery by unlocking again the bootloader, but I can't mount any partition from the recovery (which is the main problem that lead me to decide to get back to stock.
What are my chances to return to HTC stock?
I have the same problem
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
addsfsds said:
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
Click to expand...
Click to collapse
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
hasanalikhattak said:
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
Click to expand...
Click to collapse
Dude give a quick look around, all the guides are here! or come to androidiani.com to get italian translated guides and support!
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!