Database Users

Qualcomm drivers for the qhsusb dload

Can someone please post a link to download qhsusb dload drivers and tell how to install theme please.

Is your phone working? Because if you're plugging your phone to the computer and getting this error and your device is not working... it means your eMMC is fried.
Sent from my Nexus 10 using Tapatalk

My phone is dead 15 days ago!!! it is stuck on frozen lg logo splash screen, no recovery mode, only hard reset mode, when tempting download mode, it goes only to the first screen where it's writtend download mode with blue dots, another thing when on lg logo splash screen, my phone shows in device manager under modem and port com, i wanted theses drivers to try linux methode!!! any help would be much appreciated. thank you

Do you know how to use adb and fastboot?
<<Turc şi Mândru>>

yeah, the problem is, adb can't read my phone while it shows normally in device manager

devdassi said:
yeah, the problem is, adb can't read my phone while it shows normally in device manager
Click to expand...
Click to collapse
Did you solve your issue? I am in your same situation

Nexus 4 Problem: Wont boot into system or recovery, but fastboot and able to flash?!!

Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?

zroice said:
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
Click to expand...
Click to collapse
u flashed stock doing fastboot -w update?

C4SCA said:
u flashed stock doing fastboot -w update?
Click to expand...
Click to collapse
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?

zroice said:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
Click to expand...
Click to collapse
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://forum.xda-developers.com/nexus-4/help/qhsusbdload-problem-t2253874
cheers

Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.

now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird

zroice said:
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
Click to expand...
Click to collapse
dont do fastboot erase cache. Do fastboot format cache.
reinstall the correct google usb drivers manually (http://forum.xda-developers.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)
try to flash 4.2.2 and see if it boots up using the flash all bat.
that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.

Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?

zroice said:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
Click to expand...
Click to collapse
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh

I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ

halloga said:
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
Click to expand...
Click to collapse
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)

zroice said:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
Click to expand...
Click to collapse
I know this situation man, I spent many hours too and finally solution came out that simple Hope you solve it soon

well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.
This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.
When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.
So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...
Must be bootloader or hardware issue im quite sure..

screen had been black with white lines.How can i fix this

Hello i have a ls980 my problem is i installed twrp with autorec for d802 to my ls980 after reboot screen had been black with white lines. No recovery and download mode when i connect to my pc on device manager it is seen as an android adb device no com ports. How can i fix this :crying::crying:

i have the same problem...this autorec app is wrecking the g2....did u find any fix?

Same problem
tuxim said:
i have the same problem...this autorec app is wrecking the g2....did u find any fix?
Click to expand...
Click to collapse
Hello everyone..
I have bought my Lg g2 d802 few days ago and when I tried to root it and install recovery using autorec the phone screen went black after rebooting into recovery and still in that state.. no led, no download mode , no recovery nothing else just white lines on left corner.... I tried it to get its software repair but they said that the lcd has been fused and need to be replaced ...
I tried to connect it to pc and it is showing marshall london adb interface and in another pc it is showing Android with yellow mark which turned in to Android adb interface after installing drivers from internet
I tried fastboot.exe and adb.exe but no device found error in adb mode but some commands working as fastboot..
I want to know is there a Hardware problem or it is a software issue??
Kindly help me to fix this issue...

obin.arssy said:
Hello everyone..
I have bought my Lg g2 d802 few days ago and when I tried to root it and install recovery using autorec the phone screen went black after rebooting into recovery and still in that state.. no led, no download mode , no recovery nothing else just white lines on left corner.... I tried it to get its software repair but they said that the lcd has been fused and need to be replaced ...
I tried to connect it to pc and it is showing marshall london adb interface and in another pc it is showing Android with yellow mark which turned in to Android adb interface after installing drivers from internet
I tried fastboot.exe and adb.exe but no device found error in adb mode but some commands working as fastboot..
I want to know is there a Hardware problem or it is a software issue??
Kindly help me to fix this issue...
Click to expand...
Click to collapse
i gave the phone to my dad and he went and showed it to some mechanics...they changed the display and flashed a stock rom and seemed to fixed the issue...dont know any details though...all i can say is im never modding this phone again

A2017G bricked with Lineage OS and Twrp

Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the ZTE logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!

mvortex3710 said:
Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the Axon logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!
Click to expand...
Click to collapse
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin

mischa_martin said:
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin
Click to expand...
Click to collapse
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James

mvortex3710 said:
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James
Click to expand...
Click to collapse
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in

mischa_martin said:
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in
Click to expand...
Click to collapse
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.

mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
As you are in EDL now you have some options.
First I would try to flash a recovery and boot image that is proven to be working fine e.g official twrp https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715 or some A2017G stock boot.img
If that doesn't help you could get in contact with @jcadduono to be a tester for that miflash method. (As your device is already pretty badly bricked)
I don't exactly know how EDL flashing works if it depends on a exact GPT table or not.
But I can say that I flashed every single part of the A2017U bootloader except for NON-HLOS (modem) on my A2017G for each B29 and B15 and it worked just fine. So maybe we just have to exchange the modem file in the EDL package :silly:
If you don't want to take that risk you also could try sending it back to ZTE and hope they don't check the bootloader :fingers-crossed:
(Just a thought: Maybe if the EDL package won't work on your device it will be so heavily damaged ZTE can't check for bootloader unlock and accept it as a warranty case, but don't take that too seriously )
Regards,
Martin

mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
If you are not afraid then try to use my package for A2017G with MiFlash: https://mega.nz/#!88BjXKhA!TnVSobBw5PkmShSqZ-Ni8MCCbnhJP2SWRNvvXqYHSjc

I really appreciate all this advice!
Looks like the MiFlash is promising. I was able to load the phone into MiFlash from the [EDL] thread. I have just tried the A2017G package provided by djkuz and will report back with any updates.
Just got to the mifavor screen, charging the battery from empty, although quickcharge appears to be functional again.
The charging battery logo is different from before so appears that this bootstack has done the trick.
The flashing red light has gone now, appears to be loading Lineage as before! I'm so grateful for all this help
However, now the unlock pattern is coming up as 'wrong pattern'. Is there anything that can be done? My settings appear to be saved as before (wallpaper and quick settings are the same).
I will attempt to reinstall twrp recovery and fix the lockscreen over adb. Thanks very much for the help. The brick has gone!!

Lenovo k6 Power Hard Bricked.

No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.

I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42

ImSSin said:
I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
Click to expand...
Click to collapse
Thank You ?
I am also trying my best to recover the phone and i will write here so that anyone who is facing this issue can recover his/her Phone.

No Solution found for this.
...
You have to send your Lenovo K6 Power to Lenovo Service Centre and get your Motherboard replaced.
If your phone is in guarantee then you will get free replacement no matter if your phone is rooted but please don't tell about root to them otherwise they will charge money for your small mistake.

what happened?

Do a new install

faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Boss it seems that you have hard bricked your phone so it means it's first boot has been corrupted there is no chance as first boot is mandatory to flash any file, there are some tools like octopus, or Medusa box, they can repair your boot then the phone can be used its just an outside chance 5o get it in workable condition look for some person or Repairing person have this boot repairing gadget,
If this fails too or you have messed up very badly then, last option is mother board replacement, there is no software option to repair by yourself

Help please..!!!!
:crying:
Even I face the same problem...
How do I go to download mode..???
It's stuck at Lenovo screen .... It just turn off on low battery and reboots on long press of power button.. Is it compulsory to have 80% of charge to get into download mode..???

i did the same. it switches on with lenovo logo , shows the os logo animation and its stuck there. when i tried connecting it to phone it showing unspecified device.
i could get into a fastboot mode . but nothing ahead to that. please find me a solution

Help me same issue
faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Did you find any solution for this, present i'm facing same issue, please tell me if you have any solution for this...