Related
My oneplus 3 isn't found in com/ports on windowsill 10. It's unable to load recovery and won't boot to system. Fastbook still works and has a unlocked boot loader. Trying to install stock firmware to restore the device for se again. Any help would be greatly appreciated.
Try loading drivers, have no issues here. Also run cmd prompt by right clicking on cmd.exe and selecting "Run As Administrator"
Sent from my SM-N930T using Tapatalk
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Also make sure USB debugging is enabled in the developers settings and you have the correct USB mode enabled (not charging)
Sent from my SM-N930T using Tapatalk
jaydubya24 said:
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Click to expand...
Click to collapse
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Will_Xda said:
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Click to expand...
Click to collapse
here is the device manager
setup driver and try in twrp
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
jaydubya24 said:
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
Click to expand...
Click to collapse
One more thing. Connect the phone to a USB 2.0 port and not a 3.0 port. It may not be recognised in a 3.0 port.
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what I found on USBDeview. There are two other versions of the OP3 on this list. But they do not show as being connected while the phone is in Fastboot. Im unable to access the OS to enable anything that may help with it being seen on my computer.
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Win7 works and i dont tryed the nice tip on site2.
i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
update on the op3
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what shows up after the one plus boot logo appears.
I had similar problem. I was rooting my 1+3. I went to device control settings in WIN 10 and removed 1+3 drivers. Next time when i was in fastboot mode windows installed drivers. :highfive:
I used the ones that came with 1+3
jaydubya24 said:
This is what shows up after the one plus boot logo appears.
Click to expand...
Click to collapse
I think this thread will supply the solution. "your" problem is at this post https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/page-4#post-15169580
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.
I can't seem to get my OP3 connView attachment 3920805View attachment 3920806ected to my Windows 10 Home 64bit laptop. This is really annoying. Already installed Oneplus 3 drivers, Windows 10 Media Feature Pack drivers. There is no connection prompt below status bar*as you get when you get when you connect your phone to PC (charging mode, MTP or PTP those kind). Device Manager in Windows 10 don't show any "unknown devices" or "Oneplus 3" or "MTP device". Already tried the "disable verification signature" at windows 10 boot options. Still nothing. Please help. This is going nuts.
Sent from my ONEPLUS A3000 using Tapatalk
Same problem but I can't get it to see the phone in fastboot. Getting sick of trying
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
gavin-phelan said:
Same problem but I can't get it to see the phone in fastboot. Getting sick of trying
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
But you can at least transfer files between PC and phone?
Sent from my ONEPLUS A3000 using Tapatalk
I'm using Windows 10 x64, and I can connect without any problem.
When I connect the USB cable, I see a prompt in the notification area (notification.png) showing USB for charging. Touch for more options..
I select the notification, and I am given several choices (Use USB for choices.png):
Charging
File transfers
Photo transfer (PTP)
MIDI
I select File transfers, and then am able to see the contents of my OnePlus 3 from within Windows 10.
Are you not getting this notification from your OnePlus 3?
ronniepoe said:
I'm using Windows 10 x64, and I can connect without any problem.
When I connect the USB cable, I see a prompt in the notification area (notification.png) showing USB for charging. Touch for more options..
I select the notification, and I am given several choices (Use USB for choices.png):
Charging
File transfers
Photo transfer (PTP)
MIDI
I select File transfers, and then am able to see the contents of my OnePlus 3 from within Windows 10.
Are you not getting this notification from your OnePlus 3?
Click to expand...
Click to collapse
I don't have the USB notification prompt as explained above. It really sucks. I am on Oxygen 3.2.7. what version are yours at?
Sent from my ONEPLUS A3000 using Tapatalk
bmdhj said:
I don't have the USB notification prompt as explained above. It really sucks. I am on Oxygen 3.2.7. what version are yours at?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Mine is also at OxygenOS 3.2.7
ronniepoe said:
Mine is also at OxygenOS 3.2.7
Click to expand...
Click to collapse
I just bought it yesterday. $400usd gone like that. Really crap. Bump. anyone please help.
Sent from my ONEPLUS A3000 using Tapatalk
Have you tried doing a factory reset?
@everyone
If the phone is completely not detected and no notification, try enabling USB Debugging.
For the ones not seeing the phone in fastboot, look in device manager for Kedacom USB Driver, maybe under firmware. Right click, update, manually select driver, there should be a OnePlus option or at least Android. It'll work then. Windows automatically installs this stupid Kedacom driver for the OP3, don't know why.
z3nith66 said:
@everyone
If the phone is completely not detected and no notification, try enabling USB Debugging.
For the ones not seeing the phone in fastboot, look in device manager for Kedacom USB Driver, maybe under firmware. Right click, update, manually select driver, there should be a OnePlus option or at least Android. It'll work then. Windows automatically installs this stupid Kedacom driver for the OP3, don't know why.
Click to expand...
Click to collapse
Still no notification after debugging mode enabled. I tried fastboot too, no "kedacom driver" in device manager. May I know where is the kedacom driver normally placed at? Under unknown devices or just separate own tab of device manager? Any other solutions? Please help.
Sent from my ONEPLUS A3000 using Tapatalk
bmdhj said:
I can't seem to get my OP3 connView attachment 3920805View attachment 3920806ected to my Windows 10 Home 64bit laptop. This is really annoying. Already installed Oneplus 3 drivers, Windows 10 Media Feature Pack drivers. There is no connection prompt below status bar*as you get when you get when you connect your phone to PC (charging mode, MTP or PTP those kind). Device Manager in Windows 10 don't show any "unknown devices" or "Oneplus 3" or "MTP device". Already tried the "disable verification signature" at windows 10 boot options. Still nothing. Please help. This is going nuts.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
The phone is detected and is the last entry ("Universal Serial Bus devices") on your device manager screenshot. Expand that and see what it shows. Unplug your phone from computer and that entry should disappear.
z3nith66 said:
@everyone
If the phone is completely not detected and no notification, try enabling USB Debugging.
For the ones not seeing the phone in fastboot, look in device manager for Kedacom USB Driver, maybe under firmware. Right click, update, manually select driver, there should be a OnePlus option or at least Android. It'll work then. Windows automatically installs this stupid Kedacom driver for the OP3, don't know why.
Click to expand...
Click to collapse
OMG, this should be stickied. I was on this for three hours trying to figure out why fastboot wouldn't respond. ADB would recognize but fastboot wouldn't. Windows must have updated the driver recently because it worked a few days ago.
z3nith66 said:
@everyone
If the phone is completely not detected and no notification, try enabling USB Debugging.
For the ones not seeing the phone in fastboot, look in device manager for Kedacom USB Driver, maybe under firmware. Right click, update, manually select driver, there should be a OnePlus option or at least Android. It'll work then. Windows automatically installs this stupid Kedacom driver for the OP3, don't know why.
Click to expand...
Click to collapse
Thanks! I just got my OP3 and was trying to do some fastboot commands and was beating my head against the desk!! Low and behold the Kedacom USB Driver!!
Hi all,
I can't get my 5X to be detected on any PC I connect it to. I've tried on two computers, both with Google drivers installed and with different cables and it doesn't show up in device manager or ADB. I'm running out of ideas and any help is appreciated.
Thanks
hutchpe said:
Hi all,
I can't get my 5X to be detected on any PC I connect it to. I've tried on two computers, both with Google drivers installed and with different cables and it doesn't show up in device manager or ADB. I'm running out of ideas and any help is appreciated.
Thanks
Click to expand...
Click to collapse
is there any device with a question- or exclamation mark in the device manager? when connected, is your device shown as "ADB generic" or similar in device manager?
in both scenarios you'd have to install another driver.
Hi.
Had a similar issue. I just uninstalled the driver in device manager and it got recognized.
Think it was som sort of Kedacom driver.
Thanks
KnieveI
ulxerker said:
is there any device with a question- or exclamation mark in the device manager? when connected, is your device shown as "ADB generic" or similar in device manager?
in both scenarios you'd have to install another driver.
Click to expand...
Click to collapse
No unfortunately it's not even seen as an unrecognized device.
KnieveI said:
Hi.
Had a similar issue. I just uninstalled the driver in device manager and it got recognized.
Think it was som sort of Kedacom driver.
Thanks
KnieveI
Click to expand...
Click to collapse
I tried that earlier with no luck.
I was able to borrow a friend's known working Nexus 5X and plugged it into my PC and it was detected just fine. Swapped my 5X in using the same cable and USB port and nothing. I'm beginning to suspect a hardware issue.
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Monfro said:
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Click to expand...
Click to collapse
I've googled it. Tried many. Event tried to boot Windows without driver signature. Didn't work. :/
michie said:
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Click to expand...
Click to collapse
Oh sorry.
Does someone have an idea?
This might come a year too late, but in case someone else runs into the same problem (like myself), you can solve it by installing the latest (signed) ADB drivers with this Tool, then rebooting the tablet to fastboot mode and run the tool again. This still doesn't install the correct fastboot drivers, but it should now be listed as "ADB Interface" -> "Unknown Device" in the device manager, and if you right click and choose "Update driver" -> "Browse my computer for driver software", you should see a driver called "Fastboot interface (Google USB ID)", that installs and works correctly for the Pixel C.
@Mambobuzzz
One option you have and it's been updated this month too, is you could try installing and using tiny adb & fastboot from here: https://forum.xda-developers.com/t/tool-windows-tiny-adb-fastboot-august-2021.3944288/
I can't stand Windows for a few reasons! Make a live USB and try a Linux distro! You will never have this problem again and I guarantee you won't miss Windows.
Edit added:
Reasons why this is happening:
Bad connection somewhere.. The USB connection you are plugging in to on your PC could be messed up, the USB cord could be messed up, or where your type c plugs in to your device is messed up.... Oooorrrrr it's driver issue. And knowing Windows I betcha it's a driver issue. When you plug your tablet in are you enabling USB debugging and developer options and changing the "default USB configuration" from "Charging" to "File tansfer ?" And when you do those things are you watching the table REALLY CLOSELY for the little box that pops up for 5 seconds that you MUST put a checkmark in otherwise adb and fastboot will not work? Reboot a few times on your PC and update the drivers in Windows Device manager.. I remember once I had to reboot 3-4 times to finally get mine working. When you type adb --version then push enter in terminal and fastboot --version push enter what does it say?