Firmware & recoveryReviewed
Recover a Bricked TBox Plus, Ambient or UHD With QFIL
TBox Plus, Ambient or UHD won't boot? Flash Carlinkit's official recovery package with QFIL in EDL mode: right variant, eMMC or UFS, every XML pass.
Carlinkit TBox PlusCarlinkit TBox AmbientCarlinkit TBox UHD
Quick answer
To revive a Carlinkit TBox Plus, Ambient or UHD that no longer boots, flash Carlinkit's official recovery package for your exact variant with QFIL in EDL mode, with the matching programmer and eMMC or UFS setting. If it flashes but stays dead, owners flashed an older base package, then the Android 13 one: seven boxes came back.
Before you start
- A Windows 10 or 11 PC with a free USB port and administrator rights
- The official QFIL recovery package for your exact model, variant and chip, from Carlinkit support
- The Qualcomm USB driver and the QPST package (QFIL ships inside it)
- The USB data cable that came with the box, or another known-good data cable
- A pin or paper clip for the pin-hole button
Time: about 90 minutes. Tools: Windows PC, QPST / QFIL, Qualcomm USB driver, USB data cable, paper clip.
Applies to
- Connection to the car
- CarPlay and Android Auto
- Firmware in confirmed reports
- Carlinkit TBox Plus: 2024-07-04; Carlinkit TBox Ambient: 2023
- Highest risk on this page
- Brick risk
Is your box really bricked?
A bricked TBox never finishes booting: the head unit never shows it, the LEDs stay in one state or blink without change, and no menu can be reached. Several faults look like that and are fixed without QFIL, so rule them out first.
- Wrong protocol. The pin-hole button also switches CarPlay and Android Auto. A box pressed “to reset it” may only be in a protocol the car does not support; see switch the box’s protocol.
- ADB mode left on. After engineering code 142618 the box talks to computers, not cars: “Device not supported” after enabling ADB.
- The car, not the box. If an Android phone works on the same cable and port, check the car does not detect the AI box as well. Two owners below checked the cable and head unit before flashing.
- The box still starts. If you can reach Settings and the FOTA app, a local firmware update or a factory reset after an update is safer than anything here.
QFIL is for the box that no normal route reaches, or one left in a state its menus cannot undo: one TBox Plus owner had hidden the Settings icon by accident and had no other way back.
What the recovery does
Every TBox in this family runs on a Qualcomm chip with an emergency download mode (EDL) in read-only memory. In EDL the box shows up on a PC as Qualcomm HS-USB QDLoader 9008, however broken the system above it is. QFIL, Qualcomm’s flashing tool, sends the box a small loader (the firehose programmer) and then rewrites every partition listed in the package’s rawprogram XML files; the patch files fix up the partition table.
So the package must match the box exactly: a wrong programmer or memory type fails before anything is written, and images for another variant can write cleanly and still not boot. The TBox Ultra QFIL guide explains the mechanism in more detail.
Which recovery package fits your box?
Carlinkit makes recovery packages per model, variant and chip, and the chip lines do not mix. Check which TBox do I have before you ask for one.
- TBox Plus EM (668). Back label reads EM. Owners found these units with either eMMC or UFS memory, and the recovery packages they used came as six XML pairs,
rawprogram0withpatch0up torawprogram5withpatch5. - TBox Plus EAU (138). Back label reads EAU, JP or NA; the model string in Settings → About contains 138. Owners described its recovery as a single pass. The label alone is not proof: owners found boxes labelled EAU that are EM 668 inside (TBox Plus sold as EAU), so check the version string before you ask for a package.
- TBox Ambient and TBox UHD. Most current units use the SM6225 (QCM6225); earlier batches used SDM660 or QCM6125, each with its own line. Most SM6225 Ambient owners needed UFS, and one owner’s SM6225 package held both a UFS and an eMMC version, each with its own programmer. No owner in these reports flashed a UHD; it shares the Ambient’s chip lines and procedure, so ask support for the UHD package by name.
If you cannot open Settings, the chip is usually named on the product listing. Package dates matter too: TBox Plus packages exist for Android 11, 12 and 13, and owners used Ambient sets from 2023 to 2025.
Unzip the package to a short path with only Latin letters and no spaces, for example C:\recovery\plus668. Inside you should find a programmer named like prog_firehose_ddr.elf, one or more rawprogram*.xml files with matching patch*.xml files, the partition images, and often a note saying which XML files to use.
Steps
Prepare a Windows PC that QFIL can work from
- Brick risk
- Time: 20–30 minutes
- Worked for 7 of 8 reports
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.
- Install the Qualcomm USB driver and restart the PC. If the installer asks which mode to install, the first (upper) option worked.
- Install the QPST package and start QFIL from Start → QPST → QFIL, not from a loose copy.
- Sign in to Windows with an administrator account whose user name has only Latin letters and no spaces; create a new local account if yours does not.
- If Windows Security or your antivirus blocks or quarantines a file from the package, do not switch protection off. Check that the file is the one Carlinkit support sent (same name and size as in their message, and the checksum if they gave one) and ask support about the warning. Restore it, or allow only that one folder, once support confirms the file.
- Keep the recovery files in a short folder on drive C, for example next to the QFIL installation.
- If QFIL still shows the same error after a restart, reinstall the drivers and try another QFIL version, then another PC.
Each step came from a failure an owner fixed. A stand-alone QFIL misbehaved until the copy inside QPST was used. On Windows 11, one owner’s partition menus froze until he made a clean administrator profile with a plain English name; another ran Windows 11 without that change. A TBox Ambient owner’s flash went through after he switched off antivirus, the Windows firewall and other protection and moved the files into the QFIL folder on drive C; he changed several things at once, so it is not clear which one mattered. A security warning is a reason to check the file with support, not something to get past.
The driver was the blocker for three more owners. One whose QFIL error survived a PC restart cleared it by installing QFIL 2.0.2.9 and fresh drivers. One who had no Qualcomm driver at all installed it, from the driver package or through Windows Update, and got his box back. One picked the upper option in the driver installer and the flash went through; an experienced owner remembered choosing the lower one, so the choice may not matter.
An owner who had restored Android 11 on his laptop before could not restore Android 13 on it. On another laptop the flash went through first time.
Put the box into EDL mode
- Brick risk
- Time: 5 minutes
- Worked for 1 of 2 reports
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.
- Unplug the box from the car, charger and PC.
- Find the pin-hole protocol button. On the TBox Ambient it is on the end opposite the SIM, microSD and USB slots.
- Press and hold it with a pin until you feel it click.
- Still holding it, connect the box to the PC with the data cable, then release after a second or two.
- Open Device Manager and look under Ports (COM & LPT) for Qualcomm HS-USB QDLoader 9008 (COMx). Note the COM number.
A TBox Ambient owner whose QFIL showed no port at all believed the box had no button; the protocol button is also the EDL button, and holding it while plugging in brought the port up. Some guides call it a reset button; it is not one. Another SM6225 Ambient owner could not feel any button with a pin, even a thinner one, and never got a port. If the button gives no click at all, it may have come loose inside; one owner was told it needed opening, which voids the warranty, so contact the seller first.
Match the programmer and memory type before you flash
- Brick risk
- Time: 10 minutes
- Worked for 4 of 4 reports
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.
- In QFIL, click Select Port and choose the 9008 port.
- Under Select Build Type, choose Flat Build.
- Under Select Programmer, browse to the firehose
.elffile inside the package for your chip (on an SM6225 Ambient, inside the UFS or eMMC folder you are testing). - Open Configuration → FireHose Configuration and set Device Type to the memory type of that folder. Make sure Erase All Before Download is not ticked.
- Open Tools → Partition Manager. If a table of partitions appears, the combination is right. Close it without changing anything.
- If you get a Sahara error or the table does not open, unplug, re-enter EDL, and repeat with the other memory type and its own programmer.
An Ambient owner got a Sahara error every time until another owner explained that the SM6225 package holds both a UFS and an eMMC version and only one fits a given box; with the matching one the flash worked. Two more SM6225 Ambient owners had QFIL set to eMMC; switched to UFS with the 6225 programmer, both flashed and got their boxes back. A TBox Plus 668 owner saw “Failed to initialize (open whole lun) UFS” until he switched QFIL to eMMC, after which the partition table opened.
Experienced owners insist on this check before the real flash, and on one detail one of those Ambient owners had missed: after the partition table opens, unplug, reconnect in EDL with the button held, and only then start the download.
If Partition Manager never opens, change the cable and port
- Brick risk
- Time: 15 minutes
- Worked for 2 of 2 reports
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.
- Keep the same QFIL settings.
- Swap the USB data cable for another one, including older plain cables.
- Try every USB port on the PC, preferably USB 2.0 ports on the back.
- Re-enter EDL after each change and retry Tools → Partition Manager.
An owner on Windows 11 could not open the partition table with UFS or eMMC through three cables; an old 3 m cable worked. Another owner had hit the same wall: three cables and every COM port failed, and a fourth, thin 3 m cable worked.
Flash the official recovery package
- Brick risk
- Time: 20–40 minutes
- Worked for 6 of 9 reports
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.
- Re-enter EDL, reopen QFIL and set the port, Flat Build, the programmer and the memory type that passed the check.
- Click Load XML and pick the
rawprogramfile your package names; when QFIL asks, pick thepatchfile with the same number. - Click Download and do not touch the PC, cable or box until the log shows Download Succeed.
- On a TBox Plus EM 668 package with six pairs, repeat steps 1–3 for
rawprogram1withpatch1and so on up torawprogram5withpatch5, in order. - Unplug the box, wait ten seconds, and connect it to the car or a charger.
- Give the first boot several minutes: it can sit on the start screen before setup begins.
Select Build Type : Flat Build
Select Programmer : C:\recovery\plus668\prog_firehose_ddr.elf
Device Type : emmc (or ufs, whichever opened Partition Manager)
Load XML : rawprogram0.xml + patch0.xml ... rawprogram5.xml + patch5.xmlA TBox Plus EM 668 owner on Android 13 recovered his box this way to the 4 Jul 2024 build, flashing all six pairs in order. A TBox Plus owner in a Mitsubishi Pajero Sport whose box never connected got it working with a full QFIL recovery, then the latest firmware and a switch to Android Auto protocol. Another owner, whose box hung at start one day for no clear reason, brought it back with the recovery package; the first boot sat on the start screen for about 20 seconds before setup started, and the box felt slow at first.
Three more TBox Plus owners came back the same way. One box had started blinking blue and red, then stayed red and switched off; the recovery steps from the community FAQ revived it. Two TBox Plus EAU 138 owners followed an owner-written recovery guide for that variant and reported that everything worked.
Two other owners flashed a package and the box still did not work. A TBox Plus EAU that had been rebooting kept rebooting after recovery and later died completely, which points at hardware. A Plus owner restored the 138 package and still had no picture, and was told to try the 668 package instead; no result was posted. A third owner following the EAU 138 guide got only part of the way: the box blinked green and the CarPlay button lit for a second, then went out, over and over. If the flash succeeds and the box still does not start, the next step below is the one owners used.
If it flashed but still will not start, flash a base package first, then the current one
- Brick risk
- Time: 40–60 minutes
- Worked for 6 of 7 reports
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.
- Ask Carlinkit support for two official packages for the same variant (EM 668 or EAU 138): an older base package (Android 11, or Android 12) and the Android 13 package. For a TBox Ambient on the QCM6125 chip, one owner used the TBox Plus Android 11 package as the base.
- Flash the base package with QFIL as above.
- Unplug the box from the PC and do not power it up.
- Re-enter EDL with the button held and connect to the PC again.
- Flash the Android 13 package (or the newer build your car needs).
- Power the box from a charger and leave it for about 10 minutes before testing in the car; the first boot rebuilds user data.
All seven reports come from the TBox Plus or boxes on its QCM6125 chip. A TBox Plus owner in a VW Touareg found the box dead one afternoon after it had worked that morning; an Android phone on the same cable worked, so the car was fine. QFIL reported success, but the box did not start. Recovery to the Android 11 package restored normal LED behaviour, and a second recovery to the Android 13 package made it work.
A TBox Plus EAU 138 owner wrote up the same order after unbricking his box: Android 11 base images, unplug, back into EDL without powering the box, the Android 13 package, then ten minutes on a power supply. He needed three attempts and stressed the re-entry into EDL. A QCM6125 TBox owner whose box stopped starting after a flash, and one more owner, reported that the same pairing worked where either package alone had not. A Plus 138 owner whose Android 13 package would not revive the box got it going with the Android 12 package, then updated to 13 with the normal update file.
A TBox Ambient owner on the QCM6125 chip had gone further: after a recovery with an October 2023 package and an erased userdata partition, not a single LED lit. Flashing the TBox Plus Android 11 package, then the Ambient 6125 package straight over it before the box could boot, brought it back. Erasing userdata by hand left this box darker, not better, so do not try it.
A TBox Plus EAU owner in a Geely Tugella got his box working by flashing a build from February 2024 or later from the PC after the recovery flash alone changed nothing. One owner repeated the base-then-Android 13 order about ten times without success, so it is not a cure for every dead box.
TBox Ambient that drops out: try an older official recovery set
- Brick risk
- Time: 30 minutes
- 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.
- Ask Carlinkit support whether an older recovery set exists for your Ambient chip.
- Flash it with QFIL from EDL mode, exactly as above.
- Use the box for several drives before you update it again.
A TBox Ambient SM6225 owner whose box had sat unused for months found that it now started, ran for a while and dropped out, with a purple light and no CarPlay. Two recovery sets from 2024 and 2025 changed nothing; a 2023 set fixed it, and the box was running without drop-outs when the owner reported back. Two other owners described the same symptom without posting a result, so this is one report.
Verify it worked
The box should boot to the stock launcher with a fresh setup. Then check:
- Settings → About shows the model you expect and a build date close to the package date.
- The head unit shows the box in your usual protocol; if not, switch protocol before suspecting the flash.
- Insert the SIM and open a web page with Wi-Fi off. If the SIM is missing or About shows no IMEI, read the troubleshooting below before flashing anything else.
- If a “Device not activated” QR screen appears, give the box internet by SIM or phone hotspot; see QR code / device not activated. Two owners met this after recovery; internet cleared it.
Undo / rollback
There is no way back to the exact state before the brick, because a recovery flash wipes everything. Your options afterwards:
- Install any official build for your variant with the FOTA local update. After recovery, owners were advised to move to the current regular firmware for the model, because the recovery base is often old.
- Flash the same or another official recovery package again from EDL. That is the only way back from a build that does not boot.
- After two careful attempts with the correct package and no result, it is a support case, not a QFIL case.
Troubleshooting this guide
Sahara error, or “Only read 0 bytes”. The box is not in EDL, or the programmer does not fit the chip and memory type. Repeat the memory-type check with each folder’s own programmer. The TBox Ultra QFIL guide has the full Sahara checklist; it applies here too.
“Failed to initialize (open whole lun) UFS”. Your box has eMMC memory. Switch Device Type to eMMC and use that folder’s programmer. The Plus 668 owner who met this then found that his 4 Jul 2024 six-pass set would not write under eMMC; an older 23 Aug 2023 set wrote without errors, but the box stayed in download mode afterwards. Ask support for the package made for an eMMC unit rather than trying older sets at random.
The SIM or IMEI is gone after recovery. This happened to an Ambient owner who ticked Erase All Before Download, which wipes the partitions holding the IMEI and radio calibration; they are not in any recovery package. A package for the wrong variant can do the same. Contact Carlinkit support; do not flash another box’s modem files.
The box bootloops after recovery, especially on Wi-Fi. The recovery base can be old. Install the current official build for your variant with FOTA, and if the loop stays, follow AI box keeps rebooting.
The PC never shows a 9008 port. Hold the button before the cable goes in, try a USB 2.0 port and another data cable, and reinstall the Qualcomm driver; on Windows 11 another owner suggested updating the driver through Windows Update. If the button never clicks, contact the seller.
What owners said
“I flashed the 2023 recovery files through QFIL (before that I'd flashed two newer ones, 2024 and 2025, with zero reaction). It helped; so far it runs without drop-outs.”
Owner, Carlinkit TBox Ambient, Oct 2025
“I installed and ran QFIL from the QPST package and everything worked.”
Owner, Aug 2025
“The key step: I created a clean Windows 11 profile with admin rights, name strictly in English, no spaces. After that, QFIL's temporary files are created fine and the partition items work (before, it hung).”
Owner, Aug 2025
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
Where do I get the recovery package for a TBox Plus or Ambient?
From Carlinkit support: email [email protected] with the model, the variant from the back label (EM 668 or EAU 138 on a Plus), the chip from the listing or Settings → About, and that you need a QFIL recovery package. This site does not host or link recovery images.
Does the TBox Plus need eMMC or UFS?
It depends on the unit. Owners found TBox Plus EM 668 boxes with either memory type, and sellers rarely say which. The setting that lets QFIL open Partition Manager is the right one for your box.
Will recovery erase my apps and settings?
Yes. A recovery package rewrites the whole system and data area, so the box starts like new and you set it up again. Never tick Erase All Before Download: one owner lost the IMEI that way, and no recovery package restores it.
Is the Ultra guide the same?
The tool and the idea are the same, but the Ultra uses a different chip, its own programmer and UFS only. Use the Ultra guide for an Ultra 1, 2, 3 or 4 and this one for the Plus, Ambient and UHD.
Parts the fixes above need

Known-good USB data cable
A worn or charge-only cable causes drop-outs and failed flashing. Pick the ends your setup uses.

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.
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.
Related fixes
- Recover a Bricked TBox Ultra With QFIL (EDL, Firehose, UFS)Brick risk
- Update TBox Firmware Locally With FOTA and a microSD CardAdvanced
- QR Code or "Device Not Activated" After a TBox UpdateLow risk
- TBox Plus EM 668 Sold as EAU 138: 7 Owner ReportsBrick risk
- Factory Reset After Every Firmware Update? Try Cache Code 110144Advanced
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 reportChangelog
- Last reviewed against new community reports:
- Confirmed by 28 community reports on Carlinkit TBox Plus, Carlinkit TBox Ambient.
- 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 (13 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.
| Case | Confirmed on | Result | Source |
|---|---|---|---|
| case-7002 | Model not stated | 1 worked | Owner discussion threads, 3 messages |
| case-7004 | Model not stated | 1 worked, 1 did not | Owner discussion threads, 3 messages |
| case-8150 | Carlinkit TBox Plus (2024-07-04); Carlinkit TBox Plus | 3 worked, 2 did not | Owner discussion threads, 12 messages |
| case-8151 | Carlinkit TBox Plus | 6 worked, 1 did not | Owner discussion threads, 25 messages |
| case-8152 | Carlinkit TBox Ambient (2023) | 1 worked | Owner discussion threads, 2 messages |
| case-8153 | Carlinkit TBox Ambient | 1 worked | Owner discussion threads, 5 messages |
| case-8154 | Carlinkit TBox Ambient | 1 worked, 1 did not | Owner discussion threads, 11 messages |
| case-8155 | Carlinkit TBox Ambient; Carlinkit TBox Plus | 4 worked | Owner discussion threads, 25 messages |
| case-8156 | Model not stated | 2 worked | Owner discussion threads, 5 messages |
| case-9940 | Carlinkit TBox Plus | 3 worked, 1 did not | Owner discussion threads, 5 messages |
| case-9941 | Model not stated | 3 worked | Owner discussion threads, 7 messages |
| case-9942 | Model not stated | 1 worked | Owner discussion threads, 2 messages |
| case-9943 | Carlinkit TBox Ambient | 1 worked | Owner discussion threads, 3 messages |