Related
I am just getting started in Android development, and am trying to get Eclipse (running on Windows 7) to recognise my phone so that I can use it for debugging. However, my phone does not seem to be recongised by Eclipse or by running "adb devices" from a command line.
Here's what I've tried:
I've tried both MTP (media device) and PTP (camera) transfer modes (similar questions on Stack Overflow have been resolved by using PTP).
I've ensured that USB debugging is turned on in my phone's settings.
I've manually installed a driver in Device Manager, by choosing "Update Driver Software" and selecting the .inf file in sdk\extras\google\usb_driver (which I had to modify by hand to include my device).
I've tried a Nexus 4 phone, a Nexus 7 tablet, and a Motorola Moto G phone. Behaviour is identical for all three devices.
I've tried the "Universal ADB driver", in case it behaves differently to the Google driver, but it doesn't behave any differently.
I've rebooted, I've reinstalled drivers, I've tried adb kill-server followed by adb start-server, etc.
No matter what combinations of the above I try, "adb devices" lists nothing. When I look in the Windows Device Manager, I can see "Android Composite ADB Interface" listed under the "Android Device" node, so I believe I have installed the driver correctly. I am logged in as an Administrator, so it's not a permissions thing either. I've tried every answer to every single similar question on Stack Overflow, but nothing works. I've been pulling my hair out all day and am close to running out of hair... any ideas appreciated.
EDIT: It just occurred to me what could be causing this. I am running 64-bit Windows 7, but 32-bit Java. Because I have 32-bit Java installed on my PC, I installed the 32-bit SDK. Would that explain this behaviour? Should I be running 64-bit Java? The only reason why I didn't is because 32-bit Java is installed by my company's group policy...
EDIT2: I have now noticed that when I plug an Android device in, and look at its Device ID in Device Manager, the device ID does not end in "&MI_01". When I plug the device into another Windows 7 PC, the device ID does end in "&MI_01". I believe this is why "adb devices" is not able to detect the device. Any idea why one PC would see a different device ID to another, with the only difference being the "&MI_01"?
Did you install your phone USB-driver?
and can you check it on device manager is installed or not? you can download your usb driver from yur phone company website.
After you install your phone usb driver , I think the problem is solved
I think the main reason is because the computer does not recognize your phone as below 1 device used to debug code, even usb device.
You can try to do the following:
- Turn up the window update
- Uninstall driver for usb connection from your phone to your computer
- Go to the homepage of the mobile device, download driver for usb connection to the computer and then reinstall the driver
Try Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices.
Download
After downloading extract .rar file into a folder.
Go to Device Manager, right click on Android phone and click to update driver. On next screen , give path of extracted folder and install it.
You can install with msi file also. Download .msi
Finally found the answer. I was missing a file called usb.inf from C:\Windows\inf. Not sure how on earth files just go missing from yours Windows directory...
For several weeks, I was able to connect my Nexus 7 2 to my computer running Windows 7, and Eclipse would recognize it, allowing me to run apps on it. The device also showed up when I ran the adb devices command. Every time I plugged the Nexus 7 into the computer, the tablet asked if I wanted to allow USB debugging at that time. (Oddly, it never asked me whether I wanted to always allow it from that computer, but I didn't care.)
I recently updated the tablet to Android 4.4.2. I also updated the Android SDKs through the Android SDK manager. Now, when I plug the tablet in, I do not get prompt about USB debugging on the tablet, and neither Eclipse nor adb can see that it is there.
Here is a list of things I tried to do, gathering ideas from various forums around the web.
Re-download the Asus drivers for the Nexus 7 and update the driver. However, Windows does not even recognize this as the right drivers for this device.
Turn USB Debugging off and on on the tablet, and also revoke all USB debugging permissions.
Change the connection mode from media device to camera
Switch the runtime from Dalvik to ART
Type adb kill-server followed by adb start-server in the command line
Delete eclipse and all the Android SDK and download them all over again
None of this worked. Any other ideas on what to try?
It turns out that the Nexus 7 definitely needs the Google USB Driver. Finding, downloading, and installing this driver worked perfectly.
Because Google's Android OEM drivers page does not include the Nexus 7 in its list of devices that need the Google USB driver, I had been trying the driver from Asus, which did not work. I did not try the Google USB driver because for some reason my SDK manager said it had downloaded the driver, but the driver was not to be found.
Finally I found I could download the Google USB driver from this page, which clarifies that all Google Nexus devices need this driver. Now I have successfully re-connected the tablet to ADB.
I submitted a documentation bug report to Google here in hopes that the OEM drivers page can be updated to reflect that all Google Nexus devices need the Google USB driver.
Nexus 7 tablet with Android 4.4.4. Settings > Storage > USB Computer Condition.
Two checkboxes: MTP and PTP. Uncheck both.
With your phone disconnected
In windows explorer - right click computer, go to manage, in computer management find and uinstall device driver (under Android device)
Download new drivers from http://developer.android.com/sdk/win-usb.html#top
Connect the phone, windows will try to install new drivers, install drivers manually with drivers downloaded as above
The above worked for me
For me, after updating to Android 4.4.2, it was critical that I connected the device as a Camera (PTP) rather than as a Media Device (MTP). Previously, before the update, I was able to connect as a Media Device (MTP).
The problem is that you have not all needed drivers (PC can recognise your phone like usb device but debugging would not work). I solved this problem in Android 4.4.4 by uncheking all items (MTP, PTP, UMS) from menu: storage->USB computer connections and than tick 'Media device(MTP). Now all works fine.
thank you Arthur, I found Nexus 7 tab not working even after unchecking or checking. Problem solved by unchecking USB Debugging (under developer options).. settings>Developer option> USB debugging. then check (put tick the MTP device):.storage->USB computer connections and than tick 'Media device(MTP)
Complete checklist:
Enable debugging onto the device
Select USB Connection as PTP (camera)
Install the driver from http://developer.android.com/sdk/win-usb.html
Before you try anything, make sure you update your Build related tools using your Android SDK Manager. Your adb might be outdated.
Android Studio 0.3.6
Fedora 18 3.11.7-100.fc18.x86_64
Nexus 5 Kitkat
Hello,
I have been using my Samsung Galaxy Tab 3 7.0 running Android 4.1.2 everything works fine with adb.
However, I have just bought a new Nexus 5 device, and when I do the following command adb devices it doesn't show my Nexus 5.
Under Android SDK Manager | Extras | Google USB Driver | status "Not compatiable with Linux"
Because I am running Fedora 18 if I need drivers what drivers for the USB do I need?
Because the Samsung works fine and I can deploy and run my apps, I think my setup is correct. So I am wondering if there is something wrong with my Nexus 5.
I have tried the following:
adb kill-server
adb start-server
Setting the Nexus 5 Camera PTP and media device MTP didn't work.
Many thanks for any suggestions,
I had a similar problem with my Nexus 4(Android version 4.4.2), it wasn't listed in adb devices.
Make sure USB debugging is enabled from device, and do the following on your PC:
Update Android SDK (Google USB Driver)
From PC Control Panel, System -> Device manager -> Right click Nexus 4 -> Update driver.
Set android-sdk-folder\extras\google\usb_driver as path to search, include subfolders checked.
If windows tells you that the driver is up to date, just uninstall the driver (right click on nexu4 -> uninstall driver) and start from step 2 again.
After that, open a cmd and type adb kill-server and then a adb devices, now it will include your device.
https://developer.android.com/studio/run/oem-usb.html
Follow these steps,
Enable Developer options in your device. To enable the developer mode, Settings->About phone, tap Build number option 7 times continuously
Go to Settings-> Developer options and Turn on USB debugging
Make sure you reconnected the device via USB and grant permission on the dialog that appears.
From the above steps it didn't work try this step, Go to Settings->Security and turn on Unknown Sources
What you need to do is this:
Settings | About Phone
Scroll to the bottom to build number.
Tap on build number about 7 times. Each time you will get a popup message saying you are x steps away from being a developer
When you get to the final step you will get a message saying now you are a developer
Go back into settings and you will see a new setting Developer options there you will see a lot of options for developers. Enable USB debugging
Re-connect you phone to the usb, and you should see you device under adb devices.
I hope this answer helps someone else.
This simple steps worked for me, I debug on my Nexus 5 and 5X devices on Windows 8.1.
The steps to follow are these:
1) Enable from Developers Options the Debug USB Mode
2) Unplug the device from the computer
3.1) Go to Settings → Storage, in the ActionBar, click the option menu and choose USB computer connection.
3.2) If you didn't find the 3.1) option then go to Settings → Developers Options → Select USB Configuration.
4) Select Camera (PTP) connection.
5) Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection, or something like that.
6) If it doesn't work try to toggle the Debug USB Mode in the Developers Options
Finally, you should see it now in the DDMS and voilà.
My windows solution:
Go here and download and unzip to an easy location:
http://developer.android.com/sdk/win-usb.html#top
Right click 'My Computer' or 'Computer'
Select properties
Select Device manager
Look for your device. It should have a yellow mark above it.
Click 'update driver software'.
select browse my computer for driver software.
select the usb_driver folder you saved earlier.
install it
and wala. magic.
For those who are still frustrated, if you are using the experimental ART runtime, try switching back to dalvik (in developer options on device)
Here is simple solution for Windows 7 and Nexus 5 on Android 5.
Download the Nexus 5 Drivers from http://androidhost.org/jelry
Extract the zip contents and place all files in a single folder on your desktop.
Connect your device to your computer.
Launch the Device Manager on your PC.
Now you should see the Nexus 5 listed in the hardware list.
Right-click the ‘Nexus 5′ line and then click on Update Driver Software.
Next, click the ‘browse my computer’ option.
In the new window click on ‘Browse…’ button.
Go to folder unzipped at step 2. Select the folder where you extract the USB Drivers. Click Next. – make sure to tick the subfolder box too.
Now, the Windows installer will search for Nexus 5 drivers, click Install when asked for permission.
Wait for the process to complete and then check the Device Manager list to confirm that the installation was successful.
Original: http://www.android.gs/download-and-install-google-nexus-5-usb-drivers-adb-fastboot/
Note: do not forget to enable USB debugging on your device :)
Something nobody has mentioned yet:
Some cables do NOT support data. I was sitting here wondering why my Nexus 5 was refusing to show up on OSX. It turned out I was using a cable that didn't support data.
I swapped to a different cable which did support it, and suddenly I was able to use USB debugging.
If anyone is trying to connect Nexus 5 to a formatted Windows XP then follow these steps:
Download and install media transfer protocol porting kit:
MTP porting kit
Download and install WMFDistributable-11 for XP:
WMFDist-11 XP
Download and install LG United Mobile Driver v3.10.1:
stackoverflow is not allowing to share more than 2 links, please google this.
Connect your device.
Go to Device Management
Right click on Nexus 5 and click Update Driver
Select Yes this time only
Select Install Software Automatically
Wait for sometime.. and enjoy transferring files
ADB and driver versions matter. The newer the device, the lower the chances of an older version ADB to work correctly.
Apps using their own ADB copy need to be updated or at least have their ADB updated manually.
When installing Helium / Carbon for instance, it uses an old / incomplete ADB. Newer devices might not link to the ADB server for this very reason.
What I'm writing here should work for any future devices on Windows and possibly *nix OSes.
First the systems must be prepared.
on Android:
activate developer mode, either from an app (like Helium, when prompted) or by accessing the about phone section, taping build number until the developer mode unlocks
in developer settings enable USB debugging
in security settings allow unknown sources
(when connected with USB cable) set USB connectivity to PTP mode (camera device, if so labeled)
in Windows:
uninstall older USB driver (with file removal) if there is one, but only when the device is connected and in developer mode, otherwise
that particular device won't be listed
install latest USB driver after the device has been plugged in and developer mode is active, the device will be listed as unknown or other in Device Manager; the drivers can be downloaded separately from Google Android support site, these are the same as vendor drivers, with only fewer ID's in inf file making the driver not being recognized for all Android devices
if the driver does not recognise the device, no problem, install it generically: Manual Install > Show All Devices > Have Disk > pick inf location of the Android USB driver and from the list select Android ADB Interface; there's not need to edit the inf by adding hardware ids, the end result is the same
each of the modes, PTP and MTP will have their own driver entry, so if the device asks for MTP, the same driver installation procedure must be followed, again
Once these steps are/were previously done correctly, adb must be tested.
If Android SDK was installed previously, open a command prompt where adb.exe is
and test the listing of the device.
adb start-server
IMPORTANT NOTE: This command will prompt the device to allow the communication between the computer it's been linked to on the first run. The prompt will also list an RSA key specific to the PC in question. Without this prompt on start-server, ADB will NOT work! Nor will any application relying on ADB.
adb devices
Must list the device(s). If the list is empty, and most likely the RSA prompt did not occur, then no communication will work. If the list is empty the current ADB (and SDK) must be updated or installed fresh (in the case of apps bringing in their own ADB runtime, like Helium / Carbon).
In the case of applications that do bring their own ADB, if the version is old, and these apps insist in using it instead of the SDK one, these files need to be replaced with the latest ones from Android SDK. Plain and simple copy & paste.
As for Android SDK, the only required packages to be installed are SDK Tools and Platform-tools. There, ADB.exe will need some support libraries, on Windows these files are AdbWinApi.dll and AdbWinUsbApi.dll. After all is done, the SDK can be uninstalled from SDK Manager while being able to retain the ADB tool if this is the only runtime used, depending on the case in question.
After doing all steps like enable debug, ... I had to put a sim card and reboot the phone
Solution for Windows 7 and Nexus 5 (should be applicable for any Nexus device):
I figured out that my system was installing the Nexus 5 default driver for windows automatically the moment I was connecting my Nexus 5 to my system through USB. So uninstalling the default driver was in vain and it gets installed automatically anyways.Moreover if you uninstall the default driver, you won't be able to locate Nexus 5 under Devices in Computer Management. So here is what i did and worked for me!
Computer-->right Click-->Manage-->Device Manager-->Portable Device-->Nexus 5-->Update Driver Software
Choose 'Browse my computer for driver software'
1.Make sure to give this location: %APPDATA%\Local\Android\sdk\extras\google\usb_driver
Click Next and you are done.
I have suffered the same issue and was able to solve it by simply changing on my Android device (Nexus 5X) in Developer options > Select USB Configuration to RNDIS (USB Ethernet)
For those trying to connect their android phone in adb with no luck and have tried every USB configuration (MTP, PTP, RNDIS). It is worthing noting that in my case with my Nexus 5X on Windows 7 I successfully connected the phone to adb only by choosing the Charging USB Configuration. With any other configuration (MTP, PTP, ...) it doesn't work.
USB Driver: Google USB Driver v11
ADB Version: Android Debug Bridge version 1.0.39
Madx's answer is a strong hint. Now I can make MTP work for my Ubuntu 20 and Nexus 5X (Android 8) device. MTP is an easy solution in Windows for smartphone users. However, to me and many Ubuntu/Linux users, current Ubuntu/Linux MTP tools "LOOK" messy and unstable for Android devices, e.g. No folder is shown for android phone in Nautilus.
Delving deeper I find it might be a security enhancement done by GOOGLE in the Android device/phone side. Direct internal data access remains a privilege for the developers. And one needs to set/reset MTP as a developer for Android device in order to make Ubuntu MTP tools work. There is nothing wrong with Ubuntu/Linux MTP tools.
The steps for MTP data access are an extension to Madx's answer:
(For Android device) Enable from Developers Options the Debug USB Mode.
Unplug the device from the computer.
3.1) Go to Settings → Storage, in the ActionBar, click the option menu and choose USB computer connection.
3.2) If you didn't find the 3.1) option then go to Settings → Developers Options → Select USB Configuration.
4.1) Select MTP connection.
4.2) Select Camera (PTP) connection.
4.3) Select MTP connection again. (This refreshs GOOGLE MTP protocol stack, I guess)
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection, or something like that.
If it doesn't work try to toggle the Debug USB Mode in the Developers Options
And now file folders are shown up for N5X device in Nautilus.
Are these too much? There might be a bug in Android MTP implementation, and 4.2) & 4.3) are steps to WAKE Up Android MTP stack:-)
As a kind reminder, Windows and FTP are the last resorts for MTP.
Try executing :
sudo ./adb kill-server
sudo ./adb start-server
sudo ./adb devices
In my case:
The phone was connected as a media device.
Clicked on that message and got a menu. "USB computer connection"
In that menu chose to connect it as a camera (for devices that do not support MTP)
And then it worked.
Oh boy, I spent 3 hours for this simple thing and tried combination of above instructions.If it doesnt work for you, just try several combinations of above instructions and it will. I am on windows 7 and nexus 5. Issue I had was when I try to install driver from the google usb folder, windows 7 fails to install. Here are my steps:
-first uninstall all nexus drivers on windows 7. connect with USB cable, go to device manager and uninstall the driver; unplug the cable and repeat until no drivers are found and nexus shows up under "other devices" in device manager. I also configured nexus device as camera (PTP)
-follow #Dharani Kumar instructions. They make appropriate configuration changes for nexus device
-follow #Harshit Rathi instructions. They will ensure eclipse can show the device when windows detects the device
-unplug and replug the USB cable after a minute. Now you should see a pop up on nexus device. click it so that windows 7 will allow installing the driver from your local system. if you dont see this, restart your device or pc
-follow #Rick's instructions.you can download USB driver as listed by #jimbob
If you still have a problem, re read this entire thread and go from there (I spent hours on other web sites; those bits and pieces didnt help)
Go here and download and unzip to an easy location:
http://developer.android.com/sdk/win-usb.html#top
Download and install
I had the same problem, USB debugging enabled, device showing up in windows but I never got the question about RSA fingerprint when I connected my Nexus (6) device, nor did it show up in the Android Device Manager.
BUT
In the windows device manager I did have an entry saying it was an android device and Composite ADB interface etc. Still didn't work.
When I tried the previous tips about manually updating the drivers, Windows 8.1 just responded that "Windows has determined that the driver software for your device is up to date" this was not true. Looking at the driver details I saw that the driver was published by "ClockworkMod". I realized this must be because I had installed the Helium app sometime last year. So I uninstalled that, still had the same problem. Checked again, this time it was indeed google drivers, but version 7 published in 2012 (and not version 11 published 2014). I uninstalled these AS WELL and then tried the trick of reinstalling the driver from the SDK located in:
%localappdata%\Android\sdk\extras\google\usb_driver
Now when I replugged my device it finally works and can be debugged with Android Studio.
Indeed a driver problem.
Answer by Rick and MadX is the right way to do the steps (Thumbs Up for the answer)
In my case I am using
Akcess USB Type C Data Sync Cable For Nexus 5x, 5P - White
As Nexus 5x do not supply type C to usb cable I purchased it from some vendor.
Having the same issue. What I am doing stupidly is:-
I am connecting the cable in wrong way. After I reconnect it from upside down its working for me.
I might think that some of the Cables do not support debuggable. But its in my case.
This(Image) is my case the Type C should be as USB side symbol. A stupid solution, but work for me
Following on from ADB not recognising Nexus 4 under Windows 7 I am having problems getting the Eclipse android development environment to recognise my new Nexus 4. My privious Nexus S had no problems.
I believe I have followed all the advice in this previous post but am still stuck.
Can anybody who has succeeded getting the nexus 4 available for android development on windows 7, tell me what their driver detail are for the "Android Composite ABD Interface"? Mine say:
* Driver Provider: "Google Inc"
* Driver Date: 27/08/12
* Driver Version: 7.0.0.1
When my phone storage is set to either PTP or MTP, I still can't see it through the eclipse "android virtual device manager".
When set to PTP, if I run the "adb devices" command described in the linked article, I do get an entry appearing in the dos box, but nothing in the "android virtual device manager" in eclipse.
The solution is to connect your device with PTP instead of MTP and, it works.
Connected devices are not visible in AVD manager. AVD manager is for emulators.
To show connected devices, you use only ADB with this command :
adb devices
This is great step by step tutor for it:
http://androidsecurity.wordpress.com/2013/06/05/install-google-nexus-4-adb-usb-drivers-on-windows-android-studio/
Uninstall the device driver completely from Windows and re-install it.
If you dont see the device in the Devices lists:
First, you need to make sure USB debugging is enabled on your device. Settings->DeveloperOptions: Turn on debugging and enable USB debugging. Ideally, you will install the USB drivers from google, and it will work fine: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver. There are some cases that new installation may mess up the device connection. You may want to try these:
It may lost the connection, so you can try:
adb kill-server
adb start-server
adb devices
Updating to new tools may mess up the settings:
Go to Storage Options and try to set as Media(MTP) or Camera(PTP) connection. Swtiching to one of them will help
Revoke authorizations, disable usb debugging and then enable
Your Nexus 4 isn't a virtual device, so won't show in Virtual Devices Manager.
If you open the Devices view, then you should see your Nexus 4 listed, and when you run your app it should prompt for running it on as physical or virtual device.
Problem:
Asus Nexus 7 not recognized by adb when correctly installed and connected
Setup:
Asus Nexus 7 tablet
Windows 7 64 bit OS
Steps taken:
Installed 64 bit Java JDK (http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
Installed Android SDK (http://developer.android.com/sdk/index.html)
Installed Google USB driver (http://developer.android.com/tools/extras/oem-usb.html)
Set tablet to USB debugging mode
In the Windows Device Manager, the Nexus is recognized as an Android Device via Android Composite ADB Interface. The device status indicates it is connected and working properly, running driver version 7.0.0.1 (8/27/12 update) from Google.
However, when I run adb devices at the command prompt (in the sdk/platform-tools directory), the Nexus does not come up as an attached device - the list is empty.
Does anyone have any insight on what the problem might be? I have tried uninstalling and reinstalling all drivers, restarting the computer each time. I have tried a variety of usb ports and cables, as well as switching between MTP and PTP connections with no success.
Hey I found a solution to this via mkh at
https://groups.google.com/forum/?fromgroups=#!topic/android-developers/0-RzE0v-G3k
Try this (as quoted from the above source)
When the Nexus 7 is plugged in there is a persistent notification that
indicates "CONNECT AS / Media Device (MTP)". In this state adb devices
will not show the Nexus. Not exactly obvious why, but I you select the
second option "Camera (PTP)" the device is available for debugging.
This choice is persistent, and I'm guessing that with a band new
device it will connect as MTP until told otherwise
An important note about Nexus 7: There is no option for USB debugging readily available in the device Settings for 4.2.
http://forum.xda-developers.com/showthread.php?t=1989777
"Open Settings, then go to phone details (where u can see kernel, Android-version etc) then just tap your Build number 'JOP40C' 7 times!"
This sounds ludicrous, but after I did this, the developer options unlocked and I was able to see my nexus 7 in Eclipse (mac, Mountain Lion) for debugging.
In my case when I got an empty list using "adb devices" I found that the device manager showed the Nexus 7 tablet under 'other devices' with that dreaded yellow exclamation point indicating that the driver was not installed correctly. Why Windows recognized part of the tablet file system, I don't know. In any case I manually updated the driver to the google usb driver in android-sdks\extras\google.
Then adb gave me the following:
C:\Users\Brian\android-sdks\platform-tools>adb devices
List of devices attached
015d25785b601611 device
instead of a blank. I hope this doesn't mess anything else up but I can now talk to the device.
Had the same issue, Windows 7 32-bit; visited the site that Graham linked in his answer but wasn't happy running PTP (though it did work). Following the steps on another post belonging to the same thread sorted it (I can now connect as MTP); again, a direct quote from https://groups.google.com/forum/?fromgroups=#!topic/android-developers/0-RzE0v-G3k (thanks sfoucher!):
uninstall the driver in the device manager with option "delete the driver software for this device"
reconnect the Nexus tablet
let windows install a default driver which will be inadequate
uninstall again the device in the device manager with the option "delete the driver software for this device"
let windows try to find the driver, this process will fail
go back to the device manager and right click the failed device and update driver
choose the driver location in the android sdk directory (android/extra/google/usb_driver)
I should add that after step 5 I had Nexus 7 listed under Portable devices looking OK but had another Nexus 7 entry under Other Devices to which I applied the driver. My Nexus 7 now appears OK in ADB and Eclipse. In device manager I have Nexus 7 under Portable Devices and Android Composite ADB Interface under Android Device.
I too had the same issue on windows 7 64 bit.
Following thing solved my problem.
Connect the Nexus 7 and tap on Settings-About Tablet-Build version 7 times.!
This will install basic driver for windows
Now, tap on connected as media device(MTP) icon, but you will need to change it as Camera device then
Go to device manager on windows, select Nexus 7 and then update the drivers using the driver avaliable on this link http://developer.android.com/sdk/win-usb.html - This will install a driver ( You can use it with this one)
Now tap on Connected as Camera device and change it to media device - This will install one more driver and you are ready to go.!
i was having the same problem and my solution was to download the device driver from Asus. Below is the link.
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
That's how I solved this issue with a different device.
Download the drivers, unzip in a folder https://developer.android.com/sdk/win-usb.html#top
With your tablet plugged, go to System -> Device admin -> Android Device -> Properties -> Details -> Hardware ID
You'll find something like USB/VID_XXXX&PID_YYYY, we will need those XXXX and YYYY later.
Go to the folder you put your drivers and edit the file android_winusb.inf manually.
Add this:
;MY PHONE
%SingleBootLoaderInterface% = USB_Install, USB\VID_XXXX&PID_YYYY
%CompositeAdbInterface% = USB_Install, USB\VID_XXXX&PID_YYYY&MI_01
Save the file
Go back to device manager and try to update the driver with this one. (Driver -> Update driver -> Search in my computer -> Choose from a list -> Use disk).
That worked for me on a Quechua Phone.
What worked for me is downloading the USB driver from the ASUS website:
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
(you have to select the OS, which sometimes doesn't work, e.g. on the link Google returns when searching for "nexus 7 driver"). In that case, click on "Drivers and Download" and search for "Nexus 7". That gets me a page with a working OS selection.
I am using Windows 8 and the only thing that worked for me was the Nexus Root Toolkit 1.6.3 where I done the Full driver configuration Guide ... but I didn't follow the instructions there I went to step 2 and only installed the Signed drivers.
http://forum.xda-developers.com/showthread.php?t=1766475
I had the same problem. For me the newer version of adb is required to connect to the Nexus 7 i.e. to have the Nexus 7 ask me to "Allow USB debugging?"
In short:
Android Debug Bridge version 1.0.31 - Works
Android Debug Bridge version 1.0.29 - Does not work
Download the latest android usb drivers from
http://developer.android.com/sdk/win-usb.html#top
And then manually install these driver using Device Manager. Hope it helps!
I had faced two issues:
Nexus 7 not visible to eclipse/adb when connected over usb on windows 7 64-bit using latest Jelly Bean sdk
It was not showing in the 'My Computer' >> 'Portable Devices' list.
Ultimately, I found that it is an issue with the driver. Steps to resolve the issue - Open Device Manager, Uninstall the current driver (along with delete option set to yes), disconnect the device, reconnect it again, let windows install the default driver it wants, and then installed the google sdk driver again. It worked this time.
Above tells me that there is some issue with default driver and therefore, you have to delete it and re-install it. Now, it is visible in eclipse/adb and also showing in 'My Computer' also.
./hemant.virmani
Install Google usb driver from SDK Manager.
Later go to Device Manager, under "Other Devices" you'll see "Nexus" with the yellow exclamation mark. Right Click>Update Drivers>Let me choose>Let me pick from device drivers on my computer. Select android-sdk folder and click ok.
This solved my problem
Another option is if windows updates are turned totally off on your PC. In this case even if you download the USB driver & try update it manually as described above it will not work. The only way in this case is enabling windows updating drivers automatically. Once you enabled this, remove the non-working driver from device manager & connect you tablet to the PC via USB cable. The drivers will be automatically downloaded & installed by Windows.
This way worked on my Windows 7 PC.
After downloading the USB driver using the SDK manager, you can speed up the search for the new driver by telling Windows to look in the C:\Users\jdaehn\AppData\Local\Android\android-studio\sdk\extras\ folder (and sub-folders, in my case the drivers were in C:\Users\jdaehn\AppData\Local\Android\android-studio\sdk\extras\google\usb_driver)
From website below
http://www.asus.com/Tablets_Mobile/Nexus_7/HelpDesk_Download/
Download USB -> Nexus 7 USB driver for Windows
Unzip
Then follow the directions on this website below:
http://www.theandroidsoul.com/nexus-7-2013-drivers-installation-guide/
An Example for step #5, point it at this location:
C:\Users\Gene\Documents\Computer Setup (Installed Programs)\Asus Nexus Device Drivers\usb_driver
Download universal windows adb driver(Koush). Worked for me for windows pc's. http://www.koushikdutta.com/post/universal-adb-driver