v1.3.1

What's New in v1.3.1

Bug Fix — Motorola + Magisk

service.sh now correctly remounts the /oem/ partition (the actual block device mount point) before writing. Previously only /oem/media/ was attempted, which silently failed on stock Motorola firmware with Magisk.

Note: dm-verity must be disabled on /oem/ for the write to succeed. This is typically the case on custom ROMs; stock firmware with active dm-verity is generally not supported.

---

Downloads

Variant	For
GeminiBootAnimation-standard-v1.3.1.zip	Pixel · AOSP · crDroid · OnePlus · Realme
GeminiBootAnimation-MIUI-v1.3.1.zip	Xiaomi MIUI / HyperOS
GeminiBootAnimation-MTK-v1.3.1.zip	MediaTek devices
GeminiBootAnimation-Motorola-v1.3.1.zip	Motorola (stock + custom ROM)
GeminiBootAnimation-EMUI-v1.3.1.zip	Huawei EMUI

Supported root: Magisk · KernelSU · KernelSU + SUSFS · APatch

---

Changelog

• fix: service.sh — try remounting parent partition (/oem/, /system/, …) as fallback when subdirectory remount fails (fixes Motorola + Magisk)
• docs: added explicit note about dm-verity requirement for Motorola on stock firmware

Full changelog: v1.3...v1.3.1

v1.3

What's new

Motorola variant

Stock Motorola firmware stores the boot animation on a dedicated OEM partition at /oem/media/ — not /system/media/. The standard variant had no effect there. The new Motorola variant covers this path via both Magic Mount and service.sh (KernelSU + SUSFS fallback).

EMUI variant

Huawei EMUI checks /system/etc/media/ in addition to the standard paths. The new EMUI variant installs to all three locations.

Note

HarmonyOS is not supported — its rendering pipeline is proprietary.

---

Download — which ZIP?

File	For
GeminiBootAnimation-standard-v1.3.zip	Pixel, AOSP, OnePlus, Realme, crDroid
GeminiBootAnimation-MIUI-v1.3.zip	Xiaomi MIUI
GeminiBootAnimation-MTK-v1.3.zip	MediaTek devices
GeminiBootAnimation-Motorola-v1.3.zip	Motorola stock firmware
GeminiBootAnimation-EMUI-v1.3.zip	Huawei EMUI

---

V1.2

What's new

🔍 Automatic environment detection

The installer detects your root setup at install time and applies the right method automatically — no manual configuration needed.

🛠️ KernelSU + SUSFS support

SUSFS hides Magic Mount overlays from system processes, including the bootanimation service. v1.2 adds a service.sh fallback that writes the animation files directly to the partition on first boot (requires dm-verity to be disabled).

🔗 Symlink handling

Some ROMs ship bootanimation-dark.zip as a symlink to bootanimation.zip. The module now removes the symlink before writing, preventing silent failures.

---

Installation method by setup

Setup	Method	Reboots needed
Magisk	Magic Mount	1
KernelSU	Magic Mount	1
KernelSU + SUSFS	Direct write via service.sh	2

---

Downloads

File	For
GeminiBootAnimation-standard-v1.2.zip	Pixel · AOSP · OnePlus · Realme · most custom ROMs
GeminiBootAnimation-MIUI-v1.2.zip	Xiaomi MIUI
GeminiBootAnimation-MTK-v1.2.zip	MediaTek devices

---

Full changelog: CHANGELOG.md

v1.1

What's new

• Three device-specific variants for better compatibility:
  • Standard — Pixel, AOSP, OnePlus, Realme
  • MIUI — Xiaomi (installs to all MIUI media paths)
  • MTK — MediaTek devices (custom/media path)
• Animation is now installed to both /product/media and /system/media

Installation

Flash the zip matching your device via Magisk, KernelSU or APatch.

v1.0.0 — Gemini Boot Animation

Gemini Boot Animation v1.0.0

Initial release — Gemini Boot Animation ported from the Google Pixel 10.

Installation

1. Download GeminiBootAnimation-v1.0.0.zip
2. Flash via Magisk / KernelSU / APatch Manager or TWRP
3. Reboot

Compatibility

• All Android versions
• Magisk / KernelSU / APatch