Related
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
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.
First, bit of background: I am not an Android developer or even a computer geek in any way but I can follow precise instructions to a positive result. I have for instance had in the past the following devices and managed to root every single one of them sometimes in 10 minutes, sometimes with a lot more difficulty: B&N Nook, Samsung Galaxy SII, Nexus 5, Nexus 7, Nexus 9, Sony Xperia Z3 Compact, Chuwi Hi10 Pro.
Now, I have just purchased a Pixel C and I have been tearing my hair out for the best part of 48 hours just trying to install the Google USB driver and fastboot bootloader driver on it. I previously had my Windows 10 PC set up with working ADB and fastboot (sdk tools only, no Android Strudio). As proof, I recently rooted my Nexus 9 on it. With the Pixel C I tried:
-Nexus root toolkit and every single method of driver installation possible
-I then downloaded Android studio - didn't change a thing
-I then try to unlock the bootloader the manual way (command prompt inside of platform-tools - fail since the driver won't install.)
-I even wiped out my Windows install and reinstalled it fresh with Android Strudio
- I do get the device seen as an mtp device
-I do get adb function (I can reboot the device to bootloader)
-Yes I did enable usb debug and 'oem bootloader unlock'
-when I try to install te Google driver to the tablet as mtp device in Device Manager I get the message "the best driver is already installed" (no matter what Google usb driver I use, the one downloaded by Android Studio or the one I downloaded separately)
-I have also always disabled driver signature enforcement in Windows before trying to update the driver.
I am extremely puzzled and feeling defeated. If someone can tell me of something that passed me by, please tell me. If the Pixel C can be rooted on a Windows 10 PC, please tell me something I don't know...
Please note: I made the possibly mistake of letting the Pixel C update to 7.1.2 before doing anything.
Please Help!
This may or may not be a helpful response. I had the same problem and never, ever solved it. I read a gazillion articles and all sorts of detailed instructions about how to remove and update drivers. I tried for days and nothing ever worked. That's not to say that it can't be done, but I had to give up.
Do you have access to a Windows 7 computer? That will get you through the unlocking process and initial installation of TWRP. After that you won't need your PC for anything except transferring files so the drivers won't be a big issue.
badwiring said:
This may or may not be a helpful response. I had the same problem and never, ever solved it. I read a gazillion articles and all sorts of detailed instructions about how to remove and update drivers. I tried for days and nothing ever worked. That's not to say that it can't be done, but I had to give up.
Do you have access to a Windows 7 computer? That will get you through the unlocking process and initial installation of TWRP. After that you won't need your PC for anything except transferring files so the drivers won't be a big issue.
Click to expand...
Click to collapse
Thanks, so it would be a problem with Windows 10? And you manage to solve it with Win7?
I don't have a Windows 7 PC but I tried to run a Win7 virtual machine, and it can't recognise the tablet as an mtp device. So, fail.
I can't believe we're the only 2 who've had that issue and that this is not generating more help and tips. Nevermind...
Try the skipsoft tool kit thread.
I am not an expert, but the thread offers many insights into this problem. I got the drivers installed properly after some thorough failure too. Keep at it. I did it successfully about 9 months ago - long enough for me to completely forget how I did it. The answer will be there.
nexus root toolkit by wugfresh supports pixel c. good info on drivers found there.
https://www.vichaunter.org/como-se-hace/instalar-controladores-no-firmados-windows-10
Enviado desde mi SM-N9005 mediante Tapatalk
kjwaugh said:
I am not an expert, but the thread offers many insights into this problem. I got the drivers installed properly after some thorough failure too. Keep at it. I did it successfully about 9 months ago - long enough for me to completely forget how I did it. The answer will be there.
Click to expand...
Click to collapse
Hi. Thanks. I have been reading about the issue across the Internet for 3 days now and keep seeing the same instructions which lead nowhere...
dkryder said:
nexus root toolkit by wugfresh supports pixel c. good info on drivers found there.
Click to expand...
Click to collapse
As said in the original post, I used (and always have) the Nexus root toolkit. I also tried every single driver installation method in it and out of it - several times each...
chinimen said:
https://www.vichaunter.org/como-se-hace/instalar-controladores-no-firmados-windows-10
Enviado desde mi SM-N9005 mediante Tapatalk
Click to expand...
Click to collapse
Thanks. Although my Spanish is no longer that good I believe it instructs how to disable driver signature in Windows. As I specified in my original post, I have done that.
fgaine said:
Thanks. Although my Spanish is no longer that good I believe it instructs how to disable driver signature in Windows. As I specified in my original post, I have done that.
Click to expand...
Click to collapse
Ok then you only have to install the drivers manually with the nexus root toolkit
Enviado desde mi SM-N9005 mediante Tapatalk
have you tried the legacy drivers install?
chinimen said:
Ok then you only have to install the drivers manually with the nexus root toolkit
Enviado desde mi SM-N9005 mediante Tapatalk
Click to expand...
Click to collapse
That's one of the very first things I did, mate If you have read my post. ,?
fgaine said:
That's one of the very first things I did, mate If you have read my post. ,[emoji16]
Click to expand...
Click to collapse
First you have to disable the use of unsigned drivers as indicated and then install the drivers manually from nexus root toolkit. If you read your message and I did it in that order. a greeting
Enviado desde mi SM-N9005 mediante Tapatalk
kjwaugh said:
I am not an expert, but the thread offers many insights into this problem. I got the drivers installed properly after some thorough failure too. Keep at it. I did it successfully about 9 months ago - long enough for me to completely forget how I did it. The answer will be there.
Click to expand...
Click to collapse
Hi. I didn't know about the Skipsdoft toolkit. Sounds good, I will give that a go. :good:
dkryder said:
have you tried the legacy drivers install?
Click to expand...
Click to collapse
Is that using the NRT?..
chinimen said:
First you have to disable the use of unsigned drivers as indicated and then install the drivers manually from nexus root toolkit. If you read your message and I did it in that order. a greeting
Enviado desde mi SM-N9005 mediante Tapatalk
Click to expand...
Click to collapse
Thanks again. But that's what I did. Didn't work...
I always have this problem, and it always comes down to me forgetting that the device needs a different driver in ADB mode than it does in fastboot mode. Or, at least, it needs the driver installed in each mode. If you haven't already, make sure you get it working in ADB, then go through the steps again while the device is in fastboot mode. Maybe you've already made sure of that, but the last time I needed to do it, after hours of pulling out my hair, I realized that I wasn't doing all the steps of removing drivers and then installing the correct ones while the Pixel was in fastboot.
when using device manager , left click on action then select add legacy hardware, then next, then install hardware i manually select from a list, then next, hopefully android device is at top of list, if not look for any adb/fastboot , like portable device but the point is to find a adb/fastboot early legacy device and select that, then next, then select the driver from the list and hit next. should be done.
let me ask you when you installed android studio, did you go to sdk manager and select usb drivers then install. then go to users/username/appdata/local/android/sdk/extras/google/usb_driver and right click .inf file and select install and let windows install the driver(s)?
dkryder said:
when using device manager , left click on action then select add legacy hardware, then next, then install hardware i manually select from a list, then next, hopefully android device is at top of list, if not look for any adb/fastboot , like portable device but the point is to find a adb/fastboot early legacy device and select that, then next, then select the driver from the list and hit next. should be done.
let me ask you when you installed android studio, did you go to sdk manager and select usb drivers then install. then go to users/username/appdata/local/android/sdk/extras/google/usb_driver and right click .inf file and select install and let windows install the driver(s)?
Click to expand...
Click to collapse
Hi. Yes I did but it keeps saying there are no suitable drivers in the folder. When I check myself there is indeed no .inf file in it.
I have had no luck. Using both the skipsoft and the wugfresh tool.
My pixel c is locked asking for a pin and I never put a pin lock into it. What a piece of $h!t this tablet has been.
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Anyone?
no one?
bigd19888 said:
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Click to expand...
Click to collapse
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have minimal adb and fastboot installed
device is h811 20v
bootloader is already unlocked
and yes I'm using LGMobileDriver_WHQL_Ver_4.2.0
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
RuedasLocas said:
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
Click to expand...
Click to collapse
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
Don't allow Windows 10 to update your drivers - you can set that up in Windows. Google it for the how-to.
bigd19888 said:
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
Click to expand...
Click to collapse
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
RuedasLocas said:
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
Click to expand...
Click to collapse
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Your device should be seen as "LGE Android Phone" (if your lg drivers are good).
Now gonna be tricky because my OS is in Portuguese, I don''t know exactly the path name in English... use your imagination
Connect the device on a USB 2 Port !!!
In windows device manager, select "update driver", "search software on the computer", "allow to choose from a list of avalable drivers". unmark the "compatible hardware" and find on the list the needed drivers. If the "LGE" drivers don't work, try to download Universal ADB Drivers, maybe it works.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
I'm thinking it could be a corrupted LG driver. Download another from the LG US site, ONLY. Uninstall the one you have installed now, reboot and install the newly downloaded one. Then connect your phone and see if it is recognized and shown correctly in Windows Device Manager. Also, in adb type lsusb and see if the phone is listed in the output.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Boss, no need to struggle with this ADB anymore.. there is a tool called FWUL which was created for people who have driver issues... Check it out here:
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
:good:
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.