The screensaver when you turn on your smartphone (or boot animation) is the first thing you see when you press the power button. Xiaomi has traditionally minimalist: the Mi or Redmi logo on a white/black background. But what if you want something original? Can you replace it with your own image, GIF or even video?
Unfortunately, the manufacturer did not provide a built-in feature for changing the screensaver through standard settings, but there are both official workarounds (for some models) and informal methods that require unlocking the bootloader or superuser rights. In this article, we will discuss all current methods, their pros, cons and potential risks. MIUI 14 and the new firmware HyperOS, where the algorithms have changed.
We warn you in advance that there are always risks involved in tampering with system files, but if you act carefully, the result will exceed expectations β your Xiaomi will turn on with unique animations that no one else has.
1. What is the screensaver when turned on and can it be changed
Boot animation is a graphics file that is played when the operating system is booted, and on Xiaomi, it consists of two parts:
- π± Manufacturer logo - static image Mi/Redmi/POCO, It appears immediately after you press the power button, stored in the section. /dev/block/bootdevice/by-name/logo.
- π¬ Load animation is the dynamic part (usually a rotating circle or progress lane) that follows the logo. bootanimation.zip lie in /system/media/.
Can we replace them? Technically, but with reservations:
- β Official method β available only on some models through theme store MIUI (For example, on Xiaomi 13 Pro or Redmi Note 12 Pro+ It allows you to change only the animation, not the logo.
- βοΈ Unofficial methods require bootloader unlocking and root rights, give full control over the screensaver, but deprive warranties and increase the risk of "bricking" the device.
It's important to understand that when you turn on, it's not the same as a lock wallpaper or a greeting screen, and the latter are changed through the settings. MIUI Two clicks, while boot animation will require system files to be replaced.
β οΈ Note: On HyperOS devices (e.g. Xiaomi) 14 or Redmi K70) The system file structure has changed. MIUI 12-13, You may not work or you may crash. Before experimenting, check the firmware version in Settings. β The phone. β Version. MIUI.
2.Official method: change animations through themes (for supported models)
The safest method is to use built-in tools MIUI. It is suitable for devices with HyperOS or the latest versions. MIUI 14, where the manufacturer added customization support for the screensaver through themes:
- Open the Themes app (icon with brush).
- Go to the Lock Screen section.
- Scroll down to the Download Animation block (or Boot Animation in English).
- Choose your favorite animation from the offered and apply it.
If there is no such partition, your device does not support the official screensaver change, in which case only informal methods remain (see the following sections).
Among the available animations are usually:
- π Abstract patterns with smooth transitions.
- π¨ Minimalist logos with glowing effects.
- π± Thematic GIFs (e.g. with Mi Bunny characters).
β οΈ Note: Even the official change of animations may conflict with some custom firmware (e.g. xiaomi.eu).If after applying the theme, the phone started to brake when turned on, reset the theme settings to the standard in Settings. β Additionally. β Resetting theme settings.
π‘
If the theme store does not have suitable animation, try downloading third-party themes in.mtz format from the forums. XDA Developers or 4PDA. Install them through the Topics menu β Local, but check first for compatibility with your version MIUI/HyperOS.
Informal methods: requirements and preparation
If the official method doesn't work, you're left with interference with the system files, and this process requires:
- On Xiaomi, it is locked by default. Unlocking erases all data and can take up to 72 hours (due to Mi Unlock policy).
- Superuser rights (root) are obtained through Magisk or SuperSU after unlocking.
- Backup of the Logo and File Section bootanimation.zip. Without it, the restoration of the standard screensaver will be difficult.
- Special PO: ADB, Fastboot, a root-enabled file manager (such as Root Explorer or Mixplorer).
Also, prepare a new screensaver file. It must meet the requirements:
| Parameter | For the logo (logo.bin) | For animation (bootanimation.zip) |
|---|---|---|
| Format | .bin (compressed image) | .zip-file part0, part1 and the desc.txt file |
| Permission | Strictly under screen resolution (e.g, 1080Γ2400 For the Redmi Note 11) | Any, but recommended multiple screen resolution |
| Color model | RGB565 (16 bits) | RGB888 or RGBA8888 (24/32 bat) |
| Max size. | Up to 2MB | Up to 10 MB (otherwise lags are possible) |
Where can I get the finished files?
- π οΈ Create your own through Boot Animation Factory (for the first time) bootanimation.zip).
- π₯ Download XDA Developers or 4PDA (Look for topics for your model).
- πΌοΈ Create a logo in Photoshop and convert to.bin via Logo Maker (Windows app).
Unlock the bootloader through Mi Unlock Tool|
Install Magisk to get root|
Make a backup of the logo section and bootanimation.zip|
Prepare a new screensaver file in the correct format|
Install ADB and Fastboot on PC|
-->
Replacement of the manufacturerβs logo (the method for advanced)
Logo. Mi/Redmi When turned on, it is stored in a separate section of the logo, and its replacement is the most risky operation, since an error can lead to a "brick" (not being able to turn on the device:
- Download Logo Maker and create a file logo.bin from your image (the resolution must match the screen!).
- Connect your phone to your PC in Fastboot mode (turn off the device, then press Volume Down + Power).
- In the command line, run: fastboot flash logo your_logo.bin
- Reboot the device: fastboot reboot
On HyperOS, the path to the logo partition may be different! Before you run the firmware, check it through the fastboot getvar all command and find the logo: line.
If the screen is black after the firmware is installed or artifacts appear:
- π Return the standard logo with the fastboot flash logo command original_logo.bin (You must have a backup!).
- π§ Check the compatibility of the color model (should be RGB565).
- π Make sure that the file resolution matches the screen resolution exactly.
β οΈ Note: On some models (e.g, POCO F5 Xiaomi 13T) The logo section is protected by an additional signature, and changing it without special patches can cause an error in the Invalid sparse file format at header, in which case you will need to firmware the custom kernel with the check turned off.
What if the phone doesnβt turn on after the logo is replaced?
5. Replacement of download animation (bootanimation.zip)
Download animation changes easier than logo, as file bootanimation.zip It's in the system partition, and it's not protected by a hardware signature. You'll need root rights and a file manager with access to the system folders.
Instructions:
- Download or create a file bootanimation.zip (The structure should include folders part0/part1 and desc.txt).
- Open Root Explorer and go to the /system/media/.
- Backup the original file (copy it). bootanimation.zip safe-haven).
- Replace the file with your own by setting rights to 644 (owner β root, group β root).
- Reset the device.
If the animation is not played or the phone is getting stuck:
- π Check the structure bootanimation.zip: Desc.txt should indicate correct paths and delays (example: 720 480 24 permitting FPS).
- π Make sure that the file is in the /system/media/, not /data/local/ (The last one doesn't work on all the firmware).
- π οΈ If the animation twitches, reduce the number of frames or convert the gif to APNG (format with better optimization).
For HyperOS devices, the path may be different.
- Connect to the ADB and do: adb shell su find / -name bootanimation.zip
- Copy the found path and replace the file through ADB: adb push your_bootanimation.zip /found/path/bootanimation.zip
π‘
HyperOS replacement bootanimation.zip If the animation hasn't changed, try to delete the original file first, then copy the new one and license it. 644.
6. Alternative methods: Magisk modules and custom firmware
If manual file replacement seems difficult, you can use ready-made solutions:
- π§© Magisk modules: On the forum XDA There are modules like BootAnimations or MiuiBootMod that allow you to change the screensaver without manually editing system files.
- π± Custom firmware: Firmware like LineageOS or Pixel Experience often includes built-in tools to change boot animation through settings.
- π¨ Apps with root: Boot Animations (from Play Market) or BootAnimations Changer automate the replacement process.
Example of installation via Magisk:
- Download a module (e.g. BootAnimation Replacer).
- Open Magisk Manager β Modules β Install from storage.
- Select the downloaded file and wait for the installation.
- Reset the device.
Advantages of this method:
- β No need to manually edit system files.
- β It is easy to return standard animation (just turn off the module).
- β Support for animations with sound (if the module allows it).
β οΈ Note: Some Magisk modules conflict with HyperOS. Before installing, check compatibility in the module description. If after using the module, the phone goes to bootloop (cyclic reboot), boot in Recovery and remove the module through Magisk β Modules. β Delete.
7. Frequent problems and their solutions
When you replace the screensaver, users encounter common mistakes.
| Problem. | Possible cause | Decision |
|---|---|---|
| Phone not turned on (black screen) | The file is damaged. logo.bin or | Stitch the original logo.bin fastboot |
| No animations played (black screen after logo) | The wrong structure bootanimation.zip or | Check desc.txt and set up 644 rights |
| Screensaver twitches or brakes | Too large file or high resolution frames | Optimize the GIF to 24 FPS size <5 MB |
| After the replacement, the settings were reset. | Conflict with Magisk module or firmware | Restore the backup through TWRP or re-follow boot.img |
If none of the methods worked:
- π Check logs with adb logcat during booting (Look for BootAnimation: failed to open).
- π‘ Update the firmware to the latest version β in new builds of HyperOS can be fixed bugs with customization.
- π¬ Please refer to the relevant forums (for example, 4PDA), specifying the device model and firmware version.