I am trying to connect debugger to an Android phone (HTC myTouch 4G Android 2.3) from a Windows 7 64-bit pc.
Interestingly enough, everything worked fine for a few months until about a week ago Windows just started using a default Android driver instead of the HTC driver with ADB support.
I tried instructions from here: Installing the Android USB driver - not happening
but it does not work. I tried restarting, re-installing drivers, restoring to an earlier point, nothing helps.
Under "Devices and Printers" my phone appears as a generic "Android Phone". When I try to update the driver and browse to C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 where HTC driver is installed I get the following message:
"Windows has determined the driver software for your device is up to date".
WPD FileSystem Volume Driver.
USB debugging is obviously enabled on the phone. The next step is to re-install Windows, but I want to avoid it and plus there is no guarantee that it will even work.
Do you have any suggestions?
Windows is a monolithic mess
Try a few of these, if you're lucky a magic pixie will come and nudge your driver thus fixing it.
1. Uninstall Reinstall
Uninstall the generic driver from device manager probably.
Reinstall HTC drivers
2. Uninstall clean reinstall
Uninstall the generic driver from device manager probably.
Clean the registry and other stuff using CCleaner (I trust this app)
Reinstall HTC drivers
Longshot
Upgrade to Win8 and do a refresh system.
It just started working for no apparent reason.
Thank you so much for your suggestions, but I really don't know what (if anything) out of the things I tried worked.
Download and install HTC Sync Manager from HTC:
http://www.htc.com/www/support/software/htc-sync-manager.aspx
This will install the needed drivers on your computer. Let us know if it works.
Related
I am just getting started in Android development, and am trying to get Eclipse (running on Windows 7) to recognise my phone so that I can use it for debugging. However, my phone does not seem to be recongised by Eclipse or by running "adb devices" from a command line.
Here's what I've tried:
I've tried both MTP (media device) and PTP (camera) transfer modes (similar questions on Stack Overflow have been resolved by using PTP).
I've ensured that USB debugging is turned on in my phone's settings.
I've manually installed a driver in Device Manager, by choosing "Update Driver Software" and selecting the .inf file in sdk\extras\google\usb_driver (which I had to modify by hand to include my device).
I've tried a Nexus 4 phone, a Nexus 7 tablet, and a Motorola Moto G phone. Behaviour is identical for all three devices.
I've tried the "Universal ADB driver", in case it behaves differently to the Google driver, but it doesn't behave any differently.
I've rebooted, I've reinstalled drivers, I've tried adb kill-server followed by adb start-server, etc.
No matter what combinations of the above I try, "adb devices" lists nothing. When I look in the Windows Device Manager, I can see "Android Composite ADB Interface" listed under the "Android Device" node, so I believe I have installed the driver correctly. I am logged in as an Administrator, so it's not a permissions thing either. I've tried every answer to every single similar question on Stack Overflow, but nothing works. I've been pulling my hair out all day and am close to running out of hair... any ideas appreciated.
EDIT: It just occurred to me what could be causing this. I am running 64-bit Windows 7, but 32-bit Java. Because I have 32-bit Java installed on my PC, I installed the 32-bit SDK. Would that explain this behaviour? Should I be running 64-bit Java? The only reason why I didn't is because 32-bit Java is installed by my company's group policy...
EDIT2: I have now noticed that when I plug an Android device in, and look at its Device ID in Device Manager, the device ID does not end in "&MI_01". When I plug the device into another Windows 7 PC, the device ID does end in "&MI_01". I believe this is why "adb devices" is not able to detect the device. Any idea why one PC would see a different device ID to another, with the only difference being the "&MI_01"?
Did you install your phone USB-driver?
and can you check it on device manager is installed or not? you can download your usb driver from yur phone company website.
After you install your phone usb driver , I think the problem is solved
I think the main reason is because the computer does not recognize your phone as below 1 device used to debug code, even usb device.
You can try to do the following:
- Turn up the window update
- Uninstall driver for usb connection from your phone to your computer
- Go to the homepage of the mobile device, download driver for usb connection to the computer and then reinstall the driver
Try Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices.
Download
After downloading extract .rar file into a folder.
Go to Device Manager, right click on Android phone and click to update driver. On next screen , give path of extracted folder and install it.
You can install with msi file also. Download .msi
Finally found the answer. I was missing a file called usb.inf from C:\Windows\inf. Not sure how on earth files just go missing from yours Windows directory...
Before asking my question, I have looked through a few threads that share the same problem as me and have tried all the given solution with no success. I am from Malaysia.
I cannot get my device to be detected to test my app on my phone. I have checked both the "Unknown sources" and "USB debugging" settings in my phone. I am using eclipse. But if I create a random virtual device, my app is able to run there.
Okay so I am using a Motorola Atrix 2. And I'm using Windows 8 Pro 64 bit
I have downloaded android SDK bundle from here : http://www.motorola.com/sites/motodev/us-en/motodev_lp.html
I have also tried downloading the latest driver with no success. I have also added this line in the manifest android:debuggable="true"
I have tried both as a mass storage device and a media transferring device.
I would appreciate any help a lot because as of now, I cannot progress further into developing an android app and that saddens me. :(
I have attached a picture of which my android phone should be detected in the window, but as you can see, none.
https://pbs.twimg.com/media/BJu1XSgCYAEGCUd.jpg:large
go to /your-android-sdk-directory/platform-tools using command prompt.
type
adb kill-server
adb start-server
adb devices
n see whether ur device is detected now or not...
Note: if you're using a Linux machine then put ./ before adb
Install proper drivers for your adb devices, from Android-SDK archive or Motorola site.
If you are on Windows machine, go to the device manager find your device, and select folder with drivers for it.
Open you windows os's explorer, have a look at the process, if there two or more process hold your adb, try to exits the process
Check that the android:minSdkVersion is lower or equal to the Version running on the phone. If it is higher it wont show on "Android Device Chooser"
Install and run programs/drivers with admin rights.
Have you installed Motorola Device Manager?
When debugging Samsung and HTC devices I got it to work by installing that kind of software (for syncing the devices to the computer).
Download from the following: ABD Universal Driver
and install it. Make sure you have your device plugged in before installing and make sure you are on USB debug mode on the phone settings.
I've read several users having similar problems, but none of the solutions I've found have solved my issue.
I have several Nexus devices running Android 4.2.2 and they all show up as offline and none of them show a prompt when I plug them in.
I already tried:
unplugging/plugging them in
switching off/on usb debugging
restarting computer, nexus devices and the adb server
reinstalling drivers and even switching drivers to Samsung ADB drivers
Confirmed I'm running adb 1.0.31
Made sure my path points to adb.exe
Deleted any old adb.exe files on my entire computer
if you have properly installed adb and you tried all of the remedies mentioned at above the listen to my remedy:
The reason to appearing "device offline" in android 4.2.2 is that android has a security feature in 4.2.2 that create a whitelist of usb ports that can be used as debugging port.
After plugging deivce in usb and entering the command "adb devices" a popup window will be raised in your device and ask you to accept the connection:
After accepting RSA fingerprint of you usb you can now issue the "adb devices" again and see the device is no longer offline,
If you dont see the popup window, the reason is your adb version is old, your adb version must ne at least 1.0.31 (you can see the version using the command "adb version"). if version is older than 1.0.31 then update your platform-tools package using latest updates from google. You can find the latest version in sdk-repository. find platform-tools*.zip associated with your OS and download from https://dl-ssl.google.com/android/repository/platform-tools*.zip .
for example version 19.0.1 of platform-tools can be downloaded using these links:
For linux: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-linux.zip
For windows: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-windows.zip
For MacOSx: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-macosx.zip
that's it
Finally found the answer. I had installed "SnapPea", which apparently ships its own ADB.exe. It was somehow getting in the way. Uninstalling this poorly written software and rebooting fixed the issue.
As an Android developer, this type of thing is scary. Was it sending everything I did to a home server somewhere? Why should any software install ADB on a customer's computer?
This is probably the reason Google had to add this security measure in the first place...
I got the same problem and it was just my ADT Eclipse plugin wich was out of date.
I install all the updates and everything went ok.
I don't know if its the same for you, sometimes we just forgot to put the updates...
For me it was working, but a minute later (upon reconnecting the usb cable) the device was 'offline'. I got it 'online' again by disabling and then re-enabling the USB Debugging option in the developer settings of the device.
I just purchased a ZTE Cricket X500 running 2.3.4 for the purpose of testing my Android apps on. When I start the DDMS in the Eclipse Android SDK the device is not listed. The phone is in debug mode, Unknown Sources is enabled, and as far as I can tell the neccesary USB drivers have been installed. Furthermore I have a "Android Dev Phone 1" and the DDMS is able to recognizing that. My computer is running Windows 7. Any theories as to what might be going on?
try these commands:
adb kill-server
adb start-server
for some reason, this works for if the device isn't listed
I think it is because of your drivers, So install drivers for your device in your computer, then try to use it in dubug mode. so for that you have to put your device in debug-gable mode.
Hope this will help you.
Have you looked here and done everything required?
As the link says, if you are on a Windows machine or Linux machine, you need to tell your system to recognize the vendor ID for your phone. Hopefully this helps.
After developing and testing for months my android application both on the emulator and on a phone, I suddenly can not connect any more to the phone in one of the two PCs I use for development.
One PCs runs Windows XP 32bits. Here everything is ok. But my main development machine is a Windows 7 32bits: Both of them run Eclipse Galileo. I can not get connected to the Samsung Galaxy S GT-I9000T phone from there. Two Sundays ago I updated my application last version to the phone. Went on vacations. After returning I upgraded the Samsung Kies suite to the new version 2. It is supposed it installs USB drivers for Windows. I also upgraded to Android SDK 9 and ADT 9 but I'm not sure it was after the problem appeared. Then I realized can not connect to the phone. My first suspect was Samsung Kies. But I made all these intallations on the xp PC and the connection works OK. Then I returned to the Windows 7. There is another driver called "USB Driver for Windows" which I have installed from Android's SDK "SDK and AVD Manager"/"Available Components"/"Android Repository" I tried to reinstall it. I deleted the package despite the warning it can not be undone. Then I tried to find it on the "Available Packages" but it was no more there.
I reinstaled Samsung Kies, Eclipse, Android SDK but the problem remains the same:
Another fact: with USB debugging active, Samsung Kies can not connect to the phone. It detects something is connected but it stays forever trying to connect.But it occurs also on the XP machine.
In summary:
I can not get listed the "USB Driver for Windows" in the "SDK and AVD Manager"/"Available Components" for installation, even after reinstalling all the development environment
I can not get the development environment to connect to the phone for debugging.
How to fix this?
Any hint is welcomed.
Thanks in advance.
Sammy
I finally found the origin of the problem. I hope it will be useful to someone else.
Device Manager showed "ADB Interface" / "SAMSUNG Android Composite ADB Interface" with a warning sign. The device was not running 'cause some inconsistencies in the registry.
I deleted both the "ADB Interface" / "SAMSUNG Android Composite ADB Interface" and "Universal Serial Bus Controllers" / "SAMSUNG Android USB Composite Device" and reinstalled them from Windows Update. This time I didn't used Samsung Kies Tools / Install Driver menu.
Thanks for your time.
Sammy