Database Info

[FIRMWARE] Official 3.19.401.101 Firmare | [Sticky thread request] |

Hey.
I have decided to share the lastest firmware.zip package from HTC for One S (Snapdragon S3, VilleC2). Follow the instructions, so you will update your hboot, radio, recovery, etc.
WARNING!
I am not responsible for bricked devices, anyway I can help you with fixing them if they are still alive
Don't repack/unpack/change content of firmware.zip or it will simply get broken! Such packages are signed with HTC's unique signature which details needed to hack unfortunately hasn't been leaked yet (and they probably won't)
You have to check if your CID* is compatibile. If it's not, firmware won't be updated.
Type:
Code:
fastboot getvar all
and look for your "CID".
Click to expand...
Click to collapse
DOWNLOAD FIRMWARE.ZIP
Instructions:
Make sure that you have all fastboot drivers
Relock your bootloader (if it is unlocked) by inputing the following method:
Code:
fastboot oem lock
Reboot to hboot and go into fastboot mode
Flash downloaded firmware.zip by inputing the method below:
Code:
fastboot flash zip firmware.zip
Wait until flashing finishes and reboot
SUPPORTED CIDS:
HTC__001
HTC__E11
HTC__304
HTC__A48
HTC__A07
HTC__M27
HTC__032
HTC__016
HTC__203
HTC__102
HTC__405
HTC__Y13
Click to expand...
Click to collapse
Congratulations, you can now flash JB custom ROMs or stock one which you can find in THIS thread! :victory:
Click "thanks" button if I helped, it is the best thing you can reward me on XDA.
*CID - Carried ID Number

this will update hboot?
Sent from my One S C2

yes, it should

bilal_liberty said:
yes, it should
Click to expand...
Click to collapse
is it neccesary to update hboot and what is diference between 2.11 and 3.19 hboot?
Sent from my One S C2

s0kY said:
is it neccesary to update hboot and what is diference between 2.11 and 3.19 hboot?
Sent from my One S C2
Click to expand...
Click to collapse
I cant see any visible difference

There is error in one step. HBOOT will not allow flashing of firmware.zip if device is not in this mode:
fastboot oem rebootRUU
At least not HBOOT 3.01

Work for Cid :BSTAR301

kayserxx said:
Work for Cid :BSTAR301
Click to expand...
Click to collapse
Is that a question or an answer? In any case? Would it Work for CID: BSTAR301? We in Latin America are seriously being left behind here.

s0kY said:
this will update hboot?
Sent from my One S C2
Click to expand...
Click to collapse
Yes, but please read OP first, then ask

maxio1998 said:
Yes, but please read OP first, then ask
Click to expand...
Click to collapse
Did you read what I wrote about flashing zips on One S C2? fastboot oem rebootRUU needs to be issued before trying to flash zip because otherwise HBOOT will deny it (at least HBOOT 3.01).
After that HBOOT will allow flashing firmware.zip but it will fail for the first time with a line to retry immediately and then will work (like on other devices).
I mean, do you even have this phone or not? This is basic stuff, add that to the original post.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.01.0000
(bootloader) version-baseband: 16.11.20.24_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.19.401.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SHXXXXXXXX
(bootloader) imei: 35XXXXXXXX
(bootloader) meid:
(bootloader) product: villec2
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PJ4020000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3925mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

How can I flash that zip for my CID 044? Coz I can't change to supercid and my phone is s-on! And I heard that there's isn't a way to s-off yet ,so flashing this zip is seem to be the only way..
Help me guys

If your CID is not on OPs list there are a bunch of OTAs for other CIDs in a thread on the general board - http://forum.xda-developers.com/showthread.php?t=2200930
If you see yours there just download the OTA, extract the firmware.zip file from it and follow OPs instructions

sending 'zip' (27598 KB)...
OKAY [ 3.471s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 7.791s
i am on cid HTC_032

s0kY said:
sending 'zip' (27598 KB)...
OKAY [ 3.471s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 7.791s
i am on cid HTC_032
Click to expand...
Click to collapse
Like I already said:
"There is error in one step. HBOOT will not allow flashing of firmware.zip if device is not in this mode:
fastboot oem rebootRUU
At least not HBOOT 3.01 "
It will fail for the first time with message to do it immediately after possible soft-reboot but then it will work. It's not a bug, it's a feature. So, you first issue fastboot oem lock, then this.
But original poster is not listening and editing first post.

rasputyn said:
Like I already said:
"There is error in one step. HBOOT will not allow flashing of firmware.zip if device is not in this mode:
fastboot oem rebootRUU
At least not HBOOT 3.01 "
It will fail for the first time with message to do it immediately after possible soft-reboot but then it will work. It's not a bug, it's a feature. So, you first issue fastboot oem lock, then this.
But original poster is not listening and editing first post.
Click to expand...
Click to collapse
i was in fastboot oem rebootRUU mode and nothing i triend 3 times in a row and i got the same message

s0kY said:
i was in fastboot oem rebootRUU mode and nothing i triend 3 times in a row and i got the same message
Click to expand...
Click to collapse
That's impossible. Only if you first didn't do fastboot oem lock. After that you do fastboot oem rebootRUU

rasputyn said:
That's impossible. Only if you first didn't do fastboot oem lock. After that you do fastboot oem rebootRUU
Click to expand...
Click to collapse
maybe because i have wiped rom in recovery ?
Sent from my HTC One S using xda app-developers app

i have flashed it again and it works

Successful!!! Thank you!

[GUIDE][MOD] Dark Bootloader | Current Firmware 7.15.401.1 | No Red Warning Text

The following are custom firmware packages that use the hboot 1.54 (bootloader) from the Google Edition version of the HTC One. Since it is from the Google Edition, the HTC branding has been removed from the bootloader screen. It also has a nice dark look to it rather than the bright white one that is the HTC stock version.
The source thread of that dump is here.
This basically means the latest firmware packages but modified to contain the GE hboot which gives the Dark Bootloader look.
Not compatible with Sprint or Verizon
S-OFF Only!
This is for only M7 UL or M7 U Devices
This mod just uses the hboot file (version 1.54) from the above dump inserted into the newly released firmware versions.
The hboot file is the bootloader of the system and since the hardware functioning of both models is the same, parts of their firmwares are interchangeable.
Since this hboot is coming from a Google Edition there is no red warning text on the bootloader and you don't have to run one of the modified hboot files to remove it.
All these firmware packages are prepared the same. Since we don't want to overwrite our custom recovery or kernel, I have pulled the stock recovery and stock kernel out, so no change to either and no data loss. If a firmware contains a new touchscreen driver that will mandate a update of your custom recovery I will make note and possibly just bundle the firmware with the update recovery (CWM or TWRP). So far the 2 packages that do contain a new touchscreen driver have not required an update to custom recoveries.
The stock radio image for each firmware is left in the package, so if you want to change your firmware version without changing your radio, simply open the firmware zip file and delete the radio.img from the zip before flashing.
Anyone interested in the different partitions of the HTC One to see exactly what is contained in some of these firmware packages look here:
Partition list Info from SneakyGhost. He shared that info here
Reference thread about stock firmware:
http://forum.xda-developers.com/showthread.php?t=2182823
Here is a screenshot of what the Dark Bootloader looks like. The RADIO and OS versions will match the firmware package. This shows the first version:
{
"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"
}
These will work as is for most MID's and CID's. You should open the android-info.txt file within the firmware zip and make sure your MID and CID is listed. Get your current MID and CID with this fastboot command:
Code:
fastboot getvar all
If yours is not listed you will need to add your CID or MID to the android-info.txt file inside the zip files I provided. Just extract the file from the zip download and edit one of the entries found in the file to your CID/MID. Save the file and then add it back to the zip. I would delete the existing android-info.txt file from within the zip before re-adding the updated one back.
Instructions for Flashing:
Boot to bootloader:
Code:
adb reboot-bootloader
Reboot RUU mode via fastboot:
Code:
fastboot oem rebootRUU
Flash the firmware:
Code:
fastboot flash zip 3.17.502.3_firmware_darkboot.zip
After it finishes, execute the command again to complete the flash:
Code:
fastboot flash zip 3.17.502.3_firmware_darkboot.zip
Output should look something like this:
Code:
D:\Phone\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb reboot-bootloader
D:\Phone\adt-bundle-windows-x86-20130522\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.048s
D:\Phone\adt-bundle-windows-x86-20130522\sdk\platform-tools>fastboot flash zip 4.3_firmware_custom.zip
sending 'zip' (28272 KB)...
OKAY [ 2.222s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.794s
D:\Phone\adt-bundle-windows-x86-20130522\sdk\platform-tools>fastboot flash zip 4.3_firmware_custom.zip
< waiting for device >
target reported max download size of 1526722560 bytes
sending 'zip' (28272 KB)...
OKAY [ 2.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,18
(bootloader) [RUU]UZ,adsp,30
(bootloader) [RUU]UZ,adsp,41
(bootloader) [RUU]UZ,adsp,52
(bootloader) [RUU]UZ,adsp,64
(bootloader) [RUU]UZ,adsp,75
(bootloader) [RUU]UZ,adsp,86
(bootloader) [RUU]UZ,adsp,97
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,22
(bootloader) [RUU]UZ,pg2fs_spcustom,41
(bootloader) [RUU]UZ,pg2fs_spcustom,70
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,31
(bootloader) [RUU]UZ,radio,37
(bootloader) [RUU]UZ,radio,43
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,74
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,24
(bootloader) [RUU]WP,radio,49
(bootloader) [RUU]WP,radio,74
(bootloader) [RUU]WP,radio,99
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 17.818s]
finished. total time: 19.882s
Now you can type reboot you are all set.
Disconnect the cable and go back into the bootloader to see the new dark theme and also notice that when you boot up there is a little lock symbol at the bottom of your splash screen that indicates your bootloader status. If you want the Dark/Inverted splash screen I have shown on my phone it can flashed separately from here.
Just install from recovery.
Here is the Bootloader Status Icon:
Enjoy, but remember - Flash at your own risk. This firmware from the 4.3 dump changes very important bootloader partitions on your phone. Make sure you have working ADB with updated drivers.
*****NOTE - The hboot in these firmware packages contains hboot 1.54 which I understand doesn't work with fastboot commands on Windows 8.1 until you have installed the Intel USB 3.0 drivers. See HERE
Downloads:
All Packages have been updated to include the latest hboot from GE 3.58.1700.5. Fastboot commands should work on Windows 8.1
3.06.1700.10 Firmware - Included Radio: 4A.18.3263.15
3.09.401.1 Firmware - Included Radio: 4A.19.3263.13
3.10.502.2 Firmware - Included Radio: 4A.19.3263.13
3.17.401.2 Firmware - Included Radio: 4T.20.3218.03
3.17.502.3 Firmware - Included Radio: 4A.19.3263.13
3.22.1540.1 Firmware - Included Radio: 4A.20.3263.16
3.24.531.3 Firmware - Included Radio: 4A.21.3263.03
3.57.401.500 Firmware - Included Radio: 4A.20.3263.30
3.62.401.1 Firmware - Included Radio: 4A.21.3263.04
3.63.707.4 Firmware - Included Radio: 4A.21.3263.04
4.06.1540.2 Firmware - Included Radio: 4A.22.3263.14
4.19.401.8 Firmware - Included Radio: 4A.23.3263.28
4.19.401.9 Firmware - Included Radio: 4A.23.3263.28
6.09.401.5 Firmware - Included Radio: 4T.29.3218.08
7.15.401.1 Firmware - Included Radio: 4T.33.3218.15
http://www.htc1guru.com/dld/4-19-401-9_firmware_darkboot-zip/
Another change from this mod is that when your phone is turned off, it will now show a battery status image when charging:
Enjoy the new Dark Bootloader Firmware Packages.
Credits:
SneakyGhost for the partition information
graffixnyc for the 4.3 Dump
Disclaimer:
I am not responsible for any damage done to your phone from flashing this.
If you like this, hit the Thanks button or toss me a small donation.
Thanks
:good:

thank you
any MD5 Sum for this firmware zip? it's important to avoid brick
EDIT: Worked perfectly, thank you!

Tabtoub said:
thank you
any MD5 Sum for this firmware zip? it's important to avoid brick
EDIT: Worked perfectly, thank you!
Click to expand...
Click to collapse
Yep, sorry. Updated the OP to include the MD5.
Thanks

i am assuming twrp or cwm recovery wont have any issue not like the 2.24 fw, cwm and twrp touch were broken

jay661972 said:
i am assuming twrp or cwm recovery wont have any issue not like the 2.24 fw, cwm and twrp touch were broken
Click to expand...
Click to collapse
No problems with recovery because the Touch drivers are not updated.

Looks like adb not working on 4.3, my device shows offline, not sure why i just flash the 2.24 fw this morning before flashing the GE 4.3
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
crushalot said:
No problems with recovery because the Touch drivers are not updated.
Click to expand...
Click to collapse
thanks but i posted a while ago my device is offline, cant figure why, usb debug is already enable, i used 2 different usb ports and cable still showing offline and i just tried my other laptop, i type adb devices, still shows offline

jay661972 said:
Looks like adb not working on 4.3, my device shows offline, not sure why i just flash the 2.24 fw this morning before flashing the GE 4.3
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
thanks but i posted a while ago my device is offline, cant figure why, usb debug is already enable, i used 2 different usb ports and cable still showing offline and i just tried my other laptop, i type adb devices, still shows offline
Click to expand...
Click to collapse
ADB is working fine for me after flashing either of these. I didn't need to update the sdk or anything but maybe you should try. In general the changes made here should not have an affect on ADB.
If you already have 4.3, then you shouldn't be flashing this! Try the 4.3 thread.

Yo dude, thanks for putting together that neat package and thread.
Was gonna drop that stuff in my thread anyway. Just too busy at work these days so hadn't had a chance. Hope you don't mind if I take this or parts of it tomorrow when I update my thread.
Talk to me if that's an issue. I'll leave credits of course.
Mobile post

jay661972 said:
Looks like adb not working on 4.3, my device shows offline, not sure why i just flash the 2.24 fw this morning before flashing the GE 4.3
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
thanks but i posted a while ago my device is offline, cant figure why, usb debug is already enable, i used 2 different usb ports and cable still showing offline and i just tried my other laptop, i type adb devices, still shows offline
Click to expand...
Click to collapse
This happened to me, I ended up re downloading the drivers. Once, I did that I went ahead and continued on to doing the process. Even if it still shows offline, you can boot in to Fastboot. The volume down and power button way.. It'll come back tho, nothing to worry about. This process to 4.3 via RUU, gave me a couple issues at first, but got it working after a bit of playing around. I got my phone to a point that my bootloader wouldn't come up and I had 4 triangle exclamation points on the each 4 corners of my screen... 8)
The 4.2.2 GE RUU brought me back to life tho.
Good Luck!!
Sent from my HTC One using Tapatalk 4

crushalot said:
ADB is working fine for me after flashing either of these. I didn't need to update the sdk or anything but maybe you should try. In general the changes made here should not have an affect on ADB.
If you already have 4.3, then you shouldn't be flashing this! Try the 4.3 thread.
Click to expand...
Click to collapse
I am on 4.3 Rom but not firmware, im still on 2.24 fw. thanks anyway man
EDIT: Flashed 4.2.2 Rom and this and i have the new GE firmware and flashed the 4.3 Rom, all good now. Thank you for this firmware

Sneakyghost said:
Yo dude, thanks for putting together that neat package and thread.
Was gonna drop that stuff in my thread anyway. Just too busy at work these days so hadn't had a chance. Hope you don't mind if I take this or parts of it tomorrow when I update my thread.
Talk to me if that's an issue. I'll leave credits of course.
Mobile post
Click to expand...
Click to collapse
No problem at all.
Love your work as I've learned a lot.
Thanks

jay661972 said:
I am on 4.3 Rom but not firmware, im still on 2.24 fw. thanks anyway man
EDIT: Flashed 4.2.2 Rom and this and i have the new GE firmware and flashed the 4.3 Rom, all good now. Thank you for this firmware
Click to expand...
Click to collapse
I see now. It still shouldn't matter. You should be able to use this package to get the 3.06.1700.10 bootloader files. Unless your on a non GSM One like from Sprint as I believe the partition layout is different for that phone, it should work.

crushalot said:
I see now. It still shouldn't matter. You should be able to use this package to get the 3.06.1700.10 bootloader files. Unless your on a non GSM One like from Sprint as I believe the partition layout is different for that phone, it should work.
Click to expand...
Click to collapse
Im on tmobile, i know its weird first time ive seen device offline. All good now. :thumbup:
Sent from my HTC One using SinLess GE Rom

jay661972 said:
Im on tmobile, i know its weird first time ive seen device offline. All good now. :thumbup:
Sent from my HTC One using SinLess GE Rom
Click to expand...
Click to collapse
Same here. T-Mobile as well. Good to hear you up and running. Have a good one mate
Sent from my HTC One using Tapatalk 4

did everything as stated and at the very end it says it's finished total time: 21.347 seconds, however on the phone it looks like its stuck at 99% with the green bar and when i try adb reboot bootloader it just says error device not found...
edit: just unplugged the cable and it went to the black hboot screen and i just held the power button and restarted and everything seems normal, so i think i'm still good lol

itzjonjon69 said:
did everything as stated and at the very end it says it's finished total time: 21.347 seconds, however on the phone it looks like its stuck at 99% with the green bar and when i try adb reboot bootloader it just says error device not found...
Click to expand...
Click to collapse
just like firmawre flashes, the greenbar won't fill 100%.
you can't adb reboot in ruu mode, you have to fastboot reboot

itzjonjon69 said:
did everything as stated and at the very end it says it's finished total time: 21.347 seconds, however on the phone it looks like its stuck at 99% with the green bar and when i try adb reboot bootloader it just says error device not found...
Click to expand...
Click to collapse
The 99% is normal. I think it's fastboot reboot-bootloader tho
Thank you for this, crushalot. It worked great, and I love the new bootloader/Hboot. Nice work sir!

descenpet said:
just like firmawre flashes, the greenbar won't fill 100%.
you can't adb reboot in ruu mode, you have to fastboot reboot
Click to expand...
Click to collapse
I just unplugged the cable and restarted the phone normally everything works great! Thanks for the help reply though!

Big thnx for this. I've been holding off flashing a custom hboot til I saw that blackness. Very nice. It worked like a champ.

Thanks for this!
While I do get the black bootloader screen, for whatever reason, I still get a WHITE splash screen with a black unlock symbol. Weird, wonder what happened...?
Sent from my One using Tapatalk 4

Stock AT&T XL won't boot after factory reset

I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.

He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)

Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img

I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon

Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?

Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.

I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.

Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon

Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.

Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382

Stuck while flashing RUU [HTC logo with 4 triangles in corner]

Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .

popo020 said:
Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588

Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help

popo020 said:
Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help
Click to expand...
Click to collapse
post it again
i can't see it
but i think you have stuck in ruu mode

This what I have in my HBOOT
=================================
*** RELOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
RUU
=================================
like in this picture
#remove space from link
Code:
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg

If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)

popo020 said:
If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?

rzr86 said:
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?
Click to expand...
Click to collapse
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle

popo020 said:
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle
Click to expand...
Click to collapse
you shouldn't use any wipe option from twrp
your system and data partitoin are corrupted probably
also you are stuck in ruu mode
try to flash the ruu manually
see how it goes
otherwise your only option is the thread i gave you in my previous post

Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing

popo020 said:
Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing
Click to expand...
Click to collapse
try with fastboot flash zip pg58img.zip

rzr86 said:
try with fastboot flash zip pg58img.zip
Click to expand...
Click to collapse
I got this error :crying:
Code:
FAILED (remote: 12 signature verify fail)

any help bro ?

At first you said you have relocked your bootloader in order to flash the RUU.You have not S-OFF so you are forbidden to use the recovery right now and probably you are stuck in RUU mode.
As long as you have "relocked" status you could unlock your bootloader again by using the command
Code:
fastboot oem unlock
or by flashing the Unlock_code.bin again
Code:
fastboot flash unlocktoken Unlock_code.bin
After those steps you should have access to bootloader again and you should be able to use recovery to correct (the possibly corrupted) partitions by using the guide that gave you rzr86.
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
It's a painful proccess but it is the only solution I can think right now.
---------- Post added at 03:53 AM ---------- Previous post was at 03:35 AM ----------
You could also check this guide out how to reformat a partition from recovery.(This guide is for HTC One and the /data partition number is probably not the same with the sensation /data partition number but I think it's a good start to read this solution)
---------- Post added at 04:06 AM ---------- Previous post was at 03:53 AM ----------
If you have access to recovery you can use adb shell to give the command
Code:
cat /proc/emmc
so you can see the numbers for every partition in your device.
You can also check this guide out.

for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work

popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
The first command doesn't always work but the unlocktoken should unlock your bootloader again.
If you use the command
Code:
fastboot reboot bootloader
after the flash of unlocktoken you should be able to see the bootloader on the next reboot.(If you can't just try to remove the battery for some time ,put it back in and press (power) + (vol-) to get the phone in bootloader mode.
Adb commands doesn't work on fastboot or RUU modes.You can only use adb by using a recovery with that capability or with a working rom.
Anyway...If nothing of them can help you you could try (by relocking your bootloader at first) to flash an extracted system.img from an RUU by using fastboot
Code:
fastboot flash system system.img
You should better try to erase data and cache partitions before you reboot and see if you have a working ROM.
Code:
fastboot erase userdata
fastboot erase cache
fastboot reboot

Thank you for reply , I have only the tow screens displayed exactly like the image
{
"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"
}
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:

popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
popo020 said:
Thank you for reply , I have only the tow screens displayed exactly like the image
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:
Click to expand...
Click to collapse
As I saw in your first post here you are saying you have hboot 1.27 (probably from a command you gave in RUU mode)
Code:
fastboot getvar all
Now as I can see in the image your bootloader status seems to be 0.85 for the model ACE (HTC DESIRE HD).If this is an enginering HBOOT and you reverted to S-ON you probably breaked your device.I just don't get it!
HTC Desire HD HBOOT
HTC Sensation HBOOT
The sensation phones are PYRAMID models!
If it has to do with wrong flash you could try this guide.
But before you try anything give the command
Code:
fastboot getvar all
one more time and copy-paste everything here.

the image not from my phone I found it in the net , just to show you what look like
This what I have in my HBOOT
=================================
*** RELOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
RUU
=================================
and getVar All
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

If you cannot unlock your device from relocked status and you cannot flash anything to it I don't think I can help you further.You can always use varius tools like riffbox to repartition emmc chip or maybe to s-off your device (Too).
Are you apsolutely sure you tried to flash a signed system.img with relocked bootloader and it didn't flash??

Only Boots to boot menu says Tampered

I'm wondering if anyone can help with this. The phone is an Unbranded UK LTE One SV that was previously running Stock Jellybean 4.22. (Manufacturer No: 99HSH008-00).
I had it from new and it was never flashed or rooted or had S off etc. It started to play up so I got another device. At one point I was able to reset it and it worked but then randomly when it booted it would only boot to a black screen with a clock at the top. Like it had not loaded all the OS. After a while it would then just power off. Now I can't get past the boot menu. I'm trying to determine if this is a hardware fault or if it just needs to be reflashed to stock if the ROM has been corrupted.
The menu says as per attached picture :
TAMPERED
LOCKED.
Security Warning
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
eMMc-boot
March 14 2013 22:10:43-1
It boots to the following menu.
{
"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 notice it gets very hot if left for a while in this menu and the battery drains quickly. Factory reset just takes me back to the same menu as does recovery. After the HTC screen it says in red that this version is for development purposes only under. I note that on other screen shots from other devices it say the memory size next to the eMMC Boot, whereas mine has none. When connected via USB the phone is recognised on the PC in Device manager. Is there any hope or anything I can try?
Any help appreciated.

Since posting I've done the following:
First I've Unlocked my phone at the htcdev site successfully.
So now it shows this in the Boot menu
Then following instructions from here: Root for HTC One SV UPDATED 23/02/13
http://forum.xda-developers.com/showthread.php?t=2113671
I then flashed recovery.img using the downloaded file on the thread labelled as the stock recovery.
I just realised though that this file is called k2u_recovery_signed.img (which i had re-named to recovery.img)
but my phone is a K2 UL. Is this the wrong recovery file to flash with? I'm unable to enter recovery mode the phone just get stuck on the HTC quietly brilliant screen with the red development version writing underneath or just reboots in a loop. It still doesn't boot properly.
I can't seem to find the correct recovery.img.
I looked on this thread here:
http://forum.xda-developers.com/showthread.php?t=2317379
where there are 2 files for K2 UL European.
Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.6-2.14.401.2)
and
Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R)
I am able to download the 2nd file from google docs but the 1st from app.box.com can't seem to be downloaded by any of my browsers.
I reflashed the 2nd K2UL recovery.img from Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R)
But it still doesn't go into recovery mode. I sometimes get the green download arrow then it goes black or just goes straight to black so i guess its not the right file either. Is there an alternate link for the other file anywhere, so I can try that?
recovery.img
Md5Sum: B219A04154A3ED29271B14F120FDE853
I was unable to enter recovery before this so think it was already corrupted.
having no luck finding that recovery assuming its the right one. leaving it for now.

I think, that you can't boot into recovery, is a problem of mismatching files. You are using older recovery files with latest firmware.
But at least i don't know what software/firmware you are running on your phone, so try to get some more info by using fastboot with the following cmd:
Code:
fastboot getvar all
Put the output here without serial and imei numbers.
For a recovery which works with latest software, look here.
At all, this thread is a good start, if you are looking for something this phone related.

Thank you for the prompt reply, here's the info. The boot menu is now frozen so will have to remove the battery to try again and flash with that recovery you recommended. The link for TWRP 2.8.4.0 touch recovery on that thread is now dead. Is the latest version from here on (https://twrp.me/devices/htconesvlte.html) ok? It appears that
twrp-2.8.5.0-k2_ul.img is the newest compatible. Will this replace the stock recovery (that presently is likely the wrong one as the file on the other thread was non downloadable for me from app.box.com. Another link would be great, assuming its the correct file.
My aim is to get this phone working again, initially as stock jellybean 4.22 so it can be used then maybe experiment. As of now its still S-ON and unrooted but with an unlocked bootloader, but wont work at all.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2
(bootloader) version-baseband: 1.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.40
(bootloader) version-misc: PVT SHI
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233
(bootloader) partition-layout: Gen
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

twrp-2.8.5.0-k2_ul.img from here https://dl.twrp.me/k2_ul/twrp-2.8.5.0-k2_ul.img.html is now flashed and working. It's on here as the latest working version https://dl.twrp.me/k2_ul/.

lucids said:
Will this replace the stock recovery...
Click to expand...
Click to collapse
Yes, it will.
....(that presently is likely the wrong one as the file on the other thread was non downloadable for me from app.box.com. Another link would be great, assuming its the correct file.
Click to expand...
Click to collapse
You don't need stock recovery (anymore). As your system won't boot, you need another way to get your phone working and the key for this is a custom recovery.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2
(bootloader) version-baseband: 1.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.40
(bootloader) version-misc: PVT SHI
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233
(bootloader) partition-layout: Gen
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Your fastboot output seems to be some kind of "cutout". Should look like this:
D:\adb>Fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.21.40f.00.23
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.164.107
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid:
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(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!
Click to expand...
Click to collapse
finished. total time: 0.132s
twrp-2.8.5.0-k2_ul.img from here https://dl.twrp.me/k2_ul/twrp-2.8.5.0-k2_ul.img.html is now flashed and working.
Click to expand...
Click to collapse
This is good and the next step forward.
Now, from TWRP recovery, you have 2 options to get your system working:
- you can flash a stock or custom rom
- you can restore a stock backup
It's up to you now!

Ok thanks, not sure what you mean by it being a "cut out". Mine is a non SIM locked unbranded UK One SV. Prior to it going faulty it had never been flashed or rooted etc.
EDIT:
Ah I see some of the info never pasted correctly I just noticed. Here it is in full.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ******
(bootloader) imei: *******
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.089s
Bearing in mind that the bootloader is now unlocked , but its still is S-ON and unrooted what is the next step for me to recover the newest JB4.22 that I had earlier and have the phone rooted. Do I need to have S off before in order to flash a ROM back on?
I have already downloaded several files but not sure which is the correct one and the procedure.
I already have:
OTA_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1-2.14.401.6_release_338297mseg08soslxcubit.zip (431MB)
(MD5: 0d6c763962fdc8915096b11b84329dc1)
PL80IMG_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1_Radio__1.18.40a.00.05_10.81a.40.23L_release_338297.zip (674MB)
(MD5: 336f6d914ac4b7799dca4d35bfe536ed)
Thank you again for your help.

lucids said:
Bearing in mind that the bootloader is now unlocked , but its still is S-ON and unrooted what is the next step for me to recover the newest JB4.22 that I had earlier and have the phone rooted. Do I need to have S off before in order to flash a ROM back on?
Click to expand...
Click to collapse
No, S-off needed.
I think the easiest way is to restore a TWRP backup: you can use this twrp backup to restore a working OS on your phone.
This is not to flash, you must use restore.
The location on ext_sdcard for the backup is:
\TWRP\BACKUPS"Put here the serial number of your device"\Backup files you have downloaded
Or the location where the files have to be that TWRP can recognise them, explained by another guy:
Modding.MyMind said:
TWRP (folder) >> BACKUPS (folder)>> Serial Device (folder)>> Name of Backup (folder)>> backup files
If those folders do not exist as listed above then make them. Serial device will be the devices actual serial number, by typing and entering, fastboot devices, will display the serial number. Name that folder as such.
The folder which is referred to the name of the backup you can simply call it whatever. For example, help_me_422.
Place backup files inside the "help_me_422" folder.
Go to main menu of the TWRP, click on restore, you backup will be on the external sdcard so insure you select that storage so the backup will appear as an option. Now select the backup. A list for system, boot, etc, etc will appear with boxes and a check in those boxes. Now swipe to restore.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse

Thank you for the info.
So as you said there is no need for S-Off now.
On 1st attempt the Restore failed as I put the zip file itself into the last folder as opposed to all the individual files themselves and their MD5's [boot.emmc.win, data.ext4.win, recovery.log, system.ext4.win]. The restore then said it completed successfully.
Still the phone will not work and gets stuck on startup with the HTC screen with the red development only version writing underneath.
I notice that the external SD card which shows its size next to it but the internal SD card is showing as 0MB. And also when the 1st restore failed it reported that it was unable to mount the Internal SD memory. The same is true after the restore success, it says unable to mount int_sd. (See pics below). is there a way to test the internal memory to see if there is another problem or does it need re partitioning, if this isn't done via the restore process itself?

Hm, sounds not so good...
Well, i don't know this TWRP version exactly, as it is long time ago i used it.
But go to the wipe menu and look, if there (or under wipe - advanced) is an option something like "repair broken filesystem" or so (can't remember exactly what it is called).
If yes, go there and try if this option can help.

on the main menu there is WIPE - that says it does a factory reset, Wipes Cache and Dalvik
Or
There is an Advanced as you remembered well where you can choose the partitions
Dalvik cache
Cache
Data
Int SD
Android Secure
SD card
System
Either you can select to wipe the selected partitions or with another button at the bottom Repair or Change File System
I selected IN_SD and clicked to Repair and it showed as being 0MB then Failed as per attached pics. I was able to repair the cache and Dalvik cache but the Int SD still saying unmountable. Same result not working.

lucids said:
on the main menu there is WIPE - that says it does a factory reset, Wipes Cache and Dalvik
Or
There is an Advanced as you remembered well where you can choose the partitions
Dalvik cache
Cache
Data
Int SD
Android Secure
SD card
System
Either you can select to wipe the selected partitions or with another button at the bottom Repair or Change File System
I selected IN_SD and clicked to Repair and it showed as being 0MB then Failed as per attached pics. I was able to repair the cache and Dalvik cache but the Int SD still saying unmountable. Same result not working.
Click to expand...
Click to collapse
Ok, it seems that you only have one chance for your phone, a ruu.
Download this file: https://www.androidfilehost.com/?fid=24369303960683578
Rename the zip file to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard.
As you are S-on, you need to lock your bootloader again, first. Do this with the fastboot cmd
Code:
fastboot oem lock
Then boot into the bootloader and let the phone recognize the PL80IMG.zip. Confirm to update with vol+ and let it run until its finished.

Ok now while having selected the Int SD partition instead of selecting Repair I selected Change File System and then in there selected FAT, it completed and has gone back to this menu but now shows as being 4239MB as opposed to 0MB.
I will have another look at it later but presently its still not booting to the system.
Now in the Restore menu the Internal is showing 4239MB also instead of 0Mb.
So I'm trying a restore again. Fingers crossed....
This time no errors regarding mounting the Int SD but on Rebooting it goes to HTC with red writing for 30 sec then goes off.

Give the Ruu a try. It should restore everything to stock, if possible.

Thanks i posted the last post before seeing your reply about the RUU. I will give that a go and report back. After i tried the restore again (after the int Sd came back) the int sd again went back to 0MB and being unmountable. i had to fix it and format again for it to reappear as 4gb.
I relocked the bootloader so it now says Tampered and Relocked.
Re booted into the bootloader with the Ext sd card in with the PL80IMG.zip. at its root. (MD5 all ok)
First it says loading... [PL80DIAG.zip]
No Image!
Then loading... [PL80DIAG.nbh]
No image or wrong image!
Then Loading... [PL80IMG.zip]
After finding it it then says
Checking....[PL80IMG.zip]
But then remains in the bootloader after a minute or two when finished. Nothing happens for me to confirm with Vol+. I have no option to update?
If I choose Recovery from the bootloader it immediately just reboots to the bootloader again.
in fact whatever i do now it just goes straight back to the bootloader.

Ok, in this case i think you are out of luck. Sorry to say, but something seems broken, which even a ruu can't fix.

Just a thought, correct me if I'm wrong. Does the RUU require a working Recovery? If you remember my Recovery was previously corrupted I believe and before putting on TWRP there was no working stock recovery. Now TWRP is no longer available (because the bootloader is re-locked?) there is no working stock recovery to revert to in order to flash the RUU. If this is so is there a way to unlock the bootloader then put back a correct stock Recovery then re-lock it and use the RUU?

lucids said:
Just a thought, correct me if I'm wrong. Does the RUU require a working Recovery?
Click to expand...
Click to collapse
No, usually not. The Ruu has the stock file itself inside.
But, of course, you can try it. In this case you need to unlock bootloader again, then you can flash it with fastboot cmd.
I can upload the recovery.img if you want.
For the unlock you can use the already existing unlock_code.bin, i think.

Well it's worth a go I guess. Thank you that Recovery image would be very useful as I was unable to locate it or download from the app box link. My friend still uses his One SV so could come in useful at some point anyway.
I've re-Unlocked the Bootloader again and TWRP is still present and working when I select Recovery.
I'll wait for your new upload of the correct stock Recovery image and try with that.
Thanks again

lucids said:
Well it's worth a go I guess. Thank you that Recovery image would be very useful as I was unable to locate it or download from the app box link. My friend still uses his One SV so could come in useful at some point anyway.
I've re-Unlocked the Bootloader again and TWRP is still present and working when I select Recovery.
I'll wait for your new upload of the correct stock Recovery image and try with that.
Thanks again
Click to expand...
Click to collapse
Stock recovery k2ul Android 4.2.2
https://www.androidfilehost.com/?fid=385035244224390400