Home Page » News » Tutorials » How to Create a Custom Android Boot Animation Without Root Using ADB and Fastboot

Create a Custom Android Boot Animation Without Root

12 min read Step‑by‑step guide to design, package, and flash a custom boot animation on Android devices using ADB and Fastboot, without needing root access. October 03, 2026 10:30

What you will achieve

By the end of this tutorial you will have a fully functional, personalized boot animation that appears every time your Android device powers on. The process uses only ADB and Fastboot, so you never need to root the phone or install third‑party recovery images.

Why a custom boot animation matters

The boot animation is the first visual cue users see after the device powers up. Replacing the stock animation can give a device a personal touch, help differentiate multiple devices in a fleet, or even serve as a branding tool for developers. Because the animation is stored in the bootanimation.zip file on the boot partition, flashing it correctly is the only requirement – no system files are altered, which keeps the risk of bricking low.

Note: Most manufacturers lock the bootloader to protect the device. Flashing a boot animation via Fastboot typically requires an unlocked bootloader. The steps below explain how to check the lock state and, if necessary, unlock it safely. If you cannot unlock the bootloader, an alternative method using a custom recovery (e.g., TWRP) is provided.

Before you start

Back up important data – unlocking the bootloader will perform a factory reset on many devices.
Charge the phone to at least 70 % to avoid power loss during flashing.
Use a reliable USB‑C or micro‑USB cable; a faulty cable can cause intermittent ADB connections.
Install the latest Android SDK Platform‑Tools on your computer (contains adb and fastboot).
Prepare a folder on your PC where you will keep the animation frames and the final bootanimation.zip.

Step 1 – Gather the required tools

Download and extract the Platform‑Tools package to a known location, e.g., C:\adb or ~/adb.
Open a terminal (Command Prompt on Windows, Terminal on macOS/Linux) and add the folder to your PATH or navigate to it each time you run a command.
Verify the installation by running adb version. You should see something like Android Debug Bridge version 1.0.41.

Step 2 – Design your animation

Android expects the boot animation to be a ZIP archive containing a desc.txt file and one or more folders of PNG frames. The desc.txt defines the playback speed and resolution.

2.1 Choose resolution and frame rate

Most modern phones use a 1080 × 1920 (portrait) or 1080 × 1080 (square) canvas. For older devices you might need 720 × 1280. Decide on a frame rate – 30 fps looks smooth, but 15 fps reduces file size.

2.2 Create the frame folders

Inside your working directory create a folder named part0. Place every PNG frame in this folder, naming them sequentially (e.g., 00001.png, 00002.png, …). The naming must be zero‑padded to five digits; Android stops reading when a number is missing.

2.3 Write `desc.txt`

Create a plain‑text file called desc.txt next to part0. The format is:

width height fps loop

For a 1080 × 1920 animation at 30 fps that loops forever, use:

1080 1920 30 0

If you want the animation to stop after one play (useful for a splash screen), replace the last 0 with 1.

2.4 Test the animation locally

You can preview the animation on your PC with a simple script or by using the ffplay command (part of FFmpeg). This step is optional but helps catch visual glitches before flashing.

Step 3 – Package the animation into `bootanimation.zip`

Navigate to the directory that contains desc.txt and the part0 folder.
Run the following command (adjust the path to your zip utility if needed):

zip -r9 bootanimation.zip desc.txt part0

The -r9 flags create a recursive archive with maximum compression, which keeps the file under the typical 10 MB limit imposed by the boot partition.

Step 4 – Enable USB debugging on the phone

Without USB debugging ADB cannot communicate with the device.

Open Settings → About phone → tap Build number seven times to enable Developer options.
Return to Settings → System → Developer options → toggle USB debugging on.
Connect the phone to the computer via USB. On the phone, confirm the “Allow USB debugging?” prompt and optionally check “Always allow from this computer”.
In the terminal run adb devices. You should see your device’s serial number with the word device beside it.

Step 5 – Check bootloader lock status

Run:

adb reboot bootloader

This reboots the phone into Fastboot mode. Then type:

fastboot getvar unlocked

If the response is unlocked: yes, you can proceed to flash the animation directly. If it says no or the command fails, the bootloader is locked.

5.1 Unlocking the bootloader (if needed)

Unlocking varies by manufacturer. The generic command is:

fastboot flashing unlock

Most devices will display a warning and ask you to confirm using the volume and power buttons. Confirm the unlock. Warning: unlocking wipes all user data on many OEMs (e.g., Samsung, OnePlus). Ensure you have a backup before proceeding.

After unlocking, the device will reboot automatically. Repeat the adb reboot bootloader and fastboot getvar unlocked check to confirm the status.

Step 6 – Flash the custom boot animation

Make sure you are still in Fastboot mode. If not, run adb reboot bootloader again.
Copy the bootanimation.zip you created to the folder where fastboot resides, or provide the full path.
Run the flashing command:

fastboot flash boot bootanimation.zip

Some devices use the boot partition for the animation, others use a dedicated bootanimation partition. If the above command fails with “partition not found”, try:

fastboot flash bootanimation bootanimation.zip

Observe the output. A successful flash ends with “OKAY” and a short time stamp.

After flashing, reboot the device:

fastboot reboot

Step 7 – Verify the result

Power off the phone completely, then turn it on. The new animation should play immediately after the OEM logo. If the stock animation still appears, double‑check the partition name used in Step 6 and repeat the flash.

Alternative method – Using a custom recovery (TWRP)

If your device’s bootloader cannot be unlocked (some carrier‑locked phones), you can still replace the boot animation via a custom recovery that allows flashing arbitrary ZIPs.

Install TWRP for your device model. This usually requires an unlocked bootloader, but a few OEMs provide an “official” recovery image that can be flashed via fastboot flash recovery without unlocking. Research your specific model.
Reboot into TWRP (Power + Volume Up). In the main menu choose “Install”.
Copy the bootanimation.zip to the device’s internal storage (you can use adb push bootanimation.zip /sdcard/).
In TWRP, navigate to the ZIP file and swipe to flash. TWRP will place the file in the correct location automatically.
Reboot the system from TWRP and confirm the new animation.

This method does not require unlocking the bootloader, but it does require a custom recovery, which itself may void warranties.

Troubleshooting

Fastboot says “command not found” or “device not found”. Ensure the USB cable is data‑capable, the phone is in Fastboot mode, and you have the appropriate drivers (Google USB driver for Windows, udev rules for Linux).
Flash fails with “cannot write to partition”. Verify you used the correct partition name (boot vs bootanimation). Some OEMs lock the boot animation partition; in that case the custom recovery method is the only viable path.
The animation is garbled or shows a black screen. Check that the PNG files are 24‑bit RGB (no alpha channel) and that the resolution in desc.txt matches the actual frame size. Mismatched dimensions cause the system to fall back to the default animation.
The device boots into recovery after flashing. This indicates a corrupted flash. Re‑enter Fastboot, run fastboot erase boot (or bootanimation) to clear the partition, then flash again.
Boot loop after flashing. Some devices store the animation in the boot partition alongside the kernel. Overwriting it can corrupt the boot image. If this happens, you will need to re‑flash the stock firmware using the OEM’s fastboot flash script or a factory image.

Safety warnings and best practices

Data loss: Unlocking the bootloader wipes user data on most phones. Back up contacts, photos, and app data beforehand.
Warranty considerations: Unlocking the bootloader or installing a custom recovery may void the manufacturer’s warranty. Check the warranty terms for your device.
Partition integrity: Flashing the wrong partition can render the device unbootable. Double‑check the partition name and keep a copy of the stock boot image (you can extract it with fastboot dump boot boot.img before flashing).
File size limits: The boot animation partition is typically around 10 MB. Exceeding this limit will cause the flash to fail. Keep your animation concise – a few seconds of looping video is usually sufficient.

Putting it all together – a quick checklist

Back up data and charge the phone.
Install Platform‑Tools and verify adb/fastboot.
Design frames, write desc.txt, and zip them into bootanimation.zip.
Enable USB debugging and confirm ADB connection.
Check bootloader lock status; unlock if you accept the data‑wipe risk.
Flash the ZIP to the correct partition with fastboot flash boot bootanimation.zip (or bootanimation).
Reboot and enjoy your new boot animation.

With these steps you have full control over the first visual impression of your Android device, without ever needing root privileges. The same workflow can be reused to update the animation whenever inspiration strikes.

User Comments (0)

Add Comment

No comments added yet.

Add Comment

Your Name: *

Comment Title: *

Your E-mail: * We'll never share your email with anyone else.

Your Comment: *

Comments will not be approved to be posted if they are SPAM, abusive, off-topic, use profanity, contain a personal attack, or promote hate of any kind.