Related
I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?
I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html
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!
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:
So i finally got around to setting up my laptop anew, and i ran into a little snag. I've installed the Motorola device manager 2.5.4.
My XT1562 is not correctly installed as such when connected... (yes, in PTP mode, adb enabled too)
The phone knows it is connected by USB and charges, it works fine on other PCs
Reinstalled Device Manager, nope
Trying different USB port didn't help
Tried different USB cable for the heck of it
Device Manager shows Android Device "Motorola ADB interface" and one unknown "MTP".
Device shows:
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
Using the auto update for drivers doesn't work. Manually Specifying the folder for the Motorola Device Manager doesn't work, i checked, there are no drivers lying around in there...
To manually specify the driver i would have to know exactly which device that thing is supposed to be. Hm actually let me check that on the other PC brb
EDIT:
Well, ive never even installed the motorola device manager on the pc (win7 x64) and it just works. Does have the ADB device as unknown in Device Manager.
If you are using Windows 10 or win 8.1 follow this guide to disable driver signature enforcement
https://www.youtube.com/watch?v=71YAIw7_-kg
For abd drivers
http://adbdriver.com/downloads/
Then reinstall Moto device manager
I've had them installed with signatures before (It was Win10 x64 before too) no problem. Did they mess that up? Thanks ill try it
EDIT
Didn't work. Rebooted with sigs off, reinstalled 2.5.4, no difference
EDIT2: There was no driver signature warning either
Riiight, after some tinkering (including a driver backup from w7 and restore to w10 solution) i figured out the actual problem. I've installed Windows 10 N, and the optional media pack is required for these drivers to work. Go figure.
New laptop (to me) Dell e7470.
Win7 x64
Phone: XT1575
Installed:
MotorolaDeviceManager_2.5.4
MotoHelper_2.1.32_Driver_5.4.0
Motorola_End_User_Driver_Installation_6.4.0_64bit
(also tried Kushik Dutta universal adb driver from 2013)
No adb driver detected or found when all the other drivers install fine when plugging in the phone
I've tried multiple usb cables, but this all works fine on my other computers.
If reboot to fastboot Motorola ADB driver is found and installed
But no adb driver when in rom
I've done this successfully for years, first android device many moons 2008ish
I dont know why this laptop is giving me troubles, or maybe i'm just gettin old and forgot a basic sequence or step to success.
Thanks for any ideas, its got to be something dumb.
You need to turn on usb debugging - developer options.
Minimal adb & fastboot installed too.
Dev.opt. - settings - infi about phone - tap few times compilation number. @eigerzoom
What for do you need adb if fastboot works?
MDM is all you need for drivers.
I have adb debugging enabled
I apparently need it for tethering, since that isn't working.
Works just fine on my other win7 asus laptop.
Any other ideas?
it feels like windows is missing something, but its hard to feel a computer
Run cmd and type:
adb devices
I've done that, thats how i test it.
its blank
actually i test it with 'adb usb' which gives error: no devices
File transfer works?
how would it transfer files if no device is found?
adb device shows up in device manager with an error
File transfer - mtp - not needed adb drivers. From notification bar you can change/enable when connected.
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Error in win dev manager - rpm - update driver - choose from installed.
Find & choose "adb device".
I'll test it soon, sorry
Also in developer settings you can choose usb configuration mode
if I cycle through them all
All drivers get recognized except in 'audio source' mode xt1575 no drivers install, and in 'rndis usb ethernet' no adb drivers install
I haven't Windows english version - I don't know names.
So I suggest:
Uninstall all Android programms(apps) & drivers from pc, restart pc.
Install and run MDM, when it finished connect Moto with debugging on, allow the connection on Moto(it should ask itself) .
Anyone else???
eigerzoom said:
Anyone else???
Click to expand...
Click to collapse
No try what @dzidexx suggested, before asking for someone else! Especially since his solution isn't hard to try out and see if it works!
I've done all that....obviously....
ANYONE ELSE ???
something tells me i have to install a stock rom to get the adb driver to install
and then it will work fine installing other roms after that
running LOS13 currently
i've run into this in the distant past on pre 2010 devices
anyone else with ideas?