How to Revert and Uninstall ScreenTune
ScreenTune’s normal REMOVE action restores the exact files saved before the first installation. A full firmware reflash is the deeper recovery path: an owner-obtained Mazda firmware image overwrites the root filesystem. Start with REMOVE, then move to the next recovery option only if the expected state does not return.
1. Remove ScreenTune with its USB
Section titled “1. Remove ScreenTune with its USB”Use the ScreenTune USB prepared for this car. Rebuild it from the saved custom package if the original drive is unavailable.
- Start the vehicle and wait for the Mazda Connect home screen.
- Insert the ScreenTune USB into the media USB port.
- Select REMOVE from the action prompt.
- Leave the ignition on and the USB connected.
- Wait for Mazda Connect to reboot and return to the home screen.
- Remove the USB.
REMOVE restores every managed file from the first-install backup, removes active ScreenTune runtime files, and leaves the firmware version unchanged. It restores the state ScreenTune first captured, which is factory only if the unit was stock at first installation. See Install, Update, Repair, or Remove ScreenTune for the complete action flow.
2. Support-assisted recovery
Section titled “2. Support-assisted recovery”Use this if REMOVE runs but does not fully resolve the problem, for example an install that was interrupted, only partially applied, or left the system in an unusual state.
Email support with your firmware version, the screentune.log file from the USB, and a short description of what happened (what you were doing when it broke, any error on screen, and whether REMOVE completed). Don’t run a firmware reinstall first if you’re unsure; it overwrites the evidence that helps diagnose the original fault.
3. Full firmware reflash
Section titled “3. Full firmware reflash”A full reflash replaces the root filesystem and removes all modifications, including legacy AIO or manual edits. Miatafy does not supply the firmware. The procedure requires a correct-region .up image and a working USB update path. See firmware recovery for the procedure.
4. Mail-in / in-person recovery service
Section titled “4. Mail-in / in-person recovery service”For a hardware-level brick (a unit that won’t reach the USB update path at all), recovery is available as a paid mail-in or in-person service. This is a repair act at the SPI-flash level, not something a USB drive can do. Email support to arrange it.
If the CMU has legacy AIO tweaks
Section titled “If the CMU has legacy AIO tweaks”REMOVE does not undo MZD-AIO changes that existed before ScreenTune. To clear them:
- Run the AIO uninstaller if you still have it, or
- Do a firmware reinstall with a recovery USB (option 3 above)
If the modification history is unknown, use a firmware reinstall to establish a known baseline. See ScreenTune vs MZD-AIO.
Confirm the restored state
Section titled “Confirm the restored state”If the first-install baseline was stock, check:
| Check | Expected after revert |
|---|---|
| Disclaimer screen appears on boot | Yes |
| Touchscreen locks while driving | Yes |
| Android Auto returns to commander-only input | Yes, when AA Touch was installed |
If either ScreenTune behavior remains, move to the next recovery step or contact support.
Before a dealer visit
Section titled “Before a dealer visit”For a known ScreenTune-only history, REMOVE is enough. If the history is unknown or includes legacy tweaks, use a firmware reinstall. See the dealer visit guide.