I was trying to flash the factory images on the Nexus 5x through fastboot. When I kept typing fastboot devices the computer would not recognize the phone so I couldn't flash the images, however; when I go to TWRP it recognizes the phone. When I type fastboot devices it keeps saying "Waiting for device"
I'm using minimal ADB, not full SDK
yesterday i having the same issue .... when i flash last stock 7.1.1 and after that i return on PixelRom But my computer won't recognize my device normally and in fastboot mod
i have try to change bootloader , radio , vendor but same issue after download direclty on my device
i have read to change cable i have try another cable but same issue i have reinstalled 15 sec adb & fastboot and drivers and i retake my cable that I usually use and wow it's work now ......... how ?? why ?? i don't know
good luck
Renaf2 said:
yesterday i having the same issue .... when i flash last stock 7.1.1 and after that i return on PixelRom But my computer won't recognize my device normally and in fastboot mod
i have try to change bootloader , radio , vendor but same issue after download direclty on my device
i have read to change cable i have try another cable but same issue i have reinstalled 15 sec adb & fastboot and drivers and i retake my cable that I usually use and wow it's work now ......... how ?? why ?? i don't know
good luck
Click to expand...
Click to collapse
I'm not sure what the issue is but I have a feeling it has to do with Nougat. I just tried doing a bunch of the standard stuff and it's not working. I plugged in my old Nexus 6, everything is working no problem fastboot and adb. I have a feeling Google made some type of changes and possibly the fastboot/adb program that I am using is not compatible with whatever change Google has apparently made as of recent.
It's not my program since it is working fine on Marshmallow for the Nexus 6........so it makes me think that it's Nougat......I updated the LG driver which I initially thought it was and it shows no errors as well.
mikeprius said:
I was trying to flash the factory images on the Nexus 5x through fastboot. When I kept typing fastboot devices the computer would not recognize the phone so I couldn't flash the images, however; when I go to TWRP it recognizes the phone. When I type fastboot devices it keeps saying "Waiting for device"
I'm using minimal ADB, not full SDK
Click to expand...
Click to collapse
What OS do you have on your PC?
Inviato dal mio Nexus 5X utilizzando Tapatalk
i don't know if it's Nougat or not it's my first time with this issue ......... Yet it's been a while since I flash Nougat version without this issue ( and perhaps i can flash 5 Roms on one Day ) (I'm a crazy flasher XD ) .....
For me i'm on Windows ssshhiiittttyyy 10 drivers signed desactivated with settings on boot
sobe00 said:
What OS do you have on your PC?
Inviato dal mio Nexus 5X utilizzando Tapatalk
Click to expand...
Click to collapse
I have windows 7.
I'm using another laptop with Windows 7 as well, but it is currently working. The only difference between the 2 is that one is almost 5 years newer (working one) than the non-working one. Still works fine with Marshmallow Nexus 6, just not with this one right now.
Are the bootloader drivers installed? Look in the device manager.
mikeprius said:
I have windows 7.
Click to expand...
Click to collapse
Maybe you need to set fastboot driver manually in Device Management . Sorry for my not good English.
Inviato dal mio Nexus 5X utilizzando Tapatalk
sobe00 said:
Maybe you need to set fastboot driver manually in Device Management . Sorry for my not good English.
Inviato dal mio Nexus 5X utilizzando Tapatalk
Click to expand...
Click to collapse
How do you do this ? I tried setting up LG Mobile drivers for the Nexus 5x. The computer was scanning and auto found the adb driver, I still can't figure out what I am missing.
mikeprius said:
How do you do this ? I tried setting up LG Mobile drivers for the Nexus 5x. The computer was scanning and auto found the adb driver, I still can't figure out what I am missing.
Click to expand...
Click to collapse
in fastboot, hook your phone up to your computer. than go to your device manager and find your device, double click on it. right click on the second one that pops up and select update driver, select browse computer, than select pick from a list of drivers and manually install the driver for fastboot mode...hope this helps.
dominoeflux said:
in fastboot, hook your phone up to your computer. than go to your device manager and find your device, double click on it. right click on the second one that pops up and select update driver, select browse computer, than select pick from a list of drivers and manually install the driver for fastboot mode...hope this helps.
Click to expand...
Click to collapse
Huge thanks for your advice. Got the phone up and running. Fastboot now running. What you described was what was needed. :highfive: :highfive:
mikeprius said:
Huge thanks for your advice. Got the phone up and running. Fastboot now running. What you described was what was needed. :highfive: :highfive:
Click to expand...
Click to collapse
Your welcome bro and anytime. This was exactly what happened to me at one point until I figured out what the problem was. Good you get the phone up and running ?
mikeprius said:
How do you do this ? I tried setting up LG Mobile drivers for the Nexus 5x. The computer was scanning and auto found the adb driver, I still can't figure out what I am missing.
Click to expand...
Click to collapse
Plug your device in fastboot mode in your PC and open Windows's Devices Manager, now you should find your phone under "other devices" as "Android phone" or "android Devices" or something like that, right-click it and select "update driver softwere", then select "Browse my computer for driver software" and select "Let me pick from a list of device drivers on my computer" , now you should see in the menu a thing as "android bootloader interface", select it and then click next. Now you should be able to use your device in fastboot mode. Sorry if I answer only now, but this weekend I was aut for work.
Related
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
The issue I was having was due to the fact that I wasnt pressing Volume Up+Volume Down+Power, so I wasnt even in fastbook, but a screen similar to it
schwartzman93 said:
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
Click to expand...
Click to collapse
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
efrant said:
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
Click to expand...
Click to collapse
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
schwartzman93 said:
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
Click to expand...
Click to collapse
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
FastBoot Driver- Xperia Neo
efrant said:
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi,
I am using sony sricsson neo .587. I tried to connect my phone in fastboot mode. I connected in fastboot mode. I am not able to install drivers for that.
Steps I Followed
1. I updated google usb driver
2. Replaced "android_winusb.inf" file which is provided by Sony official
3. Connected phone in fastboot mode
4. It asked for drivers
5. I selected usb driver folder to install drivers
But It fails...
I am doing these all things on Windows 7 64 bit
Please help...
::EDIT::
OK Problem Solved. Thanks to PKelly517 for pointing me in the right direction.
So I'm on Windows 10 and had all drivers updated. Device Manager showed Pixel C under portable devices and ADB worked BUT when in Fastboot mode it would not recognize the Pixel C and under Device Manager it showed up as Unknown Device. Trying to install drivers resulted in an error stating "The Third-Party INF Does Not Contain Digital Signature Information."
This is the steps I took to get Fastboot working.
1. Hold Shift and Restart PC.
2. In the following screen: Went to Advance Options > Startup Settings > Restart.
3. Upon restarting, chose the options "Disable Driver Signature Enforcement."
4. Reinstall drivers under Device Manager while in Fastboot mode.
Fastboot mode is recognized after that. Hopefully this could help anybody else having similar issues.
______________________________________________________________________________________________
I'm running on Android 7.0.0 NRD90R and I've searched this entire forum on ADB/Fastboot problems not working on the Pixel C and none of the threads seem to solve my problem. I can see my device in ADB but when I go into Fastboot mode the device is no longer recognized and commands cannot be issued.
I have installed all the updated drivers, the Pixel C comes up under Portable Devices in Device Manager, and when I use the Nexus Root Toolkit 2.1.9 to unlock the bootloader it gives me this:
adb devices
5C08000604 device
fastboot devices
Checking OEM Unlockable Status:
+ Status: Allowed
Checking ADB/FASTBOOT Connectivity
adb devices
5C08000604 device
fastboot devices
+ ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
Retrying.. Checking Fastboot Connectivity
fastboot devices
I've tried using SkipSoft Drivers and that too, doesn't recognize my device in Fastboot mode. Any help would be appreciated. I've spent hours trying to get Fastboot working and I've just about had it with this damn device.
@chob0,
Is your Android SDK up to date?
cam30era said:
@chob0,
Is your Android SDK up to date?
Click to expand...
Click to collapse
Yes, I've installed all the updated drivers including the Android SDK but still not recognized in Fastboot.
chob0 said:
Yes, I've installed all the updated drivers including the Android SDK but still not recognized in Fastboot.
Click to expand...
Click to collapse
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
cam30era said:
@chob0,
Is your Android SDK up to date?
Click to expand...
Click to collapse
pkelly517 said:
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
WOW THANK YOU SO MUCH! I can't believe it was something so simple. I checked device manager before and it had shown up as Pixel C but never while I was in Fastboot mode.
chob0 said:
WOW THANK YOU SO MUCH! I can't believe it was something so simple. I checked device manager before and it had shown up as Pixel C but never while I was in Fastboot mode.
Click to expand...
Click to collapse
Glad I could help.
The fact that it was JUST the Pixel C ONLY in fastboot was the weird part.
I think I spent more time trying to understand how to update the driver than I did discovering the problem. It looks like it was the opposite for you. Enjoy the weekend.
Sent from my Pixel C using Tapatalk
You saved me a lot of stress trying to figure this out. Thanks.
pkelly517 said:
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
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.
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.
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