Fastboot not working - Xiaomi Mi 5 Questions & Answers

Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize

Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc. Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Sent from my Xiaomi Mi5 using Tapatalk

SilverMarcs said:
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc.
Click to expand...
Click to collapse
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
SilverMarcs said:
Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Click to expand...
Click to collapse
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.

FrozenPie1 said:
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
Click to expand...
Click to collapse
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Sent from my Xiaomi Mi5 using Tapatalk

SilverMarcs said:
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Click to expand...
Click to collapse
It's not working on both Windows 10 Machines i have. I'll try to install Windows 7 on my Laptop (or in a VM) and look if that works when i'm home again
Edit: Well, now i'm totally confused... For some reason fastboot started working again this morning so i was able to flash TWRP again. Anyway thanks for the help

FrozenPie1 said:
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Click to expand...
Click to collapse
I too have the same problem..****

Install MiFlash on your PC and try again, the device will show up correctly on fastbook devices command. It was a USB drivers issue in my case.

Related

Bootloop + Twrp not installing properly

Hi everyone I need some serious help. I unlocked my bootloader just fine then booted into TWRP using the command
Code:
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
after that used the ADB sideload button in TWRP. I used this command
Code:
adb sideload twrp-installer-3.3.1-0-jasmine_sprout.zip
which didn't work and then I eventually advanced wiped my device. The reason it didn't work ios because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Mactroiy said:
Hi everyone I need some serious help. I unlocked my bootloader just fine then booted into TWRP using the command
Code:
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
after that used the ADB sideload button in TWRP. I used this command
Code:
adb sideload twrp-installer-3.3.1-0-jasmine_sprout.zip
which didn't work and then I eventually advanced wiped my device. The reason it didn't work ios because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Click to expand...
Click to collapse
Hello Mac,
Are you running the commands from the adb directory? Example, adb devices which typically would show your xiaomi mi a2 device.
Is the Android USB driver showing as adb in device manager?
I have the very same device, it is a little tricky since it has an a and b partition and you have to be precise when installing a custom ROM. Here's a how to that may be of help to you, it definitely helped me a lot.
Good luck!
[ADB | FASTBOOT | LINUX COMMANDS] BootLoader, Kernel, Recovery, ROM, Root, Backup
Mactroiy said:
.... then I eventually advanced wiped my device...
Click to expand...
Click to collapse
What did you wipe? If anything except Dalvik Cache and/or Cache, then most probably you'll have to reflash stock ROM in fastboot.
Mactroiy said:
The reason it didn't work is because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Click to expand...
Click to collapse
If "Android Portable Device" drivers are installed correctly (and PC has USB2.0 slot and/or USB 3.x slot compatible with MiA2, which happens not so often), still ADB (if I am not mistaken) sees connected phone if it is
1) booted normally, USB Debugging is On, MTP is On, and ADB with this PC have been validated in phone (and still ADB has limited functionality depending on kernel), or
2) booted into TWRP
You can check ADB connection using "adb devices -l",
- if command shows nothing, then either drivers not installed or USB port is failing or nothing compatible booted in phone,
- if command shows unauthorized transport id, then you have not approved ADB in phone
If phone is in fastboot mode, then, with drivers installed and USB port being compatible, "fastboot devices" shhould show attached phone, and if it is fully unlocked, stock fastboot ROM can be reflashed

Fastboot can't detect my unlocked device

Hi I have a problem where my pc does not detect my unlocked device in fastboot. This is a problem because I tried to update from global V10.3.3.0 to miui 11 but that did not work probably because there is not the right recovery on the device. So I can not get into the recovery and I can not get into the system this would of course be no problem because I can get into fastboot but my computer wont detect my device. How can I get my 9t pro to be detected in fastboot?
My device is unlocked. I did all that some time ago and it says so when I try to boot into system or recovery.
USB debugging is on. Idk if that is still there because I did try to update the system to miui11 but it was not detecting my phone in fastboot even before I did that update.
When I connected my phone to my computer when the system still worked I could use "adb devices" and that worked
I could also transfer files and stuff when my phone was connected to my laptop
So only when in fastboot my unlocked device is not detected if it was I could get back up there.
I really hope that this is some driver problem or something. Please help
Edit:
So at this point magically the system worked again! But I still can not use fastboot
I seem to have this problem:
https://forum.xda-developers.com/k20-pro/help/broken-fastboot-t3972697

Fastboot error Android Q

Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Maharram said:
Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Click to expand...
Click to collapse
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Tianhe said:
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Click to expand...
Click to collapse
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Maharram said:
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Click to expand...
Click to collapse
I know this might sound silly but are you using the latest platform tools version ?
Tianhe said:
I know this might sound silly but are you using the latest platform tools version ?
Click to expand...
Click to collapse
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Maharram said:
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Click to expand...
Click to collapse
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7
Click to expand...
Click to collapse
Yeah im using win 10 redstone (latest version)
But also i did it on win 10 with Android 9
Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Click to expand...
Click to collapse
Going to try this. Thanks a lot <3
Maharram said:
Going to try this. Thanks a lot <3
Click to expand...
Click to collapse
Hope you get the desired result. I am also on Win 10 latest update and I had faced issues initially. I have also added a registry hack so that everytime I open CMD with shift+right click it opens with administrator privileges.

I can't install twrp, make a hard reset, update by OTA, nothing O.o

SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.
SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.

[SOLVED] Stuck on TWRP splash screen after trying to OTA update PixelExperience. HELP!

I will try to keep it short. I installed PE on my mi 8 se and it was working fine then a OTA update arrived, i clicked install and it turned off and stuck on TWRP splash screen. there is no navigation or buttons, it doesn't turn off till the battery runs out. after charging it up again it shows the twrp screen. i can go to fastboot mode by pressing power+vol- but
Code:
fastboot devices
doesn't show any devices connected to my pc. my pc also doesn't recognizes the phone and marks it as "USB unknown" and updating it with android drives shows an error stating that its not compatible.
Code:
adb devices
shows my phone when in twrp screen but that's about it.
as it stands:
-
Code:
fastboot devices
doesn't recognize devices, i think because USB debugging was off but now i have no way of boot into my phone to turn it on
-
Code:
adb devices
recognizes my phone but i don't know what to do with it
-i read somewhere that pixel experience "FBE encrypts the phone so twrp is unable to access past encryption" but i don't know what that means
-currently my phone is a brick with twrp logo, so please HELP.
THANKS in advance for help.
siyyee said:
I will try to keep it short. I installed PE on my mi 8 se and it was working fine then a OTA update arrived, i clicked install and it turned off and stuck on TWRP splash screen. there is no navigation or buttons, it doesn't turn off till the battery runs out. after charging it up again it shows the twrp screen. i can go to fastboot mode by pressing power+vol- but
Code:
fastboot devices
doesn't show any devices connected to my pc. my pc also doesn't recognizes the phone and marks it as "USB unknown" and updating it with android drives shows an error stating that its not compatible.
Code:
adb devices
shows my phone when in twrp screen but that's about it.
as it stands:
-
Code:
fastboot devices
doesn't recognize devices, i think because USB debugging was off but now i have no way of boot into my phone to turn it on
-
Code:
adb devices
recognizes my phone but i don't know what to do with it
-i read somewhere that pixel experience "FBE encrypts the phone so twrp is unable to access past encryption" but i don't know what that means
-currently my phone is a brick with twrp logo, so please HELP.
THANKS in advance for help.
Click to expand...
Click to collapse
NOTES (Read First):
- Twrp can´t decrypt data in android 12, so you need to install updates or magisk via adb sideload. If you remove pin lock in android you can install updates normally, because data can be decrypted.
- Do a clean install if your coming from PE11 or PE12 Alpha. Don´t update. And follow instructions from "Install".
- This firmware and vendor included in rom is specific to this rom, don´t try to use them in other roms.
- This twrp will probably only work with this vendor and firmware, don´t use in other roms.
Install:
1 - Flash rom (this is needed to install proper vendor and firmware)
1 - Flash Recovery via adb (Download: https://drive.google.com/file/d/1Iqa4-sBwThUAAvJsFwl6oP-D4EzRcCyq/view)
2 - Reboot recovery
3 - Factory Reset and Format Data (backup sdcard before format)
4 - reboot recovery
5 - Flash ROM via adb sideload (Advanced -> ADB sideload)
6 - reboot system
Update:
1 - Reboot recovery
2 - Advanced -> ADB sideload
3 - Reboot system
beenmoov said:
NOTES (Read First):
- Twrp can´t decrypt data in android 12, so you need to install updates or magisk via adb sideload. If you remove pin lock in android you can install updates normally, because data can be decrypted.
- Do a clean install if your coming from PE11 or PE12 Alpha. Don´t update. And follow instructions from "Install".
- This firmware and vendor included in rom is specific to this rom, don´t try to use them in other roms.
- This twrp will probably only work with this vendor and firmware, don´t use in other roms.
Install:
1 - Flash rom (this is needed to install proper vendor and firmware)
1 - Flash Recovery via adb (Download: https://drive.google.com/file/d/1Iqa4-sBwThUAAvJsFwl6oP-D4EzRcCyq/view)
2 - Reboot recovery
3 - Factory Reset and Format Data (backup sdcard before format)
4 - reboot recovery
5 - Flash ROM via adb sideload (Advanced -> ADB sideload)
6 - reboot system
Update:
1 - Reboot recovery
2 - Advanced -> ADB sideload
3 - Reboot system
Click to expand...
Click to collapse
thanks for the response,
but as i mentioned in my post, fastboot doesn't recognized my device, the attached image is the output for
Code:
fastboot devices
i have no way to reboot phone to the os, its just either TWRP splash screen or fastboot mode by pressing power+vol-
thanks, hoping for further solution.
siyyee said:
thanks for the response,
but as i mentioned in my post, fastboot doesn't recognized my device, the attached image is the output for
Code:
fastboot devices
i have no way to reboot phone to the os, its just either TWRP splash screen or fastboot mode by pressing power+vol-
thanks, hoping for further solution.
Click to expand...
Click to collapse
Have you tried to reflash to miui with mi flash tools?
maybe changing the cable or installing drivers because if it's boot to bootloader you can Always do Something.
siyyee said:
thanks for the response,
but as i mentioned in my post, fastboot doesn't recognized my device, the attached image is the output for
Code:
fastboot devices
i have no way to reboot phone to the os, its just either TWRP splash screen or fastboot mode by pressing power+vol-
thanks, hoping for further solution.
Click to expand...
Click to collapse
you should install fastboot driver first so the computer can access your phone in fastboot mode. after that you can easily use fastboot command to reinstall twrp image. follow this guide: https://beebom.com/fastboot-not-detecting-device-windows-10/
hey guys,
sorry for late reponse but i managed to fix the problem, turns out the cable i was using was faulty so i changed it with the original one and wallah it recognized my device.
then i flashed stock rom and then xiaomi eu rom, now working great.
thanks for all the help.

Categories

Resources