Develop Bugs

Phone not recognized while in bootloader, works fine when booted into ICS.

Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!

picklz said:
Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!
Click to expand...
Click to collapse
im having similar issues...im stuck in "waiting for device" in the bootloader.

I'm having the same problem and nothing I've found helps. Since I really want to unlock the bootloader, and doing so wipes the device, I'm stuck not being able to do anything with the phone until I get this worked out

I had this problem when I was unlocking the bootloader. I kept playing around with it and reinstalled the drivers multiple time. I would uninstall the driver and install the driver when the phone was in bootloader mode (I believe).
Make sure the drivers you're setting it to are new.
http://dl.dropbox.com/u/4174784/usb_driver.zip were the drivers I used. These are for GSM model, not sure if they work for the CDMA/LTE version!
Alternatively, you can install PdaNet for drivers.

I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.

Some people also had luck by installing the windows pdanet which installs drivers that should work too.

Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks buddy!
Worked for me, I thought it was due to my HTC/Motorola device drivers, so uninstalled all of those and re-installed the Samsung...but these steps worked. Thank you again (I did also hit the thanks button too FYI!)!

Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
It worked for me. Thanks!!

i have no idea why but it is just not working :/ in that last set of instuctions above...i dont even have android bootloader interface lol which is weird cause ADB is reading my phone just fine...but when in bootloader mode it just says waiting for device. Does anyone have the fastboot drivers?

Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
That method didn't work for me either. I'm running windows XP professional and do not see 'Android Device' in the list of devices... any other ideas anyone?

Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.

RMarkwald said:
Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.
Click to expand...
Click to collapse
I did,
Tried the PDAnet method as well. Adb works fine. Once I get into the boot loader the device isn't recognized. I get the Android 1.0 install prompt and cant install it.

Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks! FWIW, I had to uninstall the Samsung driver and use the Google USB driver to find the Android Bootloader Interface one... if others are having trouble, try that.

[Q] samsung drivers wont install

hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks

After installation, plug in your phone, look at your system tray for the USB icon, click it. It should show a status of installing more drivers. This can take awhile, and for a lot of people it seems to fail the last step, Android 1.0 drivers. Open control panel, system, device manager. Look for a yellow error icon. Click that, choose to install drivers manually and locally. Then select 'choose from list', find Samsung.
That should get you back on track
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#5

Were you able to unlock the bootloader? If you didn't do this, don't go installing any driver... be very careful. If you install the wrong driver in device manager, you'll screw it up. I installed the wrong driver on my main computer and I couldn't get the device manager to even recognize the phone :| I couldn't locate the right driver either because once I installed the driver, it renamed it. It was a huge pain and the only way I got this to work was by using a different PC with the correct drivers.
I have found this to be the best instructions for unlocking the bootloader. Most importantly, it includes directions on how to gain access to adb on your phone properly. Take your time and follow the instructions exactly...

Dutchy18 said:
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
Click to expand...
Click to collapse
I had the same issue, install pdanet and your phone will be recognized when in fastboot
Sent from my Galaxy Nexus using xda premium

i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks

Dutchy18 said:
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Click to expand...
Click to collapse
silly question, but after booting to fastboot, you are using the fastboot.exe, and not adb? if you type "fastboot devices" does anything show up?

no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.

Dutchy18 said:
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Click to expand...
Click to collapse
click open that yellow unrecognized device...manually choose drivers (don't do auto), and select from the list, you'll see samsung, choose the driver
that should install android 1.0...alot of people have gotten this error.
edit: another thing to keep in mind is, after installing the drivers, and fixing the device in device manager, it can still take a little bit to initialize. in your system tray there should be a usb icon, open that to see when the drivers are done

I am in the same boat. I tried for hours on 2 different Windows 7 laptops (both 64bit). I am trying to get Yakju from one of the derivitives (without unlocking the device).
Steps taken:
- Dloaded Samsung USB driver 1.4.6 & Installed: Did not recongnize in explorer or Odin (even Odin did not show a thing)
- Dladed PDA Net A302x64: Did not recognize in explorer or Odin.
Both times the GN is in Device/Printers and listed as having Android 1.0 driver. I try to manually update, but cannot seem to find driver in list (as it just has Android 1.0 driver listed). Any suggestions?

i didnt even see the "Android 1.0".. just "unknown device" all along..
i also tried on a different computer.. same issue.
about manually installing the driver.. i tried pointing him to a manual driver package i got from this forum.. it said its the same driver..
when im searching for "samsung" on the list, i dont see a relevant driver.

Well, i've saw someone else on here who was having driver issues, who also had installed both samsung & pda drivers...
uninstall both.
fresh install ONLY the naked drivers directly off samsungs website (http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW -- if you're verizon, if not, you can search there). Do the install. Plug the phone in, it will start to install its usual crap. this is the long part. then, it will fail like you saw before. in device manager, you'll see the unrecognized device. Open, it will ask you to find drivers, choose "Browse", "Let Me Pick From a List", "Samsung", and then pick the driver with the date 11/25/2011
check to see if there are any other unrecognized devices in device manager, just to be sure you got em all. at this point, plugging in your phone should show the USB connected icon in the system tray. do you see this? If you click it does it say "Eject MTP"?

Cannot stop USB drivers from auto-installing

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.

Help GNex has no OS and won't connect to a PC!

Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???

I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.

Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
stargazer127 said:
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
Click to expand...
Click to collapse

isajoo said:
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Click to expand...
Click to collapse
OK, downloaded universal naked driver 0.72, connected gnex, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, and will not allow install of of universal naked drivers, & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?

KingWickedd said:
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
Click to expand...
Click to collapse
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?

stargazer127 said:
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
Click to expand...
Click to collapse
You have to go to the device manager, double click on the "unknown usb..."
a dialog box may appear and then click on the 'driver' tab.
There u may find update/install driver button.
click on it and another window may open.
then select browse my computer for driver software and go to the respective folder where the drivers are.
then click next and it may install the drivers.
if you have installed the toolkit then you may find a folder in the toolkit's installation folder which has drivers in it.go through it if you want :good:

Google drivers not working on Nexus 5X/Marshmallow on Win7 - Is the phone too new?

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?