Database Users

No ADB mode, driver issue?

I'm Italian, sorry for my English.
A few days ago I unlocked the bootloader via Toolkit, rooted and flashed the TWRP recovery _.
But I had hard difficulty:
After driver installed, I unlocked bootloader, enable debugging and then NOTHING!
In practice, the N7 was recognized by windows 7 64bit only in FastReboot mode ..
I tried in every way possible, deleted and reinstalled the driver 50 times, restored windows to a previous point, installed the drivers manually tried without toolkit, but how ADB just do not want to know.
For hours I was still with the bootloader unlocked but without root, until came to my rescue a friend with another notebook but same windows 7 64. Load the Toolkit, install the drivers and everything goes perfectly, I do everything in 5 minutes.
On my laptop there is always the issue driver ADB, in the future I still need my PC recognized the N7 in ADB, how can I do?

One thing that I think is not well understood is that there is no "Generic Class Driver" for ADB nor for fastboot...
... even though the very driver that works for one mode (or phone/tablet device) may be perfectly fine with a different device. The wire protocol for both fastboot and adb are extremely simplistic.
So, what that means is that if the Hardware ID used by the USB device endpoint registers on the bus with a different VendorID/ProductID, Windows will (correctly) not use a previously-installed ADB driver, or previously installed fastboot driver - even though they would probably work just fine.
Here is an example. The Nexus 7 registers the following Hardware ID when ADB debugging is turned on in the OS:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
On the other hand, if you are using TWRP, it's adbd daemon shows up on the PC as:
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
This means that you might need to install a different driver for using the ADB with the OS, and a different driver for ADB under TWRP - even though it is exactly the same hardware on the other end of the cable! In the absence of a generic class driver for a given USB endpoint, Windows tries to match drivers in it's local (& internet) database based on this VID/PID pair.
If you have a look at the [ADB/FB/APX Driver] Universal Naked Driver 0.72 thread - and download it and have a look at it's included "android_winusb.inf" file - you will see literally hundred of different VID/PID pairs in the driver's android_winusb.inf file in the installer package, corresponding to many hundreds of phones/tablets. Same driver with hundreds of devices listed as compatible.
In the past I recall taking the Google (SDK) USB driver, and manually editing into place matching VID/PID pairs for a HTC phone into the .inf file. It worked perfectly; I probably flashed that phone hundreds if not thousands of times using the Google Driver (My PC is a Windows 7 Pro x64 machine btw).
Anyhow, I have pulled this stunt twice now - once editing the .inf file for the Google Driver, and I did it once with the Universal Naked driver too. You can choose which driver you want to start with.
If you want to give it a roll, you can start with any of those three drivers:
- Google (SDK) USB driver
- XDA "Universal Naked" driver
- Asus Nexus 7 USB Driver (Look under Download)
Note that since you are using W7 x64, make sure that you add each new entries to the .inf file twice - once in the ".NTx86" section, and duplicated again in the ".NTamd64" section. When editing .INF files, make sure to use an editor which preserves simple text file formatting - use "notepad", not "wordpad"
If you want a reference for what values to use, see the bottom end of this post. You should see exactly these same values in your Device Manager, however.
Note that if you see the device show up in the Device Manager as being correctly identified and marked as "working normally" - but it doesn't work - you should probably remove that driver and re-install from a different driver package.
This would certainly be the case for any drivers you saw associating with VID/PID pairs that look like:
VID_18D1&PID_4E40 bootloader/fastboot
VID_18D1&PID_4E41 single adb
VID_18D1&PID_4E42*&MI_01 composite adb
VID_0955&PID_7330 avx mode
VID_18D1&PID_D001 adb in TWRP (maybe CWM too, I didn't check)
That's a lot to throw at you, especially with Italian <=> English in the mix.
Feel free to ask questions.
bftb0

Hello,
I tried to follow your advice but I have not solved.
I'll explain what I did, so you can correct me.
-Uninstalled previous drivers (from device manager, control panel)
-Restart the PC
-Modified the inf file. Package Asus Nexus 7 USB driver (ntx86 and NTamd64 sections) attach screenshots
-Linked N7 (usb debugging actived)
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
I tried to change also too XDA "Universal Naked" driver by following the same procedure.
I tried to create another account on my pc, but no ADB!
View attachment 1734997

Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD

stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Use "Google USB drivers" you get after you install from here http://developer.android.com/sdk/index.html
Its drivers work with 4.2.2
I got 4.2.2. rooted with ADB working now via only this and no other method

No problem with adb in 4.2.2... I tested yesterday (no need psw too...)
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse

Marco16V said:
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
Click to expand...
Click to collapse
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.

bftb0 said:
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
Click to expand...
Click to collapse
When the drivers are not installed and I connect to pc N7, is only recognized as a portable device, then later recognized as Google Nexus 7.
To install the drivers (modified as described) I click reinstall driver, then later recognized (if connected to pc in android mode, with usb debugging actived) as Android Device in another voice, ADB interface. But is not recognized by the toolkit under adb devices, and even when I try using cmd.
1-When I install the drivers. seem to be installed correctly.
2-Sorry, where can I find Hardware IDs in Device Manager? What is the difference between OS adb and TRWP adb?
3 - In other pc (with same N7, same cable, same driver, same toolkit) I had no problems. I tried to change only the USB port.
4-I uninstall the driver from device manager (uninstall voice) and ask to be also uninstalled software from the PC
In some Italian forum, I found people with the same problems.
Solved by formatting PC. I would not do that ...
Thanks for your help, sorry for my English and my limited skills

AW: No ADB mode, driver issue?
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sdk but I have not solved.
I use Android 4.2.1. I'm having problems with the update! I can not update OTA (N7 stuck under the impending reboot). I also tried to download the zip file to upgrade the memory and flash it from recovery but the installation is not completed (error 7 build.prop).
I also tried to flash the factory image 4.2.1 (keeping userdata) and start again. Nothing, same mistakes!
Too many problems!

Marco16V said:
2-Sorry, where can I find Hardware IDs in Device Manager?
Click to expand...
Click to collapse
(Note I attached some pictures below)
From the Device Manager:
- Select the Device in question by right-clicking. Choose "Properties"
- A window with three tabs will appear: General, Driver, and Details. Select Details
- The "Property" combo-box-selector has 20 or 30 items - the 2nd one in the list is Hardware Ids. I attached two pictures from Win7-Pro-x64 (below)
But note as I said before: You should NOT be seeing the ADB endpoint under "Portable Devices" - if ADB Debugging is turned on in the OS, you should see it under "Android Phone" or something similar. In any event, the hardware Ids will identify it exactly
Marco16V said:
What is the difference between OS adb and TRWP adb?
Click to expand...
Click to collapse
Well, as far as the behavior of the USB driver on the PC, almost nothing. Unfortunately - for better or for worse - both TeamWin (TWRP) and CWM authors put their ADB interface on the bus with the VID/PID pair of USB\VID_18D1&PID_D001, whereas the OS puts all its USB interfaces on 18D1/4Exx.
So, even if you get a driver installed for the OS "adb" mode (say by using the Google SDK USB driver or the Asus Nexus 7 driver), it won't work for the custom recovery... unless you fix up the driver installer package to have the matching VID/PID pairs (18D1/D001) in the .INF file for that driver.
I think folks find this confusing - they think, "wait, I have a ADB driver installed" - why does it not work?
OK, there are a couple more things to try (at least before I give up). Roughly they try to answer these questions:
Q1) Is this a toolkit issue, or a driver issue?
Q2) Is it a prior driver you installed that you are not observing that is causing the problem?
The first one (Q1) is easiest to diagnose: when your PC Device Manager indicates that a device is "working normally" - AND THE VID/PID ID MATCHES WHAT YOU SHOULD EXPECT FOR THE MODE THE TABLET IS IN (regular OS, recovery boot, fastboot mode), can you communicate with the device from the Windows command line? e.g.,
Code:
C:\foo> cd C:\blahblah\sdk-platform-tools-directory
C:\blahblah\sdk-platform-tools-directory> fastboot devices
or
C:\blahblah\sdk-platform-tools-directory> adb devices
If you can communicate with the tablet from the command line - your device ID will be printed by the above commands, then you don't have a driver problem at all - there is something screwy about the way your toolkit is installed.
OK, Q2 -
When Windows installs a driver, it caches it into a kind of database. I suppose it is possible that a prior driver installation might be causing trouble. You can observe - from the device manager - all the drivers that are installed - even for devices that are not currently connected to your computer.
This is done by setting the "devmgr_show_nonpresent_devices=1" environment variable. It can be done semi-permanently this way, or for a single invocation of the device manager this way..
See the third image attached (devmgr-all-devices.jpg ) - it is my computer in that "show all devices" mode. See all that rubbish in there? It's from other Android devices (HTC, Samsung, etc).
You can walk through each one of those - even the devices that are not currently attached - and inspect the VID/PID pair to see if they happen to match the values that you are expecting to see for the different operating modes on the Nexus 7. I'll leave it up to you whether you want to do this or not; it is a bit tedious. Just don't start deleting drivers willy-nilly if you don't know what they are associated with.
Marco16V said:
Thanks for your help, sorry for my English and my limited skills
Click to expand...
Click to collapse
I am understanding everything you are saying - and your english is far better than my italian
good luck!

[Q] USB Issues with Windows 8.1

put in a new SSD and got Windows 8.1, did a fresh install on a new hard-drive, everything's been working great, My nexus 4 has worked with with ADB./Fastboot and I've been able to transfer files to and from it in MTP mode. Been like that for about 4 days until about 3 hours ago, I had Windows Explorer crash, had to run Task Manager, end the process, and then manually restart explorer.exe My device was plugged in when this happened, and afterwards, I noticed that I could no longer see my Nexus 4 under the Devices & Drives section of "This Computer" (My Computer had a better ring to it lol) First I tried rebooting both my laptop and my Nexus 4, then I tried uninstalled the drivers, rebooting, re-installing, and then rebooting again. Did that like 4 times now, each time re-downloading the drivers, and doing an MD5 hash to create a Checksum, and checking them each time. Also to no avail. ADB shows my device serial number when i enter : ADB Devices, but says it's unauthorized, so if I try anything like: ADB Reboot Bootloader, it says Device is not authorized.
So ! I don't understand wtf is going on. Was working fine before. The drivers are up to date, I just flashed the Official OTA image, and was on the leaked image prior to that. Then earlier this evening I switched to the newest version of the Nexus 5 Port, and everything was still working fine, hadn't made any changes in a couple hours before this happened. When I install the drivers, It acts like it worked. Instead of saying "NEXUS 4" under Other Devices in my Device Manager, it says Composite ADB Interface under Android Devices and MTP under Portable Devices. Sometimes tho the MTP entry will still show the Yellow Exclamation Point. But goes away. Don't know whats up with that either.
Also, it wont let me install drivers unless I am in MTP mode, which Usually you can install them regardless (tho I never tried in Camera mode, I am just assuming about that one) Usually I install drivers without MTP or Camera modes checked, but now if I try it, it says that Windows Cant find the Drivers, even tho I am obviously browsing for them myself and selecting them. And just now I tried updating instead of re-installing them, and it keeps saying that Windows has determined they are the most up to date.
So I am out of I ideas. I even updated windows media player cause that's what fixed my issue on Day 1 of running Windows 8.1 when it wouldn't recognize it at all. So I don't know. Sorry for the long post but I wanted to make sure I got everything in there so hopefully someone can narrow down what the issue is. Cause I've been at it for 3 hours, haven't slept yet, my Nexus 5 gets here today, and I need to get this fixed before I sell it to my buddy. Its brand new, only 15 days old.*
Any thoughts ?*

First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
ADB Devices, but says it's unauthorized
Click to expand...
Click to collapse
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.

eksasol said:
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
Click to expand...
Click to collapse
ok I am gonna try that now. And as far as the part about my phone being unauthorized. I already knew about the notification that pops up, i was waiting for it to happen. Never did tho. Maybe it will happen after I do the rest of what you said. thanks, i will post my results in a min

no matter what i do, i cant get MTP working. When i uninstall the ADB entry in Device Manager it gives me the check-box option for removing drivers as well, but not on MTP. And now it wont even give me the option to uninstall, update, or anything at all, even tho I uninstalled it already so it should at least give me the option to install drivers. Even tho it's showing up in Device Manager as a Portable device, if I look in Printers and Devices, it shows up as unspecified device. Disabled USB Debugging, and all that. it says its working but it wont show up in My Computer>Devices and Drives still. For some reason ever once in awhile it will pop up with the Yellow Exclamation Point tho, only for a brief second tho. other then that, its shows it like it's running correctly. Also, nothing pops up saying that windows is installing drivers when i plug it in. Which in Win 7, XP, etc, it always did. Does this not happen in Windows 8.1 ?
Also, under Driver Details, which is the only option it lets me click on MTP, it says the drivers are from 2006 lol
Update - Just reinstalled the drivers for ADB and enabled USB Debugging, and everything is still saying its working even tho its not. But when I take my phone out of MTP mode it shows up in device manager under "Other Devices" as Nexus4, with a Yellow Exclamation, and it gives me the option to update drivers, so i tried, but it says Windows Can't find my driver. This is very frustrating.

Had this problem aswell, which was caused by the N version of Windows 8 versions.
These versions dont have Windows Media Player istalled, which is needed for MTP to work.
So to fix your problem you need to download that latest Windows Media Player (WMP) from microsoft and install that.

I dont have the N version, I have WMP installed, i mentioend your fix in the OP. Had to update it, and it worked. It was working fine for the last few days, then it stopped working suddenly

double post, sorry. dont know why that happened.

Vouch. Since I use win8.1 (no n version) Mtp doesnt work. I tried all known drivers, disabled driver signature and so on. The only working combination for me is Usb Debugging + PTP. Then I use file manager to cut the files. Airdroid would be an alternative as well.

update - SOLVED * Kind of.....I say kind of cause I still don't know what caused it but apparently Flashing to the Nexus 5 Port fixed the issue lol. I am assuming something pertaining to the way USB connectivity is controlled by Android got corrupted, and a fresh install was in order. Whatever it was, it worked and i am back in business. thanks to all those who attempted to help.
Sent From My Nexus 4 via XDA Premium 4

Cannot install Shield drivers

I have downloaded the proper set of shield drivers.
I have set the shield to enable developer and debugging is on.
When I connect the shield to my Win 7 PC it shows up as an unknown device.
Now when I go to the device manager and try to update my driver for said device with my disc, Windows reports that the latest driver is installed.
I've also tried to right click on the .inf file but it will not install.
It seems that my problem is that the Shield is no showing up as something other than an unknown device.
Suggestions please
TNX

Having the same issue here; windows 10 keeps forcefully installing the "generic drivers". When I try to right click and update, it says the generic drivers are the best option (they're not!). Unfortunately the generic drivers wont show up on adb devices also..

did any1 resolve this

Win7 ADB not recognising phone

I downloaded latest ADB/Fastboot package to my Win 7 PC.
I installed the Zadig drivers exec to load drivers (as seen in another thread).
Enabled USB debug
Connected phone
ADB devices ... doesn't show phone
Phone shows ADB icon in task bar
In device manager I can see libusbK USB Devices .. ADB Interface (Interface 1) .. when I plug the phone in
I have revoked previous computers and rebooted both PC and phone with no changes
... now I am a bit lost

* Bump * .. I can't do much without ADB ... could someone at least point me to the correct drivers - what I have downloaded from Zadig do't seem to work.

I'm currently having the same problem of not being detected when I type in "ADB devices" in Windows 10 after an auto-update which can't be stopped screwed up my drivers. I found this thread while searching for an answer myself. I tried reinstalling all Qualcomm and fastboot drivers and even though my phone can be detected in Windows again (after manually selecting "MTP USB Device" as a driver update for the A7 in the device manager) I still get nothing when I type in ADB devices. Though I tried flashing something to it anyway (same TWRP recovery I already have since the file was already there) and it seemed to work? Have you tried flashing something to your phone anyway?

USB driver update failed

Hi
I am a new user for nexus 6p, For the first time I connected my device to Computer running windows 10 updated. My laptop didn't detect the usb and the driver is not installed properly, I tried downloading the latest usb driver but it didnt help , While searching for the driver folder it throws
Windows was unable to install your unkown drive

You can get the USB drivers straight from Google and try to uninstall/reinstall or download Wugfresh's NRT. There is very good driver installation tool and test to confirm you get both USB and fastboot drivers installed properly. Just follow the "Full Driver Installation Guide"

Tonyjaqs92 said:
Hi
I am a new user for nexus 6p, For the first time I connected my device to Computer running windows 10 updated. My laptop didn't detect the usb and the driver is not installed properly, I tried downloading the latest usb driver but it didnt help , While searching for the driver folder it throws
Windows was unable to install your unkown drive
Click to expand...
Click to collapse
Hi... Do you have ADB enabled in developer options? If you don't have developer options enabled, go in: settings>about phone and type 7 times on the build number, then go back in settings > developer options and enable "android debugging".
Plug your N6 on your computer, check your phone screen and allow press ok when it asks to "allow USB debugging".
Does it change something? Is your N6 recognized in device manager? Does the driver updates?

...
So My puter recognizes my phone fine....
Pop opened the configuration and General tab says:
This device is not configured correctly. (Code 1)
A service installation section in this INF is invalid.
To find a driver for this device, click Update Driver.
I try and update the driver using the "Let the puter search" feature and it finds one and tells me:
Windows encountered a problem installing the driver software for your device.
Windows found driver software for your device but encountered an error while attempting to install it.
MPE Device
A service installation section in this INF is invalid.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software.
This is all AFTER I downloaded the latest Google USB drivers and unzipped them.
Phone is set to MTP mode and debugging mode is unlocked and usb debugging is on.
No Go.