Database Info

VomerGuides [M7]: S-OFF, SuperCID, Firmware Upgrade & Custom Recovery

Welcome to VomerGuides: [M7 Edition]
Have an M8? There's a guide for that!
Hey folks!
Many of you will find this post similar to the ARHD posts I have made.
Based on several suggestions and PM's - I decided to make a separate thread in the hope that this will stop some repeated questions asked in multiple threads.
Following this guide will allow you to (in this sequence):
- Achieve S-OFF using revone
- Change your CID to SuperCID (allowing you to bypass regional ROM restrictions)
- Upgrade to the latest firmware (UL edition) without loosing any data on your SD card
- Install the latest TWRP recovery
Donations:
I do not believe that I should be charging for information sharing. However, having the physical hardware helps me improve this content and support you better as I do require hardware to test/work on for all my content and it's not always possible for me to find someone to borrow devices from.
If you would like to support my work donate to me via:
Thank you
Disclaimer & Copyrights:
I test everything before I share these guides - thus I know they work as intended. However, please proceed at your own risk as I do not take any liability for your devices.
Please do not copy contents of this guide without explicit permission from me. I like to maintain a set standard and quality of the information I share.
Please refrain from posting mirrors as I like to track downloads - I primarily use AndroidFileHost and they mirror files on multiple servers automatically.
I like to track downloads - so please use the official links provided in this guide.
Here is a mirror for all the files in case main links down:
- Firmwares
- Everything Else
Other useful files:
These files can be used to replace/add features in the latest firmware zips posted in this thread.
- Hboot v1.44: http://d-h.st/1zJ
- Touch panel Driver from firmware 2.24.401.1: http://d-h.st/lL4
- Flash-able Radio Collection: http://forum.xda-developers.com/showthread.php?t=2419699
- Going back to stock ROM: http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
Windows Users: It's a good idea to install the HTC drivers on your pc: http://d-h.st/4LL or use this toolkit to install the drivers.
READING & FOLLOWING EACH STEP IS KEY TO SUCCESS.
SECTION 0: SYSTEM PREPARATION:
First we need to get you ADB and fastboot
Windows Users, download this file and extract the folder called "adb" to your C: drive. Your path should look like this:
Code:
C:\adb\
Also, you will need to open a command prompt window using this method:
Code:
Go to the C:\adb\ folder - hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
Mac/Linux users install ADB & fastboot using: Download
1. Extract the downloaded zip to your desktop
2. Open Terminal and type in:
Code:
su
cd Desktop/Android/ (note: Android is the directory extracted from zip file)
3. Now type
Code:
./ADB-Install-Mac.sh
Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/
SECTION 1: S-OFF & SUPERCID
Downloads Required:
- revone (hboot 1.44)
- rumrunner (hboot 1.5x)
Note: If you are running a 4.4 based ROM and do not want to downgrade to a lower version to use revone or rumrunner - try this tool to S-OFF
Note: revone (used for s-off) has been reported to work best with 4.2.2 roms. Please install a 4.2.2 ROM before attempting S-OFF.
Note: If you are using rumrunner - please follow the instructions to s-off provided on the rumrunner link above. Steps below are for revone only.
Note: Read these useful tips before attempting S-OFF
Mac/Linux users: Save this file to your Desktop
Windows users: Save this file to the C:/adb/ folder
Also, before continuing - make sure you have USB Debugging enabled on your phone (Settings -> Developer Options -> USB Debugging)
If you do not see "Developer Options", Go to Settings > About phone > Software > More > click on build number 10 times. This should enable that section.
Part 1
1. Push revone to your device:
Code:
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
Windows: adb push C:/adb/revone /data/local/tmp/
2. Open adb shell by writing:
Code:
adb shell
su
3. Write in the shell:
Code:
cd /data/local/tmp
4. Then write this:
Code:
chmod 755 revone
5. Next, write the following command:
Code:
./revone -P
6. Revone reported that I needed to reboot and try again. So I wrote :
Code:
reboot
[COLOR=Red][B]Note:[/B][/COLOR]
[B]Stuck with error: -1?[/B]
When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.
To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
7. Close your Command Prompt/Terminal window. Open it again and type:
Code:
adb shell
su
8. Write (to change directory in the phone):
Code:
cd /data/local/tmp
8a. Write the following command:
Code:
./revone -P (it will now say success and ask to reboot phone - do it by typing: reboot)
8b. Once rebooted - repeat steps 7 & 8
9. To get S-OFF & unlock, write the following command:
Code:
./revone -s 0 -u
10. revone will report success. Exit the shell:
Code:
exit (or just close terminal and open a new one)
11. Reboot into bootloader:
Code:
adb reboot bootloader
12. Check if the bootloader screen show's you as S-OFF (it should be in the in the first line under the "pink" highlighted text)
13. Reboot the phone
14. Start the adb shell, again:
Code:
adb shell
15. Change to the folder where revone is stored by typing:
Code:
cd /data/local/tmp
16. Request revone to reset tampered flag by typing:
Code:
./revone -t
17. Exit the adb shell by writing: exit (or just close terminal and open a new one)
18. Reboot to the bootloader by writing:
Code:
adb reboot bootloader
19. Phone should now be S-OFF and tampered flag should be gone
Now stay at this bootloader screen with your phone plugged in to the PC - and follow the steps in Part 2 below.
Part 2
Now lets get you SuperCID:
1. Open terminal/command prompt and type (copy paste command below or make sure there a eight 1's):
Code:
fastboot oem writecid 11111111
2. Reboot phone into bootloader mode (by typing: adb reboot bootloader) and verify CID#. It should look similar to 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"
}
SECTION 2: FIRMWARE UPGRADE
FIRMWARE FAQ:
Q: Do I need S-OFF for firmware flashing?
A: YES!
Q: Do I NEED to update my firmware?
A: NO! But doing so ensures optimal phone performance.
Q: Does it matter when I flash the firmware (before or after new ROM install)
A: NO!
Q: Will updating the firmware erase my SD card or Apps?
A: NO! The firmware files provided in this guide take care of this for you so none of those get erased.
Q: If I only flash the ROM, will I get updated to the latest firmware?
A: NO!
Q: Can I install a U edition firmware on a UL edition phone?
A: YES, but you might loose the ability to connect to LTE or have some other incompatibilities.
FIRMWARE FLASHING:
Firmware Downloads (SD card will not be wiped using these files):
4.2.2 Base Firmwares:
- 2.17.401.1: http://d-h.st/PJv (Rename to firmware.zip after downloading)
- 2.24.401.1: http://d-h.st/WO9 (Rename to firmware.zip after downloading)
- 2.24.401.8: http://d-h.st/qPT (Rename to firmware.zip after downloading) *LATEST*
4.3 Base Firmwares:
- 3.06.1700.10: http://d-h.st/maA (Rename to firmware.zip after downloading)
- 3.09.401.1: http://d-h.st/PSE (Rename to firmware.zip after downloading)
- 3.17.401.2: http://d-h.st/bgE (Rename to firmware.zip after downloading)
- 3.22.1540.1: http://d-h.st/LLO (Rename to firmware.zip after downloading)
- 3.57.401.500 : http://d-h.st/z6g (Rename to firmware.zip after downloading)
- 3.62.401.1 : http://d-h.st/in6 (Rename to firmware.zip after downloading) *LATEST*
4.4 Base
- 4.06.1540.2 (Rename to firmware.zip after downloading)
- 4.06.1540.3 (Rename to firmware.zip after downloading)
- 4.19.401.8 (Rename to firmware.zip after downloading)
- 4.19.401.9 (Rename to firmware.zip after downloading)
- 4.19.401.11 (Rename to firmware.zip after downloading)
- 5.11.1540.9 (Rename to firmware.zip after downloading)
- 5.11.401.10 (Rename to firmware.zip after downloading)
- 6.06.401.1 (Rename to firmware.zip after downloading)
- 6.09.401.5 (Rename to firmware.zip after downloading)
- 6.09.401.10 (Rename to firmware.zip after downloading) *LATEST*
-----
Windows users, you need to do these steps first:
- move the file you downloaded and renamed (firmware.zip) to the C:\adb\ folder.
- next, in the C:\adb\ folder hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
-----
First, plug in phone to PC and type this in terminal/command prompt:
Code:
adb reboot bootloader
-----
Let's start by checking current system details. Type:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000 [COLOR=Red][B]< This is your bootloader version[/B][/COLOR]
(bootloader) version-baseband: 4A.16.3250.24 [COLOR=Red][B]< This is your radio version[/B][/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17 [COLOR=Red][B]< This is your firmware version[/B][/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <you don't need to know my serial#>
(bootloader) imei: <you don't need to know my IMEI>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111 [COLOR=Red][B]< This is your CID[/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4077mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Now type:
Code:
fastboot reboot-bootloader
After that, type:
Code:
fastboot oem rebootRUU
Note: You should see a silver HTC logo come up on your phone after executing this command.
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
fastboot flash zip /Users/vomer/Desktop/firmware.zip
Windows users: your command will look something like this: fastboot flash zip C:\adb\firmware.zip
Got this:
Code:
sending 'zip' (71868 KB)...
OKAY [ 4.936s]
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: 6.410s
Repeated same command:
Code:
fastboot flash zip /Users/vomer/Desktop/firmware.zip
Got this:
Code:
sending 'zip' (71868 KB)...
OKAY [ 4.884s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[cir] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(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]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,53
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 39.601s]
finished. total time: 44.485s
Note: On my phone's screen the green bar did not go to 100% of the bar ... but everything seemed ok so I moved on.
Last Step:
Code:
fastboot reboot
Then I went back to the bootloader mode (after the phone reboots successfully):
Code:
adb reboot bootloader
Checked if the update worked:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-baseband: 4A.17.3250.14 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: you don't need to know my serial#
(bootloader) imei: you don't need to know my IMEI#
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111 [COLOR=Red][B]< Oh Look! I'm Superman :) [/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
SECTION 3: RECOVERY
Note: I personally prefer TWRP - so my guide below points to using TWRP.
If you like CWM, you can follow the same steps but with the latest CWM file.
----
Get latest TWRP: http://techerrata.com/browse/twrp2/m7ul
With your phone plugged into your PC, type in:
Code:
adb reboot bootloader
Once in bootloader mode, type:
Code:
Mac/Linux: fastboot flash recovery /Users/vomer/Desktop/openrecovery-twrp-2.6.1.0-m7.img
Windows: fastboot flash recovery C:\adb\openrecovery-twrp-2.6.1.0-m7.img
Then:
Code:
fastboot reboot
You are now the the latest version of TWRP.
----
That's it! Enjoy your new found freedom

finally you made own thread

descenpet said:
finally you made own thread
Click to expand...
Click to collapse
haha yes sir! got so many PM's to do it but I didn't want to half-ass it. Had some time today so decided to get it done the proper way!

It is necessary to have bootloader unlocked?
Sent from my HTC One using xda premium

Omg thank you so much I hope this will fix my sleep of death on cm roms issue.

Amazing and easy to follow. Thanks OP

vengadorhq said:
It is necessary to have bootloader unlocked?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes, bootloader must be unlocked if your looking to do any customization!

STICKY THIS THREAD!!!
Great guide!

Wait... I need to re-lock my bootloader and remove root and go back to stock to get S-OFF? o.o?

aulterra said:
Wait... I need to re-lock my bootloader and remove root and go back to stock to get S-OFF? o.o?
Click to expand...
Click to collapse
What?
Sent from my HTC One using xda premium

Wonderful thread. It's of no use to me, but I tossed you a Thanks because when it concerns S-OFF, the simplest and most easy-to-follow guides make all the difference for frightened users.
Thanks!

descenpet said:
What?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Well i'm rooted and have my bootloader unlocked from htcdev but i'm S-ON so do I need to relock to use revone to get S-OFF? Or not? Or relock and un root? Or?

aulterra said:
Well i'm rooted and have my bootloader unlocked from htcdev but i'm S-ON so do I need to relock to use revone to get S-OFF? Or not? Or relock and un root? Or?
Click to expand...
Click to collapse
No relock needed
Sent from my HTC One using xda premium

Devaster said:
No relock needed
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
So I can Go ahead now and get S-OFF right now using revone even with an already unlocked bootloader?

aulterra said:
So I can Go ahead now and get S-OFF right now using revone even with an already unlocked bootloader?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 7

vomer said:
Yes
Sent from my Nexus 7
Click to expand...
Click to collapse
Ok sounds great. Do you think that once I have S-OFF and Super CID that the Firmware update will fix my Sleep of Death issues on CM roms? codeworkx said the issue is from what he said a KGSL derp or something. The firmware update would update the gpu driver or update stuff that would effect the gpu driver?
Just wondering, thanks for the amazing guide btw, easiest i've seen so far to follow. Will be doing it tonight after work. Wanted to do it now but I decided not to since I need my phone charged as much as possible before I go to work today (have to get into work early and I didn't know until before so My phone was nearly flat xD)

aulterra said:
Ok sounds great. Do you think that once I have S-OFF and Super CID that the Firmware update will fix my Sleep of Death issues on CM roms? codeworkx said the issue is from what he said a KGSL derp or something. The firmware update would update the gpu driver or update stuff that would effect the gpu driver?
Just wondering, thanks for the amazing guide btw, easiest i've seen so far to follow. Will be doing it tonight after work. Wanted to do it now but I decided not to since I need my phone charged as much as possible before I go to work today (have to get into work early and I didn't know until before so My phone was nearly flat xD)
Click to expand...
Click to collapse
I am not sure on gpu drivers, but this should solve the issue if it is firmware related.
Sent from my Nexus 7

Superb guide! Thanks a lot bro!

Do you no how to get rid of the red writing in boot up splash screen. One thread I read is very confusing. Do I just flash the modified hboot zip?
Sent from my HTC One

Excellent guide, should definitely be stickied. Thanks Vomer :beer: :beer: :beer:
Sent from my HTC One using Tapatalk 2

Search and install problem for RUU_K2_UL

Hi guys, i have a htc on sv. the system not start and enter on recovery
https://www.dropbox.com/s/8xfq4s4rdygh8d9/IMG_20140531_185337.jpg
As you can see i cant remove the S-On (i try htcdev, send me all instruction , i did all fine , but cant select of like the instruction of htcdev)
i try another way for install into microsd or with fastboot the rom
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT312TP02396
(bootloader) imei: **********
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3466mV
(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.080s
Click to expand...
Click to collapse
if i try to go on recovery
SD Checking...
No gift file....
Loading...[PL80DIAG.zip]
No image!
Loading...[PL80DIAG.nbh]
No image or wrong image!
Loading...[PL80IMG.zip]
Loading...[PL80IMG.nbh]
No image or wrong image!)
Click to expand...
Click to collapse
so i found this : RUU_K2_UL_JB_45_S_HTC_Europe_2.14.401.6_R_Radio_1. 15.40a.00.14_2_10.74a.40.23L_release_unsigned.zip
i try to install but give me error , i try to extract rom.zip and renamed to pl80diag.zip, (into microsd) , try the recovery...seems fine but give me error
so i try to :
C:\Android>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) Start Verify: 3
OKAY [ 0.037s]
finished. total time: 0.037s
C:\Android>fastboot flash zip RUU_K2_UL_JB_45_S_HTC_Europe_2.14.401.6_R_Radio_1.
15.40a.00.14_2_10.74a.40.23L_release_unsigned.zip
sending 'zip' (604746 KB)...
OKAY [ 35.290s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 109.491s
Click to expand...
Click to collapse
what can i do? the way is right or i need to do something new?

To go to recovery you can press and hold the power and volume down keys while your device is powered off. Then when your bootloader appears on the screen select the recovery option. Or you can use adb and type then enter:
Code:
adb reboot recovery
What you showed to be your recovery is NOT your recovery. That is your bootloader. They are different.
The only way you will achieve an unlock bootloader for your device will be to use your unlock_code.bin file provided to you through an email by HTC.
You must be in fastboot to proceed using that file.
On your screen it should display in red text, fastboot usb. When you see this on your screen then you may continue forward with unlocking your bootloader using the .bin file and instructions provided to you from HTCDEV.
With this said, you have already opened up a thread over in the Q&A section. This is a forum for Android Development.
Sent from my C525c using Tapatalk

Modding.MyMind said:
To go to recovery you can press and hold the power and volume down keys while your device is powered off. Then when your bootloader appears on the screen select the recovery option. Or you can use adb and type then enter:
Code:
adb reboot recovery
What you showed to be your recovery is NOT your recovery. That is your bootloader. They are different.
The only way you will achieve an unlock bootloader for your device will be to use your unlock_code.bin file provided to you through an email by HTC.
You must be in fastboot to proceed using that file.
On your screen it should display in red text, fastboot usb. When you see this on your screen then you may continue forward with unlocking your bootloader using the .bin file and instructions provided to you from HTCDEV.
With this said, you have already opened up a thread over in the Q&A section. This is a forum for Android Development.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Hello , this is the image not compare when i make the procedure HTCDEV, i think not compare because the operating system not go
https://www.dropbox.com/s/2s8t8dar0uil7yc/2014-06-05 17_11_28-HTCdev - Unlock Bootloader.png

@Benz83
You should have a file called, Unlock_code.bin. Place it in the same directory that currently holds your adb and fastboot files. Open up the command prompt window and change directories to the location where your adb and fastboot files currently are.
Type the following:
Code:
adb reboot bootloader
You should now see on your device screen, fastboot usb.
Go back to your command prompt window....
Type the following:
Code:
fastboot flash unlocktoken Unlock_code.bin
On your device you’ll get a message saying if you want to unlock your bootloader. Use the volume keys to select your choice, and hit the power button to confirm. Once you’re done, your device will restart and you’ll have an unlocked bootloader.
Sent from my C525c using Tapatalk

sincerally the reply on msdos is ok, all done
on the phone i not see nothing and i not see the image i posted, i will try again

Benz83 said:
sincerally the reply on msdos is ok, all done
on the phone i not see nothing and i not see the image i posted, i will try again
Click to expand...
Click to collapse
I edited my last comment. Go back and read it again.
Sent from my C525c using Tapatalk

No choose to select. Only reboot automatically

@Benz83
I want you to tell me where on your computer you currently have your adb, and fastboot files. I also want you to tell me where on your computer you currently have your Unlock_code.bin file.
Type it out as it would be on your computer.
Sent from my C525c using Tapatalk

easy
its all inside the C:\Android
fastboot adb and unlock
so inside the dir C:\android
the phone reboot on fastboot usb i type
fastboot flash unlocktoken Unlock_code.bin

Benz83 said:
easy
its all inside the C:\Android
fastboot adb and unlock
so inside the dir C:\android
the phone reboot on fastboot usb i type
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Good, so you are doing it the right way. Boot your device in to your bootloader using adb.
Code:
adb reboot bootloader
Then on your device select the option, bootloader. At the top of your screen on your device it should say either locked or unlocked. Which one does it show for you?
Sent from my C525c using Tapatalk

Modding.MyMind said:
Good, so you are doing it the right way. Boot your device in to your bootloader using adb.
Code:
adb reboot bootloader
Then on your device select the option, bootloader. At the top of your screen on your device it should say either locked or unlocked. Which one does it show for you?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
locked :crying:

Benz83 said:
locked :crying:
Click to expand...
Click to collapse
Your Unlock_code.bin is corrupted then. Try redownloading it from the attachment in your email. If it still doesn't work then you either left out some needed info when copying and pasting your token or you added more info than what was actually needed while following the steps on the HTCDEV website.
You may need to do that step again and insure you copy EXACTLY what is needed for your Unlock_code.bin file. Then when you receive your new .bin file go ahead and do as you have been doing with trying to unlock your bootloader.
Sent from my C525c using Tapatalk

ok, i will do again, (sincerally i did twice)

Benz83 said:
ok, i will do again, (sincerally i did twice)
Click to expand...
Click to collapse
Make sure you choose "other" when selecting your device.
Sent from my C525c using Tapatalk

yes yes, infact there isnt thad device

Benz83 said:
yes yes, infact there isnt thad device
Click to expand...
Click to collapse
nothing to do, i try again the all procedure but the screen step 10 after command fastboot flash unlocktoken Unlock_code.bin not let me choose nothing

ok, i will do

I also have this problem
hi
i have a HTC one SV and when tern on android not loded and go to bootloader.
i try factory reset but fast reset and come back to bootloader
i try unlock bootloader but after step 10 in htcdev in my phone not show dialog to select YES or NO
in my android folder contain this files:
{
"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've searched until I find a solution to my problem but I can not find any solution.
Can you advise me what should I do?
tanks

I don't know, whats wrong with your phone, but why are you doing a "fastboot oem rebootRUU"?
When i can remember correct, this is not needed for unlock, after flashing unlock token.

[RUU][India] HTC One E8/ M8 Ace DWGL - M8sd - 1.26.720.6 (stock) - 0PAJIMG

Hi guys,
So I got this RUU from a "friend". Here it is as promised. Have fun!
Code:
Don't try to flash this if you flashed the Lollipop RUU before this. It won't work.
Even if it does work, you may end up bricking your device.
If you end up bricking your phone, don't blame me.
Code:
0. Charge your phone to at least 60% to be on the safe side
1. Copy the file to an sdcard
2. Rename it to 0PAJIMG.zip
3. Turn off the phone
4. Press and hold valume down + Power till the HBOOT screen shows up
5. Follow the instructions
Don't forget to hit thanks if this helps you..
Hash Values: (please verify before flashing)
Code:
SHA1: A3492D5096005187DA1423416532B4932EC8BF21
MD5: 1A14A2DD4DDDF822E903D8EDAE885A77
CRC32: 355CEF2F
Download
{
"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"
}

Thanks buggerman for the effort. I am downloading it.

@ buggerman
i'm getting an error message saying
Device halted due to Large Image update fail! Press <POWER> to reboot.
Click to expand...
Click to collapse
I'm on stock recovery and s-on
Pls help

iamsuperuser said:
@ buggerman
i'm getting an error message saying
I'm on stock recovery and s-on
Pls help
Click to expand...
Click to collapse
Did you relock bootloader first?

Captain_Throwback said:
Did you relock bootloader first?
Click to expand...
Click to collapse
No i did not relock bootloader . Is it necessary ??
I'm on s-on , is s-off required for flashing ruu ??

iamsuperuser said:
No i did not relock bootloader . Is it necessary ??
I'm on s-on , is s-off required for flashing ruu ??
Click to expand...
Click to collapse
I think bootloader lock is required. As far as I know, S-Off is only required if you're flashing some other CID RUU..

buggerman said:
I think bootloader lock is required. As far as I know, S-Off is only required if you're flashing some other CID RUU..
Click to expand...
Click to collapse
How do I get s-off , sunshine did not work on 1.26.720.6
You said s-off maybe possible on 1.25.720.3, so where can I get 1.25.720.3 ??

iamsuperuser said:
How do I get s-off , sunshine did not work on 1.26.720.6
You said s-off maybe possible on 1.25.720.3, so where can I get 1.25.720.3 ??
Click to expand...
Click to collapse
SunShine doesn't work on all devices. Depending on the error message SunShine gave you when you tried it, you may just have to wait until SunShine 3.0 is released.
But yes, if you are S-ON, you MUST relock your bootloader to run an RUU.

Captain_Throwback said:
SunShine doesn't work on all devices. Depending on the error message SunShine gave you when you tried it, you may just have to wait until SunShine 3.0 is released.
But yes, if you are S-ON, you MUST relock your bootloader to run an RUU.
Click to expand...
Click to collapse
Is it possible to relock with s-on ??
Coz in THIS thread it says i must be s-off
Pls help

iamsuperuser said:
Is it possible to relock with s-on ??
Coz in THIS thread it says i must be s-off
Pls help
Click to expand...
Click to collapse
You only have to relock if you are S-ON. Just a simple "fastboot oem lock" takes care of that. But then you have to immediately flash a proper RUU to get back to a working device.
That thread you linked is unrelated to any of this. That's specifically for people that are already S-OFF.

Captain_Throwback said:
You only have to relock if you are S-ON. Just a simple "fastboot oem lock" takes care of that. But then you have to immediately flash a proper RUU to get back to a working device.
That thread you linked is unrelated to any of this. That's specifically for people that are already S-OFF.
Click to expand...
Click to collapse
Ok then to unlock Again " fastboot oem unlock " is that it ??
Sorry about the htc 101 Qs.

iamsuperuser said:
Ok then to unlock Again " fastboot oem unlock " is that it ??
Sorry about the htc 101 Qs.
Click to expand...
Click to collapse
No, you unlock following the instructions at HTCDev.

buggerman said:
Hi guys,
So I got this RUU from a "friend". Here it is as promised. Have fun!
Code:
Don't try to flash this if you flashed the Lollipop RUU before this. It won't work.
Even if it does work, you may end up bricking your device.
If you end up bricking your phone, don't blame me.
Code:
0. Charge your phone to at least 60% to be on the safe side
1. Copy the file to an sdcard
2. Rename it to 0PAJIMG.zip
3. Turn off the phone
4. Press and hold valume down + Power till the HBOOT screen shows up
5. Follow the instructions
Don't forget to hit thanks if this helps you..
Download
Click to expand...
Click to collapse
Man,you're a life saver!!! Do you know how long I've waited for this... ?

rdheepak said:
Man,you're a life saver!!! Do you know how long I've waited for this... ?
Click to expand...
Click to collapse
Glad I could help!
Sent from my HTC One_E8 dual sim

Can I flash and return to stock with twrp with this RUU ?
@Captain_Throwback.... I tried lollipop and now running phone with Twrp recovery. so If I put stock recovery and lock device can I execute this RUU. Earlier I was having error saying I am on newer version.

demail2006 said:
@Captain_Throwback.... I tried lollipop and now running phone with Twrp recovery. so If I put stock recovery and lock device can I execute this RUU. Earlier I was having error saying I am on newer version.
Click to expand...
Click to collapse
You can if you're S-OFF. Otherwise, no.
However, if you're unlocked and S-ON, there is a way to downgrade your ROM but leave the Lollipop firmware installed. It requires decrypting the RUU and creating a bootloader-flashable zip of boot, system & recovery from this RUU, which can be flashed via HBOOT directly on the device or through fastboot RUU mode. It doesn't require locking the device either, but it will delete your data and internal storage.

@buggerman i download your RUU rom and installed it i face no error throw installing but the device keep rebooting when working with wizard and after finishing the wizard quickly no network appear on both cards with unknown base-band please see my phone var's
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.12.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.720.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: 35282506xxxxxxx
(bootloader) imei2: 35282506xxxxxxx
(bootloader) meid: A10000xxxxxxxxxxx
(bootloader) product: mec_dwgl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ40000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ca994270
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s

ansi_11111 said:
@buggerman i download your RUU rom and installed it i face no error throw installing but the device keep rebooting when working with wizard and after finishing the wizard quickly no network appear on both cards with unknown base-band please see my phone var's
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.12.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.720.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: 35282506xxxxxxx
(bootloader) imei2: 35282506xxxxxxx
(bootloader) meid: A10000xxxxxxxxxxx
(bootloader) product: mec_dwgl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ40000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ca994270
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Click to expand...
Click to collapse
This is strange. It worked perfectly for one of my friends. I guess the only difference was that he is S-ON and is not on a SuperCID, but I don't think that matters here.

buggerman said:
This is strange. It worked perfectly for one of my friends. I guess the only difference was that he is S-ON and is not on a SuperCID, but I don't think that matters here.
Click to expand...
Click to collapse
How to bring my device back any idea

ansi_11111 said:
How to bring my device back any idea
Click to expand...
Click to collapse
Have you tried the TWRP backup restore?
Sent from my HTC One_E8 dual sim

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