"Android Phone" not showing up in Devices after installing drivers from the KFU foldr
nvm
Download android sdk
Install and run the app under tools you'll see usb drivers. Download and restart computer and you are good to go.
I have an HTC Incredible 4G LTE. I underwent the process detailed here to unlock the bootloader.
When i got the HTCDev website, i ran a fastboot command and it just says <waiting for device>. I tried to detect the device with adb devices, and fastboot devices, but with no success. the THC Sync manager is not installed. HTC drivers should be installed. I am plugged into a USB 2.0 port, the same one used through out the process (i even tried the other one).
I am at a loss as to what is happening. I do know that the device manager sees my phone, and shows the drivers as the latest version. It does give this message:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
The device manager is listing the driver as version 2.0.7.3.
EDIT: Was able to get driver updated to 2.0.7.18
Also, when connected to the computer normally an orange light shows near the speaker. I wasn't concerned at first as I know the Android OS is not actually up and running on the phone, but do wonder if it doesn't indicated a problem.
Another note, I am running Windows 8.
EDIT 2: More research has yielded the following "Android Bootloader Interface". Every reference installing this from the usb_driver in the ../extra/google/usb_driver folder. When I attempt to do so from the device manager Have Disk ui I receive the following error
The folder you specified doesn't contain a compatible software driver for your
device. If the folder contains a driver, make sure it is designer to work with
Windows for x64-based systems.
Click to expand...
Click to collapse
EDIT 3: Removed entire android sdk, redownloaded and installed. Removed all HTC software and drivers. Booted phone into fastboot, and windows detected an "Android 1.0" device, installed the Android Bootloader Interface driver from the google usb_driver successfully. However, fastboot devices still does not detect the phone, and device manager still shows code 10.
As of now:
No HTC Sync, or HTC Driver
phone booted into fastboot, phone displays "FASTBOOT USB"
phone is set to usb debug
phone is connected to pc with good cable to a usb 2.0 port
I have:
rebooted pc, re-installed drivers, changed usb cords, changed usb ports, even tried a usb 3.0 port, i have tried some generic fixes for code 10 errors, and completely run out of ideas
EDIT 4: After using a different computer running Windows 7 I was able to complete the process, however, i would very much like toresolve the issue with my own PC, as the Win7 laptop is not mine. I utilized the adb/fastboot/winapi files from my Win8 machine. Win7 automatically found HTC drivers (2.0.7.18) and everything seemed to work just fine. Any ideas?
Hi friends,
I recently installed a fresh windows 10 latest build (16299).. I have 64 bit windows 10.. The problem is i cant install moto z play drivers on this build. I was able to install drivers on the previous build of windows 10 but on this build i failed... Motorola Device Manager is stuck at step 2 (Installing USB drivers)... I waited for hours but it is stuck... I tried closing and opening the app but still no luck... Tried restarting and then installing drivers but still no luck.. Everything else is installed perfectly including adb but i am unable to install moto drivers.... Can someone help... Without drivers i wont be able to even flash my device
Anyone??? I need to flash my device...please help
1) Install drivers from this topic https://forum.xda-developers.com/showthread.php?t=2588979
2) After that you will be able to manually assign Android ADB Interface driver to your phone in Device Manager
freeman_g said:
1) Install drivers from this topic https://forum.xda-developers.com/showthread.php?t=2588979
2) After that you will be able to manually assign Android ADB Interface driver to your phone in Device Manager
Click to expand...
Click to collapse
I already have adb installed and it worls fine...its just i am unable to install moto drivers on my pc... I even tried after disabling driver signature bull**** that was introduced in windows...
Those pack also contains proper ADB driver. You do not need separate Moto drivers, original ADB driver from Google will work fine too.
After installation connect your phone in fastboot mode to PC and go to Device Manger. Then update the driver of your phone in manual mode (when you have to choose from the drivers already installed on your PC) and choose Android ADB driver from the list.
Tried on windows 10 and 7:
Phone is detected by ADB and commands work no problem. Boot in to fastboot (download mode) and the device isn't found when using "fastboot devices". The phone appeared in device manager with the yellow triangle but I manually updated the driver to "Android Bootloader Interface" however, I still get nothing. Am I missing something?
Thank you.
Mine never has shown in fastboot, if it shows up in device manager it should work fine. To test just try fastboot reboot.
If you corrected the issue with the driver,the problem may be with the versions of Fastboot you are using. You can download the latest Fastboot and ADB files from Google directly if you search for them it should be the first or second link.
You need google usb drivers
I have the latest google usb and platform tools on a windows 7 &10 systems using different usb ports along with multiple cables and I can not detect the phone, but I can flash.
With Google Android SDK USB drivers (usb_driver_r13-windows.zip from 'Get the Google USB Driver') installed on a Windows PC, the platform-tools adb command can comunicate with the phone when it's in the Android system.
However, after booting into fastboot, the platform-tools fastboot command cannot communicate with the phone.
Does fastboot only work with the USB drivers installed by the miflash utility?
Or does it work with different drivers from Google or Qualcomm? If so, where to download them from?
There are countless sources claiming to be the Qualcomm drivers, but they are not authoritative.
Qualcomm puts all its downloads behind a login, but even after joining the Qualcomm developer network, I still couldn't find the drivers on there.
Gigajules said:
With Google Android SDK USB drivers (usb_driver_r13-windows.zip from 'Get the Google USB Driver') installed on a Windows PC, the platform-tools adb command can comunicate with the phone when it's in the Android system.
However, after booting into fastboot, the platform-tools fastboot command cannot communicate with the phone.
Does fastboot only work with the USB drivers installed by the miflash utility?
Or does it work with different drivers from Google or Qualcomm? If so, where to download them from?
There are countless sources claiming to be the Qualcomm drivers, but they are not authoritative.
Qualcomm puts all its downloads behind a login, but even after joining the Qualcomm developer network, I still couldn't find the drivers on there.
Click to expand...
Click to collapse
I always use the so-called Minimal ADB and Fastboot package (search by Google).
Starting from that it will further download additional drivers (when phone is connected in Android or in Fastboot mode - PC must be on Internet)
But you may have problems (preventing to recognize the phone in Fastboot) with your USB cable or USB port on the PC or even with some previously installed drivers - Windows wrongly recognize and try to use a previously installed driver instead and then it doesn't work in Fastboot
To clean up the previously installed USB drivers from the particular USB ports you may use USB Deview (google for, it's been couple of years ago when I had to use it last time)
Again, countless links to 'Minimal ADB and Fastboot package' downloads from untrustworthy sources such as dropbox, droidfilehost etc,
But anyway it was not necessary. Thank you for the suggestion to clean the device. I think the Google Android SDK USB drivers contains the bootloader driver, it just wasn't installed. The device manager just needed a nudge.
To recreate the issue...
Connect the phone to the PC via USB
In Windows, go to the Device Manager.
When the phone is in Android system, it is shown in the device tree as...
Android Device > Android Composite ADB Interface
...but when the phone is in fastboot, it is shown in the device tree as...
Other devices -> Android
...with an exclamation mark over the Android device to indicate it is not working.
To fix the problem...
In Device Manager, find...
Other devices -> Android
Right click Android, and select Properties.
In the General tab, click Change Settings. At the UAC prompt, log in with an Administrator account.
In the Driver tab, click Update Driver > Browse my computer > Let me pick from a list of available drivers on my computer > Android Device > Android Bootloader Interface > When 'Update Driver Warming' is displayed, click 'Yes'
Shows: Windows has successfully updated your drivers.
Driver properties now shows: Driver provider: Google, Inc
The phone shows in the device tree as:
Android Device > Android Bootloader Interface
Now Android platform tools fastboot commands work.
Gigajules said:
Again, countless links to 'Minimal ADB and Fastboot package' downloads from untrustworthy sources such as dropbox, droidfilehost etc,
But anyway it was not necessary. Thank you for the suggestion to clean the device. I think the Google Android SDK USB drivers contains the bootloader driver, it just wasn't installed. The device manager just needed a nudge.
To recreate the issue...
Connect the phone to the PC via USB
In Windows, go to the Device Manager.
When the phone is in Android system, it is shown in the device tree as...
Android Device > Android Composite ADB Interface
...but when the phone is in fastboot, it is shown in the device tree as...
Other devices -> Android
...with an exclamation mark over the Android device to indicate it is not working.
To fix the problem...
In Device Manager, find...
Other devices -> Android
Right click Android, and select Properties.
In the General tab, click Change Settings. At the UAC prompt, log in with an Administrator account.
In the Driver tab, click Update Driver > Browse my computer > Let me pick from a list of available drivers on my computer > Android Device > Android Bootloader Interface > When 'Update Driver Warming' is displayed, click 'Yes'
Shows: Windows has successfully updated your drivers.
Driver properties now shows: Driver provider: Google, Inc
The phone shows in the device tree as:
Android Device > Android Bootloader Interface
Now Android platform tools fastboot commands work.
Click to expand...
Click to collapse
Ofc that Google's SDK should contain drivers but I suggested Minimal.. since I always use them and it's the minimal/smallest package (as the name says, and self-contained) to download and install
Btw, there is a thread on XDA for Minimal..., that should be trustworthy I think
Anyway, it's important that it works now for you. And problem is usually with some mess on the PC with previous drivers
USB Deview is small, easy to use and powerfully tool for cleaning the old drivers that have been installed who knows when in the past
zgfg said:
Btw, there is a thread on XDA for Minimal..., that should be trustworthy I think
Click to expand...
Click to collapse
Thanks, found it here: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
The latest version minimal_adb_fastboot_v1.4.3_setup.exe, is 1mb, dated is Feb 2018, hosted on androidfilehost.com.
I guess Google's platform-tools_r33.0.1-windows.zip supercedes it, it's a little bigger at 6mb, but it's portable, so doesn't require any Administrator access to install, and provenance it clear.