Update TBox Firmware Locally With FOTA and a microSD Card

What this guide covers

Carlinkit pushes only some firmware builds over the air. The rest, including many fixes owners need, are installed by hand: you put the update file on a microSD card and tell the box’s FOTA Update app to install it from there. This is called a local update.

It works the same way on the TBox Plus, Ambient, UHD and Ultra 1–4. It is labelled Advanced because a wrong file or an interrupted install can leave the box needing recovery, but the procedure itself is short. Read the whole guide once before starting, and keep the box on a stable power supply for the full install.

Before you start: choose the right file

Firmware is specific to the model, and on the TBox Plus also to the variant. A file for the wrong unit will be rejected at best. Identify your box first; which TBox do I have shows how to tell the models apart from Settings → About, the case and the LEDs.

Should you update at all?

Update when a build fixes something you actually have, or when the manufacturer or your seller asks you to. A firmware update is the single most common moment for something new to break, and the community’s own advice to a happy owner asking whether to flash a new build was blunt: if everything works, leave it.

Good reasons to update:

• A known problem on your unit is listed as fixed in a newer build. The firmware tracker lists the builds owners discuss and what changed.
• Your box was bought recently and still has its factory firmware from months ago, and you are having problems that later builds address.
• Support asked you to update before they will look at a fault.

Reasons to wait a week or two:

• The build was released days ago and nobody with your model has reported on it yet.
• You rely on the box for a long trip in the next few days.
• You have modified the system (root, multitouch, edited system files). Those changes have to be undone before an update, as described in the troubleshooting section below.

What an update keeps and what it changes

A local update installs a new system over the old one. On the builds owners discussed, installed apps, logins and the home screen survived an update from the same manufacturer; owners who moved between official builds and back did not need to reinstall everything.

The default home app is the one thing you change on purpose: you set the stock launcher before updating, so set your own launcher again afterwards. It is also worth checking the settings that live in the engineering menu (start-up delay, navigation bar, temperature display) once the new build is running, because they decide whether the box starts cleanly in the car.

Before you begin, take three minutes to protect yourself:

1. Photograph your engineering-menu settings (Settings → Other → Factory settings → 4545) so you can restore them.
2. Write down the apps you would need to reinstall and check you know their passwords.
3. Note the current firmware date from Settings → About, so you can find the matching file if you want to go back.

Two version rules came up repeatedly in the community FAQ. On the TBox Plus EAU, the move from Android 12 to Android 13 required the 30 June 2023 Android 12 build first; some owners skipped straight from Android 11 to 13 without trouble, but the advice was not to. On every model, read the release notes: if the new build only fixes something you do not use, waiting a few weeks for other owners’ reports costs you nothing.

Steps

Verify it worked

Open Settings → About and confirm the build date. Then check the things that most often change between builds:

• Connect to the car in your usual protocol and confirm the head unit shows the box.
• Insert or check the SIM: open a web page with Wi-Fi off. Ambient owners reported SIM detection changes between 2025 and 2026 builds.
• Play music with navigation running for ten minutes and listen for crackle.
• Set your preferred launcher as the default home app again, if you use one.

If any of those fail and they worked before, note it, and look up the symptom on the fixes page before rolling back.

Undo / rollback

You can install an older official build with the same Local update steps, as long as it is for your exact model. An Ambient owner whose SIM stopped being detected on 2026 builds went back to a 2025 build, and the SIM worked again at once.

If the box no longer boots at all, the FOTA app is out of reach and you need a recovery method instead. For the TBox Ultra that is a QFIL flash of the official recovery images, described in recover a bricked TBox Ultra with QFIL. That guide is Brick risk: read it fully first.

Troubleshooting this guide

“Update fail” or “upgrade failed” right after you select the file. In order of how often owners hit it: the download was corrupt (download again on a stable connection and compare sizes), the card is not FAT32, or the file is for a different model or variant. Ultra 4 owners have a dedicated page: “Upgrade failed” on TBox Ultra.

Nothing happens, or the FOTA app does not see the file. The card must be in the box’s own slot, and the file must be in the root of the card. Remove and reinsert the card while the box is on, then open Local update again. If the card still is not offered, install from internal storage as in the last step above.

The update refuses to install after you used ADB tweaks. If you ever disabled verity or remounted the system read-write over ADB (for multitouch, GPS config edits or similar), the updater rejects the system. An Ambient owner in that situation connected over ADB, ran the command below, and the update went through:

adb enable-verity
adb reboot

Then repeat the local update. The full explanation is in firmware update fails after disabling verity.

The install stops at a percentage. Wait at least 20 minutes before assuming it has failed, and make sure the box has power the whole time. If it restarts without installing, free more storage (more than 3 GB) and try again.

Online FOTA says there is no internet when there is. Use the local method in this guide; it does not need the update server at all.

The box boots but behaves strangely. Do not factory reset straight away. Clear the cache with engineering code 110144 (Settings → Other → Factory settings → 110144) and restart; reset only if problems stay.