I have tried downloading the Samsung specific drivers. It installs the modem, not sure if the adb bridge got installed. I don't see it in the device manager. I have installed kies 2.0, I have tried connecting USB via MASS storage, via Kies, and under no circumstances so far will ADB detect the device when running adb devices command. I got lots of suggestions to use Kies, I tried this. Don't see any real relationship between Kies and ADB which is a debug bridge. I simply have no clue what ADB is doing when I type adb devices. How does it look for devices, where does it check, where can i register my device with ADB?
Apparently sometimes you need to uninstall and reinstall the driver multiple times before it works (http://androidforums.com/captivate-all-things-root/136373-adb-shell-error-device-not-found.html). Also, make sure that USB debugging is turned in your application settings.
make sure you are using the correct drivers (32 bit or 64 bit). when you connect your phone in debug mode check device manager. I would bet you have an error in there. Try and delete the error and rescan for changes.
Related
Hello stackoverflow mighty community,
Please help !
I have a Datalogic DL-AXIST (http://www.datalogic.com/eng/products/automatic-data-capture/mobile-computers/dl-axist-pd-702.html) which is an android device but i guess the company fiddled a bit with its core. Also I have a windows 7 toshiba pc.
Anyway my concern is that it is not showing on the adb devices chooser.
Here is what i've tried so far:
I'm using Eclipse IDE, my SDK is up to date and i can test my application on all the other devices i tried so far.
The datalogic device has Android 4.1.1, driver is correctly installed on my pc i'm sure, enabled developer options.
I tried connecting it as MTP and PTP but will not work, there is also a CD-ROM installer connection which i tried as well, followed through the installation on my pc but still does not work.
It gets even stranger, when i used the third pc connection type and installed the device with its own adb on pc, i even copied those adb files in that folder and pasted them my eclipse's own adb. This worked ! my device was recognized but it changed for a reason i do not know.
I tried uninstalling the device driver and re-installing it from windows device manager, tried rebooting device and restarting eclipse and pc.
I really need some help because making this device work will greatly benefit my work.
Thanks !
This is genuine issue which may come frequently,but the soln is simple you may try these steps:
step 1;
try swictching developer options on and off
if the above dont works then go to device manager in your pc check portables devices select device and update driver software-->browse my comp-->let me pick list of device drivers-->select android as in option or MTP
if your device dont show in portable devices just update the device which comes in portable devices list trust me it works all time
try to do this once
1. Check if authorized:
\platform-tools>adb devices List of devices attached 4df798d76f98cf6d unauthorized
2. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" (tested with JellyBean & Samsung GalaxyIII).
Restart ADB Server:
Then restarted adb server
adb kill-server adb start-server
4. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
Now Check the device
It is now authorized!
adb devices \platform-tools>adb devices List of devices attached 4df798d76f98cf6d device
I have two Android phones
Alcatel One Touch 4030D, Android version 4.1.1, kernel version 3.4.0
Highscreen Spark, Android version 4.0.4, kernel version 3.0.21-perf.
adb devices detects the Alcatel phone, but not the Highscreen phone.
I tried to run adb kill-server; adb start-server, but it didn't help. Switching between different connection modes (Media device (MTP), USB storage) didn't help either. USB debugging is enabled.
Here are the screenshots of the Developer options settings:
How can I make adb recognize the Highscreen device?
Update 1 (03.08.2013 19:00 MSK): Adding the line 0454 to adb_usb.ini didn't help.
Update 2 (03.08.2013 19:59 MSK): My attempt to follow the official Google recommendations failed because I couldn't find the drivers for the Highscreen Spark device.
If you could setup an ADT on Linux or Mac, it will work out of the box.
We were able to connect all sorts of devices to adb easily with ADT on Linux/Mac.
If you haven't managed to connect it through usb, you can try the network connection.
Add your device to the same network, then type in the command prompt:
adb connect your_device_ip_address
Hey try to dig for drivers at Official website.
May be search other sites for USB drivers, that may help you to come out of your problem.
I had the same problem .Try it again by activating the usb mass storage.
Without adb driver for device (in your case Highscreen Spark) it is almost impossible to create a bridge(connection) between your program and device, as adb (Android Debug bridge) makes a connection between your PC/laptop to your android device And without Adb in windows Pc/Laptops its not easily possible to debug.
Because of this, Companies like samsung, lg, htc are providing adb drivers to users for easy debugging, if you dont have a adb driver for Your Device you have only one choice left , Change your operating System into linux and then see the magic.
I had this same problem. Turns out, the issue was the USB Port I plugged in to. The port directly on my laptop does not allow for ADB to see the device. The port on the back of my docking station does allow ADB to see the device. I believe it has to do with USB 3.0 vs. 2.0. I believe 3.0 blocks the protocol ADB needs to use.
You will actually require the device drivers to connect it, so try insatalling Highscreen Spark's PC Suite.
If that dosen't work or you don't find the PC Suite you can download Moborobo from here which is a universal PC Suite for smart phones and connect the device with it and then try connecting the device from abd
It may be a problem with your adb.exe. I had the same problem earlier for connecting HCL G1 tablet. I also added lines in android_winusb.ini, but could not connect yet. Then I found out this link. I got solution by changing the adb.exe file. Try this link : http://www.slatedroid.com/topic/37692-adb-drivers-problem/ Or just download the adb.exe from following link and replace it with you adb.exe file. http://sdrv.ms/NepKED It is also suggested run this command to make adb_usb.ini effective for respective adb after modifying. echo 0x2207 >> %USERPROFILE%.android\adb_usb.ini
Try these drivers
x86
x64
It works for me.
After head banging for more than a day - a small thing saved my life on my RK3066 based device:
after you update the adb_usb.ini and everything else,
and after you do a
adb kill-server
do a
adb usb
and only then do a
adb devices
saved my life
By the way
Adding the line 0454 to adb_usb.ini didn't help.
you should be adding 0x454
I was having issues with my android phone showing up when I typed adb devices but found out that it was the usb cable which caused the issue, members in my family have two different android phones each with their own charging cable. I was using one phone with the other phones usb cable just because it was the nearest and I didn't think it would make a difference but it did.
Try a different usb cable and that might help.
I have the same issue in the past but i don't found the driver on my computer today, so :
You can go on http://www.alcatelonetouch.com and find the call center for your land.
Call them , and explain the issue , they have to send you a driver to connect your phone to the computer. This drivers is very easy to install.
I have make that and i can use it for debbuging
I whish you good luck... Sorry for my English
I have already installed the drivers. I can transfer files from my Tablet to the PC.
Debug Mode is on, but adb devices and eclipse are not finding it.
It's a chinese tablet (=/) running version 2.2.
My PC is a Windows 7.
Already tried restarting ADB, but it didn't work.
Anyone knows what should I do to make it work?
Are You sure You've installed the ADB drivers for Your device or just the general device drivers? If not, check out the "Naked drivers" package on xda-developers. There are most of the important drivers.
Does Your adb interface recognize Your device when You type
adb devices
?
Here's a really nice tutorial:
http://forum.xda-developers.com/showthread.php?t=2139767
I've for some reason always had issues with ADB drivers, even when using the correct driver for the device, it says its installed but device manager says it can start for some reason. The way I've found to fix it which has always worked for me, not matter the device is to install pda Net on your PC. Its purpose is really to allow you to tether your device to your PC but it installs the ADB driver without issue.
You can find the software at http://pdanet.co/
I bought a new Alcatel Onetouch 918n phone for app testing. I can't however get it to be recognized in eclipse to test.
After some painful steps, I now see "Alcatel Android ADB interface" in Device manager. But I just can't seem to make this phone visible to Eclipse/ddms/adb.
Since i somehow (I Think after installing Alcatel Android mgr on PC) got the OEM Usb driver installed, I think I don't need the google usb driver, correct?
And Yes usb debugging on phone is on.
Please help?
Take a look at http://blog.fh-kaernten.at/wehr/?p=1182, where the author describes his problem with his device being in Device Manager but not showing up in ADB. Also look at Adb Devices can't find my phone. Some other things to try:
See what you get when you run ADB outside of Eclipse ("adb devices" from a command line). Sometimes Eclipse is finicky, so it may be better to troubleshoot this outside of it. Sometimes it's necessary to quit and restart Eclipse when it's not seeing your device, or unplug and re-plug your device.
When you make any changes, use "adb kill-server" and "adb start-server" to stop and restart the adb server, before again trying to see your device.
If possible, try a different device and see if it shows up in adb (though you'll probably have to install a driver for it first). That may tell you whether the problem is with your Alcatel phone or the software on your computer (missing SDK component, wrong USB driver, etc.)
I have a Wi-Fi Motorola Xoom that I am connecting via ADB for development. I am seeing an intermittent problem where the device (with ID number) shows up in the adb devices list, but will present as being offline.
The device and computer both show the tablet as being connected. I've tried a combination of rebooting each device and swapping USB ports, but the only thing that solves the issue is switching out the cable. Furthermore, a cable that I used yesterday doesn't work today -- I am having to use a previously non-functioning cable to connect.
Is this a driver issue? Device port issue? I have seen this issue with several versions of the Motorola drivers as well as the PdaNet drivers. I am currently using Motorola Mobile Drivers 4.7.1.
WARNING: this question referred to an older device and as such the answers may no longer be relevant to current ADB connection issues.
I met the same problems like yours, and I found out that the USB cable has mal-functions in the PIN of head USB. So I switch to the new USB cable, it just works fine and detect device as online.
I had the same problem, and switching from the USB port on the front of my machine to the port on the back made things work. It could be related to a difference in port power or USB type.
From XDA: nouvelle_adr http://forum.xda-developers.com/showthread.php?t=2247471
I downloaded the adb version and it worked.
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window"