Skip to content

USB Firmware Update Do's & Don'ts

Jakka351 edited this page Oct 8, 2026 · 2 revisions

Mk2 FG Falcon FDIM — USB Firmware Update: Do's & Don'ts

Field guide for recoring/updating the Mk2 colour FDIM (Front Display Interface Module / ICC display, via its on-unit USB port

What this is. The FDIM can take an application firmware image from a USB stick through its own loader ("USB recore").

⚠️ Exact filenames, folder, and the on-screen/service-menu trigger depend on your loader and image set — confirm those against your own procedure. Everything in the Do/Don't lists below is method-independent and applies regardless.


1. What you need

  • A small, good-quality USB stick (4–16 GB is plenty), freshly FAT32 formatted, single partition.
  • The factory/known-good image for that same part number on hand as your restore (AR79-14D017-CS.PHF).
  • A stable power source for the car/bench: ignition in the run position with a programming-grade maintainer holding ~13.5 V. The ICC is not a huge load, but a sag mid-write still bricks it.
  • 10 minutes of being left alone — no cranking, no door-latch cycling, no accessory switching.

2. USB stick preparation

Do ✅

  • Format FAT32, single primary partition, fresh. Quick-format is fine; a full format clears bad sectors.
  • Use a plain, reliable stick. Cheap no-name sticks and giant/exotic ones are a common cause of "file not found" / "update failed."
  • Put the image exactly where the loader expects it — root of the drive and the exact filename your procedure specifies (case and extension matter on some loaders). One file, nothing else competing.
  • Verify the file before copying: right part number, right hardware rev, and the container's checksums intact (PHF MODULE ID = 0x7A6 for the FDIM, and the FILE CHECKSUM must match the payload).
  • Safely eject the stick from the PC so the copy is actually flushed, not sitting in a write cache.

Don't ❌

  • Don't use NTFS/exFAT, multiple partitions, or a bootable/U3/encrypted stick.
  • Don't leave other firmware files, hidden OS junk (System Volume Information is unavoidable but fine; stray .PHFs are not), or renamed "just in case" copies on the drive — a loader that scans for a file can grab the wrong one.
  • Don't rename the factory and the patched file to look alike. Label them so you can never confuse restore vs. experiment. (Bluntly: filename the one you're flashing so a tired you at 11 pm can't pick wrong.)
  • Don't trust a copy you didn't verify. "It looked like it copied" is how a truncated file bricks a unit.

3. Before you insert — power & state

Do ✅

  • Put the car/bench on the maintainer first, confirm it's holding voltage, then work.
  • Ignition ON (accessory/run), engine off, unless your procedure says otherwise.
  • Close doors / avoid anything that keeps the body modules busy waking the bus.
  • Have the restore file already on a second ready stick (or know the restore path) before you start the update. Decide your recovery before you need it.

Don't ❌

  • Don't do this on the bare battery because "it's only the screen."
  • Don't start with a marginal battery, a running-rough idle, or anything that'll drop voltage.

4. Running the update

Do ✅

  • Insert the prepared stick into the FDIM's USB port and follow your trigger.
  • When it asks to proceed and you've confirmed the version/part number it reports matches what you intend, let it run.
  • Watch the progress indicator and let it reach completion and the unit's own "done / reset" step.
  • Expect it to take a few minutes and to reboot itself at the end.

Don't ❌

  • DON'T remove the USB stick while it's writing. This is the single most common way to brick a USB recore.
  • DON'T cut power, cycle the ignition, crank, or pull the fuse mid-update.
  • DON'T flash a version/part number it warns is mismatched. If it says the image isn't for this unit, stop — that warning is protecting you.
  • DON'T "help" a stalled bar by yanking the stick.

5. After the update

Do ✅

  • Let it fully reboot, then verify the new software/part-number/version on the unit.
  • Power cycle (ignition off, let the modules sleep, back on) once before judging behaviour — displays often need one clean sleep/wake to settle.
  • Re-check configuration: display options, language/units, illumination behaviour, and any CAN-driven features (climate readout, ambient temp, dimming) now that the new firmware is live.
  • Record the before/after versions and keep the stick/file archived with the VIN and date.

Don't ❌

  • Don't declare success on the first boot screen alone — exercise the actual features that were the point of the flash.
  • Don't throw away the factory image. It's your rollback forever.

8. Quick checklist

[ ] Maintainer on, ~13.5 V confirmed, holding
[ ] USB: FAT32, single partition, good stick
[ ] Correct patched PHF, verified part number + MODULE ID 0x7A6 + checksums
[ ] Ignition RUN, engine off, bus quiet, doors shut
[ ] Insert stick -> confirm reported version matches intent -> proceed
[ ] DO NOT remove stick / cut power until it finishes and resets
[ ] Full reboot -> one clean power cycle
[ ] Verify new version + exercise the actual features
[ ] Archive files with VIN + date; keep factory image forever

Scope: Mk2 FG Falcon FDIM colour ICC display, USB recore path. Confirm exact filename/folder/trigger against your own loader and image set; the Do/Don't discipline above is method-independent.