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] adb devices strange issue, not detecting

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.

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:

No Command, No ADB, No Fastboot Nexus 5X

So I updated my phone to fix "critical bugs". The phone turned off went into TWRP, restarted and I was met with "no command". Oh great I forgot I was rooted again. So I open up TWRP, connect to my computer and try adb, oh it didn't work. I played with the drivers for literally forever installing the google driver, and various third party ones, reading every online tutorial. No work. I purchased a new high quality cord with charging+sync. It still did not work, at this point I decided that I would use ubuntu instead of windows, I have more experience doing this stuff in ubuntu anyways. Well it still did not work, the same error. No Device Found. I went through a few tutorials on some other troubleshooting, I used nirsofts usbinfo tool and I also used lsusb in ubuntu, and I could not find my phone connected. I could plug it in and out and the lsusb would look the same either way. Though my phone was still charging. I then tried on another computer with ubuntu as well and the same problem then too. Any ideas?? I am kinda on vacation and it was my source of data+contacting people. Also somewhat concerned about the new system where they check your electronic devices at border security, when it doesn't work they definitely will think its a bomb.

Le bump??

Bump, does anyone have any ideas???

My Nexus 5x randomly stopped working on ADB saying devices not found earlier this year. That device bootlooped and received my replace a couple weeks ago and decided to finally setup and not sell it. The same thing was happening to my replacement device so I knew it was the drivers on the computer since my Sony Xperia X was able to ADB and all that. I finally setup my phone today and updated the firmware and found the issue. This is what ended up working.
Steps:
1) Uninstall old drivers by going to Windows key + R key together. Type devmgmt.msc and hit enter to open Device Manager.
2) Click on Android device or Portable Device and find your device, right click and uninstall driver.
3) Download/Update Google USB driver through SDK manager and install.
4) Connect your phone with the cord and it should install its own drivers.
5) Windows key + R key again, devmgmt.msc to go to Device Manager.
6) Go to Android Device or Other and right click on your phone and update driver software.
7) Click on Browse my computer from driver software.
8) Click on Let me pick from a list of device drivers on my computer.
9) There should be 1 or 2 lists under Model. Double click on the first one and it will update it. After that finishes, go back to step 6 and until you get to step 9 to double click and update the other item on the list to update.
10) Reboot computer and connect your device and it should work.
If you don't see Android Device > ADB interface in Device manager when you update the Google USB drivers, click on Portable > Nexus 5x and update drivers and just follow steps 6-9, then update the Android Device under Device Manager.
Once thats all done ADB should work, for me it did today but the android with no command showed up. For that when your at that screen, Hold power button + tap volume UP once (don't hold it, just tap and let go) and it should bring you to recovery screen with the choices.

Riverdales27 said:
My Nexus 5x randomly stopped working on ADB saying devices not found earlier this year. That device bootlooped and received my replace a couple weeks ago and decided to finally setup and not sell it. The same thing was happening to my replacement device so I knew it was the drivers on the computer since my Sony Xperia X was able to ADB and all that. I finally setup my phone today and updated the firmware and found the issue. This is what ended up working.
Steps:
1) Uninstall old drivers by going to Windows key + R key together. Type devmgmt.msc and hit enter to open Device Manager.
2) Click on Android device or Portable Device and find your device, right click and uninstall driver.
3) Download/Update Google USB driver through SDK manager and install.
4) Connect your phone with the cord and it should install its own drivers.
5) Windows key + R key again, devmgmt.msc to go to Device Manager.
6) Go to Android Device or Other and right click on your phone and update driver software.
7) Click on Browse my computer from driver software.
8) Click on Let me pick from a list of device drivers on my computer.
9) There should be 1 or 2 lists under Model. Double click on the first one and it will update it. After that finishes, go back to step 6 and until you get to step 9 to double click and update the other item on the list to update.
10) Reboot computer and connect your device and it should work.
If you don't see Android Device > ADB interface in Device manager when you update the Google USB drivers, click on Portable > Nexus 5x and update drivers and just follow steps 6-9, then update the Android Device under Device Manager.
Once thats all done ADB should work, for me it did today but the android with no command showed up. For that when your at that screen, Hold power button + tap volume UP once (don't hold it, just tap and let go) and it should bring you to recovery screen with the choices.
Click to expand...
Click to collapse
There is no android device or portable device, I have used many oem cables too.... Using usb diagnostic tools it doesn't even show it as plugged in, though it still is getting a charge. The positive and negative wires still are supplying electricity but the sync wires are not working, though it doesn't seem to matter what cable I use. With the second part, do you mean with using the SDK tool? I was just installing the google drivers from the standalone installer.

I don't know then. You have usb debugging enabled on developers option.

Do you have the "Qualcomm HS-USB QDLoader 9008" ? In the com ports? If so jump to this thread nexus-5x/help/finding-solution-qualcomm-hs-usb-t364828