Database Develop

unable to get Mi A2 recognized on Windows 10

Just got a used A2. Booted it up and no bootloader unlocked message. Tried to unlock bootloader but unable to get it recognized on my windows 10 PC. I have tried all ways to install the drivers, used different USBC cables, different USB port on the PC but no luck.
Developer options have been triggered & USB debugging is allowed.
Please let me know what drivers worked for you guys?
Mi drivers? Google drivers?
Thanks

iluvatrix said:
Just got a used A2. Booted it up and no bootloader unlocked message. Tried to unlock bootloader but unable to get it recognized on my windows 10 PC. I have tried all ways to install the drivers, used different USBC cables, different USB port on the PC but no luck.
Developer options have been triggered & USB debugging is allowed.
Please let me know what drivers worked for you guys?
Mi drivers? Google drivers?
Thanks
Click to expand...
Click to collapse
Try mi platform tools no matter for which device but try to get for a2 if available, windows 10 automatically installs drivers for me after some time i use minimal adb and fastboot and it worked but bootloader wasn't unlocked i unlocked it again and it worked, unlock it with critical command, i am using havoc os on mi a2 it is best

Phone not detected

Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?

This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?

MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).

I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...

Fastboot not detecting

Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).

Quaczi said:
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Click to expand...
Click to collapse
I had this problem in my Nokia 7 Plus, then i used and installed "minimal adb and fastboot" file which detected my phone in fastboot. It installs in program file with a folder named "minimal adb and fastboot"
Sent from my Redmi K20 Pro using Tapatalk

You need to enable "USB debugging" in the developper options

ImEraaz said:
You need to enable "USB debugging" in the developper options
Click to expand...
Click to collapse
It is enabled.
And ill try with the minimal adb option
Update:
Still not working

I have same problem, there is no way to recognize my 9t pro in fastboot mode... i cant do anything

First it should be intel pc
Try to install Xiaomi drivers and adb
Boot to recovery and fastboot while connecting to usb to install the drivers
Then check again

Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.

simpn said:
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
Click to expand...
Click to collapse
Try changing ports / connect to another pc
Install proper drivers .
Is your bl unlocked now ?

Got it to work under win7 with great help from this post.
What I did was:
Update to the latest miui version (to MIUI Global 11.0.3, as prompted in system settings, I hadn't bothered to update because I just want to throw miui out)
Disable OEM unlock
Reboot
Enable OEM unlock again
Reboot into fastboot
Then the phone showed up as an unknown device in Device Manager
Right clicked the device and updated the driver, chose to search for drivers in the miflash_unlock-en-3.5.1108.44\driver\xp-win7-win8 folder
The device now lists as an Android Bootloader Interface device
And now:
$ fastboot devices
e150445 fastboot
MiFlash unlock detects the phone, and I could proceed with unlocking. Still have to wait though. Tried the older-version-trick as suggested here, but that just told me to update to the latest version. Guess I'll have to wait a week then...
Hope this helps someone. This is the most tedious unlocking procedure I've encountered so far...

Fastboot not recognizing device

dear all,
I could not find any solution that helped me.
yesterday, I have updated to latest firmware+vendor MIUI Global 11.0.6.0. in order to flash Lineage OS 17.1.
But when I am in fastboot mode my device is not recognized by adb. While in regular OS the device is recognized, so USB debugging is on.
What I tried:
- bootloader unblocked successfully
- latest USB drivers
- original USB cable, other cables
- Qualcomm drivers updated
- latest platform-tool / ADB
- three different laptops
What am I missing?
all i want is to install TWRP
thanks a lot

instrumental said:
dear all,
I could not find any solution that helped me.
yesterday, I have updated to latest firmware+vendor MIUI Global 11.0.6.0. in order to flash Lineage OS 17.1.
But when I am in fastboot mode my device is not recognized by adb. While in regular OS the device is recognized, so USB debugging is on.
What I tried:
- bootloader unblocked successfully
- latest USB drivers
- original USB cable, other cables
- Qualcomm drivers updated
- latest platform-tool / ADB
- three different laptops
What am I missing?
all i want is to install TWRP
thanks a lot
Click to expand...
Click to collapse
While in fastboot mode, what was the command you used? Was it;
adb devices
or
fastboot devices?
In fastboot mode, all commands should start with fastboot 'commands'.
Sent from my MI 9 (Cepheus) using Tapatalk

i cannot believe this.. it worked.. but when I tried to flash the twrp.img it always said no such directory or whatever..
thanks man

[SOLVED] Windows drivers for Honor 4X (Che2-L11). Not detected in bootloader mode

Hi
I'm trying to flash TWRP on my CHe2-L11 via adb but it gets stuck at < Waiting for any device >.
I read somewhere that is because Windows lacks the necesary drivers (although Che2-L11 is listed as "MTP" in the devices connected to my computer).
Where can I find the necessary drivers for Win10?
Thanks a lot
Best,
-a-

OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess? Windows can not automatically find drivers for this...
Then it make sense that I cannot flash the custom recovery until the phone is detected again.
What should I do to have my phone detected in Windows while it is in bootloader mode?
Thanks a lot
-a-

Running windows update found a driver for
Google Android Bootloader Interface
However, ADB still cannot detect it
EDIT: Actually it works! Even though
adb devices
would not list anything when the phone was in bootloader mode, I was able to flash twrp
Problem solved!