Skip to content
AI Box Fix

Apps & launchersReviewed

Change the Boot Animation on a Carlinkit TBox

Replace the start-up animation on a Carlinkit TBox Ambient or Plus: put your bootanimation.zip on a FAT32 microSD card and insert it into the running box.

Illustration: Carlinkit TBox Ambient between a phone and a car screen

Quick answer

To change the boot animation on a Carlinkit TBox, copy a correctly sized bootanimation.zip to the root of a FAT32 microSD card and insert the card while the box is already running; it installs itself within seconds and plays on the next start-up. Four owners confirmed this on the Ambient and Plus. A card left in at power-on does nothing.

Before you start

  • Your exact Carlinkit model (Settings → About)
  • A bootanimation.zip built for your head-unit screen resolution
  • A microSD card of 32 GB or less, formatted FAT32
  • A computer with a card reader to format the card and copy the file

Time: about 20 minutes. Tools: computer with a microSD card reader, microSD card (FAT32).

Applies to

Connection to the car
CarPlay and Android Auto
Highest risk on this page
Low risk

Why the card only installs into a running box

The box looks for a bootanimation.zip on an inserted microSD card only while it is running. When it finds one, it copies the animation into the system and uses it from the next start-up on. A card that is already in the slot when you power the box on is not scanned the same way, so nothing changes and you are left staring at the stock animation.

That single detail is what trips most people up. One owner put the file in the card root, inserted the card and powered the box on, saw no change, and only got it working once he turned the box on first and inserted the card afterwards. An Ambient 6225 owner described the same behaviour: drop a correctly formatted file in the card root, slide the card into the already-running box, and the animation installs itself within seconds with nothing else to do.

To tell your exact model apart before you start, see which TBox do I have.

Build a bootanimation.zip that fits your screen

A boot animation is a standard Android bootanimation.zip. You can make your own or adapt an existing one, but it has to match your hardware or you get a black or stretched screen. This site does not host or link animation files; build or source your own to these rules:

  • Match the resolution to the head-unit screen. The frames must be the pixel size of your car’s display (for example 1280×720 or 800×480). The wrong size shows as a black screen or a squashed, stretched image. If you are not sure of your screen’s resolution, it is the resolution of the display in the car, not of the box.
  • Keep the standard layout. The zip contains a desc.txt and one or more part0, part1 folders of numbered image frames. The first line of desc.txt is width height fps; each part line is like p 1 0 part0.
  • Store the zip, do not compress it. Build the archive with no compression (stored), the way Android expects a boot animation.
  • Leave the sound file in place. On at least one box, deleting the audio file from the first part folder made the animation misbehave, so keep it unless you have a reason to remove it.

The length of the clip is tied to how long the box takes to boot: the animation plays in parallel and is cut off when the box has finished loading. It does not slow the boot down. Changing the play type in desc.txt so the clip runs to completion is something owners have tried with mixed results, so treat it as optional.

Steps

Install the animation from a microSD card

  • Low risk
  • Time: 10 minutes
  • Worked for 4 of 5 reports
  1. Format a microSD card (32 GB or less) as FAT32 on your computer.
  2. Copy your bootanimation.zip to the root of the card, not inside a folder. Make sure it is named exactly bootanimation.zip and that no older animation file is left on the card.
  3. Eject the card safely from the computer.
  4. Power the box on and wait until the launcher has fully loaded.
  5. Insert the card into the slot on the box, not the car’s head unit.
  6. Wait about 30 seconds for the box to copy the animation in, then restart the box.
  7. On the next start-up the new animation should play. You can then remove the card.

Four owners reported this working: two on the method’s key point of inserting the card into an already-running box, one on a TBox Plus, and one who got it right only after rebuilding the file to match his screen resolution. One owner reported that neither a card nor internal memory worked on his unit at all; if that is you, the file or its resolution is the first thing to re-check.

Verify it worked

Restart the box and watch the start-up sequence from the moment it powers on:

  • The new animation should play in place of the stock one.
  • If the screen is black or the image is stretched, the resolution does not match your display; rebuild the file at the correct size and install it again.
  • If the stock animation is still there, the card was most likely in at power-on, the file was not in the card root, or it was not named bootanimation.zip. Remove the card, boot the box, and insert the card again.

Undo / rollback

To go back, install a different animation the same way, or a copy of the stock one if you saved it. Carlinkit does not publish the stock bootanimation.zip as a separate download; it lives inside the firmware, so a clean restore means pulling it from a firmware build or re-flashing.

If you want a quick on/off switch instead, owners install the animation as a Magisk module and disable the module to return to stock. That route needs root and carries real risk; it is covered in root a Carlinkit TBox with Magisk and QFIL. It is optional and not needed for the card method above.

Other ways owners installed it

  • Over ADB. One owner pushed the file straight to the system with adb push bootanimation.zip /system/media/. It worked on his box without root, but writing to the system partition is Advanced and depends on the box allowing it, so it is not a general method. If you want to try ADB, set it up first with enable ADB on the AI box.
  • As a Magisk module. The optional root route above, useful mainly because you can toggle back to the stock animation by disabling the module.

Troubleshooting this guide

The animation did not change. The card was almost certainly in the box when you powered it on. Turn the box off, remove the card, power it on fully, then insert the card and wait. Check the file is in the card root and named exactly bootanimation.zip, with no second animation file alongside it.

The box shows a black screen at start-up after the change. The frame resolution does not match your screen. Rebuild the bootanimation.zip at your display’s pixel size and install it again; the screen is not broken.

The box reboots during or right after the animation. This has been reported when a custom animation was built wrong (for example missing or extra files) rather than from the install method itself. Replace it with a known-good animation at the correct resolution. If the box will not boot far enough to read a card at all, you need a recovery flash; see recover a TBox Plus or Ambient with QFIL.

You would rather not touch the start-up screen but want a different look. Changing the home screen or navigation default is a separate, safer change; see change the home screen or navigation app.

Nothing here helped. Note your exact model and firmware date (Settings → About) and the screen resolution, and ask Carlinkit support through their contact page. Do not install animation files from unknown sources.

What owners said

“The Carlinkit Ambient 6225 replaces the boot animation without problems if you put [the animation file], in the right format, in the root of the SD card (better not delete the sound file from folder 0).”
Worked: Animation file in the card root
Owner, Carlinkit TBox Ambient, May 2025
“Found it. You have to turn the box on first and then insert the SD card; that way it worked.”
Worked: Insert the card after the box is on
Owner, Mar 2024
“Great, it worked. […] In the end I found a boot animation elsewhere in the right resolution.”
Worked: Animation in the screen's resolution
Owner, Dec 2023

Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.

Questions owners ask

Does the archive have to be named exactly bootanimation.zip?

Yes. The file in the card root must be named bootanimation.zip, with no other copy left on the card. Owners who left the old file or a wrong name saw the animation not change.

Will a long animation make the box boot more slowly?

No. The animation plays alongside the boot, not before it, so it does not add to the start-up time. If the box finishes booting first, the animation is cut short.

Can I put it in the box's internal storage instead of a card?

The card into a running box is the route owners confirmed. One owner reported that neither the card nor internal memory worked on his unit, so if the card fails, that is the method to trust.

Do I need root to change the boot animation?

No. The card method needs no root. A Magisk module is an optional route that does need root; its one advantage is that you can switch back to the stock animation by disabling it.

Parts the fixes above need

  • Product photo from the AliExpress listing: microSD card (32 GB, formatted FAT32)

    microSD card (32 GB, formatted FAT32)

    Local firmware updates, reset files and protocol-switch files are read from a FAT32 card. A high-endurance 32 GB card copes with car heat; pick the 32 GB size.

    AliExpress

Some links above are affiliate links: if you buy through them we may earn a commission at no extra cost to you. It never changes which fix we rank first. Product photos are the sellers' own, from the AliExpress listing. Disclosure.

Did this work for you?

Tell us which fix worked (or didn't), with your box, firmware date and car. Reports are how fixes get confirmed and re-ranked.

Send a report

Changelog

  • Last reviewed against new community reports:
  • Confirmed by 4 community reports on Carlinkit TBox Ambient, Carlinkit TBox Plus.
  • Page updated:

"Confirmed" means a community member reported that the fix worked on their unit. We have not tested it on our own hardware. How we verify.

Evidence behind these counts (1 case)

One row per case: a device, a symptom and a fix, merged from owner reports. An owner counts once per fix. Reports with no outcome yet are not counted. Forum and chat message references are kept on file but not published, to protect owners' privacy; public Reddit and YouTube sources are linked.

CaseConfirmed onResultSource
case-1605Model not stated4 worked, 1 did notOwner discussion threads, 4 messages