Prerequisites
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.
- the appropriate package for the device
- a supported bricked device
- a usb cable
- fastboot
- distro utils: md5sum, strings, tail, grep, unzip ( all included in most linux distros)
- some basic linux experience
- root access on a linux machine
- patience
Instructions
- Boot the linux box and download the appropriate package for the device.
- Remove the sim card from the phone. Do not connect yet
- Extract the package in your working directory
- Open up a terminal and cd to that directory
- Run revive.sh as root and connect the device
Code:sudo ./revive.sh
The procedure is automated. At the end of the unbrick process, you will need to charge the device fully and then flash one of the full firmwares bundled, as pointed from the script. This is crucial to ensure device stability.
hello, please help, I can’t find the files I need to restore my phone (((
I still have the files from back when I first tried the unbrick tool in 2017 (it didn’t work), and that Android File Host link also works. Tried it again today on a different M7, also didn’t work.Unlikely these files exist anywhere at this time.
This thread is from 2014, that's more than half a decade!
Sent from my PH-1 using Thebear Blue XDA Labs
hello. i need that tool, kinda late ik. is it somewhere still?OP status: [WIP]
This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA, or manually, you most likely have a device stuck in QHSUSB_DLOAD. This tool is for you
Currently supported devices: m7ul.
Hey, pretty sure this is it, just uploaded it to here: https://drive.google.com/file/d/1dth0ZXazJoQXjuFWm8wow14_d8y15Uud/view?usp=sharing
sudo ./revive.sh
You can forget about any kind of support on mac. logging and usb events are different. Use a live cd or somethingGot my HTC bricked just like that in middle of a browsing session with 40% battery, this happened 2 days bak.
I have my all things set. Including the fastboot and root permission.
When i run revive.sh i am not getting the bricked device detected.
I am on Mac. Hopefully it satisfy the condition required here of a linux distro. As of now i have this m/c only no ubuntu..
I checked via tail -f /var/log/system.log (klog is diff in mac) , the following is there :
Jun 5 21:05:08 anirudhsmacbook kernel[0]: USBF: 28336.614 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
Jun 5 21:05:09 anirudhsmacbook kernel[0]: USBF: 28336.675 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
Jun 5 21:05:20 anirudhsmacbook kernel[0]: USBF: 28348.651 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
Jun 5 21:05:20 anirudhsmacbook kernel[0]: USBF: 28348.660 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
Jun 5 21:05:21 anirudhsmacbook kernel[0]: USBF: 28348.871 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
Jun 5 21:05:21 anirudhsmacbook kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
Jun 5 21:05:22 anirudhsmacbook kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
Jun 5 21:05:22 anirudhsmacbook hidd[48]: MultitouchHID: device bootloaded
Jun 5 21:05:25 anirudhsmacbook kernel[0]: USBF: 28353. 35 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
Jun 5 21:05:25 anirudhsmacbook kernel[0]: USBF: 28353. 42 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
Jun 5 21:05:25 anirudhsmacbook kernel[0]: USBF: 28353.106 AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
I guess this is not searching for Qualcomm MMC storage as mentioned in the revive shell script.
Does that mean its not in correct mode ? or does that mean mac USB driver detection is diff.
Any feedback shall be appreciated.
try with this version of emmc_recover and let me know if you still get illegal instruction