Here's the link!
Got released just today, this is a really specific problem, when your device is not recognizable by fastboot/adb/LGUP. Windows can only recognize it as qhsusb_bulk or QDLoader 9008 if you have the proper drivers installed.
I personally don't own the V10, just felt like sharing since he released it today and maybe it can be helpful for someone!
Related
Hi all, I need help trying to get the USB VCOM DRIVER to work, specifically the PRELOADER. Everything works well, except for the preloader. It gets recognised as a Mtk Usb device, the. Reconnects as a professional device, but it never gets past the Download DA Red bar. Can someone provide me with a working Preloader driver? Running Windows 10 Creator Update
Hi there,
I recently bought a cheap lg G5 from eBay which said it was stuck on a bootloop. The seller said they weren't very tech savvy and I decided to give it a try, seemed fun. I have never done this before, so when searching on Google I stumbled upon threads saying it should be rather easy to fix by using LG Bridge and let it recover/repair the installation. However, after installing LG Bridge and LG Drivers from their website , every time I boot the phone in Download mode and it progresses into a firmware updating screen, my Windows 10 64bit fails to connect the device properly and prompting me with the following message:
USB device not recognized.
The last USB device you connected to this computer malfunctioned, and windows does not recognize it.
And in device manager it shows "Unknown USB Device (Device Descriptor Request Failed).
Is there anything I could try? Is it fixable like I thought?
Bump, anyone? Im stumped but would love tot learn about this
yointed said:
Bump, anyone? Im stumped but would love tot learn about this
Click to expand...
Click to collapse
I have never had the experience to get a bootloop but my guess is that you have some driver problems, thats why its not well recognised by your computer.
Try to check if there is a youtube tutorial with some links to the drivers related to the G5.
Sorry if this isnt very helpful, but its the best I can add to this topic.
---------- Post added at 07:30 AM ---------- Previous post was at 07:28 AM ----------
Pistacho123Lol said:
I have never had the experience to get a bootloop but my guess is that you have some driver problems, thats why its not well recognised by your computer.
Try to check if there is a youtube tutorial with some links to the drivers related to the G5.
Sorry if this isnt very helpful, but its the best I can add to this topic.
Click to expand...
Click to collapse
Or try with another pc running windows 7, maybe your OS and compatibility is the problem!
Definitely a driver issue! I had a similar problem with moto x4! It was not being recognised by my pc! Uninstalling the previous usb driver fixed it for me! Try to remove any remnants of drivers you might have installed previously.
Thank you for the replies. I also thought it would be a driver issue, however I have already tried uninstalling and reinstalling the LG drivers for the LG G5 multiple times and I did not get it to work. Unfortunately, I do not have a Windows 7 computer. Would it be possible to install windows 7 solely for this, without a license key?
yointed said:
Thank you for the replies. I also thought it would be a driver issue, however I have already tried uninstalling and reinstalling the LG drivers for the LG G5 multiple times and I did not get it to work. Unfortunately, I do not have a Windows 7 computer. Would it be possible to install windows 7 solely for this, without a license key?
Click to expand...
Click to collapse
If you can find a copy of it some where. You can use it for like 30 days or so before activation.
I do not know any coding, and have never even rooted a device, but i had this problem with stock rom 8.0, tried looking into flashing new stock rom installed all the drivers, still couldnt connect to pc. After 4 days with no phone i thought id throw my other battery in it, it booted up perfectly like it was out of the box, probably because i tried the restore in safe mode... Hope this helps... P.s. id like to learn
Hello,
it seems like I am stuck with a bricked Nokia 7.2 in 9008 mode. I've read one needs a nb0 firmware. I couldn't really find anything for Nokia 7.2 specifically. Is there anything I can do at all? The bootloader is unlocked.
The phone does not react to anything except for USB connection where pc recognizes it as a 9008 device of some sort.
there is no firehose anywhere, The most beautiful thing about this is that even from others firehose from other nokia will not work ??*??*??* Thanks HMD ???
lilmonkw said:
Hello,
it seems like I am stuck with a bricked Nokia 7.2 in 9008 mode. I've read one needs a nb0 firmware. I couldn't really find anything for Nokia 7.2 specifically. Is there anything I can do at all? The bootloader is unlocked.
The phone does not react to anything except for USB connection where pc recognizes it as a 9008 device of some sort.
Click to expand...
Click to collapse
Hello, my phone is also stucked in 9008 mode, were you able to find those files. If you found can you please share the files with me. Thanks
it's a bit late for that. I've long returned the phone to the store I bought it at. I have never managed to unbrick it. Sorry.
Hi everyone,
i wanted to install a newer android version on my old LG G2 Mini. But something went wrong and now it's totally dead. The screen does not do anything. When connecting it to my computer, nothing happens.
I researched on the internet and now I have shorted the emmc testpoint to get it into download mode. That worked, so it shows up in the device manager as "Qualcomm HS-USB QDLoader 9008".
Here comes the problem: After following a couple of internet tutorials, I still didn't manage to flash anything on it.
It's not too bad, because it's not my main phone, but I'd like to use it as a second phone and I hope someone can help me.
Jojo2110 said:
Hi everyone,
i wanted to install a newer android version on my old LG G2 Mini. But something went wrong and now it's totally dead. The screen does not do anything. When connecting it to my computer, nothing happens.
I researched on the internet and now I have shorted the emmc testpoint to get it into download mode. That worked, so it shows up in the device manager as "Qualcomm HS-USB QDLoader 9008".
Here comes the problem: After following a couple of internet tutorials, I still didn't manage to flash anything on it.
It's not too bad, because it's not my main phone, but I'd like to use it as a second phone and I hope someone can help me.
Click to expand...
Click to collapse
you need the "loader.img,, File. But i can't find the File. My G2 Mini works, but I dont know, how i schould dump the File
Okay, so I recently got a oneplus nord n20 cheap because the os had been wiped. when I get it, I find out that fastboot can not be accessed, and so I try going the MSM route.
It may be worth noting, that this is my first experience with a oneplus phone.
When I boot into EDL, the computer recognizes the device as "Qualcomm hs-usb qdloader 9008" but MSM does not recognize the device at all, and the phone boots back to the no os warning after a few seconds, and I'm not sure what is causing this, or what to try next.
I'm using flash tool v4.1.7 because it is the newest version I could find a way to get around the password on, I'm not sure if using an older version of the tool like I am might lead to recognition problems or not.
I'm pretty sure I have the proper qualcomm driver
I have a rom that should be for this specific phone.
The rom I downloaded came with it's own "download tool" but it was in chinese, and seemed to be unusable anyway
I am using windows 7, I don't know if that may cause compatibility issues with the newer driver, but it's the only windows installation I've got, because I don't usually use windows anymore.
Does anyone know why my phone might be refusing to stay in EDL mode?
Does anyone know where I can get an updated MSM tool that doesn't require a login I can't get?
Try upgrading to Windows 10.
Sorry, install some drivers and a new MSM tool.
cmfCyangenModteam said:
Try upgrading to Windows 10.
Sorry, install some drivers and a new MSM tool.
Click to expand...
Click to collapse
Win10 isn't an option for me, I've got the newest driver I could find, I do have a newer msm tool downloaded, but I can't get around the account requirement, and I don't know how to get an account
Check device manager. . you probably got an exclamation point.
My guy can TeamViewer to your phone and get u set up for edl
I_Am_The_Lag_Switch said:
Okay, so I recently got a oneplus nord n20 cheap because the os had been wiped. when I get it, I find out that fastboot can not be accessed, and so I try going the MSM route.
It may be worth noting, that this is my first experience with a oneplus phone.
When I boot into EDL, the computer recognizes the device as "Qualcomm hs-usb qdloader 9008" but MSM does not recognize the device at all, and the phone boots back to the no os warning after a few seconds, and I'm not sure what is causing this, or what to try next.
I'm using flash tool v4.1.7 because it is the newest version I could find a way to get around the password on, I'm not sure if using an older version of the tool like I am might lead to recognition problems or not.
I'm pretty sure I have the proper qualcomm driver
I have a rom that should be for this specific phone.
The rom I downloaded came with it's own "download tool" but it was in chinese, and seemed to be unusable anyway
I am using windows 7, I don't know if that may cause compatibility issues with the newer driver, but it's the only windows installation I've got, because I don't usually use windows anymore.
Does anyone know why my phone might be refusing to stay in EDL mode?
Does anyone know where I can get an updated MSM tool that doesn't require a login I can't get?
Click to expand...
Click to collapse
Disable driver signature on Windows 7 first or use signed qualcomm drivers for avoiding it.
MSM uses server authorisation and is only used by the service center.
You may have to pay someone to flash the device in edl which I cannot explain here due to
XDA policies.