Database Develop

MTP & "Nexus 6" drivers won't install...help?

Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?

wfujay said:
Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?
Click to expand...
Click to collapse
I'm having similar issues, laptop running win 7 can't see Nexus 6, DL'd drivers, even tried Motorola for drivers but although showing in device manager as installed no connection

At least they installed for you. The drivers don't even recognize my device. I still get a yellow Nexus 6 in device manager with no usable connection. Ugh...
Sent from my Nexus 6 using Tapatalk

Seems to be a lot of this going around. I'm on win 8.1. I couldn't get the drivers to work via the sdk. Then I tried the Google and Motorola drivers. After deleting the devices on device manager I finally got the N6 to connect via mtp. However, I can't the computer won't connect via mtp if USB debugging is on. On top of that I can't get adb to even see the phone. I would suspect it's more of a Windows problem at this point. I need to do some more testing from another pc.
Sent from my Nexus 6 using XDA Free mobile app

Have any of you tried using Wug's Toolkit?
http://forum.xda-developers.com/showthread.php?t=2947452

Managed to connect via PTP eventually by uninstalling and reinstalling drivers, seems to work with PTP and USB debug on, but not with MTP

wfujay said:
Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?
Click to expand...
Click to collapse
This may not apply to you at all, but with the mess of Android drivers I have to install over time I've finally figure out a solution when something is not installing correctly. Did you try right clicking on the Nexus 6 (I'm assuming that has a yellow exclamation point) going to:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.

Use the universal naked drivers. I have multiple devices and the drivers don't cooperate with each other but since I installed the naked drivers I have had any issues.
http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339

I fixed it! Wug's toolkit didn't work, although I'm about to use it to unroot, lock, and return my phone to factory state since it has to be taken back to the AT&T store to be replaced due to a screen defect. Hope they don't freak out about the death star being scratched off, lol.
Anyway, oddly enough the problem is because I'm using Windows 8.1 N, which doesn't come with Windows Media Player or any of the media features. Installing the Media Feature Pack for N and KN versions of Windows 8.1 sorted it out. Installed, rebooted, done. I can now access the device in any mode and the device driver errors are gone.
So if anyone is having the same issue with Windows 8.1 N, download and install this: http://www.microsoft.com/en-us/download/details.aspx?id=42503
Reboot and enjoy!

thanks
EvanVanVan said:
This may not apply to you at all, but with the mess of Android drivers I have to install over time I've finally figure out a solution when something is not installing correctly. Did you try right clicking on the Nexus 6 (I'm assuming that has a yellow exclamation point) going to:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.
Click to expand...
Click to collapse
Same thing was going on with my nexus 6 and I tried what you said and updated everything. Now the MTP works. thanks

Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
Click to expand...
Click to collapse
Thank you so much ! MTP Works now. Hail to the king

EvanVanVan said:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.
Click to expand...
Click to collapse
Ran into the same issue initially when I was trying to root my Nexus 6. Wug's didn't work, and neither did the naked universal drivers. Added the Nexus 6 ID to the inf and still didn't work.
Had to install the Motorola driver kit, and then go through the drivers as above to find a Motorola that finally worked; while the Motorola driver is just a wrapper for some Microsoft driver that normally comes built into Windows since Windows 7.

Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac-68355/
I discovered the following troubleshooting tip listed below (amongst others) at the website above. It worked flawlessly with my brand new unlocked stock Motorola NEXUS-6 (XT-1103) and Windows-7 PC. Thank you and big props to the developer(s) who posted it!
1.Connect your Nexus 6 to computer with a USB cable and open Device manager on your computer.
2.Look for ‘Android Composite ADB Interface‘ entry, right-click and select uninstall from the context menu.
3.In the uninstall pop-up that appears, tick ‘Delete the driver software for this device’ checkbox and press the “Ok” button.
4.Disconnect your phone from your computer.
5.Disable USB debugging on your Nexus 6 from Settings » Developer options » un-tick ‘USB debugging’ checkbox.
6.Put your Nexus 6 in MTP mode (It should be in MTP by default unless you selected the Camera (PTP) mode).
7.Connect your Nexus 6 to the computer again, and let the computer re-install drivers automatically. If it doesn’t re-installs driver, try toggling the ‘USB debugging’ option on your device.

Same here. Nexus 6 stock lollipop 5.1.1 with unlocked bootloader. I thought it was my personel windows 7 pc. But no its any pc I try to connect to. Found that out because I work at a big business full of windows pc's. I remember at one point not having this problem at all. Don't know if it was before one of the lollipop updates but I remember I used to connect my phone at work on any pc the pc would automatically open MTP asking me what I wanted to do. That was without adb turned on. I've tried everything searched everywhere, installed,uninstalled drivers from Google, Motorola etc. Even tried wugfresh's instructions. My pc does not recognize my phone at all. Mtp, Adb, Fastboot, nothing. Weird thing is I also have a nexus 5 and as soon as I connect it its recognized. Don't know if it maybe the cable that's the only thing I haven't tried since my cables are not Motorola cables, or nexus 6 original cable as that is the way I bought it. But it used to connect. Now I'm stuck, at a loss. Don't get it, called Motorola, Google, T-Mobile. I think they know nothing about phones as when I tell them the problem they look at me like I'm talking Chinese. If anyone knows what the problem is and have been able to fix it please hit me up @ [email protected] Just about to give up. I just don't understand what the problem maybe. Running stock lollipop 5.1.1 with unlocked bootloader never rooted. Thanks and hope someone can help.

I had the same issue. I installed the latest google drivers from the Android SDK and my computer would not recognize my Nexus 6. I couldn't use fastboot or anything. I was able to fix this though. With my Nexus 6 hooked up to my computer, I opened device manager. There was the "unknown device" which was my Nexus 6 obviously. I right clicked on it and attempted to install the driver, the automatic driver installation method could not find it. I had to point it directly to the file. The file is located in the android-sdk files. I had to point it to c:/android-sdk/extras/google Obviously location will vary depending on where you installed the android-sdk. Just make sure to only point it to extras/google. I wen't further in the first attempt and it didn't work. I hope this helps. I suck at explaing stuff.

Long Island NOOBIE said:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac-68355/
I discovered the following troubleshooting tip listed below (amongst others) at the website above. It worked flawlessly with my brand new unlocked stock Motorola NEXUS-6 (XT-1103) and Windows-7 PC. Thank you and big props to the developer(s) who posted it!
1.Connect your Nexus 6 to computer with a USB cable and open Device manager on your computer.
2.Look for ‘Android Composite ADB Interface‘ entry, right-click and select uninstall from the context menu.
3.In the uninstall pop-up that appears, tick ‘Delete the driver software for this device’ checkbox and press the “Ok” button.
4.Disconnect your phone from your computer.
5.Disable USB debugging on your Nexus 6 from Settings » Developer options » un-tick ‘USB debugging’ checkbox.
6.Put your Nexus 6 in MTP mode (It should be in MTP by default unless you selected the Camera (PTP) mode).
7.Connect your Nexus 6 to the computer again, and let the computer re-install drivers automatically. If it doesn’t re-installs driver, try toggling the ‘USB debugging’ option on your device.
Click to expand...
Click to collapse
This didn't work the first or second time. I did steps 2 through 7 3 times and then it worked. I must have had a lot of drivers installed.
So if it doesn't work the first time, keep uninstalling the drivers and try again and again. Worse case scenario, you have to install the drivers again. hope this helps.

I want to add my own tale to his thread with the hope that it will help someone. I could not see the Nexus 6 when I set MTP mode or MIDI mode. The phone showed up on the PC when I selected PTP (camera) mode. In my case, I had four external USB3 hard drives connected. I finally turned off the hard drives and then MTP mode would be visible, both as a Portable Device, named Nexus 6, in the Device Manger, and as the same under My Computer in Windows Explorer. After Imy PC recognized the Phone in MT mode, I tuned on the external drives and all were visible.

Cannot Get Drivers Installed for Windows 8.1 - Manual Installation or SDK

I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?

@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Thanks for the reply. Unfortunately that seems to have done nothing

I'd go w/ uninstall all other drivers first, change cables and see what happens.

Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.

morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?

cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...

efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.

OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.

morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk

FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.

Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.

Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?

Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979

Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?

Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.

Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.

Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452

Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.

How to install the correct drivers for fastboot to a Windows 10 laptop?

Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!

Omninano said:
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Click to expand...
Click to collapse
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish

Datclefxuj said:
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Click to expand...
Click to collapse
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!

Omninano said:
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Click to expand...
Click to collapse
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:

Datclefxuj said:
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Click to expand...
Click to collapse
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!

Omninano said:
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Click to expand...
Click to collapse
Great! You're welcome!

Windows update to ver. 20H2, Build 19042--Pixel 5 no longer recognized

On one of my laptops, Windows 10 performed a significant update to a new major version. All completed well, except that now my Google Pixel 5 is no longer appearing as a USB device. I have 2 laptops. Below is a device manager capture of the two laptops with the Google Pixel 5 plugged in. It appears that Windows decided to reclassify how Android phones now appear (no longer under "Portal" and now under "Android Devices"). My Pixel 5 doesn't show up, instead there's a "Google Nexus ADB Interface." Well, I uninstalled it and it automatically installed again... a check for online updates says it's the latest. But in Windows Explorer I do not see my Google Pixel 5 when setting to File Transfer mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've ditched my days of being involved in firmware updates because the latest phones are so capable now, especially with customizations. I thought perhaps a driver update directly from Google would be in order, but I'm unable to find anything... only stuff for the SDK.
I posted about this on Reddit r/GooglePixel, and got no help. If anyone here has a useful idea, please share. Thanks!

I think a few things could be happening. First, if you do not have ADB tools (Android ADK) installed, it may default to the phone name because it isn't finding the ADB interface, but the other phone interfaces (PTP for example). Was the Android SDK installed on the old version too?
Also, do you happen to have it linked to your computer with "My Phone"? You may get a more accurate name if you have linked it.
But ultimately, what is your goal?

bitpushr said:
I think a few things could be happening. First, if you do not have ADB tools (Android ADK) installed, it may default to the phone name because it isn't finding the ADB interface, but the other phone interfaces (PTP for example). Was the Android SDK installed on the old version too?
Also, do you happen to have it linked to your computer with "My Phone"? You may get a more accurate name if you have linked it.
But ultimately, what is your goal?
Click to expand...
Click to collapse
Yes, I had the ADB tools, Android SDK installed on only one computer., my primary. (On the older one it didn't have ADB. <--- FALSE). ClockworkMod was installed. But I wiped that clean.
Interesting, on my other computer I rechecked--I do have Android SDK installed on it... I just didn't put ClockworkMod on it.
Not sure what you mean by linking it with "My Phone." I have a USB-C cable, which has worked before just fine. My device is simply named "Pixel 5."
Btw, after installing all ADB drivers, I'm finding that when I plug in my Pixel 5, the "Google Nexus ADB Interface" node appears again under "Android Devices." What's going on? Is Windows somehow retrieving the ADB drivers from somewhere in a CAB file or something?
My goal is simple--I want to connect my Google Pixel 5 to my laptop and have it available as a USB storage device so I can transfer files to and from the device. I've done this for years... and this latest Windows update somehow screwed things up for me.
EDIT: For what it's worth, I was able to connect to Microsoft Windows Support via chat, for free. The technician looked this up and said it's a known issue for some configurations. Apparently there will be an update in a few weeks and he suggested rolling back to the previous version if I can't wait.

cytherian said:
Yes, I had the ADB tools, Android SDK installed on only one computer., my primary. (On the older one it didn't have ADB. <--- FALSE). ClockworkMod was installed. But I wiped that clean.
Interesting, on my other computer I rechecked--I do have Android SDK installed on it... I just didn't put ClockworkMod on it.
Not sure what you mean by linking it with "My Phone." I have a USB-C cable, which has worked before just fine. My device is simply named "Pixel 5."
Btw, after installing all ADB drivers, I'm finding that when I plug in my Pixel 5, the "Google Nexus ADB Interface" node appears again under "Android Devices." What's going on? Is Windows somehow retrieving the ADB drivers from somewhere in a CAB file or something?
My goal is simple--I want to connect my Google Pixel 5 to my laptop and have it available as a USB storage device so I can transfer files to and from the device. I've done this for years... and this latest Windows update somehow screwed things up for me.
EDIT: For what it's worth, I was able to connect to Microsoft Windows Support via chat, for free. The technician looked this up and said it's a known issue for some configurations. Apparently there will be an update in a few weeks and he suggested rolling back to the previous version if I can't wait.
Click to expand...
Click to collapse
Nonsense. I have the same Win 10 version and everything connects the same. They are clueless and reverting might bring way more problems than you wish to deal with. It's a driver issue plain and simple. There is a .inf file that needs to be reinstalled but I'll be darned if I remember which and what exactly to do. I'll research it a little tomorrow and see if I can find the solution. Whatever you do don't follow Microsoft help forums, you'll be installing crap that won't help.
edit: Ok this is what I did way back and it worked. Good luck. https://forum.xda-developers.com/t/...allation-on-windows-10.3570625/#post-71364316

bobby janow said:
Nonsense. I have the same Win 10 version and everything connects the same. They are clueless and reverting might bring way more problems than you wish to deal with. It's a driver issue plain and simple. There is a .inf file that needs to be reinstalled but I'll be darned if I remember which and what exactly to do. I'll research it a little tomorrow and see if I can find the solution. Whatever you do don't follow Microsoft help forums, you'll be installing crap that won't help.
edit: Ok this is what I did way back and it worked. Good luck. https://forum.xda-developers.com/t/...allation-on-windows-10.3570625/#post-71364316
Click to expand...
Click to collapse
Thanks...
Yeah, I've been around the block enough times to know that Microsoft Windows O/S installations are often buggy and fragile. I never take a major upgrade with ease. I always expect there may be an issue. And rolling back is only a very last resort.
In my case, I do not get an unknown or MTP device listed in the Device Manager. I tried doing the INF install... both with the wpdmtp.inf file and the Google provided android_winusb.inf.... No change. Every single time I plug in my Google Pixel 5, I get an "Android Devices" node with "Google Nexus ADB Interface" showing. And, still no device listed in Windows Explorer when I switch to USB File Transfer mode.

@cytherian It was worth a shot. My laptop says something different although it's basically the same I think. Mine says, "LeMobile Android Device" and under it Android composite ADB Interface. So even though I know you know these things and probably have tried each and every one I'll list them as I'd do them.
Make sure you have the very latest Platform tools
Try a different USB port
Try an A to C adapter rather than C to C
Try a different cable.
I think since it reinstalls auto then your laptop's drivers are fine. Mine is dated 2016 so I'm sure yours is the latest. It's gonna be something simple, you'll figure it out. In the meantime can you use a different computer that recognizes it and do the file transfers there?

bobby janow said:
@cytherian It was worth a shot. My laptop says something different although it's basically the same I think. Mine says, "LeMobile Android Device" and under it Android composite ADB Interface. So even though I know you know these things and probably have tried each and every one I'll list them as I'd do them.
Make sure you have the very latest Platform tools
Try a different USB port
Try an A to C adapter rather than C to C
Try a different cable.
I think since it reinstalls auto then your laptop's drivers are fine. Mine is dated 2016 so I'm sure yours is the latest. It's gonna be something simple, you'll figure it out. In the meantime can you use a different computer that recognizes it and do the file transfers there?
Click to expand...
Click to collapse
Yep, tried USB port change... no dice. Cable is same I've been using, but tried another. Both work on my other laptop. I am really not planning to delve back into firmware flashing, but maybe I should just go install the latest Android SDK and all the drivers from that to see if that somehow fixes things.

cytherian said:
Yep, tried USB port change... no dice. Cable is same I've been using, but tried another. Both work on my other laptop. I am really not planning to delve back into firmware flashing, but maybe I should just go install the latest Android SDK and all the drivers from that to see if that somehow fixes things.
Click to expand...
Click to collapse
Yes try that for sure.

I uninstalled ClockworkMod, but this driver keeps appearing. I went to USBDeview, found 3 listings for the ClockworkMod, deleted them...
STILL... when I plug in my damned Pixel 5, this ClockworkMod driver keeps coming up! I searched the Registry. Found a few entries. Deleted them. Restarted my computer. Plugged in my Pixel 5... It's Baaaaaaaaaaaaaaaaack!
What in the world?

cytherian said:
View attachment 5258887
I uninstalled ClockworkMod, but this driver keeps appearing. I went to USBDeview, found 3 listings for the ClockworkMod, deleted them...
STILL... when I plug in my damned Pixel 5, this ClockworkMod driver keeps coming up! I searched the Registry. Found a few entries. Deleted them. Restarted my computer. Plugged in my Pixel 5... It's Baaaaaaaaaaaaaaaaack!
What in the world?
Click to expand...
Click to collapse
To remove the driver:
Open and admin command prompt
Type dism /online /get-drivers
Look through the list for the above driver. Provider Name, Date, and Version should all match. Use the Published Name in the command below
Type dism /online /remove-driver oemXXX.inf
Do be careful, there are no "are you sure" prompts with this method.
You should also be able to force it to the Google USB driver as well if you have it downloaded from the android SDK. Use the update driver button and browse to the extras\google\usb_driver folder.

l7777 said:
To remove the driver:
Open and admin command prompt
Type dism /online /get-drivers
Look through the list for the above driver. Provider Name, Date, and Version should all match. Use the Published Name in the command below
Type dism /online /remove-driver oemXXX.inf
Do be careful, there are no "are you sure" prompts with this method.
You should also be able to force it to the Google USB driver as well if you have it downloaded from the android SDK. Use the update driver button and browse to the extras\google\usb_driver folder.
Click to expand...
Click to collapse
I ran DISM and did not find ClockwordMod indicated anywhere in the driver list.
I went ahead an plugged in my Pixel 5... the "Android Devices" node appears. "Google Nexus ADB Interface" is there again. It shows that pesky ClockwordMod driver again. And when I run DISM, there's no indication of "ClockworkMod" anywhere. I do see the AndroidUsbDeviceClass, android_winusb.inf, dated 8/28/2014, version 11.
Still, can't get access to my Pixel 5 in Explorer...

cytherian said:
I ran DISM and did not find ClockwordMod indicated anywhere in the driver list.
I went ahead an plugged in my Pixel 5... the "Android Devices" node appears. "Google Nexus ADB Interface" is there again. It shows that pesky ClockwordMod driver again. And when I run DISM, there's no indication of "ClockworkMod" anywhere. I do see the AndroidUsbDeviceClass, android_winusb.inf, dated 8/28/2014, version 11.
Still, can't get access to my Pixel 5 in Explorer...
Click to expand...
Click to collapse
Did it have enough buffer to scroll all the way to the beginning of the driver list? DISM Should list all third party drivers. You might want to do:
dism /online /get-drivers > drivers.txt
notepad drivers.txt
Another alternative since it sounds like the correct driver is indeed installed
Update driver button
Browse for driver
Let me pick from a list
Select Android Composit ADB Interface
EDIT:
I re-read the thread and it seems you're trying to get usb storage to work. That should be a different driver all together. The one you're looking at should be for the android debug bridge and should disappear if you turn off USB debugging. To confirm, go to the details tab of the device properties and see what hardware ID it is.
USB\VID_18D1&PID_4EE1 = USB Storage
USB\VID_18D1&PID_4EE1&MI_01 = ADB

l7777 said:
Did it have enough buffer to scroll all the way to the beginning of the driver list? DISM Should list all third party drivers. You might want to do:
dism /online /get-drivers > drivers.txt
notepad drivers.txt
Another alternative since it sounds like the correct driver is indeed installed
Update driver button
Browse for driver
Let me pick from a list
Select Android Composit ADB Interface
EDIT:
I re-read the thread and it seems you're trying to get usb storage to work. That should be a different driver all together. The one you're looking at should be for the android debug bridge and should disappear if you turn off USB debugging. To confirm, go to the details tab of the device properties and see what hardware ID it is.
USB\VID_18D1&PID_4EE1 = USB Storage
USB\VID_18D1&PID_4EE1&MI_01 = ADB
Click to expand...
Click to collapse
Yes, I thought it was implied... wanting Windows Explorer access to files would mean USB storage. I did have sufficient buffer to scroll through the whole list. In fact, I copy/pasted it into a text editor for easy searching.
Devices showing up under "Google Nexus ADB Interface":
USB\VID_18D1&PID_4EE1&REV_0440
USB\VID_18D1&PID_4EE1
NOTE - In Events I see this:
Device install requested
Device not migrated
Driver service added (WinUSB)
I should also note that in the System Tray, for USB devices, I see "Pixel 5." I have the option to eject if I wish. So, Windows is seeing the device but perhaps somehow the wrong driver is being mapped?
What really bugs me is... WHY is this "ClockworkMod" driver even showing up? Is Windows dynamically picking it up somewhere?

cytherian said:
Yes, I thought it was implied... wanting Windows Explorer access to files would mean USB storage. I did have sufficient buffer to scroll through the whole list. In fact, I copy/pasted it into a text editor for easy searching.
Devices showing up under "Google Nexus ADB Interface":
USB\VID_18D1&PID_4EE1&REV_0440
USB\VID_18D1&PID_4EE1
NOTE - In Events I see this:
Device install requested
Device not migrated
Driver service added (WinUSB)
I should also note that in the System Tray, for USB devices, I see "Pixel 5." I have the option to eject if I wish. So, Windows is seeing the device but perhaps somehow the wrong driver is being mapped?
What really bugs me is... WHY is this "ClockworkMod" driver even showing up? Is Windows dynamically picking it up somewhere?
Click to expand...
Click to collapse
Windows loads drivers based on the hardware IDs. For some reason the ClockworkMod driver is claiming to be for one of those hardware ids. Now that I know it's supposed to be the storage driver try this:
Update Driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
See if "MTP USB Device" is listed
Another option to identify the clockworkmod driver
Details tab
Inf name
If it starts with oemXX.inf it should be safe to use dism to remove it

You know what's so bizarre?
Published Name : oem47.inf
Original File Name : android_winusb.inf
Inbox : No
Class Name : AndroidUsbDeviceClass
Provider Name : ClockworkMod
Date : 8/27/2012
Version : 7.0.0.4
Notice it's indicating the original filename as "android_winusb.inf."
Well, sure enough oem47.inf is in the Windows/INF directory, and it has "ClockworkMod" info in it.
I tried removing it with dism /online /remove-driver /driver: oem47.inf
Failed. Error: 50, "This command can only be used with an offline image."
I discovered that I could rename the files (oem47.infx, oem47.pnfx), then move them off to a TEMP folder. I rebooted... and oddly, "oem47.inf" is still showing in the DISM driver list. I ran USBDeview, noticed it was still there, so I deleted it. Ran the DISM get-drivers cmd again... STILL showing up. It did NOT mysteriously reappear in Windows/INF. So I figured it must be in the registry. The only registry entries I could find is "oem47.inf" among others in "Owners" of various DLL files.

cytherian said:
You know what's so bizarre?
Published Name : oem47.inf
Original File Name : android_winusb.inf
Inbox : No
Class Name : AndroidUsbDeviceClass
Provider Name : ClockworkMod
Date : 8/27/2012
Version : 7.0.0.4
Notice it's indicating the original filename as "android_winusb.inf."
Well, sure enough oem47.inf is in the Windows/INF directory, and it has "ClockworkMod" info in it.
I tried removing it with dism /online /remove-driver /driver: oem47.inf
Failed. Error: 50, "This command can only be used with an offline image."
I discovered that I could rename the files (oem47.infx, oem47.pnfx), then move them off to a TEMP folder. I rebooted... and oddly, "oem47.inf" is still showing in the DISM driver list. I ran USBDeview, noticed it was still there, so I deleted it. Ran the DISM get-drivers cmd again... STILL showing up. It did NOT mysteriously reappear in Windows/INF. So I figured it must be in the registry. The only registry entries I could find is "oem47.inf" among others in "Owners" of various DLL files.
Click to expand...
Click to collapse
see if pnputil will do the job. I could've sworn I've used DISM to remove online drivers before.
pnputil -d oem47.inf
or
pnputil -f -d oem47.inf

Thanks! That did the trick --> pnputil -d oem47.inf
And... I plugged in my Pixel 5... low & behold, Windows tells me it discovered a new device, setting it up... and...
YES!
I see it now in Windows Explorer!
So this was the problem. A LEGACY issue, with a leftover INF file. Somehow this was taking priority, because in the OEM list, the proper one is oem87.inf.
What an ordeal. Can you imagine if a novice had to face this?

cytherian said:
Thanks! That did the trick --> pnputil -d oem47.inf
And... I plugged in my Pixel 5... low & behold, Windows tells me it discovered a new device, setting it up... and...
YES!
I see it now in Windows Explorer!
So this was the problem. A LEGACY issue, with a leftover INF file. Somehow this was taking priority, because in the OEM list, the proper one is oem87.inf.
What an ordeal. Can you imagine if a novice had to face this?
Click to expand...
Click to collapse
Glad you got it worked out. It is a bit of driver hell. Side effect of supporting nearly every piece of hardware that one could plug into a computer. They should make it easier to manage them though. I'm actually surprised that it's still using a third party driver (oemXX.inf). My 20H2 system is using a built in driver, wpdmtp.inf.

l7777 said:
Glad you got it worked out. It is a bit of driver hell. Side effect of supporting nearly every piece of hardware that one could plug into a computer. They should make it easier to manage them though. I'm actually surprised that it's still using a third party driver (oemXX.inf). My 20H2 system is using a built in driver, wpdmtp.inf.
Click to expand...
Click to collapse
Thanks. Yes, at this late stage of the game, Windows Device Management should be revised. It's the same old interface we've had for almost 2 decades. Such a PITA to update drivers. The thing is, the Google Pixel 5 is from... GOOGLE. A software giant. Wouldn't Microsoft ensure that those drivers will be picked up and not allow an obsolete driver to override? Just boggles my mind.
Well, on my system now, the Pixel 5 is being supported by the same driver as yours, wpdmtp.inf. It seems to have been mapped when Windows 10 recognized the Pixel 5 as a new device. It was the old driver that was blocking the installation, somehow.

cytherian said:
Thanks. Yes, at this late stage of the game, Windows Device Management should be revised. It's the same old interface we've had for almost 2 decades. Such a PITA to update drivers. The thing is, the Google Pixel 5 is from... GOOGLE. A software giant. Wouldn't Microsoft ensure that those drivers will be picked up and not allow an obsolete driver to override? Just boggles my mind.
Well, on my system now, the Pixel 5 is being supported by the same driver as yours, wpdmtp.inf. It seems to have been mapped when Windows 10 recognized the Pixel 5 as a new device. It was the old driver that was blocking the installation, somehow.
Click to expand...
Click to collapse
Right, and that driver is dated 6/21/2006. The clockworkmod driver is dated 2012. I suspect that Window's logic matches the device id first and then looks for the latest driver available. In this case the question is why was the clockworkmod driver claiming to be for the storage device id rather than the ADB device id. I'd have been curious to know if you could have manually chosen the older (and correct) driver.

Question Unable to send files via USB

Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?

CyanFrank said:
Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?
Click to expand...
Click to collapse
Airdroid. No need for a cable.

When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
If the MTP makes it stutter it could be a problem with MTP or simply that MTP does more traffic and is uncovering lower level problems.

CyanFrank said:
...There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
Click to expand...
Click to collapse
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.

manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.
Click to expand...
Click to collapse
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install

Renate said:
When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
Click to expand...
Click to collapse
No, phone is charging and debugging is enabled so that I see two notifications.
Tried the first command and phone started disconnecting just like with MTP enabled. ADB had stopped working.
manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager?
Click to expand...
Click to collapse
It used to, but apparently I messed up with drivers while trying to solve the issue, so it's not working right now.
hammered58 said:
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install
Click to expand...
Click to collapse
Yeah I noticed LeMobile drivers are available to download. There is Android Composite ADB device listed as "LeMobile" but ADB still not fixed.
And it seems like I'm back to sqaure one because there's the very first issue I had: after choosing MTP on my phone all options become gray and it returns back to "only charging" after few seconds. Sometimes it even starts disconnecting/connecting.

Yeah it seems something is particularly wrong with my home PC because MTP works flawlessly with my work PC. Didn't have to install any drivers etc.

Do you have the latest windows platform tools installed?

Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.

Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
Yes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bobby janow said:
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.
Click to expand...
Click to collapse
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.

CyanFrank said:
Yes.View attachment 5774787
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.
Click to expand...
Click to collapse
That could be the one. If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one. I searched and there are a bunch of "solutions" out there and I hope you find the correct one before you have to reinstall the whole darn OS. I'll keep looking though. I was so frustrated by it I wanted to throw the laptop out the windows. lol. I still think it's one pesky driver.

I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.

EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.
Click to expand...
Click to collapse
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.

bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.
Click to expand...
Click to collapse
I mean I probably would do the same but if OP is already at the point of reinstalling Windows, I figured I would provide some less annoying options. Virtual machines have saved me immense amounts of frustration over the years and Player is phenomenal for something free of charge.

bobby janow said:
If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one.
Click to expand...
Click to collapse
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick.
Click to expand...
Click to collapse
Yeah, actually didn't think about that, thanks. I'll give it a try when I get enough time.
bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall.
Click to expand...
Click to collapse
As I said, I have no USB A-C cable that supports data transfer. But I'll borrow one to at least try.
And the thing is it might not fix the problem as well if drivers are screwed up.

If you have another USB-C port, I would try that as well. Sometimes different ports, even on the same controller, can have different results.

Unfortunately I have just one USB-C port.

CyanFrank said:
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
Click to expand...
Click to collapse
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.

bobby janow said:
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.
Click to expand...
Click to collapse
Yeah, I tried that as well.
And forgot to mention that I borrowed USB A-C cable and MTP actually worked. It's not as stable as it should be (sometimes it disconnects) but still it works.