Develop Bugs

ADB drivers for Galaxy Nexus?

I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!

thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
Did you ever find this out, I'm having the same problem.

Just install the SDK and it should work?
Sent from my HTC Desire HD using Tapatalk

yes the drivers are included in the android SDK from google website

I installed the pdanet software to get it recognized in the fastboot mode.

thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.

I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)

mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
You sir, are my hero!
Thanks alot

Easiest way is through installing PDAnet, that's what I did.
Sent from my Galaxy Nexus using XDA App

On Windows 7 you go to device manager and select
Updated driver > Browse my computer... > Let me select... > Show all > Have disk
And then browse to the inf file in the android-sdk-windows\extras\google\usb_driver folder.
It's a pain but it works perfectly.

or get a mac

appelflap said:
or get a mac
Click to expand...
Click to collapse
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.

Eoinoc said:
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.
Click to expand...
Click to collapse
Agree, although developing on a unix based machine (mac or linux) is so much faster.

gambiting said:
I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)
Click to expand...
Click to collapse
Worked perfectly, thank you!

Can somebody help me. I have everything installed but it won't recognize my device
Sent from my Galaxy Nexus using xda premium

I'm new and not allowed to post links
Go to the Samsung Homepage of your Country/Language, go to support -> download center, enter galaxy and use the autocompletion for galaxy nexus, then download the usb driver

was not working for me so I force the use of google usb driver from Android SDK by:
- opening windows device manager
- right click -> update driver on the Other devices : Galaxy(exclamation mark)
- Browse my computer option
- Let me pick from my computer option
- click next on the Show All Devices upper selection
- click Have Disk and browse toward your android-sdk\extras\google\usb_driver
- select Android ADB Interface, Next and finish with the Yes
adb devices command reply correctly
I've done the same and flash succesfully my Gnex in fastboot (once you're in bootloader the driver to update in device manager is Android 1.0).
Adding new lines in the android_winusb.inf file from the extras\google\usb_driver leads exactly to the same result.
As it's not a conventional method there might be some issues

mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
Just wanted to say thank you as this has resolved my issue. I had installed Android SDK which didnt help.
Edit: I had to install the driver to DeskNotifier application would work with my Galaxy Nexus. After installing, it did connect fine. Strangely though, as soon as I sent a test msg from my phone to the PC, my computer became extremely sluggish. I am now rebooting

USB driver still won't install
Neither the USB driver from Samsung nor Google will work on my Win7 machine with my Galaxy Nexus. I have the device plugged in and in recovery mode. The device shows up as a Galaxy Nexus on the device manager, but is unable to install either one.
Thanks for your help.

http://forum.xda-developers.com/showthread.php?t=1626895, part A. It seems the device should be booted normally to install the adb drivers.

[Solution]Windows 8 - ADB/fastboot driver problem solved!!

Hello!!​
Well, hey guys. I thought I tell you the story, on why I posted this thread.
It started as I was installing Windows 8, on my laptop, and had the same problem, as some others. I just could not install the drivers, for my Droid, so I had a looksee and found that Windows 8 didn't yet have the capability, to download unsigned drivers, unlike Windows 7. So, I found a way of "tricking" Windows, into thinking, that these drivers are legit and it isn't forbidden to use, which is exactly what this tutorial tells Windows, in a way.
So, get going and use the full potential of your Android device!
Tutorial:​
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... : devmgmt.msc
Now, the dive manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here/
To prevent confusion: When I say install, it can mean unpack, or instal... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has poped up, choose "Browse my computer" and goto your dsktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\adb reboot-bootloader
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick, from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices.
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your SAMUNG GALAXY NEXUS!"!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Addition: You can only reboot into bootloader, if you are using a motorola, Google or HTC branded Android device! This will NOT work with Samsung models (i.e. Galaxy S II/III) due to the fact, that they use Odin mode. Should the drivers need updating, for some devices, please let me know!

Motorola Razr
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.

thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Click to expand...
Click to collapse
Download MotoHelper. Right click the file and run in compatibility mode. It should install the drivers. I used this to run fastboot with my xoom.

It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.

thejakenixon said:
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
Click to expand...
Click to collapse
Bummer, I just remembered there was a setting to skip os version check in compatibility mode. Did you try that? If that won't work unfortunately I don't know what else to try. Sorry.
Sent from my Xoom using XDA Premium HD app

thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
First of all, thanks, for letting me know about the link It's uploading again ^^
Yes, you can do the same for your Motorola. But only with the ADB drivers. Just do the same as with the Samsung. Select your device, form the devman. and right click. Update device drivers -> Browse -> Let me choose from a list... -> Samsnung ADB interface.
They are all provided by Google, inc. so, they are compatible, with every Android device. I've even used my Samsung ADB drivers, for a Sony Ericsson Xperia X8. So I can actually say, for myself, that they work. You then can work, using fastboot... ^^
Have fun fastbooting!
LG familyguy59/Beatsleigher

Well, I'm definitly glad, to see I'm actually helping some people, and they're appreciating it!!
I don't remember mentioning it, but if you Need help, PM me. I'll help you via Team Viewer ^^

will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?

iconicpaul said:
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
Click to expand...
Click to collapse
Yes, it works on both x86 and x64 bit architectures of Windows 8, works withRC and with pre-release...
Sent from my GT-I9300 using xda app-developers app

confirmed, it works, thank you...very fast and easy

thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
To your edit. You have extracted the files. This is also called "installing" because you have extracted NEEDED files. Even when you extract a .zip/.rar/.tar/.tar.gz and so on, because you need files out of them, you are installing, but not to the system, but to yourself

Sorry for bringing up an old post, but this method is not working for me on Windows 8 Consumer Preview. When I'm trying to install the ADB drivers, it says the drivers cannot be installed because it's not digitally signed.
UPDATE: I got it to work by disabling the Digital Signature Enforcement on Windows 8. Steps: Restart Windows > Boot loader Menu > Other Options > Advance Options > *Computer Automatically Restarts* > Press F7 to Disable Digital Signature Enforcement

I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app

2phonejones said:
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...

iconicpaul said:
confirmed, it works, thank you...very fast and easy
Click to expand...
Click to collapse
No worries, dude That's what I posted this thread for.

familyguy59 said:
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
Click to expand...
Click to collapse
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:

Could someone pls. create a video tutorial, nad post this on Youtube, for me?
My laptop broke a couple of days ago, and my PC is only capable of running 98 - Vista, so, running on XP with 1GB of RAM.
I would appreciate this very much!
If you could do so and send me the link, via PM, I would be glad to pay 5€, via PayPal!

2phonejones said:
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Click to expand...
Click to collapse
Ok, dude! Have fun!

Didn't work for me.

jorgefcbastos said:
Didn't work for me.
Click to expand...
Click to collapse
Did you follow the tutorial COMPLETELY, or did you leave stuff out? If you left something out, it's obviously not going to work
You may have to disable device driver signing, I've had quite a few people notify me about this.
But I'll sign the drivers, ASAP, so you won't have this problem
LG familyguy59/Beatsleigher
Edit: I forgot to mention, you need to tell me what exactly didn't work, otherwise I can't really help you

[Q] One X-specific solution for fastboot under Windows 8

I tried numerous "solutions" floating around this site and web on how to get fastboot working again on my Windows 8 RTM 64bit with HOX on CM10 ROM. ADB and USB memory are working, but fastboot does nothing. Of course have driver signature off in Windows. Currently back to original HTC driver in order to have at least USB memory working reliably.

Lucas0511 said:
I tried numerous "solutions" floating around this site and web on how to get fastboot working again on my Windows 8 RTM 64bit with HOX on CM10 ROM. ADB and USB memory are working, but fastboot does nothing. Of course have driver signature off in Windows. Currently back to original HTC driver in order to have at least USB memory working reliably.
Click to expand...
Click to collapse
Have you tried to kill adb process?
Ctrl+Alt+Del -> Task Manager -> More details
Click on adb process and then hit "End Task" button
Then open cmd and try to run fastboot again.

Thanks for the suggestion, but does not work - waiting for device...

You sure you have the correct USB ADB/Fastboot drivers installed? I had to boot into a special Win* mode to install unsigned drivers.
This thread here should detail it for you. Post 2 covers the unsigned drivers part.
http://forum.xda-developers.com/showthread.php?t=1583801

Yes, had done that previously, too. For me fastboot is working (adb always was) since I use the latest one from the Android SDK.

i just installed these drivers and it worked
Download

[GUIDE]Enable USB Debugging and setup Android SDK for Fire Phone

Disclaimer:I am not responsible if using anything I've made or provided suddenly deep-fries your device or causes thermonuclear war leading to alien abductions.
Hey guys!
It's been a while that I've been seeing people having problems to enable USB debugging and setting up the Android SDK to recognize the device. So,I've made a guide to help you enable USB debugging and set up the Android SDK accordingly. So let's begin!
What you'll need:
Windows/Linux/Mac OS X with the Android SDK installed
A Fire Phone
Click to expand...
Click to collapse
Setting up Android SDK and drivers:
At first,make sure you have the Android SDK installed,adb and fastboot working.
Open the SDK manager
Click on "Tools" and then click on "Manage add-on sites"
Click on the "User Defined Sites" tab,click "Add" and paste this URL:https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
Click "Ok". Wait for it to finish. Then,from the repo of Android 4.2.2(API Level 17),select Fire Phone SDK and install it.
Remove any Fire Phone drivers using device manager
Go to the directory of the SDK and find this:
Code:
/add-ons/addon-fire_phone_sdk_addon-amazon-17/tools/KindleDrivers.exe
Run the driver setup and connect the phone having USB debugging enabled. If you don't know how to do this,it's explained below.
Done!
Click to expand...
Click to collapse
Enabling USB debugging:
Go to Settings
Scroll to the Device section and expand the section.
Tap Get info about your Fire.
Tap any item at least 7 times in 5 seconds
Developer options will appear. Set it to On.
Go to developer options and enable USB debugging.
Done!
Click to expand...
Click to collapse
Thanks a lot for reading my guide. If this was useful to you,please hit the thanks button. Feel free to comment,post or report anything. Thanks.

Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:

I am M3 said:
Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:
Click to expand...
Click to collapse
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.

I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
Could you try in a Linux distro live CD? It should detect the device without a hitch
Sent from my device running CyanogenMod 11

I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
If you're using Windows here's how I did it on Windows 7. Once you open ADB and reboot it into recovery mode remove it from Device Manager. Reboot you PC if asked. Never unplug or remove your phone through any of this. You may need to remove it a second time from Device Manager after a reboot. It'll eventually show up under Other Devices with the Model Number as the device name (at least mine did). Once it's there then go and update the driver. Tell Windows you want to pick from a list of all the devices. Scroll down until you see Amazon listed on the left side. You'll then see "Android Composite ADB Interface" listed on the right. Choose that. Then it should be recognized again and you can sideload to roll back. Once you roll back you'll probably get a lot of errors but it will work and it will root using the towelroot APK that's posted in the other forum here. I had to have my phone services so I had to do a factory reset on my phone because it broke my phone services. But the roll back process itself was very easy to do once I figured out how to get it recognized again while in recovery mode.

I did what the directions say, but I don't see the fire phone listed in the sdk.

mnknight said:
I did what the directions say, but I don't see the fire phone listed in the sdk.
Click to expand...
Click to collapse
You have to choose the correct driver in Device Manager
On Windows 8/8.1 you may have to activate unsigned drivers

Kindle drivers don't seem to be working for me!

In Windows 8 and newer you have to activate unsigned drivers.
And please choose driver in device manager!

Kindle driver not working for me on windows 7
Kindle driver not working for me on windows 7

Grizzly123 said:
Kindle driver not working for me on windows 7
Click to expand...
Click to collapse
Try using a Linux distro

hey, first sorry for my bad english. isnt my native language.
ich have installed all i need (Windows/Linux/Mac OS X with the Android SDK installed,Android SDK installed,adb and fastboot working[but i dont really know what fastboot working means.])
i have no problem with step 1-5 but i dont understand step 6. i google it but i dont understand. can you please update pictures? that would be very nice.
i have a sec question. my fire phone is netlocked(german). is where still a netlock after install andoid?
again, sry for my bad english :/
thanks for help
munir

Step 6.
In windows device manger, remove all the fire phone devices listed.
Then run the KindleDivers.exe listed in step 7.
When you plug the phone back in windows "should" find and use the right drivers.

Thank you

For reference, the drivers have now moved. The following is an extract from the latest release notes:
* Windows USB drivers have been removed from the tools directory. You may access them from the SDK Manager under Extras.
Click to expand...
Click to collapse
They're installed with the package Extras / Kindle Fire USB Driver and will be located at: android-sdk\extras\amazon\kindle_fire_usb_driver
Other than that, instructions work fine, thanks

hello op, i got as far as step 4, when you mention add the link, mine shows new, everything after step 4 is different. can you please help?

Stuck on recovery
Solved it

Update: in the sdk manager, you must select 'kindle fire usb driver' under 'extras' now, and install that package. Then, you can find it in the sdk dir under sdk/extras/amazon/kindle_fire_usb_driver/KindleDrivers.exe

Windows 10 and fastboot driver | Nexus 5X

I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?

Let windows download the fastboot drivers from the network.
boot into fastboot, connect to pc
open up
win-r
devmgmt.msc
right click the 5x device and search network for drivers (or wherever that option is)
It'll come it with something like marshall london bootloader interface. That is fine, it works, it is for different phone that is also android based. The bootloader interface is the same.

Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the very same problem when I first received my 5X. I tried every damn think on to get Windows 10 to see the device, including all listed here and manually installing the drivers downloaded from Google and various other sites. Installed various Windows 10 packages. Even LG driver packages. I believe the issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer. I'm willing to bet it would work just fine on 7 (did on every machine I tried). Eventually adb and fastboot magically started working but I still could not use MTP. The ONLY thing that got it working was, strangely enough, a reinstall of Windows 10 (chose to kept files/documents) and then updating with the Anniversary Update). I know that is like the LEAST desirable option.
Windows 10 is really just not great for this sort of thing.

stmims1124 said:
The issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer.
Click to expand...
Click to collapse
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.

sfhub said:
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.
Click to expand...
Click to collapse
Yeah, that's exactly how it's worked every other android device I've owned too-only had issues with this device and this particular Windows 10 machine. This machine is configured to get drivers automatically, but for whatever reason I just couldn't get this to work. Of course, this was just my experience but there have defintiely been other folks out there with similar (maybe not exactly the same) problems. It was infuriating!
I can't really comment intelligently regarding what Google may have done to fix this. I'm shaking my head to hear that their drivers for Nexus devices is missing the fastboot USB ID's for a Nexus phone lol

Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....
---------- Post added at 10:45 PM ---------- Previous post was at 10:34 PM ----------
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....

Thanks to all, I've solved with Google -> Android Bootloader Interface and it seems it works.