[Q] MTP Connection - Nexus 7 (2013) Q&A

Ok so I'm extraordinarily frustrated with getting this to work. I've searched the forum to the point of a headache. Something about the .inf file and hardwar id's. I've uninstalled and reinstalled the drivers a million times. I've even reflashed the stock rom. Can anyone help? usb debugging works and PTP works. Currently back to stock and all drivers currently uninstalled.

mta1981 said:
Ok so I'm extraordinarily frustrated with getting this to work. I've searched the forum to the point of a headache. Something about the .inf file and hardwar id's. I've uninstalled and reinstalled the drivers a million times. I've even reflashed the stock rom. Can anyone help? usb debugging works and PTP works. Currently back to stock and all drivers currently uninstalled.
Click to expand...
Click to collapse
Check this: http://forum.xda-developers.com/showthread.php?t=2391236

Thanks man but I've tried following that post. It doesnt makae sense that none of these work arounds work for me

mta1981 said:
Thanks man but I've tried following that post. It doesnt makae sense that none of these work arounds work for me
Click to expand...
Click to collapse
Ok, I decided to use a laptop which has never had my N7 attached to it as MTP, only as adb for wugs (before I got comfortable with doing things manually), I had the same problem you did, this is what fixed it. I had used koushes adb driver installer on it, so his driver kept intercepting it.
First I got these drivers and unpacked them: http://developer.android.com/sdk/win-usb.html#
Then I plugged in my device, with PTP enabled and updated drivers and browsed to those drivers and let it install...this did not fix it.
Disable usb debugging, plug it in, enable MTP, then go into device manager, then go into the menu and show all devices, you should see something like Google ADB driver, right-click and uninstall it, selecting delete driver checkbox, then reboot your nexus 7 while still plugged in, it should redetect your N7 as a "Nexus 7" and you should see it in Computer as a Portable Media Player, then unplug the device, wait 3-4 seconds to make sure its unmounted, then plug it back in, you should now actually see files.
NOW, once I saw that that worked, I noticed PTP stopped working, leave it plugged in, switch to PTP. then you will see the ADB driver back, uninstall it again, reboot the device leaving it plugged in, it will redetect the device again, it will say MTP again even though it's in PTP, let it finish, then unplug the device, wait a few seconds, and plug it back in, now you should be able to see it connected as a camera, and should be able to see files, now I can switch PTP ro MTP and back again with debugging off resulting in it working fine.
NOTE: USB debugging only works right in PTP mode for me.. which is fine, I tested to make sure that once debugging was off, I can unplug the device, and plug it back in and I can still switch between MTP and PTP perfectly.
EDIT: Actually I am now going to try leaving debugging enabled, in MTP mode, uninstall the ADB driver and reboot the device and see if that fixes that problem too.
EDIT2: AND IT WORKED!
So now I can have debugging on and off, in MTP and PTP mode, adb devices works perfect for either mode.
In summary, i think the REAL trick here is to put the device in each mode combination one at a time, delete the device and driver from device manager and reboot the device while it's still plugged in, then unplug the device and plug it back in, you do this for every combo outlined below, a total of rebooting and unplugging/plugging in the device 3 times...because PTP+debug on or off worked already
MTP on - Debugging off - find entry in device manager, uninstall it, reboot device, leaving it plugged in, verify it shows in Computer, unplug device, wait 3-4 seconds plug device back in, verify you can see files.
PTP on - Debugging off - find entry in device manager, uninstall it, reboot device, leaving it plugged in, verify it shows in Computer, unplug device, wait 3-4 seconds plug device back in, verify you can see files.
MTP on - Debugging on - find entry in device manager, uninstall it, reboot device, leaving it plugged in, verify it shows in Computer, unplug device, wait 3-4 seconds plug device back in, verify you can see files.
..at the end you should be able to have MTP and PTP fully working with or without debugging on.

Try installing Sony PC Companion. It will install the necessary drivers. Works great with my Nexus 7 when connecting to PC in Windows XP .

I'm on WIndows 8.1 and when I connect my N7 2013 to PC, it gives me error Unknown USB Device (port reset failed). Anybody knows how I could fix this issue?

hussam91 said:
I'm on WIndows 8.1 and when I connect my N7 2013 to PC, it gives me error Unknown USB Device (port reset failed). Anybody knows how I could fix this issue?
Click to expand...
Click to collapse
Good luck with that.

mtp
ive had my n7 for couple months now and mtp never worked only ptp until about a week ago when in cleanrom thread here http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post 3877 asked 3888 answered. I checked in android devices and did not have the android composite adb interface. so I simply unistalled the drivers I had and plugged in device and bam. working great since. don't know if it was related but the day before I updated my sdk and there were some google drivers in the update list. hope this helps someone!
I don't mind airdroid as an alternative but soooo much nicer to plug in and drag and drop!! GL!!

Related

[Q] after installing android SDK and rooting Nexus File transfer stops working

I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Disable USB debugging.
Unplug/plug in your nexus.
The USB IDs change for some reason when you have USB debugging turned on and the MTP device isn't recognized as such. PTP (camera) mode continues to work for both cases though.
Thanks for the suggestion but It still fails. I disabled debugging and still can't connect. Switching USB modes didn't help either.
If that doesn't work uninstall the adb driver & then plug your tablet back in so it will reinstall
My next suggestion would to reboot the tablet with USB debugging turned off.
If that doesn't work, my next suggestion would be to delete the existing drivers and force reinstall.
All with USB debugging turned off.
johnnyninja said:
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Click to expand...
Click to collapse
Make sure after you plug in your device you're looking at your tab and click OK on the pop up........
Sent from my Nexus 7
Thanks for all the suggestions. It's working now. I was just about ready to delete the driver and the tablet started to be recognized consistently. I was in the settings screen and toggled debugging on and off while plugging in the tablet. I noticed the info bar at the top alternating between showing "debugging" and "media device" and I selected each one a couple of times when they came up. I think that it finally worked through the ID confusion that was mentions. I'll follow the the rest of the instructions if the problem comes back.
Thanks again.
It's acting up again so I'm going to try deleting the drivers. I thought I knew what to do but I can't find any information. What's the procedure to delete the driver? I'm running os x lion
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
johnnyninja said:
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
Click to expand...
Click to collapse
Rooted my nexus 7 (2012) last night and struggling with my laptop not recognizing it. This thread solved it!
Delete the ADB on my window, toggle off debugging and restart the nexus 7 with usb connected to laptop. works like a charm.
Thank you!
Guys, my N4 got this problem too.. until just a few minute ago
I read somewhere ini goge groups (i think N5 group), and found explanation that we can change ADB or MTP "mode" on device manager. On "Androoid ADB Device" right click and select "Update Driver Software". Click "Browse My Computer for Driver Software" and then "Let me pick from blablabla...." And then select MTP USB Device, "next" and my N4 detected on Windows Explorer.
Hope it will be usefull for you guys.

[Q] My computer not recognizing MTP AT ALL

Hey guys. I been here for like 4 hours just dabbling with everything. And cannot seem to find any solution to this...
I have uninstall all drivers and restarted like ten times now doing the same process over and over, cleaning up each file carefully of the nexus or any android device.
My problem is when i plug in my nexus 7 2nd gen, it seems to not even detect squat.
I have usb debug enabled
my MTP is on
( if i switch to PTP i can access the folder)
Ive done fresh start on everything i even look through device and try changing the option to MTP and STILL DOES not work
I don't even see my nexus 7 in my HDD external or anything, nothing pops up but an ADB success driver, and when i changed it to MTP a MTP success driver with STILL no luck....
I just bought it today and it worked fine earlier, now when i root it and stuff it seems to be glitchy with my MTP
I even factory reset everything i couldn't access my ADB
any help would be appreciated
Someone said that manually updating the adb usb driver in devices should show you a choice, choose mtp. It should then sort itself out properly.
n9900229 said:
Hey guys. I been here for like 4 hours just dabbling with everything. And cannot seem to find any solution to this...
I have uninstall all drivers and restarted like ten times now doing the same process over and over, cleaning up each file carefully of the nexus or any android device.
My problem is when i plug in my nexus 7 2nd gen, it seems to not even detect squat.
I have usb debug enabled
my MTP is on
( if i switch to PTP i can access the folder)
Ive done fresh start on everything i even look through device and try changing the option to MTP and STILL DOES not work
I don't even see my nexus 7 in my HDD external or anything, nothing pops up but an ADB success driver, and when i changed it to MTP a MTP success driver with STILL no luck....
I just bought it today and it worked fine earlier, now when i root it and stuff it seems to be glitchy with my MTP
I even factory reset everything i couldn't access my ADB
any help would be appreciated
Click to expand...
Click to collapse
On your Nexus, open "settings", click on "Storage", click on options(3 vertical dots on the top right corner), click on "USB PC Connection", now check MTP option.
Try connecting to your PC (or Mac) now. I didn't have to do that on a stock build, but for some reason I had to do it on a couple of custom roms. Hope it helps ya out...
Try enabling USB debugging. I know it sounds odd but its helped me with my devices.
Sent from my Nexus 7 using Tapatalk 4
do this only if you can see PTP on PC
On PC check device manger, on Android if there is ADB driver - uninstall it
On N7 set to MTP, debug off and reboot with N7 USB cable connected to PC
It should re-install the ABD drivers on PC before N7 fully boots up
You will be back in action.
n9900229 said:
I have usb debug enabled
my MTP is on
Click to expand...
Click to collapse
Actually for me, it's the opposite. If usb debugging is on I can't access the device to view files. Try disabling it?
yea thanks though everyone I got it to work. I had my old nexus and new drivers mixing up my ports for some reason not being able to access it at all

[Q] Can't update Drivers

Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Aerowinder said:
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Click to expand...
Click to collapse
That would have been roughly a year ago. I believe I did boot straight into the OS.
mdamaged said:
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Click to expand...
Click to collapse
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Allane176 said:
That would have been roughly a year ago. I believe I did boot straight into the OS.
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Click to expand...
Click to collapse
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
mdamaged said:
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
Click to expand...
Click to collapse
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Allane176 said:
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Click to expand...
Click to collapse
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download these, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
mdamaged said:
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
Click to expand...
Click to collapse
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Allane176 said:
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Click to expand...
Click to collapse
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install Wugs NRT, as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: http://www.nirsoft.net/utils/usb_devices_view.html, but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
mdamaged said:
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install ], as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: , but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
Click to expand...
Click to collapse
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Allane176 said:
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Click to expand...
Click to collapse
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
mdamaged said:
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
Click to expand...
Click to collapse
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Allane176 said:
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Click to expand...
Click to collapse
No problem, maybe you'll work on it again and you'll figure it out. Also, you can use airdroid for transfer of files, I hear it works really well.

Device not detected.

Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
mdamaged said:
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
Click to expand...
Click to collapse
Didn't work, followed your steps in the other thread. I guess I'll just have to wait until a flashable zip for L :/
edit- And btw I tried it on both of my hard drives, one with windows 8 and one with windows 7, didn't work on either.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
wantabe said:
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
Click to expand...
Click to collapse
Thanks mate, didn't work though so I'm not sure what is going on. I'll just wait until zips get created but thanks for the help guys.

USB error PLEASE HELP!

USB will not function with my OnePlus 3, I've loaded drivers and still no avail.
templarsniper said:
USB will not function with my OnePlus 3, I've loaded drivers and still no avail.
Click to expand...
Click to collapse
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.
There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?
kenboyles72 said:
There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?
Click to expand...
Click to collapse
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.
TNSMANI said:
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.
Click to expand...
Click to collapse
I cant even root for the life of me now, Im on 8.0, I'm trying to just root the phone and to start the computer has to recognize it I understand but it won't, with my Oneplus 2 was fine,(I'm thinking maybe phone doesnt have the drivers built in to the file system, you know when you plug in and turn on MTP it shows the drivers app for Windows?) the only thing it errors plugging in.
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.
On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80
Fixed USB problem
kenboyles72 said:
On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80
Click to expand...
Click to collapse
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.
templarsniper said:
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.
Click to expand...
Click to collapse
If you are running Win 10, you will have to disable driver signing before the correct drivers are installed. May be that was your issue.

Categories

Resources