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.
Related
Solution:
If you were like me, you couldn't get ADB working no matter what you did with the drivers. As it turns out, I was plugging it into a USB 3 port on my motherboard. I have the USB 3 drivers installed, but there seems to be an adb issue with USB 3 ports. be warned, my issue is now fixed (I probably don't even need them bootleg drivers either). Thank You XDA.
Alright, so I just picked up a Galaxy Nexus (coming from Thunderbolt) today only to find out that my sdk will not detect my phone in adb devices. Now, I have the Thunderbolt and Eris working fine with it, but the NExus seems a little stubborn. Here are the steps I have taken:
1. Plug in phone, wait for win7 (x64) to install all the drivers... Success
1a. MTP and PTP both installed, using MTP for the rest.
2. Turn on debugging on my phone one more driver... Success
3. Went to the GNex Samsung support page to download and install that driver... Success
4. Go into Device Manager, everything is A-OK, drivers all happy
5. Open up my sdk prompt and type adb devices and 1 device is found, offline
6. Type it in again, nothing, maybe a glitch?
So there is nothing wrong in Device Manager, no Windows Updates, SDK works fine, but no device under adb devices. This is honestly the strangest thing ever.
If you have any special instructions regarding drivers, please be specific, stating "update your driver" doesn't really help.
Oh, and this is my first post I believe.
Update your drivers :laugh:
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it.
Srsly though...
If that doesn't work...try the PDAnet option.
My sig has a link.
Install PADnet and plug your phone in.
Then check that the new driver is the one in use.
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
efrant said:
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse
Noob question, but how do I install those drivers?
epicrevolt said:
Noob question, but how do I install those drivers?
Click to expand...
Click to collapse
Is that a joke?
efrant said:
[snip]
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse
Alright, so I have done the following:
Uninstalled all Samsung Drivers through Device Manager
Unplugged phone
uninstalled those official Samsung drivers for the GNex (available for download on their site)
Plug phone back in, both MTP and Nexus unknown
install the 1wayjonny driver... Success (It's now under Android Device in Device Manager)
adb still doesn't work... f*ck
reboot phone into fastboot (vol +/- & power)
install 1wayjonny driver... success
fastboot device recognized by 'fastboot devices' and commads work.
I believe the issue is with the MTP device as it is not recognized so therefore I can't access the phone storage. So far the only way I can get MTP working is by using the official Samsung driver, but that overrides the ADB driver by 1wayjonny (no way around it, even through uninstallation and choosing the 1wayjonny driver, Samsung one is more 'recent').
In the attachment you can see that the MTP device has no driver and therefore is unavailable.
Thank you so much for the help so far.
UPDATE: MTP Driver downloaded through Windows Update, divice still not showing up in adb. Actually when I first run adb devices after kill-server it finds the device as offline, but as soon as I type 'adb devices' again, it's gone. poof.
Hello,
I have searched the forums and Google, and was not able to find anyone else with this issue, so here I am.
I'm on Windows 7 x64 with a stock Canadian Galaxy Nexus 4.0.1 (yakjuux.)
I am trying to install GNex Toolkit and am unable to get past the first step. No matter what I try to do, any time I plug in the phone, it installs the default drivers.
Device installation settings are set to "never install drivers from Win Update." Phone is in development mode, I have removed Google Nexus from my devices (and checked the "delete drivers" box, though it doesn't even appear anymore), there is nothing for Samsung in Programs and Features, I have used USBDeview and there is nothing for Samsung/Nexus. I've tried using PDANet to no avail (I get error 103). I tried using "uninstall drivers" with GNTK, no dice (it seems to just remove a registry entry).
Any other ideas on how to make my PC install the drivers I want and not the default ones?
Thanks.
Read part A of this post.
efrant said:
Read part A of this post.
Click to expand...
Click to collapse
I have read that entire post and Bourne-nolonger's guide. Instead of showing up as "Android 1.0" device in Device Manager, my phone always shows up as Galaxy Nexus, with no yellow triangles or any other issues. (Yes, developer mode is enabled, and it seems to make no difference to how my computer responds.)
From Bourne-nolonger's guide:
"As soon as you enable this Windows will pick up a new device and it will attempt to install a driver - this will fail (or hopefully it will)." - mine never fails, it always installs drivers from somewhere. When I attempt to install new drivers to the Google Nexus device using UNK 0.7, Windows tells me that I already have the newest drivers.
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Scarf Face said:
[snip]
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Click to expand...
Click to collapse
Absolutely.
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
edit: tried doing the same in fastboot mode; the Device Manager recognized it as Fastboot mode, but did not let me install the proper drivers, saying that I already have the newest ones.
Scarf Face said:
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
Click to expand...
Click to collapse
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
efrant said:
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
Click to expand...
Click to collapse
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Scarf Face said:
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Click to expand...
Click to collapse
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Click to expand...
Click to collapse
Seems to be a problem with my PC, so I will try it with a different machine. Thanks for your help!
Ignore this. Wrong thread.
I try to unlock my My galaxy nexus bootloader but every time i connect my phone to pc in fastboot mode, it appears nothing. I had tried many google usb driver yet it didn't help. Can anyone suggest me solutions?
In fastboot mode it said:
Product name - tuna
variant - maguro
HW Version - 9
Bootloader version - PRIMEKK15
Baseband Version - SC04D0MLE3
Carrirer Info - None
Serial Number - 0146B0000E01701C
Signing - production
Lock State - Locked
There is number inside this device: SC-04D <Titan Silver>
It's currently running adroid 4.1.1
Build number: androidME_v1.2_GNexus-build_cdtdroid
Are you in windows, linux, or mac? I had a problem getting it to install the fastboot driver for my GalNex on my Asus G73 laptop in windows so it might be a similar problem. What I did was download and install the android sdk including the optional google driver, and then manually install it from the device manager. If you've installed drivers from different sources windows caches them and when you connect a new device it may use the old driver even if you've uninstalled it.
To install the driver manually make sure the phone is connected and in fastboot mode
then go to control panel -> system -> device manager
then select whatever the galaxy nexus is listed as. probably samsung phone or something along those lines.
right-click and select "update driver software
click "browse my computer for driver software" then "let me pick from a list of driver software on my computer" and finally click "Have disk..."
this will open a window for you to select the driver so hit browse, and in the explorer window go to the android-sdk folder where you installed the sdk and find the %android-sdk%\extras\google\usb_driver folder. then select the "android_winusb.inf" file. After clicking ok and ok it should list 3 drivers. I can't remember which one it is but I think one of them is a fastboot driver (If I remember correctly they're adb, composite-adb, and fastboot).
After it's installed open a command prompt and put in "fastboot devices". if there's a device id listen then it's working.
edit: the driver I refer to can be acquired here: http://developer.android.com/tools/extras/oem-usb.html
it says "The Galaxy Nexus driver, however, is distributed by Samsung (listed as model SCH-I515)." but that refers to the Verizon version.
it's working
Thank you I followed you instruction and it's amazingly working :victory:
This may help... it worked for me...
The reason the driver isn't being recognized by Windows, is that you need to edit the android_winusb.inf file. Let's now go through some simple steps to show you how to enable the Android Composite ADB Interface.
1. Download and Install Google USB Driver (yes, the generic Google USB driver, even though the Galaxy Nexus uses the Samsung USB driver in normal USB mode)
2. Next go to Device Manager and right click on Android 1.0 driver and click Properties
3. On the 'Property' drop down look for 'Hardware ids'; you should see two values like this:
USB\VID_18D1&PID_4E30&REV_0100
and
USB\VID_18D1&PID_4E30
Write down the USB\VID_18D1&PID_4E30 you will need to copy this to android_winusb.inf
4. Go to the USB driver folder and open android_winusb.inf with notepad and create a new line under 'Google Nexus (generic)' adding the above PID as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E30
*Note: There are two sections where 'Google Nexus (generic)' is found; add this line under both the "Google.NTx86" section and the "Google.NTamd64" section if you are uncertain.
Now save the file to same location
5. Next, go to Device Manager (Computer Management) > Other devices > Android 1.0
Right click on Android 1.0 driver and click 'Update Driver'
Browse to the USB drivers folder and open android_winusb.inf (Use Browse my computer for driver software)
6. Windows will present you with a pop up saying "Windows can't verify the publisher of this driver software"; click > Install this driver software anyway
7. You should now see a message "Windows has successfully updated your driver software"; make sure the driver description looks like this > Android Composite ADB Interface; then click > close
8. Device Manager will now label the device driver > Samsung Android Phone > Android Composite ADB Interface
my galaxy nexus is'nt showing in pc...its charging...but cant connect in download and fastboot mode...even not showing in device manager...tried diiferet usb cables...plzzz help me...sorry for bad english
Thanks for instructions. It worked.
I have my new Nexus 5X with Android 6 on it. I am trying to unlock and root.
I have enabled USB debugging and OEM unlock.
I have downloaded and installed the SDK package with Platform-Tools and drivers in the 'Extras' folder.
When first plugging in the phone I install the drivers with the 'Have Disk' and browse method.
Every time, installing the driver returns an Error 'Code 10 - device cannot start. 'Android ADB interface' shows up in device manager when I plug in the phone but with an exclamation point.
I have uninstalled, downloaded fresh drivers from other sources, reinstalled, tried plugging the phone in while in 'recovery' mode (starting by pressing all 3 hardware buttons).
I uninstall every time and reboot both the computer and the phone. The drivers simply won't work.
What is going on here? Is the phone/Android 6 still too new to unlock and root?
P.S. I should also say that I go into Developer options and change the Select USB Configuration between PTP and MTP (between which, I have not seen mention of the correct choice. Does it not matter?) - I cannot chose the others RNDIS, Audio Source, or MIDI; it seems to want to default to 'Charging' when I try to change to these choices.
Having the same issues on Windows 8.1. Can't get my 5x to connect to transfer files or to show up in adb.
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
bsinc1962 said:
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
ahunter said:
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
Click to expand...
Click to collapse
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
rgerrans said:
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
Click to expand...
Click to collapse
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
ahunter said:
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
Click to expand...
Click to collapse
Sorry. I should have been more specific. Part of it is I did so many different approaches they've bled together in my head and I was on my way out the door yesterday when I fired off the reply.
To try to break it down from memory (going to throw in a couple of different options since I can’t seem to fully uninstall / reinstall so please provide any corrections once you get it to work or let me know if anything doesn’t match what you find and I’ll try to remember from there):
Phase I (phone on and connected to computer):
Open Device Manager. My phone shows as Android Device | Android Composite ADB Interface or Android ADB Interface.
If it is the Composite version, I believe I had to update it to the straight “Android ADB Interface to get Phase II to work)
If you don’t see that, look to see if you have any uninstalled devices by scanning for new. If so, then right click on that device, and choose “Update Driver”
Choose “Browse my computer for driver software”
Choose the “Have disk” option and browse to your USB Driver folder
From there, choose “Google | Android ADB Interface”
Phase II (phone in recovery connected to computer)
On phone, choose “Update device from ADB”
Open Device Manager and you should see the Nexus 5 under Other Devices with the yellow triangle.
Right click on it and “Update Drivers”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list….”
Choose “Android Device”
Choose “Android ADB Interface”
Now you should be able to push the update over
Simple method: What I did was plug it in and wait for it to show up in device manager. Then I deleted the device (the one that shows adb) from device manager. Then I unplugged the device and plugged it back in... Then waited for drivers to install on it's own. Everything was good after that.
I have no trouble other than on Windows 10. Windows 10 doesn't even show the drivers from a list to install.
Sent from my Nexus 5X using Tapatalk
I followed this to get my Nexus 5X detected on my Windows 10: http://stackoverflow.com/questions/...ould-we-use-for-the-nexus-5/19839812#19839812
I have no trouble with Fastboot or adb. It only happens when I try and sideload. I end up have to use my Macbook Pro to sideload.
Sent from my Nexus 5X using Tapatalk
bsinc1962 said:
Just need the right drivers. Download the driver files from here:
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I wish it were that easy. But, no, this does not work. Nor do I believe my issue is the same as you others here, as I have Windows 7 and not the 8.1 and 10 issues that you are having.
No, no matter what driver I use, including any from your kind link, bsinc1962, they return an error, code 10 when trying just to install the drivers. I cannot go further.
What is this Code 10 error preventing drivers from installing?
For the past few days I've been trying to pass SafetyNet with root and after I failed, I tried to unroot my phone as passing SafetyNet is more important to me than having root. In the processing of doing so, I messed up some things on my device. I flashed all uninstalllers of SuperSU, Xposed, Magisk and other stuff I flashed through TWRP and deleted all SU files in bin and xbin. It removed root but I still wasn't able to pass safety net. I then messed up somehow and removed my TWRP and now when I try to access recovery it simply boots up my phone. I decided it would be the best to simply reset my phone using fastboot and adb (maybe even lock the bootloader again?). Fastboot however, cannot detect my device while abd can (not in the bootloader menu though). I have searched arround on the internet, have installed tons of drivers, reinstalled the SDK + Android Studio,... but I can't seem to get it work. When my device is booted up, it shows in Device Manager as "ONEPLUS A3003" and when in fastboot mode, it shows as "Android Bootloader Interface". Updating the drivers doesn't help. Would love if someone was able to help me out here!
The problem is the last update windows 10. You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select DRIVERS FROM THE LIST and select FASTBOOT INTERFACE (USB GOOGLE ID).
lubinek79 said:
You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select drivers from the list and select FASTBOOT INTERFACE (USB GOOGLE ID).
Click to expand...
Click to collapse
I'll try that out tomorrow, thanks for your reply!
lubinek79 said:
The problem is the last update windows 10. You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select DRIVERS FROM THE LIST and select FASTBOOT INTERFACE (USB GOOGLE ID).
Click to expand...
Click to collapse
Thanks for help, Worked for me
lubinek79 said:
The problem is the last update windows 10. You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select DRIVERS FROM THE LIST and select FASTBOOT INTERFACE (USB GOOGLE ID).
Click to expand...
Click to collapse
Got it working with your help! Had to completely remove the drivers first and than put my PC into flight mode though, because Windows 10 would keep reinstalling the drivers. Thanks for your help!