Skip to content
AI Box Fix

Firmware & recoveryReviewed

Set the Stock Launcher Before Any Firmware Update

Updating an AI box with CarCar or another launcher as default can end in a black screen. Switch to the stock launcher first. Carlinkit, Ottocast, Ownice.

Quick answer

Before every firmware update, open Settings → Apps → Default apps → Home app, choose the stock launcher, press Home once to check it appears, then update and switch back afterwards. That is the advice Carlinkit's sellers gave the community, and an Ottocast Picasou 3 owner who skipped it got a black screen and had to roll back.

Symptoms

  • You use CarCar Launcher, Agama or another launcher as your default home screen and are about to update
  • After an update made with a third-party launcher as default, the box boots to a black screen
  • The box hangs on the boot logo after the stock launcher was disabled or removed
  • An update fails or the box resets itself during an update

Applies to

Connection to the car
CarPlay and Android Auto
Firmware in confirmed reports
Ottocast Picasou 3: 2024-11
Highest risk on this page
Brick risk
Status
Workaround confirmed by the community

Why it happens

A firmware update replaces the Android system under your apps, then reboots straight into whatever app is set as the home screen. The stock launcher is built for that system. A third-party launcher is not part of the update, and if it cannot start cleanly on the new build, the box comes up with nothing on screen.

Carlinkit’s sellers told the community that updating with a third-party launcher as the default can make the update fail, wipe the box or leave it unable to boot. The warning was passed on for boxes on the same Qualcomm platform from several brands, including Carlinkit, Ownice, ApplePie and Ottocast, and the forum’s firmware posts for the TBox Plus and Ownice A5 repeated it through 2025.

To be fair to third-party launchers: many owners report updating with CarCar Launcher as the default and having no problem, and some believe the issue was fixed in builds from 2024 onwards. Nobody outside the manufacturer has explained exactly which builds are affected. Switching the default costs two minutes; recovering a box that boots to black costs an evening.

Fixes, ranked

Switch the default home app to the stock launcher before updating

  • Safe
  • Time: 2 minutes
  • Recommended in the community FAQ
  1. Open Settings → Apps → Default apps → Home app. On older Carlinkit firmware the same choice is under Settings → Apps → More → Default apps, or inside your launcher’s own settings.
  2. Select the stock launcher, the one the box came with. On TBox Ultra it is listed as Quickstep.
  3. Press Home and restart the box once. Check that the stock home screen appears at start, not your launcher.
  4. Run the firmware update.
  5. After the update, set your launcher as the default home app again.

The update itself is an advanced step with its own guide: update TBox firmware from a memory card. This advice comes from the community FAQ, which relayed it from Carlinkit’s sellers; no owner reported back on it directly, but the Picasou 3 owner in the next fix shows what happens when it is skipped.

You do not need to uninstall the third-party launcher, and its licence and settings stay in place. On TBox Ultra builds before 26 Dec 2025, owners also added their launcher under Settings → Other → App loading to make it start; the Ultra owners’ FAQ says to set that entry back to “none” once you use the normal default-app setting.

Roll back with the previous firmware if the box boots to black

  • Advanced
  • Time: 30 minutes
  • Worked for 1 of 1 report

Warranty warning: this uses developer or engineering access. Follow the undo steps afterwards; some sellers refuse warranty claims on units with debugging left enabled.

  1. Copy the previous official firmware for your box, unchanged, to the root of a FAT32 microSD card.
  2. Insert the card into the box.
  3. Power the box from a computer’s USB port instead of the car.
  4. Wait about 20 minutes, until the status light stops blinking red.
  5. Remove the card before you connect the box to the car again.
  6. Set the stock launcher as default, then update again if you still want the new build.

An Ottocast Picasou 3 owner updated with CarCar Launcher as the default and got a black screen. Putting the previous build on a card and leaving the box on computer power for about 20 minutes rolled it back, and the same owner later talked another Ottocast owner through the same recovery. The steps above apply to Ottocast’s automatic card update; on Carlinkit boxes that still boot, use FOTA Update → Local update instead.

If you disabled the stock launcher and the box hangs at the logo, reflash with QFIL

  • Brick risk
  • Time: 1–2 hours
  • Worked for 1 of 1 report

Warranty warning: this changes system partitions. A wrong file or an interrupted step can leave the box unbootable, and manufacturers treat it as outside warranty. Back up first and keep the undo steps open.

  1. Request the official recovery package for your exact model from Carlinkit support ([email protected]).
  2. Follow recover a TBox Ultra with QFIL to flash it from a Windows PC.
  3. After recovery, set your launcher as the default home app through Settings. Do not disable the stock one again.

A TBox Ultra owner who disliked the stock launcher disabled it over ADB. After the next restart the box hung on the logo. The owner tried the SD-card factory-reset file for 5 and then 10 minutes, on both FAT and exFAT cards, and the box did not reset; only a QFIL recovery brought it back.

Things to try (unverified)

  • If the box shows a black screen but music plays, reach Settings through the notification shade. On a TBox Ambient whose launcher hung, an experienced owner advised pulling down the top shade, which can take several tries, and opening Settings from there to change the default home app. The asker did not confirm.
  • Uninstall the launcher before the update instead of switching the default. Some owners do this to be sure. It is not needed and loses your launcher settings; switching the default does the same job.
  • Reset to factory before every update. One experienced owner always resets before updating and has never had a problem. It is far more work than switching the default, and the reset page explains when it is worth it.

If nothing works

Write down the box model and firmware date from Settings → About (or the box label if it no longer boots), the launcher that was default, the build you were installing and what the screen and status light do now. Film the start-up sequence.

Send that to the manufacturer: Carlinkit at [email protected], Ottocast at [email protected], Ownice and ApplePie through their seller. Ask for the recovery file or procedure for your exact model, not a newer update. If the box does not respond to recovery either, a warranty repair or a replacement is the honest answer, and start here compares the box families. Third-party launcher issues that are not about updates are covered in third-party launcher stuck on “loading phone”.

Parts the fixes above need

  • microSD card (32 GB or smaller, formatted FAT32)

    Local firmware updates, reset files and protocol-switch files are read from a FAT32 card.

Related fixes

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 2 community reports on Ottocast Picasou 3.
  • 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.