Is there a trick to make MTP work under Windows 10? I used it once (via the swipe down, hitting the USB Mode and changing to MTP) before enabeling develper mode.
Now in Developer mode I changed it under Network --> USB Configuration --> MTP but my tablet does not show up on my PC. Do I need to change anything else? Already tried switching between the USB configurations, rebooting the device and so on, but nothing seems to work...
May be wrong but:-
W10 out of the box doesn't support MTP. You may need to install the Android Debug Bridge USB driver on your Windows machine and then connect that driver to your Android device. With the tablet disconnected open W10 Device manager, now connect the tablet to the USB port. Device Manager screen should immediately refresh and show 2 lines at the top of the screen:
Android Device
Android Composite ADB Interface.
Assuming your cable is ok then the absence of these two lines indicates you need the driver installed. The driver is installed as part of Google's Android Studio in the Platform Tools sub directory. If you just want the drivers then they are available to download (no links ) There are automated methods , see http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 or Nexus Root Toolkit does it. ( You should have usb debugging enabled in the tablets Developer menu)
Once the drivers are installed then when you enable MTP via the Notification or your menu "path" then Device manager will show the tablet under the "Portable Devices" line.
I originally got my laptop to work with the Pixel C using Window 8.1. I had trouble at first finding a driver that would work. I tried various drivers, but I eventually got it to work with PDANet. I believe that the trick for me was to first use PTP to get the correct drivers installed. You should be able to switch from PTP to MTP once PTP is working correctly.
I have subsequently upgraded from Windows 8.1 to Windows 10. I had a similar issue again with the drivers. I first used PTP to get the proper driver installed and then switched to MTP.
I always use the pull down menu on the Pixel C to change from charging to PTP once working and then to MTP.
With PTP, you should be able to see the Pixel C drive on the computer but only able to access the photos. Once you switch to MTP, you should see all the folders.
For fastboot, you need to use PTP and not MTP.
Found this post via Google, it's an issue for me with the Pixel phone, too. Photo mode works normally, MTP doesn't.
For others who also find this post, I read that supposedly the Pixel phones install ADB drivers automagically, but this isn't happening for me, and @SmokinCharger's fixes haven't worked either.
Related
Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Thanks!
Did you try if it would recognize your device in fastboot bootloader?
Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium
highwaybandit said:
Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for the suggestion, highwaybandit. I tried your idea, but still have the same issue with ADB not recognizing the device, despite the device showing up successfully in Windows device manager.
I have the same problem with Ubuntu. I tried "adb reboot bootloader" and nothing. Unlocked fine with fastboot tho.
Sent from my Nexus 7 using Tapatalk 2
Username invalid said:
Did you try if it would recognize your device in fastboot bootloader?
Click to expand...
Click to collapse
Yes, and it does. I was able to 'fastboot oem unlock'. However, can't issue any adb commands.
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
Now that you mentioned it, same issue here, in addition to the ADB issue mentioned above. My N7 doesn't show up as a drive whether I have USB debugging enabled or not.
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
mickrg123, I forgot to mention: I've been getting around this issue by using Google Drive. Not as fast as moving files directly, but still a decent workaround until we get this figured out.
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
ddb540 said:
Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Click to expand...
Click to collapse
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)
Also when I check box to load camera it will show as drive
sfhub said:
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)
Click to expand...
Click to collapse
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?
mickrg123 said:
Also when I check box to load camera it will show as drive
Click to expand...
Click to collapse
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB debugging, than both MTP and PTP should work.
sfhub said:
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB mass storage, than both MTP and PTP should work.
Click to expand...
Click to collapse
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?
mickrg123 said:
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?
Click to expand...
Click to collapse
Sorry, I meant disable USB Debugging, not mass storage (I'll correct the post)
I'm sure you know where, but if not, Settings->Developer options->USB debugging
If MTP still doesn't work, then see if you have ever gotten MTP to work on the PC (ie another device in MTP mode). If not, look up how to install/reinstall MTP support for your OS version. Windows added it as part of user driver framework and one of the new versions of media player.
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
mickrg123 said:
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?
Click to expand...
Click to collapse
If your goal is just to load files onto the sdcard, have you tried "adb push"?
You don't need to have the phone visible as a device/folder on the computer to use adb to place files on the tablet.
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
1. Plug in nexus 7, MTP mode
2. Open the device manager
3. Right click the nexus 7 > uninstall drivers > unplug
4. Install drivers > http://developer.android.com/sdk/win-usb.html
5. Plug nexus 7 in, drivers will install, should say adb interface
Open up command prompt > nav to your adb folder > adb devices: device number should pop up. Good to go.
droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.
sfhub said:
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.
Click to expand...
Click to collapse
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!
droider137 said:
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!
Click to expand...
Click to collapse
No problem guy; glad you're up an flashing.
I just got my Nexus 7(2013) device.
I used to transfer files between my computer and my Nexus 4.
When I plugged in my N4, my computer recognizes my N4 and device manager showed there is a portable devices "Nexus 4"
However when I plugged in my new N7, my computer cannot detect it and device manager showed "Android Device" with "Android Composite ADB Interface" under it.
I cannot find any new drive in My Computer although the device is charging through USB.
I have tried to disable/enable USB Debugging, using different USB cables, switching USB option between MTP and PTP and reinstalling Nexus usb driver from google and all of them do not work.
May I ask for any solution?
Thanks:fingers-crossed::fingers-crossed:
Uninstall/remove the drivers
reboot
then reinstall using these drivers
http://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Even if you did it before, try again, with the removal of drivers and the reboot.
Also you may want to try different ports, cables, computers
sfhub said:
Uninstall/remove the drivers
reboot
then reinstall using these drivers
http://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Even if you did it before, try again, with the removal of drivers and the reboot.
Also you may want to try different ports, cables, computers
Click to expand...
Click to collapse
I've tried that before
I may now try a few times more
By the way, I realized that I can use Wugfresh toolkit and completed the full driver test to bootloader mode. However, I cant even detect the hard drive.
I finally enabled to use PTP to access the photos.
However I am still unable to use MTP to transfer other types of files..
Any help?:fingers-crossed::fingers-crossed:
EggShaarawy said:
I finally enabled to use PTP to access the photos.
However I am still unable to use MTP to transfer other types of files..
Any help?:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Please perform the following even if you have done it before.
In this current state, turn on MTP. Then turn off USB debugging. See if MTP shows up. If so, use this fix to get MTP working with USB debugging.
[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)
sfhub said:
Please perform the following even if you have done it before.
In this current state, turn on MTP. Then turn off USB debugging. See if MTP shows up. If so, use this fix to get MTP working with USB debugging.
[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)
Click to expand...
Click to collapse
I am sorry that I cannot understand it completely.
May I ask
1. Should I uninstall just the entry with Nexus 7 as description in Nirsoft USBDeview and then reboot?
2. You mentioned that "When you turn on USB debugging and windows asks for an MTP driver, just provide mtp_driver.zip". How can I use the zip file? After rebooting and enabling USB debugging, my toolbar on bottom-right has a icon showing I have a MTP and I can choose to "remove MTP safely" just like plugging in a USB flash drive. However, there is not a hard drive in My Computer. Maybe is it the difference between Windows XP and WIndows 7? Or did I misunderstand your instruction?
Thanks for helping! :good:
I finally did it with USB debugging and MTP on.
I occasionally update the Android ADB Interface driver and install Composite USB Device from the list and my computer detects my hard drive!!
Is it possible to get my MTP working without enabling USB Debugging or is it normal to detect mtp with USB Debugging on? :good:
EggShaarawy said:
I finally did it with USB debugging and MTP on.
Click to expand...
Click to collapse
One of the drivers you installed previously which was modified to get MTP working. was implemented too aggressively and is now blocking your ability to use MTP with USB debugging turned off.
For normal systems with no drivers loaded, they have the opposite problem, in that they can get MTP working when USB debugging is disabled, but lose MTP when USB debugging is enabled.
When USB debugging is disabled and MTP is enabled, the USB port advertises that it is compatible with standard MTP drivers, so windows automatically installs. However if you have a custom driver installed, it can block that automatic process.
With USB debugging turned on, the USB port no longer advertises MTP compatibility, so windows is normally confused and doesn't know what driver to use. That you were able to get it working with USB debugging enabled proves to me that you have a custom driver installed that was modified to get MTP working.
The way I wrote my changes to the MTP driver was to leave the standard MTP alone and only intercept the MTP when USB debugging is enabled. Thus my changes don't block normal MTP operation when USB debugging is disabled.
EggShaarawy said:
Is it possible to get my MTP working without enabling USB Debugging or is it normal to detect mtp with USB Debugging on? :good:
Click to expand...
Click to collapse
Yes, but you are going to need to figure out which driver you installed is causing the issue and remove it so it doesn't get in the way.
Alternatively, try a different PC that has never had drivers installed and use just the one I pointed you at earlier.
You don't use the zip file directly, you unzip the contents and will have a .inf file.
When windows asks for a driver (USB debugging turned on and MTP turned on) you point the install at the .inf provided. It will do the rest automatically.
sfhub said:
One of the drivers you installed previously which was modified to get MTP working. was implemented too aggressively and is now blocking your ability to use MTP with USB debugging turned off.
For normal systems with no drivers loaded, they have the opposite problem, in that they can get MTP working when USB debugging is disabled, but lose MTP when USB debugging is enabled.
When USB debugging is disabled and MTP is enabled, the USB port advertises that it is compatible with standard MTP drivers, so windows automatically installs. However if you have a custom driver installed, it can block that automatic process.
With USB debugging turned on, the USB port no longer advertises MTP compatibility, so windows is normally confused and doesn't know what driver to use. That you were able to get it working with USB debugging enabled proves to me that you have a custom driver installed that was modified to get MTP working.
The way I wrote my changes to the MTP driver was to leave the standard MTP alone and only intercept the MTP when USB debugging is enabled. Thus my changes don't block normal MTP operation when USB debugging is disabled.
Yes, but you are going to need to figure out which driver you installed is causing the issue and remove it so it doesn't get in the way.
Alternatively, try a different PC that has never had drivers installed and use just the one I pointed you at earlier.
You don't use the zip file directly, you unzip the contents and will have a .inf file.
When windows asks for a driver (USB debugging turned on and MTP turned on) you point the install at the .inf provided. It will do the rest automatically.
Click to expand...
Click to collapse
I have been using the same computer to root Galaxy Nexus and Nexus 4 and I remembered I have been using some tool similar to the one you provided.
Maybe it makes my computer cannot recognize the MTP
Anyway, Thanks
Finally caught the driver bug! W10 x64. Take one PC that would concurrently connect N10(Omnirom 6), N9 (rooted) and stock N5 and connect a Pixel C. Connects as a Pixel C in Device Manager under "Portable Devices" - enable USB debugging and W10 says "The last USB device you connected to this computer malfunctioned and Windows doesn't recognise it". Could write a book on the steps taken. Tried to add "Android Composite ADB Interface" via install legacy hardware and pointing to Googles USB drivers (v11) I get a no x64 compatible files error. Even cleaned out W10 driver store of relevant drivers via the command prompt ( and then discovered RAPR windows front end to pnputils.exe at https://driverstoreexplorer.codeplex.com/). Nexu5 with USB debugging + MTP connects perfectly haven't tried N9 or N10.
Any bright ideas?
Don't think this has any relevance with MTP working - Using Anker USB-C to USB3 cable with rounded edges on connectors - AFAIK this version has the correct resistor
download a copy of USBDeview for x64
open it, sort the list on vendorid
uninstall every driver with vendorid of 18d1
close the program, unplug all USB devices, reboot
make sure you have the newest google drivers on the pc
plug in pixel c and let drivers install, unplug pixel c and reboot
it should now work correctly
this routine has helped me every time i had issues with the pixel c and pc recognition
most of the steps came from wugfresh's nexus root toolkit advice on how to get proper drivers
i think what happens is drivers from other devices combine to create a situation windows can not fix so need to start over.
each device plugged in will get the install routine.
My oneplus 3 isn't found in com/ports on windowsill 10. It's unable to load recovery and won't boot to system. Fastbook still works and has a unlocked boot loader. Trying to install stock firmware to restore the device for se again. Any help would be greatly appreciated.
Try loading drivers, have no issues here. Also run cmd prompt by right clicking on cmd.exe and selecting "Run As Administrator"
Sent from my SM-N930T using Tapatalk
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Also make sure USB debugging is enabled in the developers settings and you have the correct USB mode enabled (not charging)
Sent from my SM-N930T using Tapatalk
jaydubya24 said:
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Click to expand...
Click to collapse
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Will_Xda said:
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Click to expand...
Click to collapse
here is the device manager
setup driver and try in twrp
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
jaydubya24 said:
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
Click to expand...
Click to collapse
One more thing. Connect the phone to a USB 2.0 port and not a 3.0 port. It may not be recognised in a 3.0 port.
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what I found on USBDeview. There are two other versions of the OP3 on this list. But they do not show as being connected while the phone is in Fastboot. Im unable to access the OS to enable anything that may help with it being seen on my computer.
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Win7 works and i dont tryed the nice tip on site2.
i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
update on the op3
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what shows up after the one plus boot logo appears.
I had similar problem. I was rooting my 1+3. I went to device control settings in WIN 10 and removed 1+3 drivers. Next time when i was in fastboot mode windows installed drivers. :highfive:
I used the ones that came with 1+3
jaydubya24 said:
This is what shows up after the one plus boot logo appears.
Click to expand...
Click to collapse
I think this thread will supply the solution. "your" problem is at this post https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/page-4#post-15169580
I'm trying to connect my Nexus 5X to a PC running windows 10, version 1903. The PC previously had android SDK installed and I was able to access a Nexus 5 using adb.
When I connect the phone to the PC, the device is detected and the PC says it's ready. However, the PC never asks what to do when the device is connected, the device doesn't show up in the file explorer window and in the device manager, it shows up as an "other device" with a yellow warning. If I open the properties, the status is the following:
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
Click to expand...
Click to collapse
The phone thinks it's connected. Initially it says "charging" and I can enable "transfer files". It makes no difference on the PC.
In the settings on the phone, "select USB configuration" is set to MTP. Developer options are enabled. If I enable USB debugging, the phone switches to the MTP driver, but there is no difference on the PC.
I tried connecting the phone to another PC and it worked fine with USB debugging enabled and disabled, so the problem seems to be on the PC.
I removed android sdk and installed the latest version using android studio. I also installed the google USB drivers. This also made no difference.
Any suggestions?