Hey guys,
I have been trying to get my phone connected to my pc for a few days now.
I am having major issues with getting adb to work. I have googled pretty much every solution, tried the drivers posted on here, everything.
It seems that turning on USB debugging on my phone does nothing. I get no new notifications in windows (7), no new hardware, no ADB Composite Interface showing up.
I really don't know what to do next - anyone else have this problem?
Are you able to try plugging it into another computer to check the usb interface isn't faulty?
I have tried it on both my work pc (vista) and my home pc, with the same result.
When I type the command adb devices I just get a empty list.
I put it into fastboot mode and was able to get fastboot devices to list the serial, which is why I think theres something wrong with USB debugging mode on the phone.
Would a factory reset fix a problem like this?
Well I have fully reformatted my pc, and restored the phone and still have the same issue.
You have to install the ADB drivers.
I attached the drivers you need.
If you need more help, let me know.
Still not working - I tried the drivers you attached, as well as previously the drivers from the android adk.
I can get a Android ADB Interface to show up in Device Manager, but the adb devices command just gives me a blank list.
Why is it that I only get Android ADB Interface, and everywhere else on the web I see Android ADB Composite Interface?
W7 x64 and using the SDK drivers mine shows up as Android ADB Composite Interface (at the top, in it's own Android Phone category) with USB debugging enabled.
If I boot the phone into recovery mode, i get Android ADB Composite Interface, adb devices lists my phone, and Android ADB Interface is disconnected.
But when the phone is running, the composite interface is disconnected, and the Android ADB Interface is connected, but adb devices lists nothing.
I have just put on cyanogen mod 6 tonight, and its still the same. Is there any other part of the phone that might cause this?
Tonight I tried on my mates pc, it didn't work, but his desire showed up right away.
It's really frustrating buying a 'developer' phone which I can't develop on.
Well look's like this is a froyo problem with certain devices -
http://code.google.com/p/android/issues/detail?id=9437
So from reading the previous link it seems it's an issue with non 00 mac address's, like the wifi issue. My mac address on my nexus starts with 38.
But the updated broadcom driver in cyanogen mod 6 fixes wifi issuse I have, but not the adb issue.
What is the best way to try get something done about this?
Related
ADB stopped working on my desktop suddenly (It still works on my laptop) adb devices show nothing, and adb shell brings "error: device not found."
I've uninstalled the drivers and reinstalled many times, going over the process outlined here: http://forum.xda-developers.com/showthread.php?t=532719&highlight=adb+noobs
Running KingxKxRom 2.2 (Hero rom)
I've looked on the forums for people with the same problem, but their solutions didn't work for me. Example: stopping the adb.exe process, etc
USB debugging is checked.
Device manager shows:
Android Phone:
Android Composite ADB Interface
USBDeview shows:
Android Phone: HTC Android Phone USB Device
Android Phone: USB Mass Storage Device
Android Phone: Android Composite ADB Interface
Any ideas how to fix this?
What OS are you running?
On my computer?
Windows XP
Have you tried removing your usb drivers in the device manager?
This same thing happened to me. I just uninstalled all of the usb ports, and when I reset my computer it recognized the ports, and everything seemed to work again.
Hey all, I hope this is the right forum.
I installed the Samsung Drivers on Windows 7 x64 and attempted to install the google Android SDK drivers. I managed to get ADB working, my phone is in debug mode and I've managed to do a lot of cool things and run linux commands with BusyBox. Problem is though, windows keeps screwing it up, so currently "adb devices" will not always show my device, even if I have debug on and such. The phone says USB connected when I plug it in, but after a couple minutes, windows says something to the effect of "Could not install USB Device" or "One of these devices has malfunctions, windows does not recognize it". And in device manager, I cannot seem to get it installed under PCI devices like most guides say, it installs under USB. This sux
I apologize if this is the wrong place, if so, I would be happy if a moderator could move this.
Please note, I think adb was just disconnecting and the solution was simply to type in...
adb connect 127.0.0.1
Thanks
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
nikpmr said:
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
Click to expand...
Click to collapse
Does it show up when typing adb devices in the command prompt?
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
nikpmr said:
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
Click to expand...
Click to collapse
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Try to force ADB to redetect with adb kill-server.
abrahammmmmmm_ said:
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Click to expand...
Click to collapse
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
nikpmr said:
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
Click to expand...
Click to collapse
Is your computer windows 7, 8 x32 or x64bit? I can probably do it today if you've got a windows 7 x64bit computer since I wont have to do much looking
I'm running win 7 64 bit. Thanks again for your help!
nikpmr said:
I'm running win 7 64 bit. Thanks again for your help!
Click to expand...
Click to collapse
NOTE THAT YOUR PHONE SHOULD NOT BE CONNECTED DURING THIS PROCESS
I already searched & set up the update folder so you don't have to do all the dirty work d:\
Ok Well I'm just going to make this quick and not really got through the basics like how to unzip things because if you don't know how to do that you probably shouldn't be trying to get s-off on your phone anyway so I'll just assume you already know how.
Step 1. open control panel select hardware and sound and open Device Manager with the administrative logo one the side.
Step 2. Near the top or somewhere on this list there's supposed to be a drop down that reads "adb devices, adb android, adb, android, adb drivers etc. Mine shows Android USB Devices it actually just varies based on computer I can't really go to the specifics of it but I'm sure you can find it.
Step 3. Select that dropdown menu and right click whatever shows (there should only be one thing) and then select Update Driver Software and choose the option that says Browse my computer for driver software and locate the htc drivers folder which should already be unzipped, select the whole folder and have the option to include subfolders checked. click next or whatever it says to finish
Step 3 Now you must remove your device from the Portable Devices dropdown menu to ensure all drivers are detected for the phone, to do this right click on HTC First and just select remove, wait until it's done. and now just reconnect your device and let all the drivers install and it should now be done!
Make sure you look at the screenshots I attached to make sure you don't accidentally remove or update something else also because that's where the drivers folder is an i'm pretty sure you'll need that
A reboot of the computer is recommended btw
Ask questions if you have any
View attachment 2459140
View attachment HTC_drivers_Win7_x64.zip
View attachment 2459141
Wow, that's quite explanatory, thank you! Unfortunately I only see the category ADB Devices when the phone is connected and in recovery mode, and I only see the category Portable Devices when the phone is connected, booted, and in debug mode. (Neither of these categories are visible when the phone is disconnected from the computer.) I did however try installing the drivers you gave me with the phone connected and in recovery mode, but to no avail; after the phone boots ADB Devices disappears and Portable Devices appears. Uninstalling Portable Devices doesn't help either; it just reinstalls when I reconnect the phone.
I am trying to get the category ADB Devices to appear in the Device manager when the phone is turned on and in debug mode so that I can use ADB while the phone is booted.
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
nikpmr said:
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
Click to expand...
Click to collapse
How exactly did you replace the HTC First driver with the Generic USB Composite Device Driver?
I'm looking to port app restores - mostly game saves - from my old phone to the Droid Turbo. I've used Helium in the past but I can't get the Turbo to connect to Windows 7 yet. I've been trying to use the drivers linked from the Helium URL and here, but without success.
Anyone have luck tracking down USB drivers?
Any suggestions other than Helium?
Update:
Looks like the Motorola drivers started working as soon as I posted this (of course...).
This one was driving me nuts the last two days. On Win8.1 x64, the driver wouldn't auto-load when the device was plugged in. Until I saw your edit reason, I didn't even think to go through the manual device list and select the driver manually. "ADB Interface/Mot Composite ADB Interface" worked for me, as well.
Also, if you change your USB Storage mode on the phone, it may also change how the ADB Interface is detected. I had to manually add the ADB Interface driver a second time when I turned on MTP mode for the USB Storage connection. I had had it previously disabled while trying to figure out the ADB issues, once I had ADB working, I re-enabled MTP and subsequently Windows "forgot" the ADB device driver again.
For others: I had to go through the device manager, pick the unknown adb device and update drivers, pick drivers, select the clockworkmod section on the left and instead of mot composite I had to use the first option, android composite adb interface. Now my mtp connection works. Haven't tried reconnecting yet so it may well forget the drivers again, but at least I know what to do now!
Need the drivers from google sdk kit. Just google search installing adb drivers. I used helium fine.
I am so frustrated right now I don't even know what to do. Here is where I am and I welcome any ideas. I have read and tried every suggestion I can think of.
I have a Win 8 laptop I want to connect the Nexus to so that I can sideload 5.1. Currently the phone is still factory stock.
With debug turned off, my computer sees the nexus and I can transfer files. It sees it as an MTP device
With USB DEbug checked, my computer no longer sees it at all.
I have the latest android sdk installed.
When I go into platform tools and run adb devices- it is blank, nothing in either state (debug on or off).
Also it is not recognized in "Fastboot devices" when in fastboot mode, so the computer is not seeing it.
I have used USBDEview to delete drivers, then reinstalled using the latest Google USB drivers. no Help.
I have tried using motorola device manager to install proper drivers, no help.
Tried using Koush universal drivers and it did not help.
Thank you for any ideas you may have.
Try using "Nexus Root Toolkit" to set up the drivers for you. It has a driver setup tool.
aawshads said:
I am so frustrated right now I don't even know what to do. Here is where I am and I welcome any ideas. I have read and tried every suggestion I can think of.
I have a Win 8 laptop I want to connect the Nexus to so that I can sideload 5.1. Currently the phone is still factory stock.
With debug turned off, my computer sees the nexus and I can transfer files. It sees it as an MTP device
With USB DEbug checked, my computer no longer sees it at all.
I have the latest android sdk installed.
When I go into platform tools and run adb devices- it is blank, nothing in either state (debug on or off).
Also it is not recognized in "Fastboot devices" when in fastboot mode, so the computer is not seeing it.
I have used USBDEview to delete drivers, then reinstalled using the latest Google USB drivers. no Help.
I have tried using motorola device manager to install proper drivers, no help.
Tried using Koush universal drivers and it did not help.
Thank you for any ideas you may have.
Click to expand...
Click to collapse
I just went through that a couple hours ago. I ended up having to go in the device manager, and manually point it to look for the drivers in the platform-tools folder of windows sdk. Once I did that, the little yellow triangle went away, and all was well, adb and fastboot worked as normal. Hopefully that works for you too.