Develop Bugs

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:

Eror update Amazon Fire Phone

Hi. Today i get new update for my phone Fire OS 4.6.3 (463001420) for Unlocked Fire Phone. But when i tried intall it, phone catchs "Eror". Now, when i try turn on mobile, opened recovery. I tried "Factory reset", but again opened recovery.
I downloaded 4.6.3 (463001420) bin and try install it use adb. I opened my terminal and wrote "adb sideload <name>" but got error "cannot read <name>".
So, i checked adb connection - pc do not found it: List of devices attached - none.
I deleted SDK, install it again and tried this steps:
"
1. In the Android SDK Manager window, from the Tools menu, click Manage Add-on Sites.
2. In the Add-on Sites dialog box, click the User Defined Sites tab, and then click New.
3. In the Add Add-on Site URLdialog box, enter the following URL:
4. https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
5. Click OK and then Close. Wait for the Android SDK Manager to refresh, as indicated by the progress bar.
6. Expand Extras and click Amazon Kindle Fire USB Driver.
7. Click Install n Packages.
8, In the Choose Packages to Install dialog box, accept the license agreements for the packages, and then click Install.
9. In your Android SDK directory, at \extras\amazon\kindle_fire_usb_driver, run KindleDrivers.exe, and then follow the instructions on the screen."
After 8 step i opened SDK directory and did not find KindleDrivers.exe,.
So, i do not understand, how i can adb, how i can update fire phone. Need helps, pls!
P.S. Sry, my english is very bad, i am from Russian.

..

mazay2 said:
Hi. Today i get new update for my phone Fire OS 4.6.3 (463001420) for Unlocked Fire Phone. But when i tried intall it, phone catchs "Eror". Now, when i try turn on mobile, opened recovery. I tried "Factory reset", but again opened recovery.
I downloaded 4.6.3 (463001420) bin and try install it use adb. I opened my terminal and wrote "adb sideload <name>" but got error "cannot read <name>".
So, i checked adb connection - pc do not found it: List of devices attached - none.
I deleted SDK, install it again and tried this steps:
"
1. In the Android SDK Manager window, from the Tools menu, click Manage Add-on Sites.
2. In the Add-on Sites dialog box, click the User Defined Sites tab, and then click New.
3. In the Add Add-on Site URLdialog box, enter the following URL:
4. https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
5. Click OK and then Close. Wait for the Android SDK Manager to refresh, as indicated by the progress bar.
6. Expand Extras and click Amazon Kindle Fire USB Driver.
7. Click Install n Packages.
8, In the Choose Packages to Install dialog box, accept the license agreements for the packages, and then click Install.
9. In your Android SDK directory, at \extras\amazon\kindle_fire_usb_driver, run KindleDrivers.exe, and then follow the instructions on the screen."
After 8 step i opened SDK directory and did not find KindleDrivers.exe,.
So, i do not understand, how i can adb, how i can update fire phone. Need helps, pls!
P.S. Sry, my english is very bad, i am from Russian.
Click to expand...
Click to collapse
Hi, I got the steps below from a post made by hijax2001. I modified the steps somewhat to cover the problem you are having. I don't know if they will work, but you can try them if you like.
1) Put update-fire-phone-35.4.6.3_user_463001420.bin in your ADB folder.
2) On your computer go to Device Manager and delete any SD4930UR and or Unknown device that appear when you plug your phone into the computer. Unplug your phone from the computer. Skip steps 3 and 4 if you see "Kindle Fire> Android Composite ADB Interface" when you plug in your phone into the computer.
3) If you need the Kindle Fire ADB drivers then download and install the Kindle Fire ADB drivers on your computer from here: Kindle Fire ADB drivers
4) Plug your phone back into the computer. The drivers for the phone should be installed and you should see "Kindle Fire> Android Composite ADB Interface" in Device Manager. Move on to the next step even if the drivers are not installed.
5) Power off the phone. Turn the phone back on by pressing and holding the Power and Volume Up buttons until the Fire System Recovery screen appear.
6) Use volume down to reach "Apply update from ADB" option, then press Power to select the option.
7) From ADB type ADB devices. If you see what looks like a serial number (letters and numbers), then ADB is seeing your phone and you can skip to Step 9. If nothing there, follow Step 8.
8) If ADB doesn't detect your phone go to Device Manager and right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer. Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>. Go back to ADB and type ADB devices. ADB should now detect your phone.
9) Type the command ADB sideload update-fire-phone-35.4.6.3_user_463001420.bin (Note: you can copy and paste the filename). When the phone display "install from adb complete", press the power button to select "reboot system now". The phone should update to Fire OS 4.6.3.

jack9955 said:
Hi, I got the steps below from a post made by hijax2001. I modified the steps somewhat to cover the problem you are having. I don't know if they will work, but you can try them if you like.
1) Put update-fire-phone-35.4.6.3_user_463001420.bin in your ADB folder.
2) On your computer go to Device Manager and delete any SD4930UR and or Unknown device that appear when you plug your phone into the computer. Unplug your phone from the computer. Skip steps 3 and 4 if you see "Kindle Fire> Android Composite ADB Interface" when you plug in your phone into the computer.
3) If you need the Kindle Fire ADB drivers then download and install the Kindle Fire ADB drivers on your computer from here: Kindle Fire ADB drivers
4) Plug your phone back into the computer. The drivers for the phone should be installed and you should see "Kindle Fire> Android Composite ADB Interface" in Device Manager. Move on to the next step even if the drivers are not installed.
5) Power off the phone. Turn the phone back on by pressing and holding the Power and Volume Up buttons until the Fire System Recovery screen appear.
6) Use volume down to reach "Apply update from ADB" option, then press Power to select the option.
7) From ADB type ADB devices. If you see what looks like a serial number (letters and numbers), then ADB is seeing your phone and you can skip to Step 9. If nothing there, follow Step 8.
8) If ADB doesn't detect your phone go to Device Manager and right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer. Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>. Go back to ADB and type ADB devices. ADB should now detect your phone.
9) Type the command ADB sideload update-fire-phone-35.4.6.3_user_463001420.bin (Note: you can copy and paste the filename). When the phone display "install from adb complete", press the power button to select "reboot system now". The phone should update to Fire OS 4.6.3.
Click to expand...
Click to collapse
Thank you very much! I am so silly(
I could update phone. No problem!
Moder, pls close this thread

Can't unlock bootloader, fastboot not detecting device

UPDATE: Got it working on a windows 7 machine.
I've been trying to unlock my bootloader but have been having issues. I have done the following:
- Enabled Developer Options
- Enabled USB Debugging
- Enabled the OEM Unlock in the Developer Options
- Installed drivers via android SDK
I have adb and fastboot installed from the android SDK. Using that, I have been able to see my device with 'adb devices'. I have also been able to reboot it using 'adb reboot bootloader'. However, once the phone is in fastboot, it does not seem to be detected by my machine. I have tried 'fastboot devices' to no avail. Using 'fastboot oem unlock' just stalls at '< waiting for device >'. Am I missing something?
I have also tried:
- Using a different computer
- Using different USB ports
- Using different ADB / fastboot package (the minimal one).
Please assist! I'd really like to unlock my bootloader now for future flexibility.

There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"

Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)

crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.

yourbuddypal said:
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
Click to expand...
Click to collapse
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"

amitte said:
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
Click to expand...
Click to collapse
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working

yourbuddypal said:
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
Click to expand...
Click to collapse
Yes this is normal. For the bootloader part, do not let windows search automaticly. Do as i described earlier exept use the driver i uploaded for you or search any other nexus usb driver install guide since the process did not change
Same applies to the installation when you are in the system already. Exept do not override any driver that is under portable devices since its the file transfer protocoll driver.

I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!

yourbuddypal said:
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
Click to expand...
Click to collapse
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Solution on Linux
I had a similar problem earlier today on one of my linux boxes. Turns out, in order to use fastboot (successfully) under linux, you need to run fastboot with sudo rights.
If I had to guess, I'd guess this is because unlike adb, fastboot doesn't run as a server, so fastboot always needs to get elevated permissions to communicate with a device on a USB port.
Maybe it's possible that Windows wants Administrator rights for similar reasons?

duckxtales said:
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
Click to expand...
Click to collapse
Sorry, I really don't have any more feedback to give you. It really did seem like voodoo when it worked. The only thing I can think to explain the "random" aspect is that perhaps it is related to the quality of cable used. I was using these (http://www.amazon.com/Orzly-Type-Cables-Assorted-Colours/dp/B013RMG5WY/ref=cm_rdp_product), which have now been taken down due to cable standards as described in the comments section for that product. I was thinking that maybe the different USB port on the desktop machine was somehow able to get sufficient voltage or something. Voodoo!

I am having the exact same issue with my 6P right now. However it shows when I do adb devices, just not fastboot devices. Weird...
I even uninstalled the Google USB driver and reinstalled it using Android Studio but Still did not work. Then I even went to Device Manager and uninstalled and deleted the driver. Then went manually to file path C:\Users\MyWindowsLoginName\AppData\Local\Android\sdk\extras\google\usb_driver and clicked next. It installed successfully, but displays as Android Composite ADB Interface. So I guess that is correct then?
Tried to just sideload the new 6.0.1 OTA update using adb since adb devices was recongizing it but still not found...
C:\Users\Matthew\AppData\Local\Android\sdk\platform-tools>adb sideload angler-MMB29M-from-MDB08L.zip
loading: 'angler-MMB29M-from-MDB08L.zip'
error: device '(null)' not found
EDIT: I got it after unplugging my phone, killing the adb.exe process in task manager, waiting until in bootloader before plugging phone in, then running fastboot devices shows the serial number now. I hope that helps others!

I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?

I had the same trouble on my 64 bit Windows system. I believe it was HTC sync software that threw the monkey wrench. But I uninstalled that software together with all the adb fastboot drivers for my other devices, removed all adb fastboot versions, then installed the 64 bit version of the Minimal adb fastboot tool.
All good now

Garvinr said:
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
Click to expand...
Click to collapse
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)

wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Thank you.
I follow this step. now I can use fastboot.

crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
Thanks man! Worked immediately after updating the drivers!

I too had this issue.
Manually installed drivers using this guide.
(pretty much the same instructions as wangxiangg, but with pics)

wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Man. That was it. Worked like a charm. Thank you.
To clarify, you do this while you are in Fastboot Mode and you right-click on "Android" in step 1.
You can go through the steps while you are in Fastboot Mode and with the cable still plugged in.

amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Someone give this man a cookie!
it worked!!!!!!!!

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?

7T Android ADB Fastboot Driver Issue on Windows

Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.

raskulous said:
Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
I've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.
Click to expand...
Click to collapse
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.

Soapy! said:
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.
Click to expand...
Click to collapse
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.

raskulous said:
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.
Click to expand...
Click to collapse
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).

Soapy! said:
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).
Click to expand...
Click to collapse
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'

raskulous said:
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'
Click to expand...
Click to collapse
When you check the driver properties do they match what's in the attached image?

Soapy! said:
When you check the driver properties do they match what's in the attached image?
Click to expand...
Click to collapse
No, this is what I get after installing the "Composite ADB" driver from google.

raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
Have you tried to uninstall AND delete all android/android usb drivers, then reinstall oneplus drivers? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing

[QUOTE = "bynarie, postagem: 83974147, membro: 5375894"]
Você tentou desinstalar E excluir todos os drivers USB do Android / Android e reinstalar os drivers oneplus? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing
[/ CITAR]
Tank You

raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
I had the same problem before, with fastboot not recognizing the device and only "waiting for device.." appear when I'm on bootloader mode on the phone. I got it working when I chose bootloader driver (Google USB drivers) on Windows Device manager (under the same screen like your screenshot). Put your phone on bootloader mode, open Device Manager (Windows), plug your phone and Android devices should appear. The Google drivers should come up (assuming you installed them) when you click on Update Driver, then choose bootloader. If successful, device should appear under fastboot devices command. Fastboot should then work.

for "fastboot waiting for devices" problem check solution here https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/

Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com

CheshireShorty said:
Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Click to expand...
Click to collapse
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.

_sky.captain_ said:
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.
Click to expand...
Click to collapse
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.

Battled a bit with this one... Just to let others know. I had no change to get it work with Win11. Using Win10 everything worked fine. Luckily I had other PC with Win10 so I got everything working.

ej8989 said:
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.
Click to expand...
Click to collapse
Thanks! I wasn't able to install the Google drivers manually with the device manager but this worked for me.
Just click on "View All optional updates" after checking for updates, expand driver updates and choose the Google - Android Bootloader Interface. I wasn't aware of that option in Windows update.