Database Develop

Help with adb issues

so i had ADB (sdk 1.5 r3) set up on this laptop (in xp) it was working fine on my htc dream 32b, went to update the sdk to 1.6r1 and now neither my dream that worked before or the magic will be recognized as adb devices.
tried following the instructions in the adb thread utilizing usb deview, now i have 3 "drivers" listed per phone, usb composite, usb mass storage and adb, but mass storage and adb always show not connected (even when mass storage is enabled) on both phones, windows asks me if i want to "eject" the adb interface or the mass storage controller...
any insight would be appreciated, on a side note i have never gotten the mt3g (magic) to interface with adb but the dream has been used MANY times before and still functions on my personal laptop but this is the one at work

Make sure you uninstall the drivers from device manager, not just remove them.

the drivers install immeadeatly again after hitting uninstall in device manager when re plugging in the magic, doing that worked with the dream when i installed it the first time

Nexus USB Debugging does nothing

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?

[Q] ADB Installed, but sometimes fails.

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

[Q] ADB drivers?

I installed the usb drivers for my nook as per the instuctions in this guide: http://nookdevs.com/NookColor_USB_ADB#Windows_XP.2C_Vista_and_7
It seems to have worked and in device manager "ANdroid composite ADB device" shows up under Android Phone.
But when i type adb devices when my nook is plugged in, i still dont get and devices there.
Im running 64 bit Windows 7 on an Intel Core i7 machine.

I couldn't get the ADB drivers to work via those instructions either. Luckily we have people around here that are MUCH smarter than I am.
http://forum.xda-developers.com/showthread.php?t=910008&highlight=adb+driver+install
Follow the instructions and install the software from that thread, worked for me great.

I am having the same problem here. It seems like everything is installing fine. I deleted the old usb mass storage device, installed everything, but then when I try to do adb devices, I get a blank line. No serial number. I then tried adb wireless, I connected using adb connect 192.168.2.4 and it said connect it was connected. I then ran adb devices and it spit back that it was connected to that ip address but it still doesn't give me a serial number.

This is what I get:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>

Sorry for the multiple posts.
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.

[Q] Windows 7 ADB Drivers / App restores w/o root?

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.