Nexus S not showing up on DDMS - android

I am using Windows 7/64 bit HP laptop
I have installed both Java 32 bit as well as java 64 bit. Installed Android environment.
Installed Google Version 4 driver from Android AVD and SDK Manager.
Windows automatically installed the nexus driver and it shows up in my computer->manage->device manager->Storage->Android UMS composite USB device.
Windows shows the removable storage for the connected Nexus S device.
but don't see anything on DDMS for device neither does "adb devices"
shows anything.

Did you enable USB debugging under Settings -> Applicatons -> Development? If you didn't, the phone won't show on DDMS

Check that USB Debugging is enabled in your Application Settings.

Related

Device not recognize in android studio for android debugging

My device Xiaomi Redmi MI A1 is running stock android, don't mistake it to be running MIUI.
Things I did :
(1) Enabled developer options and enabled USB debugging.
(2) Connected to my PC and downloaded Google's USB drivers for Android Studio as well as OEM USB drivers from Xiaomi.
(3) Installed it and also updated the device drivers from device manager by manually selecting the OEM USB driver file (it was showing no updates available afterwards), but Android Studio was still not recognizing my device.
(4) I also downloaded MI PC suite from their website but now it wasn't recognizing my device, I connected my device in PTP with USB debugging enabled.
I am using Windows 10 ( Version 1703; build 15063.632 )
My device config is AMD A6 processor at 1.8 GHz quadcore with 4GB RAM.
try to do this things...
1) change your USB mode to file transfer .
2) enable to install from Unknown sources ....
go to settings->additional settings/Privacy/Unknown Sources
3) also enable install via USB in developer options
4) restart Android Studio.
Try changing the "Select USB Configuration" option to MTP.
It worked for me after installing the Mi PC Suite from here: pcsuite.mi.com
Try changing the USB mode to PTP or any other, in some systems PTP is only recognised in Android studio.
open file explorer
right click on my computer
press on Manage
open the device manager
you can see unknown USB connected
right click and press on update driver
press on browse my computer
press on let me pick
press on USB composite and Next
that it!! you will get a popup that your device is recognized now,
you can see it in the device manager now, your USB is recognized now.
Good luck!

adb doesn't show nexus 5 device

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

USB driver Asus Nexus 7 Windows 7

I have tried every suggestion on this website and many others to no avail. Is it even possible to do android development for a nexus 7 on windows?
I have tried the usb driver downloaded from the sdk manager, the one from asus. I have tried changing the usb mode to PTP and I am still getting the the same message when I try to install the driver (manually).
"Windows could not find driver software for your device"
I know this question has been answered, but I just ran into an issue where uninstalling the Unknown Device, and then updating the driver manually was not working (by selecting the sdk/../usb_drivers folder). No matter what I did from Device Manager, I could not get the drivers to be found/installed.
Hopefully this helps someone - if you have an issue installing the device (Win7), this worked for me:
Disconnect the USB from the device.
On the device, go to Settings -> Developer Options, and click Revoke USB debugging authorizations.
On the device, go to Settings -> Storage -> USB Computer Connection (available on the drop down menu at the top right of your screen). Verify that Media device (MTP) is CHECKED.
Reconnect the device, and it should install successfully without a problem. If not, attempt to update the driver manually and point Windows to the usb_drivers folder of your SDK.
I just had this problem occur for me with two factory new Nexus devices (Nexus 7 and Nexus 4). For both devices, I had to do the steps above and everything worked fine afterward.
Ok here's something awesome. When browsing for the driver DO NOT select the architecture (i.e. amd64 or i386). Just browse to the "usb_driver" folder. It is working now.
\your_sdk_path\android-sdk\extras\google\usb_driver
I had to hook up 4 Nexus 7s (2012) on Windows 7.
After much trials, tribulations and many errors, here is what I had to do, for EACH device.
Plug in the Nexus 7 using USB. Watch it fail to install one out of 4 drivers.
Now, Computer -> Manage -> Device Manager -> Right Click on device -> Uninstall
NOTE: Check "Delete the driver software...". This buys you some time
-> OK
Unplug USB, wait 5 secs, plug it back in.
Windows tries to install a driver.
BEFORE it can complete, Right click on the device that appeared in the device list
and select "Update driver software"
Gotta be fast here. Time is of the essence. If you are slow, delete and repeat.
Browse to the Google driver ( \extras\google\usb_driver ) -> OK
Try connecting via Eclipse..
For me, at this point, the stupid Nexus was asking whether to accept a key.
Say OK, and I was all set. Not fun...
I have a new nexus 7 with 4.4. Had to "enable usb debugging mode" specifically in developer options.
Haven't seen this mentioned previously. Everything seems to work fine after that.
Here is a guideline how to install nexus 7 driver in windows: http://developer.android.com/tools/extras/oem-usb.html
I was also facing same type of problems and following this guideline my problem was resolved.
In a nutshell:
open SDK manager and install Google USB Driver
then manually update your device driver from Device Manager(control panel>>other devices)
Install the driver manually through device manager of your PC.
Try following these instructions: http://developer.android.com/tools/extras/oem-usb.html I couldn't get it working but after installing them manually it worked just fine.
Windows installs different set of drivers depending on whether you have USB Debugging enabled or disabled in Settings -> Developer Options (Of course, if your device is not rooted, you don't have to worry about USB Debugging as you won't see the Developer Options).
So unlike Lo-Tan suggested above, it is NOT required to disable USB Debugging.
I would rather install the drivers in 2 steps:
- First have the USB Debugging enabled and manually update the drivers.
- Second, disconnect the device, enable the USB Debugging and again manually update the drivers.
As Lo-Tan suggest, it is required to have MTP Enabled as explained in point number 2.
I was having issues with the latest adb usb drivers on my 2012 nexus 7. I installed an older version from this link and they worked. https://app.box.com/s/2c25e8bc42ecce400afd
Nexus 7 2013:
When changing mode and looking at device manager:
MTP: i see only the "Nexus 7" device under "Portable Devices", not updatable
PTP: i see "Nexus 7" under both "Portable Devices" and "Other devices"
none: i see only "unknown device" under "Other devices", not updatable
So, to fully install drivers, with adb interface, i had to put it first into PTP mode (+debubbing mode).
Then update the drivers of the nexus 7 device under "other devices" manually with the google drivers.
Now put the tablet in MTP mode and update the nexus 7 driver under "portable devices". choose "let me pick...", then "composite..".
The "Android Composite ADB Interface" now appear under "Android Device".
et voila..
I found that when installing either the Asus or Google OEM drivers it didn't install. But when updating the driver from device manager choosing "pick from list" and select Google as the manufacturer and select "Android ADB Interface Version 10.0.0.0" (after installing the Google USB Driver)
Notably this is on Server 2012 (albeit more similar to Win 8), but the same might apply to Win 7.
Just in case you have Windows 7 edition N:
Windows 7 N edition is a release of Windows 7 distributed in Europe that lacks the Media Center/Player parafernalia, so that the users can choose their own. Windows 7 N does not include the drivers for the Nexus 7. The Nexus N drivers "suddenly appear" when you install the Media Feature Pack for Windows 7 N and Windows 7 KN. Otherwise it is difficult to make the Nexus 7 connect through USB. After the upgrade, it recognizes the Nexus 7 automatically by plug-&-play.
My Nexus 7 2013 worked fine connected to my laptop for months. Then yesterday I couldn't get it to be seen by the debugger. I tried every thing on this page with no luck. I especially like the driver installation guide in the Nexus Root Toolkit (NRT) and USBDeview, but no luck. NRT's driver installation guide has step by step instructions that are great for debugging these types of Nexus driver issues. I highly recommend it.
Today, it is working fine again.
The difference? Yesterday, I was in my office and my laptop was docked in a docking station that has built in USB hubs. Today, my laptop is undocked and there is no USB hub. Both days I was connecting my Nexus to the same USB port, and while I couldn't get my laptop to see my Nexus, my Motorola and Samsung devices were fine.
I don't know why this makes a difference, but if you are stuck with this problem, try removing any USB hubs and/or undocking your laptop.

Asus Nexus 7 not recognized by Android dev tools via adb

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

Eclipse doesn't recognize Galaxy Nexus on Fedora 16

I have successfully installed Eclipse and the Android SDK on Fedora 16. However, when I connect my Galaxy Nexus (with debugging enabled), and click Run in Eclipse, the device manager doesn't find my phone.
On Windows I had to install USB drivers for the phone but I don't believe there are any drivers for Fedora 16.
Is it possible to mount my phone AND test on Fedora 16?
If you click on DDMS, does you device show in the Devices window? If not, here is a list of problems to check:
Your USB cord connection to the device is too loose.
If its an old USB cord, there could be an internal break within the wires.
The socket within the device for the USB cord could be bent.
I installed mtpfs and it worked after a few tries and reboots.

Categories

Resources