[HTC Vivid, Raider, Velocity] dexter93:
Prerequisites

a linux box/live cd with automount disabled and without unity

the appropriate package for the device

the latest RUU for your device

a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device

a usb cable

some basic linux experience

patience

DISCLAIMER:

We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.

Instructions

​

NEW:

Detailed video on the process. Its displaying the process on a Sensation, but its pretty much the same thing. Thanks to kgs1992 :)

[YOUTUBE]db5f3If-2Jw[/YOUTUBE]

Boot the linux box and download the appropriate package for the device.

Extract the package in the home directory

Open up a terminal

Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery

Detect the device using the script provided. Type this in the terminal

./brickdetect.sh

You should get something like sdX. We are interested on that "X"

Unplug the usb cable from the device

Backup the hboot currently in the phone by using this command. Plug the device in ONLY when asked to

sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12

Replace the "X" with the letter the script gave you

Follow the on-screen instructions from emmc_recover

Hexdump the b_hboot to check the hboot version

hexdump -C b_hboot.img |less

The output should be like this:

00000000 05 00 00 00 03 00 00 00 00 00 00 00 00 00 10 40 |...............@|
00000010 d8 fc 0f 00 d8 fb 0f 00 d8 fb 1f 40 00 01 00 00 |...........@....|
00000020 d8 fc 1f 40 00 00 00 00 12 00 00 ea 31 2e 38 33 |...@........1.83|
00000030 2e 30 30 31 31 00 00 00 38 32 36 30 20 53 50 4c |.0011...8260 SPL|
00000040 00 00 00 00 00 f0 20 e3 53 48 49 50 00 00 00 00 |...... .SHIP....|
00000050 00 f0 20 e3 00 f0 20 e3 48 42 4f 4f 54 2d 38 32 |.. ... .HBOOT-82|
00000060 36 30 00 00 00 f0 20 e3 39 34 61 63 34 34 62 66 |60.... .94ac44bf|

This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.83

Side note on the hboots for the Holiday

Hboot 1.85.2525 is the ICS Juopunutbear hboot based on 1.85.0025. In this package it comes as "hol1.85ics" - use that in the version name instead of "1.85"

Hboot 1.85.2121 is the GB Juopunutbear hboot based on 1.85.0021. In this package it comes as "hol1.85gb" - use that in the version name instead of "1.85"
​

If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again

Unplug the device

Check again it is the right version, because if you do a mistake here, you won't be able to go back

You can only flash the same version as the one in the device.

!!!!!DO NOT ATTEMPT TO FLASH ANOTHER VERSION OR DOWNGRADE!!!IT HAS BEEN PROVEN FATAL!!!!

Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.83, 1.84, 1.85gb, 1.85ics) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to

sudo ./emmc_recover --flash holV.VV.nb0 --device /dev/sdX12 --backupafter hboot_f.nb0

Follow the on-screen instructions from emmc_recover. A successful flash should have this output:

511+1 records in
511+1 records out
1047808 bytes(1.0 MB) copied

Unplug the device, put SIM, microSD card and battery in and power on

Congratulations, the device is unbricked.

FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.

Notes on the procedure:

​

If the device doesn't power on, get a copy of the hboot_f.nb0 and b_hboot.img (should be located in the home directory) and contact us

The connection between the device and the pc will be unstable, and will time out. You have to be quick when doing the above, specially while flashing. If the connection times out don't panic, just unplug and replug the device

Unity and automount are known to cause issues in ubuntu 11.04 and 11.10. We recommend getting rid of both, or use a 12.04, or 10.04/.10 liveCD

USB3 ports do not work properly. Please plug the device in a USB2 port

How to disable automount on ubuntu

gsettings set org.gnome.desktop.media-handling automount false

Downloads

For Vivid, Raider, Velocity ( Holiday):

32bit version MD5: 9172d77fb8a335675bf5ff3d64b9efc5

64bit version MD5: 3958de3729b7add72c0e3123d89745f7

Don't have a linux distro installed on your pc? We highly recommend this livecd
​