Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
This guide can be helpful. It clears out 'ghosts' of past device connections.
http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html
Also Wugs toolkit has a really good guide to cleaning out drivers. Then stop short of installing drivers. Then Windows should auto configure MTP drivers when You plug in the device.
I also make sure that I have deleted any drivers in uninstall programs in the Windows control panel.
Its a lot of steps, but it can save time over try this, try that. It returns your computer to like an Android device had never been plugged in before. Now any routine to install drivers (after the device is recognized as an MTP device) should go smoothly.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Anderson2 said:
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
Click to expand...
Click to collapse
My Device Manager shows NO Nexus devices of ADB interfaces, so I'm stumped at step 1.
Related
I had a lot of trouble getting the adb drivers on my work Win7 x64 laptop working. Here's what seems to have done the trick.
1. Pull up a commandline, go to Documents and Settings\username\.android directory, and do
Code:
echo 0x04e8 >> adb_usb.ini
if you haven't done so already.
2. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
3. Set device in adb mode (Settings | Applications | Development | USB debugging(x)).
4. Plug device into computer. You will get a tray icon with stuff spinning. Click on it. If things go fine, you'll eventually see a list of drivers with "Ready to use" and green checkmarks.
If all the drivers have checkmarks, you're done--you had it easy. This guide is for cases like mine where you find that two drivers, "CDC Serial" and "SAMSUNG_Android" are labeled "No driver found" and adb doesn't work.
5. Right-click on My Computer, choose Properties, then "Device Manager". Expand "Other devices".
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).
Man, thank you so much. I was going crazy with this. Worked for my T-mobile SGS3. :cyclops:
One thing that's not mentioned, after I fixed the ADB and the CDC driver, it threw an error in the MTP device, I just let Winblows install that one automatically and it worked fine.
There is less steps needed,i got my ADB working in Windows 8 64bit RC1 developer preview flawlessly.
Just disable driver signature,install sdk,add sdk folder to windows environment and you are done.
nice. I didn't have any problems with mine, just sayin. Its always nice to see people help each other.
Sent from my SPH-D710 using xda premium
Worked perfectly on my PC and the Kies could see the phone as well (GT-I9100).
Thanks again !! :good:
Longest ADB guide I've ever seen.
Sent from my sph-d710 using xda premium
Thanks for this!
Great guide man! Helped solving some driver issues with Windows 8.1 and Note 3, particularly installing the SAMSUNG_android adb device manually!
Thank you very much!
I thought I would never find a tutorial like that, it saved my life lol. Thank you so much!
Hello,
I have searched the forums and Google, and was not able to find anyone else with this issue, so here I am.
I'm on Windows 7 x64 with a stock Canadian Galaxy Nexus 4.0.1 (yakjuux.)
I am trying to install GNex Toolkit and am unable to get past the first step. No matter what I try to do, any time I plug in the phone, it installs the default drivers.
Device installation settings are set to "never install drivers from Win Update." Phone is in development mode, I have removed Google Nexus from my devices (and checked the "delete drivers" box, though it doesn't even appear anymore), there is nothing for Samsung in Programs and Features, I have used USBDeview and there is nothing for Samsung/Nexus. I've tried using PDANet to no avail (I get error 103). I tried using "uninstall drivers" with GNTK, no dice (it seems to just remove a registry entry).
Any other ideas on how to make my PC install the drivers I want and not the default ones?
Thanks.
Read part A of this post.
efrant said:
Read part A of this post.
Click to expand...
Click to collapse
I have read that entire post and Bourne-nolonger's guide. Instead of showing up as "Android 1.0" device in Device Manager, my phone always shows up as Galaxy Nexus, with no yellow triangles or any other issues. (Yes, developer mode is enabled, and it seems to make no difference to how my computer responds.)
From Bourne-nolonger's guide:
"As soon as you enable this Windows will pick up a new device and it will attempt to install a driver - this will fail (or hopefully it will)." - mine never fails, it always installs drivers from somewhere. When I attempt to install new drivers to the Google Nexus device using UNK 0.7, Windows tells me that I already have the newest drivers.
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Scarf Face said:
[snip]
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Click to expand...
Click to collapse
Absolutely.
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
edit: tried doing the same in fastboot mode; the Device Manager recognized it as Fastboot mode, but did not let me install the proper drivers, saying that I already have the newest ones.
Scarf Face said:
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
Click to expand...
Click to collapse
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
efrant said:
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
Click to expand...
Click to collapse
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Scarf Face said:
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Click to expand...
Click to collapse
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Click to expand...
Click to collapse
Seems to be a problem with my PC, so I will try it with a different machine. Thanks for your help!
Ignore this. Wrong thread.
I 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?
When I connect Nexus 5X to a Windows 10 PC, I can't see it in File Explorer.
Many people said that one should change the option from charging only to MTP in the USB connection notification, appeared when plugged in. But I don't even have that notification, and cannot find the option anywhere else.
In Devices and Printers, there's a Nexus 5X under Unspecified; and in Device Manager, I can see a "ACER ADB Interface" there which I assume is for Nexus 5X. I tried to download Nexus driver from Google buy it seems is the same with the ACER ADB thing and is not helping.
Any tips or solutions? Thanks in advance!
PS. First xda thread started by me, yay!
UPDATE: After awhile, maybe it's because I slid the screen while connected, the notification did pop up. But EVEN after I chose MTP, there's still nothing in my File Explorer...
Hiya,
I had the same thing happen on my 5X. I was only able to get to the "Use USB for Charge / MTP" dialog by enabling Developer Mode.
To do that: Go to Settings / About Phone, and scroll all the way to the bottom.
Tap "Build number" seven times. On the sixth tap, you should see a message that says "one more tap will unlock Developer mode" or something to that effect.
Back-arrow to the Settings main menu.
Click on Developer options
Look for Networking / Select USB Configuration.
Choose the mode you want.
The notification should appear when you plug in the USB cable to your computer.
elzapato said:
Hiya,
I had the same thing happen on my 5X. I was only able to get to the "Use USB for Charge / MTP" dialog by enabling Developer Mode.
To do that: Go to Settings / About Phone, and scroll all the way to the bottom.
Tap "Build number" seven times. On the sixth tap, you should see a message that says "one more tap will unlock Developer mode" or something to that effect.
Back-arrow to the Settings main menu.
Click on Developer options
Look for Networking / Select USB Configuration.
Choose the mode you want.
The notification should appear when you plug in the USB cable to your computer.
Click to expand...
Click to collapse
Thanks for this info! I'll keep that in mind, but now I still have problem after chose the transfer mode. Maybe it's because I slid the screen while connected, the notification do pop up. But EVEN after I chose MTP, there's still nothing in my File Explorer...
could be a driver issue?
download and install latest usb drivers.
Go to My Computer> Properties>Device Manager> Find the android device>Right Click update driver software>Browse My Computer>set to folder where you have usb driver saved and go from there?
You can also try to let me pick (instead of browse local folders) and pick the google ADB interface from there.
I have also had success in the past using other software (PdaNet) to manage the whole installataion of drivers; but this adds software to both phone and computer ... may or may not be useful.
After re-reading your first post its definately driver related. It shouldnt say Acer just ADB Interface or google adb interface.
alienboytw said:
When I connect Nexus 5X to a Windows 10 PC, I can't see it in File Explorer.
Many people said that one should change the option from charging only to MTP in the USB connection notification, appeared when plugged in. But I don't even have that notification, and cannot find the option anywhere else.
In Devices and Printers, there's a Nexus 5X under Unspecified; and in Device Manager, I can see a "ACER ADB Interface" there which I assume is for Nexus 5X. I tried to download Nexus driver from Google buy it seems is the same with the ACER ADB thing and is not helping.
Any tips or solutions? Thanks in advance!
PS. First xda thread started by me, yay!
UPDATE: After awhile, maybe it's because I slid the screen while connected, the notification did pop up. But EVEN after I chose MTP, there's still nothing in my File Explorer...
Click to expand...
Click to collapse
Check Device Manager, is it listed as ACER Device? It probably is. It happened to me. Select the device, mouse right, update driver, choose "let me pick a driver" or something simmilar. Then you should get a list of compatible drivers and 2 entries, the current ACER driver and some generic USB driver. Choose the generic USB driver. That did the trick for me.
This i got from reddit . I had the same problem today this link helped me .. hope it helps you too
arpan_pratik said:
Check Device Manager, is it listed as ACER Device? It probably is. It happened to me. Select the device, mouse right, update driver, choose "let me pick a driver" or something simmilar. Then you should get a list of compatible drivers and 2 entries, the current ACER driver and some generic USB driver. Choose the generic USB driver. That did the trick for me.
This i got from reddit . I had the same problem today this link helped me .. hope it helps you too
Click to expand...
Click to collapse
@arpan_pratik, Thank you! You are the best! This is exactly what my problem is and I solved it using your suggestion!
Although I didn't yet find any useful information from reddit regarding my issue, you must used some magic keywords
@The_Automator, thank you, too! It indeed is a driver issue. I tried many times to update the driver or uninstall the ACER ADB driver, but none of them worked. Didn't realize that it is Windows chose the wrong default driver. Don't know why, maybe it's because I installed adb before?
So, for the record, here are some key points to solve the problem:
The wrong driver for my Nexus 5X showed in Device Manager is ACER Device\ACER ADB Interface
No use to install Nexus driver from Google, even use "Browse my computer for driver software" and search the extracted Google driver folder. Windows will say the driver is up to date.
So I have to do this: In Device Manager -> RMB on ACER Device\ACER ADB Driver -> Properties -> Update Driver -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> check "Show compatible hardware" -> choose "MTP USB Driver" (this is a Microsoft driver under "standard MTP Device" category) -> Problem solved!
Then I can find my Nexus 5X in Device Manager here: Portable Devices\Nexus 5X
After the right driver installed, if I try again to update the driver using ""Search automatically for updated driver software", Windows 10 will actually install the wrong driver (ACER ADB) back!
Thank you all in this thread to help me exclude other possibilities, lock down the culprit and finally solve the issue!
Just got a Nexus 5X, and I'm having the same problem under Windows 10. I don't see an Acer device in Device Manager though, I see a "Nexus 5X" under "Other devices" with a yellow triangle exclamation mark.
When I tried following the steps, I don't have "Show compatible hardware" nor "MTP USB Driver". When I tried installing "MTP Device", I get an error "The install class is not present or is invalid."
cigar3tte said:
Just got a Nexus 5X, and I'm having the same problem under Windows 10. I don't see an Acer device in Device Manager though, I see a "Nexus 5X" under "Other devices" with a yellow triangle exclamation mark.
When I tried following the steps, I don't have "Show compatible hardware" nor "MTP USB Driver". When I tried installing "MTP Device", I get an error "The install class is not present or is invalid."
Click to expand...
Click to collapse
Were you ever able to get this working on your PC?
azsl1326 said:
Were you ever able to get this working on your PC?
Click to expand...
Click to collapse
Yeah, and it's been a while so I don't remember exactly, but I think it was a different cable that made it work.
I've switched to a Droid Turbo 2. The 5X didn't have enough battery life for my usage.
thanks
i fuking love u
SadsArches said:
i fuking love u
Click to expand...
Click to collapse
Huh? LOL
Sent from my Nexus 5X using Tapatalk
Brilliant! Solved and excellently described. Many thanks.
Bruce
cigar3tte said:
Just got a Nexus 5X, and I'm having the same problem under Windows 10. I don't see an Acer device in Device Manager though, I see a "Nexus 5X" under "Other devices" with a yellow triangle exclamation mark.
When I tried following the steps, I don't have "Show compatible hardware" nor "MTP USB Driver". When I tried installing "MTP Device", I get an error "The install class is not present or is invalid."
Click to expand...
Click to collapse
If you have other android devices that is working on your PC, you'll notice that the driver used is the "wpdmtp.inf" you can get it on your 64-bit Windows on this location:
"C:\Windows\WinSxS\amd64_wpdmtp.inf_31bf3856ad364e35_10.0.16299.15_none_42867195f7d5106b\wpdmtp.inf"
Locate this file via device manager and choose "MTP USB Device"
And viola! You can now transfer files again in your Nexus 5x!
I am in the same boat but my PC stopped recognizing my phone at all. PC will see all my other devices including my pixel 2xl. But every since that Nov update I believe my PC's and diffet cables does not show up at all. Have read all the threads and so far nothing has worked for me.
Travisdroidx2 said:
I am in the same boat but my PC stopped recognizing my phone at all. PC will see all my other devices including my pixel 2xl. But every since that Nov update I believe my PC's and diffet cables does not show up at all. Have read all the threads and so far nothing has worked for me.
Click to expand...
Click to collapse
Did you get it working again? I have 2 other phones working fine but the nexus5x disappeared and cant get it back. Even deleted the cache and the data for the System apps named "External Storage and Media Storage" as some suggested. Shows up as unknown device now.
AlienTeck said:
Did you get it working again? I have 2 other phones working fine but the nexus5x disappeared and cant get it back. Even deleted the cache and the data for the System apps named "External Storage and Media Storage" as some suggested. Shows up as unknown device now.
Click to expand...
Click to collapse
Nope, was never able to find a fix. If you do please let me know.
Yes I got it working. Since longer USB cables only shows unknown device I installed android development system and it made no difference.. But I had a 6inch charging cable that came with my power brick and I tried that and viola the Nexus showed up.. Not as a nexus 5x like before but as something like romaster composite ADB interface or something and I was able to flash TWRP recovery so now I can at least get access to it. Backed up the memory to a flash drive.. Have not flashed SU or anything yet but that should not be a problem with TWRP installed.. And like usual it takes a few flashes and rebooting into TWRP for it to stick other wise the recovery goes away.. Still dont know why the longer USB cables make any difference.. I even tried it out on a USB extension socket which is a 20 foot long USB extender and that also works.. So it must be something else like when I had the MB changed the adapter I was using did not work for data transfer.. Might be using some wire that is missing in the longer cable..
I'm trying to connect my Nexus 5X to a PC running windows 10, version 1903. The PC previously had android SDK installed and I was able to access a Nexus 5 using adb.
When I connect the phone to the PC, the device is detected and the PC says it's ready. However, the PC never asks what to do when the device is connected, the device doesn't show up in the file explorer window and in the device manager, it shows up as an "other device" with a yellow warning. If I open the properties, the status is the following:
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
Click to expand...
Click to collapse
The phone thinks it's connected. Initially it says "charging" and I can enable "transfer files". It makes no difference on the PC.
In the settings on the phone, "select USB configuration" is set to MTP. Developer options are enabled. If I enable USB debugging, the phone switches to the MTP driver, but there is no difference on the PC.
I tried connecting the phone to another PC and it worked fine with USB debugging enabled and disabled, so the problem seems to be on the PC.
I removed android sdk and installed the latest version using android studio. I also installed the google USB drivers. This also made no difference.
Any suggestions?