Skip to content
AI Box Fix

Firmware & recoveryReviewed

Recover an ApplePie UX999 With QFIL (eMMC, Firehose)

UX999 Ultra, Rocket or Max dead after a firmware change? Flash the maker's full recovery set with QFIL in EDL, with the right firehose and memory type.

Illustration: ApplePie UX999 Ultra held in a hand inside a car

Quick answer

To revive an ApplePie UX999 Ultra or Rocket that hangs or will not boot after a firmware change, flash the maker's complete QFIL recovery set for that exact model from EDL mode, one rawprogram and patch pair per session. That worked for 3 of 5 owners. On a UX999 Max, QFIL only connected with the SDM450 firehose and eMMC.

Before you start

  • A Windows 10 or 11 PC with the Qualcomm USB driver and QPST (QFIL ships inside it)
  • The complete QFIL recovery set for your exact UX999 model and chip, from the maker's support or your seller
  • Your exact model: Ultra (SM6115, firmware APM1688), Ultra 3.0 (SM6225), Rocket (QCM6490), Rocket Q (QCM4490) or Mini / Pro / Max (SDM450)
  • A known-good USB 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

Devices
Connection to the car
CarPlay and Android Auto
Firmware in confirmed reports
ApplePie UX999 Rocket: 2024-04-29
Highest risk on this page
Brick risk

Is your UX999 really bricked?

A bricked UX999 never reaches the launcher: it hangs on the boot logo, or its LEDs light and go out, and nothing you insert on a card changes that. Several problems look similar and have safer fixes, so check them first.

The same factory-reset guide also covers erasing only the userdata partition with QFIL. That can fail: one Ultra owner’s box hung on the Android 13 logo after a downgrade, and after the userdata erase it did not start at all. A full recovery, as below, is what brought it back.

What a QFIL recovery does

Every UX999 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 sends the box a small loader, the firehose programmer, then rewrites the partitions listed in the set’s rawprogram XML files; the patch files fix up the partition table.

The programmer has to match the chip and the storage type has to match the memory, or QFIL fails before writing anything. The TBox Ultra QFIL guide explains the mechanism and the PC setup in detail; this page covers what is different on ApplePie boxes.

Which recovery set fits your UX999?

ApplePie sets are per model and chip, and they do not mix. Use the version string from Settings → ApplePie Settings if you noted it while the box still worked; otherwise check the case label or the seller’s listing.

  • UX999 Ultra (SM6115, firmware APM1688). The Ultra 1.0 and 2.0 set owners used is an Android 13 set dated 31 Mar 2023 with six pairs, rawprogram0 with patch0 up to rawprogram5 with patch5.
  • UX999 Ultra 3.0 (SM6225). The Ultra 1.0 and 2.0 files do not fit it. In December 2025 no Ultra 3.0 set was known among owners, so ask the maker for it by name.
  • UX999 Rocket (QCM6490). One owner’s set dated 9 May 2023 did not revive his box; the set dated 29 Apr 2024 did. The Rocket Q (QCM4490) has its own firmware line (see the Rocket hub); no owner here recovered one.
  • UX999 Mini, Pro and Max (SDM450). These use eMMC memory and the SDM450 firehose.
  • UX999 Plus 1.0 and 2.0. In 2023 owners had no QFIL set for the Plus 1.0 at all. Ask the maker before you try QFIL on one; one dead Plus 1.0 came back with the seller’s single-file firmware instead (last step below).

Unzip the set to a short path with only Latin letters and no spaces, for example C:\recovery\ux999. A normal APM….zip update file for the microSD card is not a recovery set; QFIL cannot use it.

Steps

Check the firehose and memory type before you flash

  • Brick risk
  • Time: 15 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.

  1. Prepare the PC as in the TBox Ultra guide: Qualcomm driver, QFIL started from QPST, an administrator account with a Latin-only user name.
  2. Unplug the box from the car and the PC.
  3. Hold the pin-hole button with a pin and, still holding it, connect the box to the PC. Release after a second or two.
  4. In Device Manager, look for Qualcomm HS-USB QDLoader 9008 (COMx) under Ports (COM & LPT).
  5. In QFIL, click Select Port and choose that port, then choose Flat Build.
  6. Under Select Programmer, browse to the firehose .elf file from your model’s set (on a Mini, Pro or Max, the SDM450 programmer).
  7. In Configuration → FireHose Configuration, set Device Type to the memory type of your set (eMMC on a Mini, Pro or Max). Make sure Erase All Before Download is not ticked.
  8. Open Tools → Partition Manager. If the partition table appears, the combination is right. Close it without changing anything.

A UX999 Max owner could not get QFIL to work with his box at all until an experienced member told him to find the right firehose and pick eMMC; it was the memory type, and the SDM450 programmer was the right one. He did not say what he flashed afterwards, so this is a confirmed setting, not a confirmed recovery.

On the UX999 Ultra the pin-hole button is the EDL button, not a reset. A Rocket owner whose QFIL showed no port was asked whether he had pressed the button; holding it before the cable goes in is the step owners most often miss.

UX999 Rocket: flash the recovery set, and try a newer set if an old one fails

  • Brick risk
  • Time: 30–45 minutes
  • Worked for 2 of 3 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.

  1. Re-enter EDL with the button held and set the port, Flat Build, programmer and the memory type that opened Partition Manager.
  2. Click Load XML and pick the first rawprogram file of the set; when QFIL asks, pick the patch file with the same number.
  3. Click Download and wait for Download Succeed.
  4. If the set has more pairs, close QFIL, unplug the box, re-enter EDL and flash the next pair. Repeat until the last one.
  5. Unplug the box, connect it to the car and give the first boot several minutes.
  6. Once it starts, install a current build from the microSD card as described on the Rocket hub.

A Rocket owner whose picture froze got his box back only with the recovery set dated 29 Apr 2024; an older set from May 2023 did not work. Two other Rocket owners could not go back to an older build from the microSD card: the screen stayed black for about 15 minutes, then the box reset itself and kept the same build. One of them rolled it back with a QFIL recovery.

One Rocket owner’s box had been stuck in a reboot loop with no SIM or card inserted. QFIL reported a successful download for every pair, and the reboots stayed. That points at the hardware rather than the set.

UX999 Ultra: flash the full recovery set, one pair per session

  • Brick risk
  • Time: 30–45 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.

  1. Hold the pin-hole EDL button while you connect the Ultra to the PC, and check for the 9008 port.
  2. In QFIL, set the port, Flat Build, the programmer and the memory type that opened Partition Manager.
  3. Click Load XML, pick rawprogram0.xml, then patch0.xml when asked, and click Download.
  4. After Download Succeed, close QFIL and unplug the box.
  5. Re-enter EDL, reopen QFIL and flash rawprogram1.xml with patch1.xml. Repeat up to rawprogram5.xml with patch5.xml.
  6. Unplug the box, connect it to the car and wait for the first boot.
Select Build Type : Flat Build
Select Programmer : C:\recovery\ux999\prog_firehose_ddr.elf (from your set)
Load XML          : rawprogram0.xml + patch0.xml  ...  rawprogram5.xml + patch5.xml
                    one pair per QFIL session, unplug and re-enter EDL in between

The Ultra owner whose box hung after a downgrade from Android 16 to Android 13, and then stopped starting after a userdata erase, reported that the full recovery fixed it. Experienced members describe the same order for the Ultra set: one pair, exit QFIL, unplug, reconnect with the button held, next pair.

A second Ultra owner flashed the 31 Mar 2023 set pair by pair without a single error. Before the flash his LEDs lit but the car did not connect; afterwards the LEDs stayed off. A member offered him a full backup of a working Ultra, and no result was posted.

UX999 Plus 1.0: install the seller's single-file firmware on stable power

  • 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. Ask your seller or the maker’s support for the firmware for the UX999 Plus 1.0, and how to install it.
  2. Power the box from a power bank or another stable USB supply, not the car.
  3. Install the firmware as the seller describes and watch the LEDs until the update has finished.
  4. Let the box boot, then set it up again.

A UX999 Plus 1.0 owner could not get the Miracle Thunder flashing tool to read his dead box: it found the box and installed drivers, then stopped with error 222 or other codes. Erasing userdata with QFIL did not help either. The seller sent a single-file firmware; installed with the box on a power bank, it brought the box back, on Android 13. The owner was not sure which of his steps did it, so treat this as one report.

Verify it worked

The box should start to the stock launcher with a fresh setup. Then check:

  1. Settings → ApplePie Settings shows the version string you expect for your model, for example APM1888 on a Rocket.
  2. The car shows the box in your usual protocol.
  3. The SIM works and the IMEI is shown in Settings. If not, do not flash modem files from another box; contact the maker’s support.
  4. Update to the newest official build for your model from the microSD card. The recovery base can be old; the firmware tracker lists the builds owners discuss.

Undo / rollback

There is no way back to the exact state before the brick, because a recovery flash rewrites everything. Your options afterwards:

  • Install any official build for your model from the microSD card, as the Rocket hub describes.
  • Flash the same or another official recovery set from EDL again. On the Rocket that is also the only route back to an older build that owners found.
  • After two careful attempts with the correct set and no result, it is a support or warranty case, not a QFIL case. Start here compares the box families if you need a replacement.

Troubleshooting this guide

Sahara error, or QFIL shows no port. The box is not in EDL, or the programmer does not match the chip. Hold the button before the cable goes in, and use the programmer from your model’s own set. The full Sahara checklist is in the TBox Ultra QFIL guide. On a Rocket, owners suggested restarting the PC after a Sahara error in Partition Manager.

“Failed to open device, type:eMMC”. The storage type does not match the box. A Rocket owner got this message and was told to set the correct memory type, and to unplug the box or restart the PC after a wrong attempt before trying again.

Download Succeed, but the box still does not start. Flash every pair again from fresh EDL sessions, and check the set is for your exact model: Ultra 1.0 and 2.0 files do not fit an Ultra 3.0. A Rocket that keeps rebooting after a clean flash, or an Ultra whose LEDs stay dark, needs the maker’s support.

The SIM or IMEI is gone after recovery. Never tick Erase All Before Download: it wipes the partitions that hold the IMEI and radio calibration, and no recovery set restores them. Contact the maker’s support.

Ottocast boxes. The tool is the same, but the builds and the way into EDL differ; see recover a dead Ottocast Picasou 3 with a PC flash.

What owners said

“Same for me: the rollback only worked by restoring through QFIL.”
Worked: Full QFIL recovery set
Owner, Apr 2025
“Yes, I've sorted it already; it was the memory type. The SDM450 firehose is the right one.”
Worked: SDM450 firehose and eMMC memory type
Owner, ApplePie UX999 Mini / Pro / Max, Oct 2024
“I brought the box back to life. I don't know what helped. […] I asked the seller for the firmware; he sent a single-file one. Plugged into a power bank, I updated while watching the LEDs and it updated.”
Worked: Seller's single-file firmware on stable power
Owner, ApplePie UX999 Plus 1.0 / 2.0, Oct 2023

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 QFIL recovery set for my UX999?

From the maker's support: Exploter, [email protected], or the seller you bought from. Give the exact model (Ultra, Ultra 3.0, Rocket, Rocket Q, Max) and the chip. This site does not host or link recovery sets, and a set for another model can leave the box worse off.

Can I use the Ultra 1.0 or 2.0 recovery set on an Ultra 3.0?

No. The Ultra 3.0 uses a different chip (SM6225), and owners pointed out that the Ultra 1.0 and 2.0 files do not fit it. Ask the maker for the Ultra 3.0 set by name.

Can I roll a UX999 Rocket back from the microSD card instead?

Two Rocket owners could not. After they flashed an older build from the card, the screen stayed black for about 15 minutes, then the box reset itself and kept the same build. One of them rolled back only with a QFIL recovery.

Will a QFIL recovery erase my apps and settings?

Yes. A recovery set rewrites the system and data partitions, so the box starts like new and you set it up again.

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 5 community reports on ApplePie UX999 Rocket, ApplePie UX999 Ultra, ApplePie UX999 Mini / Pro / Max, ApplePie UX999 Plus 1.0 / 2.0.
  • 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 (4 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-8930ApplePie UX999 Ultra1 worked, 1 did notOwner discussion threads, 13 messages
case-8931ApplePie UX999 Rocket (2024-04-29)2 worked, 1 did notOwner discussion threads, 22 messages
case-8932ApplePie UX999 Mini / Pro / Max1 workedOwner discussion threads, 5 messages
case-9920ApplePie UX999 Plus 1.0 / 2.01 workedOwner discussion threads, 2 messages