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 .

ADB Help

I thought I had this figured out and adb and fastboot was working after I reinstalled usb driver from web--but
I can not type adb devices and have phone seen. I did reinstall driver per web directions and Device Mgr says it is up to date.
Attch 3 pics
1. is my comp Device Mgr screen. The opened Android Phone is where I updated from and says up to date. The opened Portable Devices shows G:\. I thought it use to show the device by name.
View attachment 807632
2. Is blackrose installer seeming to work but didn't proceed any further on it
View attachment 807633
3. Is Command Window
View attachment 807635
Any ideas what I am doing wrong. When I open Command Window I cd/
then type adb devices. Also tried it with sdk path selected. Debugging is on.
Thanks
Ken

I've never worked on my Nexus from Windows. But is it because it is mounted as a drive? As in, you mounted the SD Card for access in Windows when you connected your Nexus?

Thanks
but i didn't mount anything. just plugged in. phone says usb connected and and select to copy files. so, i didn't mount. in command window, as mentioned, i just opened window and typed cd/ then typed adb devices
sorry if i misunderstood your comment
what about the adb server outdated comment in command window?

I just did a fresh adb install the other day and allowed SDK manager to update all drivers and tools. I installed the SDK zip to the root of my C:\Drive
Note: ADB moved from \tools to \platform-tools\
After plugging my phone in and turning on USB debugging, I type:
CD\
CD androidSDK\platform-tools\
ADB Devices
Then you should see a serial number for your phone.

i just got to that point while you were posting
too bad my blackrose and hypersense files are gone
however, i have no platform-tools in sdk. only platforms with android-2 thru android-8
and mine is platforms not platform per note
trying to install it too platforms and get path right. don't see how to install from SDK and AVD
i have nothing listed in avd manager

can't get sdk r15 to install with platforms-tools
can't fetch repository and can't get to screen where you can change https to http to allow fetching of repository

well after unsuccessfully trying to update sdk and not getting the repository I restored the android folder from full image bu I made with Acronis
still saw in tools that adb had been moved to platforms-tools, which I did not have
I found adb under the temp folder and re exe it and it moved back to tools and after adb start-server was able to get adb devices working
not sure how it got moved

[Q] minSdk(API 8) > deviceSdk(API 1)

Hello,
Trying to get Nexus 7 (2013) Lollipop to operate with Android Studio v1.0.2 on a Windows 7 platform.
minSdkVersion 8
targetSdkVersion 21
When Run/Choose Device is displayed, and a real device is selected, I get the following error:
Error: minSdk(API 8) > deviceAdk(API 1)
These are my settings for the SDK/Extras:
I cannot locate any setting for the deviceSdk level, so I have concentrated on the ADB driver itself and currently have the latest_usb_driver_windows.zip - Google 32/64 ADB Driver - "Android Composite ADB Interface" installed. This driver is dated 8/28/2014.
A previous driver http://www.koushikdutta.com/post/universal-adb-driver
from ClockworkMod had been installed with the same results. ClockworkMod, Android Device, "Google Nexus ADB Interface"
Several system restarts have been done after ADB drivers have been changed.
Can someone please direct me to the answer for the deviceSdk API level error?
Thank-you.

It appears to be FIXED! I confirmed the functionality only yesterday.
Not sure exactly what the issue was, but I noticed that jre1.8.0_31 kept wanting to load an update. Apparently the JDK/JRE pairing was in error.
Removed JDK/JRE7; reinstalled JDK/JRE8 for Win64.
Environment Variables
ANDROID_SDK_ROOT
C:\Users\<name>\AppData\Local\Android\sdk
JAVA_HOME
C:\Program Files\Java\jdk1.8.0_25
With this configuration I can now use an AVD and can use the Debug facilities (Breakpoint, Step, StepOver).
caprock said:
Hello,
Trying to get Nexus 7 (2013) Lollipop to operate with Android Studio v1.0.2 on a Windows 7 platform.
minSdkVersion 8
targetSdkVersion 21
When Run/Choose Device is displayed, and a real device is selected, I get the following error:
Error: minSdk(API 8) > deviceAdk(API 1)
These are my settings for the SDK/Extras:
I cannot locate any setting for the deviceSdk level, so I have concentrated on the ADB driver itself and currently have the latest_usb_driver_windows.zip - Google 32/64 ADB Driver - "Android Composite ADB Interface" installed. This driver is dated 8/28/2014.
A previous driver http://www.koushikdutta.com/post/universal-adb-driver
from ClockworkMod had been installed with the same results. ClockworkMod, Android Device, "Google Nexus ADB Interface"
Several system restarts have been done after ADB drivers have been changed.
Can someone please direct me to the answer for the deviceSdk API level error?
Thank-you.
Click to expand...
Click to collapse

Driver installation problem.

My OnePlus 3T, in recovery is installing as " LeMobile Android Devices, Android ADB Recovery Interface"
i am not able to install in sideload mode, can anyone help?

For Windows:
A few steps to get rid of the LeMobile pesky driver (or another driver for PnP devices).
1. Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2. Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3. Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4. Go to the device manager. Do not refresh of rescan! Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver
5. And You're done!

nAFutro said:
For Windows:
A few steps to get rid of the LeMobile pesky driver (or another driver for PnP devices).
1. Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2. Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3. Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4. Go to the device manager. Do not refresh of rescan! Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver
5. And You're done!
Click to expand...
Click to collapse
trying to install driver from oneplus driver folder, it is giving me that the driver is not for windows 10 64bit

tekken1972 said:
trying to install driver from oneplus driver folder, it is giving me that the driver is not for windows 10 64bit
Click to expand...
Click to collapse
Have a look at https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
The toolkit has the drivers. OnePlus is being weird with drivers. I've read from another user that OnePlus is using the driver download internally but it is not yet published.

nAFutro said:
Have a look at https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
The toolkit has the drivers. OnePlus is being weird with drivers. I've read from another user that OnePlus is using the driver download internally but it is not yet published.
Click to expand...
Click to collapse
Did all the above still could not install the drivers.

Problem solved by latest windows 10 64bit update
Google, Inc. - Other hardware - Android Bootloader Interface

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