Develop Bugs

[Q] ADB works, but no MTP/PTP functionality

So I got my Nexus 7 2013 to work perfectly on my laptop, which runs Windows 7 x64. However, on my desktop, which also runs Win7 x64, I only have the ADB working correctly for the N7. As I recall, sometimes there is a device under Device Manager called "D:/", which is non-descriptive, but seems like the closest thing to the N7. I have tried to update this mysterious device's drivers by pointing to Google's USB drivers and the OEM drivers, but neither was accepted. There are also no devices with missing drivers listed in Device Manager.
At this point, I am not sure how to proceed. Is there a precise way identify under what device name/category the N7 shows up in Device Manager? Please advise. :fingers-crossed:

See if this helps:
http://forum.xda-developers.com/showthread.php?t=2391236

Cool, I'll give this a try in a bit.

zeppelin101 said:
Cool, I'll give this a try in a bit.
Click to expand...
Click to collapse
I cant get Nexus 7 to show has folder when check in MTP mode. it will show as camera folder PTP. Any solutions to this problem? very frustrating!

mickrg123 said:
I cant get Nexus 7 to show has folder when check in MTP mode. it will show as camera folder PTP. Any solutions to this problem? very frustrating!
Click to expand...
Click to collapse
Make sure USB Debugging is disabled, device is plugged in, and go to device manager in windows. Then right click on nexus 7 or android adb device, or any similar name. Then after uninstalling everything, unplug device and replug it in. Let windows get the drivers, and MTP should work!

fevanson said:
Make sure USB Debugging is disabled, device is plugged in, and go to device manager in windows. Then right click on nexus 7 or android adb device, or any similar name. Then after uninstalling everything, unplug device and replug it in. Let windows get the drivers, and MTP should work!
Click to expand...
Click to collapse
Thats my problem it doesn't when trying this.

mickrg123 said:
Thats my problem it doesn't when trying this.
Click to expand...
Click to collapse
get this and delete anything related to google and adb.
http://www.nirsoft.net/utils/usb_devices_view.html

fevanson said:
get this and delete anything related to google and adb.
http://www.nirsoft.net/utils/usb_devices_view.html
Click to expand...
Click to collapse
Deleted everything related to google and nexus. Still installs as adb device but doesnt show as nexus 7 device! Wug fresh has this program in its tool kit

It might sound dumb, but I was literally just having this issue. But apparently certan roms or kernel disable MTP mode when they are installed. i reinstall every driver just now. My fix was as easy as going to Settings > Storage > Menu Button Top right > Enable MTP box.

tonu42 said:
It might sound dumb, but I was literally just having this issue. But apparently certan roms or kernel disable MTP mode when they are installed. i reinstall every driver just now. My fix was as easy as going to Settings > Storage > Menu Button Top right > Enable MTP box.
Click to expand...
Click to collapse
What kernal or rom are you running?
---------- Post added at 10:10 PM ---------- Previous post was at 10:02 PM ----------
mickrg123 said:
What kernal or rom are you running?
Click to expand...
Click to collapse
Going to try a custom rom see if that works!

I have tried a number of the suggestions in this thread, including the deletion of all my google/adb/nexus (and samsung) drivers. None of these steps resolved my problem. However, at the end of the day, I can still use both ADB and MTP, just not at the same time. So it's not a big deal. I think I will mess around with Tasker and/or get a widget for turning ADB on/off.

Are you ale to get a nexus 7 device to show so you can access internal storage? I can only access camera storage.

mickrg123 said:
Are you ale to get a nexus 7 device to show so you can access internal storage?
Click to expand...
Click to collapse
Yea, that's what MTP is.

zeppelin101 said:
Yea, that's what MTP is.
Click to expand...
Click to collapse
That's my problem I can't access mtp.

mickrg123 said:
Are you ale to get a nexus 7 device to show so you can access internal storage? I can only access camera storage.
Click to expand...
Click to collapse
Are you running stock?
If so, do you have USB debugging turned on?
If you have USB debugging turned on, the USB IDs change and it might not (depending on what you have previously installed) recognize the MTP device anymore.
If you turn off USB debugging, it should recognize MTP.
Now if you are on a custom ROM, there might be some issues on the ROM side causing the MTP problem. Try going back to stock and see if it works.
If you are on stock and have the case where MTP only works with USB debugging disabled, then you can try this driver inf I put together to address that.
It is available in this thread:
http://forum.xda-developers.com/showthread.php?t=2391236

[Q] Rooted Nexus 7 Unique MTP Issues

Ok so I have a rooted nexus 7 that won't show up as an mtp device ever since I rooted another nexus 7 on the same computer. I have uninstalled all the drivers and re installed them a million times with device manager and USBDview nothing works. It connects to other computers as an mtp device, however ever since I rooted the other nexus 7 on the same computer it won't work. Also I don't have access to the other nexus because it was my friends. Obviously it's a computer issue because it connects to other computers as an mtp. I'm really out of things to try as I have searched for this problem, but only found people saying to re install the drivers. I would really appreciate some help because I don't know what to do. Thanks.

bkbkaufman said:
Ok so I have a rooted nexus 7 that won't show up as an mtp device ever since I rooted another nexus 7 on the same computer. I have uninstalled all the drivers and re installed them a million times with device manager and USBDview nothing works. It connects to other computers as an mtp device, however ever since I rooted the other nexus 7 on the same computer it won't work. Also I don't have access to the other nexus because it was my friends. Obviously it's a computer issue because it connects to other computers as an mtp. I'm really out of things to try as I have searched for this problem, but only found people saying to re install the drivers. I would really appreciate some help because I don't know what to do. Thanks.
Click to expand...
Click to collapse
I also have weird issues. What I usually do is make sure the Nexus is configured for only one connection. So for MTP mounting I have PTP unchecked and USB debugging unchecked. Then I plug into the computer.
If it doesn't mount as MTP, I find it's usually because Windows has attempted to connect via ADB drivers. So I go into Device Manager and uninstall the device under "Android" while checking the box to remove drivers for the device. Then I unplug the Nexus and plug it back in, and it uses MTP drivers. I've always struggle with these driver issues for the Nexus, i don't know why it's so difficult. Good luck!

When I had issues with my mtp I had to uninstall adb drivers then plug my device back in so it would use mass storage and install the drivers. Somehow I have adb and mass storage working now with USB debugging on.
Check in device manager when you have adb uninstalled and see what your device comes up as.
Sent from my Nexus 7 using xda app-developers app

datallboy said:
When I had issues with my mtp I had to uninstall adb drivers then plug my device back in so it would use mass storage and install the drivers. Somehow I have adb and mass storage working now with USB debugging on.
Check in device manager when you have adb uninstalled and see what your device comes up as.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I uninstall the adb drivers but for some reason windows automatically installs them right back instead of mtp drivers and then if I go to update drivers and select mtp as an option it says it won't work

When I try to install the mtp drivers it says "Windows found driver software for your device but encountered an error while trying to install it...your device can't start" Then it automatically installs the adb drivers. What would be the reason it won't let me install the mtp usb drivers? Has anyone else encountered this?

[Q] Can't update Drivers

Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.

Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?

Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887

Aerowinder said:
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Click to expand...
Click to collapse
That would have been roughly a year ago. I believe I did boot straight into the OS.
mdamaged said:
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Click to expand...
Click to collapse
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.

Allane176 said:
That would have been roughly a year ago. I believe I did boot straight into the OS.
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Click to expand...
Click to collapse
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.

mdamaged said:
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
Click to expand...
Click to collapse
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.

Allane176 said:
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Click to expand...
Click to collapse
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download these, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.

mdamaged said:
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
Click to expand...
Click to collapse
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.

Allane176 said:
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Click to expand...
Click to collapse
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install Wugs NRT, as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: http://www.nirsoft.net/utils/usb_devices_view.html, but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.

mdamaged said:
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install ], as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: , but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
Click to expand...
Click to collapse
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.

Allane176 said:
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Click to expand...
Click to collapse
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.

mdamaged said:
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
Click to expand...
Click to collapse
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.

Allane176 said:
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Click to expand...
Click to collapse
No problem, maybe you'll work on it again and you'll figure it out. Also, you can use airdroid for transfer of files, I hear it works really well.

Can't get Fastboot to work

Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks

I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.

Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)

jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96

jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.

@Istvan_86,
We should move the discussion for your problem here.

cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.

Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?

Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.

FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.

cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!

Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.

cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.

Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.

What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.

Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html

@clockcycle,
This solution works 100% too. https://www.ubuntu.com/

CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!

Can't use ADB

So I uninstalled all of the previous Samsung/Koush/Intel Android USB drivers for and downloaded SDK Google USB driver. But I can't get adb to work - when I connect the phone, it says Pixel XL under Portable Devices in Device Manager (Win 7.) I can transfer files, but ADB just won't work.
I used some Intel and Koush Android ADB Device drivers previously, and the Google Nexus ADB device did appear in Device Manager, but adb was still a no go.
Does anyone know how to fix this?
Thanks.

Just to make sure, you did enable adb debugging in developer options, right? When you connect the phone to your computer, are you choosing the transfer files option? What is showing up in device manager?

skaforey said:
Just to make sure, you did enable adb debugging in developer options, right? When you connect the phone to your computer, are you choosing the transfer files option? What is showing up in device manager?
Click to expand...
Click to collapse
I enabled debugging in developers options.
I tried most of the settings - charging, file transfer, ptp.
When I connect the phone, only one thing appears - Pixel XL under Portable Devices.
I can transfer files as mtp and ptp.
I can also update the driver for Pixel XL and force Google Nexus ADB driver (I believe it comes from something like 2013-2014 USB driver package by Koush.) When I do that, Pixel XL disappears and Android ADB device replaces it under Android Devices. But ADB still doesn't work, when I do adb devices - nothing shows up.
I can also update this driver with a current Google USB driver from the latest android SDK. I think it's version 11. When I do this, Android ADB device gets replaced with Pixel XL under Portable Devices. Still no adb.
I have updated Java SDK, I have updated Windows 7. I spent literally 4-5 hours on this, and I can't figure it out.

When you see it as adb under device manager, try removing the driver by right clicking and uninstall. Unplug the device and replug it in. Then make sure it's using the newest SDK driver, that's what worked for me.

Tried a different computer. Adb worked as soon as I installed the 15 seconds adb installer.
There's something wrong with my main computer. I already tried uninstalling and reinstalling the driver - it just doesn't work - every time the device is recognized as mtp usb device.

Any tips would be greatly appreciated!

nabbed said:
Any tips would be greatly appreciated!
Click to expand...
Click to collapse
Erase every adb and fastboot folder you have and download android SDK and reinstall platform tools

nabbed said:
Any tips would be greatly appreciated!
Click to expand...
Click to collapse
You could try using the adb minimal with fastboot at the xda link below. It was updated on 10-22-16 this is what I use.
http://forum.xda-developers.com/showthread.php?t=2317790