Database Info

Fastboot Not Recognized

Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.

chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL

Venomtester said:
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.

Windows XP makes life easier

chriscerv90 said:
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.
Click to expand...
Click to collapse
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL

Venomtester said:
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.

chriscerv90 said:
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.
Click to expand...
Click to collapse
I know this may sound silly at this point but did you try moving it to a different usb port? I have seen that work before.
AT&T HTC OneX
Android 4.1.1
ViperXL

try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.

I had to use a different Micro-USB cable to get it work. Try that.

Yeah I actually have tried all those steps. Thanks for the replies guy. I check out that application.
I'm starting to think something is wrong with my HOX
Sent from my HTC One X using xda app-developers app

DvineLord said:
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Click to expand...
Click to collapse
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:

glad you got it fixed, check out his other apps they are life savers and they work how "real" windows apps should work.

I have the same problem
chriscerv90 said:
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:
Click to expand...
Click to collapse
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??

abhilashlinge said:
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??
Click to expand...
Click to collapse
If your on Windows 8 problems will occur but there are methods you need to look into. Windows 7 is your ally.
First Uninstalled the drivers for the device using the program in the previous post. Second, make sure your cable is working correctly. Third, make sure you have the correct drivers for you phone on the computer - - HTC Sync causes problems sometimes. Fourth, plug in the phone in while it's on and let the drivers install correctly. Fifth, place the phone in fastboot and let drivers install. Should work.
Remember sometimes you need to restart your computer and try different USB ports. Some users have said 3.0 ports cause problems.
Good luck.
Sent from my SM-N900A using XDA Premium 4 mobile app

chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
I ws installing a Ruu zip but process got failed and hboot version changed to 1.54.000 . my device is in now relocked status and bootloader is not reconised by hp envy. adb still showing my device my i lost fastboot mode completely. Any solution there???
I already tried several drivers method. Error is something HTCAND4 in driver events log.

What did u do?

Can't connect to laptop

I wanted to install a new rom, and so I did all the wipes and formated system, before this I updated my recovery and I think this is why my laptpo dosent recognise my phone once I mountUSB in recovery...any ideas?

dark'em said:
I wanted to install a new rom, and so I did all the wipes and formated system, before this I updated my recovery and I think this is why my laptop dosent recognise my phone once I mountUSB in recovery...any ideas?
Click to expand...
Click to collapse
You got to uninstall the drivers of (Windows 7) for the usb ports from the "device Manager". and reinstall the drivers. Else try to connect to another system. You might be lucky. I had a similar problem and i tried this about 5 times as i had multiple usb ports and wasnt able to pinpoint which one was having the problem. Also uninstall any adb drivers or any other tools related to nexus. then try to reconnect and check it out. Even if this dosent work you might need to reinstall the ROM on your device after doing a complete factory reset/datawipe.

paydy12 said:
You got to uninstall the drivers of (Windows 7) for the usb ports from the "device Manager". and reinstall the drivers. Else try to connect to another system. You might be lucky. I had a similar problem and i tried this about 5 times as i had multiple usb ports and wasnt able to pinpoint which one was having the problem. Also uninstall any adb drivers or any other tools related to nexus. then try to reconnect and check it out. Even if this dosent work you might need to reinstall the ROM on your device after doing a complete factory reset/datawipe.
Click to expand...
Click to collapse
Thanks but I used fastboot and it worked, the problem was with the new recovery

[Q] Unbricked successfully, ADB broken?

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.

Does usb debugging is on?

Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?

If You use asus drivers it worth to try universal naked driver.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.

Hmm... How windows show tablet when You connect it to PC?

Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?

It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?

Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.

Try first remove all drivers and software for tablet. Then install universal naked driver.

Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.

[Q] Do I need HTC drivers after a Cyanonegmod rom is installed?

Do I need HTC drivers after a Cyanonegmod rom is installed?
Acutally I can't connect my device to the PC (Win7 x64).
Thanks
Sent form HTC One S Ville C2

Andrewww65 said:
Do I need HTC drivers after a Cyanonegmod rom is installed?
Thanks
Sent frm HTC One S Ville C2
Click to expand...
Click to collapse
You need HTC drivers Doesn't matter which ROM you have installed.

LS.xD said:
You need HTC drivers Doesn't matter which ROM you have installed.
Click to expand...
Click to collapse
What do you think about this problem? Why my PC dosen't reognice my device?

Andrewww65 said:
What do you think about this problem? Why my PC dosen't reognice my device?
Click to expand...
Click to collapse
You want to connect your storage to copy files? Try uninstalling all drivers.

LS.xD said:
You want to connect your storage to copy files? Try uninstalling all drivers.
Click to expand...
Click to collapse
Since I installed Cyanogenmod 4.3 onto my device I can connect my storage but without enabling the storage my PC doesn't recognize the device properly.
The reason my asking is I'd like to update the recovery (as I heard TWRP 2.6.0.0. does't support KitKat and want to upgrade it to 2.6.3.0. or newer).
When I try to flash a newer recovery with fastboot I get an error message "device not found". Doesn't matter the storage connection is on or off. Unfortunately my ROM doesn't have setting for fast reboot or something but I assume it's off.
The latest official HTC driver's installed.

Andrewww65 said:
Since I installed Cyanogenmod 4.3 onto my device I can connect my storage but without enabling the storage my PC doesn't recognize the device properly.
The reason my asking is I'd like to update the recovery (as I heard TWRP 2.6.0.0. does't support KitKat and want to upgrade it to 2.6.3.0. or newer).
When I try to flash a newer recovery with fastboot I get an error message "device not found". Doesn't matter the storage connection is on or off. Unfortunately my ROM doesn't have setting for fast reboot or something but I assume it's off.
The latest official HTC driver's installed.
Click to expand...
Click to collapse
You need the drivers but not htc sync. That should be uninstalled. I've also had problems with adb but i've noticed that if connection to pc is set as MTP the pc recognize it and ADB works. You can try this as well
Sent from nowhere over the air...

I've read several threads here...
Rapier said:
You need the drivers but not htc sync. That should be uninstalled. I've also had problems with adb but i've noticed that if connection to pc is set as MTP the pc recognize it and ADB works. You can try this as well
Sent from nowhere over the air...
Click to expand...
Click to collapse
It could be a stupid question but how to connect the device and PC as MTP?
I've read several threads here and found MTP drivers in .cab files including .inf and .cat files. When I tried to update the portable devices drivers I get the message (My Windows7 x64 is Hungarian, maybe the translation isn't totally correct): "You already installed the up to date driver - WPD file system driver"
Just to summarize the situation:
- HTC One S Ville C2 - Unlocked but S-on !!!
- HTC sync and HTC sync manager are uninstalled.
- Unofficial Cyanogenmod 10.2 by bilal_liberty - I do not have an option to check whether the usb debugging is on or off.
- When I connect the device the windows can see it, gives it a driver letter but I can' use any fastboot/flash command.
- My phone recognize the connection and offers to turn on the usb storage and it works.
Thanks for your help.

Andrewww65 said:
It could be a stupid question but how to connect the device and PC as MTP?
I've read several threads here and found MTP drivers in .cab files including .inf and .cat files. When I tried to update the portable devices drivers I get the message (My Windows7 x64 is Hungarian, maybe the translation isn't totally correct): "You already installed the up to date driver - WPD file system driver"
Just to summarize the situation:
- HTC One S Ville C2 - Unlocked but S-on !!!
- HTC sync and HTC sync manager are uninstalled.
- Unofficial Cyanogenmod 10.2 by bilal_liberty - I do not have an option to check whether the usb debugging is on or off.
- When I connect the device the windows can see it, gives it a driver letter but I can' use any fastboot/flash command.
- My phone recognize the connection and offers to turn on the usb storage and it works.
Thanks for your help.
Click to expand...
Click to collapse
The debugging ON is done in the Dev Options. If you don't have Dev Options you should go to about phone an tap several times on the Build Version till you got the message "Now you're a developer"
I don't remember in CM1.2 but in CM11 there's a menu in Settings-Storage to change from UMS to MTP

Rapier said:
The debugging ON is done in the Dev Options. If you don't have Dev Options you should go to about phone an tap several times on the Build Version till you got the message "Now you're a developer"
I don't remember in CM1.2 but in CM11 there's a menu in Settings-Storage to change from UMS to MTP
Click to expand...
Click to collapse
Ok it's done. Thank you so much (button pushed:good.
I don't know why the dev option is hidden in CMs like this.
So Dev option/Debugging is on and MTP connection enabled. Now I get a new error message: "device offline". But it's on. Screen unlocked etc.:crying:

Andrewww65 said:
Ok it's done. Thank you so much (button pushed:good.
I don't know why the dev option is hidden in CMs like this.
So Dev option/Debugging is on and MTP connection enabled. Now I get a new error message: "device offline". But it's on. Screen unlocked etc.:crying:
Click to expand...
Click to collapse
This could be due to older or incorrect drivers. I had some issues several times due to improper drivers and I had to try several times till it worked. Starting with the HTC ones and up to the default Google drivers found in the Android SDK. Finally I make it work but believe me, I don't know how it worked I just tried until I got the proper drivers that worked

Rapier said:
This could be due to older or incorrect drivers. I had some issues several times due to improper drivers and I had to try several times till it worked. Starting with the HTC ones and up to the default Google drivers found in the Android SDK. Finally I make it work but believe me, I don't know how it worked I just tried until I got the proper drivers that worked
Click to expand...
Click to collapse
Thanks Rapier! I will do like that.

Question Fastboot not working in Windows 11 [Resolved]

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