Database Users

[Q] Windows ADB USB drivers?

After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?

beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable

When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2

download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium

i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium

You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.

Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.

driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?

bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.

Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)

reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.

Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.

bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.

I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?

Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC

Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app

I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app

Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.

ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse

rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.

[Q] ADB not showing device

Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.

akrabi said:
Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.
Click to expand...
Click to collapse
Did you enable usb debugging?

Also check that you have an option selected under Settings>Storage>USB Computer connection, not having either MTP or PTP selected there will also bork adb.

If you still can't get it to work, try Koush's universal drivers: Link

still not working...
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???

akrabi said:
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???
Click to expand...
Click to collapse
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.

taodan said:
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.
Click to expand...
Click to collapse
Ok, so I'm with my Nexus connected as an MTP device, with the driver from XDA installed (see attached image), USB Debugging enabled:
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
C:\>

Any advice???
Anyone has any advice??
I really have not idea what to do. Tried everything...
Thanks

Works on a different computer
I've connected the phone to my borther's PC and installed the drivers from the SDK. It worked without any problem.
I really can't figure out why it's not working on my laptop.

[Solved]
OK...
So as I said before I tried connecting when PTP is checked and when neither PTP nor MTP are checked and on both couldn't install the drivers properly (neither from xda nor from sdk).
What worked for me:
1. Uncheck both PTP & MTP
2. Device Manager -> Nexus 4 -> Update Driver Software -> Browse my computer for driver software
3. Now instead of browsing to the location I went to "Let me pick from a list..."
4. It should show a list of devices/manufacturers. Clicked "Show All Devices"
5. On the bottom right click "Have a disk"
6. Point to the android_winusb.inf file from Android SDK
7. Choose Android ADB Interface from the list
8. Let driver install
Click to expand...
Click to collapse
Hoped it will help someone.
Thanks to everyone that tried to help. :good:

[Q] USB Driver for Nexus Player?

I'm trying to do a bit of development for Android TV on my Nexus Player. I've got the player connected to my computer via USB, developer mode enabled, and USB debugging turned on. It shows up in device management but is unknown as there are no drivers installed for the device; and of course when I try and debug my app the player doesn't show up in the connected devices list. I have tried installing the Google USB Driver (Rev. 11) via the SDK manager; and unfortunately Asus's support is pretty useless. Anyone know where I can find the Windows drivers, or if there is some step I'm missing? Thanks!

Tried Koush ADB Drivers?
http://www.koushikdutta.com/post/universal-adb-driver
Cheers Rob.

halfluck said:
Tried Koush ADB Drivers?.
Click to expand...
Click to collapse
Unfortunately that didn't work.
I got it up and running by:
Selecting update driver
Browse my computer for driver software
Selecting let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting \android-sdk\extras\google\usb_driver\android_winusb.inf as the driver
Hope this helps anyone else who comes across this issue.

I just pasted the hardware ID's from device manager into the INF file of the normal ADB drivers and that worked fine.

Funkwheat said:
I just pasted the hardware ID's from device manager into the INF file of the normal ADB drivers and that worked fine.
Click to expand...
Click to collapse
How do you do that exactly?

Phoexyael16 said:
How do you do that exactly?
Click to expand...
Click to collapse
Goto the properties of the unknown device in your device manager, then goto Details and then Hardware ID's, then copy and paste those into the INF file in the same format the others are in.

Funkwheat said:
I just pasted the hardware ID's from device manager into the INF file of the normal ADB drivers and that worked fine.
Click to expand...
Click to collapse
How could you view the hardware ID's if you were not able to connect with the device?
DevinWatson said:
Unfortunately that didn't work.
I got it up and running by:
Selecting update driver
Browse my computer for driver software
Selecting let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting \-sdk\extras\google\usb_driver\_winusb.inf as the driver
Hope this helps anyone else who comes across this issue.
Click to expand...
Click to collapse
I get "error code 10" every time I try this.

Can't find my devicein adb devices list

after downloading platform tools I opened cmd and typed adb devices comand but my device was not listed in devices,USB Debugging was enabled and it was set to File Transfer

Did you install the Asus driver?

debdeep98 said:
Did you install the Asus driver?
Click to expand...
Click to collapse
yes

Does it appear in my computer or device manager? And a confirmation pops up on the device about key authorisation when using adb. Did you allow that? Also try the original cable.

QPST driver install...

Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5

Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$

L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now

L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update

JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port

fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that

L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar

fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.

Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?

Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.