I have an android BQ Aquaris E5 HD with the version 4.4.2 and when I plug it on my mac, the android file manager launch and it's all ok, but when I run my android app from eclipse my phone doesn't appear on the devices list to run the app.
But if I try for example with a Samsung SIII it works fine
What can be wrong here ?
I also have a BQ E5, but the FHD version.
Try this:
1) Install ADB Driver Installer and make sure your device appears in this software screen.
http://adbdriver.com/
2) Go to Eclipse
3) Go to Windows / Open Perspective / DDMS
4) In the screen that appears, to the left of the tab where it says "Threads" there is a small triangle up-side-down "View Menu"
5) Select "reset adb"
6) Accept in your phone the message of authorization
Your device should appear now and be available.
Good luck
I had the same problem, same device (BQ Aquaris 5 HD), same Android version (4.4.2), also a mac (#Serge answer is for Windows OS I think) . I found the solution following this answer from user dustmachine in another topic.
Follow the steps about editing the adb_usb.ini, in my case the vendor ID was 0x2a47 but check it yourself just in case.
The command echo 0x2a47 >> ~/.android/adb_usb.ini did not work for me for some reason. If that happens to you, go to your home folder (terminal will open there by default, or just execute the command cd) and execute the command ls -a to see the hidden files and check that the .android folder exists. Go in (cd .android) and execute echo 0x2a47 >> adb_usb.ini and it should work just fine. You can check it for example with pico (pico adb_usb.ini).
Now reset adb. In my case as I don't have it as an environment variable, I went to the folder where the adb program is, inside the sdk. It should be something like /android-sdk-macosx/platform-tools/. Just look for it around, should be easy. To reset the adb execute the command ./adb kill-server (or just adb kill-server if you have adb as a environment variable) and then ./adb devices. It should restart the daemon. Plug your Aquaris and execute ./adb devices again. If everything went well, it should appear now.
One more thing. It should appear now in your mobile phone a pop-up with an advice about debugging from that computer. If you don't accept it the device will appear as offline and unelectable when prompt to pick device in eclipse, for example. If you accept the device will finally be available for debugging as when you work with the emulator.
Sorry if I explained some obvious steps, but I encountered a ton of problems with small things like those while finding the solution.
If you still encounter problems, be sure that you have set your device to debugging mode (the seven build-number tap). Check this questions for more detailed information:
How to load my app from Eclipse to my Android phone instead of AVD
adb not finding my device / phone (MacOS X)
Do you have USB Debugging turned on?
go to settings -> Developer options -> and turn on USB Debugging.
MAC Yosemite with Bq Aquaris E10 3G Android 4.4.2 (API 19)
1) Disconnect USB from MAC
2) echo 0x2a47 >> ~/.android/adb_usb.ini
3) adb kill-server
4) CONNECT TABLET to MAC using USB
5) adb devices
Related
I just upgraded my Android device to 4.4.2 and now Eclipse will not be able to choose a running Android device when I want to run my project. The Android Device Chooser shows my device up with a serial number as "????????????" and Target as "unknown" and State as "??". Additionally, I have enabled Developer Options with USB Debugging.
what os are you using. i see that on my linux box with some devices. i normally kill adb and restart it as root and the devices shows up and works correctly. found that solution years ago on stack overflow or something like that. not sure if the same thing is needed with windows/osx. on linux, assuming adb is in your path:
$ killall adb
$ sudo adb devices
otherwise os you're trying to connect it to and the specific device information would probably be helpful in tracking it down.
I have a few suggestions. Try them in this order until it works.
Reboot the phone.
Try turning off and then back on "USB Debugging" on your phone (in Developer Options probably).
open cmd > go to the your Android SDK directory > type cd platform-tools > type ./adb kill-server > then finally type ./adb start-server
References:
Eclipse - Target "unknown" in Android device chooser
Android device chooser - My device seems offline
The solution for my device after updating was to completely uninstall the device driver from device manager and reinstalling it. I am using windows and my mobile was shown as Android Phone and not as Nexus 7. Home it helps someone.
LG Nexus 4
Android 4.3 (USB DEBUGGING ACTIVE)
ADB 1.0.31
on Kubuntu 13
My /etc/udev/rules.d/51-android.rules is taken from here https://code.google.com/p/51-android/
Like i said everything i got with #adb devices command is:
List of devices attached
00b453e41****** offline
(i censored the id)
Any other info that could be userful?
Ok i solved by myself, it seems it was an issue of permissions.
Just made my user:group owner of the /home/user/.android folder (and all files inside), the owner was root before and i think this was the problem. Now everything works.
Another solution for people that might find themselves looking for one:
For Android 4.3
Under Developer options, click "Revoke USB debugging authorizations:
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
With the new update to 4.2.2 to my Galaxy Nexus and Nexus 7, I can't find both my devices under adb.
These are the steps I took:
Updated to 4.2.2
Updated ADT and SDK through the SDK Manager
Checked ADB version, it's at 1.0.31
Restarted PC and Tablet and Phone numerous times
When I run adb devices, it's just blank. I have the same issue on Windows 8 and on Ubuntu 12.10, but on Ubuntu it shows my device and it says offline.
Are there any other steps I can take?
From the adb docs
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
So, unplug, wait, replug in the cable, and hit ok (on modal dialog that appears on your device)
If you hit cancel, the device will show up as offline via adb devices
Try pre-installing the drivers for your devices. Make sure, under Windows, that your device is recognized in the System control panel first.
I use Windows 7 and my Galaxy Nexus wouldn't be recognized by the system until I installed the device drivers before plugging them in. From the comments, this works on Windows 8 as well.
Galaxy Nexus drivers
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#
Goto Manual & Drivers > Software
Nexus 7
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
Just though Id share my experience, I had -
Unplugged and re plugged in the device
Installed the correct platform tools
Installed the correct Android bridge Turned USB debugging on and off
and on and off an...
Tried WiFi but it said it was offline
etc. etc.
What fixed it for me was changing the device connection from Mass Storage to MTP. To do so, with the phone unplugged you go into -
"Settings" -> "Storage" -> Click the menu Button -> "USB computer
connection" -> "Media device (MTP)"
Hope this helps some one from going crazy!
Thanks,
Ash.
I tried everything mentioned here and in other posts. It wasn't the cable, the USB port, rebooting the PC or Nexus 7, killing and starting adb or enabling/disabling USB Debugging.
It was due to the 4.2.2 OTA update, I simply replaced the \platform-tools\ folder, as described here: Android ADB device offline, can't issue commands
Download the updated platform-tools: http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip
adb wait-for-device
works for me. Just unplug your usb device, run this command, and while it's waiting, plug your device in, then it will just work. :)
Here is what I did (Galaxy S4 4.2.2):
go to Settings => about this device => click several times on "Version number", that is to say something like "JDQ39.I9505XXBHYTGKDD" (not android version or anything else) ; here you will see that Google or Samsung have a lot of humour as you have to click until multiple times until having a toast displaying "You are at few clicks from being a developer" ; after something like 10 clicks, you have a toast "You are a developer"
Go "Development options" (in the "More" tab (rigjt tab of settings menu)) ; be sure that "USB debugging" is checked.
And it works ! Eclipse can see your S4(or any other device) 4.2.2 !
I had this problem today and fixed it by rebooting the Tab2 while leaving it plugged into the laptop/eclipse
Check if you have installed android-adb-tools in Ubuntu. If you do, the adb tool may be old. Uninstall and make an alias to the latest adb tool you download with the ADB plugin. To check the adb version do "adb version" if it's 1.0.29 is the old, the latest and working for Android 4.2.2 is 1.0.31.
I made a lot of stuff until i realized this.
going to Developer Options and checking USB Debugging solved it for me
My solution used on cm10.1 nightly build on droid bionic, was after updating the newest usb drivers, using the Mass storage option (instead of the MTP option for USB computer connection), then unchecking and rechecking in developer options, "ADB over network" option. Then it did the RSA pop up dialog.
For me the best solution was:
Update the Android SDK via the SDK-Manager. Removing the '.android' folder in my usr directory ( Windows 7 ) and re-plugging the device back in. Worked flawlessly due to the ADB RSA key issue. I had an older version of ADB that I stashed into c:\windows\system32\ due to not wanting to install an entire freakin SDK when all I wanted was a command prompt. Good ol' Google, the new Microsoft.
You may use an old version of adb.exe. Update platform-tools.
You may have to set a new path to adb.exe as well.
In case it helps someone else arriving here, I had this problem with a ZTE phone.
I tried installing the driver based on the offical list here but in Device Manager the driver was marked as not installed correctly.
In the end I found the way to make this work was:
Press Menu Button
Choose "Connect to PC"
Choose "Default connect type"
Choose "Install Driver"
Plug in phone and on PC select option to install the driver
Then change "Default connect type" to "PC software"
After doing this I was able to do:
adb kill-server
adb start-server
adb devices
and view my device.
It's working on windows 8 using Android 4.4.2
Reset your phone,
go to setting->about phone-> seven time click on build number.
go to back and go to developer options check USB debugging.
go to windows 8 start menu click on profile picture and click change profile picture.
Select devices and on Download over metered connections.
Connect your phone via cable your PC and wait.
I was developing an android application from Eclipse, connecting my Acer ICONIATAB A 500, with Android 3.0.1. And I did not have any problem.
Now I'm trying to developing the same application on Acer ICONIATAB A 501, with Android 3.2
and my ADB can't find the new device, while Windows can find it! I set in my tablet Debug USB option active, and I installed the appropriate driver on Windows.
I installed even the last Google USB driver (Rev. 7)
I tried to list the device find form adb with command
adb devices
from command line, but List of devices attached is empty.
What can i do?
execute these line
adb kill-server
adb start-server
if it is mobile device check that in settings, developers options , debugging mode is checked or not
You need to install LGUnitedMobileDriver package from the LG website, even though Windows 7 automatically installed USB drivers for the phone.
Try to update your Android-SDK on your computer (in Eclipse or whatever IDE you are using), this helped me solve a similar Problem.
I'm trying to run my applications on OMEGA T107 tablet. But adb doesn't see my device. I tried almost everything.
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.
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.
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
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.
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.
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.
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.
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
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.
Uninstalling all old "Android ADB Interface" drivers that were installed previously and then installing the new one worked for me.
Debugging needs to be enabled on the target device in order for adb to see it.
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
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
Go to Device Manager
Right-click Android Composite ADB Interface
Uninstall devices
Right-click your LocalPC then select Scan for hardware changes
Your device should be enabled
Open Command Prompt
adb kill-server
adb start-server
adb devices