Multi-OEM Dynamic Boot Animation

Overview

Multi-OEM Dynamic Boot Animation (authored by Stinky Panda) provides a reliable, systemless framework for customizing Android boot sequences across diverse OEM interfaces, including Xiaomi (MIUI/HyperOS), OPPO (ColorOS), Realme (Realme UI), and generic AOSP firmware.

Installing custom boot animations has traditionally been one of the most common causes of bootloops for modders. Mismatched frame dimensions, unsupported image compression (such as deflated rather than store-only ZIP compression), or missing desc.txt terminating newlines cause the native Android bootanimation binary to fault or enter infinite replay loops.

Multi-OEM Dynamic Boot Animation eliminates this vulnerability by wrapping the animation delivery in an autonomous health-check watchdog that monitors startup timing and disengages the overlay if any fault occurs.

Technical Architecture & How It Works

The module operates across three complementary components:

1. Multi-Stage Animation Overlay

Android loads boot animations from prioritized locations:

1. /product/media/bootanimation.zip
2. /system/media/bootanimation.zip

The module establishes systemless mounts on these locations, injecting animations packaged with the requisite part structures (part0, part1, etc.) and non-compressed format (zip -0) essential for hardware surface decoders.

2. Startup Watchdog (service.sh)

The module’s late-service daemon monitors the core Android init system property:

sleep 60
if [[ "`getprop init.svc.bootanim`" = "running" ]]; then
    # Boot animation is still looping after 60 seconds -> potential hang
    echo > $MODDIR/disable
    sh $MODDIR/umount.sh
    echo "Device startup failure detected. Module disabled automatically." > $MODDIR/boot_failure.log
    exit
else
    # Startup successful -> execute random animation selection for next boot
    sh $MODDIR/random_animation.sh
fi

If the animation daemon is still actively spinning after 60 seconds, the module concludes that the system has hung, immediately calls umount.sh to unmount the overlay from memory, and writes a recovery flag.

3. Dynamic Animation Shuffler (random_animation.sh)

When the phone reaches normal operation, random_animation.sh scans the module directory for alternate animation archives, randomly selects one using $RANDOM, and stages it as the primary bootanimation.zip for the subsequent device restart.

Adding Custom Animations

To introduce your own animations:

1. Ensure the animation archive is stored using 0% compression (Store method in 7-Zip or zip -0 -r bootanimation.zip desc.txt part*).
2. Verify that desc.txt includes a trailing blank line.
3. Copy the archive into /data/adb/modules/bootanimation/ with a distinct filename (e.g. cyberpunk.zip).