Develop Bugs

[Q] Rooting Problem

I'm following the stickied unlocking bootloader and root thread.
I got to step 13. type this into your command prompt window fastboot oem get_identifier_token
It says waiting for device.
I got search in the thread and come across
ckpv5 said:
"waiting for device" usually means the usb bootloader driver is not installed.
Connect your device in fastboot mode. Open your device manager, manually update driver for that "android 1.0".
Attached here both driver for 32bit & 64bit. Use the one that suit to your PC.
Click to expand...
Click to collapse
I download the driver and follow instructions here
ckpv5 said:
I'm also on Windows 7 64bit.
What you need to try is, hopefully what I remember is correct ...
be on fastboot usb
open device manager, on the "android 1.0" :
update driver software
browse my computer for driver software
let me pick from a list of device drivers on my computer
android usb device
next
have disk
browse to the driver you downloaded (browse up to *.inf)
it will detect as my htc
next
ignore any error
the usb bootloader driver will be installed
EDIT : Tested.. the above step is correct.
Click to expand...
Click to collapse
Windows 7 says "The folder you specified doesn't contain a compatible software driver for your device."
I try using the Google driver from the android adk but that doesn't work either. I also tried letting windows update find it. Those drivers won't work either.

when you are in fastboot mode and connect it to the usb. you should now see fastboot usb. if you do not see "fastboot usb" you are not connected. something with your drivers

intrepid9 said:
I'm following the stickied unlocking bootloader and root thread.
I got to step 13. type this into your command prompt window fastboot oem get_identifier_token
It says waiting for device.
Windows 7 says "The folder you specified doesn't contain a compatible software driver for your device."
I try using the Google driver from the android adk but that doesn't work either. I also tried letting windows update find it. Those drivers won't work either.
Click to expand...
Click to collapse
Download the latest HTC Sync Manager, it will install all the drivers needed.
Then you can uninstall the Sync Manager if you want to but leave the drivers.
http://www.htc.com/www/software/htc-sync-manager/

jaredl45600 said:
when you are in fastboot mode and connect it to the usb. you should now see fastboot usb. if you do not see "fastboot usb" you are not connected. something with your drivers
Click to expand...
Click to collapse
I do see fastboot usb
ckpv5 said:
Download the latest HTC Sync Manager, it will install all the drivers needed.
Then you can uninstall the Sync Manager if you want to but leave the drivers.
http://www.htc.com/www/software/htc-sync-manager/
Click to expand...
Click to collapse
Thanks. It works!

[GUIDE]Enable USB Debugging and setup Android SDK for Fire Phone

Disclaimer:I am not responsible if using anything I've made or provided suddenly deep-fries your device or causes thermonuclear war leading to alien abductions.
Hey guys!
It's been a while that I've been seeing people having problems to enable USB debugging and setting up the Android SDK to recognize the device. So,I've made a guide to help you enable USB debugging and set up the Android SDK accordingly. So let's begin!
What you'll need:
Windows/Linux/Mac OS X with the Android SDK installed
A Fire Phone
Click to expand...
Click to collapse
Setting up Android SDK and drivers:
At first,make sure you have the Android SDK installed,adb and fastboot working.
Open the SDK manager
Click on "Tools" and then click on "Manage add-on sites"
Click on the "User Defined Sites" tab,click "Add" and paste this URL:https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
Click "Ok". Wait for it to finish. Then,from the repo of Android 4.2.2(API Level 17),select Fire Phone SDK and install it.
Remove any Fire Phone drivers using device manager
Go to the directory of the SDK and find this:
Code:
/add-ons/addon-fire_phone_sdk_addon-amazon-17/tools/KindleDrivers.exe
Run the driver setup and connect the phone having USB debugging enabled. If you don't know how to do this,it's explained below.
Done!
Click to expand...
Click to collapse
Enabling USB debugging:
Go to Settings
Scroll to the Device section and expand the section.
Tap Get info about your Fire.
Tap any item at least 7 times in 5 seconds
Developer options will appear. Set it to On.
Go to developer options and enable USB debugging.
Done!
Click to expand...
Click to collapse
Thanks a lot for reading my guide. If this was useful to you,please hit the thanks button. Feel free to comment,post or report anything. Thanks.

Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:

I am M3 said:
Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:
Click to expand...
Click to collapse
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.

I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
Could you try in a Linux distro live CD? It should detect the device without a hitch
Sent from my device running CyanogenMod 11

I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
If you're using Windows here's how I did it on Windows 7. Once you open ADB and reboot it into recovery mode remove it from Device Manager. Reboot you PC if asked. Never unplug or remove your phone through any of this. You may need to remove it a second time from Device Manager after a reboot. It'll eventually show up under Other Devices with the Model Number as the device name (at least mine did). Once it's there then go and update the driver. Tell Windows you want to pick from a list of all the devices. Scroll down until you see Amazon listed on the left side. You'll then see "Android Composite ADB Interface" listed on the right. Choose that. Then it should be recognized again and you can sideload to roll back. Once you roll back you'll probably get a lot of errors but it will work and it will root using the towelroot APK that's posted in the other forum here. I had to have my phone services so I had to do a factory reset on my phone because it broke my phone services. But the roll back process itself was very easy to do once I figured out how to get it recognized again while in recovery mode.

I did what the directions say, but I don't see the fire phone listed in the sdk.

mnknight said:
I did what the directions say, but I don't see the fire phone listed in the sdk.
Click to expand...
Click to collapse
You have to choose the correct driver in Device Manager
On Windows 8/8.1 you may have to activate unsigned drivers

Kindle drivers don't seem to be working for me!

In Windows 8 and newer you have to activate unsigned drivers.
And please choose driver in device manager!

Kindle driver not working for me on windows 7
Kindle driver not working for me on windows 7

Grizzly123 said:
Kindle driver not working for me on windows 7
Click to expand...
Click to collapse
Try using a Linux distro

hey, first sorry for my bad english. isnt my native language.
ich have installed all i need (Windows/Linux/Mac OS X with the Android SDK installed,Android SDK installed,adb and fastboot working[but i dont really know what fastboot working means.])
i have no problem with step 1-5 but i dont understand step 6. i google it but i dont understand. can you please update pictures? that would be very nice.
i have a sec question. my fire phone is netlocked(german). is where still a netlock after install andoid?
again, sry for my bad english :/
thanks for help
munir

Step 6.
In windows device manger, remove all the fire phone devices listed.
Then run the KindleDivers.exe listed in step 7.
When you plug the phone back in windows "should" find and use the right drivers.

Thank you

For reference, the drivers have now moved. The following is an extract from the latest release notes:
* Windows USB drivers have been removed from the tools directory. You may access them from the SDK Manager under Extras.
Click to expand...
Click to collapse
They're installed with the package Extras / Kindle Fire USB Driver and will be located at: android-sdk\extras\amazon\kindle_fire_usb_driver
Other than that, instructions work fine, thanks

hello op, i got as far as step 4, when you mention add the link, mine shows new, everything after step 4 is different. can you please help?

Stuck on recovery
Solved it

Update: in the sdk manager, you must select 'kindle fire usb driver' under 'extras' now, and install that package. Then, you can find it in the sdk dir under sdk/extras/amazon/kindle_fire_usb_driver/KindleDrivers.exe

No fastboot devices but can use adb devices.

Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks

I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

ELoTRIX said:
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeah me too, same ROM and PC OS. Very strange

CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10

But phone starts ok in OOS system?
If, yes, download TWRP 3.0.2.1 original & TWRP 3.0.2.1-19 modified. Put them in phone sd card. Download FLashify from Play store and flash recovery .img. Then go recovery to test if it works.
One of those will work.

inflames19 said:
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
Click to expand...
Click to collapse
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....

Thanks for the different solutions, I'll try it for myself.
But I'm still wondering why the unlock worked because there it used fastboot too

1
me too its says : Witting for devices !!!
Rom: OOS 3.2.7
PC: Windows 10

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.

1
rpsgrayfox said:
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
Click to expand...
Click to collapse
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem

Since there are a lot of people complaining I think the problem is bigger than we think :/ My OP3 nor OPO are seen

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Sir Mohd said:
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Click to expand...
Click to collapse
I'm sorry to hear it didn't work, I'd try to reinstall adb and fastboot then using Minimal Adb and Fastboot found in this thread http://forum.xda-developers.com/showthread.php?t=2317790

ELoTRIX said:
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Click to expand...
Click to collapse
Please tell us how you did That ,
Ty.

Sir Mohd said:
Please tell us how you did That ,
Ty.
Click to expand...
Click to collapse
I have just installed on my Windows 10, a Virtual Machine (VMware) with Windows 7 installed all driver oneplus 3 and adb+fastboot and it works

I have the same issue. Got my OP3 yesterday and have been trying in vain to get my Windows 10 install to recognise the phone in fastboot mode, but to no avail. I am unable to unlock my bootloader.

I think the problem is with Windows 10. My laptop did an update yesterday, I think that's the problem.

Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help

It appears to be an issue with Windows 10 drivers. I have used an ancient install of Xubuntu on an older EeePC in order to unlock the bootloader and flash TWRP and SuperSU. I've still had no luck getting fastboot to be recognised on Windows 10, though on Xubuntu, it is recognised instantly with no issues.

inflames19 said:
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
Click to expand...
Click to collapse
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u

Sir Mohd said:
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Click to expand...
Click to collapse
I'm not at my pc atm but I'll try my best:
If you plugin your op3 there will be a cd mounted with the setup for the driver.
I just installed this driver with the setup.exe (on a complete new instance of Windows 7).
After the installer was finished, I opened cmd.exe and could use adb and fastboot.

Unlock bootloader - "waiting for any device"

I got my OP3 today and am trying to unlock the bootloader. I've tried every tutorial and toolkit out there but they all get stuck at the same point in adb, "waiting for device". The "adb devices" command works fine but anything else gets stuck on "waiting for any device". I've tried googling the issue but none of the suggestions have worked so far. Any input would be great.

did you enable oem unlocking from developer options?

bro you may be running win 10 and to connect fastboot on that u need adb driver which u will find on windows update all u have to do is just connect your phone with data transfer mode and update the window 10 . ull find something name qalllcom its adb drive or i dont but after that it will like charm.

I have all the necessary developer options checked. After futzing with it for hours, I tried a different computer (also Windows 10) and it worked right away. I'm going to see what the driver issue is this evening because I still would like to use the original computer I was using. Thanks for the replies!

What does "adb devices" return?

aadityarulez said:
What does "adb devices" return?
Click to expand...
Click to collapse
Screenshot:

for bl unlock, you need to be at fastboot mode, and installed right driver, for me working any of stock Google USB package fastboot bootloader driver.

Go to fastboot mode and do "fastboot devices", then try unlocking bl.

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

harish15 said:
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.

shobuddy said:
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.
Click to expand...
Click to collapse
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs

harish15 said:
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried this several times over. I do not get the tick option to delete.

shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Pm me, if case, you need some guidance.
Sent from my Xiaomi Mi 5 using XDA Labs

Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help

shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface

peterk-1 said:
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface
Click to expand...
Click to collapse
I tried this but didn't see any new/different entry in DM when I rebooted into bootloader. Didn't see OnePlus under manufacturers either.

cyspak said:
Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help
Click to expand...
Click to collapse
Okay so this is the problem. I figured it out 2 days ago.
check the bootloader driver when you're in fastboot. Right click it and update driver, it should be the Android Bootloader 9.00, and not Bootloader 11.00
it's a silly weird fix, but it should be under Android and not Kedacom
I was using the Android SDK Studio Platform Tools and Google Drivers provided from SDK Studio

deleted

Similiar to the previous users post I'll try and be a bit more clear.
unplug your device if plugged in.
boot in to fastboot mode on your device.
Go to your PC and access device manager
plug your device in and you should see
"kedacom" instead of android interface
now inside you wanna click update driver
browse my compute for driver software > let me pick from a list of driver software > "Android adb sooner interface"
if its not that exact one check for the one that does say adb interface.
https://www.youtube.com/watch?v=Gdl6P2akRK0

I created a bootable USB drive with Linux Mint to solve my problem. It was Windows 10 that would recognize my OnePlus 3 in "Fastboot Mode" with Kedacom drivers.

OP3 Not Found By Fastboot (Win 10)

So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.

MrHaPpY66 said:
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
Click to expand...
Click to collapse
Have you enabled oem unlocking from developer options?

I'm having the same problem. After going back to Oxygen OS (now 3.5.4) from MIUI 8 fastboot just doesn't work anymore. ABD works just fine (tried on Minimal ABD and Fastboot on Windows and ABD installed over Android Studio on Ubuntu. Fastboot did recognize the phone on Ubuntu but flashing TWRP resolved in a bootloop (tried the old and the new recovery image).
All drivers are installed on both Windows and Ubuntu (I even removed all drivers on Windows and added them again) and just to make sure everything gets installed I disabled driver signature verification on Windows, but as I said - still no luck.
Edit: Of course USB Debugging and OEM Unlocking is enabled (my bootloader is also unlocked since I already had tried out multiple roms)

Had the same Problem, Win10 is the Problem + the old OP Drivers + the new Update to Win10 etc.
Nothing worked, tryed everything. Created a Thread last week here also...
After that i created a new Partition and installed Win7 on it. All works fine, only thing is while Boot ur System u have to pick ur OS or it waits 30sec to boot up but thats ok.
Now i have Win10 for everything and i reboot to win7 for Fastboot/OP3
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Didnt tryed the last Tip.

KornY10 said:
Win10 is the Problem
Click to expand...
Click to collapse
Can't solve your problem, but OP3 fastboot does work in Windows 10. I did have to disable driver signature verification to install the driver in the first place, and you'll have to leave it off for the driver to stay functional, but it definitely works on Win 10.

I dont tryed ur Way, so yes after disable Driver sign. it works like u Said but i did not Test it.

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 .

Same here

It's driving me crazy. I've updated from a rooted stock OS (incl TWRP) via full OTA directly to 3.2.7, which removed TWRP and root.
I now cannot enter a Fastboot mode which detects the USB connection. Thus I can't flash TWRP again and can't root my phone, making lots of apps unusable.
I've tried every suggestion on every thread but nothing works...
Sent from my ONEPLUS A3003 using Tapatalk

Also got kedacom on my device manager after automatic driver update but my phone still isn't recognised in adb devices, does everyone else's serial number show up?

You guys still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs

Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work

SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
Good that you found the solution..
Sent from my Xiaomi Mi 5 using XDA Labs

Well I didn't really solve the problem on win 10 so i just decided to use Ubuntu instead. Worked well

SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
I tried that too, but didn't work. What driver did you select in Device manager?

superiscch said:
I tried that too, but didn't work. What driver did you select in Device manager?
Click to expand...
Click to collapse
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)

SgtIcetea said:
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
Click to expand...
Click to collapse
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good ?

superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Yeah that one. After disabling the driver signature verification you have to re install it, when it's not disabled windows just doesn't install it although it says it does. After I disabled it Windows actually showed a completely new window during installation to install the driver properly

superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Man, had to just do it through my Ubuntu VM. Tried Win 10 Win 7, all gave me troubles.
Started Ubuntu, setup ADB and unlocked in a breeze

i have same problem