I recently got a replacement of Samsung Galaxy Note 3 with Lollipop (stock rom, no root). I used to use this device with rooted version and it worked perfectly with my Android Studio on my OSX 10.10.5 Yosemite.
Now, with a new phone, it doesn't want to connect.
What I have done:
Installed/re-installed Samsung Kies3 OR Android Data Transfer that was provided from Google many many times. (Interestingly, data transfer works just fine.)
Reinstalled adb drivers using this adb not finding my device / phone (MacOS X)
-> What's funny is, in my System Information, it says SAMSUNG_Android instead of Unkown device.
Disabled/Enabled developer mode & USB Debugging
Restarted the phone
Changed the cables, Used/Not used usb hubs.
Tried on PC (Windows 10, Android Studio). WORKS LIKE A BOSS.
The problem I'm guessing
I think the phone fails at registering my Macbook Pro as a trusted device because every single time I connect to my Macbook Pro, it would ask if I want to allow USB debugging on this device. (Yes I check "always allow on this device" every time it is asked. I tried to revoke USB debugging authorizations, too)
Has anyone have the same problem? I really need to work on my laptop because I'd have to go somewhere out of town where I can't be in front of my PC.
Thank you in advance!!
After looking and looking, I finally found a solution.
It was because of EasyTether I installed on OSX and my phone.
Using this solution, I solved the issue.
Only problem was I could not unload the kext so I just removed it and restarted the OSX. Finally device showing up on ADB.
EDIT: copying and pasting the this solution part to save an extra click
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
I am trying to debug my application using a real device instead on the emulator. When I try to connect, it gives me the message:
USB device not found
I tried to unplug and plug it again, but it did not work. And I have also enabled USB debugging and unknown sources options in my device.
Any help is appreciated!
Thanks!
I had this problem with a Nexus 7 - it appeared in Device Manager fine but wasn't recognised by Android Studio. The device had USB debugging turned on. Eventually I noticed an icon in the top left hand corner that said "Connected as a media device. Touch for other USB options." When I selected this I was able to change from Media Device (MTP) to Camera (PTP) and then it started working.
If you are on windows, many times it will not recognize the device fully and because of driver issues, the device won't show up.
go to settings
control panel
hardware and sound
device manager
And look for any devices showing an error.
Many androids will show as an unknown USB device.
Select that device and try to update the drivers for it.
This solution works for every unrecognized android device... mostly general brands don´t come with usb debugging drivers...
go to settings
control panel
hardware and sound
device manager
And look for any devices showing an error. Many androids will show as
an unknown USB device or just Android
First thing you need will be your device IDs. You can get them opening up the device manager and finding the "Unknown Device" with a yellow exclamation point. Right click on it and select 'Properties', and then go to the 'Details' tab. Under the 'Property' drop down menu, select hardware IDs. There should be two strings:
USB\VID_2207&PID_0011&REV_0222&MI_01
USB\VID_2207&PID_0011&MI_01
Copy those strings somewhere and then navigate to where you downloaded the Google USB driver. Then you need to open up the file 'android_winusb.inf' in a text editor. I would recommend using Notepad++.
First, create a sub-section for your device. I called mine ';RCA 6378W2' but it doesn't really matter what you call it. Then, under the sub-section you created paste the Device ID strings you copied from the Device Manager, preceded by '%SingleAdbInterface%'. If you need help, look at this screenshot.
NOTE:
If you are using Windows 8 or 8.1, you will need to disable device driver signature checks before you'll be able to install the modified driver. Here's a quick video on how to disable device driver checks http://www.youtube.com/watch?v=NM1MN8QZhnk. Ignore the part at the beginning about 64 bit, your computer architecture doesn't matter.
Please look at this article, for more information and MacOS instructions.
Try a different cable, ideally an official Samsung one.
I had tried a crappy USB cable I had lying around and then tried another which was Samsung and works perfectly now.
Not sure why they would be different though but worked for me.
Found out for Samsung, Installing Kies also update the usb driver which solve my problem with connecting my Samsung Galaxy S Advance with Android 4.1.2 to Android Studio on Windows 7 64bit.
In this case the devise manager shows device driver is updated and working, but when I connect my phone Android Studio does not recognize my device.
I had the same problem with connecting my Galaxy Nexus to win7 x64. I solved it by getting drivers, they can be downloaded from here or also via Android SDK manager.
After you put your phone on developer mode, restart it. That worked for me, maybe it will work for you also. After restarting it, the phone was recognized, drivers were automatically installed. Note - I'm running on Windows 7.
I've been having this issue on Mac OSX Mavericks using Android Studio, using my Samsung Galaxy Express , I did a little trick, Run -> Edit Configurations - > Run -> Show chooser dialog. When I "play" and the dialog appeared, I connected my device and it did appear. ;)
You need to install the driver first. Follow the instructions on the Android's developers website:
http://developer.android.com/tools/extras/oem-usb.html
I had the same problem with a Samsung galaxy note 2. It was recognized on one pc but not on another one (both running windows 7 64b). After hours of struggling, I installed Kies (from the Samsung website) on the pc where Android Studio was unable to detect the smartphone (Kies was installed on the other one).
Like magic, Android Studio detected the phone !!! I noticed that the Kies installer installed some driver for the phone.
Consequently, for those meeting the same detection problem, I would strongly advise to first install Kies.
Galaxy S7, I had to go to Settings, Developer Options and allow USB Debugging. This asked to approve computer it was attached to and it showed up instantly.
I had tried restart the device, and it's work, popup and ask want to trust the mac for debug mode.
I am using Samung S8, I tried to install:
Intel Android Driver
Samsung USB driver
But the adb bridge driver was still missing.
I finally got it to work by installing the Samsung Smart Switch application which is a media manager application.
Updated at 2018-04-20: If you are struggle with the driver, just use http://adbdriver.com/downloads/
If you're using a USB Type-C cable, check if it has the charging and data transfer capability. Many USB Type-C cables are for charging only, and are not recognized by Android Studio.
Check installed drivers. If drivers ok, check device usb-port it could be damaged.
I have a Samsung Galaxy S4. Although visible from Devices, my phone was not listed as connected from Android Studio. I tried a few things independently, and then together, and found that only a combination of steps fixed the issue, so this is for you if measures listed above or on another site did not work on their own.
Enable USB debugging from "Developer Options"
Download Kies from Samsung. I believe Samsung US has replaced Kies with a new software called Smart Switch, but this did not resolve anything for me. I found a Samsung UK download of Kies that worked fine.
After connecting your phone to your PC via USB, go to your phone notifications and click on USB settings at the top. Switch it to Camera mode.
I repeat, only all 3 of these together fixed the issue, so if some fixes you have tried haven't worked, use these 3 and it could fix the problem for you. Best of luck.
Restart Android Studio Worked in my case
For me, this simple trick worked:
I actually enabled and disabled the listed USB Adapter for android in the device manager (Control Panel -> Hardware & Sound -> Device Manager). And holy moly it's working! :D
The solution for me was following the instructions at https://developer.android.com/studio/run/oem-usb.html#InstallingDriver. Specifically, the key part from that link that helped me to find the solution was this: "Install a USB Driver. First, find the appropriate driver for your device from the OEM drivers table below." This means that you cannot find a single link that applies to everyone as the solution. It will depend on your device! "So I visited the page to get OEM Drivers at https://developer.android.com/studio/run/oem-usb.html#Drivers. In my case, the device I was using was an LG K8 LTE. I had to go to http://www.lg.com/us/support/software-firmware-drivers#, Browse by product and I found the driver I needed under the Model Number "LGAS375 KG K8 ACG - AS375", Cell Phone Product. From http://www.lg.com/us/support-mobile/lg-LGAS375 I used the "Install the USB DRIVER" for Windows (http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425).
Depending on the device model you are using, you will need to find the specific drivers that work for your phone, and that should work.
How to get connection to device working using adb command line:
USB debugging enabled on phone and phone connected.
I am exercising these commands on linux(redhat and ubuntu) but same commands work under the hood on windows. The device manager runs adb commands. You can find a console in your device manager or regular command-line works if you set up your paths to SDK.
If you can run adb and see something like ???????? in devices list ..
$ android-studio/sdk/platform-tools/adb devices
List of devices attached
???????????? no permissions
You might be running the adb server as a regular user.
You might have to run the adb server as root.
So kill the server as regular user and start it as root.
$ adb kill-server
$ which adb
$ sudo <fullpath>/android-studio/sdk/platform-tools/adb start-server
Now look at adb devices list, if it is first time this machine connects to this phone you will see "unauthorized".
$ adb devices
List of devices attached
MWS0216A31xxxxxx unauthorized
At this point on phone you should have dialog popped up and you can tap ok to authorize. Then you should see "device" in the devices list and commands like shell/push/pull/sync/backup... should work.
$ adb devices
List of devices attached
MWS0216A31xxxxxx device
$ adb shell "uname -a; df; ls /storage/sdcard0/Download"
Linux localhost 3.10.90-g2ff1b22 #1 SMP PREEMPT Tue Dec 27 17:12:50 CST 2016 aarch64
Filesystem Size Used Free Blksize
/dev 1.3G 108.0K 1.3G 4096
/sys/fs/cgroup 1.3G 12.0K 1.3G 4096
/mnt 1.3G 0.0K 1.3G 4096
/sys/fs/cgroup/pids: Permission denied
/system 2.4G 2.3G 106.8M 4096
/cust 492.0M 327.7M 164.3M 4096
/cache 248.0M 160.0K 247.8M 4096
/splash2: Permission denied
/3rdmodem 59.0M 4.9M 54.1M 1024
/3rdmodemnvm: Permission denied
. .
/storage 1.3G 0.0K 1.3G 4096
/data 25.1G 10.9G 14.2G 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 25.1G 11.2G 13.8G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
.
.
Lovely jubly. Hopefully.
For example:
My file path:
C:\...\sdk\extras\google\usb_driver\android_winusb.inf
My data to paste:
;Tablet PC
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
%CompositeADBInterface% = USB_Install, USB\VID_18D1&PID_0003&REV_0230&MI_01
Well, in my case updating drivers, restarting Android Studio, restarting my phone, changing the USB mode or unplugging USB did not help.
Then I went to the dev settings in my phone, toggled the Dev. Mode off and back on, and it worked. AS was open and phone was plugged at the moment.
I had this problem occurring suddenly in Dell Ubuntu linux machine with Android Developer Studio. I did the following steps
1. I opened "System Settings"
2. Select the listed item "Software and Updates"
3. Click on the tab "Additional Drivers"
4. There was a mention about "Dell Inc: Unknown" and the option "Do not use use the device" selected. I selected the alternate driver mentioned and did an "Apply the Changes".
It started working.
I just ran adb command prompt and hit 'adb devices' and it showed daemon was not running. It installed itself and now i can able to see android devices there.
C:\...\...\source\repos\ABC\ABC\Ex.Android>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ZF22Q3T unauthorized
and Reload the project
Windows, many times it will not recognize the device fully and because of driver issues, the device won't show up.
1).go to settings
2).control panel
3).hardware and sound
4).device manager
Restarted my PC and worked in my case.
Before asking my question, I have looked through a few threads that share the same problem as me and have tried all the given solution with no success. I am from Malaysia.
I cannot get my device to be detected to test my app on my phone. I have checked both the "Unknown sources" and "USB debugging" settings in my phone. I am using eclipse. But if I create a random virtual device, my app is able to run there.
Okay so I am using a Motorola Atrix 2. And I'm using Windows 8 Pro 64 bit
I have downloaded android SDK bundle from here : http://www.motorola.com/sites/motodev/us-en/motodev_lp.html
I have also tried downloading the latest driver with no success. I have also added this line in the manifest android:debuggable="true"
I have tried both as a mass storage device and a media transferring device.
I would appreciate any help a lot because as of now, I cannot progress further into developing an android app and that saddens me. :(
I have attached a picture of which my android phone should be detected in the window, but as you can see, none.
https://pbs.twimg.com/media/BJu1XSgCYAEGCUd.jpg:large
go to /your-android-sdk-directory/platform-tools using command prompt.
type
adb kill-server
adb start-server
adb devices
n see whether ur device is detected now or not...
Note: if you're using a Linux machine then put ./ before adb
Install proper drivers for your adb devices, from Android-SDK archive or Motorola site.
If you are on Windows machine, go to the device manager find your device, and select folder with drivers for it.
Open you windows os's explorer, have a look at the process, if there two or more process hold your adb, try to exits the process
Check that the android:minSdkVersion is lower or equal to the Version running on the phone. If it is higher it wont show on "Android Device Chooser"
Install and run programs/drivers with admin rights.
Have you installed Motorola Device Manager?
When debugging Samsung and HTC devices I got it to work by installing that kind of software (for syncing the devices to the computer).
Download from the following: ABD Universal Driver
and install it. Make sure you have your device plugged in before installing and make sure you are on USB debug mode on the phone settings.
I am new to mac and trying to use various Android devices for development. Everything was working fine till today when Android devices simply wont show up in DDMS view in eclipse. I have tried to use Terminal to look up connected Android devices using:
~adb devices
Device list comes up empty. Emulator shows up fine in the DDMS view as well as in the device list from command line.
I have tried the following:
Disconnected the device from the computer.
Restart the computer.
Restart the device.
Connected the device.
adb kill-server, adb start-server
Nothing seems to work. Any advice will be much appreciated.
Firstly ensure that your device is connected in "Charge Only" mode, so that the sd-card is not mounted on your local system while testing.
Next, if you're on Ubunutu, as mentioned on the Android Dev website here, you need to set up the device for development to see it in the list.
If you're developing on Ubuntu Linux, you need to add a udev rules
file that contains a USB configuration for each type of device you
want to use for development. In the rules file, each device
manufacturer is identified by a unique vendor ID, as specified by the
ATTR{idVendor} property.
EDIT: So you're on a mac, then a little lookup throws this SO question up. According to the post, this was the work-around:
ADB on Mac OS X stops recognizing the attached device after installing
EasyTether driver. Use kextload/kextunload to unload from memory the
EasyTetherUSBEthernet.kext kernel extension manually. It is in
/System/Library/Extensions/
Start USB debugging(in settings>applications>developer options) on device first.
And still there is problem, try following link.
http://developer.android.com/tools/device.html
It helped me to detect my Micromax Canvas Hd
Run any project in Emulator.While running the Project you can see the device in DDMS.
everyone, I would like to connect my galaxy nexus to the eclipse, which allows me to use the real device for debugging my program, however, my galaxy nexus does not appear even I have clicked on the usb debugging option in the developer mode. Can anyone give a hand to me, thank you!
Which operating system are you using?
If on Windows:
Have you installed the ADB and FastBoot? Does your device show up if you do adb devices?
If not, follow the instructions here or here.
Reconnection your device, open a console window and type: adb devices. If your device is listed in the output, Eclipse will also pick it up.
For Samsung provided firmware and drivers, check here.
If on Linux:
Follow this tutorial. You don't necessarily have to unlock the bootloader. As long as your device shows up in adb devices after adding the device identification lines in udev, followed by a udev restart with sudo service udev restart, all should be good.
Here is another tutorial that claims to install ADB automatically on both Windows, Linux and Mac. I haven't tried it myself. So it might be a good idea to peep inside the Knives-&-Forks scripts before executing them.
Make sure the USB driver is installed. Instructions can be found here.
You need to install the Galaxy Nexus driver from Samsung
Galaxy Nexus USB Driver