Database Users

[Guide] No Boot - No Recovery - No Download Mode Unbrick Guide

No Boot - No Recovery - No Download Mode Unbrick Guide​
Qualcomm HS-USB QDLoader 9008 or Secure booting error (No Boot - No Recovery - No Download Mode) or "QHSUSB_BULK"​
Hi team, if you have come here I'm sorry you are having this problem! But my friend and I have been to hell and back trying to fix this problem and we wanted to share our method of success for any poor soul who is experiencing the same thing! For our situation the USB was unplugged half way through flashing a KDZ or going back to stock firmware and created the No Boot - No Recovery - No Download Mode problem.
This has only been tested on the D855.. Just so you know.​
First off, here are some links which you may need to have a look at if you have not done so already. Most of the bricking problems have already been extensively talked about by people here on XDA. For the method that works, we had to pull information from everywhere and spent a long time looking for the solution.
How to go back to stock - http://forum.xda-developers.com/showthread.php?t=2785089
Link for TOTs and KDZ's from the above thread - http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
The Main Fix for the problem - http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
The G2 version of the fix (for reference if you still have problems 55+ pages) http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
This is your last stop shop if everything is broken and nothing works, involves hardware fix - http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
The problem we encountered several times with all of the described methods above, is that many do not describe important things. While the main fix thread for the Qualcomm HS-USB QDLoader 9008 mode, which is shown in device manager, is very well written and detailed, the programs which are linked in this thread are questionable and haven't worked for many users with some offering to fix for money. We searched the internet and located a working version of the program which worked without giving a "Device was not found in dload trying to flash programmer" like the one provided on the XDA page. Use the links below for a working version from this thread http://androidforums.com/threads/lg-g2-not-turning-on-help.916865/
My first point is if you are having problems with any of the things, CHANGE YOUR USB CABLE or use the stock cable (I know most experienced users know this). The reason for this problem has something to do with different USB cables being made for different purposes and are of different qualities. Having an error on the USB ports gave us only qhsusb_bulk on windows device manager, without Qualcomm HS-USB QDLoader 9008 as well.
If you are still having problems, check your USB ports. It is really important to make sure this isn't the problem or you will be trying to fix this problem endlessly.
First attach the USB cable to the computer. When you plug your phone in, make sure you attempt to enter download mode by holding the volume up button when you plug the USB into your phone. Even though the phone will not enter "Download Mode" It will allow the phone to be detected by your computer (at which point you can release the buttons, it should then show "Qualcomm HS-USB QDLoader 9008" under ports. If this is not displayed you have a problem with the USB cable or port, or your phone is hard bricked and you need to head to the above guide for the hardware fix. If you have followed so far and are wondering what to do from here, once the "Main Fix" guide ends, head over to the "How to go back to Stock" thread above. Your phone should be showing "firmware upgrade" and you can proceed to flash a new updated KDZ on your device then everything will work and your nightmare should be over!
Working Boarddiag - https://drive.google.com/file/d/0BzkqP9M0LLWQUkEyRkZrVHlEbDg/view
Qualcomm USB Drivers (Essential for the aforementioned "Main Fix" above) - https://drive.google.com/file/d/0BzkqP9M0LLWQblF6Vl9OcUkwUDA/view
LG United Drivers (Phone Drivers) - https://drive.google.com/file/d/0BzkqP9M0LLWQUURDTHlYOW5YRms/view
If this helped you to fix your nightmare don't forget to hit the thanks button!

The "Wroking Boarddiag" asks for PW. aside from that, very good find, thanks

detected as qdloader hs usb 9008
board diag- ap check failed device not in downld mode

For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64

Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?

MrMuli said:
Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?
Click to expand...
Click to collapse
I just fixed my Lg g3 with this method. Not sure if it will work with AndroidNetUSB
Would like to help for any difficulties. (e.g. Not able to find TOT file) etc.
Thanks to @Orcam & @kryptonite

This did not work. Here's what I tried:
1. Without battery
2. Changed drivers as @shawe_ewahs says
3. With battery
4. Admin and non-admin
5. Changing COM ports
But, every time, I get:
"Device was not found in dload trying flash programmer
TEST Aborted!!"
My LG G3 D851 is in Qualcomm HS_USB QDLoader 9008 (COM 41) so I know it is in the correct mode! Agh, it is very frustrating. Any help is appreciated. Thanks.

Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*

furiify said:
Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*
Click to expand...
Click to collapse
No problem. Hope it didn't take you as long as it took us to find all the right stuff

I'm having this problem, but when I plug in without a battery all that shows up in device manager is "Unknown USB Device (Device Descriptor Request Failed)". I tried to do the hardware fix and was able to force the device to reboot by touching the pins. But all that happens is it disconnects and reconnects from USB without being detected properly.
I should note that when I turn the phone on right now, it stays stuck in the initial LG G3 splash screen. When I plug in without a battery, it shows an empty battery icon with a wire and a triangle question mark.
Any idea what I'm doing wrong? I think if I can just figure out how to get my machine to detect my phone as the qdloader hs usb 9008 I can figure out the rest.

The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.

Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.

Dr1t3r said:
The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.
Click to expand...
Click to collapse
phaim said:
Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.
Click to expand...
Click to collapse
Sounds like it may be a problem with windows from what you two have said. Perhaps compatibility mode is the way to go. They did release a pretty major windows 10 update since I posted this guide.

Bricked phone but can still get into EDL mode

Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.

Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit

daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason

Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?

daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible

i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!

A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted

The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.

i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152

Broken EDL mode

Hello everyone. I'm stuck here on strange bug: when device rebooted to EDL it gives "unknown usb device (device descriptor request failed)". Tryed on desktop Win10, worked before but not now. Connected to laptop Win7, never attached device before, gave me same error. So I assume I broked edl some way? Is it possible to recover?

EDIT: Make sure you install them, especially the Qualcomm driver while Driver Signature Mode is disabled.
If you haven't already, try installing the Qualcomm USB Drivers. You can follow the simple guide here:
https://bit.ly/2EdPjlm
Afterward, reboot and try again.

KwesiJnr said:
EDIT: Make sure you install them, especially the Qualcomm driver while Driver Signature Mode is disabled.
If you haven't already, try installing the Qualcomm USB Drivers. You can follow the simple guide here:
https://bit.ly/2EdPjlm
Afterward, reboot and try again.
Click to expand...
Click to collapse
QC drivers already installed, and EDL mode worked fine week ago - when I flashed TWRP.

Solved. There was two problems:
1) Zadig WinUSB driver, which prevents phone from normal EDL work
2) When you reboot phone in EDL mode and unplug it, you get 43 error 100% no matter what. All manipulations with device and it's drivers must be made right after reboot to EDL without unplugging

@KwesiJnr: There is no need to disable Driver Signature Enforcement in Windows. I have flashed with MiFlash quite a bit on Windows 10, never had to disable it.
@SionGrey: Just follow the instructions in the first couple of paragraphs of https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514. You don't need to flash the packages linked there. The version of MiFlash that @jcadduono provides is sufficient for flashing Marshmallow/Nougat EDL packages. In you are flashing an Oreo EDL then I think you will need the version of MiFlash from December 2016 (Google it), I never had any luck with @jcadduono's version when flashing Oreo. The installer is in another language but the program runs in English. Zadig's WinUSB drivers will definitely interfere with MiFlash, uninstall them from Device Management before installing the Qualcomm drivers. I never got a failure at 43%. You can restart EDL mode on the phone without unplugging, just hold Volume Up + Volume Down + Power (in that order) until you see a red light blink in the upper left corner of the phone. Then just refresh in MiFlash.

@AnonVendetta
You got wrong idea. There was no any 43% flashing error. I posted above that I solved my problem. It was "unknown usb device (device descriptor request failed)" in device manager, and it happened because phone MUST be plugged-in during reboot to EDL mode. No un-plugging and re-plugging when phone is already in EDL

SionGrey said:
@AnonVendetta
You got wrong idea. There was no any 43% flashing error. I posted above that I solved my problem. It was "unknown usb device (device descriptor request failed)" in device manager, and it happened because phone MUST be plugged-in during reboot to EDL mode. No un-plugging and re-plugging when phone is already in EDL
Click to expand...
Click to collapse
Thanks man, you helped me a lot - appreciate it. I didn't plug in the phone to my computer at the right time. I got it now.

I noticed someone had quoted me recently. But I can't be of any help. It's been over a year since my Axon 7 was stolen. I've moved on to a better device. The A7 was still a pretty good phone though.

Axon 7 die after update.

Hi everyone.
I tried to update my axon to oreo but I saw an error and process was aborted.
Now I can't turn on my phone. Vibration, red lamp blink and that's all.
Is there any chance to save my phone ?
Please help.

@rym199: Judging by your topic's title, I thought you had a hardware failure. If you can get into EDL mode, then you can reflash a stock ROM of your choice. If MiFlash/Axon 7 EDL Tool can't detect the phone, then you are probably in DFU mode, in which case you will need to use the DFU MultiDL Tool to switch from DFU to EDL. Then you can flash it and start clean.

rym199 said:
Hi everyone.
I tried to update my axon to oreo but I saw an error and process was aborted.
Now I can't turn on my phone. Vibration, red lamp blink and that's all.
Is there any chance to save my phone ?
Please help.
Click to expand...
Click to collapse
Doubt you'll be able to do much with the above info
With the phone off, hold Vol UP and Vol DOWN, then insert the USB cable (it has to be connected to the PC on the other end already). After that, go to Device Manager on your PC and check under the Ports (COM & LPT) tab. If it says Qualcomm HS-USB QDLoader 9008, just use EDL Tool (by djkuz, check on the ROMs, kernels, development section) with a file that corresponds to the model of your phone (by the way, which is the phone model as stated in the back?).
If it says DFU then you'll have to follow raystef's guide on how to use the new DFU tool, then use EDL tool

Choose an username... said:
Doubt you'll be able to do much with the above info
With the phone off, hold Vol UP and Vol DOWN, then insert the USB cable (it has to be connected to the PC on the other end already). After that, go to Device Manager on your PC and check under the Ports (COM & LPT) tab. If it says Qualcomm HS-USB QDLoader 9008, just use EDL Tool (by djkuz, check on the ROMs, kernels, development section) with a file that corresponds to the model of your phone (by the way, which is the phone model as stated in the back?).
If it says DFU then you'll have to follow raystef's guide on how to use the new DFU tool, then use EDL tool
Click to expand...
Click to collapse
When I connect to PC there is a Qualcomm like you wrote. I try tomorrow, Thank you so much

@Choose an username...: I was intentionally vague because I wanted the OP to do his own research. Give them just enough info to get started, then it's up to them to do the rest. Searching Google isn't hard. And I was a bit pressed for time.

Choose an username... said:
Doubt you'll be able to do much with the above info
With the phone off, hold Vol UP and Vol DOWN, then insert the USB cable (it has to be connected to the PC on the other end already). After that, go to Device Manager on your PC and check under the Ports (COM & LPT) tab. If it says Qualcomm HS-USB QDLoader 9008, just use EDL Tool (by djkuz, check on the ROMs, kernels, development section) with a file that corresponds to the model of your phone (by the way, which is the phone model as stated in the back?).
If it says DFU then you'll have to follow raystef's guide on how to use the new DFU tool, then use EDL tool
Click to expand...
Click to collapse
It works ! EDL mode with 8.0 custom Oreo = my phone alive Thank you guy's !

Brick Saved!! OnePlus 8 Pro Oxygen OS 12 to Android 11 downgrade brick saved. Methods I used and pitfalls.

Background:​
OnePlus 8 Pro IN2020
Original OS version is OxygenOS 12 Android 12
How my phone turned into brick:​
Try flashboot unsupported TWRP and other third party recoveries.
After a few tries, eventually causing my phone turning into a brick
What my error looks like:​
Not able to boot into system
Showing "the current image(boot/recovery) have been destroyed"
Can access fastboot and detect by system
​Method:​
Follow the steps in How to UNBRICK OnePlus 8 or 8 Pro! by Max Lee (Thank you my man, Max, for this video)
​Pitfalls in 2022 (IMPORTANT before UNBRICK!):​A USB 2.0 and Third-party USB cable are highly recommended​I was unable to boot into Quadcomm EDL mode while using the stock cable and USB 3.0 connector. Pressing the correct Volumn Up & Volumn Down and Power Button will boot the phone to fastboot in no time.
I successfully got into the EDL mode and finished flashing the phone using my iPad Pro Type-C charging cable which is an USB 2.0 one.
Use a newer version of the Qualcomm driver if you find the device not correctly detected​Use Qualcomm HS-USB QDLoader 9008 driver.
A new Quadcomm driver will help you flash your device correctly the first time!!!
Windows 11 won't let you install unsigned driver by default, but there's a way round​
Press Shift key while click Reboot in start menu to enter Advanced Options
Click Trouble shoot in Advanced Options
Click Advanced options, click Startup Settings then click Restart
After restart press 7 when required
If your computer won't restart, just unplug your phone temporarily
after this your device will detect by your computer correctly.
Pressing buttons requires special timing and preconditions and a few more tries​
To fully power off your phone, press Volume up and Power button for 10 seconds. Release immediately after the screen turns black.
Your phone is in the state of powered off even your screen displaying error message or charging animation, just make sure it's not in fastboot, recovery or booting animations.
Connect your phone to your computer before press Volume up and down and Power Button all at the same time to enter EDL mode.
Prepare yourself with Device Manager and MSM tool open and configured correctly before your phone enter EDL mode. There's a about 10 second window for you to start flashing.
Fail amid your MSM flash process:​Don't panic if you see error message saying you didn't finish flashing​
You can flash it anytime just make sure checking all the things above and enter EDL mode
Check these things：​
Check your Windows can install the unsigned driver correctly
Check Device Manger in Control Panel if your device is correctly detected as a COM device as Qualcomm HS-USB QDLoader 9008 or something like this
Use administrator privilege to open the MSM software
Check your cable connection is stable or not.
Finally, thanks Dr.E (Max Lee) for your help. Without your video instructions, I won't revive my phone. It spares my pain to ask my dad for money for a new phone I don't actually need.
Hope everyone could find some helpful information in this post and flash your phone like a champ.

A even better way to enter EDL mode is power off and unplug your device, and after hold volume up and down at the same time, plug in the USB 2.0 cable to the computer. It works every time!!

i cant join rdl mode always restarting fastboot mode