[Q] Code 37 for SAMSUNG Android Composite ADB Interface - Samsung Infuse 4G

I've been trying for quite a while to get my Infuse to talk to ADB, still with no success.
I'm running:
PC:
Windows XP (32-bit) SP3
Samsung drivers from the AT&T website (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)
Infuse:
Firmware: 2.2.1
Baseband version: I997UKCH1
USB debugging turned on
No matter what I do, I get a Code 37 from the SAMSUNG Android Composite ADB Interface. (It shows up under "ADB Interface" in the device manager, but I get "Windows cannot initialize the device driver for this hardware. (Code 37)".)
If I disable USB debugging, I can mount the device with no problems in Media player mode or Mass storage mode.
I've also tried with the Kies package drivers and the Samsung driver from PdaNet, still with no luck.
I can debug an emulator session with no problem - just not the actual device.
I started with the guides here:
http://forum.xda-developers.com/showthread.php?t=1388644
I've tried the instructions for Epic here:
http://forum.xda-developers.com/showthread.php?t=1109374
and looked at the Galaxy issue here:
http://forum.xda-developers.com/showthread.php?t=1022272
I've tried with a Samsung-branded USB cable as well as a third-party one.
Any ideas what might be going on?

Do youvhave the android sdk installed? With the platform tools add on? Because adb is no longer in the sdk/tools folder of the android sdk ...its in the add on platform tools...then once installed you need to navigate to the platform tools to get advanced to work.
Sent from my SAMSUNG-SGH-I997 using xda premium

Yep, I've got the SDK installed - can run adb from the platform-tools directory, but it never sees my device:
C:\Program Files\Android\android-sdk\platform-tools>.\adb version
Android Debug Bridge version 1.0.29
C:\Program Files\Android\android-sdk\platform-tools>.\adb devices
List of devices attached

Related

Can not get Android 64 bit USB driver to instal

I am running vista ulimate 64 bit. I have the Samsung moment with Android 1.5. I can not get the usb driver to install on my computer.
I downloaded the android 64 bit usb driver from the sdk developer site, as well as an alternate download I found from one of the threads in this forum.
Followed these steps:
1) Type "bcdedit /set testsigning on" at an admin command prompt
2) Reboot
I have test mode in the corners...
When I point windows to the proper directory, it is not able to install the driver with the following:
Problem Event Name: PnPDriverNotFound
Architecture: x64
Hardware Id: USB\VID_04E8&PID_681C&REV_0222
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
HELP!!???
What do you mean by the first step, I have never seen that before in any adb guide? Just go to device manager, uninstall the current driver under adb interface and install the 64 bit driver.
are these the drivers you tried to install for your phone?
What are you trying to do on your phone, just see the SD Card?
I've tried several times to get these drivers to upload here and couldn't so use this link
Couldn't link either, good gosh
He said something about the SDK so I assumed he was talking about ADB...
@elephant007:
Hi,
My Windows7 is not detecting following drivers:
CDC Abstract Control Model (ACM)
CDC ACM Data
XDA
I am trying to connect my DIAM100 (Running 2.2 Froyo) as a USB Storage.
If you have the drivers can u email them to me?

[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] adb drivers

Okay, I know there are lots of posts about getting adb drivers to work on the g tablet but I can't seem to get to step 1. When I plug in my USB cable, my PC doesn't ask me to install anything. It just seems to assume that it is a USB drive. I tried to force the install via Install Hardware and pointed it to my modified android_winusb.inf file. When I did that it came up with three different options (Android ADB Interface, Android Bootloader Interface, and Android Composite ADB Interface). I tried all three but none of them will start successfully.
My cable connects to the mini-USB port (I have a keyboard connected to the full size USB port). I can't imagine that would make a difference, though.
I can copy files over to the g tablet from my PC; I just can't get ADB to work. What am I doing wrong?
First, you need to install the Android SDK on your computer. ADB shell is a program contained within the Android SDK. If you install the latest version, you also need to install "Android SDK Platform-tools" (launch the SDK and AVD Manager, then select the "Android SDK Platform-tools" package). You can connect the miniusb cable to your tablet and use adb shell, but I prefer to use adbwireless (free app in market); for some reason my computer won't recognize my tablet when connected via the cable. Then just open up cmd.exe (if you're using windows) and go from there. You'll need to locate the actual adb executable file, so you can run it in the command window. You'll also have to learn the commands as to how to do things, but lists of common commands can be found with a simple search.
I had problems with getting the debug usb drivers to install on a win7 dev machine. So I just installed adb wireless onto my gtab from the market. On my win7 box I just use 'adb connect x.x.x.xort' to use adb over the wifi.
It's pretty handy.
I figured it out. For others that run into this, I had to uninstall the drivers with USBDeview. I only uninstalled the one with a description of NVIDIA Tegra 2 USB Device. The second half of this YouTube video shows what to do for a phone:
youtube.com/watch?v=1UF5w1dKe2U
Then disconnecting and reconnecting the USB cable installed the drivers correctly. Weird.

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.

Need Help with ADB

I have read many guides about setting up and using ADB, I am using an older computer with windows xp sp3. I just got my first nexus device which is a nexus 5, in device manager the phone shows up as " samsung android phone" and then "google nexus adb interface". I have tried uninstalling and then reinstalling the drivers using many different ones found on xda. I have the android sdk installed and adb seems to be working, at least when I type in "adb version" the version number comes up, but when I type "adb devices" nothing comes up as attached devices. This is really frustrating me, as I have have been trying to get this working for days now.i have already uninstalled every other android related driver using USBDeview. If anyone could please help me with this I would greatly appreciate it. I'm almost to the point go giving up! Could the problem be because I rooted the phone before getting all this setup? I ask this because when I try to update the driver in device manager it always shows driver type as clockwork mod no matter what driver I try to use
Did you enable ADB via Dev Options on the phone?
theesotericone said:
Did you enable ADB via Dev Options on the phone?
Click to expand...
Click to collapse
Do you mean USB debugging, yes I have that enabled
Go to device manager select your phone (samsung device or whatever it's showing!!) and right click and select "Update Driver Software".
On the next screen, select "Browse my computer for driver software" and set the path to : C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
I have used C:\Program Files (x86) because that's the place in which I have installed the SDK. Put a tick mark on "Include subfolders" and then hit Next...
Your device drivers will be installed again and adb will be working!
PS: Please make sure you have the latest android sdk and usb_driver downloaded from SDK manager!!

Categories

Resources