If you want to customize your Android device’s startup animation without modifying system files or relying on OverlayFS, the Bootanimation Module is one of the easiest solutions available. Designed for rooted Android devices, this lightweight module lets you replace your device’s bootanimation.zip in a completely systemless way.
Unlike many boot animation modules, this one doesn’t depend on Magisk Magic Mount or OverlayFS. Instead, it uses bind mounts, making it compatible with Magisk, KernelSU, and APatch while keeping the installation simple and clean.

In this guide, you’ll learn everything about the Bootanimation Module, including its features, requirements, installation process, usage, troubleshooting, FAQs, and more.
Table of Contents
What is Bootanimation Module?
Bootanimation Module is an open-source Magisk module developed by readonlynux that allows you to replace your Android device’s default boot animation with your own custom bootanimation.zip.
Instead of editing system partitions, the module copies your custom animation into its own directory and bind-mounts it during every boot. This makes the modification completely systemless and easy to remove whenever you want.
The module also includes a simple command-line utility called bootanim, making it easy to apply, remove, enable, or disable custom boot animations.
Features
Bootanimation Module includes several useful features:
- Works without OverlayFS or Magisk Magic Mount
- Supports Magisk, KernelSU, and APatch
- Completely systemless installation
- Automatically detects boot animation location on modern Android devices
- Simple command-line interface
- Experimental WebUI support
- Lightweight and fast
- Easy to uninstall without affecting system files
Requirements
Before installing the module, make sure your device meets the following requirements.
Root Access
Your device must be rooted using one of the following:
- Magisk
- KernelSU
- APatch
Existing bootanimation.zip
Your device must already use a standard bootanimation.zip.
The module cannot work on devices that use proprietary boot animation formats such as Samsung’s .qmg files.
Terminal App
You’ll need a terminal application or ADB shell to use the included bootanim command.
Examples include:
- Termux
- Terminal Emulator
- ADB Shell
Download Bootanimation Module
Download the latest stable release from the project’s official GitHub Releases page.
Always download the newest version to receive bug fixes and compatibility improvements.
How to Install Bootanimation Module
Installing the module is straightforward.
Step 1
Download the latest Bootanimation Module ZIP.
Step 2
Open your root manager.
- Magisk
- KernelSU
Step 3
Go to:
Modules → Install from Storage
Select the downloaded ZIP file.
Step 4
Wait until installation finishes.
Step 5
Reboot your device.
Setting Up the Terminal
After rebooting:
- Open your terminal app.
- Type:
su
- Grant root permission.
- You can now use the bootanim commands.
How to Use Bootanimation Module
The module includes a command called:
bootanim
To view available commands:
bootanim help
Apply a Custom Boot Animation
If your custom animation is located at:
/sdcard/bootanimation.zip
Run:
su
bootanim set /sdcard/bootanimation.zip
If successful, you’ll see:
Bootanimation applied successfully
Reboot your device to see the new animation.
Remove Custom Boot Animation
To remove the installed animation:
bootanim reset
Disable Boot Animation
Temporarily disable the custom animation:
bootanim disable
The stock animation will be used after reboot.
Enable Boot Animation Again
Enable the custom animation:
bootanim enable
Check Current Status
View the current module status:
bootanim state
It displays:
- Whether a custom animation exists
- Whether it is enabled or disabled
Experimental WebUI
The module also includes an experimental WebUI.
It provides a simple graphical interface for managing boot animations instead of using terminal commands.
The WebUI is optional and currently considered experimental.
How It Works
Instead of replacing system files, the module performs these steps:
- Copies your custom
bootanimation.zip - Stores it inside:
/data/adb/bootanimation/
- During every boot, bind-mounts the file over the system boot animation.
Because system partitions remain untouched, removing the module instantly restores the original boot animation.
Troubleshooting
Bootanimation file not found
This usually means:
- Wrong file path
- Missing ZIP file
Verify the file location and run the command again.
Boot Animation Doesn’t Change
Check whether:
- Module is installed correctly
- Root permission is granted
- The custom animation exists
Run:
bootanim state
If no animation is installed, apply it again.
Device Still Shows Stock Animation
Possible reasons include:
- Animation is disabled
- Incorrect ZIP format
- Installation failed
Enable it again:
bootanim enable
Boot Loop After Installation
Although uncommon, if your device cannot boot:
- Enter recovery mode
- Disable or remove the module
- Reboot
Since everything is systemless, removing the module restores the original animation.
Samsung Devices
Most Samsung devices use:
.qmg
instead of:
bootanimation.zip
Because of this, Bootanimation Module usually will not work on Samsung firmware unless the ROM uses the standard Android boot animation format.
Compatibility
The module has been tested on Android 15 but should work on most Android versions that use bootanimation.zip.
Compatible with:
- Android 11
- Android 12
- Android 13
- Android 14
- Android 15
Support on older versions depends on your ROM.
FAQs
Does this module require Magisk?
No.
It supports:
- Magisk
- KernelSU
- APatch
Does it need OverlayFS?
No.
One of the biggest advantages is that it works completely without OverlayFS.
Can I restore the original boot animation?
Yes.
Simply run:
bootanim reset
or uninstall the module.
Where is the custom animation stored?
The module stores it in:
/data/adb/bootanimation/bootanimation.zip
Does it modify system files?
No.
Everything is systemless.
No system partition is edited.
Can I use multiple boot animation modules?
It is not recommended.
Running multiple modules that replace the boot animation may cause conflicts.
Use only one boot animation module at a time.
Credits
Developer: readonlynux
License: MIT License
Icons: Google Material Icons (Apache 2.0 License)
Conclusion
Bootanimation Module is an excellent choice if you want a clean, lightweight, and systemless way to customize your Android boot animation. Unlike traditional solutions, it doesn’t rely on OverlayFS or Magic Mount, making it compatible with modern rooting methods like Magisk, KernelSU, and APatch.
Installation is simple, the included bootanim command makes managing animations easy, and uninstalling the module instantly restores your device’s original boot animation. If your device uses the standard bootanimation.zip format, this module offers one of the safest and most convenient ways to personalize your Android startup experience.


