Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
ADB detects my phone just fine, but I can't get Windows (8.1) to recognize my N5 via either MTP or PTP mode. It shows up in Device Manager as just "MTP" with the yellow exclamation point. Not really sure what to do from here. I do have the Google USB driver installed for ADB, not the universal ADB drivers.
Any thoughts?
I have a new, unrooted, bootloader-locked F8332 Xperia XZ to which I am trying to connect via adb from my Windows 7 computer so that I can attempt an 'adb restore' of the applications and data from my current device. I already have the Android SDK installed and downloaded the XZ adb and fastboot drivers from the Sony developer site. However, I have not been able to install the drivers. When I connect the XZ (with USB Debugging enabled) and look in the Windows Device Manager, I get "Xperia XZ" listed under Portable Devices and nothing related to adb shows up. If I try to update the drivers and point Windows to the downloaded drivers for the XZ, it tells me that no drivers were found. With the XZ connected, I can run 'adb devices' and what I get is a blank list. I can connect the XZ set up for fastboot and it will show up in Device Manager as an Unknown Device. Attempting to install the drivers there also fails with a similar "no driver found" error.
My current device is a rooted Xperia TX. In order to get that device to show up with 'adb devices' I have to set its USB Storage Mode setting to Mass Storage, otherwise it will not work. The XZ, however, does not let me change the storage mode from MTP because whatever I choose (e.g. PTP) gets reverted to MTP immediately. So the questions is how do I get the XZ to be seen by adb or in a configuration that will allow me to install the relevant drivers? I am probably missing something simple because the threads in the forum relating to adb stop at "install the adb drivers" with no additional details. Any help would be appreciated.
Did some more playing around and figured out how to get the ADB interface to show up in Windows. As with my Xperia TX, the issue is related to the USB Configuration setting under Developer Options. For anyone who might run into this situation, it seems that USB Configuration has to be set to MIDI for ADB to work.
I had tried changing that setting to PTP, but it would not stick, it would always change back to Charging Only. Thinking that perhaps PTP would not stick because I did not have an SD card on the phone at the time, I put in an SD card and tried again, but the result was the same. Thinking that it would not actually work since what I was attempting had nothing to do with music, I set USB Configuration to MIDI and to my surprise the setting stuck. I plugged the phone into my computer and the Windows Device Manager showed a new "ADB Interface" entry with an exclamation mark. Right-clicking on ADB Interface and selecting Update Driver allowed me to choose the driver I downloaded from the Sony Developer Site. Windows accepted the drivers (with a prompt about the drivers being unsigned) and the Device Manager entry changed to "Sony sa0115 ADB Interface Driver." The XZ gave me a prompt about allowing the computer to have debug access, which I accepted. At this point I could go to a command prompt, run "adb devices" and the XZ showed up in the list, as expected.
The "adb restore" that I was attempting was (mostly) successful in transferring my applications and their data to the XZ. I still don't know why the PTP setting will not stick, or if that is normal.
Felix1701D said:
Did some more playing around and figured out how to get the ADB interface to show up in Windows. As with my Xperia TX, the issue is related to the USB Configuration setting under Developer Options. For anyone who might run into this situation, it seems that USB Configuration has to be set to MIDI for ADB to work.
I had tried changing that setting to PTP, but it would not stick, it would always change back to Charging Only. Thinking that perhaps PTP would not stick because I did not have an SD card on the phone at the time, I put in an SD card and tried again, but the result was the same. Thinking that it would not actually work since what I was attempting had nothing to do with music, I set USB Configuration to MIDI and to my surprise the setting stuck. I plugged the phone into my computer and the Windows Device Manager showed a new "ADB Interface" entry with an exclamation mark. Right-clicking on ADB Interface and selecting Update Driver allowed me to choose the driver I downloaded from the Sony Developer Site. Windows accepted the drivers (with a prompt about the drivers being unsigned) and the Device Manager entry changed to "Sony sa0115 ADB Interface Driver." The XZ gave me a prompt about allowing the computer to have debug access, which I accepted. At this point I could go to a command prompt, run "adb devices" and the XZ showed up in the list, as expected.
The "adb restore" that I was attempting was (mostly) successful in transferring my applications and their data to the XZ. I still don't know why the PTP setting will not stick, or if that is normal.
Click to expand...
Click to collapse
i tried what your mentioned and succeed,but i really want my 'mobile device' （a blue screen phone）show in my ‘file manager’。is there any method？
by the way,are all these mtp problem due to unlock bl?
Confirmed on my Xperia ZX F8331. I have to select MIDI interface to access to the ADB interface.
Btw, I'm rooted and the bootloader is unlocked.
Thanks for your report!
Connected as MTP. Debugging enabled
It shows up on device manager as MTP USB Device (update driver says the best driver is already installed)
It shows up on adb devices
It doesn't show up if I try to assign a letter.
Help!
Just got a pixel 3a, it's running android 9. I want to unlock the bootloader. I'm following one of the popular root guides on this forum. I can't seem to get adb or fastboot to find my device.
Installed ADB applications from https://developer.android.com/studio/releases/platform-tools.html
Turned on developer options in phone, turned on USB debugging, plugged in phone.
Wasn't prompted for device authorization from phone.
Changed USB connection mode to PTP.
I have tried all USB connection modes, I verified the cable used to connect the pc to the pone is a data cable as I can transfer data when the phone usb mode is set to file transfer, ptp, or midiInstalled adb/phone device driver using https://developer.android.com/studio/run/win-usb
Still no debugging authorization prompt, but device manager lists the phone under 'Android Device' as 'Android Composite ADB Interface'.
'adb devices' doesn't list anything, tried 'adb kill-server', 'adb start-server', and 'adb usb'
'adb devices' doesn't list anything
reboot phone into fastboot by shutting down and holding power+volDown
'fastboot devices' doesn't list anything
Rebooted my pc, rebooted the phone, retried everything.
I'm at a loss, any suggestions?
Yea I've had some issues with adb/fastboot on windows as well. Sometimes it just won't detect the device, rebooting into my Linux install finds it instantly though. I haven't looked into how to fix it yet though as I can always just reboot to Linux. If you're on a version of windows that supports WSL, perhaps you should try that?
Sent from my Google Pixel 3a XL using XDA Labs