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
Related
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.
Hi,
I try to flash my OP3.
I did first the UNLOCK, that worked with the CMD (Running Windows 10).
My device is Unlocked.
But when I wanna try fastboot flash recovery recovery.img
Or I type then it says waiting for device...
and when i typ: fastboot devices
then if gives nothing.
Yes, I did the OEM unlock in developers options en USB debugging is on.
HELP!
HELP!
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
peterk-1 said:
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
Click to expand...
Click to collapse
Yes, I did that.
But not working...
Over WiFi it's working, but not with USB.
Oke, ADB is working, but only when the device in ON.
When I does the device in Fastboot.
Than it doesn't work!
HELP!
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
YourTheBest said:
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
Click to expand...
Click to collapse
I'm also stuck with this, could briefly tell me how you set up a VM with window's 7 please? I tried with Ubuntu but no luck installing the adb and fastboot? Stuck with no recovery so please help
First Tick OEM unlock and enable usb debugging. And install latest driver
Ajshal said:
First Tick OEM unlock and enable usb debugging. And install latest driver
Click to expand...
Click to collapse
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
How did you install the driver? do you have windows 8 or above?
daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
I have same pblm on my LG K10 dude
therightperson_630 said:
How did you install the driver? do you have windows 8 or above?
Click to expand...
Click to collapse
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
daviss101 said:
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
Click to expand...
Click to collapse
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
therightperson_630 said:
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
Click to expand...
Click to collapse
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
daviss101 said:
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
Click to expand...
Click to collapse
go to device manager and manually uninstall kedacom driver and install minimal adb/fastboot from the link I posted, they'll install the driver automatically
daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
YourTheBest said:
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
Click to expand...
Click to collapse
How do I get a free version of windows 7 without downloading a cracked ISO?
I had previously rooted my OP3, but accidentally updated it with the OTA open beta update, losing twrp recovery. I'm finding it incredibly difficult to flash twrp again to reroot.
The bootloader is still unlocked, and USB debugging is on with OEM unlocked, but I keep getting FAILED messages when I attempt to flash. "fastboot devices" shows the device (as a series of numbers).
I've tried using the OnePlus3&[email protected]_radaideh, but when attempting to flash it shows the below and then fails:
error: no devices/emulators found
I couldn't get it to work on my computer at home (win10) and read about problems with the OP3 drivers being unsigned (even with driver enforcement off). I'm also struggling on win7 - for some reason, the driver is listed in the Device Manager under the hardware group TP-LINK Android Phone and I can't get it to work using the OnePlus Android Bootloader Interface (under OnePlus, Inc.) or the Android Bootloader Interface (under Google, Inc.).
Could anyone suggest anything I should try?
Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.
emuandco said:
Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.
Click to expand...
Click to collapse
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above
justmast said:
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above
Click to expand...
Click to collapse
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.
emuandco said:
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.
Click to expand...
Click to collapse
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though
justmast said:
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though
Click to expand...
Click to collapse
Yep I was here aswell. Boot into driver signature mode and install the proper drivers. If you connect your device you can change the drivers. I don't have a PC next to me so I can't give you exact steps. The unbrick tool has the proper drivers, just follow the first few steps of that instruction to get it to show up as Qualcomm or something else as long as it isn't Kedacom.
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
windows 11 is still on its embryonic stage expect some bugs and compatibility issue, try reinstalling all drivers of your poco f3 but before that, you need to disable driver signature enforcement before reinstalling drivers search on google on how to disable this matter
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
i am currently running on win 10, nebrassy and vasishath twrp build no issue about fastboot, maybe you should try to downgrade your pc
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Phat Phreddy said:
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
Click to expand...
Click to collapse
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
mlcattini said:
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Click to expand...
Click to collapse
But I said its working on ADB..
RollDload said:
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
Click to expand...
Click to collapse
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Phat Phreddy said:
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Click to expand...
Click to collapse
you could try, however miflash doesn't need installation you just need to unzip it. you can also try to change USB port better if rear and 2.0
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Phat Phreddy said:
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Click to expand...
Click to collapse
then it was definitely a problem in the driver.