LG V40/LG general USB FASTBOOT working drivers??? - LG V40 Questions & Answers

Hello, I just wanted to unlock LG V40 official way/pie OS on it.
But I was for quite a long time stuck on that my Windows 10 were not able
to recognize the LG V40 in fastboot mode - so I was unable to perform fastboot commands...
Which drivers for fastboot do you use? After a long time I was able to find this thread https://forum.xda-developers.com/t/guide-v20-fastboot-access-in-windows.3491439/
but this seems absurd to me, that one need to look to LG V20 thread to find working fastboot drivers for LG from some mysterious package that miraculously works.
I am really glad that this works, but how to find/from where to get working fastboot drivers for my own and not to be dependent on
somebody, who creates some driver package, that maybe will not work after some time?
I used to normally get to the fastboot of my LG G7 so I was totally confused when I found out, that my old driver folder which I used to unlock the bootloader of LG G7 suddenly does not work... what happened? Did Windows 10 stop being compatible with fastboot drivers from LG?
Is it some legacy google fastboot drivers that work?
Or is it some general Qualcomm fastboot driver I need to look for?
Thanks to anyone willing to share knowledge about this.

I can't really help much, although I've gotten adb / fastboot to work on win 8.1 and 10.
The really unusual thing I found was that under windows, even after you've gotten the device to work with adb, you STILL have to find the device in device mgr, when connected with fastboot, and the SELECT the same driver AGAIN to work with fastboot.
I hate windows. I only have it for things like qfil. Linux is so much easier. Anyway, sorry for the rant. But, in my case, to get fastboot to work, find the indicator with the android ! mark and then assign the same adb driver for it.
I didn't have to use any specific one off package, it worked with (it was either lg or google adb usb driver - I'm not booted in windows to look at the mo).
cheers

AsItLies said:
I can't really help much, although I've gotten adb / fastboot to work on win 8.1 and 10.
The really unusual thing I found was that under windows, even after you've gotten the device to work with adb, you STILL have to find the device in device mgr, when connected with fastboot, and the SELECT the same driver AGAIN to work with fastboot.
I hate windows. I only have it for things like qfil. Linux is so much easier. Anyway, sorry for the rant. But, in my case, to get fastboot to work, find the indicator with the android ! mark and then assign the same adb driver for it.
I didn't have to use any specific one off package, it worked with (it was either lg or google adb usb driver - I'm not booted in windows to look at the mo).
cheers
Click to expand...
Click to collapse
Thank you for your reply. I didn't know that the same driver for ADB works for fastboot... I implicitly assumed that driver for fastboot must be different.
The "Android" device in device manager was what was driving me crazy. So thank you for this information, I will probably test
if this works on my other PC.

Related

Fastboot Troubles

I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.

Win7 don't recognize my fastbooted htc One

Hello,
i was going to unlock my phone ( done with desire,desire hd and sensation too) but i got a problem with recognizing phone in fastboot
i tried in a pc with windows8 64bit ( installing manually drivers like procedure) and also on win7 32bit
Both system see my phone when in normal mode, using adb devices it shows the letter/numbers
but once i type adb reboot booloader it rebbot it and then nothing..
Phone recognize Fastboot USB and my pc recognize it as working, but adb devices list nothing
Any help?
i also installed htc sync manager
EDIT:
is because i'm a totally IDIOT ,yes
I was typing adb devices in fastboot INSTEAD of fastboot devices..
I'm an idiot right xD??
erto90 said:
is because i'm a totally IDIOT ,yes
I was typing adb devices in fastboot INSTEAD of fastboot devices..
I'm an idiot right xD??
Click to expand...
Click to collapse
No, this is not it at all.
Newb mistake is the preferred terminology. "Newb" because unlike a noob you at least figured out the issue on your own and then shared back with the community. This is never a bad thing
None the less, thread closed as requested.

[Q] HTC One fastboot devices returns blank

Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
zWiLLX said:
Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
Click to expand...
Click to collapse
i would say you havent installed the drivers. best thing to download to get your HTC one to recognize in any mode is the HTC sync manager. i know its kinda annoying but the phone will get recongized in every mode and the initial plug in just requires a few minutes to detect, download, and install the drivers.
syaoran68 said:
i would say you havent installed the drivers.
Click to expand...
Click to collapse
I did try the "stripped" HTC One drivers found here on XDA.. I mean http://forum.xda-developers.com/showthread.php?t=2217396 seems pretty straightforward!
But yes at this point in the game why not give the full bloatware a try, thx
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Is your phone actually in fastboot mode?
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
BenPope said:
Is your phone actually in fastboot mode?
Click to expand...
Click to collapse
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
skinsfanbdh said:
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Click to expand...
Click to collapse
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
zWiLLX said:
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
Click to expand...
Click to collapse
there is a thread around for people who are having issues with windows 8. the soulution for you problem is probably in that thread
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
zWiLLX said:
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
Click to expand...
Click to collapse
to use fastboot commands it needs to say fastboot usb
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
zWiLLX said:
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
Click to expand...
Click to collapse
when it says waiting for device you have to close that cmd screen and if your phone says fastboot usb it will start but you have to manually close the first window
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
zWiLLX said:
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
Click to expand...
Click to collapse
when your phone is in bootloader does it say fastboot usb at the top?
i think the links for drivers are for samsung devices he said its copied from his other thread. you need to get drivers from somewhere else
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
zWiLLX said:
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
Click to expand...
Click to collapse
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
try pressing the power button while in bootloader. does it switch between hboot and fastboot usb?
MacHackz said:
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
Click to expand...
Click to collapse
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
yea it has to be plugged it to the computer first
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
Hey, I replied to your email PM me your TeamViewer info
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey guys, Im experiencing similar problems. How exactly did you guys solve it?
Thanks
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey, I´m experiencing the same problem here. Could you help me too?
Kenchinito said:
Hey, I´m experiencing the same problem here. Could you help me too?
Click to expand...
Click to collapse
Sorry for the very slow reply. Unfortunately, we won't know why HTC didn't play nicely with my Lenovo/Win8 laptop. However, I was quick to try a different older netbook I had lying around. At first, nothing happened, and I got used to the Sense UI enough to tolerate it.
But, I couldn't wifi tether and a few other unacceptable details, so I tried again last week with the same netbook that didn't seem to work the first time, and voila! Flawless. Maybe a reboot of that kicked it into gear, but both ADB and Fastboot were recognizing the HTC as a specific device, as opposed to the lenovo which found a ghost device with no name.
I am guessing too many android devices were installed and in the registry as USB devices, disorienting the PC, even though they were uninstalled, perhaps their drivers lingered as shared drivers. In theory I had S3 S4, HTC, possibly S2 and Motorola drivers all present.
The key is, keep the drivers on a folder on your phone with adb fastboot etc, and try a couple diff laptops. You'll know it worked when the device is recognized via "devices" with its unique number in both adb and fastboot.
Now running Revolution HD Google Play after trying CM 10.2 and Revolution HD Sense. CM did not work very smoothly with a lot of force crashes (navigation and music) and I can strongly recommend RevolutionHD google play edition.
Beware though, the first wipe takes out all the contacts and pictures etc, unfortunately, because I thought they would be spared.

[Q] Fastboot and Windows 8?

Hi all,
I have recently updated to the one and am having some trouble getting the fastboot commands working. Having been rooting/unlocking my phones for a few years now and have never really found the need to sign up and ask question as you can generally find what you need to solve most problems on here.
I have updated the driver using tutorials from here using the windows 7 ones. I have done this and everything works fine, the device is recognised. I can use the adb command to get the device connected information and adb reboot into bootloader, however when I get into the bootloader and into fastboot usb a windows notification pops up saying 'USB not recognised , the usb device connected to this computer malfunctioned and windows does not recognise it.'. As expected when I try any fastboot command it says it is waiting on device and is stuck there.
Hopefully it is something stupid I am missing out and not the device.
Any help would be good.
Thanks.

Question Windows 10 drivers for fastboot

My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
LesGirauds said:
My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
Click to expand...
Click to collapse
there is hundreds of tutos in youtube, go and check them
tutibreaker said:
there is hundreds of tutos in youtube, go and check them
Click to expand...
Click to collapse
And I've viewed a number of them. Could you link to one that actually works?
Seriously, I'm not stupid. I've tried a number of supposed solutions. I'm not a Windows geek, it's true, but I'm happily techie on UNIX platforms. Maybe this is something other than the actual driver. I'm more than happy to learn.,
LesGirauds said:
And I've viewed a number of them. Could you link to one that actually works?
Seriously, I'm not stupid. I've tried a number of supposed solutions. I'm not a Windows geek, it's true, but I'm happily techie on UNIX platforms. Maybe this is something other than the actual driver. I'm more than happy to learn.,
Click to expand...
Click to collapse
For those who have problems installing , you need to create a new folder called "Desktop" in C:/Users/*Your user*
LesGirauds said:
My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
Click to expand...
Click to collapse
This is exactly my problem on Redmi note 11S. I already tried a lot of drivers and tutorials and still no succes. In linux fastboot works.
PS: Les Girauds, you can unlock bootloader by mtkclient (linux), not just via official tool (Mi unlock). I already did it.
Magic Cucumber said:
you can unlock bootloader by mtkclient
Click to expand...
Click to collapse
Thanks, might give that a go.
I tried another UNIX based unlock solution yesterday (a python prog from GitHub) and whilst it didn't work cleanly (nor successfully unlock the device) I did see in the garbled error message returned about having to wait 121 hours. So maybe the phone will be successfully unlocked on Tuesday!
tutibreaker said:
For those who have problems installing , you need to create a new folder called "Desktop" in C:/Users/*Your user*
Click to expand...
Click to collapse
Thanks, that's worked. The Yt video didn't show for me so I copied it's URL and opened in a separate browser window. The video went through the process for Win 11 but I guess it's the same for Win10 (my system), and it worked so that's OK. Weird thing is, it was only an install of the generic adb drivers which I'd installed previously anyway, and had been using for some time, doing updates on my Lenovo tablet etc. So they were there and working once upon a time. I can only assume that the process of installing the MiUnlock screwed them up somehow.
@Magic Cucumber - it might be worth you simply reinstalling the standard adb platform tools, It might give you back fastboot access
Magic Cucumber said:
you can unlock bootloader by mtkclient (linux),
Click to expand...
Click to collapse
Thank you. It worked. The MIUnlock said I had to wait but mtkclient did it immediately.
Now I'm going to flash a custom ROM, and maybe twrp, just have a device I'm happier with. Xiaomi phones maybe good value but I don't like the stock software.

Categories

Resources