How I fixed the MTP issues on Nexus 7 - Nexus 7 General

Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits.
Yesterday, I checked the optional Windows updates and noticed a new Samsung MTP driver. So I updated the driver and when I connected the tablet running on 4.1.1, the device was not detected. Today, after I got the OTA update, I tried again to connect the tablet and it failed to detect the device properly.
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
2) Right click on it and select Properties.
3) Click on Change Settings button.
4) Go to Driver tab and click on Uninstall button.
Make sure you check the Delete Driver option, when you uninstall the driver.
I did not have to reboot the computer, by simply connecting the tablet Windows detected the new hardware and reinstalled the proper drivers.
Now I can access both my Nexus phone and tablet, using the same cable and through adb.
Not sure if the combination of both 4.1.2 and new Samsung drivers helped, but the above steps fixed the MTP detection issues I had. Check the Microsoft driver date, is from 2006???
{
"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'm on Android 4.2.1 and I tried your method but I got a "No Driver Found" error.

Fixed !
I'm on 4.2.1 stock ROM too and it worked perfectly for me, as described !
Thank you very much !:good:

Teck, nobody online aside from you could do anything with this, your instructions fixed it.
So, two questions. Do you have a paypal, and if you do, what's the price of your usual beer?
I'm buying you one.
also any idea on how to fix the same issue on an ipod touch?

If anyone having problems turn off USB debugging and device will show up
Sent from my HTC One X using xda premium

acidspider said:
If anyone having problems turn off USB debugging and device will show up
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I had to do. Just place your files inside your internal memory before you turn on your debugging.
Sent from my Nexus 7 using xda app-developers app

Another way of fixing this on Windows 8: This problem may happen because you have the Google ADB driver from the Android SDK installed. Windows will pick the ADB driver over the MTP driver, even when USB debugging is turned off on the Nexus 7. It also comes back when you upgrade from Windows 8 to Windows 8.1. To fix this:
Plug the Nexus 7 in and make sure USB mode is set to MTP
Run devmgmt.msc
Locate the ADB driver, which may be under "Android Devices" or "ADB Devices"
Right-click on it and select "Update driver software"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
With "Show compatible hardware" checked you should see two drivers under "Model":
"Android ADB Interface"
Either "MTP USB Device" or "Composite USB Device"
Select "MTP/Composite USB Device" (that is, the one that isn't "Android ADB Interface") and click Next.
Device should now appear as an MTP device.
Confirmed working with the Nexus 7 2013 as well.

Thank you, that worked exactly how you listed it.

TheBeano said:
Another way of fixing this on Windows 8: This problem may happen because you have the Google ADB driver from the Android SDK installed. Windows will pick the ADB driver over the MTP driver, even when USB debugging is turned off on the Nexus 7. To fix this:
Plug the Nexus 7 in and make sure USB mode is set to MTP
Run devmgmt.msc
Locate the ADB driver, which may be under "Android Devices" or "ADB Devices"
Right-click on it and select "Update driver software"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
With "Show compatible hardware" checked you should see these two drivers under "Model":
"Android ADB Interface"
"MTP USB Device"
Select "MTP USB Device" and click Next.
Device should now appear as an MTP device.
Click to expand...
Click to collapse
Reinstalled ADB drivers to try this... MTB device does not appear on list.
Why can't someone just post a link to the drivers needed for MTB to work?

drumtrucker said:
Reinstalled ADB drivers to try this... MTB device does not appear on list.
Why can't someone just post a link to the drivers needed for MTB to work?
Click to expand...
Click to collapse
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!

Hi. Totally confused Nexus 7 noob
TECK said:
Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits....
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
Click to expand...
Click to collapse
I've been reading and searching and reading and.... on my Win 7/64, there is no "Other" or "Unspecified Devices" in Device Manager. There is no Nexus 7 under any option in Device Manager. {sigh} Device Manager also does not show either "Android Devices" or "ADB Devices."
I've tried having Windows search for new hardware (it found my wireless router, not my Nexus 7).
I've swapped out the USB cables and tried different USB plugs on the CPU and on a powered hub (the plugs all work with other USB devices).
The Nexus WILL read a thumb drive, so the plug on the Nexus works
I tried turning off the Nexus, rebooting the computer and then plugging the Nexus back in and turning it on. Nothing, Windows did not see it "arrive."
"Safely remove hardware" does not see it.
I looked for a folder on the C: drive that has google drivers in it, no such folder.
I unlocked Developer Options and tried switching between Camera and MTP modes.
I turned off USB debugging.
I have a semi-solid memory that I WAS able to plug the Nexus in and TRF files across a USB cord when I first got it (mid-December) -- but I'm not 100% sure (I'm old and my brain leaks...).
My Win 7 is completely updated, according to MS. I'm baffled. What can I try next? Thanks. (Sorry this is long -- I DID watch the funny noob movie when I registered, and tried to balance: "be short" with "provide all the info.")

It works for me, thank you very much!

SnowTao said:
My Win 7 is completely updated, according to MS. I'm baffled. What can I try next?
Click to expand...
Click to collapse
Try usbdeview from Nirsoft, it will show you what device (if any) the Nexus 7 is registering as when you plug it in.

Doesn't Nexus 7 Toolkit (the tool for rooting and all) also install some drivers?
I haven't really have any problems connecting N7 to W7 (lol) stock, but since I've rooted it (and the toolkit installed their own drivers), I've had even less problems.
Only thing I don't like is MTP itself, I'd prefer removable drive, so I could easily manage files and all from total commander, but that's a design flaw, not a bug.

stalnie betw.
drumtrucker said:
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!
Click to expand...
Click to collapse
You the man! This worked for me too...was getting really frustrated seeing that MTP yellow error icon and not having my N7 appear in explorer during USB debugging mode.

thanks!
TECK said:
Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits.
Yesterday, I checked the optional Windows updates and noticed a new Samsung MTP driver. So I updated the driver and when I connected the tablet running on 4.1.1, the device was not detected. Today, after I got the OTA update, I tried again to connect the tablet and it failed to detect the device properly.
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
2) Right click on it and select Properties.
3) Click on Change Settings button.
4) Go to Driver tab and click on Uninstall button.
Make sure you check the Delete Driver option, when you uninstall the driver.
I did not have to reboot the computer, by simply connecting the tablet Windows detected the new hardware and reinstalled the proper drivers.
Now I can access both my Nexus phone and tablet, using the same cable and through adb.
Not sure if the combination of both 4.1.2 and new Samsung drivers helped, but the above steps fixed the MTP detection issues I had. Check the Microsoft driver date, is from 2006???
Click to expand...
Click to collapse
Thanks! Simple and brilliant

drumtrucker said:
Reinstalled ADB drivers to try this... MTB device does not appear on list.
Why can't someone just post a link to the drivers needed for MTB to work?
Click to expand...
Click to collapse
TheBeano said:
Another way of fixing this on Windows 8: This problem may happen because you have the Google ADB driver from the Android SDK installed. Windows will pick the ADB driver over the MTP driver, even when USB debugging is turned off on the Nexus 7. To fix this:
Plug the Nexus 7 in and make sure USB mode is set to MTP
Run devmgmt.msc
Locate the ADB driver, which may be under "Android Devices" or "ADB Devices"
Right-click on it and select "Update driver software"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
With "Show compatible hardware" checked you should see these two drivers under "Model":
"Android ADB Interface"
"MTP USB Device"
Select "MTP USB Device" and click Next.
Device should now appear as an MTP device.
Click to expand...
Click to collapse
I tried this, but it did not work for me. With "MTP USB Device" driver installed, I still could not see my Nexus 7 in Window Explorer. I tried deleting drivers, installing, updating, to no avail. Finally, one of the times I picked "Let me pick from a list of device drivers on my computer", I saw a "USB Composite Device" in the list. I picked it. It installed, and suddenly my Nexus 7 was visible in Windows Explorer. Here is the info on the driver:
Driver Provider: Microsoft
Driver Date: 6/21/2006
Driver Version: 6.1.7600.16385
Digital Signer: Microsoft Windows.
I have a Nexus 7, running Android version 4.2.2
The computer I was having trouble with is running Windows 7 Pro. I have another computer, running Windows 7 Home Premium. It has always been able to see the Nexus 7 in Windows Explorer. It has the same *old* driver installed. I did not know where to get that driver from. I just hit on it using the procedure above.
Here are some of the drivers which did NOT work for me:
Driver Provider: Google Inc.
Driver Date: 5/24/2012
Driver Version: 6.0.0.0
Driver Provider: Google Inc.
Driver Date: 8/27/2012
Driver Version: 7.0.0.1

drumtrucker said:
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!
Click to expand...
Click to collapse
this worked perfect on my n4 win8x64
thanks
stupid google and lg, thanks a lot for not providing good drivers or usb disk mode (like nokia)

worked fine for me also, thnx a lot

Thanks Bro!!!
TECK said:
Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits.
Yesterday, I checked the optional Windows updates and noticed a new Samsung MTP driver. So I updated the driver and when I connected the tablet running on 4.1.1, the device was not detected. Today, after I got the OTA update, I tried again to connect the tablet and it failed to detect the device properly.
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
2) Right click on it and select Properties.
3) Click on Change Settings button.
4) Go to Driver tab and click on Uninstall button.
Make sure you check the Delete Driver option, when you uninstall the driver.
I did not have to reboot the computer, by simply connecting the tablet Windows detected the new hardware and reinstalled the proper drivers.
Now I can access both my Nexus phone and tablet, using the same cable and through adb.
Not sure if the combination of both 4.1.2 and new Samsung drivers helped, but the above steps fixed the MTP detection issues I had. Check the Microsoft driver date, is from 2006???
Click to expand...
Click to collapse
Literally banged my head on computer before finding your solution.. Just was not deleting the old drivers. Uninstalled it so many times. Deleting the old drivers is the key.
However, still my TV is not liking the MTP. Banging my head on TV now.

Related

ADB Drivers

Hey everyone,
I have been happily using android on nand for quite sometime, and everything has been going well. However, I must have the wrong adb driver installed on my windows 7 computer and can't seem to remove it fully or install the proper one ever. Every time I remove it from device manager, and plug it back in, windows finds it as an HTC composite device, and adb through command line can't find any devices, ever! I would really like to be able to use this feature for things like tethering and what not.
Also, if anyone has any information on how to tether using any OS, windows, mac or linux, I would greatly appreciate it, along with any applications that might be helpful! I have done proxoid in the past and it worked well, pdaNet looks like it might work, but again I don't have a connection to my windows computer!
Thanks in advance for all of the help!
I am using the android SDK usb driver for ADB, you just have to edit a file and add the vendor ID. I can do things like adb logcat, adb shell gives me odd characters in directory listings,I get a ? from adb devices, not sure what that is about.
C:\Documents and Settings\Administrator\.android\adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e79
0x0bb4
The 0e79 is for my Archos tablet, works fine there. 0bb4 is what showed up in device manager when I plugged in the phone.
I tried to install that driver for my Polaris and it doesn't work.
It shows "Installing Android Phone" while I have my device plugged in. It takes forever and seems that the USB connection hangs the driver install process, but as soon as I disconnect my device, Windows shows me an error message.
Instructions for Vista\Windows 7
For WinVista/Win7
These OS will install Android as a mass storage device. You must uninstall the driver and update to the android driver model.
Instructions:
1) Unplug all removable devices(thumb drive, sdcards, etc) beside the Android phone.
2) Locate "Device Manager", usually under "control panel"
3) Select "Universal Serial Bus Controllers"
4) Select USB Mass Storage Device.
Note: to check if you have the correct device, click on the details tab and select "compatible ids" under properties. There should be three items listed under value.
5) Select uninstall driver
6) Close the window. Now in device manager a new "Android Phone USB device" with a yellow! will appear... If not, Unplug your android device or select Action -> Scan.
Note: view optional steps below if you still have problem with the your windows automatically installing drivers.
7) Click on the "Android Phone USB device"
8) Select "browse my computer to driver software"
9) Under "search this location for driver", Browse for the location that you have unzip the android_usb_windows and select the corresponding folder for your system(AMD64 for 64bit systems or x86 for 32bit systems. Right click -> properties on "My Computer" to check which system you have)
The driver is now installed and is ready to use.r
***Optional.
1. Go to System under Control Pandel.
2. Click on Hardware Tab and Under "Device Installation" select “Never search windows update for drivers”, then OK.
3. Go to Enable debugging on your phone. (Settings->Applications->Development->USB debugging).
4. Run USBDeview and remove all instances of Android Phone
5. Unplug your phone, and plug it in again.
7. Continue on step 7) above.
To turn off search windows update in windows 7, use this link below
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
To turn off automatic driver installation in windows 7, use the link below
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
SuperJMN said:
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
Click to expand...
Click to collapse
mine hung as well, what i ended up doing was turnng off the automatic installation. Then uninstalled the adb interface driver that was already installed. Then turning back on automatic installation. Then plugging phone back in and as it was installing automatically, manually installing the adb interface driver at the same time. Eventally the automatic install would error out and the manual install would work. It took like 15 or 20 minutes for it to finish.
when i uninstalled the adb interface, it turned into ''android phone'' in device manager. That was the driver i manually installed while the phone was automatically installing. I know it dont make much sense but it worked for me.
It looks like that will be my fate as well. It also says, that when I do the manual install of the ADB drivers that I already have the most current version installed!!! OH well, keep trying!
Same behavior on my pc with windows 7 32-bits.
When I have lucky the adb driver is connected (working correctly) for a few minutes and then it's disconnected.
i've tried various things to install adb driver, since last night but i've got nothing. i can't install adb driver for my xperia arc.
i installed sdk manager and usb driver. but when i try to install or update driver, i always see this message like "you're using the latest version". So i can't install it.
and also i've tried to uninstall driver and unplugged / plugged my device. then w7 automatically install driver. so i can't install adb driver again.
i want to root my phone, using this way at this link http://forum.xda-developers.com/showthread.php?p=18805560#post18805560
so i must install adb driver, please help me.
thanks everybody
edit: i've windows 7 home premium, 64-bits

[DRIVERS] Nexus 4 Driver for Windows

If you have windows, you will need these drivers to use ADB or Fastboot with your Nexus 4. The long method of getting this is downloading the SDK and running it. I have extracted the drivers and put it into a rar file for easy use.
Follow these steps if you haven't plugged your phone into your computer before.
1. Download the file.
2. Extra the files into a folder.
3. Plug your phone in.
4. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
5. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
If you already installed other drivers and they don't work for you. Download the drivers below and follow these steps:
1. Enable USB Debugging on your phone.
2. Plug your phone into your computer.
3. Go to Device Manager on your computer and locate your device. It will either be under "Android Devices" or "Other Devices" depending whether drivers have been installed or not.
4. Right click on your phone and select "Uninstall."
5. In the box that appears, check the option to "Delete the driver software for this device" then proceed.
6. When that is done, go back to Device Manager and refresh.
7. Locate your phone and right click to select "Update Driver Software."
8. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
9. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
10. Unplug your phone and restart your computer.
11. Plug it back in and everything should work.
Download link:
http://www.mediafire.com/?8xb50uktar8096i
Thanks to efrant for clarifying exactly how to manually select your drivers.
I would suggest everyone download Android SDK.
You have a Nexus device right?
http://developer.android.com/sdk/index.html
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
ijip said:
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
This thread is for Nexus 4 drivers, not the SDK.
Ask your question in the Q&A section.
theexel said:
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
Click to expand...
Click to collapse
Yep, I never needed the whole SDK before. I only download the platform tools too.
Have any other ADB drivers installed? Because then you need to uninstall those:
Go into command prompt and write:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
Delete all devices including driver software in the "Android Device" section.
Then reinstall the Nexus 4 drivers.
If that still doesn't work, update the driver when connected with usb debugging on and manually add by rightclicking the device, click update driver software, then the "Browse my computer for driver software", then "Let me pick from a list..." then "Show all devices" and then Have disk.
Then you simply point to the driver and select the "Android ADB Interface" (Or something like that) it also has driver for bootloader and composite, bootloader is for fastboot, can't remember what composite is for, but you shouldn't use those.
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
qvert said:
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
Click to expand...
Click to collapse
Go to Device Manager on your PC. If debug mode is enabled, you should see your device listed as an Android phone or something of the sort. If it has a yellow exclamation mark or some sort of symbol next to it, then that means the drivers aren't properly installed. Assuming that is the case, follow FISKER_Q's directions:
Right clicking the device, click update driver software, then the "Browse my computer for driver software." Select the usb_driver folder that you extracted and you should be good to go.
Subbed to refer to later when i have the N4
Sent from my Nexus S
jark99 said:
Subbed to refer to later when i have the N4
Sent from my Nexus S
Click to expand...
Click to collapse
This thread is also in the Misc section of the reference guide in case you can't find it later
I did the same thing and I cant get adb to see my device however fastboot will =/
Shambala001 said:
I did the same thing and I cant get adb to see my device however fastboot will =/
Click to expand...
Click to collapse
Did you enable debugging on your phone yet?
If not, go to Settings > About phone, then tap on "Build Number" 7 times. Go back to settings and you will see developer options. Go in there to enable USB debugging.
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Nitemare3219 said:
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Click to expand...
Click to collapse
Glad you got it figured out. :good:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Try leaving the phone plug in. Go to Device Manager. Find the ADB drivers and uninstall it. While in Device Manager, have it scan for new changes. You should see your phone appear. Right click it and manually install the drivers.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
IAMLordspeed said:
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
Click to expand...
Click to collapse
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Stryder5 said:
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Click to expand...
Click to collapse
I had to put a check in the box next to "Delete the driver software for this device" to get this to work. Otherwise Device Manager will keep detecting the old drivers.

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.

Bricked my device?

Hi! I made a huge mistake, I deleted my whole storage on the M7 and also wiped it completely. I didn't manage to get fastboot drivers running on my pc so the M7 has just been in my drawer for some time now.
Now I want to get it going again. I have a Windows 10 Laptop (very old laptop though) and on my M7 I still have hboot 1.44.0000 and TWRP 2.8.6.0.
Can someone please tell me how to get the drivers going so I can transfer a rom onto my device?
HitchslapHTC said:
Hi! I made a huge mistake, I deleted my whole storage on the M7 and also wiped it completely. I didn't manage to get fastboot drivers running on my pc so the M7 has just been in my drawer for some time now.
Now I want to get it going again. I have a Windows 10 Laptop (very old laptop though) and on my M7 I still have hboot 1.44.0000 and TWRP 2.8.6.0.
Can someone please tell me how to get the drivers going so I can transfer a rom onto my device?
Click to expand...
Click to collapse
Boot your device to the bootloader in fastboot mode and connect it to your pc.
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install the latest driver from the list. :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
Boot your device to the bootloader in fastboot mode and connect it to your pc.
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install the latest driver from the list. :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you for your answer! Unfortunately my computer does not recognize I plugged in the device. It's in fastboot mode though.
{
"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"
}
HitchslapHTC said:
Thank you for your answer! Unfortunately my computer does not recognize I plugged in the device. It's in fastboot mode though.
Click to expand...
Click to collapse
So your computer does not detect the device at all? No connection sound?
Try a different usb port and/or cable. It's best to avoid ports on the front of your pc. Make sure to use a port at the rear. It's possible there could be a hardware issue with the port the phone though.
If you have access to a Linux OS it would be worth trying it with that. Since Linux doesn't require drivers to connect to Android devices. If Linux doesn't see it then it's probably the port on the phone. :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
So your computer does not detect the device at all? No connection sound?
Try a different usb port and/or cable. It's best to avoid ports on the front of your pc. Make sure to use a port at the rear. It's possible there could be a hardware issue with the port the phone though.
If you have access to a Linux OS it would be worth trying it with that. Since Linux doesn't require drivers to connect to Android devices. If Linux doesn't see it then it's probably the port on the phone. :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I tried it with a collegue's pc at work, it shows that it's an unknown usb device, mine doesn't even do that (matter of the usb port version?). I can't do stuff at his pc obviously but I don't think the M7's USB is broken!
Would it be possible to copy a rom via OTG/USB stick onto the device?
HitchslapHTC said:
I tried it with a collegue's pc at work, it shows that it's an unknown usb device, mine doesn't even do that (matter of the usb port version?). I can't do stuff at his pc obviously but I don't think the M7's USB is broken!
Would it be possible to copy a rom via OTG/USB stick onto the device?
Click to expand...
Click to collapse
Ok that's a good sign that it's detected by other pc. usb2 or usb3 ports are best. Standard usb ports and internal/external usb hubs should be avoided. You could try unplugging all non essential usb devices then uninstall your usb host controllers. They will auto install after rebooting the computer and may at least force renegotiation of newly connected devices.
Failing that make a bootable Linux usb pendrive. You can then boot Linux from the usb drive and try connecting with that. I have a mini guide here on how to do this. :good:
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219
Sent from my SM-T230 using Tapatalk
Danny201281 said:
Ok that's a good sign that it's detected by other pc. usb2 or usb3 ports are best. Standard usb ports and internal/external usb hubs should be avoided. You could try unplugging all non essential usb devices then uninstall your usb host controllers. They will auto install after rebooting the computer and may at least force renegotiation of newly connected devices.
Failing that make a bootable Linux usb pendrive. You can then boot Linux from the usb drive and try connecting with that. I have a mini guide here on how to do this. :good:
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Deinstalling the usb host controllers didnt change anything
I'll try it at home again. There I have also an Ubuntu linux installation on my Windows pc. But I remember that didnt help either last time I tried it (I think I even installed it for that specific reason).
Edit: Ok I'm home, M7 gets detected in fastboot mode in Win 10 but is unknown device. What do I do next?
HitchslapHTC said:
Deinstalling the usb host controllers didnt change anything
I'll try it at home again. There I have also an Ubuntu linux installation on my Windows pc. But I remember that didnt help either last time I tried it (I think I even installed it for that specific reason).
Edit: Ok I'm home, M7 gets detected in fastboot mode in Win 10 but is unknown device. What do I do next?
Click to expand...
Click to collapse
Install this http://download1443.mediafire.com/qzmgethe1ntg/2lyl151pt5pah2v/HTC-Mobile-Driver-v4.17.0.001.zip
Reboot pc and try again :fingers-crossed:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
Install this http://download1443.mediafire.com/qzmgethe1ntg/2lyl151pt5pah2v/HTC-Mobile-Driver-v4.17.0.001.zip
Reboot pc and try again :fingers-crossed:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Nothing changed
When I try to install a driver (I have downloaded various M7 drivers) manually Windows always says that the newest driver is already installed...
I have no idea where the one you gave me is installed though...
HitchslapHTC said:
Nothing changed
When I try to install a driver (I have downloaded various M7 drivers) manually Windows always says that the newest driver is already installed...
I have no idea where the one you gave me is installed though...
Click to expand...
Click to collapse
Did you extract the zip? Maybe I should have mentioned that. The download in provided is a zip file. But it contains an .exe installer. Extract the installer and run it to install the driver.
You said it was detected as unknown device. Is the device now showing up in device manager, even as unknown device? If so have you tried the procedure I posted earlier?
Sent from my SM-T230 using Tapatalk
Yes I installed the exe, that wasnt the problem
You mean this one?
"
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install the latest driver from the list. "
I cant find "Android USB devices"
HitchslapHTC said:
Yes I installed the exe, that wasnt the problem
You mean this one?
"
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install the latest driver from the list. "
I cant find "Android USB devices"
Click to expand...
Click to collapse
The only other thing I can think is that is because you have hboot 1.44.
Hboot 1.44 and Windows 8 would not work together. Maybe it's the same for Windows 10. I don't know to be honest.
If you have a ubuntu os try it with that. Connect with usb then in a terminal window type
Code:
lsusb
That will give you a list of devices attached. If you see a device something like "Hightec Computer company" that's your m7. And adb/fastboot should work on Linux.
Alternatively if you have an OTG device you could use it to flash a Rom.
Sent from my HTC One using Tapatalk
In Linux it says unknown after the command.
Well, I ordered an OTG cable, hope that'll work in TWRP.
Thanks anyway!
Sent from my Moto X using XDA Free mobile app
Danny201281 said:
The only other thing I can think is that is because you have hboot 1.44.
Hboot 1.44 and Windows 8 would not work together. Maybe it's the same for Windows 10. I don't know to be honest.
If you have a ubuntu os try it with that. Connect with usb then in a terminal window type
Code:
lsusb
That will give you a list of devices attached. If you see a device something like "Hightec Computer company" that's your m7. And adb/fastboot should work on Linux.
Alternatively if you have an OTG device you could use it to flash a Rom.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
HitchslapHTC said:
In Linux it says unknown after the command.
Well, I ordered an OTG cable, hope that'll work in TWRP.
Thanks anyway!
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
lsusb is a basic Linux command if it returned unknown you probably typed it wrong.
lsusb = list Usb ----- {LSUSB}
Did you use a Capital I (i) instead of Lowercase L (l). ?
Sent from my HTC One using Tapatalk
No no, it listed all my USB devices with an unknown one (literally ) in between which is the M7.
Sent from my Moto X using XDA Free mobile app
HitchslapHTC said:
No no, it listed all my USB devices with an unknown one (literally ) in between which is the M7.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure I understand? A screenshot would help if you can provide one :good:
Here's one from mine. With M7 connected in bootloader.
Sent from my HTC One using Tapatalk
Danny201281 said:
I'm not sure I understand? A screenshot would help if you can provide one :good:
Here's one from mine. With M7 connected in bootloader.
View attachment 3656640
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I have the "same" list, just imagine instead of "Ideazon, Inc" it says "Unknown"
HitchslapHTC said:
I have the "same" list, just imagine instead of "Ideazon, Inc" it says "Unknown"
Click to expand...
Click to collapse
Ok, but do you see HTC (High Tech Computer Corp) in your list?
If you do then Linux sees your phone and adb/fastboot will work :good:
Sent from my HTC One using Tapatalk
No I see Unknown. And my other devices. No HTC related thing.
Sent from my Moto X using XDA Free mobile app
Danny201281 said:
Hboot 1.44 and Windows 8 would not work together. Maybe it's the same for Windows 10.
Click to expand...
Click to collapse
Yes it is the same with 10, it won't connect with hboot 1.44. Ubuntu or Win 7 should work. Alternatively there should be a workaround for Win8 that's also supposed to works for 10. Will try to find it

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.

Categories

Resources