I'm trying to push an app from eclipse to my phone but adb doesn't work. It doesn't see my phone when I write 'adb devices'. First I thought it could be a problem of Cyanogen Unofficial Android 5.0, so I reverted to 4.4, but it doesnt work either. I followed an answer on this this question 'adb doesn't show nexus 5 device' by installing the driver but the device manager tells me, that the driver isn't installed (Code 28). When I try to install it manually it doesn't work, neither uninstalling works.
I had same problem. Fixed it by doing to device manager
1. Find the ADB driver. If it shows the warning sign then click on update driver.
2. Choose to update the file locally yourself.
3. Browse the file. It always shows a SAMSUNG COMPOSITE DRIVER. Select that option and let it happen.
Don't worry if your device is not Samsung. The same driver works for almost all devices. Mine is a YU Yureka with CM12.
Hope this helped you.
Delete the device from Device Manager.
Rescan for hardware changes.
List item will show up with "Unknown driver" status.
Click on "Update Driver" and select /extras/google/usb_driver
Device Manager will find the driver and warn you about installing it. Select "Yes." This time the device got installed properly.
[source] Android device does not show up in adb list
Try this tool when your device is connected.
--> http://adbdriver.com/
Normally it should list your device and notice it has a faulty driver.
Hit the install button and it wil replace the faulty one with a working one.
[Source] Personal Experience
Related
I was trying to install some custom recovery and ROM on to my phone when I got to this situation.
(I have my windows update turned off)
ADB or fastboot shows
<waiting for devices>
I tried and saw few solutions.
I'm writing a detailed solution to this.
this was how I solved it.
if you have more suggestions you can answer below.
the only reason for this is that your PC is not recognizing Phone.which is a driver problem.
You have to understand a few things before starting with the solution.
you may know this too.
when you are in your recovery adb gets into something like recovery mode(just framing some terms myself)
in bootloader, it takes fastload mode.
each of this mode needs different drivers other than what the driver you use with adb when your phone is running on OS.
so what you have to do is.
if you are trying to get into recovery mode or fastload mode.
open device manager(settings>devices>(more options)Device manager).
now boot the phone into the required mode using manual or adb method.
the device manager reloads and a new driver will be shown. either in Android or pointing device or others folder.
select the driver and update online.(always preferred).
if you don't find an online driver you have to select manual update here.
select browse my computer.
select let me pick.
select browse.
at last, you have to select the usb-driver provided by the google.
in
sdk>extras>google>usb-driver
it will show the updatable driver.select and press next to install.
press ok now it should work correctly.
Happened to MACOS Mojave 10.14.6 while trying to install twrp-3.3.1-2-enchilada.img.
Solved it by running:
adb reboot-bootloader
Then, when the phone boot into bootloader,
fastboot boot twrp-3.3.1-2-enchilada.img
worked like a charm
Run following command to get your device into FastBoot mode (from adb-driver folder if using Windows System)
adb reboot-fastboot
For me, I couldn't even see my Android device in Windows 10 Device Manager until I went into Settings/General/Developer options and set Select USB Configuration to MTP (Media Transfer Protocol) instead of the default Charging Only, and also found a different USB cable that wasn't a charging-only one. Then, as #sushanthkille indicated above, I still had to install an updated driver, but the way he describes via Device Manager didn't work. For my LG G4, I had to go to https://www.lg.com/us/lgeai/Drivers/pages/mobile-drivers.html (found via googling for windows 10 LG G4 drivers) download the Windows driver, and install it manually. After all that, my G4 finally showed up in Windows 10.
For me it was not turning on usb debugging.
(settings -> developer options(you should activate this if you don't see this option) -> usb debugging.)
I had to update Windows 10 to resolve this issue.
I believe the needed update was a driver update for Android Bootloader Interface from Google, Inc. Windows updated several things at once so I can't verify that is what specifically solved the problem for me.
Usually it's the drivers' issue on Windows!
Just install the appropriate OEM driver from here:
https://developer.android.com/studio/run/oem-usb#Drivers
I've just spent a lot of time with the same problem, and it turns out to be because I have a Samsung phone.
There are a log of Fastboot blogs out there but what they don't always mention is, Samsung devices have no fastboot mode. So if yours is a Samsung device, don't waste time on any of the drivers and settings, because it will not work on Samsung. You can use adb but not fastboot.
There's another post with more info here: https://android.stackexchange.com/a/187573/111755.
Easy way
download the Google USB Driver from the official website (https://developer.android.com/studio/run/win-usb)
Turn off your device and connect with your PC or laptop with a USB plugging
go to the device manager, You will see Other devices. There you will see the Android option. Right-click on it and press on update driver, then click on Brouse my computer for driver S/W. then Let me pick from the list and continue with All devices and next. Then browse again and select the file from the folder you have downloaded and click on install. and restart
I recently bought LG G3 and I have enabled debugging mode but Eclipse is still not recognizing it, back when I used the Galaxy S3 for development I had to install Samsung Kies. The G3 drivers are installed and I can see it in My Computer, do I need something like the Kies but for the LG? If so can someone please post a link for that?
See update below
I found the answer that worked for me.
When you plug in the phone, bring down the status shade, pick the USB item ("USB connected") then, from there, pick "Internet connection" -- I chose Ethernet, but I'm not sure the choice matters on the dialog that pops up..
This enables USB debugging to become active; leaving it on Charging, MTP, or PTP does not work.
Once you do this, you can follow #Siddharth's steps to setting the ADB drivers, if needed. (You may need to use the actual LG drivers and not the Google drivers, but once I got this far, it was just like any other phone.)
Caveat
For me, even after going through this once, I still get the "installer" first and then have got go in and choose the "Internet connection" again. But, at least it works.
Update 10 Dec 2014
A recent firmware update has, indeed, removed the "Internet connection" as an option. Instead, PTP now works. I still get the "Connected as an installer" notification every time I plug in the phone and have to click on the notification then click on "Camera (PTP)" -- or wait about a minute. It's slightly better than what It was.
Also note: When this change occurred I had to install the drivers again for the phone, since it comes up as a different type of device when "Camera (PTP)" is chosen than when I used the "Internet connection" option.
For me, this has solved the problem: simply go to LG's website, http://www.lg.com/us/support/software-manuals, select the model (I have selected 'D850') and go to Software Updates tab where you can download the driver. I have installed it and then Eclipse recognized my device. I'm working on Windows 8.1, by the way.
yakobom
After a lot of searching and trying all solutions still I couldn't connect my LG G3 to eclipse on mac. Finally I find this solution, it works for me hope for you works too:
Install LG USB driver for mac
Go and enable developer mode in your G3 (Setting->About phone (in General Tab)--> Software information --> Tap 8 times on Build Number) then you will see the message which says the Developer option is enabled
In this step you expect that after connecting your mobile via USB cable, the Eclipse detect it
But for me it didn't happen
in this step you need to go (Setting--> Developer Options--> and turn off this option from above green (on/off) switch then again switch on this option from same place (If you don't do this step the "USB Debugging" mode will stay fray and you can not enable it)
In Developer Options menu scroll down until find the "USB Debugging" then tic it and enable it.
almost finished , you should back and configure running mode for your application and see the G3 in your connected usb devices
Try this solution :
Right click on My Computer --> Properties --> Device Manager
Right Click on your device --> Update driver software
Click on "Browse my computer for driver software"
Give path of your android sdk like "D:\Android_Sdk\sdk\extras\google\usb_driver" and tick "Include subfolders"
Click
Now repeat the steps till "Browse my computer for driver software".
Then click on "Let me pick form list of device drivers on my computer". Click on the first option and click next and then click yes. Drivers will be installed for your device.
Hope this helps.
Change the USB mode to PTP and you will get the RSA prompt.
Within the prompt, select allow it > ok and you are done.
This worked for me when I had the same problem on a Mac computer.
To contribute to possible solutions for this fix: I am using an LG G3 on a Mac.
In my case, ADB saw it as a device when I checked, and the Mac showed the device information in the System Information window, yet Eclipse did not see it. I also did not get the RSA confirmation pop-up when I connected the device through USB.
To fix, with my G3 connected, I selected the USB PC Connection (either from the navigation bar or through the settings) and changed it to be Send Images (PTP). Once this was on, I was given the RSA pop up and Eclipse recognized the phone in the Run Configurations window.
If you have this problem on Ubuntu; here is what I did to get it working:
Switch to PTP from MTP on the phone (this assumes you're connected via USB)
Disconnect the USB cable
Go to settings -> developer options and select revoke usb authorizations then ok
Make sure USB Debugging is checked
Reconnect the USB cable and your phone will say its connected as an installer; wait a minute or three and debugging mode should appear on the status bar (on the phone)
Open Eclipse and go to DDMS
Select "reset adb" in the dropdown if your phone isn't appearing yet
Working on Windows 7. All of the solutions from other sites didn't help (i.e. restarting adb and switching between MTP, PTP, Charing). In the end, I found this article (http://www.technobuzz.net/install-lg-g3-lg-drivers-windows-mac-usb-adb/), which contains links for the necessary drivers for the lg g3 (and some others I think). This did the trick and made the RSA key fingerprint dialog appear finally. After confirming, adb and eclipse recognize my device perfectly!
I had this buggy error with my LG Optimus L3 phone connecting to Win7/8 machines!
Cause: Device Driver was missing as it seemed at the end when I fixed it!
How to Fix:
Search through web (using Google) "LG < Your_Phone_Model Number > Drivers Download".(Ex.:- Go to About phone in your settings list > Model Number, for me it's LG-E400f)
Mostly the first few links are related to the required Device Driver download page.(Ex.:- for me I got the following link and for each device driver LG or most of the other vendors/manufactures have that kind of a Manuals and Drivers Page) Visit that page mentiioning about software update and drivers downloads.
Scroll down to the section of "Manuals and Software Update" and doing just the Step 1 was enough for me, which is "Install the USB DRIVERS "
Download it(for Mac or Windows) > Install It > Check Your Eclipse ADT > and it should be visible under Devices tab by now
Cheers!!!
Hope this helps to someone else to clearly get to the solution!
it seems that Eclipse shows the offline mode for lg G3 and some newer devices
and there is no way no use these devices for ADB debugging
there is a way
I am using windows 10
1- download this 11 MB file < http://dl2.uncox.com/android/upload/platform-tools-v22.zip>
2- then go to the directory that you installed the SDK
3- extract the zip file in to the platform-tools folder , override all files(click yes to all) be sure that Eclipse doesn't running
4- open Eclipse and select your android device that stands in devices tab at the right-top corner of your screen and then you can see the arrow near the screen- capture icon and you will find the reset-ADB. click on it ,after that your phone will ask you to allow android debugging for your device click on it
5- congratulations .now you can see that your device shown online
i hope this will help .sorry for my english
I also had a great deal of trouble when attempting to debug android applications on my shiny new LG G3. What ended up working for me was first installing the default google drivers onto the G3 and then following the process detailed by #lilbyrdie.
The process of installing the google usb drivers is very nicely gone through here.
However, with the most recently pushed android update to the G3 there are no longer the options for internet connection or charge only; but they seem to have fixed this defect forcing you to make this odd choice to enable debugging. The only options remaining are MTP and PTP, but if you pull down the notification drawer, choose the 'USB connected' notification (assuming the device is connected to your computer via USB of course) and from there click on 'Media sync (MTP)' even if it is already selected then debugging should be enabled.
Android can't update on the fly the developer mode. So, after turning on developer mode (and given you have the latest driver) switch the green button(under settings->general->developer options) to off and then back on. Then turn debug mode on (after that windows recognizes a new device) and you should be good to go.
In my solution for Windows 7 was helpful to update Android SDK Tools to latest version.
ADB Single/Composite values for LG G3 phones -
I found it was necessary to update (~userName/.android/)adb_usb.ini file with the line 0x1004:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207
0x1004
In addition, I needed to add the following entry in (.../sdk/extras/google/usb_driver/)android_winusb.inf:
;
; Android WinUsb driver installation.
;
...
[Google.NTx86]
...
;LGE Android Phone
%SingleAdbInterface% = USB_Install, USB\VID_1004&PID_633E
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_01
[Google.NTamd64]
...
Oh, and set USB to PTP as well as turn-on USB debugging.
When you're all done with the file modifications and several passes at installing the drivers (ref. earlier posts), you can verify your phone is ready via the Device Manager. It will list your phone as "Android Device"->"Android Composite ADB Interface". I believe an earlier post explains setting up the drivers
I know there's a ton of posts on this subject but none of them have helped me so far. Recently I did a clean install of my computer and now my Sony Ericsson Xperia Arc isn't showing up in my list of devices in Eclipse (it did show up before I reinstalled my computer). Now, to fix it I've tried the following:
Install latest drivers from Google SDK/Sony Ericsson developer website (windows told me that my drivers were already up to date).
Turn on USB Debugging (I am 100% sure it is turned on. I tried switching it off and on again, didn't help).
Install all SDK updates available (At this point I was trying anything but this didn't help either).
Run adb devices (It says "List of devices attached" but the list is blank)
Manually add the vendor ID in the adb_usb file
Kill the adb-server and start it again
None of the above have had any results. My device is still not listed in adb devices and thus also doesn't show up in my devices list in Eclipse. Does anybody know of anything else I can try to solve this problem? I'd really like to get on with developing apps again.
EDIT:
I forgot to mention, I do see my android phone in My Computer. I can move files onto it etc.
EDIT 2:
I think the issue is being caused by conflicting drivers. When I look into my driver file details I see:
WpdMtpDr.dll
winusb.sys
WUDFRd.sys
WpdMtp.dll
WpdMtpUS.dll
Should there be five entries? I don't know much about this but after having researched a bit I think maybe if I would remove WpdMtpDr.dll it would solve the problem. However, it is located in system32 and I don't like removing stuff there unless I'm sure of what I'm doing. Does anybody know if this is indeed likely to be the cause?
EDIT 3:
I FINALLY fixed it after being stuck on this forever, so I'll post my solution in case anybody comes across the same problem. What I did was actually pretty simple. Just go to the device manager and right click on "Xperia Arc S" which for me was listed under "Portable Devices". Click "Update driver software", then "Browse my computer for driver software", then "Let me pick from a list of device drivers on my computer". Now double click "USB Composite Device". After this open adb devices and restart the adb server (or just restart your pc, that should work as well). This fixed it for me, so if you have the same problem I hope this helps.
The answer in EDIT 3: worked for me.
Just go to the device manager and right click on "Xperia Arc S" which for me was listed under "Portable Devices". Click "Update driver software", then "Browse my computer for driver software", then "Let me pick from a list of device drivers on my computer". Now double click "USB Composite Device".
I had problems with Asus Memo Pad and Windows 7. Now adb finally works.
First of all, can you make other actions with the device when it's connected to you pc?
like moving photos/music from the device and to it?
If not then I think it's either a drives issue or as mentioned a malfunctioning cable and I would definitely replace the cable and set up the latest Sony drivers you can get from here:
http://www.sonymobile.com/gb/tools/pc-companion/
If this package doesn't help, then I would go further and install the arc drives you can get from here:
http://developer.sonymobile.com/downloads/drivers/sony-ericsson-xperia-arc-xperia-neo-xperia-play-xperia-acro/
are you successfully running your application on the emulator?
I just upgraded my phone to 4.2.2, but now i cannot use it in eclipse anymore.
I tried rebooting the device, reset my debug-settings but I cannot get it to work anymore.
I saw it is already a registered issue. There are some new security enhancements, so there should be a dialog (see here at bottom) but this dialog doesn't appear. I don't have several accounts on the phone, which is pointed out in the issue..
Anyone any suggestions?
EDIT: Look at accepted answer below, this should cover all cases. In my case, there were some packages missing, which weren't shown in the Android SDK Manager. I just found the Packages -> Reload in the Android SDK Manager... And I thought this happens automatically
You need three things in order to make sure this update goes smoothly:
Make sure your device is actually running 4.2.2 and the problem is not something else
Your SDK is updated to the latest tools. The adb binary in all but the latest version does not support the 4.2.2 security enhancements.
You are on the main account of your device in case of multiple user accounts.
Connect your Device to your computer and execute adb devices (make sure USB debugging is enabled). You should see something like this:
3tiu52839ry082j3 offline
Right about now, there should be a dialog on your device that looks something like:
Check the Always allow from this computer box if you want and click OK.
That's about it.
Some other things to check:
Make sure your USB cable isn't broken. Sometimes, the smaller cables break inside the main one, and your device may charge but have no data connection. Try with a different cable, or try accessing files on the device over USB (this will go fine if your cable is fine)
Make sure you're using the newest version of adb. Even after I updated my SDK tools, I couldn't get my device authorized when using adb. I eventually figured out that the Nvidia install of the NDK and SDK tools had updated my PATH variable to use the adb from that install, which wasn't the latest update. By using the adb in my newly updated install, I was able to get it all working.
For me it was solved by changing Nexus 7 tablet to "Camera(PTP)" mode.
Check out this blog post on how to do it.
After USB connection of Nexus 7 and confirming digest on Nexus 7, also connecting through TCP/IP with ADB worked.
Wierdly, unchecking and rechecking the "Allow USB Debugging" option popped me the window and selecting "ok" solved my problem.
If none of the solutions worked for you then Reset ADB.
Go to Devices ---Click the right most down arrow----Select Reset ADB from the list.
I had tried everything suggested here and suggested in every log/blog that I could find in google, but still no go. The USB cable is known to be good. ADB is version 1.0.31 (as shown with , USB Debugging is enabled in the Nexus 7 tablet, the SDK was updated to the very latest tools as available on 1-mar-2013 for 4.2.2/API 17. I had tried both Media and Camera modes for USB, rebooted windows, rebooted device over and over again, re-installed latest google USB driver, etc. etc. but ADB Devices still showed nothing.
I hard reset the Nexus 7 tablet thinking that maybe the screen to allow usb debugging had appeared but got hit with cancel. But that didn't work either.
What finally worked was:
going into windows control panel | Device Manager,
selecting NEXUS under Portable devices,
then in the Driver tab clicking on update and manually selecting the Google USB driver (the check feature said it was up to date). Previously, the date shown was in 2006, afterwards a date in 2012 (but more on this in a moment).
That didn't fix anything though.
So then I switched USB from MEDIA device to Camera device - THEN it wanted to install driver software, so I let it do that. Afterwards, I noticed that the driver for the Nexus was back with the 2006 version, BUT then ADB DEVICES FINALLY SHOWED OFFLINE!!!! HALLELUJAH AND the Nexus was displaying the Dialog to allow USB debugging, and it now all works.
What I am not sure of is what step actually solved the problem. I don't think it was necessary to hard reset the Tablet, but the fiddling with the device driver wasn't a very convincing solution either - I don't think the driver was corrupt - but maybe it had to be changed to get the right driver associated with the tablet when connected as a Camera Device. In any event, it is necessary to connect the tablet as a Camera device for ADB to work...
Restarting device or enabling USB debugging did not solve my problem.
However I changed USB PC Connection to "Camera(PTP)" mode and adb devices showed the device id of the phone.
After reading a lot post talking about this particular problem, I actually solved it by resetting user permissions on files (that were owned by root): ${HOME}/.android/adbkey and ${HOME}/.android/adbkey.pub
Go to Device Manager and uninstall your device and remove from USB
HAve you CMD opend and make sure you are at least in ADB Help.
Connect device to USB and continue with steps provided by Raghav Sood - few answers ahead of me.
Worked for me just fine
I tried with this custom build and it works for me. Now I can see my logcat in Eclipse again.
https://github.com/khaledev/ADT/releases
Download the zip file then in Eclipse menu Help > Install New Software... > Add > Archive... Just pick the downloaded zip and do the rest of the install process.
I am trying to enable USB Debugging on Android so that I don't need to use the emulator.
I did what all the posts all around the web say to do: I went to settings -> applications -> Developer -> USB debugging
It still does not turn on the notification sign that USB Debugging is enabled, and Eclipse does not recognize it, and uses the regular emulator.
Does anyone have any idea what is wrong?
You haven't specified what device you are using or what operating system you are using, so that could be helpful.
A few things to keep in mind:
1 Don't mount as USB storage.
2 You also need to make sure to install the drivers for your phone so that the Android Debug Bridge (ADB) can properly communicate. After these are installed, try the command "adb devices" and you should see an item in your list of devices.
Update based on your comment: You can download Kies from Samsung, which include the drivers (as well as other things): http://www.samsung.com/us/kies/
Or you can find unofficial driver-only packages, such as: http://forum.xda-developers.com/showthread.php?t=961956
I think you'll need the OEM USB dirvers.
Read this:
OEM USB Drivers
My experience with windows has been that you might need to un-install the USB drivers under device manager. Then disconnect the device (restart might be required). After plugging the device back in make sure you use the manufactures drivers if available
you have installed your device driver rite?then right click on your app name->run as->run configurations->target->select manual->apply.after that click on debug button then it will ask you to select the device.
If everything else is tested, try with another USB cable.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
Fruthermore on some devices you will be asked to accept an RSA key, which allows debugging through your computer. This ensures that other adb commands cannot be executed unless you're able to unlock your device.
Detailed information can be found here:
http://developer.android.com/tools/help/adb.html It is the overview about adb commands (which is used to send data to your device) and it starts with the steps how to bring your phone to debug-mode.
I wish to add to Danation's answer with the following.
If you have installed KIES, and you've tried following instructions a couple of times (for the android SDK package) without success, here's what worked for me:
As a precaution, disconnect the device, and press 'Revoke USB Debugging authorizations'.
Now, go to kies, and reinstall the device driver as seen on the image below.
Connect the device.
For me, it was a routine, it usually works when installing kies, but I was stuck on this today for a little while, and I hope i can help others with my solution as well..