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

Return to stock has gone a bit Pete Tong - help!

I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.

crank_girl said:
I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.
Click to expand...
Click to collapse
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
p.s. can you actually flash something with adb??

Lots of people seem to confuse adb with fastboot. Is that what you want to use?

Thanks both for responding. I think I've gotten myself a bit confused over what is supposed to be working at any given time.
I can get the phone into EDL mode and fastboot. Fastboot devices finds my phone. MiFlash doesn't find my phone despite having the QHSUSB driver installed.
What's the easiest way to return my phone to stock? I have MiFlash and Axon7toolkit installed.
Cheers!

Choose an username... said:
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
Click to expand...
Click to collapse
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
Click to expand...
Click to collapse
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!

You have the wrong drivers.

crank_girl said:
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!
Click to expand...
Click to collapse
I tried to post yesterday and for some reason the XDA app didn't post the answer... Basically this:
-Forget ADB and that program that you're using to see the devices. EDL uses COM protocol, has nothing to do with adb at all.
-Go to Device manager and find where QUSB_BULK is. If it is in Unknown devices, either right click on it and try to install the driver automatically, or search for "Qualcomm HS-USB QDLoader 9008 drivers", download, install and try to install it on QUSB_BULK. If it is in an "USB devices" tab or on Ports "COM & LPT" simply right click, Uninstall device, Delete driver software for this device

I've done that several times over but miflash still isn't detecting it.

crank_girl said:
I've done that several times over but miflash still isn't detecting it.
Click to expand...
Click to collapse
all right. Try EDL Tool by djkuz. I don't know if the same packages work but just download another edl package

It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.

crank_girl said:
It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.
Click to expand...
Click to collapse
How come? The right driver literally appears on the last photo...

Choose an username... said:
How come? The right driver literally appears on the last photo...
Click to expand...
Click to collapse
I know, right? It's a mystery. Never had this happen before.

crank_girl said:
I know, right? It's a mystery. Never had this happen before.
Click to expand...
Click to collapse
If it doesn't work try MiFlash on another PC, it sometimes happens that it won't detect it by any means

[SOLVED] I bricked A2017G

Hello, i have ZTE Axon 7 Gold model and i bought silver one which i bricked. I flashed Unlock bootloader for Nougat instead of Marshmallow in ZTE Axon 7 toolkit. I can't boot to EDL mode, when i try to hold all buttons for 5 seconds, it shortly powers off and it shows red dot again. I have only QUSB_BULK when connected in device manager and i can't flash anything with it. Please help.
I can't access EDL, ADB, fastboot and DFU mode. No boot screen, nothing, it just stays black. I will try to discharge it.

Hello guys again, i solved my problem. It was a driver issue. I installed every driver, including the driver raysteff66 provided and it took time while cleaning old drivers. It didn't worked. What worked for me is using driver navigator (you can use similar driver installers). I don't use these program for daily use (they're not recommended for it), but when drivers simply refuses to install, they come to the rescue. It found that i have missing ZTE DFU driver. I downloaded it and program force installed it. After that i rebooted the system and Voila! it detects my device as DFU. After that i used DFU MultiDL tool and it switched it to Qualcomm 9008 EDL mode. I flashed EDL Rom and celebrated my success.
Read this if you have QUSB_BULK as your only driver displayed in device manager.

Help! 6T is hard bricked. Device does not match image.

Problem: The OnePlus 6T cannot boot into fastboot mode or ADB mode. When regularly booting, I get a "device is corrupt, can't be trusted" message. I achieved this by rooting my phone through suggested methods, then uninstalling Magisk, and locking my bootloader through the all in one tool. The all in one tool can no longer detect the device under any circumstance.
Attempted Solutions: I downloaded the MSM download tool and it says "Connected." The device shows as "Quallcomm HS-USB QDLoader 9005 (Com 5)" I also got it working for Com 6. The driver and connection appears to be fully functioning. USB debugging was enabled before I bricked my phone. When I start the download, I get stuck in the param preload phase, with the error message "DEVICE DOES NOT MATCH IMAGE." The "Verify" button works perfectly and says it's working.
I have downloaded every version of the MSMDownloadTool I could possibly find. I assume I have the most recent update of the OS -- It updated quite recently. I tried every single version I could find, including the most recent one (fajita_41_J.50_210121) and got this error every time. I know it's running Android 10, unless Android 11 for 6T is a thing.
I ran the program as an administrator.
I tried multiple USB ports, all with the driver properly installed.
I reinstalled drivers (signature patching is disabled and I don't assume drivers are the issue)
I restarted both the phone and computer multiple times.
I disconnected and reconnected the USB over and over, holding both volume buttons.
Why would I be getting a "device does not match image" and how can I bypass it to force the upload anyway?
I am using an INTERNATIONAL unlocked version. NOT a T-Mobile version. Since I can't access fastboot mode, I was not able to adjust certain settings. USB debugging was enabled, though, could this be the issue?

Hi,
Wrong Section please post in the correct thread to receive optimal answers.

arjunbalan1994 said:
Hi,
Wrong Section please post in the correct thread to receive optimal answers.
Click to expand...
Click to collapse
So what thread should this be posted in? Because I have the same problem/question and can't seem to find an answer. . .