I have installed the latest Motorola USB drivers which include support for the Triumph.
When I plug in my phone, "adb devices" does not list my phone.
My device manager shows my device under Phone as well as Disk Drive. Both use the WPD FileSystem Volume Driver and refuse to let me update the driver by pointing the motorola drivers in Program Files. It continues to tell me that "Windows has determined the driver software for your device is up to date."
Any ideas?
I am currently in just about the exact same predicament =/
I have some possible avenues that we could both share:
Idk if you were able to find a phone number for Motorola (American that is) but i finally found one
Motorola Mobility, Inc.
600 North U.S. Highway 45
Libertyville, Illinois 60048 USA
Telephone: +1 847 523 5000
Here is a link to yet ANOTHER programmer having the same prob as us =/, but he got it figured out using the steps he posted there
Also there is live support chat here.
If you find a solution to this problem, please, please, please let me know =) And i will do the same for you if i get it figured out soon.
Edit:
Nevermind, i got mine to work just fine =)
Heres what i did:
Used USBDeview to uninstall all previously failed attempts at drivers lol
NOTE: You will have to run USBDeview as an Administrator(right click, select Run as administrator)
In the device manager, after uninstalling all the others, right click on what pops up for the device, click update driver, browse for your own, than from there it was a series of selecting from lists, but the key thing here is to remember that eclipse debugs programs on external devices using the adb interface, which should be a pre loaded option in said select lists =)
Hope this helps!!!
Have you enabled debug mode for your phone? This can be done via settings->application settings->development->USB debugging
Whenever I've had a problem with adb recognizing my devices I've managed to fix it by adding a reference to it in my .android/adb_usb.ini file.
I only run Linux/OS X at home and I don't want to try and blindly describe how to do it on Windows from memory, but they discuss it here http://android.modaco.com/topic/294799-adb-windows-7-and-the-pulse-tutorial/
And google gives the USB Vendor ID's here http://developer.android.com/guide/developing/device.html .
On my linux box I added:
0x0489
To my adb_usb.ini (using the Foxconn ID which on linux you can find directly via lsusb, I think you could use devcon on Windows to find it) and it shows up on my device list.
Just because this link hasn't been dropped in any answers (and I always find myself looking for it), here are the manufacturer's development drivers.
This is what worked for me. I have a Moto Triumph and Win7 x64...
Turn on Unknown Sources, USB Debugging
Install Motorola USB development driver. Unfortunately, Motorola broke the old driver URL, as well as many development forum URL's. Fortunately, Softpedia has copies of the installer. Grab the 32 bit or 64 bit version depending on your OS.
Plug in your phone by USB
Open Device Manager
View hidden devices
Uninstall default drivers (Disk Drives\Qualcomm USB, DVD\CD\Android SCSI CD-ROM, Portable Devices\F:)
Action > scan for hardware changes, or Disconnect/reconnect phone
Repeat till ADB appears (probably w/ a yellow icon indicating it's not fully installed)
Right-click ADB > update driver > browse my computer for driver > pick from a list > Motorola > Android Sooner ADB (the first entry)
Accept security warning
Done. If it worked properly, you can now view your device using adb devices.
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 know this question has been asked numerous times, but none of the threads have had an answer to solve my problem. It seems no matter what i try Eclipse just wont detect my phone, I have set it to debug mode in the settings, i've installed "Kies 3" on my laptop and it says i have the latest drivers already installed on my phone when i try to update it.
I've installed the google USB driver package from the sdk manager and have downloaded and installed the samsung driver from the samsung website. Windows recognizes the device and in the device manager under android phone it appears as "SAMSUNG android ADB Inerface".
Im running windows 7 and have even tried deleting all the mounted dive drivers from regedit as i seen suggested in another thread but still no joy! Really starting to get frustrated with this at this stage i've been trying for two days now to figure this out!
This is such a pain! I need to be able to debug on my phone too as i'm using features that the emulator can't handle (i.e. audio recording). I'm all out of ideas here so any help would really be appreciated!
Thanks
The method I followed to install my GT-I9300 drivers was this:
Download samsung drivers from this link:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Then just connect your phone and make sure you have a stable Internet connection: It will download required drivers automatically.
Also, make sure you have enabled Android developer options in your phone settings. Enable USB debugging in developer options.
I usually get it to work, when I switch the USB mode in my smartphone (e.g. MTP to PTP). This way, windows starts downloading more drivers.
1) Try disconnecting device from PC, revoke USB Debug authorization from settings menu, and then re-authorize the computer you are working on once you connect it again.
2) Check to see if you see the phone in DDMS perspective (left hand side) - if so, try clicking on it and it should work.
3) try removing all drivers (Google, Samsung etc.) + scan "leftover" registery entries using a reg cleaning program. Then install ONLY Kies Light version and try again.
4) It once worked for me - try changing the USB cable (preferably, to an original one)
Let us know if something worked!
1) enable USB debugging in your phone's settings.
2) ensure that you have the proper drivers installed.
3) open adb in command prompt and run "adb connect"
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.
Any ideas where I can begin to find out what's going wrong?
I have a T-Mobile Pulse Mini (Huawei) which I'd like to get working for developing and testing apps on. I can't get it to be seen by Android Debug Bridge despite restarting the adb server. (and emulators are seen by adb any way so that's unlikely to be the problem).
In the device manager the phone is displayed as a CD-ROM and when I select 'transfer files' from the auto 'PcOptions.exe' it is then displayed as a USB driver but in either case I can't see it in adb. I have enabled debugging on the phone. I remember it took me ages to get it to work on my previous Vista 32-bit. I can't figure out where to search from here. The drivers used to install the phone are on the phone itself.
Thanks very much.
Drivers. If you can't see the phone in ADB, it's almost always a driver issue and this is especially common on Windows. The regular user drivers are sometimes different from the ADB drivers. If you can find the OEM dev drivers directly that's ideal, otherwise there's a way to modify the INF file which you'll have to Google for unless someone else provides it, as I don't remember the details at the moment.
I want to test my applications on LG P500 device. But emulator is not detecting the device. When i try to add USB driver which is there in SDK, it is not accepting . Please tel me how to configure Device for testing.
I struggled long and hard to get the correct USB driver installed for my P500. I ended up installing a few different things, and over the course of two or three reboots I managed to get it going.
I'm pretty sure the actual setup details you need can be found here (Note, this is the New Zealand section of the LG website - which is where I am, but it should work globally).
If you follow that, you should be able to install the USB driver. Once done, go to SETTINGS-APPLICATIONS-DEVELOPMENT on the phone and turn on USB Debugging and Stay Awake - these help when you are using the phone to test code.
You can test that its actually working by going into the Android SDK folder shown below and typing adb devices (in the directory shown, remove the (x86) if you are using 32-bit windows) - mine shows up as follows:
c:\Program Files(x86)\Android\android-sdk-windows\platform-tools\adb devices
List of devices attached
80A354043044674101 device
I hope that helps - let me know if you are still having problems.
Change your phone settings to allow USB Debugging. Home->Settings->Applications->Development->USB Debugging. Then connect your phone and run ddms to see if your phone shows up.The emulator will not show your phone, but it should be recognized in DDMS
If some one trying to work on LG P500, Please follow the steps.
1> Connect your Phone to system.
2> Enable settings>SD Card & phone Storage > Mass storage only.
3> Now it will open the SD card. Go to PC suit dir, Install the application whc in turn contain USB drivers. After installation has completed desable mass storage only.
4> Change your phone settings to allow USB Debugging. Home->Settings->Applications->Development->USB Debugging as Apesa ans Steve suggested
(Even i hve installed LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All.exe )Please let me knw wht exactly this driver will do . )