Location and replacement of the bootanimation file in Android

When starting any modern smartphone based on the operating system Android the user sees a colorful splash screen that replaces the manufacturer’s logo and precedes the appearance of the desktop. This visual element, known as bootanimation, is stored in the form of a special archive and is loaded into the device’s RAM in the very first seconds after turning on the power. For enthusiasts and developers, knowing the exact location of this file is key when customizing the interface or creating your own firmware.

By default, the system accesses the system partition, which is often write-protected by ordinary users without superuser rights. Understanding the file system hierarchy Linuxon which Android is based allows you to determine exactly where to look for this resource in order to replace it with a custom version or disable it altogether. In this article, we will analyze in detail the directory structure and methods of working with boot animation.

It is worth noting that in different firmware versions and on devices from different vendors, the paths may differ slightly, but the basic logic for allocating system resources remains unchanged. Critical zip is not executable code, but is a sequence of frames compressed by the Deflate algorithm. This opens up wide possibilities for modification without the risk of damaging the bootloader, provided that packaging rules are followed.

Standard paths to the loading animation file

In the classic Android architecture, the animation file is located in the root directory of the system partition. The main and most common way is /system/media/. This is where the system looks for the file bootanimation.zip when initializing the interface loading process. If you have root access and connected to the device through a terminal or file manager with access to system folders, this is the first place you should look.

However, equipment manufacturers often make their own adjustments to the standard file structure. On some devices, especially from companies Samsung or Xiaomi, you may encounter file duplication or its placement in alternative locations for backup. For example, the copy may be in a directory /product/media/ or even in /oem/media/if the OEM partition is mounted as readable.

When searching for a file, it is important to consider the download priority. The system checks several paths sequentially, and the first file found will be used for display. This means that having a file in one of the alternate directories may override the default system animation. For complete control over the process, you need to check all possible locations.

• 📂 Main path: /system/media/bootanimation.zip
• 📂 Alternative path for custom firmware: /data/local/bootanimation.zip
• 📂 Backup on some devices: /product/media/bootanimation.zip
• 📂 Path for themes design: /data/data/com.android.thememanager/files/

⚠️ Attention: Direct editing of files in a partition /system is only possible if you have root access and unmount the partition in read-write (RW) mode. Careless actions can lead to a bootloop (cyclic reboot).

Download priority and animation search mechanism

The animation loading mechanism in Android is more complex than simply accessing one fixed path. The service management process SurfaceFlinger or BootAnimation implements search logic that depends on the device configuration and operating system version. Understanding this priority is necessary to successfully replace the standard screensaver with a custom one.

First of all, the system checks for the presence of a file in the directory /data/local/. This is done specifically so that users and developers can test their animations without having to reflash the entire system partition. If a file is found here, it will be used regardless of what is in /system. This is the most secure replacement method for devices with root access.

If the file is not in the local data directory, the search continues in the system partition. The order here may vary, but usually the path /system/media/is checked. In modern versions of Android, starting from 10 and higher, a system of dynamic partitions and project partitions has been introduced, which can transfer a file to /product/media/. The system will always select the first valid archive that can decode correctly.

Developers of custom recovery, such as TWRP, often use this priority feature to set themes. The installation script simply copies the new archive to /data/local/, and after rebooting the user sees the new picture. This eliminates the need to modify the protected system partition, which significantly reduces risks.

File path	Priority	Requirements	Damage risk
/data/local/bootanimation.zip	High (1)	root access	Minimum
/system/media/bootanimation.zip	Medium (2)	Root + RW mode	High
/product/media/bootanimation.zip	Medium (2)	Root + RW mode	High
/oem/media/bootanimation.zip	Low (3)	Depends on the vendor	Medium

Archive structure bootanimation.zip

The animation file is a standard ZIP archive, but with one important feature: it should not contain compression for internal image files, although the archive itself can be compressed using the storage method (Store). Inside the archive there is a text file desc.txt, which is the configuration center of all animation. It is he who tells the system the screen resolution, frame rate and sequence of playback of parts.

In addition to the description, the archive contains folders with the name part0, part1 and so on. Each folder contains a sequence of frames in the format png. The system reads these images in order and displays them on the screen. It is important that file names are numbered with leading zeros (for example, 00001.png, 00002.png), otherwise the playback order may be disrupted.

The image format is strictly regulated. Typically, a color depth of 24-bit without an alpha channel or 32-bit with transparency support is used. Using unsupported PNG formats or excessive compression will result in the animation not running and the system will show a black screen or default logo. The size of each frame must correspond to the resolution specified in desc.txt.

In the description file, you can also set the playback cycle. Some parts of the animation can be played once (for example, a brand logo), while others can be looped until the system is completely loaded. The flexibility of this format allows you to create complex loading scripts that simulate the operation of the interface before it actually launches.

• 📄 desc.txt: the main settings file with resolution and frame rate parameters.
• 📁 part0: the first part of the animation, often the manufacturer's logo.
• 📁 part1: the second part, usually a looped waiting animation.
• 🖼️ Frames: images in PNG format without compression inside the archive.

⚠️ Attention: When creating your own archive, make sure that the compression method for PNG files is set to "Store" (no compression). Using Deflate for images inside a ZIP will make the animation unreadable for Android.

How to edit desc.txt?

The desc.txt file contains lines like: "width height frame_rate". For example, "1080 1920 30" means FullHD screen and 30 frames per second. Next are the lines "p 1 0 part0", where 'p' means part, '1' is the number of repetitions (0 is infinite), and 'part0' is the folder name.

Replacing animations via ADB and computer

For users who prefer to work with a computer, the toolkit ADB (Android Debug Bridge) provides a powerful and safe way to replace a file animation. This method does not require installing file managers on the device itself and allows you to control the data transfer process. Before you start, you need to enable USB debugging in the "For Developers" menu.

The first step is to obtain superuser rights in the ADB session. Enter the command adb rootif supported by your firmware, or use adb shell followed by su. After this, you need to mount the system partition in write mode if you plan to replace the file in /system. However, as mentioned earlier, it is easier and more reliable to work with the partition /data.

The process of replacing a file in a local directory is as follows. First, delete the old file (if there is one), then download the new archive from your computer. It is important to check the permissions of the downloaded file so that the system can read it. Usually the rights 644 (read for everyone, write for the owner) are sufficient.

adb push bootanimation.zip /data/local/
adb shell chmod 644 /data/local/bootanimation
adb shell reboot

If you decide to replace a system file, the procedure becomes more complicated. You will need to run the command adb remount or manually remount the partition via mount -o rw,remount /system. After copying the file, be sure to restore the original access rights and owner, otherwise the system may refuse to boot. An error in access rights is one of the most common causes of problems after modification.

Installation via custom recovery (TWRP)

Owners devices with custom recovery installed, such as TWRP or OrangeFoxhave the most convenient tool for modifying system files. In this mode, partitions are unmounted or writable without restrictions, which simplifies the replacement process. In addition, in case of an error, you can always restore the backup copy of the System partition.

The easiest way is to use a ready-made ZIP archive with animation firmware, which can be installed as a regular mod. The installation script (updater-script) will automatically detect the desired directory and copy the file with the correct rights. This eliminates the need to manually enter commands in the recovery terminal.

If you want to install the file manually, go to Advanced → File Manager in the TWRP menu. Go to the directory /data/local/ or /system/media/, delete the existing file and use the button Add to load a new archive from internal memory or USB drive. After completing the operation, do not forget to set the correct permissions (Permissions) on the file: rw-r--r-- (644).

The advantage of the recovery method is the ability to create a full backup before making changes. If the new animation causes a black screen on boot, you can go into recovery and restore the original file in a couple of minutes. This makes the method as safe as possible for experimenting with the visual style of the device.

⚠️ Attention: Recovery interfaces may differ depending on the version of TWRP and the device. Make sure that you copy the file exactly to the file system that corresponds to your current state (Data or System), and not to the temporary recovery storage cache.

Possible problems and errors during modification

Despite the apparent simplicity of replacing a picture, the process is often accompanied by technical difficulties. The most common problem is a "black screen" instead of animation. This usually means that the system was unable to unpack the archive or the image format inside is incompatible with the graphics accelerator of your smartphone.

Another common mistake is ignoring the new file and starting a standard animation. This occurs if access rights are violated. The file must be readable for the user system or root. Also, the problem may lie in the name: the file must be named strictly bootanimation.zip, any additional characters will lead to the system not seeing it.

In rare cases, incorrect animation can lead to a delay in loading the system. If the archive is too large or contains ultra-high-resolution frames, the processor may spend significant time decoding before transferring control to the application loader. This is especially true for budget devices with weak hardware.

If, after replacing the animation, the device goes into a cyclic reboot (bootloop), do not panic. In most cases, it is enough to boot into Recovery mode, go to the file manager and delete the file bootanimation.zip from the folder /data/local/. The system will automatically pick up the backup copy from the system partition, and the phone will boot normally.

• ❌ Black screen: incorrect PNG format or compression inside ZIP.
• ❌ Old animation: incorrect permissions.
• ❌ Bootloop: critical error in desc.txt or a broken archive.
• ❌ Flickering: the frame rate in desc.txt does not match the capabilities of the screen.

Is it possible disable loading animation completely?

Yes, it is possible. To do this, you need to delete the file bootanimation.zip from all possible directories (/system/media/ and /data/local/). As a result, when you turn it on, you will only see the manufacturer’s logo (which is hardwired into the bootloader) and will immediately go to the password entry screen or desktop. Some users create an empty stub file, but complete deletion is more effective.

Why doesn't my animation work on Android 13/14?

New versions of Android have tightened the requirements for security and system integrity (Project Treble, dynamic partitions). The file in /system can be protected by bootloader verification (AVB). It is recommended to use only the path /data/local/, since it is not verified by the system signature and has priority for user modifications.

How to find the exact screen resolution for desc.txt?

You can find out the resolution via ADB command adb shell wm size. This information can also be found in the device specifications on the manufacturer's website or in applications like CPU-Z. In the file desc.txt the first two numbers must exactly match the physical resolution of your display.

Is it safe to change bootanimation on a locked bootloader?

If the bootloader is locked, you will not be able to get root access and write the file to the system partition. However, on some devices the substitution mechanism works through /data/local/ even without unlocking, if there are vulnerabilities or specific developer settings. But in most cases, a full replacement requires unlocking the bootloader, which will reset all data from the phone.

Where can I download ready-made bootanimation files?

There are many forums and repositories, such as XDA Developers, where enthusiasts share their work. You can also find ready-made packages in theme stores for specific launchers or custom firmware. When downloading, always check the comments to make sure the animation is compatible with your screen resolution.