Database Info

Bricked HTC One S/Won't boot past start up

I was going through the process and got stuck at the place some other folks are; getting root to work. In an effort to troubleshoot this myself I reflashed the different recoveries and the interim one seemed to boot up fine. When root wouldn't stick I did a master reset.
This is where it gets bad - when root still wouldn't work I went to advanced and formatted everything. I did this because it worked on the GS2 when I would have problems. Now when I reboot it gets stuck on the HTC Quietly Brilliant screen. Please help even though I brought this on myself.
tl;dr
The phone is stuck on the htc start up screen and I cannot get it to boot up or into recovery. Please help!
Update: I can get into bootloader and also into recovery. I cannot mount the sdcard to push any files to the phone through adb though.

Have you tried holding down power button for 10 sec and the hold vol- while pressing the power button? it worked for me when i Semi-bricked.. let me know how it turns out if not try the ruu in the dev section..
---------- Post added at 05:32 PM ---------- Previous post was at 05:30 PM ----------
Maybe you can download the nandroid posted in the dev section and push the system partition..

you formatted everything ?? including /system ?
If so you have formatted the ROM and thats why it wont boot..
Try to put a rom in your folder where adb and fastboot is located.. And type the command (whilst in fastboot) fastboot flash nameofrom.zip
if that fails run an RUU. If you need to change it to match your version, Extract the rom.zip and modify the android-info.txt to match your CID and MID.
If you dont know how to get them, in fastboot, use the command fastboot getvar all
good luck and dont panic you'll be fine

You don't need to mount the SD Card to push files over with ADB in fastboot.

Help Please!
I have this same problem and adb and fastboot not working for me.. can anyboy walk me thru this please..

do you have the right drivers ? do you have all the necessary files in the right location ?
what happens when you boot into bootloader and connect usb ?

azzledazzle said:
do you have the right drivers ? do you have all the necessary files in the right location ?
what happens when you boot into bootloader and connect usb ?
Click to expand...
Click to collapse
It says device not found but i have installed all the necessary drivers..

azzledazzle said:
do you have the right drivers ? do you have all the necessary files in the right location ?
what happens when you boot into bootloader and connect usb ?
Click to expand...
Click to collapse
Its definitely driver related issue.. htc sync didnt work.. fastboot connects to usb but im lost after that..

I got adb working but now it says protocol failure when i try to push the files to \sdcard..
Sent from my YP-G70 using xda premium

I have the same problem as the OP. I tried to flash several ROMs this way:
Code:
C:\androidsdk\android-sdk-windows\tools>fastboot flash /system Rom_xda.zip
sending '/system' (525202 KB)...
OKAY [ 25.529s]
writing '/system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 67.731s
As you can see, the signature verification failed. What can be done about it?
Thanks
-J

Hi,
I have the same problem it shows the "HTC quietly brilliant" bootscreen, nothing happends, I tried these things:
Alle here: http://forum.xda-developers.com/showthread.php?t=1609190 (I know it's for the One X),
Go into Fastboot and right in cmd on computer:
"fastboot flash boot boot_signed.img",
clear system, cache, etc.
and
Download, start RUU: "RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe" - I hope it's the right one
I got the same fail like the others:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"the signature verification failed"
( Sorry for my bad English )

HTC One s Bricked help!!!!!
hey guys i just got my one s last week and i just got curious and started messing with it and rooted it after that i started downloading things on the phone like themes and then i turned my phone off before school when i turned it on it was stuck at the start where it says htc. i asked my brother in law what happened he said that i got it bricked and that i needed to try to restore it well i tried to connect it to my computer and my computer doesnt read the phone nor command prompt and the only way it reads it is when i put it in the bootloader section where when you click fastboot and then shows boot loader thats when it reads it and every time i try recovery it wont work then everytime i try clock work mod it says i need an sd card and well as you know the htc one s doesnt have an sd card and i tried so many programs like odin im not that good with command prompt but does anyone know a software that can restore the phone when you are in the boot loader section can soemone please help me

I don't know much about this but did you put it in download mode before you connected to your pc
Sent from my HTC VLE_U using XDA

kmao2004 said:
I was going through the process and got stuck at the place some other folks are; getting root to work. In an effort to troubleshoot this myself I reflashed the different recoveries and the interim one seemed to boot up fine. When root wouldn't stick I did a master reset.
This is where it gets bad - when root still wouldn't work I went to advanced and formatted everything. I did this because it worked on the GS2 when I would have problems. Now when I reboot it gets stuck on the HTC Quietly Brilliant screen. Please help even though I brought this on myself.
tl;dr
The phone is stuck on the htc start up screen and I cannot get it to boot up or into recovery. Please help!
Update: I can get into bootloader and also into recovery. I cannot mount the sdcard to push any files to the phone through adb though.
Click to expand...
Click to collapse
The interim version of CWM does not mount for USB storage, try using a different version if you cannot get any ADB commands to work. Not that it will fix your issue with ADB, but if you can get the storage mounted you put the ROM on it and flash. Hope it all works out bro.

Try this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using Tapatalk 2

bricked
after adb reboot bootloader my phone never booted to boot loader and it is not turning on . the red led flashes when connected to charger.is my phne bricked?
kmao2004 said:
I was going through the process and got stuck at the place some other folks are; getting root to work. In an effort to troubleshoot this myself I reflashed the different recoveries and the interim one seemed to boot up fine. When root wouldn't stick I did a master reset.
This is where it gets bad - when root still wouldn't work I went to advanced and formatted everything. I did this because it worked on the GS2 when I would have problems. Now when I reboot it gets stuck on the HTC Quietly Brilliant screen. Please help even though I brought this on myself.
tl;dr
The phone is stuck on the htc start up screen and I cannot get it to boot up or into recovery. Please help!
Update: I can get into bootloader and also into recovery. I cannot mount the sdcard to push any files to the phone through adb though.
Click to expand...
Click to collapse

[email protected] said:
after adb reboot bootloader my phone never booted to boot loader and it is not turning on . the red led flashes when connected to charger.is my phne bricked?
Click to expand...
Click to collapse
Try holding the power and volume down buttons down simultaneously.
Sent from my One S using Tapatalk 2

Just FYI for you new guys that hijacked the thread. Too many problems posted in one thread can quickly become hard for folks trying to help to keep track of which problem they are responding to. Or, what has been already been recommended for each issue. A better way till your post count is up is to try here:
http://forum.xda-developers.com/showthread.php?t=2110195
Also, Yassa--Need to get a shorter user ID then your email address--
Just my 2 cents--

bricked my htc one s
i seemed to bricked my htc one s changing roms..
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH24MW405604
(bootloader) imei: 359901046962037
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(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 cant push any files through adb because its missing sh
adb push (no such file.. and so on... -__-
i have 2 days working on this
can anyone please help

hello guys, i have been trying to fix my bricked htc one s for days now and i dont seem to be getting it right.....
VLE PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.09.0000
RADIO-0.16.31501S.17_2
OPENdsp-V25.1.0.32.0405
Emmc-BOOT
APR 2 2012,21:08:24
PLEASE ANYBODY OUT THERE I NEED HELP...... I HAVE TRIED FLASHING A NEW ROM SOOOO MANY TIMES BUT STILL STUCK BETWEEN START UP SCREEN AND RECOVERY MODE

[Q] One s won't Boot, Buttons Flashing

Using Ubuntu 12.04 linux
Hello, Yesterday i used the moonshine s-off and now my phone won't fully boot. When I hold down the power button the buttons start flashing and if i hold it down until they stop(about 10 seconds) and release it, the HTC boot screen with "This version is for development only" with show up, then it turns back off. Any help is much appreciated
Edit:
I've been able to get it to boot to Recovery by Booting it to the Htc screen with the method above and hold down the power button though the duration of that screen. It will Go black then if I hit the power button again it with boot to Recovery(I have Touch CWM), but I can't access sdcard for flashing(can't mount the /sdcard directory).
I can also get it to boot to Fastboot the same was as recovery but with holding the Volume Down button any time i hold the power button, but Fastboot doesn't seem to detect it

Biom4st3r said:
Hello, Yesterday i used the moonshine s-off and now my phone won't fully boot. When I hold down the power button the buttons start flashing and if i hold it down until they stop(about 10 seconds) and release it, the HTC boot screen with "This version is for development only" with show up, then it turns back off. Any help is much appreciated
Click to expand...
Click to collapse
Are you on stock? or running another ROM?
Was moonshining successful?
First I would try going to bootloader and factory reset (you will erase all your apps, photos, files)
If that didn't work I would run a RUU.exe

tivofool said:
Are you on stock? or running another ROM?
Was moonshining successful?
First I would try going to bootloader and factory reset (you will erase all your apps, photos, files)
If that didn't work I would run a RUU.exe
Click to expand...
Click to collapse
Yes I am one stock
I'm sure sure if the moonshine work because its Terminal Closed before I could see it
I have tried Factory reset. but all it did was shutdown
I'm on linux and can not run executables

Biom4st3r said:
Yes I am one stock
I'm sure sure if the moonshine work because its Terminal Closed before I could see it
I have tried Factory reset. but all it did was shutdown
I'm on linux and can not run executables
Click to expand...
Click to collapse
boot up phone in bootloader and see what it says. Whether S-on or s-off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

tivofool said:
boot up phone in bootloader and see what it says. Whether S-on or s-off
Click to expand...
Click to collapse
It is still s-on

Biom4st3r said:
It is still s-on
Click to expand...
Click to collapse
you could flash this stock recovery. After that in bootloader pick "clear storage". Having stock recovery fixes the sd mounting issues.
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img
Then you could put back on your CWM or TWRP and mount usb storage, put on a ROM, fastboot flash boot.img and install ROM.

tivofool said:
you could flash this stock recovery. After that in bootloader pick "clear storage". Having stock recovery fixes the sd mounting issues.
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img
Then you could put back on your CWM or TWRP and mount usb storage, put on a ROM, fastboot flash boot.img and install ROM.
Click to expand...
Click to collapse
After I flashed Stock Recovery. and booted into recovery it came up to a screen with the phone and a Green down arrow then to change to a Red Triangle with a ! And a picture of a phone

Biom4st3r said:
After I flashed Stock Recovery. and booted into recovery it came up to a screen with the phone and a Green down arrow then to change to a Red Triangle with a ! And a picture of a phone
Click to expand...
Click to collapse
That is just the stock recovery. Telling you that you aren't authorized to use it.
You want to boot up into bootloader, not recovery.

tivofool said:
That is just the stock recovery. Telling you that you aren't authorized to use it.
You want to boot up into bootloader, not recovery.
Click to expand...
Click to collapse
Oh ok. So i can just flash, say CM10.3, and it'll be fine?

Biom4st3r said:
Oh ok. So i can just flash, say CM10.3, and it'll be fine?
Click to expand...
Click to collapse
I hope so, as long as the Moonshine attempt didn't mess with anything.
So, if you haven't, while on stock recovery, boot into bootloader and clear storage.
Then put back custom recovery, mount usb storage for your new ROM, flash the boot image and install rom.
Hopefully your hboot is 2.15 (and I really hope you have an S4 and not a villeC2)

tivofool said:
I hope so, as long as the Moonshine attempt didn't mess with anything.
So, if you haven't, while on stock recovery, boot into bootloader and clear storage.
Then put back custom recovery, mount usb storage for your new ROM, flash the boot image and install rom.
Hopefully your hboot is 2.15 (and I really hope you have an S4 and not a villeC2)
Click to expand...
Click to collapse
I cleared storage, but when i tried to Mount Usb Storage i got "E:Unable to open ums lunfile (No suc"

i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(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: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(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.061s
I tried RUU 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 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot

Biom4st3r said:
I cleared storage, but when i tried to Mount Usb Storage i got "E:Unable to open ums lunfile (No suc"
Click to expand...
Click to collapse
Try a different recovery
CWM
Or
TWRP

tivofool said:
I hope so, as long as the Moonshine attempt didn't mess with anything.
So, if you haven't, while on stock recovery, boot into bootloader and clear storage.
Then put back custom recovery, mount usb storage for your new ROM, flash the boot image and install rom.
Hopefully your hboot is 2.15 (and I really hope you have an S4 and not a villeC2)
Click to expand...
Click to collapse
My Hboot is HBOOT-1.14.0005

Biom4st3r said:
My Hboot is HBOOT-1.14.0005
Click to expand...
Click to collapse
K, you need to upgrade your firmware or everything is just gonna bootloop on you.
either run a windows environment so you can run a RUU or
this tutorial for upgrading firmware
http://forum.xda-developers.com/showthread.php?t=2322755

tivofool said:
K, you need to upgrade your firmware or everything is just gonna bootloop on you.
either run a windows environment so you can run a RUU or
this tutorial for upgrading firmware
http://forum.xda-developers.com/showthread.php?t=2322755
Click to expand...
Click to collapse
Followed the Firmware update and it when smoothly I'm HBOOT 2.15, unlocked w/ TWRP. I Flashing the cm-10.1.3-ville.zip From TWRP and it bootlooped me. Thank you for all this by the way. I just switched from Motorola and this is all foreign to me

Biom4st3r said:
Followed the Firmware update and it when smoothly I'm HBOOT 2.15, unlocked w/ TWRP. I Flashing the cm-10.1.3-ville.zip From TWRP and it bootlooped me. Thank you for all this by the way. I just switched from Motorola and this is all foreign to me
Click to expand...
Click to collapse
You are welcome. Helping smart people is easy.
---------- Post added at 04:47 PM ---------- Previous post was at 04:43 PM ----------
Oops, didn't read about the bootloops part. Did you fastboot flash boot boot.img?
Need to do that since you are S-On.
And by the way, That Cyanogen has been notorious for bootloops even when installed correctly. Sense ROMs don't bootloop or the new 2.16 firmware ROMs are better.

HTC ONE SV stuck on black screen with battery showing

Good morning guys,
firstly i really have tried to read up on everything i can possibly before i posted this, i've been looking around trying to get as much info as i can
So from the start my HTC ONE SV is softbricked (i think) it tried to update a few months back and half way through the process something went wrong it shut down and rebooted, and it was just a black screen and battery icon (showing that it was charging still)
I then went to Hboot Recovery and started the process, what i found odd was that when it went to the recovery icon, the 2 swirling arrows over the device icon, it would show that for a couple of seconds then reboot itself it would repeat this process for about 5 minuets then finally boot up the phone into the HTC ONE screen, chime would play (but stutters) and then load me back to where i was in the first place a black screen with the battery icon, and time
So clearly something is corrupted either the restore portion or the os it'self, i decided that it would need to be re flashed.
i have gotten as far as Ulocking the bootloader and now i have what i belive is a compatible Rom for my phone,
so all that remains now is for me to actually do the process i've seen a lot of guides around but generally they all default to a ONE S not a ONE SV which either means no one has made a full guid for SV or the S and SV are compatible ?
anyway i was hoping someone here may have the time to help me out with how to do a flash back to stock
HTC ONE SV UK Orange / EE / same carrier no SD card (if that is needed let me know)

Whippyice said:
Good morning guys,
firstly i really have tried to read up on everything i can possibly before i posted this, i've been looking around trying to get as much info as i can
So from the start my HTC ONE SV is softbricked (i think) it tried to update a few months back and half way through the process something went wrong it shut down and rebooted, and it was just a black screen and battery icon (showing that it was charging still)
I then went to Hboot Recovery and started the process, what i found odd was that when it went to the recovery icon, the 2 swirling arrows over the device icon, it would show that for a couple of seconds then reboot itself it would repeat this process for about 5 minuets then finally boot up the phone into the HTC ONE screen, chime would play (but stutters) and then load me back to where i was in the first place a black screen with the battery icon, and time
So clearly something is corrupted either the restore portion or the os it'self, i decided that it would need to be re flashed.
i have gotten as far as Ulocking the bootloader and now i have what i belive is a compatible Rom for my phone,
so all that remains now is for me to actually do the process i've seen a lot of guides around but generally they all default to a ONE S not a ONE SV which either means no one has made a full guid for SV or the S and SV are compatible ?
anyway i was hoping someone here may have the time to help me out with how to do a flash back to stock
HTC ONE SV UK Orange / EE / same carrier no SD card (if that is needed let me know)
Click to expand...
Click to collapse
Update: just to add it's stock everything i've never hacked or modded this phone so it was on the last official os for HTC ONE SV what ever that was think MAYBE 4.2.2 and i have purchased a sd card just incase it was needed,

You can flash a custom recovery (TWRP) and flash back a working rom, if the bootloader is already unlocked.

old.splatterhand said:
You can flash a custom recovery (TWRP) and flash back a working rom, if the bootloader is already unlocked.
Click to expand...
Click to collapse
ok dude, sounds like a plan,
ummmmm how lmao i see your quite knowledgable on here i see you post quite a bit so thanks for paying attention to mine, i am trying to do exactly what you said but right now nothing seems to do what is explained on the web, i have the latest TWRP.img and i've tried to push it over from adb, i get an error saying "error cannot load "recovery.img" i've made sure it's in the same DIr as my adb
i've been trying to load it onto the sd card and get it to auto update from their no success either
halp
thanks again dude, i'm tryng to not be ignorant and still reading up at the same time but nice to have some help from a pro

I've heard "i have the latest TWRP" many times, but (without wanting to hurt you) this means nothing (latest from their web page? version number? for which model? so many things which can differ)!
You need to understand to provide proper information to us, so we can help better!
Not every recovery is working on 4.2.2, but this one should do.
Read the guide there how to install, you can't flash recovery with adb!
Then we need more information about your phone model, please! There are versions of One SV with or without LTE, carrier based... ...we don't know which one you own.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)

ha ok that's fair enough i guess i know where your coming so yeah i can understand that, ok so i have the following
[Recovery] TWRP Recovery 2.7.0.x (recommended for 4.2.2
ADB
AdbWinApi.dll
fastboot
TWRP-2.7.0.1-k2_ul-k2u
in folder C:\android
(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.11.61.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(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!
Hopefully that's everything

Ok, use the recovery and the how to install, to flash the recovery.
I'll attach here a dll file which you should also use/put in your adb folder (unzipped of course).
When you are in recovery you should do wipe system, data, cache & dalvik cache (unlocking bootloader did wipe your data anyway) and then you can proceed with flashing this rom.
Your info stated you have a k2ul (with LTE), so use the k2ul version. Or, you can also restore a TWRP backup, see this thread.
Or another option would be a custom rom, like this.
Good luck!

ok so i have added the dll to the adb folder in C;\android
i opend cmd (with admin)
typed
cd \android
typed
fastboot flash recovery recovery.img
and got
C:\Android>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
i am pretty sure it's me who is doing something wrong
sorry dude, i'm a total noob at this stuff, (blame my gf for breaking my phone lol)

Your recovery.img is also in this folder?
What is the output of fastboot devices?
Is your bootloader showing on the top "Unlocked" an "Tampered"?

ok so my folder now looks like this
abd
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
recovery.img
in C:\android
What is the output of fastboot devices = i'm not sure how to tell really ?
Is your bootloader showing on the top "Unlocked" an "Tampered"? = yes in fastboot usb mode with ***tampered*** & ***unlocked*** at the top

fastboot devices should show you your serial number (which you removed in getvar result).
Something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i have currently showing
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd \android
C:\Android>fastboot devices
fastboot
C:\Android>

Ok, remove it from your post. Should be fine!
Your fastboot should be able to flash the recovery.img to your phone.
Now its time for me to go to bed.

old.splatterhand said:
Ok, remove it from your post. Should be fine!
Your fastboot should be able to flash the recovery.img to your phone.
Now its time for me to go to bed.
Click to expand...
Click to collapse
ok dude, i'll keep trying
thanks for your help
EDIT:
So i randomly managed to do it using one a all in one tool kit from Hasoon2000
one, (all varients kit) so i now have a working recovery manager,
now how do i get the flash os on their Via sd card ?
thanks

So i have managed to flash 2 roms now
1 stock rom which was provided too me, seemed to flash fine, however result is the same a black screen with battery and time with no single for data
2 team vipersv flashed fine tried various different ways of flashing it all seemed fine, boot up to same result black screen, battery icon, no reception for data
i belive that this is now not a rom issue it must be something relating to something else, 2 flashed roms with the exact same result dosn't make much sense that it would be them
i've seen a couple of other posts around is it worth re flashing a stock kernal again ? thanks

Did you flash the boot.img with fastboot?

old.splatterhand said:
Did you flash the boot.img with fastboot?
Click to expand...
Click to collapse
Hey,
i don;t think i have done that the following things have now been done
Bootloader was unlocked Via, HTCDEV code
WTRP flashed to recovery (working)
superUS flashed fine (working as far as i know)
stock kernel flashed VIA TWRP (flashed fine)
VierpSV flashed (flashed fine) same result)
Saturn III flashed (flashed fine) same result
stock flashed (flashed fine) same result,
they are the only things that have been flashed to the phone, if there is anything else that needs doing i haven;t done it as far as i know lol
EDIT;
i've just seen this in another thread i don't have my phone with me right now but assuming that my hboot is over mentioned version below could this be the problem ?
Quote:
Do I need to flash the boot.img manually in fastboot?:
No, if you're using TWRP and are on a Hboot-version lower than 1.13
Yes, if you're using any other recovery (like CWM)
Yes, if you're using TWRP and your ville has the Hboot-version 1.13 or hig
I have no flashed the boot.img (ViperSV) via fastboot so whats the difference between it being flash from twrp and from fastboot ? it seems to be still flashing the install from twrp

As you are S-On, you should definitely flash the boot.img with fastboot cmd.
Stock kernel for flashing in recovery is only for S-Off devices.

old.splatterhand said:
As you are S-On, you should definitely flash the boot.img with fastboot cmd.
Stock kernel for flashing in recovery is only for S-Off devices.
Click to expand...
Click to collapse
trying to figguer out if i am S-off or not,
is their any telltell signs that your S-off
?
EDIT
i am S-on, it says it right at the top lmao sorry
ok now i need to get S-off lmao. but i can't get into the os at pressent so i don't know if i can get S-off whitout being able to get to the os ?

No, you need a working os.
Did you flash boot.img with fastboot already?
And you can't boot into the os?

Need help restoring HTC One S. Or flash a working Rom!?

( Text below is just an explanation to my issues and why I need help! )
Hallo dear XDA forum people I ahve many times read posts and fixes about my cellphone here and managed to unlock, root and install Super SU on my HTC One S. It still has the stock rom, given it's now unlocked and rooted etc. Last weeks I've been having problems with calling out or receiving phone calls. Due to the cellphone hangs every time. So factory reset it to default. The problem persisted somewhat. It now just gets sluggish and I can't hear the other one speaking. Even though the cellphone actually made the connection. So thought about downloading a RUU or flash to another ROM to see if it's cleaner and more stable.
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 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
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/showthread.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. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum

SOLVED flashed working ROM and fixed SD card mounting error.
After 3 weeks of frustration and trying I finally got my phone booting with a ROM. As I couldn't find any RUU.exe files for my phone and the RUU.zips didn't work either I had to go custom ROMing. I'll explain the whole process with steps I did so that others can read easily
1. Go into Bootloader, choose Fastboot and connect your phone with the USB cable. Open up CMD in your Fastboot/ADB folder by holding SHIFT+Right Click and type: ''Fastboot devices'' without the quotas, to see if your phone appear like SH32HW.... etc. You can also use the command: ''Fastboot getvar all'' to pull a few lines of comparable information.
2. Download the stock recovery file here: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img , place it in the Fastboot/ADB folder and open CMD again, if you haven't already, in the Fastboot/ADB folder and type ''Fastboot flash recovery ville_recovery_signed.img''
Let the file flash and when it's done type ''Fastboot reboot-bootloader''
3. After the short reboot choose Clear Storage. Your phone might try to boot after this. just hold the power button + volume down to restart it into bootloader again. Then choose Factory Reset from bootloader menu. The phone might try to boot again after this but restart it manually into bootloader if it gets stuck.
4. After clearing storage and factory resetting go into Fastboot USB mode again and use CMD in the Fastboot/ADB folder again to flash your custom recovery file. I used TWRP 2.8.7.0.zip. This TWRP recovery is signed for HTC One S S4. The guide for the Viper ROM recommends the TWRP2.6.3.0 for phones with HBoot 2.15, and TWRP2.6.1.0 for Hboot 2.16 phones.
The command for flashing this file is ''Fastboot flash recovery twrp-2.8.7.0-ville.img''
5. After flashing the custom recovery reboot bootloader with the command ''Fastboot reboot-bootloader''. Then after the short reboot go into recovery from bootloader.
6. At this time your SD card should work. Choose to mount USB from the ''Mount'' menu in TWRP. Attach the USB cable if you haven't already. Transfer your ROM.zip file to your SD card with this method.
( I used the Viper ROM found here: http://venomroms.com/htc-one-s/ )
7. After the transfer is complete choose ''install from zip'' in TWRP and choose the ROM.zip of your choice.
( I choose the Viper_One_S_3.2.0.zip file and chose the ''full wipe'' option, removing apps I didn't want etc. )
8. After installation let the phone work it's magic for like 10-15 minutes if necessary. It'll hopefully boot into the new system in time and you can complete the setup
---
The importance is that the stock recovery steps up til I flashed TWRP again fixed the SD card error. There's more fixes you could try if this didn't work and they can be found here: http://forum.xda-developers.com/showthread.php?t=2086156

I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...

Rapier said:
I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...
Click to expand...
Click to collapse
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked Thanks by the way ^^

HTC-One-User said:
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked [emoji14] Thanks by the way ^^
Click to expand...
Click to collapse
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...

Rapier said:
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hmm... My SD card actually got un-mountable and messed up after having stock ROM and just choosing to do a factory reset in the bootloader. That is when my problems started! But now after testing just this recovery and clearing storage, factory rest, flash new TWRP in exact that order fixd my issue. If I would factory reset before clearing storage and cache it would do nothing for me. It's weird but now it's ok and works ^^
Should have made a video of me restoring my phone to youtube so others can see to O.O
Edit: Made one here. it's not in awesome quality but it shows the whole process https://www.youtube.com/watch?v=_emclhywhlw

HTC One M8 Softbricked and Unable to Flash

Hi, A friend gave me a Verizon HTC One M8 that was softbricked by a failed attempt to root or modify the device. I am unable to find out what the original owner did to the phone.
The phone will get stuck on the HTC logo for approximately two minutes and then reboot. I can get into the bootloader no problem, but the recovery and the factory wipe options go to the HTC logo and then get stuck at a black screen with the backlight on for approximately two minutes before rebooting. The command "fastboot oem rebootRUU" goes to the same HTC logo for approximately two minutes before rebooting, fastboot is unable to see the phone in this mode.
Because the bootloader is locked and cannot be unlocked because it is a Verizon, and the phone is S-ON, I am unsure how to fix the phone.
I have attempted to use RUU from a microsd card numerous times with the RUU images from here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845. the 4.4.4 one appears to complete successfully, but still bootloops after restarting.
Thank you in advance for your help.

I think (a redacted version of) the output from getvar-all would likely be helpful to see what state your phone is in and determine how to best resolve it.

Thank you for your quick reply. I have attached the "fastboot getvar all" output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <<SERIAL>>
(bootloader) imei: <<IMEI>>
(bootloader) imei2: Not Support
(bootloader) meid: <<MEID>>
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Well.....if you send that puppy to me I can s-off an attempt to reflash it for you. Not sure what else you can do with an s-on phone that you cant talk to in ruu mode.
Sent from my Nexus 6 using Tapatalk

While I appreciate your offer, I would like to try and resolve this without sending it out unless I really have to. Is there anything that you can think of that might work for me?
While I am unable to get the phone to boot into RUU mode for fastboot, I can get it to flash the RUU from microsd. For some reason it is still unable to boot after this. Is there another image or something I am doing wrong?
Thanks again for the help.

After you ran the ruu from SD did you attempt a factory reset? BTW, not sure if this helps your comfort level or not if it comes down to it but I have s-offed more vzw m9 than anyone. All done via mail.
Edit...and I would be more than willing to take a look remotely using team viewer.
Sent from my Nexus 6 using Tapatalk

When I attempt to do a factory reset, the HTC logo comes up and goes to a black screen for about 2 minutes and then bootloops. I am unable to format any partitions using fastboot and the only one that erases is cache. The big issue is that it is bootloader locked, otherwise I would have just flashed TWRP. I will contact you in private about that teamviewer help when I am at my computer. Thank you for the offer.

I thank dottat for all of his help over teamviewer.
Unfortunately, the phone has a locked emmc and is completely bricked.
Thank you everyone on this forum for your help.

So I'm having an eerily similar problem. The thing is I wasn't trying to do anything to my phone, it just randomly got stuck in a bootloop. I haven't tried anything with the RUU because I assumed it wouldn't work with verizon (I'm very new to all this) so I'm going to try later when I get the chance. What's the process to find out if the emmc is locked?

When I flashed a RUU with a newer version number then the one on it, after a reboot it would still be the old version number as if the flash did not take.

Which version number am I looking at? I know how to flash the RUU but I don't know exactly what I'm looking for there
---------- Post added at 08:46 PM ---------- Previous post was at 08:21 PM ----------
I tried a couple different files listed, and one seemed to flash correctly. I hit the update now option and now my phone won't turn on at all, no bootloader, no nothing. Bricked completely or am I waiting for something to happen??

Try charging up the phone for a bit. If that doesn't work you may have bricked it

yup, got bricked. oh well.

wmitchell2014 said:
yup, got bricked. oh well.
Click to expand...
Click to collapse
You left it on a charger? Does the light light up at all?
Sent from my SM-T320 using Tapatalk

nope, there is absolutely no response from the phone. Tried the battery recalibration thing and every other combination of things I can think of. I will leave it plugged in over night to see what happens but it was plugged in for a few hours today and nothing happened.

Attempted GPE conversion from VZW M8, no bootloader, no root, no adb, etc.
Not sure what to do at this point, have been to 10 different posts on ways to get this back to stock, or even usable and I cannot come out of this alive.
When I start up the Phone, it goes to the HTC One splash screen, then restarts, goes to it again, then goes to the Stock Recovery Screen with the Red Triangle.
I have tried to flash a rom etc using a sd card, but says this;
Install /sdcard...
Finding update package...
(waits about 2 minutes while loading)
Verifying update package...
Installation Aborted
Write host_mode:0 done
I get the red triangle recovery screen and can choose reboot system now, apply sd card, etc. as normal.
if I reboot it does the same thing.
Somehow in the conversion, my MID ended up as 0P6B17000, it used to be 0P6B20000
Cid is now 11111111, was VZW__001
I cannot access the bootloader screen so I cannot try to load using 0P6BIMG.zip
Can anyone put me out of my misery?

Connect it to a pc with adb and try "fastboot reboot-bootloader" to get from recovery to bootloader
Sent from my Nexus 5 using Tapatalk

pattafurr02 said:
Not sure what to do at this point, have been to 10 different posts on ways to get this back to stock, or even usable and I cannot come out of this alive.
When I start up the Phone, it goes to the HTC One splash screen, then restarts, goes to it again, then goes to the Stock Recovery Screen with the Red Triangle.
I have tried to flash a rom etc using a sd card, but says this;
Install /sdcard...
Finding update package...
(waits about 2 minutes while loading)
Verifying update package...
Installation Aborted
Write host_mode:0 done
I get the red triangle recovery screen and can choose reboot system now, apply sd card, etc. as normal.
if I reboot it does the same thing.
Somehow in the conversion, my MID ended up as 0P6B17000, it used to be 0P6B20000
Cid is now 11111111, was VZW__001
I cannot access the bootloader screen so I cannot try to load using 0P6BIMG.zip
Can anyone put me out of my misery?
Click to expand...
Click to collapse
If you are still s-off I can fix it. A team viewer session would help since your mid/cid are no longer standard.
Sent from my Nexus 6 using Tapatalk

dottat said:
If you are still s-off I can fix it. A team viewer session would help since your mid/cid are no longer standard.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
How do I go about doing that ?
Thank you !

pattafurr02 said:
How do I go about doing that ?
Thank you !
Click to expand...
Click to collapse
on PC,
https://www.teamviewer.com/en/download/windows.aspx