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] Nexus S not responding in fastboot

Hi all,
I am noticing something with nexus s.
When in recovery or in normal homescreen, my nexus s communicates properly with adb commands
But there seems to be no communication from the nexus s when in fastboot mode.
Everytime I enter a fastboot command, I always get a "waiting for device" and nothing happens.
Am I missing something?
Thanks.
Heeter

If your PC is running Linux then you will need to be root.

No I am running windows 7
I got the Android 1.0 driver. Windows Device manager recognizes that my phone is hooked up,
But when I type in "fastboot devices" it is not listed there.
Thanks
Heeter

When I hook up my Nexus S in fastboot mode, I see this at the bottom:
Code:
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Everytime I unplug/replug USB wire, another "STANDARD_SET_CONFIGURATION" line gets added
I type "fastboot devices" into fastboot, and my Nexus S does not show up.
The phone is currently unlocked, but I would like to lock to reset it and start from factory rogers setup again.
Any help would be greatly appreciated.
Thanks
Heeter

You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::

rubbamade said:
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
Click to expand...
Click to collapse
I do have that already, rubbamade.
My Device Mangler is recognizing Android 1.0, and has the drivers for that I took from PDAnet.
The PDAnet itself couldn't install properly, so I extracted the drivers from the package and manually installed them through the Device Mangler.
I still cannot connect to fastboot.
Heeter

I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter

I guess you made your decision already in getting rid of windows lol. Anyway goodluck with the fastboot issue. And I hope the 3G issue is looooooog gone from your life. Take it easy
Arnel
Sent from my Nexus S using Tapatalk

LOLOL,
A whole bunch of thanks for that radio to you again
Heeter

Good choice ditching windows. Lol
Offtopic: how is debian compared to Ubuntu concerning repo n 3rd party drivers? Seriously considering switching to debian since Ubuntu adopted the crapy Unity
Sent from my Nexus S using Tapatalk

The driver isnt right if your phone wont show. You have to let windows find the correct driver out of the drivers you point it to. Either point it to x64 or x86 directory only. No further. Windows will find it.
Go to the fastboot thread in development and get the drivers.
Uncle Jimmy says hello

Heeter, it's maybe a bit late but unless you're really strapped for disk space you can keep Windows and create a separate partition for Linux, using the grub bootloader to choose between the two. I'm a Linux user myself (mostly Arch but I love to test most new distros) but I have lots of disk space and I keep an up-to-date Windows 7 installed for testing purposes and gaming.
Since - I have to admit it - I suck at most games, my Windows doesn't get used much but I don't begrudge the space it takes up. On Debian you should have less trouble with the adk and drivers - here's a good post at Howtoforge about using the adk http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-debian-squeeze

Heeter said:
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
Click to expand...
Click to collapse
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.

bender_123 said:
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
Click to expand...
Click to collapse
I tried that like 50 flippin times! everytime, PDAnet stays locked up during the pulling driver area. I have come back half hour later, still not complete. Then, when I unplug the cable, it spits out an error, and uninstalls itself.
What I ended up doing was, during the PDAnet install, it creats a root folder in C:/Program Files/PDAnet (or whatever it is). Now when it got stuck there, I went into that root folder, copied the "usb-win" driver package from there and set it aside. Then I went into the Device Mangler, and right clicked and manually installed the PDAnet driver.
Hiya Gun26, Thanks for that link. I am actually a site supporter on that site, if you search up "Heeter" over there. Been for a couple of years now.
I guess I could go back to dual booting, haven't done that in a long while either.
Heeter

That was just a suggestion about the dual booting - if you enjoy gaming, why give it up? Linux and Mac may be great (and BSD let's not forget) but for gaming it's either Windows or a console. I don't think you'll have any trouble with the adk and drivers on Debian. Good to hear about your connection to Howto Forge - it's a really useful site.

Thanks for that Gun,
I haven't had time to move back to Debian, and I really do like gaming once in a while.
I should be up and running dual boot this weekend.
Thanks again, guys.
Heeter

i'm having this same problem, it's rather annoying

[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

Pixel drivers on Windows 11

Hey there people,
I can't find a solution for this one, so here I am!
I want to transfer files from my computer on Windows 11 to my original Pixel, but I can't find a way to install drivers for it:
Automatic driver install does not work
Google USB drivers aren't compatible with it according to the device manager
Google drivers from the full list of Windows drivers don't work either
The phone is detected as 4 Pixels in the device manager, as well as a disk which isn't readable and returns nothing in the disk management service of Windows.
Any tip will be really greatly appreciated!
Thanks in advance to you all

BTW I tried the usual fixes: original cable, other USB port, reboot, changing the USB management setting to PTP/MTP… nothing works.

follow these instructions brother. The fix for me was to put the phone in fastboot mode before trying to install the Google drivers. You do that by issueing the command "adb.exe reboot bootloader",

Android drivers for windows

I have an rca tablet I can not get any drivers to work to get to replace/update the firmware and I was wanting to ask if anyone has found anything that works.
I have tried mediatek, rca and all other drivers I can find and nothing seems to work on windows 10 64.
Thank You

DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com

xXx yYy said:
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
Click to expand...
Click to collapse
Thank You will give a try

I have a Windows 7 64 bit system and I am trying to find drivers to access an rca rct6703w13
I have tried every driver I can find and nothing seems to work does anyone know something that will work?
I would be very grateful if anyone could help?
Thank You

Oh boy, I still remember this pain trying to find and use such drivers on Windoze:
- try another port
- try another cable
- try this driver or that one
- try doing a rain dance with 3 days old undies on your head, and turn only clock wise, unless it's full moon, then turn counter clockwise but stop briefly after ever two and a half turns
Maybe, as workaround, you could boot from a linux CD and try your approach from there.
Whenever I flash from my debian, it works: If "fastboot devices" still doesn't show anything then usually I have forgotten to plugin the cable

By using my "Yet Another Universal ADB Driver" Package (see the link in my signature) one can remove all the old adb drivers if that is the issue, but this case seems to be more interesting...
On win10 it seems that the adb is embedded to the winusb driver the same or similar way (registry wise) that my package is using. Now that I have tested, the behavior is similar with my devices. When using file transfer connection the adb is not recognized. With others, charging, photo, midi the abd works fine. To make adb work with file transfer one have to install the correct driver. In this case google's general driver could be okay, one match for vendor and product ids in it ...
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
What I tested using virtual win7 64bit, it seems to behave the same way... which is a bit weird as I've tested it with my driver package. Worked okay then I think. The Android device used has changed since though.. It worked on win10 back then too.. the change has to have happened later.. or I didn't use file transfer..
@steadfasterX 's maid or salt or whatever it's called nowadays might be usable in this case. It's a Linux having SP flash tool etc. available..
edit: tested and it turned out that the updated phone is the problem... using another phone my driver package worked as expected..

@resxwni01
1. Don't confuse USB-driver and ADB-driver: the USB-driver since ever is by default part of any OS, so also of Windows OS. The ADB-driver is an extra protocol what allows you to communicate with a phone's Android ecosystem via an USB-connection.
2. Latest generic ADB-driver ( correct: ADB client ) got released August 2022 and is officially versioned 33.0.3.
3. AFAIK a 64-bit version of ADB-driver doesn't exist.
With regards to install this ADB-driver on a Windows 7,8.1,10,11 PC:
It's NO USB-driver installer - as introduced above by @CXZa - needed what unnecessarily bloats the Windows registry with crap.
You
1. simply create on any mounted drive of Windows PC a folder named "ADB",
2. extract there to the 3 files what are in the attached ZIP file,
3. add path of created folder "ADB" to Windows environment variable PATH, thus ADB-driver is systemwide accessible -
how to is described here
How to Set the Path and Environment Variables in Windows
Information on how to set the path and environment variables in Windows 2000, Windows XP, Windows Vista, and Windows 7.
www.computerhope.com

@jwoegerbauer , you're funny guy...