Thank dexter93 hard work, the S-OFF, when version 2.3.7, very good for the S-OFF, but I do not have flashing jb_hboot.zip Due to negligence, forget SD PH319.zip boot the update, the USB connected to the computer, prompt QHSUSB_Drivers, install the driver, connected to the computer, the screen lights, but a black screen, no idea! If you need pictures, I will upload. Once again express our gratitude!Please excuse my English!
[UNBRICK] HTC Unbricking Project
- Thread starter dexter93
- Start date
-
- Tags
- development
Hi I have a problem, my Vivid became the "bricks". anything that does not respond when connected to usb black screen in the boot does not go on the fifth paragraph of recovery or what is happening. help. yet it is not a riff box to restore an error, you may backup fullflash made any jtag box for htc vivid? s-on, Root is like, but a 5 point problem. sorry for my english
Last edited:
Hello,
Anybody got success in unbricking vivid? One that bricked while OTA update to ICS.
Thanks...
Best Regards
Anybody got success in unbricking vivid? One that bricked while OTA update to ICS.
Thanks...
Best Regards
Not sure if my phone is truly bricked or not, but I can't seem to get into recovery. Long story short, my phone died overnight one day (wasn't rooting, upgrading ROM's or flashing anything). I'm now able to get it into Hboot, but not into recovery and every time I try to start it up, it just hangs at the HTC logo screen. I've tried flashing boot.img and recovery.img thru fastboot, even tried using every PH39IMG.zip our there, but I can't seem to get anything to work.
So bricked or something completely different?
I'm using a Rogers Raider with S-on and it was rooted. Any help would be appreciated. Thanks,
So bricked or something completely different?
I'm using a Rogers Raider with S-on and it was rooted. Any help would be appreciated. Thanks,
try to lock the bootloader and flash a ruu. that should restore it in working condition
Hey Dave, did you manage to get this problem fixed? I have a friend with this same problem.
Sorry got a one X...... And no..... Still have it.... Still bricked..... Oh well.... Live and learn.
Sent from my HTC One X using xda premium
Sent from my HTC One X using xda premium
I think my phone is dead. I dont know if this will work for me. And I dont think I have the capabilities to do this. Im not at all familiar with linux. I have a windows 7 laptop(can i run this with that?) Here's what happened to me :http://xdaforums.com/showpost.php?p=28986140&postcount=13 I am (or was) s-on at the time of brick so if theres any hope please let me know. Im also willing to pay someone to fix this for me. I just don't want to deal with it at this point. I have finally given up trying to be a nerd wannabe 
So if your interested pm me! My phones already dead so i got nothing to loose.
So if your interested pm me! My phones already dead so i got nothing to loose.root@qc26-deepin:/home/qc26/Unbrick_Holiday_32bit# ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
tailf /var/log/kern.log
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.920343] qcserial 1-2:1.0: Qualcomm USB modem converter detected
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.926996] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.950635] usb 1-2: USB disconnect, device number 7
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.959238] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.960331] qcserial 1-2:1.0: device disconnected
Aug 8 16:18:34 qc26-deepin kernel: [ 9290.424789] psmouse serio1: resync failed, issuing reconnect request
Aug 8 16:18:34 qc26-deepin kernel: [ 9290.448636] psmouse serio1: hgpk: ID: 10 00 64
Aug 8 16:18:37 qc26-deepin kernel: [ 9292.918719] usb 1-2: new high-speed USB device number 8 using ehci_hcd
Aug 8 16:18:37 qc26-deepin kernel: [ 9293.082023] qcserial 1-2:1.0: Qualcomm USB modem converter detected
Aug 8 16:18:37 qc26-deepin kernel: [ 9293.082248] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
I am waiting for any suggestions！thanks
Searching for bricked device...
Device can't be detected. Check connections
tailf /var/log/kern.log
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.920343] qcserial 1-2:1.0: Qualcomm USB modem converter detected
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.926996] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.950635] usb 1-2: USB disconnect, device number 7
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.959238] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Aug 8 16:18:34 qc26-deepin kernel: [ 9289.960331] qcserial 1-2:1.0: device disconnected
Aug 8 16:18:34 qc26-deepin kernel: [ 9290.424789] psmouse serio1: resync failed, issuing reconnect request
Aug 8 16:18:34 qc26-deepin kernel: [ 9290.448636] psmouse serio1: hgpk: ID: 10 00 64
Aug 8 16:18:37 qc26-deepin kernel: [ 9292.918719] usb 1-2: new high-speed USB device number 8 using ehci_hcd
Aug 8 16:18:37 qc26-deepin kernel: [ 9293.082023] qcserial 1-2:1.0: Qualcomm USB modem converter detected
Aug 8 16:18:37 qc26-deepin kernel: [ 9293.082248] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
I am waiting for any suggestions！thanks
I have had success with several vivid units I have had brought to me. 2 of the people said that it got stuck on 34% and stayed there then they unplugged it. I just went and pulled the battery held the volume down key and just tapped the power button went into hboot clicked the bootloader and saw bootloader USB and then ran the ruu file.
Sent from my HTC PH39100 using xda app-developers app
If you have followed all the steps carefully and fulfilled the prequisites, then the detect script should tell you if its repairable using our methods. Else, you'd need to JTAG it
Sent from my HTC Sensation using xda app-developers app
Hello, guys, need a bit of help on this. My Vivid got bricked while downgrading to GB, it's S-ON and locked bootloader. It charges the battery but stays invisible under Linux/Win, neither does the script detect it, get a device can't be detected error message. Is there anything else I can do? I'm following tutorial step-by-step. Or jtag is my last resort? Any help is appreciated, thanks!
If it charges, you most probably have bootloader access. check that, and try to fflash a ruu
Thanks for fast reply. My bad, forgot to mention that the phone charges battery without any indication, I'm taking measures by voltmeter. When the battery is fully charged, it discharges extremely fast, in an hour or so. How do you think, is there anything else I can try (like this method) or anything else?
I have a little progress on the phone, maybe there can be some advice to my situation. When I do the wire trick, device is recognized in Win7 as QHSUSB_DLOAD, in Linux I get:
Sep 5 22:19:15 angel-desktop kernel: [14963.072056] usb 1-7: new high speed USB device using ehci_hcd and address 21
Sep 5 22:19:15 angel-desktop kernel: [14963.205011] usb 1-7: configuration #1 chosen from 1 choice
and that's it, it still does not get detected by the script. Is there anything that could be done?
Sep 5 22:19:15 angel-desktop kernel: [14963.072056] usb 1-7: new high speed USB device using ehci_hcd and address 21
Sep 5 22:19:15 angel-desktop kernel: [14963.205011] usb 1-7: configuration #1 chosen from 1 choice
and that's it, it still does not get detected by the script. Is there anything that could be done?
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
15We are proud to announce that the Vivid, Raider and Velocity is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
The "core" of the unbricking project dev team:
MOVZX
RussianBear
Fuses
Dexter93
Testing stuff and irc support:
globatron
Deceptivechaos
dburgd84
Snake_skw
Other stuff:
dmcb123
xIndirect
Hawke84
Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.7Prerequisites
- 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
- 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
You should get something like sdX. We are interested on that "X"Code:./brickdetect.sh - 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
Replace the "X" with the letter the script gave youCode:sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12 - Follow the on-screen instructions from emmc_recover
- Hexdump the b_hboot to check the hboot version
The output should be like this:Code:hexdump -C b_hboot.img |less
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.83Code: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|
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
Code: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:
Code: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
Code:
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
4
This is a quite unexpected behavior and usually it is caused by dodgy hardware,or other unknown factors. You can try this method, but I am pretty sure it won't work for you
stuck in ruu mode vivid, when plugged in it's black htc screen with 4 triangles, check pics
not sure how it got there, but i'm willing to guess that it had something to do with ics upgrade/attempt to s-off.
bootloader is locked, ics ruu stops at 34%
when flashing rom.zip from ruu through fastboot it stops here
(bootloader) start image[tz] unzipping for pre-update...
(bootloader) start image[tz] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 116.140s
Fastboot getvar all returns this
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.85.0025
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: 0360
(bootloader) version-main: 3.26.502.54
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) product: holiday
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH3910000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: b215ac78
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.527s
looks like no radio, lol interesting
hopefully this can help, if not i will have to send to HTC but they had my incredible S for a month now with no solution yet lol so i dont wana wait another month for this guy.
ready to give this a shot
You are stuck on the pre-update. When you see thisyou simply have to flash the rom.zip againCode:FAILED (remote: 90 hboot pre-update! please flush image again immediately)2
I have had success with several vivid units I have had brought to me. 2 of the people said that it got stuck on 34% and stayed there then they unplugged it. I just went and pulled the battery held the volume down key and just tapped the power button went into hboot clicked the bootloader and saw bootloader USB and then ran the ruu file.
Sent from my HTC PH39100 using xda app-developers app1
