English | 简体中文

A simple module that replaces boot animations with custom ones and works on almost every Xiaomi device. This module is also compatible with tablets since, in contrast to phones, tablets frequently modify their animations according to the orientation of the device.

This module utilizes systemless mount to mount the bootanimation files to the specified location, ensuring no modifications are made to the system partition.

• Magisk v26.1+ / KernelSU v0.8.0+ / APatch 10568+
• Android 11+ (API 30+) running MIUI/HyperOS

1. Use the GitHub Actions workflow to build your custom module
2. Download the built module from Artifacts
3. Flash .zip module in the Magisk / KernelSU / APatch app

During the first installation, you'll be prompted to backup your current boot animation. The backup functionality helps you restore the original animations if needed.

First Install:

• When installing the module for the first time, if no backup exists, you'll be prompted to backup your current boot animation
• Backups are stored in /data/adb/boot-backups/ and include all bootanimation*.zip files from your selected location

Module Updates:

• When updating the module, the backup process will be automatically skipped if a backup already exists
• Your original boot animations remain safely backed up from the first installation

To restore your original boot animation:

1. Disable or uninstall this module in Magisk/KernelSU/APatch
2. Reboot your device

1. Add GitHub Actions workflow for automated module building (Done)
2. Auto detect and select path for corresponding models

You can use GitHub Actions to build a custom boot animation module without any local tools! The workflow automatically downloads the latest release as a base.

1. Fork this repository
2. Go to Actions → "Build Custom Boot Animation Module"
3. Click "Run workflow"
4. Set Source to template
5. Select your Device model (e.g., liuqin)
6. Select the Template (e.g., HyperOS)
7. Select the Target location
8. Download the built module from Artifacts

1. Fork this repository
2. Add your bootanimation.zip files to the upload/ folder
3. Commit and push your changes
4. Go to Actions → "Build Custom Boot Animation Module"
5. Click "Run workflow"
6. Select upload as the source
7. Select the Target location
8. Download the built module from Artifacts

• bootanimation.zip - Main boot animation
• bootanimation01.zip - Alternative 1 (rotation variant)
• bootanimation02.zip - Alternative 2
• ... and so on

Each bootanimation.zip should contain:

bootanimation.zip
├── desc.txt          # Required: Animation descriptor
├── part0/            # Required: First animation part
│   ├── 00000.png
│   ├── 00001.png
│   └── ...
├── part1/            # Optional: Second animation part
│   ├── 00000.png
│   └── ...
└── ...

<height> <width> <fps>
<type> <count> <pause> <path>
...

Example:

1880 2880 60
p 0 5 part0

• c = play complete, p = play and repeat
• First number = loop count (0 = infinite)
• Second number = pause after loop (in frames)
• Path = folder containing the frames

A bootloop saver module is strongly advised even if there is little possibility that flashing this module would cause your device to bootloop. I am not responsible for any damages caused to your device or data by using this module. Use at your own risk.

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.