Database Develop

Problems with ADB install..

Hello all,
I have been following the guide posted by Nephron http://forum.xda-developers.com/showthread.php?t=532719 but am having a few problems with my computer recognising my G1 as an ADB device...
My computer's OS is Vista. I have followed the guide to the letter, have downloaded the SDK and unzipped it to C:\ root. I have checked my phone and ensured that 'USB Debugging' is checked. My computer doesn't try to install the Android 1.0 driver (as the original drivers are already installed) and my device is ready to use as a storage device - HOWEVER it is not acknowledging it is an ADB device.
I have tried using USBDeview but it won't let me uninstall the 3 already installed Android drivers. I have even tried manually uninstalling them through the taskbar USB device manager. Even when I uninstall them and re-connect my phone, it automatically installs the standard drivers and doesn't give me an option to select the SDK drivers.
Hope that makes sense to someone. How can I install these damn SDK/ADB drivers on my G1?! Thanks.

Try this...
Remove every mass storage device except your phone (Any usb memory sticks, external HDD's, other phones, etc)
Open the start menu, right click on 'Computer', click 'Manage', and you may need to click continue here.
On the next page, click on 'Device Manager' on the left hand side. In the list on the right, open up the tree for 'Universal Serial Bus Controllers'
Find 'USB Mass Storage device' in the list. Right click it, click 'Uninstall'
Click 'Action' at the top, then 'Scan for hardware changes'.
If it all goes well, you should now be asked to locate a driver, point the the Android USB driver. Good luck.
PS, this is all from memory of the issues I had, so if you get stuck, post back .

Worked a charm, thanks!
(Mods...can this be merged to the NEWBIE Q&A thread for ADB/Fastboot etc...more useful place for it than here!)

Glad I could help .

OK...
New problem...
I am using command prompt on vista, entered the following:
cd C:\android-sdk-windows-1.5_r2\tools
adb devices (shows my device listed as HT845KV02724)
adb shell (shows a # on the following line)
However....when I enter adb it returns with /sbin/sh: adb: not found .....what have I done wrong? I have checked that the SDK is in C:\ and have downloaded the SDK again just to be sure. What do I need to change???

Once you type adb shell, you're in a terminal on your phone, you can type shell commands there, you need to type exit before typing adb again.
Basically, it's working as intended .

G! shows as "Unknown device" in device manager - Can't Connect!!

for the past 18 months I have been able to access my G1 via USB. I could mount it easily and ADB was set up correctly. for some reason this week, it stopped working. now when I plus it in, I get the "USB Not Recognized" error in XP, and my device no longer shows up as an adroid phoen in Device Mgr. It now says unknown device.
I have tried updating the driver with no luck.
Any ideas would be great,
Thanks

Something similar happened to me. After trying to mess around with Live Wallpapers and DroidExplorer, my phone doesn't show up. I get the "Error: Device not found".
I have the latest USB driver, but yet device manager keeps saying that it's up to date when I try to reinstall (however under Driver Details, Vista says the location of the drivers are on System32 and they're Microsoft drivers....)
Edit: after searching Google for answers, I stumbled on a Google Group and found that someone fixed their issue (similar to mine) by installing HTC Sync. I did, and voila! ADB works again.
http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169

OUTSTANDING!! That did it. Thanks a bunch, and thanks for the link!

fixed for real now
So the above didn't do it for me, here's what I did:
download and extract USBDeview
Open it up and remove the 3 or 4 entries that say "android phone"
Unlplug (if its plugged into USB) your phone and replug it in, the "found new hardware" window should pop up and be sure to install the drivers that came with the SDK.
That took care of my USB mounting situation, but I still couldn't get adb or fastboot to see my device. Turns out I had adb.exe and fastboot.exe in my WINDOWS/System32 folder as well as in the SDK/tools folder (prolly from when I updated the SDK). Having them in 2 spots seemed to cause problems so I removed them from the SDK/Tools folder. Alternatively I could have removed the other set, but I didn't want to go to my SDK folder every time to use them, this way I can access ADB from any folder on my computer.
This is all from memory so if something's not clear, lemme know. All I know is ADB and Fastboot are working now.

adb devices

Hello
Im brand new to Android and adb/fastboot.
I have looked at tutorials on youtube all day, and for everybody else their devices just pops up when you type adb devices.
I get nothing
I have done it correctly, because I get all the commands when I type adb/fastboot.
Im running windows8, could that be the problem?
Do I need some kind of extra USB drivers for my google glasses?
I do find my glasses as a camera tho.
EDIT:
So after watching a few more tutorials I understood my problem. Its windows8 usb drivers thats not correct.
I have tried to install correct drivers and edit the .ini files that need editing, but now I encountered a new problem.
Windows wont let me install correct usb drivers for google glass.
When I have device manager open, windows have already installed them as “Portable device – Glass1″
I click uninstall and they disaper from my device list, once I click “scan for new hardware” I can see that they reapper on my device list as other devices. Within 2sec windows autoinstall them as “portable device -glass1″ again.
So I try “update driver software” but this dont work either, I select the correct file and path, but I keep getting this message “windows has determined the driver software for your device is up to date”.
Im running windows8.
Any help is appreciated.
EDIT2:
As far as all the tutorial movies tell me to disable driver signing I have done so.

If all of the adb commands were working, then chances are you need to enable debugging on your Glass. Settings >> Device info >> Turn on debug

Update:
The way to bypass windows8 and installing usb drivers, is that I need to use the option "Have Disk" and then install usb drivers that way.
All works fine now.

[Q] Windows 7 ADB Drivers / App restores w/o root?

I'm looking to port app restores - mostly game saves - from my old phone to the Droid Turbo. I've used Helium in the past but I can't get the Turbo to connect to Windows 7 yet. I've been trying to use the drivers linked from the Helium URL and here, but without success.
Anyone have luck tracking down USB drivers?
Any suggestions other than Helium?
Update:
Looks like the Motorola drivers started working as soon as I posted this (of course...).

This one was driving me nuts the last two days. On Win8.1 x64, the driver wouldn't auto-load when the device was plugged in. Until I saw your edit reason, I didn't even think to go through the manual device list and select the driver manually. "ADB Interface/Mot Composite ADB Interface" worked for me, as well.
Also, if you change your USB Storage mode on the phone, it may also change how the ADB Interface is detected. I had to manually add the ADB Interface driver a second time when I turned on MTP mode for the USB Storage connection. I had had it previously disabled while trying to figure out the ADB issues, once I had ADB working, I re-enabled MTP and subsequently Windows "forgot" the ADB device driver again.

For others: I had to go through the device manager, pick the unknown adb device and update drivers, pick drivers, select the clockworkmod section on the left and instead of mot composite I had to use the first option, android composite adb interface. Now my mtp connection works. Haven't tried reconnecting yet so it may well forget the drivers again, but at least I know what to do now!

Need the drivers from google sdk kit. Just google search installing adb drivers. I used helium fine.

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?

Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.

Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!

OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse

mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!