Related
Please help if you can
My first 32gb Nexus 7 had no problems showing up as an mtp device on windows 7.
Am running a rooted 4.1.2 and all is well with mtp as well as adb, toolkits, etc.
I purchased one more as a gift, and that one can only be set to ptp in the internal storage settings.
If I try to set it to mtp, it takes, but does not show up in windows or in adb.
The only way to see it or use adb or a toolkit on it, is to set it to ptp which shows up as a camera with read only permissions.
Both tablets are using the same rom etc.
Have tried this on 2 PC's (win 7 as well as xp)
Any Ideas?
Thanks
On my (rooted) Stock 4.2.1 tablet, MTP mode only seems to show up if ADB Debugging is enabled.
Sort of odd; PTP will work whether or not ADB Debugging is turned on, but MTP only shows up when ADB debugging is also enabled.
If you have not enabled "Developer Options" on the tablet, go to
Settings->About tablet
and tap on the last entry ("Build number") 6 or 7 times in succession. This will allow the following menu item to appear under settings:
Settings-> {} Developer options
You can enable ADB debugging from there.
The PTP/MTP toggle control is at
Settings -> Storage -> Menu (top RH corner) -> USB Computer connection
good luck
MTP vs PTP
bftb0 said:
On my (rooted) Stock 4.2.1 tablet, MTP mode only seems to show up if ADB Debugging is enabled.
Sort of odd; PTP will work whether or not ADB Debugging is turned on, but MTP only shows up when ADB debugging is also enabled.
If you have not enabled "Developer Options" on the tablet, go to
Settings->About tablet
and tap on the last entry ("Build number") 6 or 7 times in succession. This will allow the following menu item to appear under settings:
Settings-> {} Developer options
You can enable ADB debugging from there.
The PTP/MTP toggle control is at
Settings -> Storage -> Menu (top RH corner) -> USB Computer connection
good luck
Click to expand...
Click to collapse
Thanks, but I guess I was not very clear.
ADB Debugging is turned on but only works in PTP mode.
MTP does not work at all, even though it's checked.
ganovim said:
Thanks, but I guess I was not very clear.
ADB Debugging is turned on but only works in PTP mode.
MTP does not work at all, even though it's checked.
Click to expand...
Click to collapse
Even after reading this and your 1st post, I am still a little uncertain.
I *think* you are saying that you want to get MTP working on the second unit. And I *think* you are also saying that (additionally) ADB only seems to work when you have PTP mode selected.
Reading between the lines - are you testing things with the same computer for both tablets? (Or, another way to put that, if the answer to this previous question is no, do you see any "Unknown Device" messages in the Device Manager when you toggle things around?)
I fooled around with mine not more than 30 minutes ago. Leaving it plugged into the PC the entire time (Win 7 Pro x64), I could toggle USB Debugging on/off and back and forth between PTP/MTP. Although I didn't actually try a live ADB session in both MTP/PTP modes, the file browser thing would pop up for PTP mode no matter what I had ADB debugging set to, and for MTP mode that would only happen if I had ADB debugging enabled. At no time did I see any unrecognized devices in the Device Manager.
And I think that what I just said above doesn't help you.... arghh.
MTP vs PTP
bftb0 said:
Even after reading this and your 1st post, I am still a little uncertain.
I *think* you are saying that you want to get MTP working on the second unit. And I *think* you are also saying that (additionally) ADB only seems to work when you have PTP mode selected.
Reading between the lines - are you testing things with the same computer for both tablets? (Or, another way to put that, if the answer to this previous question is no, do you see any "Unknown Device" messages in the Device Manager when you toggle things around?)
And I think that what I just said above doesn't help you.... arghh.
Click to expand...
Click to collapse
First of all thanks for the interest.
Bottom line is as follows.
MTP mode does not work period.
However....
when I boot into recovery, (TWRP) the pc sees the usb connection, and I can use adb commands.
So it leads me to conclude that there is something off in the System files. But (and it's driving me nuts)
they are a clone of the first (MTP functioning) Nexus 7.
Thanks again
@OP
You can uninstall the drivers(all of the n7 drivers), then unplug, then replug it in, then let it install its drivers again. This solved the mtp issues other users had.
I'm running Windows 7 64bit and followed the Ultimate guide to unlock and root my Nexus 4.
Everything went well but now it looks like that Windows won't recognize my phone as a device. When I plug in the phone, the auto-play window will pop out and recognize it as Nexus 4, but there is no other options. (Normally the auto-play will ask if open folder to view files or transfer photos). I can't see my phone in device manager either.
If I turn on the USB debugging mode, I can see it in device manager but still cannot see it in My Computer. Looks like Windows can't access the SD card at all.
I tried switching to the camera mode but the problem remained. Please help.
desperate bump. can anyone help?
Maybe it's a stupid advice, but have you tried change the USB port in PC?
glancer2315 said:
desperate bump. can anyone help?
Click to expand...
Click to collapse
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.
Colourkey said:
Maybe it's a stupid advice, but have you tried change the USB port in PC?
Click to expand...
Click to collapse
yes, i did.
abaaaabbbb63 said:
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.
Click to expand...
Click to collapse
thanks for your advice. the problem is that, without USB debugging mode on, I can't see Nexus 4 in Device manager, even though the Windows Auto-play will say Nexus 4 connected. (Nothing in My Computer either)
With USB debugging mode on, I uninstalled the driver and Windows would try installing the driver. Now it shows up as MTP device with an exclamation mark. I tried manually update the driver (direct it to the Google SDK folder and pick the android_windowsusb.inf) but it says it does not support x64. I don't think the 64 bit driver is digitally signed.
I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.
SovereigN7 said:
I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.
Click to expand...
Click to collapse
i did and it remains the same.
Is there anyway I can know all the files names of the drivers so that I can manually delete them from system folder? When I uninstalled it from the device manager, I don't see the option "Delete the driver software for this device".
I can still see it under "adb devices" list.
I think there are some conflicts in the drivers.
Now when I connect Nexus 4 (without USB debugging mode on), it will show up in device manager under Android Device.
With USB debugging, it will then show up under Portable Devices.
However, it's supposed to work the other way around. that is (no USB debugging --> portable device; with USB debugging --> Android Device).
How can i solve this?
Have you tried manually installing the drivers before plugging in the phone, vs letting windows choose the drivers it wants to install? One option you could try is installing PDA Net on your pc. It will install reliable drivers on your pc.
i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB
Alex240188 said:
i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB
Click to expand...
Click to collapse
thank you for your long and detailed reply.
this is what i wanted to do, but the problem is that when I uninstall them, I don't get to see the option "delete the driver software for this device". What should I? cuz every time I plug in Windosws just tries to automatically install the driver for me.
Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.
glancer2315 said:
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.
Click to expand...
Click to collapse
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status
Alex240188 said:
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status
Click to expand...
Click to collapse
hi, adb devices works. (will list my device when usb debugging is on)
with usb debugging off, under portable device, the device status says "This device cannot start. (Code 10)". thanks.
still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?
glancer2315 said:
still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?
Click to expand...
Click to collapse
I have this same issue I'm trying to find a fix, that's how I found your thread. Alex gave very good info make sure you go back to his posts and hit his "Thanks" button, I did it on everyone one of his posts in this thread. I'm starting to think it's a hardware issue and not a software issue, I've never had this issue on any device. When I got it new running stock 4.2.2 MTP didn't work. ADB works and PTP works, just not MTP no matter what I try. I recommend you learn to use, ADB push and pull to move your files if you don't already know how to use it (To use ADB I need to check PTP for it to work and not MTP) you might need to do the same. I will keep you posted if I find a fix.
Sent from my Nexus 10 Pimpin AOKP 4Life
I'm just getting more and more confused with this.
If Adb works then you must have an Adb driver installed for the phone. However your also stating that you get no box for uninstall driver.
With USB debugging disabled you said that it appears as an android phone rather than a portable device. This should not be.
With debugging disabled what happens if you Try to uninstall in device manager
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
My theory still stands that you have updated the mtp driver with adb drivers. Hence why mtp doesn't work but ptp does.
The problem is getting to a position where you can uninstall the adb drivers from the mtp device and let it reinstall the proper drivers
Sent from my Nexus 4 using xda app-developers app
I plugged another Nexus 4 in, and all the drivers loaded perfectly. I then tried my Nexus 4 phone, and nothing happens. No mtp, no adb, no boot loader drivers. Its my phone. My next step is to find a zip file that I can flash via custom recovery, which will bring all the binaries and ROM back to stock. Anybody know where I can find this? I'll probably lose the custom recovery, but hopefully it will be fixed and I can flash the custom recovery again.
LG-E960
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
Thanks for this. It worked like a charm:good:
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
YOU ARE AWESOME. THANKS :good::good:
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
i was looking for the solution, i'll try this tonight for my n7. will it work the same way for N4 too?
adbanginwar said:
i was looking for the solution, i'll try this tonight for my n7. will it work the same way for N4 too?
Click to expand...
Click to collapse
You got a free thanks!
It should be the same exact solution for any Nexus.
annoyingduck said:
You got a free thanks!
It should be the same exact solution for any Nexus.
Click to expand...
Click to collapse
i'm very annoyed with windows 8... argh broke most of the things...
adbanginwar said:
i'm very annoyed with windows 8... argh broke most of the things...
Click to expand...
Click to collapse
Try (i know !) to not get frustrated...
The mapping is a bit different, you'll get it with some patience, and then you'll have a good lesson in windows 8!
annoyingduck said:
Try (i know !) to not get frustrated...
The mapping is a bit different, you'll get it with some patience, and then you'll have a good lesson in windows 8!
Click to expand...
Click to collapse
Your way did not work for me. by defaul ADB drivers will installed when plugged in and not ADB composite. i followed the method 4 provided by wugfresh nrt. it worked for me, i rooted n4 and then unlocked+rooted n7_2013.
EDIT: oh, and mine works on ADB composite, weird!!
A request to OP. @annoyingduck
Could you please bring the first post in-order? The information is so cluttered that its agonizing to read.
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
You're so full of ****. Giving creedence to this crap through ignorance. Shame on you.
I have carefully followed the instructions in [GUIDE] Unlock/Root/Flash for Nexus 6P.
However, when I type "adb devices" at the command prompt, I just get "List of devices atttached" without a serial number. When I try "fastboot devices" when in bootloader, the cursor comes back without any message. What should I try next. Thanks in advance.
PrevailNow said:
I have carefully followed the instructions in [GUIDE] Unlock/Root/Flash for Nexus 6P.
However, when I type "adb devices" at the command prompt, I just get "List of devices atttached" without a serial number. When I try "fastboot devices" when in bootloader, the cursor comes back without any message. What should I try next. Thanks in advance.
Click to expand...
Click to collapse
Did you add the current version of platform-tools to your environment variables path? Did you also install the Google USB drivers from the sdk? Also on the phone you have USB debugging enabled and then when you plug it into pc it will ask for authorization on your phone.
Yes, I am running adb and fastboot from within the platform-tools folder. USB debugging is enabled as well as OEM unlocking in developer options. I switch from USB charging to file transfer (MTP) when plugging in. The USB drivers seem to be working fine, since I have no trouble transferring files, etc. Just don't know what else to try to get adb working.
I can't find the video that helped me but this is what I remember.
Go to device manager, locate the phone, tick the drivers tab, update drivers, browse, let me pick, have disk, and locate your drivers (I uswd the straight up Google drivers). At some point you have to choose from 3 ADB choices, it's the top one, Android ADB Interface. Good Luck, it worked for me.
BTW- for me fastboot found my phone but not ADB.
PrevailNow said:
Yes, I am running adb and fastboot from within the platform-tools folder. USB debugging is enabled as well as OEM unlocking in developer options. I switch from USB charging to file transfer (MTP) when plugging in. The USB drivers seem to be working fine, since I have no trouble transferring files, etc. Just don't know what else to try to get adb working.
Click to expand...
Click to collapse
Did your phone ask to authorize your PC when you plugged it in?
Gizmoe said:
Did your phone ask to authorize your PC when you plugged it in?
Click to expand...
Click to collapse
I get two notifications when plugging in the 6P. One says, "USB debugging connected". The other says, "USB for charging. Touch for more options".
PrevailNow said:
I get two notifications when plugging in the 6P. One says, "USB debugging connected". The other says, "USB for charging. Touch for more options".
Click to expand...
Click to collapse
OK. Unplug your phone. Go to dev options. Turn off USB debugging. Also revoke USB debugging authorizations. Then re-enable USB debugging and plug phone in. It should now ask if you want to allow USB debugging for your PC on your phone screen. Check to always allow device.
Gizmoe said:
OK. Unplug your phone. Go to dev options. Turn off USB debugging. Also revoke USB debugging authorizations. Then re-enable USB debugging and plug phone in. It should now ask if you want to allow USB debugging for your PC on your phone screen. Check to always allow device.
Click to expand...
Click to collapse
What he said, this is key to get ADB working.
Gizmoe said:
OK. Unplug your phone. Go to dev options. Turn off USB debugging. Also revoke USB debugging authorizations. Then re-enable USB debugging and plug phone in. It should now ask if you want to allow USB debugging for your PC on your phone screen. Check to always allow device.
Click to expand...
Click to collapse
I did as you suggest, but I continue to get the same two notifications, just as before.
The first says "USB debugging enabled. Touch to disable USB debugging.", without any request to authorize my specific PC.
PrevailNow said:
I did as you suggest, but I continue to get the same two notifications, just as before.
The first says "USB debugging enabled. Touch to disable USB debugging.", without any request to authorize my specific PC.
Click to expand...
Click to collapse
It's a driver or port issue then on your PC. Are you trying in a USB 2.0 or 3.0 port? I got mine in a 3.0. In device manager it should say under Android devices tree " Android Composite ADB Interface". Try switching ports or if you see it listed wrong in device manager manually update the drivers.
---------- Post added at 06:21 PM ---------- Previous post was at 06:16 PM ----------
It is important though that you get the toast notification about allowing USB debugging and it will show you an rsa fingerprint.
You said you had a second notification that said "USB for charging". Have you tapped that notification and changed it to file transfer?
jiggyb21 said:
You said you had a second notification that said "USB for charging". Have you tapped that notification and changed it to file transfer?
Click to expand...
Click to collapse
Adb works in charging mode. They are not even getting the authorization toast to allow USB debugging on PC.
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
@PrevailNow If you have any other phone software installed try disabling or uninstalling it. Other phone manufacturers tools can cause problems with adb as well.
Gizmoe said:
@PrevailNow If you have any other phone software installed try disabling or uninstalling it. Other phone manufacturers tools can cause problems with adb as well.
Click to expand...
Click to collapse
I think you are right about this. I appear to be making some progress. After removing a previous installation of Sammy Kies, I got the PC authorization request for debugging, and the adb interface driver shows up now, as expected, in the device manager.
I am also able to get "adb" to return my serial number; but "fastboot" doesn't detect any attached devices. I have deleted and reinstalled all 4 SDK packages, but "fastboot" still doesn't detect my 6P. I just don't know what else to try, so any ideas would be appreciated. I thank those who have already responded with helpful information.
You're using old platform tools, I guarantee it...
Sent from my Nexus 6P using Tapatalk
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
4K2K said:
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
Click to expand...
Click to collapse
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Alternative solution is to use KDE Connect app over Wifi. Bonus is that once set up, it is possible to push files from the phone to the PC without any interaction on the PC side - e.g. useful if the PC doubles as a file server.
losteagle said:
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Click to expand...
Click to collapse
Both of my home & works computer (Win10 14959) failed to detect it as MTP or PTP drive. Might have been due to those having previous phone's drivers.
But I faced same problem with fresh out of the box Win8 laptop.
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
ksj0823 said:
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
Click to expand...
Click to collapse
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Citroon said:
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Click to expand...
Click to collapse
Wanted to add my voice here too that I did the same - I had to clean up previous drivers I had installed over time for varios phones and different ADB versions like the one from clockworkmod - once I cleaned that out and installed google drivers from SDK PTP worked and I was able to do Helium restores
I had issue on my Win10 PC, but I found that after I disabled USB debugging, it would work as MTP/PTP, but not for ADB of course. So apparently, I have to toggle USB debugging ON/OFF to switch back and forth from MTP and ADB.
Small pain in the butt.
Solution.
I had the same issue. Drove me NUTS for about an hour. In the end, simply unchecked the USB DEBUGING in developer settings. This will make it pop up immediately.
Update:
I clearly should have read the post above mine first.