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)
Related
Hey all,
Away on holiday and trying drastically to s-off my desire s. Would do it at home via linux but being in cambodia, and using only Internet cafes, it has its limits.
I'm trying it on my hotel computer but I don't have the adb drivers for xp to detect it (only detects sd card)
Tried a few drivers but none worked. Can someone post up a zip to the desire s adb drivers please?
Cant install sdk as too big and long to do on someone else's pc
Thanks,
Dj
The only way is to download the SDK (which is a quite small file).
However, the only thing you'll have to do is:
- Run the SDK Manager
- Go to "Availible packages"
- Select "Google USB Driver package, revision 4" and download it.
These are all relatively small files, so it should be doable.
Good luck!
djstanley said:
Hey all,
Away on holiday and trying drastically to s-off my desire s. Would do it at home via linux but being in cambodia, and using only Internet cafes, it has its limits.
I'm trying it on my hotel computer but I don't have the adb drivers for xp to detect it (only detects sd card)
Tried a few drivers but none worked. Can someone post up a zip to the desire s adb drivers please?
Cant install sdk as too big and long to do on someone else's pc
Thanks,
Dj
Click to expand...
Click to collapse
Hello,
I don't believe that you require the ADB or the SDK!
Look at the APhaRevx website it has the following instructions
Boot your device normally, plug USB in, charge only mode. Enable USB debugging in settings, make sure 'HTC Sync' is UNINSTALLED (on Windows).
Windows - Install these drivers: HTC Windows drivers and run alpharevx as an administrator.
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
I believe you need the android usb drivers supplied by google to get it to connect. They can be downloaded using the sdk package manager. Also I'm not sure it will work having the Samsung drivers installed and you may have to uninstall them first.
they are installed already since i installed the whole sdk manager pack
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
ringnutz said:
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
thx for answer but I already done that..any other suggestions?
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
What drivers are showing up when you plug in the device? If it says Samsung then you don't have the android drivers installed. And I believe you can't have both installed only one or the other as only one will load when you plug in the device not both.
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
tzacapaca said:
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
Click to expand...
Click to collapse
When you plug the device in, under Device Manager in Windows, there should be listed Android Composite ADB Interface under the device. If not the Google USB drivers were not installed properly.
yeah I dont think my theme is the culprit, there are many reasons why ADB wouldnt show devices. Also Heimdall>Zadig is good for drivers.
run sdk manager and install latest google drivers as well.
are you on Windows OS?
nope,not your theme its the culprit..cuz i didnt install it and i cant install it cuz of no adb connection which is required by a tool named AutoDEOTool1.0.3
I installed latest google driver via sdk manager too..
yes,on Win 7 64 bits
*pulling hair*
I didn't have my usb cable yesterday to check it out but adb actually works with the Samsung drivers. Device Manager>Android Phone>SAMSUNG Android ADB Interface. And when I type the command "adb devices" it shows up. This works both if you plug the tablet in wihtout powering it up and when its turned on so I'm not sure what your problem is. I do have Kies installed on the laptop too so yours should be working if you installed the sdk and drivers correctly.
Which Tab do you have? I have the 6210 unlocked wifi only, it could be other models work differently. Not sure if you have a locked bootloader that you can access the tab through adb.
GT P6200 European
and here is what i get on cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tavi>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\Users\Tavi>adb devices
List of devices attached
C:\Users\Tavi>
EDIT:SOLVED!
Thank you all for answers
How did you solve this?
I input in cmd adb fastboot reboot and suddenly the device got the command and then recognized my tab..(pretty strange i know)
make it done
tzacapaca said:
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
Click to expand...
Click to collapse
do this steps:
1) remove battery
2)insert battery
3) connect the phone via usb will turned off and leave it till usb android phone installed
4) turn ur android phone on
5) wait for full boot
6) install Motorola usb driver .zip attached down there
7)select charge only mode
8) then write the commands of tacoroot.bin
9) when all is done hit the thanx button
ADB wireless
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Unitedforlife said:
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Click to expand...
Click to collapse
What do u mean adb wireless?
Hi, I'm having an extremly annoyning issue with my S8530. I can't seem to make Windows XP SP3 32-bit recognize properly my phone. I have install all the drivers I could find (old, new, from official site, from the undergorund of the internet) and it still gets stuck on detectic USB Serial Port giving just the message that something went wrong and it can't install driver (from auto-detecting devices from Windows). It did install Composit and Modem parts of the drivers but it allways stuck at that part no matter what driver I pre-install, how many restart I do to the PC, how many USB ports I keep chainging, how many USB cables I swap, how many restart I give to the phone. I'm starting going bananananananananananananananananananas.
Any ideeas are greatly apriciated.
Respect Ovidiu
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Renate NST said:
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Click to expand...
Click to collapse
ADB over USB so I can make Kies recognize my phone, wich won't work in Mass Storage. And it should be plug and play (after installing Kies wich installs the drivers or by just intalling the drivers alone). I don't have other machines to trie with Windows 7 (wich allways worked before) and my current PC barelly handles 5 open tabs of Chrome so no Windows 7 options here.
Plug your phone into the Windows box.
Go to Device Manager and find under Properties the VID/PID.
Check the INF file for the ADB driver and see if your IDs are in there.
If not, make a section like all the other sections with your VID/PID in it.
Install the driver.
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
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",