Related
Right, I hope I am not being a total noob with this but here goes.
I got my HTC One V today, I plan to unlock bootloader and root my device.
So, following the bootloader stages, blah blah blah (at HTCDev).
And then, I get this: (< waiting for device > )
(Attached image 1)
So, I done some research, and it seemed to narrow down to me not having the right drivers. So I've done some driver research and so on, and installed a few. I also installed HTC Sync.
And then I got to this, when the device is turned on and plugged in through USB:
(Attached image 2)
So, now I try to turn it off and enter the bootloader, follow the steps and so on, but I still get < waiting for device >. Also, if I got to device manager while in this mode I am presented with this:
(Attached image 3)
I have tried following some guides and steps to fix this but I'm getting nowhere.
Anyone think they could help me?
when using fastboot or adb make sure you have adb drivers from android sdk and htc drivers from htc sync and also close htc sync in your tray.
Sent from my HTC One V using Tapatalk 2
by the way, anybody can help me how to relock bootloader ?
-EDIT-
gonemad02 said:
when using fastboot or adb make sure you have adb drivers from android sdk and htc drivers from htc sync and also close htc sync in your tray.
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
I am almost certain I have the ADB drivers and the HTC Drivers from HTC Sync. Although I am not so sure about the HTC Sync drivers. I downloaded and installed the program and then I exited it when I try and fastboot.
My device manager now says this when I go into the bootloader on my HTC One V.
(attached image 1)
Any help would be greatly appreciated.
HI..check ckpv5's post...it is the link to the thread he created to unlock the boot loader...if you need right drivers install htc sync.....
Then put in bootloader and let it install..then wait for it in fastboot....after all drivers have been installed it will work.....
BUT BEFORE THAT YOU HAVE TO DELETE THAT UNKNOWN DEVICE AND RE-CONNECT YOUR DEVICE..
shubhamchamaria said:
HI..check ckpv5's post...it is the link to the thread he created to unlock the boot loader...if you need right drivers install htc sync.....
Then put in bootloader and let it install..then wait for it in fastboot....after all drivers have been installed it will work.....
BUT BEFORE THAT YOU HAVE TO DELETE THAT UNKNOWN DEVICE AND RE-CONNECT YOUR DEVICE..
Click to expand...
Click to collapse
I have followed that thread about 5/6 times but still get waiting for device.
Installed and reinstalled HTC Sync about 4 times.
The drivers appear to be on my computer, yet I'm still getting waiting for device.
Jamizzle93 said:
I have followed that thread about 5/6 times but still get waiting for device.
Installed and reinstalled HTC Sync about 4 times.
The drivers appear to be on my computer, yet I'm still getting waiting for device.
Click to expand...
Click to collapse
Pictorial representation for thee!!
EDIT: sorry i didnt read your post properly...most probably try installing sdk and the usb driver package that comes with it..i had it installed as it is very useful
shubhamchamaria said:
Pictorial representation for thee!!
EDIT: sorry i didnt read your post properly...most probably try installing sdk and the usb driver package that comes with it..i had it installed as it is very useful
Click to expand...
Click to collapse
I assume you mean this driver: (attached image 1).
Yeah, its installed. Also, if I try and install this driver in fastboot mode on the bootloader it says the driver cannot be found. (attached image 2 & 3).
Jamizzle93 said:
I assume you mean this driver: (attached image 1).
Yeah, its installed. Also, if I try and install this driver in fastboot mode on the bootloader it says the driver cannot be found. (attached image 2 & 3).
Click to expand...
Click to collapse
Try my files here: http://bit.ly/IwbRMu
It has Android SDK but the old version, you can skip that one if you want to.
It has Android USB driver and HTC usb driver. So on any unknown device, just point to the drivers folder and see whether it helps or not. After install, reboot your pc first.
Edit: It may be old version but it works great for my new Win7 PC at work that I receive today
ckpv5 said:
Try my files here: (android tools)
It has Android SDK but the old version, you can skip that one if you want to.
It has Android USB driver and HTC usb driver. So on any unknown device, just point to the drivers folder and see whether it helps or not. After install, reboot your pc first.
Edit: It may be old version but it works great for my new Win7 PC at work that I receive today
Click to expand...
Click to collapse
Just to catch everyone up, following on from advice and images above I uninstalled the driver I had installed in this image (image 1).
I am now trying to reinstall a driver which will hopefully work and not give me a <waiting for device> message when trying to unlock the bootloader.
These files in Android Tools still don't seem to want to work, I am getting the following messages below: (images 2 and 3).
Also my hardware ID's are as follows: (image 4).
Jamizzle93 said:
Just to catch everyone up, following on from advice and images above I uninstalled the driver I had installed in this image (image 1).
I am now trying to reinstall a driver which will hopefully work and not give me a <waiting for device> message when trying to unlock the bootloader.
These files in Android Tools still don't seem to want to work, I am getting the following messages below: (images 2 and 3).
Also my hardware ID's are as follows: (image 4).
Click to expand...
Click to collapse
Image 2, seems like you don't point to driver folder as it read:
C:\Users\James\Downloads\Android Tools
It should read: C:\Users\James\Downloads\Android Tools\HTC Driver\Driver Files\XP_x86
I have finally got it to work, after ages of trying a number of different drivers I have found something which eventually returned a result. I now have my identifier token.
Jamizzle93 said:
I have finally got it to work, after ages of trying a number of different drivers I have found something which eventually returned a result. I now have my identifier token.
Click to expand...
Click to collapse
Good to know you got it working.... so case closed
Edit your title to (Solved).
Jamizzle93 said:
I have finally got it to work, after ages of trying a number of different drivers I have found something which eventually returned a result. I now have my identifier token.
Click to expand...
Click to collapse
I am also facing the same problem, how did you solve the problem? Plz help
bootloader issue
biecp008 said:
I am also facing the same problem, how did you solve the problem? Plz help
Click to expand...
Click to collapse
Just follow this guide. Everything is explained in the post itself
http://forum.xda-developers.com/showthread.php?t=1598964
[email protected] said:
Just follow this guide. Everything is explained in the post itself
http://www.forum.xda-developers.com/showthread.php?t=1598964
Click to expand...
Click to collapse
FTFY
Sent from my HTC One V using xda app-developers app
Uninstalled htc sync manager & drivers, solved the problem.
I installed htc sync and drivers , was still stuck at waiting for device , uninstalled htc sync - still stuck right there any ideas ?? i got windows 8.1 , is that the problem by any chance ??
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.
Hi Guys
Ive installed Cyanogen 10.1 on m HTC One X all went fine no issues with install etc. However since I have installed im unable to get my PC to identify my htc one x for an ADB connection. I have updated all software from SDK Manager its no longer asking for downloads however the device is never found by ADB. I used the all in one toolkit to root and install the rom but this is now coming up with the same error. I have read that some phone need an edited driver once updated to cyanogen 10.1 does anyone have the modified inf file for the one X all i can find is one for the Samsung which doesnt work I already give it a shot .
Any help appriciated as i spend a good few hours trying to work this one out last night.
You have to enable USB debugging and allow ADB in developer options... Both are by default disabled on CyanogenMod
desmond1303 said:
You have to enable USB debugging and allow ADB in developer options... Both are by default disabled on CyanogenMod
Click to expand...
Click to collapse
Hi Mate
Thanks for the responce sorry should have said I have already enabled Developer Options within Cyanogen and have enabled usb debugging and the new one required for 4.2 which is ADB over network but ADB still still error no device found. Its seem to be something to do with the driver as I originally used the HTC drivers to flash and now I have a generic rom i.e. not one configured by HTC the PC doesnt appear to correctly identify the device. I have reinstalled the drivers a numbr of times and have also tried using the Google driver but my PC states this is not correct for the device and refuses to install it.
Well... I have the stock HTC drivers and they work for every single rom I have tried yet, weather AOSP or Sense...
Have you tired a different PC ?
You given adb root access in dev options?
Sent from my HTC One X using xda app-developers app
treebill said:
You given adb root access in dev options?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi Mate
Thought I had enabled all the options but possibly found the issue. I had enabled USB debugging and ADB over network but hadnt amended the root access to have apps and ADB enabled. Im in work at the mo so cant test but will def check this out as soon as I get in later. Hopefully that will sort it thanks for the assist guys will report back later to cofnirm either way.
Hi Guys
Sorry same issue I have enabled the root access for ADB aswell as apps now my PC is identifying the phone have tried adb when phone installed as My HTC and also installed with HTC Android Interface however adb still isnt detecting my phone when connected. Any Ideas would be great
does fastboot work ?
if you type in fastboot devices wile in fastboot usb mode, what does it say ?
desmond1303 said:
does fastboot work ?
if you type in fastboot devices wile in fastboot usb mode, what does it say ?
Click to expand...
Click to collapse
Yeah seems ok shows
Phone Name Fastboot
Im sure its a driver thing as ive been installing drivers manually and now i can get the phone to read in adb but it errors as offline like
Phone Name offline
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
crazyg0od33 said:
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
Click to expand...
Click to collapse
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
andybones said:
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
Click to expand...
Click to collapse
So just install and plug my phone in and the drivers will be installed?
Sent from my HTC6500LVW using Tapatalk 4
EDIT - that didnt do anything
Looks like I need to try something else...
crazyg0od33 said:
EDIT - that didnt do anything
Looks like I need to try something else...
Click to expand...
Click to collapse
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
andybones said:
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
Click to expand...
Click to collapse
My BMP is the same but my HTC Driver Installer is 4.0.3.001
Maybe I can find that other one and it will work for me
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
eL_777 said:
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
-snip-
-eL
Click to expand...
Click to collapse
Yeah I'm going to try it out on my roommates laptop that only has samsung drivers and the ADB installed and see what happens. Can't reformat the PC cause it's my School desktop and I've got work on there.
Once my macbook pro comes back from repairs I'll use that though, since I've never had issues running adb commands on my mac
Found a soultion
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
gald said:
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
Click to expand...
Click to collapse
MPT USB Drive isnt one of my options
However I've found that it's microsofts USB3 drivers, which override the Intel ones.
I just got my macbook back from repairs and it has USB3 ports as well so I was worried it wouldnt work, but its working fine from there
I'm having this same problem and nothing I do is working. I even tried from another computer but had no luck. adb finds the phone fine but fastboot just won't work. This is keeping me from getting S-Off. Someone please help.
Edit: Nevermind I think the issue is that I'm using Windows 8.1
I'm having the same problem I'm windows 8 64bit...
I have a nagging feeling that it's pda net.. I need to look into it today sometime
Sent from my HTC6500LVW using xda app-developers app
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