Hey everyone,
So I got my Mi Mix 3 yesterday and I wanted to unlock the bootloader. ( for obvious reasons )
But I encountered a problem. I can't get the Mi Unlock Utility to detect my Mix 3, even though I can communicate with it via ADB
I think I have permission to unlock it, since I get to the unlocking screen
I'm thinking it might be a problem with the drivers.
Or maybe it is a problem with fastboot, because it doesn't show up when I type "fastboot devices"
And yes, I entered fastboot mode with power+volume down.
Did anyone else encounter this problem?
Thanks in advance.
No screenshots because I can't post links yet unfortunately.
Device: Xiaomi Mi Mix 3
MIUI: Miui 10.0 | Stable 10.0.12.0(PEECHFH)
Kernel: 4.9.112-perf-gba589af
Hardware: V1
on
Windows 10 x64 1803
Ryzen 5 1600
CaptainTimo said:
I'm thinking it might be a problem with the drivers.
Or maybe it is a problem with fastboot, because it doesn't show up when I type "fastboot devices"
And yes, I entered fastboot mode with power+volume down.
Click to expand...
Click to collapse
Update:
I installed the Google USB Drivers and Fastboot is working, only when I start the Utility my phone displays:
Code:
Press any key to shutdown
After that, I can't connect to it in fastboot until I fully restart my PC.
Did u activated USB debugging from developer option?
PeppeCNN said:
Did u activated USB debugging from developer option?
Click to expand...
Click to collapse
You don't need usb debugging for unlocking with fastboot
CaptainTimo said:
Update:
I installed the Google USB Drivers and Fastboot is working, only when I start the Utility my phone displays:
.
Click to expand...
Click to collapse
Turns out windows 10 doesn't like to unlock Xiaomi phones.
I used a pc with windows 7 and it worked. Now have to wait a few more hours before I can unlock.
I am having the same problem as you, any idea how to fix it without windows 7?
xstewminator said:
I am having the same problem as you, any idea how to fix it without windows 7?
Click to expand...
Click to collapse
You can also use Windows 8 or 8.1. But other than that I couldn't find any other solution.
Maybe you can try to setup dual-boot on your windows 10 machine, so you have windows 10 and 8.1 installed at the same time. And use the 8.1 for unlocking/flashing your Mix 3.
CaptainTimo said:
You can also use Windows 8 or 8.1. But other than that I couldn't find any other solution.
Maybe you can try to setup dual-boot on your windows 10 machine, so you have windows 10 and 8.1 installed at the same time. And use the 8.1 for unlocking/flashing your Mix 3.
Click to expand...
Click to collapse
Windows 10 - disable driver enforcement
Mackay53 said:
Windows 10 - disable driver enforcement
Click to expand...
Click to collapse
Didn't work for me
CaptainTimo said:
Didn't work for me
Click to expand...
Click to collapse
What steps did you do after booting into win10 from advanced boot options
Mackay53 said:
What steps did you do after booting into win10 from advanced boot options
Click to expand...
Click to collapse
I used a CMD command and rebooted my PC to disable driver enforcement.
But I already succeeded in unlocking and flashing the EU rom using a windows 8 PC.
Mackay53 said:
Windows 10 - disable driver enforcement
Click to expand...
Click to collapse
So I've tried that, for some reason it still has the same problem... I'm going to try to do it on a windows 8.1 machine, but I'm not very hopeful...
Also sometimes it gets to the point of recognizing the device, but then it says device is unlocked, but it actually isnt...
picture attached
xstewminator said:
So I've tried that, for some reason it still has the same problem... I'm going to try to do it on a windows 8.1 machine, but I'm not very hopeful...
Also sometimes it gets to the point of recognizing the device, but then it says device is unlocked, but it actually isnt...
picture attached
Click to expand...
Click to collapse
Have you bound the phone to your account via settings and enable OEM unlock from dev options?
Ok well, I got it to work on my windows 8.1 machine.
This does appear to be an issue with windows 10 in some way.
Now to wait 53 hours... RIP
xstewminator said:
Ok well, I got it to work on my windows 8.1 machine.
This does appear to be an issue with windows 10 in some way.
Now to wait 53 hours... RIP
Click to expand...
Click to collapse
With Windows 10 works...if was unlocked, what u have to wait 53 h? I didn't understood
What RIP?
PeppeCNN said:
With Windows 10 works...if was unlocked, what u have to wait 53 h? I didn't understood
What RIP?
Click to expand...
Click to collapse
You have to wait so many hours before you can unlock, usually 72 hours
Mackay53 said:
You have to wait so many hours before you can unlock, usually 72 hours
Click to expand...
Click to collapse
Maybe I misunderstood...he told before that was unlocked...or was someone else?
Inviato dal mio MIX 3 utilizzando Tapatalk
I also encountered some driver difficulties with Windows 7. My issue was a previously-installed Samsung driver which Windoze was using for the Xiaomi phone. If you have an old driver, Samsung or generic, you need to uninstall it first from the Windoze Add/Remove Programs screen. The Xiaomi driver, once installed, also seemed to cause some problems with other USB drivers, now when I boot it takes a couple of minutes before the keyboard and mouse start working, not a big deal, just another thing to add to the long list of intractable problems with my Windoze installation.
You probably were getting that error due to another running instance of adb server. Try running adb kill-server in admin command prompt, then open the Xiaomi utility.
Sent from my Mi MIX 3 using Tapatalk
Mackay53 said:
Windows 10 - disable driver enforcement
Click to expand...
Click to collapse
It failed for me. I have usb debugging on, OEM unlock is on...
I have correct drivers fastboot adb
not sure what else to do.
Any ideas? Or is windows 10 a lost cause?
Related
I have problem with my OPO.
I try to install TWRP 2.8.6.0 but after that my phone doesn't boot. Nothing work. I hold power button for 2 minutes and nothing.
I do everything like in this guide but it doesn't work. http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I connect my bricked phone and Windows see it "other devices- unknown device"
I done cmd commands, update driver, select Qualcomm 2012/widnows8/qcmdm/ QDLoader 9008 and after that I have error " Windows found driver software for your device but encountered an error while attempting to install it. This device cennot start(Code 10)"
And it is my problem. I stopped at point 2b in the Guide becouse I can't install drivers.
here is video of that. https://drive.google.com/open?id=0B9...G8tbnNES2VZWG8
Please fast help, becouse I really need this phone next weekend.
Please, can someone help me?
Rebeluch said:
Please, can someone help me?
Click to expand...
Click to collapse
when i bricked my oneplus one, i had similar issues. I had to reinstall windows in order to make it work.
hellcat50 said:
when i bricked my oneplus one, i had similar issues. I had to reinstall windows in order to make it work.
Click to expand...
Click to collapse
Do you pluged phone into USB port and computer can't see it?
Do you reinstalled system to Windows XP?
Rebeluch said:
Do you pluged phone into USB port and computer can't see it?
Do you reinstalled system to Windows XP?
Click to expand...
Click to collapse
I used windows 8.1
reinstalled windows 8.1 on a new partition
It's now a long time ago so i can't quite remember what problem exactly i had, but I know that it didn't worked and i reinstalled windows and it worked.
Actually one month after I bought my oneplus one i bricked it
have u tried disable windows driver signature enforcement? becoz after windows 7, driver that doesnt have digital signature are not installed unless u disable the enforcement
MrxSiN said:
have u tried disable windows driver signature enforcement? becoz after windows 7, driver that doesnt have digital signature are not installed unless u disable the enforcement
Click to expand...
Click to collapse
Yes, I do this in Advanced restart options and click F7. And windows still can't see phone.
I bricked my Oneplus One while flashing CM11 via fastboot using manual commands on cmd.
After giving all the commands for fastboot flash, during reboot the phone did not reboot and it just got bricked.
The big issue with the brick is that the phone is not being recognized as QHSUSB_BULK but it is showing as Unrecognised Device ... i am not able to update the drivers to qualcom 2012 the windows is giving an error as "Windows was unable to install your unknown device".
I've turned on the Testing Mode to install unsigned drivers and the gpedit policy to stop windows automatically installing drivers is also enabled. Also i've changed the setting in control panel Devices and printers -> Device Installation Settings to "Let me choose what to do "and "never install driver software from windows update".
Still the problem persists Please HELP Me.
praik96 said:
I bricked my Oneplus One while flashing CM11 via fastboot using manual commands on cmd.
After giving all the commands for fastboot flash, during reboot the phone did not reboot and it just got bricked.
The big issue with the brick is that the phone is not being recognized as QHSUSB_BULK but it is showing as Unrecognised Device ... i am not able to update the drivers to qualcom 2012 the windows is giving an error as "Windows was unable to install your unknown device".
I've turned on the Testing Mode to install unsigned drivers and the gpedit policy to stop windows automatically installing drivers is also enabled. Also i've changed the setting in control panel Devices and printers -> Device Installation Settings to "Let me choose what to do "and "never install driver software from windows update".
Still the problem persists Please HELP Me.
Click to expand...
Click to collapse
Okay,calm down!
Which windows are you using? Are you sure you're not able to boot to fastboot mode?
I'm using windows 8.1 64bit version.
Mr.Ak said:
Okay,calm down!
Which windows are you using? Are you sure you're not able to boot to fastboot mode?
Click to expand...
Click to collapse
When i press power button + vol. up for 10sec the windows recognizes the device but shows it as Unknown Device and then the Driver Update is not being done. What should i do?
praik96 said:
What should i do?
Click to expand...
Click to collapse
Did you even read my question?
Sent from my A0001 using Tapatalk
faced that too a while ago, try to use win 7 ( best is xp ) with driver signature thing off, now google hardbrick opo recovery and u will find a website with the steps along with a mi flaasher tool for windows , now download the color os hradbrick recovery zip and also the latest cos 13.1.2 fastboot zip.
U willl eb able to bring back ur opo to life by using that color os zip along with the mi flasher tool but then the screeen behaves really weird ( happened to me )
but everything got normal after i flashed the cos 13.1.2 zip by fastboot
Kartike said:
faced that too a while ago, try to use win 7 ( best is xp ) with driver signature thing off, now google hardbrick opo recovery and u will find a website with the steps along with a mi flaasher tool for windows , now download the color os hradbrick recovery zip and also the latest cos 13.1.2 fastboot zip.
U willl eb able to bring back ur opo to life by using that color os zip along with the mi flasher tool but then the screeen behaves really weird ( happened to me )
but everything got normal after i flashed the cos 13.1.2 zip by fastboot
Click to expand...
Click to collapse
That's why I was asking him about which windows he use.Windows XP is hassle free for this driver's issue.
Sent from my A0001 using Tapatalk
Mr.Ak said:
That's why I was asking him about which windows he use.Windows XP is hassle free for this driver's issue.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm using windows 8.1, earlier i mentioned it in the title.
praik96 said:
I'm using windows 8.1, earlier i mentioned it in the title.
Click to expand...
Click to collapse
find a Xp system and you'll not have any issues.
Sent from my A0001 using Tapatalk
Mr.Ak said:
find a Xp system and you'll not have any issues.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If i install xp on my laptop via dual boot and what drivers will i need other than Qualcom 2012 ? or the xp's inbuilt windows driver will do the trick along with Qualcom 2012 drivers?
praik96 said:
If i install xp on my laptop via dual boot and what drivers will i need other than Qualcom 2012 ? or the xp's inbuilt windows driver will do the trick along with Qualcom 2012 drivers?
Click to expand...
Click to collapse
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
You should download One Plus USB drivers.
If you prefer you should use One Plus Toolkit.
Mr.Ak said:
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Can anyone direct me to safest way to dual boot windows xp s3 on windows 8.1 already installed with UEFI mode?
I dont want to end up with screwing my laptop too.
praik96 said:
Can anyone direct me to safest way to dual boot windows xp s3 on windows 8.1 already installed with UEFI mode?
I dont want to end up with screwing my laptop too.
Click to expand...
Click to collapse
Youtube
Sent from my A0001 using Tapatalk
Mr.Ak said:
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Tip1: Use correct usb cable.
I thought the error was is usb drivers but it seems that the error was in usb cable. I lost my oneplus usb cable quite a while ago and was using third party usb cable for data transfer and charging. Tried to connect the bricked OPO with that cable only.
Just ought to try connected with different cable here used Amazon Basics micro usb cable and VOILA!!! The drivers were automatically installed by windows this time.It worked on current windows 8.1. Dont know it was luck or really dumb choice of USB cable.
But thank you very much for helping me out.
Hello
I need help with my TF700.
I had this tablet for some time. It was unlocked with TWRP and ZOMBI-POP.
Last week I wanted to upgrade it for KIT-Kass 7.1
I wanted to update my TWRP for kang wersion ( 2.8.7.4) through TWRP and during the process it rebooted.
Then I've got a bootloop on normal starting. I can't get into recovery mode through power + vol up - tablet has no respond for that
I can only go to fastboot through power + vol down but when I connect it to windows with adb drivers or to linux(FWUL) it sees no device and no respond for any command.
Do You have any idea what to do ?
Thank You in advance
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Nektopoli said:
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Click to expand...
Click to collapse
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Do you have access to a Windows 7 computer/laptop. There's an issue with Windows 10 and the fastboot drivers not working together, and causing a problem like yours. - NP
marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Found this in another thread, windows 10 fix. - NP
"I used Windows 10 and had to disable driver signature enforcement. Once I did this the PC recognized the tab without issue. "
To disable;
http://www.thewindowsclub.com/disable-driver-signature-enforcement-windows
Thank You for the info, but I have laptop with Windows7 and still the same.
But if I have text on screen like this Starting fastboot USB download protocol can the device still be hard-bricked ?
Maybe I am missing some drivers ?
I would d/l Minimal ADB and Fastboot from here;
https://forum.xda-developers.com/showthread.php?t=2317790
and Universal_Naked_Driver_0.72 here; - NP
https://forum.xda-developers.com/showthread.php?t=2263822
For now the problem is I can not install the "naked driver" because devices manager can not see TF700 when it is connected, so I can't update the driver
Have you tried sending the [fastboot reboot] command to see if the tablet will reboot. When I bricked my TF201t my laptop didn't see it but it still took the commands allowing me to wipe the recovery partition and install the correct TWRP. - NP
Dear Guys
I know that this topic is quite old, but I am still fighting with this problem.
I tryied different drivers, 3 different computers ( two with windows 10 one with windows 7) and I can;t connect to fastboot.
The tablet is in this mode, but when I will use adb and type any command like fastboot reboot - it displays "waiting for device"
Do You have any idea what else can I try ?
Best regards
Hi,
me too! I was using it at lunch - no problem. Got home and turned it on and unrecoverable bootloader error.
Hey Everyone!
Just got my Mi Mix 3 and the hardware is awesome, but I'm having trouble unlocking the bootloader through the mi unlock tool, I already have permissions from my account with my OG Mi Mix, but for some reason it will not detect the Mix 3. Sometimes it does detect the phone if I start Fastboot while plugged in and with the tool open on my windows 10 pc, but it cannot verify the phone, even though I have signed in on the phone through my Mi Account.
Any Ideas on what could be causing this? I saw another thread a coupe weeks ago with a similar issue, but the only way they got it working was with a win7 machine, of which I don't have.
I have all the proper drivers and utilities installed, but nothing is working, even tried it on a different windows 10 machine and still no avail.
Wondering if anyone else is having the same problem?
Thanks in advance for the help!
Try rebooting Windows (10).
cobben said:
Try rebooting Windows (10).
Click to expand...
Click to collapse
Yeah I did, Multiple times, and I even tried a different Windows 10 computer... Still no luck...
xstewminator said:
Hey Everyone!
Just got my Mi Mix 3 and the hardware is awesome, but I'm having trouble unlocking the bootloader through the mi unlock tool, I already have permissions from my account with my OG Mi Mix, but for some reason it will not detect the Mix 3. Sometimes it does detect the phone if I start Fastboot while plugged in and with the tool open on my windows 10 pc, but it cannot verify the phone, even though I have signed in on the phone through my Mi Account.
Any Ideas on what could be causing this? I saw another thread a coupe weeks ago with a similar issue, but the only way they got it working was with a win7 machine, of which I don't have.
I have all the proper drivers and utilities installed, but nothing is working, even tried it on a different windows 10 machine and still no avail.
Wondering if anyone else is having the same problem?
Thanks in advance for the help!
Click to expand...
Click to collapse
Driver signature enforcing might be the issue on windows 10, might need to deactivate it on pc boot or go to earlier version (win7)
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP