Hello,
My Windows 7 PC is not able to detect the drivers for Xperia L. I have already installed the PC Companion and also installed the Flash Tool drivers, ADB Universal Drivers. Still it doesn't detect the device.
ADB Debugging is enabled.
Can you give a download link for the drivers?
Thanks.
ReSkid said:
Hello,
My Windows 7 PC is not able to detect the drivers for Xperia L. I have already installed the PC Companion and also installed the Flash Tool drivers, ADB Universal Drivers. Still it doesn't detect the device.
ADB Debugging is enabled.
Can you give a download link for the drivers?
Thanks.
Click to expand...
Click to collapse
Try a different approach. Go into your device manager on your PC. You can go into device manager by going into properties of MY COMPUTER or Control Panel\System and Security\System
When your device is connected, do you see an exclamation mark in devices. Reinstall it by finding drivers manaually.
IF this all fails, just delete the device and refresh it.
Another very useful trick is to delete the unknow device (xperia L) and restart your Xperia L. Then search for device changes. it will be detected automatically.
Is your MTP ticked in Xperia / Connection/ USB connection on your phone ?
Hnk1 said:
Try a different approach. Go into your device manager on your PC. You can go into device manager by going into properties of MY COMPUTER or Control Panel\System and Security\System
When your device is connected, do you see an exclamation mark in devices. Reinstall it by finding drivers manaually.
IF this all fails, just delete the device and refresh it.
Another very useful trick is to delete the unknow device (xperia L) and restart your Xperia L. Then search for device changes. it will be detected automatically.
Is your MTP ticked in Xperia / Connection/ USB connection on your phone ?
Click to expand...
Click to collapse
Unfortunately, I have done all that. Isn't there a driver setup file for this phone? Can't seem to find it anywhere.
Thanks!
I'm facing the same problem.
I'm tryng to unlock the boot loader following the instructions on Sony website, but when it comes to use fastboot it just keep saying <waiting for device>.
And I have installed all the stuff you said, too.
ReSkid said:
Unfortunately, I have done all that. Isn't there a driver setup file for this phone? Can't seem to find it anywhere.
Thanks!
Click to expand...
Click to collapse
xperiaL said:
I'm facing the same problem.
I'm tryng to unlock the boot loader following the instructions on Sony website, but when it comes to use fastboot it just keep saying <waiting for device>.
And I have installed all the stuff you said, too.
Click to expand...
Click to collapse
Oh I remember, i was facing the same problem for bootloader. I am uploading the drivers. These should work. The trick is download the 2kb file and past it into google drivers and then find them from the PC.
Good Luck.
Hnk1 said:
Oh I remember, i was facing the same problem for bootloader. I am uploading the drivers. These should work. The trick is download the 2kb file and past it into google drivers and then find them from the PC.
Good Luck.
Click to expand...
Click to collapse
Thanks a lot man, Please if you could share the instructions.
ReSkid said:
Thanks a lot man, Please if you could share the instructions.
Click to expand...
Click to collapse
getochkn said:
the whole of this was my phone was softbricked. I wanted to get into recovery so I could use ADB to try to fix it. When it's softbricked, ADB won't start up, therefore I could use ADB.
Trust me, I know how to use ADB, I just wanted to know if there was a key combination to get our phones into recovery mode with ADB because ADB wouldn't work because my phone was softbricked. It had nothing to do with me not knowing how to use ADB or how to set it up, it had to do with my phone would brick it self before ADB started, so therefore I couldn't send any ADB commands.
Click to expand...
Click to collapse
Don't mention it mate. Hit thanks if you think I helped
DRivers for Xperia L
http://forum.xda-developers.com/showthread.php?p=46681107#post46681107
Problem solved. It was tricky, though.
Having PC companion installed wincrap didn't make me choose other drivers.
So I disabled the signature verification for drivers -> rebooted -> connected Phone while pressing the vol UP -> opened device manager -> select s1boot fastboot (which had a warning icon) -> selected driver manually (the .inf file we replaced following the first steps.
then i just used cmd as in the guide.
et voilà, bootloader unlocked.
I hope this is helpful to those who faced my same problem.
Related
Hello,
My mother just got a Sony Xperia M2, and I wanted to root it for her... Well, I have a Samsung Galaxy S4, and it's way easier to do it !
I followed the tutorial from this website : Developer . sonymobile . com
I downloaded everything (I'm on Windows 8, I also got the extra stuffs to DL), and it was pretty fine until the "connect your device" part !
In the tuto, you should Turn off the phone, connect the USB wire to the computer, and then press Volume UP while you connect the phone in USB...
After that you need to select the drivers from Flashmode, I select the right folder, but it's not working ! It says that I don't have "Android ADB Interface" or thing like that. So, I can't update the drivers, and can't complete the unlocking !
From the official video (that I can't link or past) they gave on the website, my problem starts at 4:20
Do you have an idea please ??
Thanks !
First of all, before trying to flash anything it is better to check if the phone connects fine while running normally. Download PC Companion if you don't have it already (it's a nice app anyway, you may need it), run it, connect the phone via USB and see if it gets recognized. Then you will need to enable the USB Debugging for ADB access:
http://www.phonearena.com/news/How-to-enable-USB-debugging-on-Android_id53909
After that check with Flashtool if it gets recognized with the phone on. Then I'm not sure anymore, but don't you need to hold the volume key(s) BEFORE connecting the phone to the USB to enter flash modes?
Flysch said:
Hello,
My mother just got a Sony Xperia M2, and I wanted to root it for her... Well, I have a Samsung Galaxy S4, and it's way easier to do it !
I followed the tutorial from this website : Developer . sonymobile . com
I downloaded everything (I'm on Windows 8, I also got the extra stuffs to DL), and it was pretty fine until the "connect your device" part !
In the tuto, you should Turn off the phone, connect the USB wire to the computer, and then press Volume UP while you connect the phone in USB...
After that you need to select the drivers from Flashmode, I select the right folder, but it's not working ! It says that I don't have "Android ADB Interface" or thing like that. So, I can't update the drivers, and can't complete the unlocking !
From the official video (that I can't link or past) they gave on the website, my problem starts at 4:20
Do you have an idea please ??
Thanks !
Click to expand...
Click to collapse
Use flashtool from this link :http://www.flashtool.net/index.php
After installing it, install Drivers from <Installed Dir>/flashtool/drivers folder.
If you don't know, select all platforms.
May be you need to disable "driver signature check" for win 8.
Tutorial here : http://forum.xda-developers.com/showthread.php?t=2095087
Try with flashtool, it should work now.
mvv1277 said:
May be you need to disable "driver signature check" for win 8.
Tutorial here : http://forum.xda-developers.com/showthread.php?t=2095087
Click to expand...
Click to collapse
Thank you, the only solution was this thing ! "Disable driver check" was it !
And in order to be clear (maybe for people who will need help too), I deleted/disabled the drivers of the Xperia M2 from the computer. So it was like I plugged the phone for the FIRST time again. The computer wants to install drivers, just Cancel, and right-clic -> Install (or update) drivers, and you're done ! !
MY BOOTLOADER IS FINALLY UNLOCKED ! Thank you really !
Hey
A couple of days ago i tried to install the latest CM12 nightly. After updating it my phone crashed everytime it booted up. I did a factory reset and tried to flash older versions but nothing seemed to work so i went into CWM recovery 6.0.4.5 and pretty much formatted everything.
I still have access to the bootloader and recovery but my Windows 8.1 PC doesn't recognize my phone ("Unknown usb device" "Windows has stopped this device because it has reported problems. (Code 43)") I can't access my phone with adb or fastboot now. This looks like a driver problem but i tried a lot of different drivers on multiple PC's.
What can i do now?
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Darth said:
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
zagorteney said:
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
Click to expand...
Click to collapse
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer. ?
Darth said:
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer.
Click to expand...
Click to collapse
And in future: please, stay on stock.
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
dermaxe said:
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
Click to expand...
Click to collapse
Try this: http://nirsoft.net/utils/usb_devices_view.html
It helped me a few times.
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
Did you use USBDeview or you just manually removed all drivers that you saw?
I went into USBDeview and uninstalled everything that was android related
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
How do i enable usb debugging without any os?
dermaxe said:
How do i enable usb debugging without any os?
Click to expand...
Click to collapse
chaco81 said:
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
Click to expand...
Click to collapse
USB debugging enabled is only needed when using Adb from within the Android OS. It's not needed for adb use in recovery mode, and never needed for fastboot.
??
good to know
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
For me this sounds more like computer realted problem rather than device. If you can try all of those steps ( installign drivers, etc ) on another pc maybe this will solve your issue
Just tried it on a fresh installation of W7 but my device wasn't recognized and i couldn't install any drivers for it. How can it be a PC related problem if it doesn't work on so many different configurations?
If you run it on VirtualBox, see this answer (prepend http, I can't post links): superuser.com/a/887249/239087
To make it short, you need VirtualBox Extension Pack, and you need to configure the USB port to use USB 2.0 at least.
Unable to unlock bootloader on my xperia l the flashboot software says driver not found,cannot find appropriate usb_driver for my phone on net tried many none worked!.Urgent need!!
Tried on all xda questions but none resolved the matter.
mohitsinghania said:
Unable to unlock bootloader on my xperia l the flashboot software says driver not found,cannot find appropriate usb_driver for my phone on net tried many none worked!.Urgent need!!
Tried on all xda questions but none resolved the matter.
Click to expand...
Click to collapse
Did you tried flashtool driver pack?
If not, then follow below steps.
Hope you'll succeed
You have to install it manually. Just download below flashtool driver pack (link below)
http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS4zLTIwMTQwMjA5
Download above and double click on it > next > fastboot drivers (at bottom of the list) install it and now connect your phone in fastboot mode.
Now follow and Complete popups for fastboot.
(If there's popup for MTP drivers, just cancel it)
After installation is finished Disconnect device and connect again in fastboot mode.
(VolUP and then connect USB )
If above process fails, let me know
If you found this helpful, there's a thumbs up button, just press it
Regards,
hitman-xda
Unable to download driver and driver not present for xperia L
hitman-xda
Hey thanks a lot to reply..
I am unable to download driver as usual, screenshots has been attached, and also in the drivers list in fastboot driver Xperia L is not mentioned, that is the main problem, otherwise i would have downloaded the driver of my phone from sony website. Xperia L bootloader unlocked owner might help please.
hitman-xda said:
Did you tried flashtool driver pack?
If not, then follow below steps.
Hope you'll succeed
You have to install it manually. Just download below flashtool driver pack (link below)
Download above and double click on it > next > fastboot drivers (at bottom of the list) install it and now connect your phone in fastboot mode.
Now follow and Complete popups for fastboot.
(If there's popup for MTP drivers, just cancel it)
After installation is finished Disconnect device and connect again in fastboot mode.
(VolUP and then connect USB )
If above process fails, let me know
If you found this helpful, there's a thumbs up button, just press it
Regards,
hitman-xda
Click to expand...
Click to collapse
Thank you it worked with an older flasboot driver installer
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Use PC Companion repair option (marked with a red box on my screenshot).
LitoNi said:
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Click to expand...
Click to collapse
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Install the drivers that are inside flashtool.
Mr_Bartek said:
Use PC Companion repair option (marked with a red box on my screenshot).
Click to expand...
Click to collapse
As mentioned, SPCC doesn't recognize my phone. It somewhat does but doesn't give me the option to repair. There are these other screens which i think are prior to the repair page (hopefully) but i was stuck at the page when it asks me to remove the battery or skip if built in. It asks me to press ok to skip but hitting the ok button didn't do anything.
zacharias.maladroit said:
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Click to expand...
Click to collapse
Thanks my desktop is running windows 10 and i know theres so many issues with it.
gm007 said:
Install the drivers that are inside flashtool.
Click to expand...
Click to collapse
The drivers from flashtool does not include any xperia Z5 series.
Thank you guys for the quick responses, I managed to reflash the .200 through flashtool without any hiccups. which is weird that it didn't work for .163 earlier. I didn't wipe anything, so after flashing .200 i updated the SDK stuff from Google SDK.exe which i think it solved some, from there I flashed .163 (MM) again and it worked. Kept all data intact, even my encrypted Class 10 SD card worked without any issues. So far so good, haven't really encountered any errors, fingers crossed :fingers-crossed: once again thank you for the quick responses.
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