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 G2, more information is in the post

Hello guys,
I need help to unbrick my Lg G2 d802 32GB. First of all i rooted the phone and then flashed TWRP on it, because i wanted to install Cyanogenmod. The install instructions told me to go into recovery mode. As i wanted to do that, my phone needed a restart and it didnt start anymore.
I cant go into recovery mode or download mode, nor can i do anything with it. I have already tried many solutions, but none of them worked.
It would be really nice if you can give me some answers on what i could have done wrong and help me get my phone back to normal. It doesnt matter if it gets fully wiped, because i backupped everything before i wanted to install cm.
Here is a list of the links i have already tried:
http://forum.xda-developers.com/showthread.php?t=2582142 The problem with this is, that the phone connects and disconnects over and over again and you dont have time to switch out the broken things. Im using Ubuntu 15.10 if that helps. Is there any way to make Ubuntus drivers act like Windows drivers, because on Windows its connected all the time and doesnt disconnect?
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 The problem with this is, that the phone doesnt get shown under the name "Qualcomm HS-USB QDLoader 9008" mode but under the name "Qualcomm hs-usb diagnostics 9006" . How can i get it into this mode?
The other methods are requiring recovery or download mode in which i cant go.
Thanks in advance for you help!!

Gundeltraud said:
Hello guys,
I need help to unbrick my Lg G2 d802 32GB. First of all i rooted the phone and then flashed TWRP on it, because i wanted to install Cyanogenmod. The install instructions told me to go into recovery mode. As i wanted to do that, my phone needed a restart and it didnt start anymore.
I cant go into recovery mode or download mode, nor can i do anything with it. I have already tried many solutions, but none of them worked.
It would be really nice if you can give me some answers on what i could have done wrong and help me get my phone back to normal. It doesnt matter if it gets fully wiped, because i backupped everything before i wanted to install cm.
Here is a list of the links i have already tried:
http://forum.xda-developers.com/showthread.php?t=2582142 The problem with this is, that the phone connects and disconnects over and over again and you dont have time to switch out the broken things. Im using Ubuntu 15.10 if that helps. Is there any way to make Ubuntus drivers act like Windows drivers, because on Windows its connected all the time and doesnt disconnect?
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 The problem with this is, that the phone doesnt get shown under the name "Qualcomm HS-USB QDLoader 9008" mode but under the name "Qualcomm hs-usb diagnostics 9006" . How can i get it into this mode?
The other methods are requiring recovery or download mode in which i cant go.
Thanks in advance for you help!!
Click to expand...
Click to collapse
some went bad when you flashed your custom recovery..
you can try 2 things srk tools and do the nuke download..
maybe you need to short ciscuit your motheboard to get download mode.. seach for it.

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

A2017U completely stock on b32, miflash won't read it for downgrade

As the title says, I can't get miflash to see my device so I can downgrade and unlock. I've been through every guide most likely and have tried every possible combination I can think of. So my question is, is there anyway I can root and unlock on b32 without edl?
The device works fine, adb, Qualcomm drivers all work as they are supposed to and again, many different approaches to try and get it to work but have had no success getting miflash to see my device in edl.
If it makes a difference I downgraded to b19
I'm still a rookie but far from a newb, is there anyway around me having to hunt down another computer that might make miflash see my device?
Desperate

There's no way man cause u need to unlock your bootloader and bootloader is disabled in b32, so u'll need edl mode in order to flash b19 booltloader to root, if your pc does not recognize your device you might want to try in a different pc or maybe change the usb cable you using that might help

Thanks man. The crazy thing is one of the tool kits can see the device in edl as it checks for the just before it prompts miflash to open but then miflash doesn't see it.

Does your phone show in Device Manager when you put it in EDL mode? If so, what does it say? QUSB_BULK or Qualcomm HS-USB QLoader 9008 (COMn)

I do recall it saying Qualcomm hs-usb qloader once or twice before, one of the times I uninstalled and reinstalled everything. Other than that I recall it saying qusb_bulk. Is that what's killing it for me?
BTW I finally got it to downgrade to b19 through SD card upgrade in the stock recovery but still no luck with miflash recognizing it.

Also I just tried to reboot to bootloader from stock recovery and it still boots me into the ROM :/

I had the "QUSB_BULK" message instead of the Qualcomm Qloader thing a while back.
Took a while to realise I didn't have .NET Framework 3.5 installed. The moment I installed it, MiFlash detected and everything was fine. I would also advice you to make those Qualcomm driver and MiFlash installations in Driver-Enforcing mode.
Also, the bootloader doesn't work as they disabled it on B19 upwards. You can fix it with the FASTBOOT_UNLOCK zip from this thread: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514

Solved!!! I had to install miflash on the D; hard drive not the C; for some odd reason.. Hit refresh and it immediately recognized the device. Happy days people. Happy days

Lol, that's a new one. Glad you got it solved.

Lol me too, literally days... I was beginning to question myself.

Possible Bricked device please help

I followed all guidelines including fastboot flashing unlock_critical. Everything was flashing fine & it got to a point where it rebooted & now all i have is a black screen it will not turn on or go to fastboot at all screen is completely black. If I am hooked up to my pc and try the combo buttons for fastboot my computer makes a sound as it would with any device attached. Please tell me i didnt totally brick my phone. I would appreciate any help!
The phone shows up in the device manager as qualcom hs-usb qdloader 9008 (com 8). Theres gotta be something i can do.

jessejamesd2i said:
I followed all guidelines including fastboot flashing unlock_critical. Everything was flashing fine & it got to a point where it rebooted & now all i have is a black screen it will not turn on or go to fastboot at all screen is completely black. If I am hooked up to my pc and try the combo buttons for fastboot my computer makes a sound as it would with any device attached. Please tell me i didnt totally brick my phone. I would appreciate any help!
The phone shows up in the device manager as qualcom hs-usb qdloader 9008 (com 8). Theres gotta be something i can do.
Click to expand...
Click to collapse
Try my guide https://forum.xda-developers.com/raz...ivers-t4086479
To get drivers working.
this happend to me also to get to boot loader when drivers are installed use "fastboot reboot bootloader"
And maybe have to spam it ...( After typing it once press arrow up and enter ) afew times to get in to bootloader. Hope this will help.
Your phone isn't bricked you can still sort it.

Try this guide it says unrooting how ever it's the same process if your phone is bricked https://forum.xda-developers.com/razer-phone-2/how-to/razer-phone-2-unroot-step-step-t3896529