Firmware & recoveryReviewed
ApplePie or UX999 Update Keeps Failing? Swap the microSD Card
ApplePie or UX999 update fails with an error (ERROR/1) from the microSD card? Swap to a different card and copy the file fresh. UX999 Ultra and Plus.
ApplePie UX999 UltraApplePie UX999 Plus 1.0 / 2.0
Quick answer
On an ApplePie or Playaibox UX999 box, when a firmware update from the microSD card fails with an error every time (ERROR/1, or an error screen after the file copies), swap to a different, known-good card and copy the file to it fresh. That fixed it for 2 of the 3 owners who reported back; one also reset the box.
Symptoms
- An ApplePie or UX999 firmware update ends in an error every time, such as ERROR/1
- An error screen appears right after the update file finishes copying to the card
- The update runs to 100% and then shows error
- Re-downloading the file and reformatting the same card changes nothing
- The box reads the card but the update never completes on any build
Applies to
- Devices
- ApplePie UX999 Ultra
- ApplePie UX999 Plus 1.0 / 2.0
- Connection to the car
- CarPlay and Android Auto
- Highest risk on this page
- Advanced
- Status
- Workaround confirmed by the community
Why it happens
Before an ApplePie or UX999 box installs a build, it reads the update package from the microSD card and checks it. A card that is failing, too slow, or not read reliably can corrupt the package as the file is written to it or as the box reads it back. The check then fails and you get an error, even though the file you downloaded is sound.
These boxes install firmware from the card directly: when they find a valid file they show a prompt and ask you to confirm, with no separate update app. That is different from the Carlinkit TBox, which installs through its FOTA app, covered in update TBox firmware with FOTA. If your box never offers the update at all, rather than erroring, that is a different problem; see ApplePie or Ottocast update prompt missing.
Re-downloading the file and reformatting the same card does not help when the card itself is the weak link. The fix owners reported was a different card.
Fixes, ranked
Swap to a different microSD card and copy the file fresh
- Advanced
- Time: 20 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.
- Get a different microSD card, ideally a new 16–32 GB card from a known brand. Do not reuse the card that kept failing.
- Format it FAT32 on a computer. One UX999 Ultra owner’s new card was formatted exFAT when the update finally took, so if FAT32 still fails, a new card in exFAT is worth trying.
- Download the official update file for your exact model again on a computer, and copy it unchanged to the root of the card. Do not unzip it and do not put it in a folder.
- Insert the card into the slot on the box, not the car’s head unit, and run the update again.
- If it still fails, factory reset the box and reinstall, as one owner did at the same time as the new card.
One owner who hit ERROR/1 twice changed the SD card and the update then installed with nothing else different. A UX999 Ultra owner, stuck on Android 12 and getting an error on every build he tried, changed to a new microSD card in exFAT, factory reset the box, and reinstalled through the box’s own OTA installer app; the box upgraded to Android 13. Because those two changes went together in one report, they count as a single confirmation here, under the card swap.
The one owner for whom this did not work, on a UX999 Plus, had an update that ran to 100% and then said error; he had already changed the card with no difference. So a failing card is a common cause but not the only one. If a second card does not help either, work through the file and the box itself, below.
Things to try (unverified)
- Re-download and rewrite the file before you blame the card. The advice to the UX999 Plus owner above was that the download can arrive corrupt, the write to the card can go wrong, or the box’s existing software is at fault, so re-download the file, write it to the card again, and factory reset the box. He reported that none of this, nor changing the card, helped him, so treat it as a check rather than a cure.
- Factory reset and reinstall on its own. A reset was part of the one UX999 Ultra owner’s success, bundled with the new card, so it cannot be judged by itself from these reports. If you reset, back up nothing you cannot reinstall; see factory reset after a firmware update.
- Confirm the file is for your exact model. An update built for a different ApplePie or UX999 variant can be refused with an error that looks like a card fault. The firmware tracker lists the builds owners discuss.
If your box is a Carlinkit TBox rather than an ApplePie or UX999, the equivalent page is “Upgrade failed” on TBox Ultra, which covers the corrupt-file and FAT32 checks for that family.
If nothing works
Note the box model and its current firmware version (on UX999 boxes under Settings → ApplePie settings), the exact file name on the card, the card’s size and format, and the exact error text. A photo of the error screen helps.
For ApplePie and Playaibox UX999 boxes, ask the maker’s support (Exploter, [email protected]) for the correct file for your model and variant. If the box refuses every official file for its model even from two good cards, a warranty claim is the honest next step; start here compares the box families.
What owners said
“Solved. I changed my microSD card to a new one, exFAT format, did a factory reset, then installed [the OTA installer]. After that, it seems to have upgraded to A13 successfully.”
Owner, ApplePie UX999 Ultra, Nov 2024
“I changed the SD card and was able to update it successfully.”
Owner, Apr 2023
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
Does the card have to be FAT32?
FAT32 is the safe default and what most boxes expect. One UX999 Ultra owner's update finally took on a new card formatted exFAT, so having a sound card mattered more than the format. Try FAT32 first.
I reformatted the same card and it still fails. What now?
Reformatting cannot fix a card that is failing or too slow to read reliably. Use a different card, ideally a new one from a known brand, and copy the file to it from a computer.
Do I have to factory reset as well?
Not always. One owner reset the box and reinstalled through its OTA installer app together with the new card; the other only changed the card. Try the card on its own first, because a reset erases everything on the box.
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.
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.
Carlinkit TBox Ultra (Android 15)
If an older box is too slow for the apps you run: the TBox Ultra is Carlinkit's Android 15 box, with an SM6350 chip. Check that the variant on the listing supports your car's protocol before buying.
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.
Affiliate links: we may earn a commission at no extra cost to you. Disclosure.
Related fixes
- ApplePie or Ottocast Update Prompt Missing? Insert the Card LiveAdvanced
- Update TBox Firmware Locally With FOTA and a microSD CardAdvanced
- "Upgrade Failed" on TBox Ultra: Corrupt File, FAT32, Free SpaceAdvanced
- Factory Reset After Every Firmware Update? Try Cache Code 110144Advanced
- ApplePie or UX999 Black Screen After a Firmware UpdateAdvanced
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 2 community reports on ApplePie UX999 Ultra.
- 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 (1 case)
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-1611 | ApplePie UX999 Ultra | 2 worked, 1 did not | Owner reviews, 2 messages |