Related
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
mseebass said:
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
Click to expand...
Click to collapse
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
bigcrav said:
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
Click to expand...
Click to collapse
Thanks for your help. I allready tried an other usb port. It did'nt work.
I wanted to avoid it but I reinstalled windows. Now it works. Thanks again.
Hmm, messed with this problem for ages yesterday, mtp installed fine in normal mode but refused when in 'usb debugging' mode
simple fix, find your wpdmtp.inf file in windows/inf
edit it like shown, look for the [Generic.NTx86] and [Generic.NTamd64] entries near the top of the file........
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
...then update the driver in device manager, use automatic search
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
I did a clean install of windows and that solved the issue for me. Thanksfor your help anyway.
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
meangreenie said:
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
Click to expand...
Click to collapse
Just FYI, just got a Nexus 4 from T-Mobile yesterday and the device ID is slightly different:
VID_18D1&PID_4EE2&MI_01
01 at the end instead of 00
---------- Post added at 09:11 AM ---------- Previous post was at 08:53 AM ----------
Fitchman said:
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
Click to expand...
Click to collapse
How/where do you install those files/drivers? There are no instructions.
lannister80 said:
How/where do you install those files/drivers? There are no instructions.
Click to expand...
Click to collapse
When Windows asks where the drivers are you point to the folder with the ones you want to use...
EddyOS said:
When Windows asks where the drivers are you point to the folder with the ones you want to use...
Click to expand...
Click to collapse
It doesn't ask. I plug in the phone, and Windows says it can't install the MTP driver.
If I go into Device Manager and find the phone (with the yellow triangle and !) and select Update Driver Software, then navigate to the i386 folder from the Universal Naked Driver (on an i5 system), it tells me that "The best driver for your device is already installed" or something similar.
Of course, if I uninstall the device from device manager (and presumably the bad MTP driver as well), it disappears, so I have nothing to point to to install the drivers.
Earlier today I reinstalled the drivers for my N4 on my work PC (Vista Business) and I had to reboot before it recognised the N4 as an MTP Device - prior to that it only saw it as an 'MTP Device'. Now it sees at 'Nexus 4'
I have a similar problem I have a kindle fire
I have install the ADB driver but am having extreme difficulties getting the MTP drivers to work
I have tried everything (every solution on Google)
and nothing works
I've tried the "Media Transfer Protocol Porting Kit"
I tried to get Microsoft help they gave me the run around and confused me even more
here is the conversation
Microsoft: "Thank you for that information
Nathaniel I was checking your product key and it is blocked that is why you can not connect these devices to your computer, you may be a victim of counterfeit software so in this case since it is an OEM computer which means that the manufacture of the computer installed Windows 7 on your computer I recommend you to contact the manufacture of your computer to see if they have an option in order to resolve this issue you are having."
me: when i contact them what do I ask for?
Microsoft: You need to ask for a new product key
me: I am confused what does this mean? that the manufacturer put windows 7 OS on here illegally? but all PC's come with windows OS so every PC in the world is suspect to counterfeiting
them: No, this could be because someone still some information of your computer and use the product key to try to activate Windows until the product key got blocked
No, the name is not involved in this case it is jut the product key
what do I do?
is there an alternative to MTP drivers?
Solved
Hi, i had the same problem described in previous posts and I managed to solve thanks to what is written by meangreenie.
In practice, in the windows\inf of my Windows 7 the file wpdmtp.inf was no longer present but there is only the "compiled" version (wpdmtp.pnf).
I retrieved the file from an earlier version founded in he folder Winsys and so the LG driver are installed without further problems.
Jon McDougal said...
You might be using the wrong driver (Android ADB) instead of the MTP driver. This happened to me the other day!
If you're in Debug Mode, you've already done the first step I was going to suggest.
Here's the second step that worked for me: Open Device Manager -> Click Android Device (top of my list) which exposes "Android Composite ADB Interface" -> Right click that device -> Update Driver Software -> Browse My computer for driver software -> Let me pick from a list of device drivers on my computer -> then choose "MTP USB Device" -> Next
Mine installed the MTP driver and then the N4 opened normally.
Click to expand...
Click to collapse
That works for me with USB Debug ticked and in MTP Mode but not in PTP Mode (on CM10.2-nightly-20130817). I absolutely can't see my pics in no way... (I suppose this is a bug from Google to be fixed in further updates). ADB and FB are correctly working as tested with NexusRootToolkit 1.7.1 Drivers Test.
May it help to delete original DCIM folder and start from a new one??
edit: Shame on me... I forgot that I've formatted my SDcard, so I've no picture in DCIM folder.... Sorry! So I can say that McDougal trick totally worked for me!
try to check the device manager to check the missing drivers with ! mark
Maybe I'm not completely getting the problem, but just doing this worked fine for me:
danielms22 said:
Enable USB debbuging in your phone. Go to Settings -> about phone -> tap about 10 times on build number item until USB debbuging is unlocked.
Also, on your computer go to the device manager, look for your phone, if you find it, right click on it, then update Driver Software, browse computer, Let me pick from a list of device drivers on my computer, USB composite device
That should do it.
Click to expand...
Click to collapse
No need for additional driver download or anything...
Finally a working solution
Finally I found a solution.
Visit answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/mtp-usb-device-drivers-will-not-install-correctly/0ee71b7c-4ae7-403f-abbb-63c7ed9a79f9?rtAction=1387606800207 and search for the "Bret B"'s answer which has also been marked as the most helpful answer. It works perfectly. He simply says..
Go to the Registry Editor (Start –> Run –>type in, “regedit” (without the quotes) then click OK.
Search the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
Go upto Edit>Find, type in or copy/paste Portable Devices
In the right hand pane you will see the (Default) value “Portable Devices” on the string
Once found, you see a string value called UpperFilters –> delete it!
Reconnect the device. Finished!
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
akashi said:
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
heat361 said:
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
Click to expand...
Click to collapse
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
Click to expand...
Click to collapse
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
heat361 said:
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
Click to expand...
Click to collapse
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
Try pointing the path to the Google drivers in the android-sdk in device manager and not the naked drivers.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
This is what I did and waited for the PC to install the adb drivers.
I plugged the phone in and with the USB plugged in turned it off while holding the volume up and down keys. This made my nexus 4 go into download mode and the PC automatically installed the adb drivers. After I just unplugged and held the power button to restart the device hope this helped.
Sent from my Nexus 4 using xda premium
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
Thanks.
Click to expand...
Click to collapse
When you uninstalled what's there now, you did make sure to check the box that will remove the old drivers from your PC?
Just in case, HERE is another source for the drivers.
dinhume echoes
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
akashi said:
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
Click to expand...
Click to collapse
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
El Daddy said:
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks. I tried version 16.01 and still have this problem.
The problem is whenever I uninstall/install the ADB driver or disconnect/reconnect the USB, **ONLY** the "Nexus 4" appears on the Device Manager which I manually install the ADB drivers to. There is not a second "Nexus 4" on the Device Manager for the MTP or PTP.
On my laptop when I remove all drivers and reconnect the USB cable, I always see 2 "Nexus 4" listed on Device Manager. One for the ADB interface and the other for the MTP or PTP.
Please help!
Any ideas please?
Any Solution to ADB connection problems?
Hi was there any solution to this, as I seem to have the same issue.
I have tried different drivers and MTP & PPP modes as well as loading the PDAnet drivers and software.
Each time now I take care to remove all the drivers and also delete the drivers in all modes (Android running and Bootloader running)!
MTP & PPP load different copies of the drivers.
I can get either "Nexus 4" showing up in the device driver or "Google ADB Interface" or Android ADB interface" according to the driver loaded.
I can see the device when Android is running ie "ABD Devices" gives me the serial number and connected, then I can send an ADB command "adb Reboot-bootloader" the Nexus then reboots into the bootloader screen, the device driver changes to the bootloader driver (installs if not installed) however then I loose connection to the Nexus phone! "ADB Devices" returns none connected.:fingers-crossed:
I also tried unplugging and plugging back in the phone in bootloader mode but do not get adb to see the handset or it to react to commands.
I'm just about ready to try a toolkit to see if I can get past this roadblock!!!
Current computer is Win7-x64
This weekend I will try on a different computer.....Win8-X64
All comments appreciated
That's because you cant use adb when in boot loader. You use fastboot
Sent from my Nexus 4 using xda app-developers app
I have same problem on my work laptop DELL when my custom desktop machine works just fine with both Nexus 4 and 7. :/
Kind of frustrating, I can't seem to get my computer to recognize the Nexus 7. I'm running Windows 7 64bit. I do have the Android SDK installed with 4.3 updated to the latest already. Can't imagine what could be triggering this... hmmm
Use the SDK manager to download the Google USB drivers. Head to device manager on your windows, update the driver for the nexus 7 which has an exclamation mark, and select the android SDK folder to install the drivers.
Hope it works for you.. That solved it for me.
Sent from my Nexus 7 using xda app-developers app
You can get latest drivers here:
Description/Download
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
will this drivers works under win8 (64)?
They should.
meine12 said:
will this drivers works under win8 (64)?
Click to expand...
Click to collapse
It works PnP on my Win8-64
Sent from my Nexus 7 using xda premium
sWirL said:
Use the SDK manager to download the Google USB drivers. Head to device manager on your windows, update the driver for the nexus 7 which has an exclamation mark, and select the android SDK folder to install the drivers.
Hope it works for you.. That solved it for me.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sfhub said:
You can get latest drivers here:
Description/Download
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Hmmm unfortunately still nothing. When I browse either the usb_driver folder or my SDK folder (with the Google USB drivers), I still get a "Windows was unable to install your Nexus 7, Windows could not find driver software for your device." message.
So I've been scratching my head over this one. I tried USB debugging mode, reinstalling the drivers, etc. Basically with USB debugging and the SDK drivers, I can finally get something installed, I see the Android Composite ADB Interface, but MTP is still eluding me. So PTP works fine now, but MTP is so damn annoying...
Once I disable USB debugging, I'm back to square one, its no longer MTP that has the ! sign in device manager, but instead, Nexus 7 again. Searching the SDK folder yields nothing and not even PTP works once USB debugging is gone.
PharaohsVizier said:
So I've been scratching my head over this one. I tried USB debugging mode, reinstalling the drivers, etc. Basically with USB debugging and the SDK drivers, I can finally get something installed, I see the Android Composite ADB Interface, but MTP is still eluding me. So PTP works fine now, but MTP is so damn annoying...
Once I disable USB debugging, I'm back to square one, its no longer MTP that has the ! sign in device manager, but instead, Nexus 7 again. Searching the SDK folder yields nothing and not even PTP works once USB debugging is gone.
Click to expand...
Click to collapse
I created the attached MTP driver inf to see if it would address your issue.
If it works let me know which OS version you are running. I think you mentioned windows 7 64-bit, but sometimes people switch machines in the efforts of trying to get things working.
You can install by telling the driver install not to search and to look for the driver in the path you downloaded and EXTRACTED this zip file.
The other way to install is to right click on the ? question mark entry in devmgmt.msc and go to the tab with the update driver option.
sfhub said:
I created the attached MTP driver inf to see if it would address your issue.
If it works let me know which OS version you are running. I think you mentioned windows 7 64-bit, but sometimes people switch machines in the efforts of trying to get things working.
You can install by telling the driver install not to search and to look for the driver in the path you downloaded and EXTRACTED this zip file.
The other way to install is to right click on the ? question mark entry in devmgmt.msc and go to the tab with the update driver option.
Click to expand...
Click to collapse
Thank you! That worked fantastic, still running Windows 7 64-bit. Can I ask what you did to get this working?
EDIT: This works fine for USB Debugging Mode, but when I turn that off, the Nexus 7 will try and install this MTP driver and get a "this device cannot start" error (on Windows). Although I'm more than happy with this solution, just info for anyone browsing this thread later on.
PharaohsVizier said:
Thank you! That worked fantastic, still running Windows 7 64-bit. Can I ask what you did to get this working?
EDIT: This works fine for USB Debugging Mode, but when I turn that off, the Nexus 7 will try and install this MTP driver and get a "this device cannot start" error (on Windows). Although I'm more than happy with this solution, just info for anyone browsing this thread later on.
Click to expand...
Click to collapse
If you want, you can try the version in this thread:
http://forum.xda-developers.com/showthread.php?t=2391236
This driver inf only affects MTP under USB debugging and will defer to windows for MTP when USB debugging is turned off.
You'll need to go to devmgmt.msc and Portable Devices, find Nexus 7, right-click, find the option to uninstall drivers, choose that, righ-click on Nexus 7, remove device, reboot.
Then specify the new path for the driver install (the one from that thread is mtp_driver, instead of mtp_driver_all in this thread)
Also you may want to post your experiences on that thread so people can find it in the future.
Yep I can confirm this one works as well. Awesome!
PharaohsVizier said:
Yep I can confirm this one works as well. Awesome!
Click to expand...
Click to collapse
Do you still have the issue where it says device could not be started when you turn off usb debugging?
Not sure if I'm having the same problem or just similar.
With usb debugging mode enabled, the tablet appears as Nexus 7 with no drivers found.
Without usb debugging mode, the Nexus 7 doesn't appear at all, not even under "other devices" or as a .USB composite device.
First tried installing Google USB Driver Rev. 8 from the SDK manager, with no luck.
Trying to manually install the extracted WPDMTPNX.INF driver with "Include subfolders" checked gives "Windows was unable to install your Nexus 7" as a result.
ROM: ParanoidAndroid 3.93
Kernel version 3.4.0-g365a6e0
msilby said:
Trying to manually install the extracted WPDMTPNX.INF driver with "Include subfolders" checked gives "Windows was unable to install your Nexus 7" as a result.
Click to expand...
Click to collapse
I sent you a PM.
msilby said:
With usb debugging mode enabled, the tablet appears as Nexus 7 with no drivers found.
...
ROM: ParanoidAndroid 3.93
Kernel version 3.4.0-g365a6e0
Click to expand...
Click to collapse
I attached a modified driver inf for your setup in the referenced post. See if that works for you.
mtp_driver_usbdebug_paranoid.zip
http://forum.xda-developers.com/showthread.php?p=44253804#post44253804
I believe your USB IDs are different from stock because of the ROM you are running.
I don't think it will fix your problem of not seeing the device properly with usb debugging disabled (I think that is possibly a rom issue), but it should theoretically get your device visible with usb debugging enabled.
Right-click on Nexus 7 in start menu->run->devmgmt.msc and choose the tab that allows you to update drivers and specify a folder where you unzip'd the zip file.
sfhub said:
Do you still have the issue where it says device could not be started when you turn off usb debugging?
Click to expand...
Click to collapse
Nope, it works fantastic!
Hello guys!
I have already read some topics on this forum but it is my first message.
As indicated in the title, I cannot connect my Nexus 4 on my computer using MTP. This computer is running Windows 8.1 Update 1. So far I have tried every method I have seen on the web so I am a little bit desperate.
I have tried to plug my device on other computers and it was automatically detected on Windows 7, Windows 8.1 Update 1 and Ubuntu 14.04.
On my computer, as it does not auto-configure MTP I have tried to install ADB drivers, hoping it would help me. Universal ADB drivers, Naked Drivers and drivers from the SDK didn't changed anything. I also tried changing USB port.
It always recognised my phone as a "Nexus 4" in the "Other devices" section of the Device Manager (I do not have "Android Device" section), except in when MTP + debugging are activated. Then I have both "Nexus 4" and "MTP", in "Other devices" section.
It does not work in PTP mode either and I also tried uninstalling/reinstalling the Nexus Root Toolkit, even if I do not see how it can help...
One last point: I have the "connected as multimedia device" notification on my Nexus 4 when MTP is activated, even if it's not recognised by Windows.
Do you have any idea of what I can do?
Have you tried Nexus 4-specific drivers? Try following this guide.
Marvlesz said:
Have you tried Nexus 4-specific drivers? Try following this guide.
Click to expand...
Click to collapse
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes
Bartimoot said:
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes
Click to expand...
Click to collapse
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Here is another post from another forum that has something you could try:
still1 said:
ttwiitch said:
still1 said:
1. make sure Settings ->Storage -> Menu[3 dots on top right] -> USB Computer Connection is MTP
2. USB debugging is disabled (if you ever enabled it)
3. make sure the drivers installed is MTP drivers rather than adb device(you do this when you unlock/root nexus)
point 3 is important. thats the reason why its not getting detected
Click to expand...
Click to collapse
2. Where in setting do I check for USB debugging?
3. How do I check this? (I'm not rooted)
Click to expand...
Click to collapse
2. developer option.. if you have not enabled developer option then you wouldnt have enabled USB debugging. so skip this
3. Connect your nexus to PC-->Go to Control panel-->device manager
you will see something like Android adb in device manager
Right Click and click "Update device Software"
Click "Browse your Computer for driver Software"
Click "Let me Pick from a list of device drivers on my Computer"
Click Next, for the device list shown.
Click to expand...
Click to collapse
Tell us how it goes..
Thank you for spending some of your time to help me Marvlesz, I really appreciate.
Marvlesz said:
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Click to expand...
Click to collapse
Yes, I saw it worked for a lot of people, for what I have read, but it seems that I am not that lucky
When picking from the list, I tried from the Android Device section and it displays "Unable to find any drivers for this device". Same Results in “Mobile devices”.
When I try “Show all devices”, I have a lot of possibilities. I just tried “MTP Device” from both “Standard MTP-Compliant Device” and “Standard MTP-Compliant devices” sections, and it displayed “The install class is not present or is invalid”
Am I cursed?
I was wondering, is it possible that the problem is coming from my hardware? Or its drivers? (Those for the motherboard maybe?)
EDIT: I just found this thread : http://forum.xda-developers.com/showthread.php?t=2493734
I will try it and I will keep you updated when it is done.
EDIT 2:
So I tried the solution... and it worked! :good:
I had the N version of Windows 8.1, mainly to avoid useless software like Windows Media Player, and it was the exact problem.
Sorry for taking a little of your time, and thank you again!
No problems, I'm glad you had it fixed.
Anyone else with problems seeing the storage after plugging into PC? adb command works and device drivers installed. Found another forum where turning the usb from MTP to charging and back under developer options does the trick. I have a non stock ROM and seeing if fresh out of the box experiences the same thing.
I have the same issue and can't seem to figure out how to get it to work. My work around has been to use ES File Explorer and open Remote Manager.
Edit: I just plugged it in again to see what I can find. I turned off USB Debugging and Developer Options. Plugged in and pulled the notification bar down, there is an option to change USB Settings to Charging, Power Supply, File Transfers (this works), Photo Transfer and MIDI. Give it a go!
rramey23 said:
I have the same issue and can't seem to figure out how to get it to work. My work around has been to use ES File Explorer and open Remote Manager.
Edit: I just plugged it in again to see what I can find. I turned off USB Debugging and Developer Options. Plugged in and pulled the notification bar down, there is an option to change USB Settings to Charging, Power Supply, File Transfers (this works), Photo Transfer and MIDI. Give it a go!
Click to expand...
Click to collapse
I am running to the exact same problem.
I have tried with USB Debugging off AND on, still no go. I think there's a problem with installing the drivers. Whenever I check the device manager, it still says the drivers weren't installed. I have tried installing the Google drivers. What do we do?!
Kandydish said:
I am running to the exact same problem.
I have tried with USB Debugging off AND on, still no go. I think there's a problem with installing the drivers. Whenever I check the device manager, it still says the drivers weren't installed. I have tried installing the Google drivers. What do we do?!
Click to expand...
Click to collapse
Need to get the drivers to install first and foremost. Even with USB Debugging on, I'm still able to pull down and change from charge only. Those drivers are key. I had to restart my computer before it was able to take the install.
rramey23 said:
Need to get the drivers to install first and foremost. Even with USB Debugging on, I'm still able to pull down and change from charge only. Those drivers are key. I had to restart my computer before it was able to take the install.
Click to expand...
Click to collapse
I'm able to get to the pulldown and change the setting from charging to MTP. Every time I do that, I get a window showing that I'm installing the drivers for Nexus 6P. Then it completes. I can do this over and over again. In the device manager, there's a little exclamation mark by the Nexus 6P and says these drivers weren't installed Code 28. I have exhausted Google to no avail!
Anyone find a solution to this?
Kandydish said:
I'm able to get to the pulldown and change the setting from charging to MTP. Every time I do that, I get a window showing that I'm installing the drivers for Nexus 6P. Then it completes. I can do this over and over again. In the device manager, there's a little exclamation mark by the Nexus 6P and says these drivers weren't installed Code 28. I have exhausted Google to no avail!
Anyone find a solution to this?
Click to expand...
Click to collapse
You chose to install the drivers manually instead of having the system do it for you? Right click the yellow exclamation .. update drivers .. allow me to pick .. choose the download file location see what that gives you.
zosimov21 said:
You chose to install the drivers manually instead of having the system do it for you? Right click the yellow exclamation .. update drivers .. allow me to pick .. choose the download file location see what that gives you.
Click to expand...
Click to collapse
When I choose the location, I see a bunch of options. The most relevant ones are ADB Interface and Android Device. Under Android Device there are several more options such as Android Adapter Interface, Android Bootloader Interface, and the such; no mention of MTP.
Kandydish said:
When I choose the location, I see a bunch of options. The most relevant ones are ADB Interface and Android Device. Under Android Device there are several more options such as Android Adapter Interface, Android Bootloader Interface, and the such; no mention of MTP.
Click to expand...
Click to collapse
Did you already download the google USB drivers?
Should just be able to choose the android_winusb.inf driver. It should allow MTP
zosimov21 said:
Did you already download the google USB drivers?
Should just be able to choose the android_winusb.inf driver. It should allow MTP
Click to expand...
Click to collapse
I have downloaded them. How do I specifically choose just that file? When I go through updating the driver, it asks for a folder location.
Go to dev options, switch the USB from ptp back to mtp and it works for me
xxsashixx said:
Go to dev options, switch the USB from ptp back to mtp and it works for me
Click to expand...
Click to collapse
Tried. Keeps trying to install the MTP drivers and it won't go through.
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
bartendersimon said:
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
Click to expand...
Click to collapse
I don't have any other drivers from any other devices. This is a clean install of Windows 8.1. I've only tried connecting my 6P, my OG 6, and my 9. All have the exact same problem.
Kandydish said:
I don't have any other drivers from any other devices. This is a clean install of Windows 8.1. I've only tried connecting my 6P, my OG 6, and my 9. All have the exact same problem.
Click to expand...
Click to collapse
You might wanna try installing Huawei Drivers and see if that help
HiSuiteSetup_2.3.55.1.zip
http://download-c.huawei.com/downlo...loadId=16205&version=90864&siteCode=worldwide
bartendersimon said:
You might wanna try installing Huawei Drivers and see if that help
HiSuiteSetup_2.3.55.1.zip
http://download-c.huawei.com/downlo...loadId=16205&version=90864&siteCode=worldwide
Click to expand...
Click to collapse
I installed that application and I was able to see my device, the apps, the contacts, everything. EXCEPT I wasn't able to access the device from Windows Explorer which means I am not able to transfer files.
Kandydish said:
I installed that application and I was able to see my device, the apps, the contacts, everything. EXCEPT I wasn't able to access the device from Windows Explorer which means I am not able to transfer files.
Click to expand...
Click to collapse
So when you change the option in the phone from charging to file transfer, did you check the device manager to see if there any unknown device showing somewhere?
bartendersimon said:
So when you change the option in the phone from charging to file transfer, did you check the device manager to see if there any unknown device showing somewhere?
Click to expand...
Click to collapse
Changing it from charging to MTP shows a MTP device in Manager with a yellow exclamation mark next to it. When looking into the details, it says that no drivers are installed. When I try "Updating Drivers", it says "Windows failed to install drivers. Code 28" or something along those lines. Code 28 MEANS that Windows failed to install drivers.
Thanks for nothing Microsoft.
Nexus 6p Connection to PC Issue - This Helped!
I had similar problems with PC not recognising my Device. I found http://www.technobuzz.net/install-google-nexus-6p-usb-drivers/ which helped me solve my issues.
1. Downloaded and installed the Huawei Nexus 6p drivers. This installed a Huawei Task Manager which connection to pair was still not recognisable.
2. Deleted old drivers (acer, samsung, htc) from' Device Manager'. This actually helped PC recognise my device which showed up in the Device Manager>Other Devices>Nexus 6p, also in PC interface but once moved off charging to MTP, computer didnt recognise device.
3. Downloaded and installed the adb/fastboot installer. Followed instructions till step 10. My screen didn't show anything like Andoid ADB interface, it displayed MTP file install, which I installed. Just remember to refresh in My PC interface when changing over from charging to MTP, sometimes Nexus 6p will be hidden.
4. Uninstalled the Huawie Task Manager.
This has solved my problem with PC and Device connection. The instructions given are from what I can recall of the process I went through.
Credit to Sidharth Rathore from Technobuzz for this solution.
Hope this helps.
Later.
p.s. I have a windows 10 laptop if this helps.
bartendersimon said:
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
Click to expand...
Click to collapse
I was having the same issue until I uninstalled some other debugging drivers I had installed. So I would recommend crawling through your installed apps for any other android usb drivers and uninstalling them if you still have this issue.
Working on mine right now. Found that USB 3.0 ports will not recognize device. Once plugged into a 2.0, it is recognized. Might help your issue