Develop Bugs

[Q] Data transfer via MTP on ubuntu

Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system:
Code:
[49875.145923] usb 1-1.2: new high-speed USB device number 12 using ehci-pci
[49875.240046] usb 1-1.2: New USB device found, idVendor=0bb4, idProduct=0c02
[49875.240057] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[49875.240063] usb 1-1.2: Product: MT65xx Android Phone
[49875.240068] usb 1-1.2: Manufacturer: MediaTek
[49875.240072] usb 1-1.2: SerialNumber: ...
but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi

prinz.z said:
Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system. but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi
Click to expand...
Click to collapse
I guess this is more an Ubuntu issue/question than Fairphone's..
You can follow instructions here
Code:
$ sudo mtpfs -o allow_other /media/MTPdevice
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=0bb4 and PID=2008) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:2008 @ bus 2, dev 20
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: FP1
Nautilus gave me read-only access to content under the custom mount point /media/MTPdevice. dmesg gave me the same log as yours when recognizing the device...

It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)

Okay, I see.. With my former phone (LG O4x, cm-11) it was working flawlessly with mtp on Ubuntu, that's the rason I asked.. With the fairphone, I'm simply using adb for the moment to copy single files..
elchi1234 said:
It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)
Click to expand...
Click to collapse

[Q] Bricked Find 7

Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot

bcuraman said:
Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot
Click to expand...
Click to collapse
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.

suraj.das said:
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.
Click to expand...
Click to collapse
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0

bcuraman said:
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.

suraj.das said:
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.
Click to expand...
Click to collapse
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?

bcuraman said:
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?
Click to expand...
Click to collapse
I have no idea. Sorry. Maybe use your friend's pc? OR VM?

Hi there. I too am having issues with my Find 7 as well. I just bought it today. The previous owner apparently went to flash cm11 and he soft bricked it. The phone will power on to the start screen the the screen stays black and goes on and off. I can get to fastboot but not recovery. I have read in the oppo forums that I need to push the stock recovery too it but am unfamiliar with fastboot. I am willing to pay someone to get this phone working. Any input would be greatly appreciated.

MsmDownloader works great from inside an Windows XP VMWare virtual machine.

VK815 rooting help

I've seen reports of the VK815 being rooted and would like to root mine. Is there someone who has a VK815 and has rooted it who is willing to share how they accomplished it?
I have 'adb' available and working, the developer mode enabled, and can talk to the phone. Trying to attain superuser from the 'adb shell' doesn't work because the 'su binary' is missing. 'adb reboot recovery' gives the ''dead android' and the 'power/volume -' key combination results in a normal boot.
Thanks,
Jim

I rooted my vk815 with one click root from the g3 section. Not sure yet how to post links I'm new to xda...
---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------
http://forum.xda-developers.com/showthread.php?t=3056951

That looks like a solution for those who have Windows PC's connected to their tablets. I'm a linux only and should have put that in my original post.
I guess I could look at the script and see if there's any clues inside it.
Thanks,
Jim

There is a python script for using the send command with the files. On my phone and at work, so difficult for me to look up, but I'm sure googling send command LG python will turn it up (probably under g3 or g4 forums...)

danaff37 said:
There is a python script for using the send command with the files. On my phone and at work, so difficult for me to look up, but I'm sure googling send command LG python will turn it up (probably under g3 or g4 forums...)
Click to expand...
Click to collapse
I've seen it and given it a try. The writer and everyone else in the thread look like they aren't working with a VK815. The VK815 doesn't trigger loading of the 'serial' module. I don't have one on my system so that looks like a problem. I keep getting this error message:
[email protected]:/root# qcdlcomm.py /dev/ttyUSB0
Traceback (most recent call last):
File "/home/jim/Desktop/qcdlcomm.py", line 13, in <module>
import serial
ImportError: No module named serial
For anyone who's interested; the python script is here about a quarter of the way down the page. hxxp://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772/page46 (Change the x's to t's)
Jim

Seems like the kernel can't figure out what chip is handling the serial I/O for the tablet so it only loads 'usbserial_generic'. That module can't change any of the comm parameters. The error messages now want a more specific module loaded before running the python script.
[1655862.790132] usb 1-9: new high-speed USB device number 9 using ehci-pci
[1655862.905356] usb 1-9: New USB device found, idVendor=1004, idProduct=6293
[1655862.905359] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1655862.905361] usb 1-9: Product: LGE Android Phone
[1655862.905363] usb 1-9: Manufacturer: LG Electronics Inc.
[1655862.905365] usb 1-9: SerialNumber: VK815275a2846
[1655862.905753] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655862.905755] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655862.905757] usbserial_generic 1-9:1.0: generic converter detected
[1655862.905816] usb 1-9: generic converter now attached to ttyUSB0
[1655862.946215] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
[1655862.946343] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[1655862.946356] usbserial_generic 1-9:1.0: device disconnected
[1655863.049404] usb 1-9: reset high-speed USB device number 9 using ehci-pci
[1655863.164195] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655863.164201] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655863.164203] usbserial_generic 1-9:1.0: generic converter detected
[1655863.164288] usb 1-9: generic converter now attached to ttyUSB0
[1655863.164329] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
Jim

jowski said:
Seems like the kernel can't figure out what chip is handling the serial I/O for the tablet so it only loads 'usbserial_generic'. That module can't change any of the comm parameters. The error messages now want a more specific module loaded before running the python script.
[1655862.790132] usb 1-9: new high-speed USB device number 9 using ehci-pci
[1655862.905356] usb 1-9: New USB device found, idVendor=1004, idProduct=6293
[1655862.905359] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1655862.905361] usb 1-9: Product: LGE Android Phone
[1655862.905363] usb 1-9: Manufacturer: LG Electronics Inc.
[1655862.905365] usb 1-9: SerialNumber: VK815275a2846
[1655862.905753] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655862.905755] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655862.905757] usbserial_generic 1-9:1.0: generic converter detected
[1655862.905816] usb 1-9: generic converter now attached to ttyUSB0
[1655862.946215] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
[1655862.946343] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[1655862.946356] usbserial_generic 1-9:1.0: device disconnected
[1655863.049404] usb 1-9: reset high-speed USB device number 9 using ehci-pci
[1655863.164195] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655863.164201] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655863.164203] usbserial_generic 1-9:1.0: generic converter detected
[1655863.164288] usb 1-9: generic converter now attached to ttyUSB0
[1655863.164329] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
Jim
Click to expand...
Click to collapse
I doubt there are drivers for linux for a g4 in Linux, and I know people used the script for that. You are doing this in download mode? I can't remember since it's been a while for me setting it up, but does the Android sdk install the generic android USB drivers in Linux?

danaff37 said:
I doubt there are drivers for linux for a g4 in Linux, and I know people used the script for that. You are doing this in download mode? I can't remember since it's been a while for me setting it up, but does the Android sdk install the generic android USB drivers in Linux?
Click to expand...
Click to collapse
The kernel modules handle what drivers would do in Windows.
I'm in the download mode and if I boot normally instead of into download; I can talk to the tablet with adb. I'm thinking that maybe if I comment out the serial port settings code, the script might work. I'll try that later.
Jim

jowski said:
The kernel modules handle what drivers would do in Windows.
I'm in the download mode and if I boot normally instead of into download; I can talk to the tablet with adb. I'm thinking that maybe if I comment out the serial port settings code, the script might work. I'll try that later.
Jim
Click to expand...
Click to collapse
I just know in the past for fast boot mode on other devices, I had to run the Android sdk tools and add some udev rules. But I can't remember if the sdk tools was simply for executables, or for modules/drivers

danaff37 said:
I just know in the past for fast boot mode on other devices, I had to run the Android sdk tools and add some udev rules. But I can't remember if the sdk tools was simply for executables, or for modules/drivers
Click to expand...
Click to collapse
When I can talk to the tablet; adb works but fastboot doesn't. 'adb reboot recovery' gives the dead android. This is turning into a real adventure.

There has to be something after 'modprobe usbserial' to load a specific module on the PC so it can talk to the VK815. Would the Windows ddl's give a clue?
Jim

Well, I'll be go to ....
Commenting the block of code that sets the serial port settings worked! I went into the download mode with the key press (power off, volume +, connect the usb cable, wait for Firmware Update screen, release volume +) and ran the script and was talking to the tablet. Looks like the next step is to load the goodies first and then try the manual commands to install root.
Whatcha think gang? I'm thinking we're almost there and how cool is that!!!
Jim
edit: [email protected]:/# ./qcdlcomm.py /dev/ttyUSB0
Traceback (most recent call last):
File "qcdlcomm.py", line 47, in <module>
port=sys.argv[-1]
File "/usr/lib64/python2.7/site-packages/serial/serialutil.py", line 282, in __init__
self.open()
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 296, in open
self._reconfigurePort()
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 325, in _reconfigurePort
raise SerialException("Could not configure port: %s" % msg)
serial.serialutil.SerialException: Could not configure port: (25, 'Inappropriate ioctl for device')
Any ideas??? I changed the 'ser' block to
ser = serial.Serial(
port=sys.argv[-1]
)
I'm back to thinking it's a module that needs to be loaded.

Previous post errors were due to 'cdc_acm' being reloaded and me not checking that before running the script. Fixed that and reloaded usbserial. Now the errors are:
[email protected]:# qcdlcomm.py /dev/ttyUSB0
Special commands: ENTER, LEAVE, exit
# ENTER
Traceback (most recent call last):
File "/home/jim/Desktop/qcdlcomm.py", line 100, in <module>
cmd(input)
File "/home/jim/Desktop/qcdlcomm.py", line 87, in cmd
rawcmd(commands[input])
File "/home/jim/Desktop/qcdlcomm.py", line 63, in rawcmd
ser.write(input)
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 490, in write
if not self._isOpen: raise portNotOpenError
serial.serialutil.SerialException: Attempting to use a port that is not open
So much for talking to the tablet.
Jim

I tried usb_modeswitch and got something that may be encouraging. I'll post the command and output so someone who knows a bit about usb_modeswitch can shed some light.
[email protected]:/home/jim/Desktop# usb_modeswitch -p 0x6293 -v 0x1004 -M a1
Look for default devices ...
product ID matched
Found devices in default mode (1)
Access device 067 on bus 001
Get the current device configuration ...
OK, got current device configuration (1)
Use interface number 0
Use endpoints 0x01 (out) and 0x81 (in)
Not a storage device, skip SCSI inquiry
USB description data (for identification)
-------------------------
Manufacturer: LG Electronics Inc.
Product: LGE Android Phone
Serial No.: VK815275a2846
-------------------------
Looking for active driver ...
OK, driver detached
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
Sending the message returned error -1. Try to continue
Reset response endpoint 0x81
Reset message endpoint 0x01
Could not reset endpoint (probably harmless): -99
-> Run lsusb to note any changes. Bye!
There are other messages that can be sent as part of the command. I'm wondering if this is how we can gain access to the device using linux.
Jim

Tried the windows method from an XP machine. Keep getting a "Device cannot start. (Code 10)" error. Tried uninstalling and reinstalling the LG drivers along with the VZW drivers. Also tried using only the VZW drivers. Same results. The device manager says the DIAG port is COM16 but Send_Command.exe can't open port 16.
Anyone had success rooting from XP or do I need to try Windows 7?
Jim

jowski said:
Tried the windows method from an XP machine. Keep getting a "Device cannot start. (Code 10)" error. Tried uninstalling and reinstalling the LG drivers along with the VZW drivers. Also tried using only the VZW drivers. Same results. The device manager says the DIAG port is COM16 but Send_Command.exe can't open port 16.
Anyone had success rooting from XP or do I need to try Windows 7?
Jim
Click to expand...
Click to collapse
I tried XP but the device drivers wouldn't install. 7 worked great for me tho. But I'm not real good with Windows possibly some others would know better??

So my tablet today prompted me to update to 11A. But since it's rooted, so it didn't go thru. Does anyone know what we can do with that info? Like to keep root and update?

I gave up on finding a linux solution and did it with WinDoze 8. A root canal has to be less painful. At least it's rooted now.
I'm holding off on the update until after I get a few apps loaded that require root access. I wish there was a way to turn off the updates and nags.
Jim

I think the linux answer to talking to the VK815 involves the BCM2079x on the tablet. Could that mean the linux box trying to load a serial driver would need to do something like 'modprobe bcm2079x'? If so, where to we find the config for it in the kernel .config?
Jim

I know this is an old thread, but maybe someone can send me in the right direction. My non-rooted VK815 updated to 6.0 and ruined the battery life. So, I'd like to root it. I can only find threads on rooting the previous version - has anyone rooted the 6.0 version?

Fire TV 1 Bricked with Marshall London HS-USB Diagnostic 9006

My Fire TV bricked and none of the described un-bricking method works.
When connecting through USB I can see "Marshall London HS-USB Diagnostics 9006 (COM21)" port in Device Manager. I also observed that MiFlash tool recognize it as "\\?\usbstor#disk$ven_qualcomm&prod_mmc_storage&rev_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}"
I have unbricked my Mi Phone using this tool and it requires a ROM containing boot, kernel, system etc. images and other flashing scripts. Do we have similar kind of ROM available for Fire TV?

I am in the same boat.

Did you try this

{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Looks like I goofed up big time. Now I only see QHUSB_DLOAD and I am not able to see any drive on OSX or Linux. I am suspecting the Mi Flash tool that I was using to check it did something. Instead of showing "\usbstor#disk$ven_qualcomm&prod_mmc_storage&re v_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}" it is now showing COM20.
On linux I tried this command
Code:
dmesg | tail
and it shows following output
usb 1-2: new ISB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB_DLOAD
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered for Qualcomm USB modem
qcserial: 1-2:1.0: Qualcomm USB mode converter detected
usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
Any help in this regard is appreciated.

{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Ok.. I have a Linux VM (ubuntu 16.x) booted up, and the FireTV is recognized as a /dev/sdb device. I have downloaded the .bin file from amazon. How do I decompress the BIN file to get the images folder to dd over to the firetv partitions?
I am a linux newbie, so missing that key step
NEVERMIND - Figured it out

Thanks Rbox & {ParanoiA} for hte unbricking guide. I successfully recovered my FireTV and am back up and running.

Rbox/{ParanoiA} any way to recover my fire TV from the state it is currently in.
One more observation. Now it is showing the connection as "Marshall London HS-USB Diagnostic 9008"

After googling a bit I zeroed in that it should be recoverable. I a following this link
http://www.androidbrick.com/unbrick-all-qualcomm-snapdragons-from-qualcomm-hs-usb-qdloader-9008-if-you-have-the-right-kind-of-rom-qhsusb_dload/
However I need following files (MPRG8064T.hex and 8064T_msimage.mbn) in addition to what mentioned in this. I am not able to find anything other than MPRG8064.hex and 8064_msimage.mbn anywhere. I am not sure whether I can use these files or not

MPRG8064.hex and 8064_msimage.mbn did not work
Can Anyone provide MPRG8064T.hex and 8064T_msimage.mbn file?

Just uploaded the requested - http://www.mediafire.com/download/jqfx835f5ompvf4/q.7z
the link contains the non T variant of the requested files

In an attempt to get the device from 9008 to 9006 mode, I attempted http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html without success

After two months of reading and testing every trick i've read on blogs, youtube, russian or chinese forums, and still at the exact same place. No matter what I do or try, I can't get out of the bloody 9008 state. Did any of you had any breakthrough on the problem? Thanks!

OP3 not recognized on Win10

My oneplus 3 isn't found in com/ports on windowsill 10. It's unable to load recovery and won't boot to system. Fastbook still works and has a unlocked boot loader. Trying to install stock firmware to restore the device for se again. Any help would be greatly appreciated.

Try loading drivers, have no issues here. Also run cmd prompt by right clicking on cmd.exe and selecting "Run As Administrator"
Sent from my SM-N930T using Tapatalk

Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.

Also make sure USB debugging is enabled in the developers settings and you have the correct USB mode enabled (not charging)
Sent from my SM-N930T using Tapatalk

jaydubya24 said:
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Click to expand...
Click to collapse
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10

Will_Xda said:
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Click to expand...
Click to collapse
here is the device manager

setup driver and try in twrp

A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.

Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.

jaydubya24 said:
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
Click to expand...
Click to collapse
One more thing. Connect the phone to a USB 2.0 port and not a 3.0 port. It may not be recognised in a 3.0 port.

peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what I found on USBDeview. There are two other versions of the OP3 on this list. But they do not show as being connected while the phone is in Fastboot. Im unable to access the OS to enable anything that may help with it being seen on my computer.

http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Win7 works and i dont tryed the nice tip on site2.

i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .

You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs

update on the op3
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what shows up after the one plus boot logo appears.

I had similar problem. I was rooting my 1+3. I went to device control settings in WIN 10 and removed 1+3 drivers. Next time when i was in fastboot mode windows installed drivers. :highfive:
I used the ones that came with 1+3

jaydubya24 said:
This is what shows up after the one plus boot logo appears.
Click to expand...
Click to collapse
I think this thread will supply the solution. "your" problem is at this post https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/page-4#post-15169580