Database Info

[Q] Can't install ADB drivers- need help!

I figured it out!
I'm having trouble getting my computer to recognize my phone as an ADB device. I have an HTC EVO, running cyanogen 6.1. I've downloaded the android SDK, as well as several of the SDK components (Google-usb-driver, platform-tools, and several APIs).
When I plug in my phone, my computer would not recognize it as an ADB device, so i removed the drivers from my computer and tried again. I attempted to manually install the drivers from the file (C:\android-sdk-windows\google-usb_driver) with no luck. I tried going into the amd64 file (I'm running windows 7, 64bit), but my computer would not recognize the drivers.
I'm new to all of this (this is my first post)- any and all help would be greatly appreciated

I am having the same problem with a HTC Hero (Sprint) tried everything but i can't get my pc to regocnize the adb driver

same thing with stratosphere.
I have the same problem with an unrooted samsung stratosphere. I need to install the adb drivers to use the smartdog remote web desktop through usb. The samsung usb drivers are already installed so it won't let me install the adb drivers. What can I do?

Funny I thought I was having problems with ADB cuz I'm on a Mac but it appears you Windows catz are SOL too...WTF is up with ADB not recognizing devices? Somebody should have a fix or some info on this, so frustrating, I just wanna root my damn devices!

had the same issue. here what I did and it worked:
- go to junefabric dot com
- download and install PDANet( 'cause it got adb usb driver in it)
- uninstall PDANet( if you have no use of it. don't worry, adb usb driver doesn't uninstall)

[Q] Phone not recognized by computer

Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel

MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA

ADB driver for new ROM

I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.

keaukraine said:
I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
Click to expand...
Click to collapse
Goto developer tools and enable usb debugging ADB on the ROM your using it should do the trick.........
There are no new ADB drivers the same drivers are used for all the ROMS.......:laugh:

keaukraine said:
I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
Click to expand...
Click to collapse
Make sure your Motorola drivers are up to date. Just go to:
https://motorola-global-en-roe.custhelp.com/app/answers/prod_answer_detail/a_id/89881
If I had a dollar for every time I said that, I'd be making money in a very weird way.

[Q] [CM11] Can't find my Moto G via USB, ADB, Fastboot

Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.

Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!

jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050

Adb devices show blank after Twrp wipe

I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.

Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk

Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!