I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
LOL, I just switched back from Ubuntu to Windows 7 just to see how things have progressed. There are so many little Windows 7 quirks that drive me crazy that drove me back to Ubuntu almost instantly. Give Linux a try. A good starting Linux OS would be Linux Mint:
http://www.linuxmint.com/index.php
I had a similar issue when I tried it. Despite the fact that there are 64-bit drivers for Vista/7 available, I don't believe they actually work for ADB currently. I'm pretty sure everyone who has ADB working is using Windows XP 32-bit.
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
ch4dr0x said:
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
Click to expand...
Click to collapse
I faced the same problem a few days ago. I have Windows 7 Ultimate x64 and in a first installations the drivers work fine and the device has been displayed, but BAM when I try to use ADB no way.
After many tries I resolved the issue running the Command Prompt as "Run as administrator" and VOILA worked fine.
I hope this can help you.
ch4dr0x said:
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
Click to expand...
Click to collapse
Try Mint instead of Ubuntu. Mint is Ubuntu based. The big difference with Mint is that it already has all of your codecs installed - great for beginners.
If you installed first the htc sync, you have to remove the current drivers..
and had the drivers from the androidsdk pack! There's is a a lot of program who delete usb installed hardware/drivers.. delete all from htc on this programs!
Hope this solves ur issue!
I use Win7 64bit(rc1) .. i have the amd64 driver installed..
I see the phone from adb (not fastboot) when it's normally connected with USB debugging turned on.
I see the phone from fastboot (not adb) when it's in fastboot mode.
I have no choice but to laugh at myself, just realized I was IN FASTBOOT on my phone and not recovery. Fail me.
Now if I could just edit this apps2hd code /sigh.
ricardomega said:
If you installed first the htc sync, you have to remove the current drivers..
Click to expand...
Click to collapse
and remove htc sync, there are a process than cause problem with adb (i don't remember the name)
I kill this process and adb 100% work fine, or unistall HTC Sync..
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
ricardomega said:
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
Click to expand...
Click to collapse
Except that... that wasn't my issue Its ok thanks for the input.
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
parrot5 said:
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
Click to expand...
Click to collapse
The same confi, the same result
Everything works fine here with Win 7 Ultimate x64, you just install the driver in the Android SDK.
make sure u have usb debugging checked... cause i have windows 7 rtm ultimate and my adb works fine... i just loaded the needed file into windows/system32 and also put my fastboot.exe in there and added the tools folder to the environment variables and have no problems
What do I load to the system32 folder? I can't install the drivers from the SDK package. Is there a way to overwrite the ones Windows automatically installs and thinks is more up to date?
detonate said:
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
Click to expand...
Click to collapse
Make sure your phone is in recovery mode and NOT fastboot mode.
Finally, I experienced that error you people had been reporting. It MAY have to do with the HTC Sync driver, as suggested, but it really had worked fine with other roms before, so I am not sure. I tried uninstalling and reinstalling the driver, tried to push the ADB driver manually, but that didn't work. And, before I try to uninstall the HTC Sync driver as suggested (I don't even know if I have that installed), I got it working by just plugging in another USB flash drive. Go figure.
So for anyone still having the issue after trying all other solutions, try this bizarre one:
1. Go to device manager and uninstall the HTC disk drive device. (This alone won't work, I tried)
2. With phone still plugged in, plug in a USB disk drive (or maybe just any USB device?) into another USB port.
3. Suddenly Windows 7 detect that unknown ADB driver, as it should. Now you can go ahead to install the correct ADB driver.
As a side note, this computer running Windows 7 Beta/RC have had a lot of problems with USB disk drives in general. The problems disappear after Windows 7 RTM (final).
Is the Captivate not able to see the Captivate when it is plugged into the computer? I have windows 7 running via VM Ware on my Mac, Because that is all I have, and it won't see the phone. I want to use the Odin Stock restore but if it won't recognize my phone I guess I can't use it.
Chris
What version of vmware? Not sure on the mac, but is there an option for it to pass usb through to the vm? Did you install the drivers in the win7 vm for the captivate? More details would be helpful.
Yeah I installed the drivers on win 7 in VMWare, Its on a mac. Its VMWare Fusion3. When I plug it in my Comp asks me would you like to mount in OSX or windows and I click Windows and it just won't mount. So if I try it with debugging mode on It will mount onto the Mac no matter if I select OSX or windows. So i'm just wondering if the samsung USB can't connect through VMWare.
do you have the android sdk installed on your Win 7 VM?
The reason I ask is because you could run "adb devices" in a command prompt on the vm to see if the VM is seeing the device at all.
it sounds like it may be a bit easier to just boot camp your mac if you have access to you windows 7 disk, just create a small partition that you can go back to in times of need
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)
I downloaded the uber files tonight to root my HTC Thunderbolt. However, when I moved onto the second step using ADB, I've hit a bit of a snag.
While I am seeing the device listed under devices, it's telling me it's offline. This despite the fact I can copy files to and from the microSD card, as well as internal memory. Below is what I see at my terminal:
[email protected]:~/Desktop/ThunderRoot/downgrade$ adb devices
List of devices attached
HT14DS015334 offline
I am using Ubuntu Lucid Lynx 10.04 32bit version. At this point, I'm guessing it has something to do with the HTC drivers since I didn't install HTC Sync (there is no version in linux, right??)
Anyone on here use linux with their Thundebolt? If so, are you connecting it via ADB??
Thanks,
Robert
I use 10.04 64bit and 11.04 64bit all the time with ADB. You don't need drivers with Ubuntu.
offline means it sees it but it's not connected. try replugging it in and/or kill the adb server and restart it.
as stated above, you do not need drivers for Ubuntu.
try adb kill-server
then adb start-server
you might also need to start the server as root.
UGH!! Turns out the problem was debug mode on the phone. Or rather the fact it WASN'T in debug mode!!!
Enable/Disable USB Debugging Mode - HTC Thunderbolt ADR6400
Once I changed that it showed up as device!!!
Anyone done this in an Ubuntu 11.04 VM in VMware workstation?
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