Database Users

X64 and MTP not showing up?

My nexus 7 isnt showing up on my Windows 7 x64 machine... any help on what I can do?

numus said:
My nexus 7 isnt showing up on my Windows 7 x64 machine... any help on what I can do?
Click to expand...
Click to collapse
This is part "bump" and part assistance. You can at least get the Nexus 7 connected via ADB using these steps:
enable USB debugging
install the Android SDK (from Android's developer site)
from the SDK manager install the latest version of the USB driver too.
Make sure your Nexus 7 is hooked up.
Go into your device manager (Start > Control Panel > Device Manager)
navigate to the right Nexus device (not MTP in this case),
right click it,
click Update Device Drivers.
Choose your own driver manually.
When asked for a folder, navigate to C:\[your username]\AppData\Local\Android\android-sdk\extras\google\usb_driver
make sure searching in folders is checked
...that should at least get the ADB driver running. From there you can PUSH or PULL files or open the SHELL, but I don't know of a client-side file manager that makes those things easy yet. This is just one step of many, I bet...

2 things
Have you the latest win media player installed on PC? If not, update it.
Is n7 USB debugging on? If so, turn it off.
That should allow MTP to begin. If not, try the previous post
Sent from my Nexus 7 using xda app-developers app

If your using a N or KN version of Windows 7, you can't use MTP. N and KN versions of Windows have media foundation and other media-specific features stripped from it; and MTP itself does not work.
If you are on such an OS, then this media pack may help:
http://www.microsoft.com/en-us/download/details.aspx?id=16546

espionage724 said:
If your using a N or KN version of Windows 7, you can't use MTP. N and KN versions of Windows have media foundation and other media-specific features stripped from it; and MTP itself does not work.
If you are on such an OS, then this media pack may help:
http://www.microsoft.com/en-us/download/details.aspx?id=16546
Click to expand...
Click to collapse
Other MTP devices show up... I have my epic 4g touch hooked up right now and it shows MTP... just the google nexus 7 wont...
primetechv2 said:
This is part "bump" and part assistance. You can at least get the Nexus 7 connected via ADB using these steps:
enable USB debugging
install the Android SDK (from Android's developer site)
from the SDK manager install the latest version of the USB driver too.
Make sure your Nexus 7 is hooked up.
Go into your device manager (Start > Control Panel > Device Manager)
navigate to the right Nexus device (not MTP in this case),
right click it,
click Update Device Drivers.
Choose your own driver manually.
When asked for a folder, navigate to C:\[your username]\AppData\Local\Android\android-sdk\extras\google\usb_driver
make sure searching in folders is checked
...that should at least get the ADB driver running. From there you can PUSH or PULL files or open the SHELL, but I don't know of a client-side file manager that makes those things easy yet. This is just one step of many, I bet...
Click to expand...
Click to collapse
ADB works without a problem.. it is just hte MTP that wont show up

I have the same issue. If I select PTP, the camera shows. Once I switch back to MTP, it goes away and no disks are displayed. In Device Manager I see Android Phone, I installed Google drivers and adb works. I have a Google Nexus also and is OK.

You're not alone, Sir.
http://forum.xda-developers.com/showthread.php?t=1821536

Anyone who found a fix for this? Couldn't get it to work on W7, on Windows 8 still no MTP. I can use it for debugging with the ADB, but everything I tried failed. Now I'm using AirDroid, but this option is the way slower.

reemprive said:
Anyone who found a fix for this? Couldn't get it to work on W7, on Windows 8 still no MTP. I can use it for debugging with the ADB, but everything I tried failed. Now I'm using AirDroid, but this option is the way slower.
Click to expand...
Click to collapse
Either the PDAnet or official Asus drivers work for me.
Sent from my Nexus 7 using Tapatalk HD

on 4.4.2
Here's the official documentation from Google for enabling this protocol.
"Transfer files through USB" (Google this** and click the link by support.google.com)
Relevant Info:
On your device, make sure that the USB computer connection is set to “Media device (MTP).”
Go to Settings > Device > Storage. Then open Menu > USB computer connection.
MTP should be selected by default, but you may have to uncheck MTP, check and uncheck Camera (PTP), and then recheck MTP.
** Unfortunately I'm not able to post external links having fewer than 10 posts, so I'll update this when I'm able. If I forget, just ping me.

[Q] Nexus 7 USB connectivity to Windows XP SP3

Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???

try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app

o82239 said:
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE

ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Sent from my Nexus 7 using xda app-developers app

:-/
Is there any justice for me in this bad bad world of octa-core processors and Razer Edge!!! :'(

ansh360 said:
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
Click to expand...
Click to collapse
??? It worked and it doesn't work ???
What worked?
Try to delete the precompiled inf-file 'C:\WINDOWS\inf\wpdmtp.pnf', edit the 'C:\WINDOWS\inf\wpdmtp.inf' (see link in the post in the top...), open the XP device-manager, right-click in the yellow '!' and 'update driver'...
twics said:
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Click to expand...
Click to collapse
Do you have edit the 'C:\WINDOWS\inf\wpdmtp.inf'?
Sent from my Nexus 7 using xda app-developers app

I had a lot of problems myself getting Windows XP to work with my Nexus 7 as well... eventually I discovered that installing the latest version of Windows Media Player fixed the problem.
I wrote up a post on this issue on another forum (Sorry, XDA - this was before I discovered you guys), back in December of last year.
Anyway, here is my original post...
http://www.nexus7nexus10.com/forum/nexus-7-help/2600-cannot-connect-pc-2.html#post36608
(Actually, this whole thread is worth reading.)
The only nuisance factor is having to remember to re-enable USB debugging (Titanium Backup needs USB debugging enabled, and complains if itsn't) AFTER I've run some MTP Windows XP related file backups (USB debugging needs to be disabled, or MTP won't work)...
....or at least that is my experience.
Hope this is of some use.
Rgrds,
Ged.

Hello guys,
I have the same issue on windows XP with Nexus 7. I tried everything what was suggested and nothing is working.
I have Windows XP SP3 with WMP11 and MTP porting kit installed as well. the device is recognized and driver is instaled fine. But it's not visible on "my computer" in MTP mode. I tried to turn on usb debugging and still device is invisible in windows explorer, the same is when usb debugging is turoned off.
When device is in PTP mode it appears in "my computer" and i'm able to browse it and see all pictures and photos.
How can i browse my device in MTP mode and copy files there? Please reply if anybody knows what to do to fix this issue.
Thank you.

ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.

Taowtp said:
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Click to expand...
Click to collapse
The above workaround was spot on, thanks

Nexus 7 not showing up in Windows

Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?

C'mon... Somebody..:? Anybody?

Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium

do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.

androidkid311 said:
Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried that. Doesn't work. Nothing makes it register.
Billchen0014 said:
do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.
Click to expand...
Click to collapse
Tried this too. I've been using the new factory cable and it doesn't work. I've tried five different cables and different usb ports. Also tried factory resetting and different roms as well.

Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck

Wilks3y said:
Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck
Click to expand...
Click to collapse
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.

Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
{
"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"
}

Username invalid said:
Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
Click to expand...
Click to collapse
Is tha driver different from the drivers I downloaded from the SDK manager?

nicholi2789 said:
Is tha driver different from the drivers I downloaded from the SDK manager?
Click to expand...
Click to collapse
It is version 7.0.0.1.

nicholi2789 said:
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.
Click to expand...
Click to collapse
No worries mate best of luck !!
Let us know if not and I'll try find another way

I found this while searching. http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip . USB drivers for win 8 problems-
Sent from my Nexus 7 using Tapatalk 4 Beta

best and quick solution. Open "settings"
nicholi2789 said:
Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?
Click to expand...
Click to collapse
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC

iralamanoj said:
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC
Click to expand...
Click to collapse
Haha, thanks for the help, but I wish it were that simple. It was a first Gen Nexus7 by the way too.
I'm no novice to the ways of Android, and i tried everything under the sun to get it to work. Nothing Would make it show up on the computer.
Anyways, it just ended up turning off one day (with a fully charged battery too) and wouldn't turn back on. I ended up calling Asus and they repaired it for me. It had a burnt out USB port. They fixed it and it's up and running fine now.
Long story short, be careful what you buy on eBay one, and two, Asus has EXCELLENT customer support. From the day I called them to the time I got it back fully repaired only took 7 days exactly. And I didnt have to pay for shipping. If you ever have a problem with an Asus product don't hesitate to call them.

I just solved my problem. The Nexus 7 was not showing up in the device manager and windows explorer. Once usb plugged it would charge but do nothing.. In device manager I found "ACER Composite ADB Interface". I googled it and this is the problem. apparently Windows update install this thing but it doesn't work with the Nexus 7. You have to uninstall it (don't forget to check the delete from computer box or else it will reinstall itself). Then look for this : ASUS Android Composite ADB Interface Driver 8.0.0.1 for Windows 7 64-bit and download it.(sorry I can't post links)
Now with your Nexus 7 plugged in update your driver by selecting the browse my computer option and locate the file you just downloaded and there you go it should work. After months of searching it's finally working. :victory:

[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)

The MTP fix is ONLY for the STOCK ROM and handles the case
USB debugging disabled - MTP working
USB debugging enabled - MTP not recognized
If you cannot get MTP working at all, I suggest you
uninstall your current device drivers
using device manager/devmgmt.msc or Nirsoft USBDeview
you may want to
set devmgr_show_nonpresent_devices=1
prior to starting devmgmt.msc and
view hidden devices within devmgmt.msc
REBOOT
reinstall
The ADB fix is for getting ADB to work while in Recovery (tested on stock and twrp).
Google USB device drivers can be found here:
Driver info/download - http://developer.android.com/sdk/win-usb.html
Direct download - https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Nirsoft USBDeview can be found here:
http://www.nirsoft.net/utils/usb_devices_view.html
use this to remove old driver assignments, sort by date and choose Nexus 7 entries
====
MTP mode (with USB debugging enabled)
I got tired of having to disable USB debugging to get the MTP device recognized.
This happens because the USB ID for the MTP device changes when USB debugging is turned on and isn't recognized by windows anymore. The particular problem is the compatible IDs list from the tablet is not advertising USB\MS_COMP_MTP when USB debugging is enabled and windows doesn't know to use the MTP drivers.
I created the following driver .inf file to fix the problem so you can have usb debugging enabled and still have MTP working.
I only tested it on Windows XP.
This ONLY fixes the problem where MTP works with USB debugging DISABLED, but stops working when you have USB debugging ENABLED.
If you can't get MTP working under any circumstance, you have some other problem. Try
double checking
Settings->Storage->3 dots->USB computer connection->Media device (MTP) is enabled
removing your drivers using Nirsoft USBDeview and rebooting
When you turn on USB debugging and windows asks for an MTP driver, just provide the following and it should install the driver hooks and start recognizing the MTP device from that point on.
Let me know if there are any issues and I'll try to address.
mtp_driver.zip is for USB debugging enabled and stock ROM
INFO: this same method of fixing the unrecognized IDs might not work for custom ROMs. I have forced the MTP USB ID for a custom ROM to be recognized and it does so successfully, but when the windows MTP driver tries to initialized the device, it fails. This indicates there may be additional issues with the MTP support on the custom ROM side.
====
ADB support (within Recovery)
I wanted to get adb working in TWRP and adb sideload working in stock recovery but adb wasn't recognizing the device.
Here we have the same problem as above. The USB IDs for the ADB interface change when you are running Recovery and are no longer recognized by the driver. You'll notice that when you are running TWRP you will see an unknown device called "flo". This is actually the ADB USB interfaced but windows doesn't know that.
I created a simple fix for this problem. Just download the official Google USB/ADB drivers from above. Then download android_winusb.inf.zip from the attachment. Unzip the Google drivers and replace the android_winusb.inf file in the Google drivers with the one in the attachment.
android_winusb.inf.zip - unzip this file to get android_winusb.inf. Replace the file of the same name in the Google USB drivers with the one in this zip file
If you feel replacing a file is too complicated, the following attached file has all the changes done for you. Just unzip to get the adb_driver folder, right-click on the "flo" device, choose install drivers, and point the driver install to the adb_driver folder
adb_driver.zip - if you want everything already done for you, this file includes the driver inf and the driver so you don't need to replace anything. This will work for adb within both Android and Recovery.
platform_tools.zip - this is adb 1.0.31 that supports RSA identification introduced in Android 4.2.2
====

Wow or strange should be more of the reply. I have done this before but it never worked. Thanks for the help. For anyone else needing help here is what I did. First opened the Nexus Tool Kit, then Full Driver Installation Guide, launched USBDeview, then - In particular look for devices with Vendor ID - "18d1" or... "04e8" - Simply right click these devices, and select the option to: - "Uninstall Selected Devices", final step unplugged the device and plugged it back in and it worked. Also MTP enabled USB Debug unchecked. Thanks again...
-AkWingnut

sfhub said:
This fix is ONLY for the STOCK ROM and handles the case
USB debugging disabled - MTP working
USB debugging enabled - MTP not recognized
If you cannot get MTP working at all, I suggest you uninstall your current device drivers (using device manager/devmgmt.msc) and reinstall.
Google USB device drivers can be found here:
Driver info/download - http://developer.android.com/sdk/win-usb.html
Direct download - https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
====
I got tired of having to disable USB debugging to get the MTP device recognized.
This happens because the USB ID for the MTP device changes when USB debugging is turned on and isn't recognized by windows anymore. The particular problem is the compatible IDs list from the tablet is not advertising USB\MS_COMP_MTP when USB debugging is enabled and windows doesn't know to use the MTP drivers.
I created the following driver .inf file to fix the problem so you can have usb debugging enabled and still have MTP working.
I only tested it on Windows XP.
This ONLY fixes the problem where MTP works with USB debugging DISABLED, but stops working when you have USB debugging ENABLED.
If you can't get MTP working under any circumstance, you have some other problem.
When you turn on USB debugging and windows asks for an MTP driver, just provide the following and it should install the driver hooks and start recognizing the MTP device from that point on.
Let me know if there are any issues and I'll try to address.
mtp_driver.zip is for USB debugging enabled and stock ROM
EDIT: I removed the following file since it appears the issue with MTP on Paranoid is on the ROM side. The USB IDs were different and the driver inf I provided was able to get the windows side to recognize the MTP device and associate the MTP drivers, but when the MTP driver tried to initialize the MTP device, it wasn't responding properly.
mtp_driver_ubdebug_paranoid.zip (experimental) is for USB debugging enabled Paranoid ROM
If you need it just let me know.
Click to expand...
Click to collapse
There is a easier way if your running Windows 8 go into device manager while the nexus 7 is plugged in it show Google adb interface something like that so click on it and find hardware updates then from there hit manual update it give youa search option and another just pick manual it show the adb one or mtp select the one for mtp and you should be okay I will post pictures later on so it makes it easier to understand my instructions
Sent from my Nexus 7 using xda app-developers app

dakunclear said:
There is a easier way if your running Windows 8 go into device manager while the nexus 7 is plugged in it show Google adb interface something like that so click on it and find hardware updates then from there hit manual update it give youa search option and another just pick manual it show the adb one or mtp select the one for mtp and you should be okay I will post pictures later on so it makes it easier to understand my instructions
Click to expand...
Click to collapse
Not sure if this is particular to newer versions of windows or you have installed some previous drivers which allow MTP to show up when you do the manual driver install but for winxp even though it has the MTP driver on the system it won't give you the option to use it when you click on Android phone/devices, Portable devices, or Imaging devices categories under the manual driver install option. It just says no compatible drivers.
I'm a little suprised if your win8 install is showing MTP as a compatible driver, why it didn't just auto-install this from the beginning w/o user intervention?
The problem some folks are encountering (at least on older windows) is that since the tablet no longer advertises USB\MS_COMP_MTP in the compatible ID list, windows doesn't know what type of device this is, thus it doesn't provide you with any device drivers to use.

Added support for ADB within Recovery (tested on stock and TWRP)

Wow!
Welcome back! Hope we held down the fort well enough while you've been away!
Sent from my SPH-L900 using Tapatalk 2

Thanks, been a while. Haven't been around to look at the fort yet. Have new toy to play with.

sfhub said:
Thanks, been a while. Haven't been around to look at the fort yet. Have new toy to play with.
Click to expand...
Click to collapse
Welcome back! It's good to see you deving again!
Stop by the Pub some time. There are plenty there that would love to say "Hi!" to you.
Bugging up my phone, so you don't have to!
{
"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"
}
Need help? [email protected] on GTalk or by Email

TrayLunch said:
Welcome back! It's good to see you deving again!
Stop by the Pub some time. There are plenty there that would love to say "Hi!" to you.
Bugging up my phone, so you don't have to!
Need help? [email protected] on GTalk or by Email
Click to expand...
Click to collapse
Say hi, pass him a round, and thank him for his work
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2

Great to see your work again SFhub! You've been missed.
Sent from my GT-I9505G using Tapatalk 4

notianag hovels
My New nexus 7 was connected to PC(windows7), USB debugging enabled:
I can see files from the PC.
But adb can't reach Nexus..
D:\>adb version
Android Debug Bridge version 1.0.29
D:\>adb devices
List of devices attached
while I connect my Galaxy SIII to PC, adb works:
D:\>adb devices
List of devices attached
cc05905f device
Anyone have any clue what happen to the Nexus7?

molo88 said:
My New nexus 7 was connected to PC(windows7), USB debugging enabled:
I can see files from the PC.
But adb can't reach Nexus..
D:\>adb version
Android Debug Bridge version 1.0.29
D:\>adb devices
List of devices attached
while I connect my Galaxy SIII to PC, adb works:
D:\>adb devices
List of devices attached
cc05905f device
Anyone have any clue what happen to the Nexus7?
Click to expand...
Click to collapse
You need adb versions 1.0.31 or greater. Earlier versions do not support the RSA identification introduced in android 4.2.2
I added platform-tools.zip to the first post which contains the adb version you need so you don't need to do large downloads.

thanks
work flawless
thank you very much

Worked perfectly with CleanRom 1.6
Many Thanks !!

shortyboy said:
Disable debugging in developer options or gotto this thread
http://forum.xda-developers.com/showthread.php?t=2391236
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Myster said:
Worked perfectly with CleanRom 1.6
Many Thanks !!
Click to expand...
Click to collapse
Just wondering how u did that? http://forum.xda-developers.com/showthread.php?t=2447839

I honestly do not know ...
I use an Outlook sync application called Android Sync ( http://www.android-sync.com ) which comes with the option to install universal android drivers and device specific drivers so maybe a driver from that package in combination with this mtp fix worked

debbuging mode
Hi,
im new to xda and this was the most similar topic to my issue with MTP i could find, so sorry if i'm posting it in wrong one.
Im having the opposite problem. Its not like i cant live with that, since i can move my files freely as long as i enable usb debbuging. But still, its bothering me.
I can connect my Nexus 7 only with debbuging mode enabled. When i disable usb debbuging, win7 wont recognize my nexus as MTP device (PTP works). I can see Nexus 7 in device manager as "other device" but windows isnt able to install drivers correctly.
I tried to fix it by uninstalling the old nexus drivers (both manually and with usbdeview) but after a reboot im having the same issue.
When i try to update the drivers manually, it wont let me use the drivers distributed by google and asus support.
Anyone had the same issue?
Thanks and sorry for my English

Similar problem. Driver was installed and working. USB debugging on and only PTP modus gave me access in Windows. MTP never works. After reboot no connection possible at all. Only for adb in fastboot modus connection was possible. Deinstalling, reinstalling do not fix the problem. Reimaging Windows solves the problem till I reboot Windows...

Thank you so much for the information!
I was trying to sideload kitkat when my computer stop recognizing my nexus in recover! Your modified ini did the trick!

Hi! This doesn't work in windows 8.1 pro 64 bit. I get this:
I tried two different downloads with the same result so the hash mismatch is not because corrupt files. I'm clueless.
Correction: the modified ini doesn't work, nor the adb driver or the original driver.
FIXED: You have to boot windows with driver signature enforcement disabled. This is something that got implemented in windows 8. The issue is that the driver isn't signed and in windows 8 you can't install unsigned drivers unless you do this advanced bootup.

Samsung Windows drivers problem

Looking for some help please, with my new-to-me S5. I want to root it, mostly so that I can restore Titanium backup from my S4, but probably to install CM12 too. I have installed (and uninstalled, rebooted, installed, rebooted, many times) the latest Samsung drivers e.g. Samsung_USB_Driver_v1.5.51.exe, I have tried installing Kies3, I have tried different USB cables, I have tried my Win7x64 laptop, my wife's Winx64 PC; none of them will show the phone in Windows Explorer.
I did try it on a very old laptop (Core solo) that happens to have a play copy of Win8.1, and it worked! I then tried to use Odin v1.85 and Odin v3.09 to push CF-Auto-Root, and it always ended with Odin "Not responding" - presumably because the laptop doesn't have the guts.
I did put Win10 preview on a spare hard drive in my laptop, but no joy after installing Samsung_USB_Driver_v1.5.51.exe. Under Win7 I had tried older versions of the drivers too.
Ant bright ideas please??
TIA

fjuniper said:
Ant bright ideas please??
TIA
Click to expand...
Click to collapse
Kies will install the correct drivers so uninstall Kies completely, reboot your PC then install it again, check for updates and if any update kies then run it.
When it is running plug in your phone to a USB port that is directly on the PC not via any hubs and you must use the cable that came with the S5, other cables will not work correctly, make sure it installs the drivers at this set up.
Windows does not necessarily install the correct drivers, you need to go to My Computer > properties >. device manager and find your device in the list it should be shown as Android Mobile Phone if that is there then make sure the installed drivers are Samsung Android ADB Interface, if it isn't showing this driver them change it.
The other option if you have the Samsung drivers installed is to plug in the phone check in Device Manager on your PC and find your phone then check and change the drivers.
Turn off any firwall whilst you do this as that can block the device as well

Thanks for the suggestions. Yes, I had tried the original Samsung cable as well as others. Plugged straight into a ThinkPad, no USB hub.
Uninstalled Kies and the Samsung driver package, rebooted, installed Kies, checked for updates (none), and - Nothing. Nothing in Device Manager, nothing in the Safely Remove Hardware tray applet. Nothing in the notification area of the phone. The firewall was disabled for all of that post-reboot.
It's driving me mad...
I do eventually get a USB Device Not Recognised popup with Unknown Device shown in the window. By now, there is also an Unknown Device showing in Device Manager under Universal Serial Bus Controllers. I could Update Driver, but unsurprisingly Windows can't find one. My only other option would be to use the Have Disc option, but only if I had the right .inf file... :crying:

"None of them will show the phone in windows explorer"
You know you need to put the phone into download mode to use ODIN?
It won't show in explorer when you do that, but ODIN should say it is connected
And use the latest version of ODIN you can find, 3.09 should work, 3.10.6 is latest

*Detection* said:
"None of them will show the phone in windows explorer"
You know you need to put the phone into download mode to use ODIN?
It won't show in explorer when you do that, but ODIN should say it is connected
And use the latest version of ODIN you can find, 3.09 should work, 3.10.6 is latest
Click to expand...
Click to collapse
Thanks for replying. Yes, I have tried plugging in with it in download mode and using Odin, but it wasn't showing the COM port, so it wasn't recognised using that either. I even tried pushing CF Auto Root, but of course it failed.

It sounds like the cables you've tried are faulty, so long as the phone USB port is not
Multiple PCs say to me it's not a PC issue
The samsung drivers just need installing with the installer, don't worry about manually installing them, once you have working USB cables/port it will install them automatically so long as you ran the installer

Have you attempted to use different USB ports on the computer you are using? Contrary to what Detection has said, the fact that you can get it working on another computer with all of your cables does point to this being a PC problem and not a cable problem. My suggestion would be to completely uninstall Kies, keep it uninstalled, use different USB ports and allow windows to install the drivers itself.
On various occasions, removing Kies has worked, and on another it was the USB port that I was using that was the problem.

OP said he tried two different Win 7 PCs before trying the 8.1 laptop on which he had partial success
My guess is if he is constantly moving the cables from PC to PC, if they are faulty, bending them around is possibly making the connection by the time it ended up on the laptop it recognised the phone from, like when your charger cable breaks inside and you have to wiggle it around to make a connection
But as he also said, it failed to work even on that - so that's 3 machines, one partially recognised the phone - Id say the chances of it being a bad USB port over 3 machines, or even bad machines are very slim
Bad phone USB port or bad cables is my guess
Either that, or Win 7 isn't playing nice with the phone/drivers

I remember reading somewhere that with windows 7, you have to run odin as an administrator......also remember reading that it's not just the firewall you have to disable, but the anti virus as well......It may not help to uninstall kies as this *may* remove the Samsung drivers. Probably be better to leave it installed, but to use windows task manager to kill any running kies processes before you start odin up, as (from what I've read ) kies will interfere with odin.......
And for info.......odin 3.09 is the version I have successfully used on my phone.
Sent from my rooted kn0x0 stocKK SM-G900F S5

Thanks for all your replies while I was asleep.
I have used multiple USB ports on the 2 Win7 machines, multiple cables including the one that came with the phone. When I dropped the firewall, it was f/w and AV as it's one program (Symantec) (corporate laptop, not locked down). I have tried running Odin as administrator. If it wasn't for the fact that it did work on the ancient Win8.1 laptop, I would have thought the problem was with the phone port, but I could see it in Windows AND Odin displayed the COM port - it was just that Odin then went "Not responding"... which I assume was a system performance issue...
I will have another try tonight with yet more cables and I must have some USB ports I haven't tried yet... None of it makes sense and I am not a noob.
Edit: This is all having a negative effect on my laptop too - I used to be able to see internal and ext SD on my S4 in windows explorer - at the bottom of the right pane it had i9505 then you saw a folder for each SD. Now I just see ext SD as a drive letter.

Try this:
Install or just use the portable version of "Ghostbuster"
http://ghostbuster.codeplex.com/
Unplug all USB devices from the machine other than K&M
Run Ghostbuster as Admin
On the first device listed of each section, right click and choose "Add Class"
That should highlight the entries in that class and flag the ghost entries
Do that for every section until you have them all highlighted
Now click "Remove Ghosts" at the bottom and let it do it's thing
That will remove all non connected USB devices and their drivers
Once it's done - reinstall Samsung drivers just using the normal installer
Plug phone in and see if you get any better luck with it being detected
{
"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"
}

Thanks Detection, I hadn't come across that before. It deleted LOADS of ghosts... ...but unfortunately it hasn't moved me on at all. Still nothing in WinExplore, no COM ports in Odin. I am somehow jinxed, or rather this S5 is.
Edit: Just did it all again with a couple of reboots for luck - no better.

fjuniper said:
Edit: Just did it all again with a couple of reboots for luck - no better.
Click to expand...
Click to collapse
Open up the Device Manager on your PC then plug in your phone and look for any new connections to appear in the USB controllers list there may be Unknown device or another named device if you see a new connection unplug the phone and check the list again to see if it has disappear from the USB list, if you see a USB device appear and disappear from the list as you unplug and plug in the phone this is the one you want.
Right click on this and select Update Driver Software, click Browse My Computer then click Let me pick from a list, if you have the Samsung drivers installed on your PC you should see one or more called Samsung Mobile USB Composite Device, select the most up to date version if you have more than one listed and install that.
If you don't see the Samsung USB drivers un-tick the box that says Show compatible hardware, scroll down the list to the left and find Samsung Electronics Co Ltd, there will be more than one, click on each one until you see Samsung Mobile USB Composite Device in the right window, then click on that and install it.
You will get a warning saying that changing the driver may cause the device to not work properly just click OK and install the driver, if it works the USB device in the list should change to Samsung Mobile USB Composite Device.
Try this and see if it gets you sorted manually but don't forget to make sure you have installed the Samsung drivers on your PC first

ag4751 said:
Open up the Device Manager on your PC ...
Click to expand...
Click to collapse
Thanks, I will give that a go, though it will not be until Saturday as I don't have the phone with me. I am pretty sure that it does appear / disappear in Device Manager, and I did look at manually updating from there, so your suggestions should be helpful.

ag4751 said:
Open up the Device Manager on your PC then plug in your phone and look for any new connections to appear in the USB controllers list there may be Unknown device or another named device if you see a new connection unplug the phone and check the list again to see if it has disappear from the USB list, if you see a USB device appear and disappear from the list as you unplug and plug in the phone this is the one you want.
Right click on this and select Update Driver Software, click Browse My Computer then click Let me pick from a list, if you have the Samsung drivers installed on your PC you should see one or more called Samsung Mobile USB Composite Device, select the most up to date version if you have more than one listed and install that.
If you don't see the Samsung USB drivers un-tick the box that says Show compatible hardware, scroll down the list to the left and find Samsung Electronics Co Ltd, there will be more than one, click on each one until you see Samsung Mobile USB Composite Device in the right window, then click on that and install it.
You will get a warning saying that changing the driver may cause the device to not work properly just click OK and install the driver, if it works the USB device in the list should change to Samsung Mobile USB Composite Device.
Try this and see if it gets you sorted manually but don't forget to make sure you have installed the Samsung drivers on your PC first
Click to expand...
Click to collapse
When I manually select the Samsung Mobile USB Composite Device, I always get "Windows encountered a problem installing the driver software for your device. This device cannot start. (Code 10)", so I am still stuck...

fjuniper said:
When I manually select the Samsung Mobile USB Composite Device, I always get "Windows encountered a problem installing the driver software for your device. This device cannot start. (Code 10)", so I am still stuck...
Click to expand...
Click to collapse
There are a couple of things you can try as Windows is preventing the installation.
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
I had this error message last year with something I was trying to install but I can't remember just how I sorted it out.