Develop Bugs

[Q] need help with usb debugging

i bought my xperia play 4 days ago and i cant seem to get the usb debigging to work. MTP and MSC work fine, but when i enable usb debugging, all it shows is SEMC HSUSB driver and both MTP and MSC do not work. i have tried instaling the gordon gate drivers, reinstalling pc companion. i'm trying to root my phone (2.3.4) without unlocking the bootloader but i cant do that until i have usb debugging working.

I have found that some PC's just don't like doing it... Do you have another machine that you can test on?
I know on my PC it just won't pick it up correctly, even after reinstalling the drivers (and at one stage Windows and testing on a virtual linux box) and it just fails. I have to use my partners laptop.

thank you for your reply may i know wad os your machine was using? mine is windows 7.

Windows 7 also, but then so is the laptop that I am running on. Not sure what was the problem and just got sick of trying to fix it to be honest

d31b0y said:
Windows 7 also, but then so is the laptop that I am running on. Not sure what was the problem and just got sick of trying to fix it to be honest
Click to expand...
Click to collapse
ohh welll.... i just deleted the android sdk manager. i'll try to redownload and reinstall it and the pc companion. if that fails, i'm going to try using virtual box with windows xp. i've been trying for a few days now, hope i can root it successfully without resorting to unlocking the bootloader.

Might be better off setting up a dual boot with XP. Otherwise you can run into problems with sharing the USB slots between the host and virtual machine.

if only i could do that..... btw, do you have any idea how to install the drivers? its a 6mb file from developers world, and i cant seem to find a way to install it.. http://developer.sonyericsson.com/wportal/devworld/search-downloads/driver?cc=gb&lc=en

Yep, just extract the files and then when you plug the device in and it's looking for drivers, point it towards the folder that you just extracted. Should do it automatically after that.
If it doesn't look for drivers any more, which can happen if you have connected it in the past, you can open your computer manager (Start -> run -> Compmgmt.msc) then select device manager. Find the device in the list and right click and update drivers. Finally, just select the path to search to be that of the folder that you extracted.

i have tried what you said, but it says it cannot find the driver software for this device. this is with usb debugging enabled. when usb debugging is enabled, both mtp and msc do not work.. the only indication of the device on my com is from device manager.

Which OS do you have ?
64 Bit, or 32 Bit(x86) ?
-32/64bit drivers: http://www.multiupload.com/0XZV1LXRVA
Click to expand...
Click to collapse

Can't get Nexus 7 to show up on computer

Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far

and yes forgot to put in the title but this is for the Nexus 7FHD 2013

Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.

sfhub said:
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
Click to expand...
Click to collapse
tried USB 3.0 as well as 2.0 on desktop doesnt work, shows up as a device on safely remove hardware, and I can also see it under other devices in hardware manager or whatever but doesnt display in computer
USB debugging enabled or disabled on stock doesn't work.. tried going back to stock and doing driver installation etc as well

In device manager are there any unknown devices?

Did you remember to
Originally Posted by Geodude074 View Post
When you uninstall the driver, make sure you check the option to DELETE the driver as well. Otherwise when you try to reinstall it, it will just reinstall the old driver again

Driver instal with WinXP
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.

un1bomber said:
Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
Click to expand...
Click to collapse
Just go in settings then storage and then computer usb connection by opening preferences in storage and then make sure mtp is checked.

Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!

un1bomber said:
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
Click to expand...
Click to collapse
We are always here to help.
I remember few years back I installed miui ROM on my xperia n couldn't connect to PC , only to realise USB wasn't turned to mtp by default. I thought it was a bug, tried everything even to fix it only to realise this.

Thanks a lot !!! This solution worked perfectly for me
You saved lots of time for me
Thanks a ton :good::good::good:
Best regards,
RR215 said:
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
Click to expand...
Click to collapse

If nothing else here has helped you solve this issue, check my thread, it should be of some help to you...

I'm having an issue where I can connect to my laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick

[Q] Cannot Unlock Bootloader on Windows 8.1

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.

Can't get Fastboot to work

Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks

I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.

Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)

jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96

jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.

@Istvan_86,
We should move the discussion for your problem here.

cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.

Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?

Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.

FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.

cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!

Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.

cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.

Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.

What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.

Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html

@clockcycle,
This solution works 100% too. https://www.ubuntu.com/

CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!

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.