Info: Nexus 5x Build NPF26F, v 7.1.1 , Developer option, OEM unlocking & USB debugging enabled, Windows 7 x64
Install USB drivers for Nexus 5x (latest_usb_driver_windows.zip)
Trouble is the inf file does NOT contain Hardware Id for this phone (Just purchased Nexus 5x 11/2016)
Windows Device Manager Hardware Id --> USB\VID_18D1&PID_4EE2&REV_0310
I have added this ID to the inf file (%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&REV_0310)
With this addition to the inf file, the driver is installed. Device manager reports the 5x as "SAMSUNG Android Phone", "Android ADB Interface
After doing this the 5x is still not recognized in by adb
Because of the Hardware Id has changed the driver/adb are hosed.
btw I have also install via Android Studio, Android SDK Manager method.
and used the zip file from here developer.android.com/studio/run/win-usb.html
Any thoughts
Thanks
Related
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
1. Open C:\WINDOWS\inf\wpdmtp.inf
2. Scroll down to around line 29
3. Note the following sections:
Code:
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
4. Edit those sections to this (simply add the GenericMTP line below the existing entry):
Code:
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
5. Save the file
6. Uninstall the old undetected MTP device (if it exists)
7. Plug in your Nexus 10
8. Auto-install the MTP Device
9. Win
Notes:
- Works with the Nexus 4 as well (possibly other Nexus devices?)
- Tested to work under Windows XP Professional x64 SP2
Credit: http://forum.xda-developers.com/showthread.php?t=1291293
XP and Nexus 10
The added lines in step 4 must match the hardware ID of your Nexus 10, which you can find by plugging it into your computer and checking the Nexus 10 properties in device manager. Mine, which I got last week, apparently has an earlier ID code. This method also works for 32-bit Windows XP, although MTP driver is unsigned.
Nexus 10 on Windows XP using MTP USB driver
Thanks for providing a simple solution for connecting Nexus 10 to a PC running under Windows XP using the MTP USB driver. However, it didn't work for me initially, because the necessary files, wpdmtp.inf and wdpusb.sys (and I assume others) were missing from my Win XP installation. After some searching, I discovered that the MTP USB drivers are installed along with Windows Media Player 11, so you need to install the Media Player 11 upgrade. Then make the changes to file wpdmtp.inf, as above, and all should go well.
By the way, when I contacted Google Play Tech Support by telephone to find out why my new Nexus 10 would not connect to my Windows XP machine, they were unable to help. Their Tech Support website was similarly unhelpful. Incredible!
I hope this forum helps other bewildered Nexus 10 owners.
cheers, Mike.
Does anyone know how to get the Venue 8 7840 working with adb? I can see the device as "Venue 8 7840" in the device manager under "Portable Devices" and using "Update Driver Software" says the drivers are up to date and lists "MTP USB Device". I have USB Debugging enabled and its plugged in via USB yet executing adb devices in Android Studio lists nothing. Any ideas?
Do you have the latest Intel Android USB Drivers?
Windows 10
Has anyone been able to install the latest Intel Android USB drivers with Windows 10 Pro? I get an Event error 441 error every time I try to install the drivers with the following event detail:
EventData
DeviceInstanceId USB\VID_413C&PID_B14B&MI_00\7&c5d474c&1&0000
LastDeviceInstanceId USB\VID_413C&PID_B14A\4BK00LXA01
ClassGuid {EEC5AD98-8080-425F-922A-DABF3DE3F69A}
LocationPath
MigrationRank 0xf000ffff0000f132
Present false
Status 0xc0000719
The Dell Venue does show up as in the Device Manager under Portable Devices as an MTP USB Device in Windows 10 but not as an Android Device.
I believe it did work correctly under Windows 8.1. In Windows 10, my Nexus 5, 7 (2013), and Nexus 10 show up as and ADB device, however, I understand these devices are not Intel processors.
I finally got the Dell Venue 7840 to show up in Windows 10 as an ADB device. In Device Manager, under the "View" menu, I selected "Show Hidden Devices". It then, for the first time, showed up with a question mark under "Other Devices." I removed and then reinstalled the same Intel USB drivers, rebooted, and the device now shows up in Device Manager as an "Intel Android Device" with a "Android ADB Interface." Most importantly, it shows up under the Command Prompt with the "ADB Device" command.
The official website does not have the USB driver. Anyone know where can I get it?
Thanks
I'm not sure which OS your running, I personally just use the generic drivers that come with the sdk on Linux and it works.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Grab and install Android Studio.
Once it's installed, use the SDK Manager to install the Google USB Drivers.
The driver should be located at/:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
Link to Google's USB driver page:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Extract zip and right-click on win-usb file and choose 'Install'. Then when you plug in your device, it should pick up ADB driver automatically. For Fastboot, bootloader mode, you'll need to go into Device Manger, find the 'Android' device, update driver/pick from list/Android/Android Bootloader Device.
Has worked on every Android device I have owned since it became available.
PhoenixPath said:
Link to Google's USB driver page:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Extract zip and right-click on win-usb file and choose 'Install'. Then when you plug in your device, it should pick up ADB driver automatically. For Fastboot, bootloader mode, you'll need to go into Device Manger, find the 'Android' device, update driver/pick from list/Android/Android Bootloader Device.
Has worked on every Android device I have owned since it became available.
Click to expand...
Click to collapse
Of note, you need to have the phone in fastboot mode and connected to the PC to update those drivers.
Is there any signed adb driver for GT2 Pro for Windows 10? I can see only WinUsb device "ADB Interface" after connection but empty adb devices list. On Windows 7 I can use legacy method but it doesn't work on W10. Thanks.
Go to Windows update and check for updates. It should show compatible adb driver. Manual adb driver install did not work for me. Also make sure to use up to date platform-tools.
I have no problems with windows 11 everything works, before I had win 10 and also no problems
I found a Driver setup file in Android 13 image. I have installed it and restarted the pc. After connecting the phone I can see signed Android Composite ADB Interface (made by Oppo) in the Device Manager but still after executing adb devices there is no device in the list.
OK, found the root cause, if somebody has a similar issue, it works with minimal adb fastboot v1.4.3 from here