Database Info

Unable to find Samsung Intercept ADB drivers, help ?

I can't seem to find the adb drivers for samsung intercept. I tried pointing to the usb drivers folder in SDK/tools directory.

bump! help

Intercept - Windows USB Drivers and ADB Tool Software
Here are some links:
1.
Intercept Windows USB Drivers
http://forum.sdx-developers.com/intercept-guides-and-tips/samsung-intercept-usb-drivers/
2.
ADB Tool Software
http://forum.sdx-developers.com/int...steps-to-install-adb-tool-on-your-windows-pc/
Hope, this is sufficient.

[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.

[Q] Code 37 for SAMSUNG Android Composite ADB Interface

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

[Q] Root one phone using another phone

I just had an idea. I know you can root some phones using ADB and I got to thinking. All android phones have an ADB daemon running in the background that you can connect to through usb on your pc using the ADB client application provided by google(adb.exe) and usb adb drivers provided by google.
Now that you can turn your phone into a USB host using USB OTG, wouldn't you be able to use your phone instead of a computer? With a Micro-B to Micro-B USB cable? Someone has already ported the ADB client to android(ARM-Linux ELF). So someone would just need to port over the drivers to android, and then we could connect to adb on one phone using another with a terminal emulator. Right?
What are your thought?
I have attached the adb and fastboot clients that were ported to android. (adb-fastboot for arm)
EDIT:
I found this for raspberry pi (which is arm based):http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130

So after reading a bit more it seems that the drivers aren't even needed. They are only needed when using ADB with windows. But, since Android doesn't use "udev" I don't know if or how android would recognize that another phone is connected.