Related
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
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.
I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.
Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app
It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.
I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.
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.
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
Can someone explain why connection of the P2XL to Windows 10 via USB is so troublesome?
At a minimum, each time I connect I have to:
1. Update the device driver via Windows Device Manager from "MTP Device" to "MTP USB Device" (there are two of these)
2. Tap on the P2XL notification "USB for Charging" to change it to "USB for File Transfer"
I have set "Select USB Configuration" in Developer Options to MTP, but this doesn't help.
How can I configure my phone to connect for MTP each time I connect it via USB?
Thanks
JWadle said:
Can someone explain why connection of the P2XL to Windows 10 via USB is so troublesome?
At a minimum, each time I connect I have to:
1. Update the device driver via Windows Device Manager from "MTP Device" to "MTP USB Device" (there are two of these)
2. Tap on the P2XL notification "USB for Charging" to change it to "USB for File Transfer"
I have set "Select USB Configuration" in Developer Options to MTP, but this doesn't help.
How can I configure my phone to connect for MTP each time I connect it via USB?
Thanks
Click to expand...
Click to collapse
Are you using the USB adapter that came with the device, or a standard 2.0 USB A-C cable?
Using the white USB cables that came with the P2XL.
Try just using the charging cable connected to the PC, it's all I use to connect to my Win 10 PC, and the only thing I have to do is make sure the device is set to MTP, I never have to mess with drivers on the PC.
Are your drivers up to date? Are you saving any changes on the PC after making them? Not sure why you're getting the MTP Usb / MTP Device option unless it's related to using the dongle (which I never have)...
It's not Win10 dude, I connect a few times a week for Andromeda purposes, plug and go.
three west said:
It's not Win10 dude, I connect a few times a week for Andromeda purposes, plug and go.
Click to expand...
Click to collapse
In my case it WAS Win 10. None of my phones would connect for MTP. I frequently use ADB and windows was trying to use those drivers by default. After messing around in device manager I finally was able to select the windows MTP drivers. After that all my phones were able to connect with windows via MTP.
Sent from my Pixel 2 XL using Tapatalk
Wtherrell how did you do that? my phone won't even show up on device manager
I I R C I had to delete all the old ones and start fresh. Some of the old ones were not obvious but somewhere on line or in the forums I found some clues about what to look for and delete. I wish I could remember exactly where but I can't at the moment.