If you want to see the solution directly, see the summary
2020.10.13: Remember a little thing. Tonight, the official miui upgrade is daily. I am playing on the computer, and continue to play the csgo man-machine for a while before the phone is turned on. The redmi interface has been stuck on the redmi interface after the call is finished. Generally, after booting the redmi interface, the boot animation should be displayed, and I can't enter the boot animation. start testing
feature
- Unable to enter the recovery mode: Long press the power button and the volume up button, the phone vibrates, the bright screen is the redmi interface, sometimes it will automatically restart like this when it is left, that is, the cycle is stuck in the boot interface.
- If you plug in the power at this time, the indicator light will turn red and it should indicate that it is charging.
- Because the usb debugging is not turned on, it is impossible to test whether it can be debugged.
- I also wondered if it was the problem caused by the magisk module, which was not verified later. After all, I did not add any new "optimization" modules.
- Then I searched it online, and there was no meaningful answer, it was just a idiom.
Later, I suddenly remembered that I haven't tried fastboot mode (Bootloader mode). So I tried it: Long press the power button and the volume down button, and a cute bunny appeared. It's easier to get in.
- Brush the recovery partition again and reboot into recovery.
- After successfully flashing in, and successfully booting to the recovery mode, when the TWRP start interface appears, then you can start happily again.
Unexpectedly, after entering the recovery, it automatically flashed the original flashing package according to the openrecoveryscript script (the flashing package has been confirmed that md5 is correct, and generally the wrong package of md5 often has error code 7), but after thinking about it, why not try again?
- After brushing at 22:24, the system restarted; at 22:30, the system officially turned on.
- . . . There really is you, really metaphysics
to sum up
- Therefore, the cycle card boot interface cannot enter the recovery mode, but if you can enter the fastboot, you can use fastboot to flash the recovery again and re-enter. After entering the recovery mode, it is a small machine that can be used at will.
- If it is the official original system, the same is true. Extract the official recovery and re-flash in fastboot. (Please note the following precautions)
What, then? Then flash in your available flash package in the recovery partition, if not, pass in one (can you upload things in the official rec, don’t know, maybe)
Of course, if it’s not a third-party rec (official system, the BL lock has not been unlocked) , Directly in fastboot mode, just use the corresponding software to flash the machine on the computer (that is, wire flash)
Unless it is really caused by your own major physical operations (such as falling into the water), don't believe in the nonsense of changing the motherboard (too expensive!), try it yourself first
Note : AboveEstablished in unlocked BootLoader case of(Only in this way can the recovery partition or the line brush be activated) Newer machines generally have BootLoader locks, and the old ones generally do not.
If there is a BootLoader and a Qualcomm machine that has not been unlocked, you can also try to force recovery on port 9008 . Other inability (specifically, Baidu, I have not tried)
How do I know if there is a BootLoader lock: You can search it online or in the official community, such as Xiaomi’s https://www.xiaomi.cn/ , you can click on a model in the MIUI download, and click the download button There is a flashing tutorial on the right. On the left, you can see whether all models have BL lock information. --> BootLoader lock information of all Xiaomi phones
BootLoader extension
References know almost Q & A brush recovery need to do to unlock the bootloader :
Author: Paul Yang
If the bootloader is locked, the boot partition cannot be erased in fastboot and recovery situations, but these two methods can be bypassed to flash . The high-universal 9008 port flashing third-party rec can start third-party rec, because some mobile phone bootloader does not verify The signature of the rec partition.
If BL is locked, even if you forcibly flash the unofficial boot, BL will verify the digital signature of the boot partition, so the Android kernel cannot be loaded into RAM and the system cannot be started.
Whether the bootloader is locked or not depends entirely on the manufacturer’s strategy. The principle of locking is to modify the value of a specified location in a designated partition. BL detects this value at startup to determine the locked state. There are usually four values: locked, Unlocked, unlocked, and critically unlocked.
Where is the bootloader? The bootloader is a collective term for several startup stages. The bootloader is similar to the boot manager of the computer and is responsible for starting the user-level operating system of the mobile phone. For Qualcomm mobile phones, the one responsible for starting the Linux kernel is aboot. The fastboot program is in aboot In the partition, recovery is started after loading the Linux kernel of the rec partition.