Related
Ok, I've just upgraded to windows 7. I was pretty psyched about the whole thing, and my computer seems like a whole new machine, coming from XP 32 bit.
So one thing I'm attempting to get adb to work with my phone. Heres my first problem - right off the bat, my computer doesnt recognize my phone as anything but an unknown device. YES I'VE TRIED DEBUGGING, DISK DRIVE, ETC., but nothing works.
I go to device manager, all I see is unknown device. Ok fine. I download the adb files that allow you to download the Android 2.1 thing and usb drivers. Still nothing works. I go to device manager, try to update the drivers for said "unkown device" and i get a message "the drivers are the newest up to date" or something. I try downloading the 64-bit HTC Hero drivers, same thing. I download and install HTC Sync, same thing.
I get this message when I plug the phone in...
"USB Device not recognized
One of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message"
So my question is, how do i get my computer to recognize my phone, even as storage device??
jasongthang said:
Ok, I've just upgraded to windows 7. I was pretty psyched about the whole thing, and my computer seems like a whole new machine, coming from XP 32 bit.
So one thing I'm attempting to get adb to work with my phone. Heres my first problem - right off the bat, my computer doesnt recognize my phone as anything but an unknown device. YES I'VE TRIED DEBUGGING, DISK DRIVE, ETC., but nothing works.
I go to device manager, all I see is unknown device. Ok fine. I download the adb files that allow you to download the Android 2.1 thing and usb drivers. Still nothing works. I go to device manager, try to update the drivers for said "unkown device" and i get a message "the drivers are the newest up to date" or something. I try downloading the 64-bit HTC Hero drivers, same thing. I download and install HTC Sync, same thing.
I get this message when I plug the phone in...
"USB Device not recognized
One of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message"
So my question is, how do i get my computer to recognize my phone, even as storage device??
Click to expand...
Click to collapse
try uninstalling htc sync and using a different usb port. does that work?
And to address how to get it to recognize as a drive, when you plug it in you should be presented with options where you can make it a disk drive. Or pull down your notification bar and change the type.
elegantai said:
And to address how to get it to recognize as a drive, when you plug it in you should be presented with options where you can make it a disk drive. Or pull down your notification bar and change the type.
Click to expand...
Click to collapse
On the phone yes, I can select a different type. On my computer, I just get that unknown device message.
And out of the blue I just tried a different USB port, and now it works as a storage device.
Did you restart the computer after installing the drivers? Sometimes mine gets a little goofy like that.
jasongthang said:
On the phone yes, I can select a different type. On my computer, I just get that unknown device message.
And out of the blue I just tried a different USB port, and now it works as a storage device.
Click to expand...
Click to collapse
i had that issue with one of my usb ports too. i think sometimes a bank of usb ports are used as basically a usb hub, and the evo doesn't like that, from what i understand.
Reboot comp, reboot EVO. Connect 'em, and then go into Device Manager, uninstall the "unknown device" (EVO), and then have it scan for new devices. Now, when it says scanning for drivers (or something to that effect) look for an advanced or "skip checking Windows Update for drivers" option. Then navigate to the ADB drivers in the Android SDK and tell it to use those. Make sure you have USB Debugging turned on, and EVO's set for "Charging Only".
If that still doesn't work, then there's an incompatibility with your computer's USB controller and Win7.
drmacinyasha said:
Reboot comp, reboot EVO. Connect 'em, and then go into Device Manager, uninstall the "unknown device" (EVO), and then have it scan for new devices. Now, when it says scanning for drivers (or something to that effect) look for an advanced or "skip checking Windows Update for drivers" option. Then navigate to the ADB drivers in the Android SDK and tell it to use those. Make sure you have USB Debugging turned on, and EVO's set for "Charging Only".
If that still doesn't work, then there's an incompatibility with your computer's USB controller and Win7.
Click to expand...
Click to collapse
lol, I did all that a few times, but im sure its not an incompatibility issue. probably just a skipped step somewhere.
jasongthang said:
lol, I did all that a few times, but im sure its not an incompatibility issue. probably just a skipped step somewhere.
Click to expand...
Click to collapse
If your computer is old enough, incompatibility is a possibility. See if there's other ports you can use, like on a different side of the case. Also, what brand computer?
--Swyped from my EVO using XDA App.
drmacinyasha said:
If your computer is old enough, incompatibility is a possibility. See if there's other ports you can use, like on a different side of the case. Also, what brand computer?
--Swyped from my EVO using XDA App.
Click to expand...
Click to collapse
stop! lol its fine. it works. i guess i should have stated that i've been on these forums for quite a while, and have flashed and rooted a few different phones using this computer, but with xp.
i just switched to windows 7, and of course lost all my drivers, and everything I had saved would have to be switched to 64-bit. I just couldnt get anything to work, but it seems to work now.
and I dont know what brand necessarily this computer is. i built it. I do have a dell keyboard though.
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.
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.
Using USB - C cable to connect my N5X to computer, but the computer won't recognize, load new drivers or anything. I vaguely recall having to set something on my old N4 so resolve this issue, but can't remember what it was. Is this because of the C cable?
Thanks in advance.
Did you checked the USB debugging and also set it to file transfer instead of charging??
Verstuurd vanaf mijn Nexus 5X met Tapatalk
Thx Leontine. I had forgot to enable USB debugging, although I am still having issues. When I select "Use USB for: Photo transfer (PTP), I can see the DCIM folder on my phone within Windows Explorer. But when I select File transfer, I don't see anything. What am I overlooking?
Sooner Magic said:
Thx Leontine. I had forgot to enable USB debugging, although I am still having issues. When I select "Use USB for: Photo transfer (PTP), I can see the DCIM folder on my phone within Windows Explorer. But when I select File transfer, I don't see anything. What am I overlooking?
Click to expand...
Click to collapse
Sometimes your computer can install the wrong driver by default
Computer>Device Manager
Assuming you have downloaded the latest usb drivers from google
Find your android device right cllick update driver software> browse my computer >let me pick >Google Inc>Android ADB Interface>Should be good to go..
OR
You can use add on software something like pdanet+ and you should be okay
leontine said:
Did you checked the USB debugging and also set it to file transfer instead of charging??
Verstuurd vanaf mijn Nexus 5X met Tapatalk
Click to expand...
Click to collapse
Yup. You have to manually select the USB mode every time you connect the phone to PC. It gets tiring quick, but not a deal breaker.
You shouldn't have to mess with the USB debugging feature at all. I was running into the issue where it would install the driver and even show "Nexus 5x" as connected but not show up in Windows Explorer, regardless of what connection I set the phone to. Connection settings are available by just pulling down the top menu once the phone's connected.
I went into Windows Device Manager (while the phone was plugged in) and uninstalled and deleted the drivers under "Android." When I then unplugged and plugged the phone back in, it worked. On a side note, it now isn't shown under USB devices or even in the Device Manager, but that doesn't really matter. It's showing up in Windows Explorer.
pkadavid said:
You shouldn't have to mess with the USB debugging feature at all. I was running into the issue where it would install the driver and even show "Nexus 5x" as connected but not show up in Windows Explorer, regardless of what connection I set the phone to. Connection settings are available by just pulling down the top menu once the phone's connected.
I went into Windows Device Manager (while the phone was plugged in) and uninstalled and deleted the drivers under "Android." When I then unplugged and plugged the phone back in, it worked. On a side note, it now isn't shown under USB devices or even in the Device Manager, but that doesn't really matter. It's showing up in Windows Explorer.
Click to expand...
Click to collapse
I'm still not successfully seeing my N5X in Windows Explorer when selecting File Transfer. Photo Transfer works. When I go into Device manager, I found my N5X (listed as a Portable Device and only seen when in PTP) and attempted to update the driver>Browse my computer>Let me pick...Don't see Android as a manufacturer. For what is it worth, I am running Windows 10.
Any help is greatly appreciated.
In the notification center you have to choose the connection mode. It isn't the same as in the developers options...
Thx AlphaGeekV2. From the notification pull down, I chose "File Transfers" but still cannot see my N5X in Windows explorer. Any other ideas?
Sooner Magic said:
Thx AlphaGeekV2. From the notification pull down, I chose "File Transfers" but still cannot see my N5X in Windows explorer. Any other ideas?
Click to expand...
Click to collapse
Try it on a friend's system with W7 and see if it works there. If so, it's something with W10, and we can diagnose further.
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.