I'm trying to run my applications on OMEGA T107 tablet. But adb
doesn't see my device. I tried almost everything.

- 30,437
- 17
- 118
- 169

- 737
- 1
- 9
- 17
-
13What is almost everything??? – Frank Sposaro Aug 04 '12 at 17:28
-
See https://stackoverflow.com/questions/6159532/how-to-install-adb-driver-for-any-android-device/62916180#62916180 – Ojonugwa Jude Ochalifu Jul 15 '20 at 13:41
-
FOR LINUX CHECK HERE: https://android.stackexchange.com/questions/144966/how-do-i-get-my-device-detected-by-adb-on-linux – João Pimentel Ferreira Jan 04 '21 at 21:51
16 Answers
Some of these answers are pretty old, so maybe it's changed in recent times, but I had similar issues and I solved it by:
- Loading the USB drivers for the device - Samsung S6
- Enable Developer tools on the phone.
- On the device, go to Settings - Applications - Development - Check USB Debugging
- Reboot O/S (Windows 7 - 64bit)
- Open Visual Studio
I think it was step 3 that had me stumped for a while. I'd enabled developer tools, but I didn't specifically enable the "USB Debugging" but.

- 2,084
- 2
- 24
- 34
-
-
2Develop Options - USB debugging ON did the trick for me as well Using a n "hena T107" tablet- Thanks – Elliot Jun 15 '20 at 00:28
-
FOR LINUX CHECK HERE: https://android.stackexchange.com/questions/144966/how-do-i-get-my-device-detected-by-adb-on-linux – João Pimentel Ferreira Jan 04 '21 at 21:51
I tried all the ways listed on the web for a whole day, but I didn't get any solutions. Then, I followed a link and in just two minutes my problem was solved!
By the way, it's for Windows users!
Find out the vendor id of the device from device manager.
To do this, connect the OTG port to the USB port of your computer.
Go to Start Menu and right-click on “My Computer” and chose “Properties”.
Select the “Devices” option which will open “Device Manager”.
Select your device (mostly in USB devices or Other devices) and right-click and choose “Properties”.
Choose the “Details” tab and select “Hardware Ids” from the property dropdown, you can see the hardware id, in my case it was x2207 .
Open android_winusb.inf and add these lines:
;<Device name> in our case I gave MK808
%SingleAdbInterface% = USB_INSTALL, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_INSTALL, USB\VID_2207&PID_0010&REV_0222&MI_01
Open C:\Users\.android\adb_usb.ini and add the following entry
0x<device id> .. in our case it is 0x2207
Restart ADB by
adb kill-server
adb start-server
Now ADB should recognize the device.

- 5,089
- 2
- 35
- 50
-
4Thanks, got my MIO A105 up and running now! On OSX the vendor ID can be found in "System Information > Hardware > USB". The adb_usb.ini file can be found in ~/.android – Roy Oct 14 '14 at 08:22
-
/!\ The link redirects me to a phishy news site that tries to load unauthenticated scripts and install chrome extensions, a link update would be appreciated – Nino Filiu Feb 04 '19 at 13:49
-
1I already describe everything which was in the link. so there is no need to visit the link. @NinoFiliu I will remove the link to prevent any harmful script. Thanks for mentioning – Omid Heshmatinia Feb 04 '19 at 18:48
-
1Why doesn't this mention where android_winusb.inf is? I found like 6 of them on my PC. – Scorb Mar 28 '19 at 15:53
-
@ScottF you can download any mobile driver, but the best choice is to download google one from the SDK MANAGER and change and use that file there. Its in Extra Folder – Omid Heshmatinia Mar 29 '19 at 02:34
-
2
-
FOR LINUX CHECK HERE: https://android.stackexchange.com/questions/144966/how-do-i-get-my-device-detected-by-adb-on-linux – João Pimentel Ferreira Jan 04 '21 at 21:51
I had same issue, none of the solutions worked for me.
Open Settings Menu -> Developer Options -> USB Debugging should be on
Android 11
Settings -> System -> Developer options -> USB debugging

- 18,865
- 13
- 88
- 163
-
Using android 11 I had to go to Settings -> System -> Developer options -> USB debugging. (Slightly the same but since I had to search a bit, I add this comment ^^) – Matt Walterspieler Aug 17 '21 at 13:05
-
Wow, I use my Android 12 phone regularly for development and somehow it turned that option off by itself. Not sure why. I didn't event think that this would be off. – Csaba Toth Aug 25 '22 at 05:46
The normal way to fix this is indeed to restart the adb server :
adb kill-server
adb start-server
then
adb devices -l
should list connected devices
But it possible that it doesnt fix the problem. It appends to me.
I had to disable/enable
the debug mode on the device, and then restart adb server.

- 14,902
- 14
- 51
- 81
-
2that does not solve the problem, I've been doing that for hours. It's something more – João Pimentel Ferreira Jun 23 '19 at 12:25
-
Yup. I was really puzzled because the PHONE said "usb debugging connected" AND "lsusb" clearly showed it, AND the same model of phone worked fine with the same computer yesterday. – John Gilmore Sep 08 '21 at 22:02
On Windows it is most probably that the device drivers are not installed properly.
First, install Google USB Driver
from Android SDK Manager.
Then, go to Start
, right-click on My Computer
, select Properties
and go to Device Manager
on the left. Locate you device under Other Devices
(Unknown devices
, USB Devices
). Right-click on it and select Properties
. Navigate to Driver
tab. Select Update Driver
and then Browse my computer for driver software
. Choose %ANDROID_SDK_HOME%\extras\google\usb_driver
directory. Windows should find and install drivers there. Then run adb kill-server
. Next time you do adb devices
the device should be in the list.

- 31,729
- 16
- 153
- 201
Not all USB cables can transfer data. Try using a different USB cable if your device is charging, but doesn't establish a connection to your machine.
Read more: How to tell a USB charge-only cable from a USB data cable - Dignited
What operating system are you on? If you running Windows you will want to make sure you have the drivers. You should also make sure that your Android SDK Manager is not only installed, but it also contains some additional things for different devices. Not sure if yours is in there or not.
Make sure that your phone has debugging enabled. I found myself having to run
adb kill-server
adb devices
often.

- 1
- 1

- 8,511
- 4
- 43
- 64
-
1
-
-
yes this one from google, using SDK manager. I thought that drivers could not mach but cant find anything for this tablet :/ – Adrian Deja Aug 04 '12 at 18:00
-
Yeah. I couldn't easily find a driver for that tablet either. Tough look. Let us know if you find one. Should have factored that into your purchasing decision. You can always install Ubuntu :) – Frank Sposaro Aug 04 '12 at 18:05
On windows, you will need to install drivers for the device for adb to recognize it. To see if the drivers are installed, check the device manager. If there is any "unrecognized device" in the device manager, the drivers are not installed. You can usually get the adb drivers from the manufacturers.

- 5,158
- 5
- 34
- 39
-
i know, ofcourse i`ve checked, drivers are installed i think just drivers from goodle aren`t good one – Adrian Deja Aug 04 '12 at 18:13
-
Google doesnt provide drivers for devices from different manufacturers. When you say drivers are installed, did you install it yourself, perhaps from a CD that came with the tablet? – Aswin Kumar Aug 04 '12 at 18:22
-
Try installing [PdaNet](http://junefabrics.com/android/) for windows. When installing this application, they also install many drivers for different devices. I've found this to be a single easy source for installing many device drivers. – Aswin Kumar Aug 04 '12 at 18:24
-
no i dodn`t becouse i haven`t any cd and can`t find drivers that will be mach :/ – Adrian Deja Aug 04 '12 at 18:25
For Windows 8 64 bit with a Nexus 10 device, this worked for me:
https://github.com/koush/UniversalAdbDriver
It has a link at the bottom to this:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi

- 18,472
- 5
- 61
- 80
It worked for me in my Astro Tab A737 Download and install PdaNet+ from http://pdanet.co/a/ in your computer.
follow all steps in the wizard while installing .Once the drivers are installed Android studio should recognize the tablet.
Also, make sure the device is in PTP mode.

- 41
- 3
Uninstalling all old "Android ADB Interface" drivers that were installed previously and then installing the new one worked for me.

- 825
- 1
- 9
- 22
-
Tried everything, updated to the latest google driver, edited android_winusb.inf and adb_usb.ini -- nothing worked until I uninstalled ADB driver and let windows (7) install a new one automatically. – il--ya Jan 01 '21 at 02:24
Keep in mind while you connecting device Android propose to select one of possible connection options. In my case:
- File transfer
- Power charging
- Media
Not all types of connection will work with ADB. In my case need to select Power charging to be able to connect to ADB

- 390
- 1
- 4
- 10
Intel has a peach of an article on this. It's all the same driver. It's just a Device ID mismatch in the Inf file which can be edited, or Windows forced to Install the driver we point it to. Intel's article is very thorough and takes care of every hurdle you come across. The link - https://software.intel.com/en-us/xdk/docs/installing-android-debug-bridge-adb-usb-driver-on-windows

- 31
- 1
Enable
Developer options
.Set
USB debugging
on.It can show a dialog
Allow USB debugging?
(with RSA fingerprint). Confirm it.If the device hasn't appeared in a device list, try to eject USB wire from the smarthpone and plug again.
You can change a connection option between:
- Power charging
- File transfer
- Media transfer
- USB-modem
- MIDI.

- 26,736
- 15
- 188
- 224