Touchscreen Software Hang or Unexpected Reboot
What does TESLA-UI_A004 mean?
The TESLA-UI_A004 (Tesla) EV fault code means: Touchscreen Software Hang or Unexpected Reboot. This is a moderate severity code.
Common Symptoms
- Touchscreen goes black for several seconds then restarts on its own
- Climate controls, navigation, and media become unresponsive until the screen comes back
- Autopilot and Autosteer remain functional but the visual display freezes or goes dark
- UI_a004 appears in the service alert list when you pull codes with Scan My Tesla
- Screen reboots happen repeatedly, sometimes every few minutes while driving
- Backup camera feed does not display when you shift into Reverse
- Voice commands stop responding and the Tesla logo boot screen appears unexpectedly
Probable Causes (Ranked by Likelihood)
- Corrupted or worn eMMC flash storage on MCU2, causing the UI process to crash during read/write operations Very Likely
- Overheating MCU2 or MCU3 board caused by inadequate thermal paste or blocked airflow in the dash assembly Likely
- Pending or failed over-the-air software update that left the UI partition in an inconsistent state Likely
- Loose or corroded 12V accessory battery causing brief voltage drops that reset the infotainment node on the CAN bus Possible
- Faulty or failing MCU2/MCU3 hardware requiring board-level replacement or full unit swap Possible
- Third-party OBD adapter or USB device drawing excessive current on the USB hub and destabilizing the MCU power rail Less Likely
Step-by-Step Diagnostic Procedure
Start with a soft reset. With the car in Park, hold both scroll wheel buttons on the steering wheel simultaneously for about 10 seconds until the screen goes black and the Tesla logo appears. This clears transient software hangs and costs nothing.
If the reboot loop continues after the soft reset, do a full power cycle. Go to the touchscreen service menu (Controls > Safety > Power Off), wait the full 2 minutes without opening a door or touching the brake, then press the brake to restart. This fully reinitializes all CAN nodes including the UI controller.
Check for a pending OTA update. After the screen comes back, go to Software in the main menu. If an update is waiting or shows 'Installing,' let it complete on Wi-Fi before drawing any further conclusions. An interrupted update is a common cause of UI_a004.
Inspect your 12V accessory battery. Use a multimeter to measure voltage at the 12V jump-start terminal under the hood (front trunk area, model dependent). You want 12.4V or higher with the car idle. Below 12.0V points to a weak 12V battery that can cause CAN bus instability and repeated MCU resets.
Remove any third-party USB devices, OBD adapters (including your OBDLink MX+ or Veepeak), or dashcam drives plugged into the center console or glovebox USB ports. Retest for 24 to 48 hours. If the resets stop, the external device was destabilizing the USB hub on the MCU.
Use Scan My Tesla or TM-Spy with your OBDLink MX+ adapter to pull the full fault log. Look for companion codes like UI_a002, UI_a006, VCFRONT faults, or BMS voltage irregularities logged within the same time window as UI_a004. Multiple UI codes together point harder at MCU hardware.
If reboots persist after all software and power checks, the eMMC flash on the MCU2 is the prime suspect, a known wear-out failure on vehicles built before late 2021. This requires either an eMMC chip replacement at a specialist EV shop or a full MCU2/MCU3 swap. This step requires Tesla Toolbox 3 or a qualified independent EV technician and is beyond DIY scope.
Frequently Asked Questions
What does Tesla code UI_a004 mean?
It means the car's infotainment software, the process running on the MCU2 or MCU3 media control unit, has either hung without responding or restarted on its own without being told to. Think of it like a PC that blue-screened. The car's drivetrain keeps running, but the screen goes dark and all the functions tied to it, climate, nav, backup camera, are unavailable until it reboots.
Can I still drive my Tesla with UI_a004 active?
Yes, but with limitations. The drive motors, battery management, and safety systems run on separate controllers and are not affected by the UI crash. However, you will lose climate control input, navigation, the backup camera, and visual Autopilot feedback while the screen is down. Do not rely on Autopilot or Autosteer during an active reboot loop since the visual display is part of driver monitoring for those features.
How do I fix UI_a004 myself?
Start by holding both steering wheel scroll wheels for 10 seconds to soft-reset the screen. If that does not fix it, power the car fully off via Controls > Safety > Power Off and wait 2 full minutes. Also check that no pending OTA update is stuck, and remove any USB devices or OBD adapters plugged in. A weak 12V battery can also trigger repeated UI resets, so test that too with a multimeter.
How much does it cost to fix UI_a004?
If it is a software glitch or a bad 12V battery, you are looking at $0 to $150. If the eMMC flash chip inside the MCU2 is worn out, an independent EV shop can reball or replace just the chip for around $300 to $600, which is the most cost-effective hardware fix. A full MCU2 replacement at an independent shop runs $500 to $900. Tesla service will often push an MCU3 upgrade which runs $1,200 to $1,500 installed.