Skip to content
AI Box Fix

Firmware & recoveryReviewed

TBox Ultra Black Screen After Boot: Screen Sleep, Nav Bar, QFIL

TBox Ultra shows a black screen after the boot logo? Turn off the navigation bar, stop the screen from sleeping, or recover with QFIL. Ultra 1, 2, 3 and 4.

Illustration: Carlinkit TBox Ultra 4 on a car's console at night

Quick answer

If you hear sound but see black in Android Auto, turn off the box's system navigation bar and clear the cache with code 110144; that ended the black starts for two of three Ultra owners. If the screen goes dark on its own, stop it sleeping (adaptive sleep Never, or Stay awake in Developer options), and if the box never gets past the logo, recover it with QFIL.

Symptoms

  • After the Carlinkit logo or "loading" text the screen stays black
  • Navigation voice or music plays, but the picture is black, especially in Android Auto
  • The screen goes dark a while after start and stays dark until you reconnect
  • The black screen started after you changed a display, launcher or developer setting
  • It happens only on some starts and a reconnect fixes it

Applies to

Connection to the car
CarPlay and Android Auto
Head units mentioned in reports
BMW iDrive 7 / 8; Various Generic Android head units
Firmware in confirmed reports
Carlinkit TBox Ultra 4: 2025-10-21
Highest risk on this page
Brick risk
Status
Workaround confirmed by the community

Why it happens

“Black screen” covers several faults with one look. The most common is that the box has started and is running, but the picture never reaches the car: you hear navigation and music, and the interface still reacts to swipes under the black layer. Owners linked this to the box’s own side navigation bar and to stale cache on Android Auto starts.

The second is ordinary Android screen sleep. The TBox Ultra has no power button, so if adaptive sleep or the screen timeout switches the display off, nothing wakes it. That is why the Ultra owners’ FAQ puts adaptive sleep first, and why an owner who switched off USB debugging suddenly met a dark screen.

The third is a box that does not finish booting at all, typically after a setting its launcher cannot handle, a disabled system app, or a bad update. Only a reset or a reflash helps there. On some BMWs with wireless CarPlay, a reply from the manufacturer’s side pointed to a firmware bug that needs a newer build.

Fixes, ranked

Turn off the system navigation bar and clear the cache

  • Advanced
  • Time: 5 minutes
  • Worked for 2 of 3 reports

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. Open Settings → Display → System navigation bar and set it to Off. On older builds the switch is under Settings → Other → Factory settings → 4545 → Other.
  2. Go back to Settings → Other → Factory settings, enter 110144 and tap OK to clear the cache.
  3. Unplug the box and connect it again.
  4. Start the car several times over a few days and note whether the black start returns.
Engineering menu Other tab with the system navigation bar switched off. Reconstructed screen, labels may differ by firmware.

A TBox Ultra 2 owner, running a projection app on an Android head unit, had sound with no picture on some starts. Start-up delays of up to 60 seconds helped only partly; turning off the navigation bar and clearing the cache made every start stable without delays. An Ultra 1 owner with the same set-up applied both changes and had no black screen afterwards. A third Ultra 1 owner did both several times and still sees black starts. More on the bar itself is in remove the navigation bar and floating button.

Keep the screen awake with Developer options

  • Low risk
  • Time: 5 minutes
  • Worked for 1 of 1 report
  1. If the screen is dark, wake it with a Bluetooth keyboard paired to the box, or reconnect until it starts with a picture.
  2. Open Settings → About and tap Build number seven times to enable Developer options, if they are not already on.
  3. Open Developer options and turn on Stay awake (keep the screen on while charging).
  4. Restart the box and check that the screen stays on.

An Ultra 1 owner turned off USB debugging and from then on saw only a black screen after boot. The box had decided to switch the display off, and the only ways to wake it were a power button the Ultra does not have or a Bluetooth keyboard. Turning on Stay awake in Developer options fixed it.

Set adaptive sleep to Never; reset from the card if Settings is unreachable

  • Advanced
  • Time: 15 minutes
  • Worked for 0 of 2 reports
  • Recommended in the community FAQ

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. Open Settings, type adaptive sleep in the search field and set it to Never.
  2. In the same place, tick do not turn off while looking at the screen.
  3. If the screen stays black and you cannot reach Settings, reconnect the box several times; if it boots once, undo whatever display, launcher or developer setting you changed last.
  4. If it never boots to a picture, ask Carlinkit support ([email protected]) for the SD-card factory-reset method for your exact model, copy what they send to a FAT32 card, insert it and power the box.

This is the black-screen fix in the Ultra owners’ FAQ, and it remains the first thing to check when the display goes dark on its own, but no owner has yet reported it working. Two owners whose black screens came only on some Android Auto connections said the setting changed nothing; both recover by unplugging the box, waiting about ten seconds and reconnecting. A TBox Ultra 4 owner whose box went black after changing the screen width with a third-party launcher asked for a way to reset without the interface; the forum pointed to the SD-card reset file, but that owner ended up recovering with QFIL.

Recover a box that never boots 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.
  2. Install Qualcomm USB drivers and QFIL on a Windows PC.
  3. Put the box into EDL mode and connect it by USB.
  4. Load the full recovery set: the programmer file and the XML files with storage type UFS. The programmer alone is not enough.
  5. Flash, wait for completion, then start the box in the car.

The TBox Ultra 4 owner above first got a “Sahara protocol error” when loading only the programmer file. With the complete official image set, the flash went through and the box worked. Afterwards the no-internet exclamation mark appeared and had to be dealt with separately. Follow recover a TBox Ultra with QFIL step by step.

Things to try (unverified)

  • BMW with wireless CarPlay. A reply from the manufacturer’s side said some wireless-CarPlay BMWs show a black screen that needs a firmware update, while a wired-CarPlay black screen needs a reset or QFIL. An Ultra 3 owner on iDrive 8.5 found that the 28 Jun 2026 build worked with wireless CarPlay and the 22 Jul build lost it. No owner has confirmed a fixed build yet.
  • Pull down the notification shade. On a black screen with sound, owners advise swiping down from the top edge, sometimes several times, to reach Settings and undo a recent change.
  • Do not disable the stock launcher. A TBox Ultra owner who disabled it over ADB was stuck at the logo, and the SD-card reset file did not help; see stock launcher before a firmware update.

If nothing works

Record the model and firmware date (from Settings → About if it still starts, otherwise the label), the car and head unit, wired or wireless connection, CarPlay or Android Auto, what you changed last, and whether sound plays during the black screen. A short video from power-on to black is the most useful thing you can send.

Send it to Carlinkit support at [email protected]. If the box boots but behaves oddly afterwards, see factory reset after a firmware update. If it stays black after a QFIL recovery with official files, the fault is likely hardware, and a warranty claim or replacement is the honest answer; start here compares the box families.

If the screen is an Android head unit (TEYES and similar) and not the car’s factory screen, the unit is one more link in the chain: the TEYES hub lists what owners of those units fixed, counted separately from the AI box reports on this page.

What owners said

“Then I turned off the system navigation bar (the box's own side menu) and cleared the cache (code 110144): start-ups became stable even without start-up delays.”
Worked: Navigation bar off and cache cleared
Owner, Carlinkit TBox Ultra 2, Jul 2026
“Update: I found out the box had decided to turn the screen off. […] In Developer options I managed to turn on the "don't turn off the screen while charging" toggle.”
Worked: Stay awake turned on in Developer options
Owner, Carlinkit TBox Ultra, Mar 2026
“From time to time, when Android Auto starts: a black screen. […] I applied the settings from the FAQ straight away and they had no effect on that screen appearing.”
Did not help: Adaptive sleep set to Never
Owner, Apr 2026

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

Questions owners ask

The screen is black but music and navigation voice still play. Is the box dead?

No. The box has started; only the picture is missing. Owners could still swipe in the interface underneath. Work through the navigation-bar and screen-sleep fixes before anything stronger.

Is there a button combination that factory resets a TBox Ultra?

The button on the case switches CarPlay and Android Auto, it does not reset. When Settings is unreachable, ask Carlinkit support for the SD-card reset method for your model, or use QFIL recovery.

My BMW with wireless CarPlay shows black with the Ultra. What then?

A reply from the manufacturer's side said some wireless-CarPlay BMWs need a newer box firmware. One Ultra 3 owner on iDrive 8.5 found the 28 Jun 2026 build worked with wireless CarPlay and a later one did not.

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.

If none of these fixes work

Try every free fix above first. Each of these needs a car whose screen already runs wired CarPlay or Android Auto. We have not tested them: check the seller's compatibility list for your car and head unit, and that the listing shows the exact model named here, before you buy.

  • Wireless CarPlay / Android Auto adapter (Carlinkit Mini Ultra 3)

    If you only use the box to get CarPlay or Android Auto without a cable, a plain wireless adapter has no Android system to update, overheat or crash.

    AliExpress

  • Replacement AI box (Carlinkit, Android 13, SM6225)

    If the box is out of warranty and still fails after the fixes above, another Carlinkit box keeps your apps on the car screen. It needs wired CarPlay or Android Auto in the car. Pick the NA variant for North American cars, EAU elsewhere.

    AliExpress

  • Replacement from another maker (Ottocast P3 Pro)

    If you would rather switch brands, Ottocast's P3 Pro runs Android 13 and has HDMI out. It needs the connection protocol Ottocast lists for your car. The listing opens on a cheaper Mini adapter: select the P3 Pro option and check the picture and name before you pay.

    AliExpress

Affiliate links: we may earn a commission at no extra cost to you. 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 Ultra 2, Carlinkit TBox Ultra, Carlinkit TBox Ultra 4.
  • 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 (5 cases)

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-0043Model not stated1 workedOwner discussion threads, 2 messages
case-0044Model not statedRecommended in the FAQ (not counted)Community FAQ, 4 messages
case-4016Carlinkit TBox Ultra1 workedOwner discussion threads, 2 messages
case-4017Carlinkit TBox Ultra 2; Carlinkit TBox Ultra2 worked, 1 did notOwner discussion threads, 7 messages
case-4022Model not stated0 worked, 2 did notOwner discussion threads, 4 messages