Related
Creating a troubleshooting thread to see if might be able to get some help on a big problem I'm having with my LG G2...
I'm trying to restore my VZ LG G2 to stock so that it can be returned (audio input is malfunctioning). I am currently running TWRP + CM 11 Nightlies on it.
When I enter download mode, I see the screen "Firmware Update" and it says "B99" and "Rooted" at the bottom.
When I use the R&D Test Tool + LGMobile Support Tool to try to restore to VS98011A_01.kdz, the software update runs on my computer as if it is pushing the update to the phone, but the phone itself shows no actual status change. It just sits there with 0% on the status bar.
When it finishes on my computer it says (on my computer) that the software update was successful. Unfortunately my phone boots into CM just like it normally does with all my apps and data there.
Based on some suggestions I have seen, I have tried manually changing to COM 41 and disabling the device as a modem in device manager -- does not make a difference.
I have no idea why no actual change is happening on the phone. Any suggestions?
Man, this is brutal. I thought that maybe the issue was that I was using the 3.10 LG United drivers instead of the 3.8 drivers, so I uninstalled 3.10 and installed 3.8.
Unfortunately now the LG G2 is recognized when it is in normal mode (running CM 11.0) but Windows shows "No drivers found" when I put it in download mode:
USB Composite Device: Ready to Use
CDC Serial: No drive found
CDC ECM: No driver found
LGE Android Phone: No driver found
Network Controller: No driver found
The last four all show up under "Other devices" in device manager with an exclamation.
Previously I was at least able to see the LG Android VZW etc. etc. under COM/Ports with 3.10 drivers installed.
I am burning so much time trying to figure this out. Mayday, mayday!
For anyone that may come across this thread in the future, I want to share what ultimately worked.
I followed the TOT method instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2448960
It was just as easy as the KDZ method, but actually worked! Here are the two things that seemed to make a difference:
1. I installed the _Verizon_ LG drivers referenced in that thread
2. I manually changed to COM41
Following all instructions in that thread everything worked like a charm.
I have a rooted Verizon LG G2 that I somehow screwed up when going to Lollipop from KitKat. I have lost my 3G and LTE capabilities, thus no data unless connected to WiFi. From what I have read, it sounds like I need to try to revert to stock and start over. This is where I am having my major issues. I have tried the .kdz and the .tot methods of returning my phone to stock firmware. Upon placing my phone into Download mode on both a PC and a laptop (Windows 7 on both) my phone is at best recognized as a USB Modem Phone ADB Port, not the Port (COM LPT) that is required for either method to work. What can I do to get my phone to register as the Serial Port so that the LG Flash Tools will recognize it? (I have installed the most recent LG VZW Drivers and have uninstalled other drivers without any changes). Thanks
!bump having the same issue myself
Beeve said:
I have a rooted Verizon LG G2 that I somehow screwed up when going to Lollipop from KitKat. I have lost my 3G and LTE capabilities, thus no data unless connected to WiFi. From what I have read, it sounds like I need to try to revert to stock and start over. This is where I am having my major issues. I have tried the .kdz and the .tot methods of returning my phone to stock firmware. Upon placing my phone into Download mode on both a PC and a laptop (Windows 7 on both) my phone is at best recognized as a USB Modem Phone ADB Port, not the Port (COM LPT) that is required for either method to work. What can I do to get my phone to register as the Serial Port so that the LG Flash Tools will recognize it? (I have installed the most recent LG VZW Drivers and have uninstalled other drivers without any changes). Thanks
Click to expand...
Click to collapse
Screenshots, exact details, please. Maybe it's a simple driver fix or maybe it's a scary Qcomm diag mode issue (hopefully the good one). You've installed the latest drivers from LG, yes (3.12 or 3.13)? You often (usually) have to manually update the driver in Device Manager. Nothing listed under COM ports at all while the phone is in download mode?
Standard what-have-you:
Install latest LG Drivers (can be downloaded from LG support website).
Open Windows Device Manager and look under COM Ports for the LG device. Right-click on device, choose properties, and change the COM port to Port 41. Even if it says that port is already in use, do it anyways. This the port that LG Flash Tools uses to flash their stock images.
NOTE: Some tutorials will tell you to set your computers date back to make LG Flash Tools work: that is incorrect with version 1.8x and unnecessary, ignore them.
After the port is set to 41, unplug the USB cable from the phone, then open up LGFlashTools.exe. Select the correct VS980 .dll file and select the TOT file to flash. Press OK. Then press the yellow arrow in the upper left of the main LG Flash Tools window. It will think for a minute, then say Ready! or some such crap in the upper left port 41 box. Then you plug the USB cable back into the phone and it will start flashing. You do not have to wait until it reaches 100%, only until the phone fully boots up and presents you with the LG Setup Wizard (1st thing it asks for is your language preference). After you get there just close the LG Flash Tools program.
If it does not successfully flash:
-- Make sure you connect the USB cable directly to a motherboard port, do *not* use a hub.
-- Do not connect or remove others devices to your system until the flashing is done, as I've had that bork my flash before.
info
culot said:
Screenshots, exact details, please. Maybe it's a simple driver fix or maybe it's a scary Qcomm diag mode issue (hopefully the good one). You've installed the latest drivers from LG, yes (3.12 or 3.13)? You often (usually) have to manually update the driver in Device Manager. Nothing listed under COM ports at all while the phone is in download mode?
Standard what-have-you:
Install latest LG Drivers (can be downloaded from LG support website).
Open Windows Device Manager and look under COM Ports for the LG device. Right-click on device, choose properties, and change the COM port to Port 41. Even if it says that port is already in use, do it anyways. This the port that LG Flash Tools uses to flash their stock images.
NOTE: Some tutorials will tell you to set your computers date back to make LG Flash Tools work: that is incorrect with version 1.8x and unnecessary, ignore them.
After the port is set to 41, unplug the USB cable from the phone, then open up LGFlashTools.exe. Select the correct VS980 .dll file and select the TOT file to flash. Press OK. Then press the yellow arrow in the upper left of the main LG Flash Tools window. It will think for a minute, then say Ready! or some such crap in the upper left port 41 box. Then you plug the USB cable back into the phone and it will start flashing. You do not have to wait until it reaches 100%, only until the phone fully boots up and presents you with the LG Setup Wizard (1st thing it asks for is your language preference). After you get there just close the LG Flash Tools program.
If it does not successfully flash:
-- Make sure you connect the USB cable directly to a motherboard port, do *not* use a hub.
-- Do not connect or remove others devices to your system until the flashing is done, as I've had that bork my flash before.
Click to expand...
Click to collapse
LG site has latest VS980 drivers as 2.18
When I plug in my phone and download mode starts, Device Manager will intially show it under 'Other Devices' as 'Android'. Then it will load a generic Android ADB driver. If I hijack the driver install I can manually install an LG Port (COM and LPT) driver, but it will error upon install. It will still show with a yellow exclamation point. I can still change the Port here, but its the error that I think is holding everything up.
I've tried both the kdz and tot method to no avail.
I've tried on a PC, both front and rear USB ports, and a laptop (both USB ports) and no luck.
Any other info I can provide to you? Thanks for helping
Beeve said:
LG site has latest VS980 drivers as 2.18
When I plug in my phone and download mode starts, Device Manager will intially show it under 'Other Devices' as 'Android'. Then it will load a generic Android ADB driver. If I hijack the driver install I can manually install an LG Port (COM and LPT) driver, but it will error upon install. It will still show with a yellow exclamation point. I can still change the Port here, but its the error that I think is holding everything up.
I've tried both the kdz and tot method to no avail.
I've tried on a PC, both front and rear USB ports, and a laptop (both USB ports) and no luck.
Any other info I can provide to you? Thanks for helping
Click to expand...
Click to collapse
Stick to the rear USB ports on the PC, definitely. I've sometimes had it work via a hub, sometimes not (more often not).
So you've chosen the LGE AndroidNet driver, yes? And at this point you don't have the LG Flash Tools open yet, yes? It's best to keep that closed until after you've set the COM port to 41 (probably safe either way, but it does flag a conflict in com ports sometimes, which IME, doesn't matter, but still). While leaving the phone plugged into the USB, is that exclamation point still there after reboot? Screenshots? What error message does it provide under the devices status when you choose Right-click->Propertires(/Alt+Enter)?
Info
I've attached screenshots of the driver error as I install it and its properties. I've also attached shots of using the kdz method showing that nothing is detected when I press the phone information button, and also a shot of the error saying phone is disconnected when starting the flash process.
Beeve said:
I've attached screenshots of the driver error as I install it and its properties. I've also attached shots of using the kdz method showing that nothing is detected when I press the phone information button, and also a shot of the error saying phone is disconnected when starting the flash process.
Click to expand...
Click to collapse
Oh gosh, I'm sorry, I didn't see this reply! XDA sometimes notifies me of replies, sometimes it doesn't. Often it doesn't, grrrr! Are you still stuck here? lol. crap, so sorry.
EDIT:
Oh, when I was mentioning port 41 I think was thinking LG Flash Tools for TOT files, no the 2014 version (which I haven't used in a while).
But that's moot, thanks to the 'device cannot start' error. This should put it into perspective:
- Uninstall all the drivers for that, all LG drivers, all Android drivers, kill 'em all -- this includes uninstalling all LG smartphone software, too. (Note: using something like UninstallTool is always best (IObit has a bloatware-laden tool like that that's free), but surely the Windows Installer should uninstall fine.)
- Reboot.
- Reinstall LG Drivers with their installer.
- Boot device into Android then plug in USB.
Windows should do the usual finding drivers rigamarole, and if it's taking a long time (more than 30 seconds or so), unplug device, the Windows add drivers dialogs should disappear, then plug it back in.
- Check Device Manager to make sure the drivers automatically loaded up, check the details on each of the drivers to make sure it's the LG driver (since you should have no other LG or Android drivers installed at this point it should be).
- If exclamation point next to device, the do the update driver thing and choose the correct LG driver.
- Reboot Windows.
- Unplug device.
- Put device in 'Download Mode' and connect USB (use motherboard ports if on desktop, not hub or case ports; never had port problem on laptop).
- Check Device Manager to see if drivers auto-found it (usually not, for me).
- Update them to LG drivers.
Is the driver still throwing up errors at this point?
Oh, when in Device Manager, select the device, then choose from the menubar View->Device by Connection. It will show the other drivers loaded for that device, and more importantly, it will show just where the device is connected to. A screenshot of that would be mucho helpful if your problem still persists.
Again, sorry I didn't get back to you. D:
Ha ha, I wasn't notified of this either. I never did get it to work. Because what I was really looking for was to get my radios working again, I had another member suggest going to a ;stock-ish' rom and flashing it (xdabbeb) along with the 12b bootstack. Lo and behold this worked for me. I was able to get my phone to show up via ADB so that I could push the files over. I never could get the .tot or .kdz to work, but I don't have the need to continue on at this point.
Thanks for your help though!
hello BEEVE i have screwed my lg g2 in the same way so can you please tell me how did you fix it or give me a link or something anything is fine
thanks in advance
I ended up flashing to a Rom that was based on stock LG. Been awhile so I don't remember. It seemed to help after a while. I also used the LTE Discovery app whenever I wasn't using my phone. The thought was that it would trick it into working. I think what actually ended up working was time. It just eventually started working better. Maybe a combination of everything, I don't know. I no longer use the phone so it's a little sketchy.
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.
I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
ileikpi said:
I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
Click to expand...
Click to collapse
either you are not in bootloader mode on the phone or you need to fix your drivers.
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
I got stuck at that step as well, had to do a hard reboot, attempts at reinstalling the drivers only seemed to make it worse!
JP_93 said:
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
Click to expand...
Click to collapse
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
ileikpi said:
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
Click to expand...
Click to collapse
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
JP_93 said:
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
Click to expand...
Click to collapse
Zadig doesn't let me right click to uninstall drivers T-T. I tried reflashing twrp and redoing everything in the guide to make sure I didn't miss anything but I'm still stuck at < waiting for any device >. Unlocked bootloader seems so close yet so far... Thank you very much for your help thus far tho!
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Bucci83 said:
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Click to expand...
Click to collapse
Yep it does.
lafester said:
either you are not in bootloader mode on the phone or you need to fix your drivers.
Click to expand...
Click to collapse
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
ileikpi said:
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
Click to expand...
Click to collapse
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Bucci83 said:
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Click to expand...
Click to collapse
Ok I'll try that when I get home.
Sorry but may I ask if you remember what your phone was called in device manager when you rebooted it into bootloader? Was it "Android", some Qualcomm code (ie. QUSB_BULK), or ADB something? In @JP_93 and my cases, our phones were simply labelled as "Android" in device manager.
Unlocked using a different PC
Ok guys, I managed to unlock my phone using a friend's computer with no problems. The drivers in my own pc were definitely messed up and uninstalling and reinstalling them didn't work.
Thank you very much to everyone for your help and sorry if I blew this out of proportion!
Glad you got it to work!
I'm trying to flash a new KDZ on my phone with LGUP. I have the LG drivers (4.5, downloaded from lg.com) installed in a Windows 10 Virtualbox (running under Debian), as well as the LGUP-0.0.3.23 installed (downloaded from https://lgflash.com/LGUP/), but when I plug in my phone in "download mode" and then start LGUP it keeps telling me "there is no handset connected".
Windows's "bluetooth&other devices" page in the settings does see (under "other devices") my phone, listed as "LG AndroidNet Phone" but this also says "Driver error". Any idea what I might be doing wrong and what this driver error might be about?
From what I've seen around here, I'm not sure if anyone has ever successfully been able to use LGUP using any kind of virtual environment of Windows. You'll save yourself some headaches if you can find a Windows computer to do this step on.
Hmm... I see, thanks