When I plug my phone into my computer with USB Debugging enabled, literally nothing happens. The computer does not even detect a device has been plugged in and the phone does not show the charging LED.
When USB Debugging is turned off, without disconnecting my phone my computer detects it.
I think there's an issue with ADB on the phone as the error occurred after trying to patch ADBD using Chainfire's ADBD insecure.
So long without a reasonable answer?
Vivo Y55A, but your solution is probably similar, because this is a pretty generic issue. With platform-tools installed, using "adb devices" I saw nothing attached. Developer Options was of course activated (via tapping Build Number 8 times), and USB Debugging was set to "on." Below those options are "USB Debugging Mode" which I had forgotten to set to MTP (it was on Picture Mode or something). Still no device.
I changed the USB cable and that solved the problem. Aside from being faulty, some cables may have only the power connectors wired, and the serial lines may not have any connection. Do try at least a couple of other cables, as well as a couple of other USB ports (sometimes the driver pointing to a particular port may be faulty).
USB debugging can sometimes be hectic. I've faced similar issues without any reasons. The best thing you can do is, root your phone using any popular rooting software and then download WIFI ADB. Its pretty simple and decent to use.
When I run adb devices there are no devices showing as connected. My device is a LG Optimus Exceed 2 running 4.4.2
There are many of these posts around, so here's what I've done:
I'm using the cord that came with the phone. It charges and tries to sync photos, so it isn't an issue here. Switching usb ports and trying a powered usb hub doesn't affect it either.
I've added the vendor id (0x1004) to ~/.android/adb_usb.ini
Restarted and unplugged any combination of things you can think of
USB Debugging is on. And has been restarted. Same with Unknown sources.
I have never used EasyTether, nor is it installed anywhere on my computer.
Updated adb, updated my sdk.
Restarted adb server
Tried installing LG's drivers: http://www.lg.com/us/support-mobile/lg-VS450PP (They say they don't support Mac S/W upgrade, yet they have a package to install. No help there)
I have a Nexus S running 4.1 that works, and an old LG phone running Gingerbread that connect.
Any wizards out there who've already struggled with this who have advice?
I tried all of the connection types (charge, MTP, PTP) but perhaps not "Internet Connnection, modem"? You can change it by pulling down the system-wide drop down menu and touching "USB connection".
This is how I fixed it, but I thought I'd tried this already, so I can't guarantee it wasn't this in conjunction with one of the things done above.
PTP seemed to do the trick. Never had to do that on any other device...
I had the exact same problem. Selectin Internet Connection and then Ethernet as the USB connection type fixed it and everything is working as expected now.
I know this sounds like a stupid answer, but the same thing happened to me. It turns out the micro USB cord was just bad - which is weird, because it still charged the phone perfectly fine. After testing the bad cable unsuccessfully on a phone that had been recognized on my mac before, I switched to a different micro USB cable, and that made all the difference.
This is late in the game but I had an additional step to all the other suggestions. The phone was showing up in the System Profiler after I switched the usb mode to 'MTP' mode, but I didn't see any usb tethering options. After adding the phone's vendor ID to the usb ini file, enabling the developer and usb debugging, killing and restarting adb, I still didn't see my device in adb devices.
I finally had to download the Mac driver for the phone directly from LG.com. After installing and rebooting on the computer, the device showed up in adb devices.
I can't seem to connect my Samsung Galaxy Note II (N7100) to my Windows 8 Machine (aiming to use the phone for debugging - but current can't even connect the device as mass storage). No USB notification is shown when connecting the mobile by cable.
Things I have checked thus far:
USB Cable (works on different machine and with HTC phone)
USB Ports (tried different ports, 2.0 and 3.0, all working)
PC USB Drivers
Phone (connects to my Win 7 machine)
Samsung Kies (and Samsung driver) and Google USB Driver both installed
PS. The reason Im asking this here is because I'm aiming to use the phone for development and I'm hoping to get some answers that aren't "have you double checked the cable?" like on every Google search I have performed so far. Hopefully another developer recognises this issue.
OK. so You've obviously done the basics and made sure all the cabling is functional.
it sounds like the Volume is not mounting in windows 8
if it's not detected in Windows Device Manager, and More importantly, if it's not visible in Disk Management, then the volume simply is not Mounting.
I would suggest
Try connecting to a Windows 7 Machine and see if it works, if it does, Then Most likely you need Windows 8 Drivers
I would be contacting Samsung Engineers for support on the Issue
What version of Kies are you using
i found this that might be useful for you
Ultimately, as you know the volume is not mounting due to Driver issues, and this needs to be resolved if you are to have a solution
You could always Try setting up XP Mode in Windows 8 and see if it recognizes that way.
Granted this is a bit of a workaround and a bit stuffy, but. Hey, it's another option.
let me know how you go
Go to dial pad & type *#0808#
It displays USB settings
Select MTP+ADB option
Press OK button
Connect to USB cable to PC
It shows Connected as a media device."
Has anyone found a good solution to debug a galaxy nexus as it gets power?
I can only debug and use the nexus 10 while its plugged into my computer. I can only charge the nexus 10 when its plugged into a wall.
It charges from USB so what am I suppose to do short of rooting the device and using ADB connect to its IP address?
Do they make cables? Are there ways to send more amps through a USB slot? would a USB hub work?
Something, anything? This is truly a nightmare
I see you're leaning towards a hardware solution, but my answer is more of a workaround I am using:
I assume that most of your debugging you do on emulators, but if you just need to know what's crashing your app on nexus 10, maybe you can try ACRA to get the stack trace. I found it very useful as I cannot test all devices and all versions, plus my IDE is on a VM without USB support... I call it "poor man's debugging".
More on this post: android - how to send crash reports
If it was me, I would get two USB cables (1 Nexus 10 cable and another USB-USB cable) and splice the power leads from one into the Nexus 10 cable. That way you could then plug the Nexus 10 cable from computer to Nexus 10, and the other cable from your wall charger.
Of course, you have to be comfortable doing this, and sure of your soldering.
EDIT 1: I should also note, that you might wish to look into the POGO pins on the side of your Nexus 10. I believe that these can be used to charge the device (I'm sure a little bit of googling will confirm this). You could see if there are any docks out yet (There weren't when I last checked a couple months back) that could be used to charge it, leaving the USB connection free.
If you don't mind to root your device, or already have done this. ADB over WIFI could be an option. You can find the directions for ADB over TCP in this post:
How can I connect to Android with ADB over TCP?
adb devices was working fine last year, but after upgrades and new software installs,
adb devices no longer recognizes USB attached Android devices.
Here is what I have tried:
adb kill-server
adb devices
adb usb
error: Device not found
If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.
If you use Easy Tether, BEFORE you plug in your phone run:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
(or unplug/plug your phone in after)
If you are done debugging and want to use EasyTether again, either restart or:
sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If you want to remove the EasyTether kext so it never hassels you again:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext
Reference/Credit: http://www.intohand.com/post.php?s=2011-02-17-android-debug-bridge-not-just-working-on-mac
Having just connected a brand new Motorola Atrix 2 to my Mac running 10.6.8, I had to pull down the menu from the top of the screen, tap on "USB Connection", and change it from "Motorola Phone Portal" to "Charge Only" before it would show up in my list of devices from adb. Hope this helps!
Following the google bug submission... I set usb mode to Charge Only, and it detected the phone immediately. Pretty silly.
Another alternative: on modern Apple iMac's, the USB port closest to the outside edge of the machine never works with ADB, whereas all others work fine. I've seen this on two different iMacs, possibly those are USB 1.0 ports (or something equally stupid) - or it's a general manufacturing defect.
Plugging USB cables (new, old, high quality or cheap) into all other USB ports works fine, but plugging into that one fails ADB
NB: plugging into that port works for file-transfer, etc - it's only ADB that breaks.
If none of the above works for you just as it didn't for me, just try using a different cable. The cable I was using was my friend's cable but it was only meant to charge over USB, not to pass data over USB. I don't know how to tell the difference between micro USB cables that do or don't support data over USB but it's worth a try! Good luck!
I too am having this problem. However, it isn't just a problem with ADB, it's a problem with android devices in general on Mac OSX 10.6.6 Snow Leopard. Devices that used to work in 10.6.4 will no longer even mount the device as a USB drive. Googling to see if I can find the answers.
Change the USB connection type to 'Charge Only'. That was the only change I made it showed up on my device list. Weird.;)
I have seen another report of this bug. I have not been able to reproduce it myself yet.
The bug is:
MacOS X 10.6.6 [on some hardware] breaks adb [for some phones].
If anyone is able to reproduce the bug, feel free to add details of the exact hardware, build numbers and so on. I've asked the person who can reproduce the bug, to report it to google using the form at http://code.google.com/p/android/issues/entry
When he does that, I will add the bug report URL here, and people can add their hw/sw details to the bug report.
In the meantime, to be safe, I would recommend Apple users should NOT accept the snow leopard upgrade to 10.6.6, which was pushed on Jan 6 2011 (so it may already be too late for most).
Peter
I was having the same issue and tried connecting as charge only, but that didn't solve the problem, then unchecked the "Unknown sources" option to allow installation of non-market applications, tried it again and it recognized the device. I'm running android 2.2.3.
The bug report to Google is
http://code.google.com/p/android/issues/detail?id=15583
If you have encountered this bug (upgrade to MacOS 10.6.6 and adb no longer sees some phones on USB) please add a comment with any useful relevant info (like your exact hardware type).
I just ran into this problem using my HTC Inspire (Android 2.3.3) and Mac OS 10.6.8. The phone did not enter USB debugging mode when I connected it to my USB hub, but it did start USB debugging mode when I connected it directly to my MacBook Pro.
... and then, of course, it showed up in the list of devices attached.
The EasyTether fix worked for me, although first I had to load the kext file, then unload it. My Droidx popped up right away!
By the way, I'm running Snow Leopard 10.6.8 on my MacBookPro, so those who are having trouble with adb and connecting devices should check any USB applications, like EasyTether, for conflicts. Also be sure to follow all the above rules for
1. Application debugging (Settings->Applications->Development)
USB debugging: ON
2. USB connection (on notification bar).
Choose USB Mass Storage (altho Charge Only also works with my droidx and MacBookPro)
3. Unknown Sources (Settings->Applications->Unknown Sources = ON)
I have the same problem, I solved using an alternate install method.
First I put an sd card in my device.
Then I use a File Manager to transfer the .apk to the device, and I install it from the device
You can see a tutorial in
http://www.youtube.com/watch?v=7UOAw124y1s
I had this problem today with my HTC mytouch phone and OS 10.6.8. At the same time, the phone reported a damaged SD card. The solution was to remove the Micro SD card and erase/format it using disk utility as FAT 32. The name I gave the SD card volume appeared in the Finder when I tried connecting again (charge only). For some reason, Android reported the card as damaged but could not format it. I used a Micro SD USB adapter. My Macbook didn't see the card until I carefully slid it out and back into the adapter slot. This is a known problem with HTC android phones.
The last time I updated my tablet, it turned off "allow USB debugging", and I spent a half hour or so spinning my wheels. Double check that that is turned on in settings.
This thread is old but perhaps my answer will help somebody. Using a Motorola MB865 with OSX, ADB would recognize my phone only after I performed a factory reset.
I got the idea from this thread.
This was after I tried all the other tricks listed in other threads:
adb kill-server followed by adb start-server
Make sure USB Debugging is enabled
Make sure vendor USB ID listed in adb_usb.ini
Switching USB cables. For what it's worth, I did have to switch cables in order for the Mac to see the device. But this had no effect on ADB.
In the end, the factory reset did the trick.
in my case what worked:
disconnect device
exit android studio
run 'Activity Monitor' and kill adb
start android
studio reconnect device
For some devices running Android 4.4.2, you must enable tethering. You can do this in "Tethering and Mobile hotspot" and then check "USB tethering".
Try restarting the Mac in "Safe Mode". It worked for me (macos X.9.5)
Make sure that USB Debugging is enabled in Settings -> Application -> Developemnt, and also that the selected USB method is PTP and not MTP (not supported in OSX).
After connecting the device and enabling the USB debugging please go to the path of adb, which is now inside the android-sdk-->platform-tools and type the following command ./adb devices. I think this will list the devices connected.