ECU writing error

A writing error means the tool started putting software into the ECU and did not finish. The
ECU is now holding something incomplete. What you do in the next minute decides whether this is a
five minute retry or a bench job.

Before you do anything else

Do not disconnect the tool. Do not turn the ignition off. Do not close the software, unplug the
USB cable, or move the car. Leave everything exactly as it is and read this first. Most recovery
routines only work while the session is still open and the ECU is still in programming mode. Break
the connection and you usually lose that option.

What has actually happened

The ECU was in programming mode, the old software had already been erased or partly overwritten,
and the transfer stopped before the new software was complete. The ECU is not damaged in the sense
of being physically broken. It simply has nothing valid to run, which is why it often will not
respond to a normal request afterwards.

Nearly all of these come down to one of a small number of causes:

• Voltage dropped or fluctuated during the write
• The connection was interrupted, at the OBD port, the USB cable, or the bench wiring
• The laptop slept, hibernated, or a background process took priority
• The ignition dropped out, either by the key being touched or by the vehicle timing out
• Another device on the bus interrupted the exchange

Recovering it

1. With everything still connected, use the tool’s recovery or resume option if it offers one.
   The wording differs between versions, so look for anything offering to continue, repeat or
   recover the interrupted operation.
2. If it offers to write again, write the full file, not a partial write. The
   ECU’s contents are now unknown, so nothing can be assumed about what is still in there.
3. If the tool cannot see the ECU at all, check your voltage before you conclude anything. A
   support unit that has run flat during a long write looks exactly like a dead ECU.
4. If the ECU still does not respond on OBD, stop. Do not keep cycling the ignition and retrying.
   Each attempt is another chance to make it worse, and none of them will fix an ECU that has lost
   its bootloader path.

When it becomes a bench or boot job

If the ECU no longer identifies over OBD, the recovery has to happen at the ECU rather than
through the car. That means either a bench connection, powering and communicating with the ECU
directly out of the vehicle, or a boot connection, where the ECU is opened and the tool talks to
the processor itself. Which one applies depends on the ECU. Both write the full original back.

This is the point at which having the original read matters more than anything else in this
article. If you took a full read before you started and saved it, this is recoverable. If you
used a virtual read and never physically read the ECU, you do not have the customer’s original
and you are relying on a database copy being right for that exact vehicle.

Stopping it happening again

• A proper battery support unit on the vehicle, not a trickle charger. A trickle charger is
  built to put charge back into a battery slowly. It will not hold voltage steady against the load
  of an ECU write, and voltage collapse partway through a write is the single most common cause of
  this error.
• Laptop on mains, with sleep, hibernate and USB power saving all switched off.
• USB straight into the laptop. No hubs, no extension leads.
• Nothing else plugged into the OBD port and nothing aftermarket live on the bus. Trackers,
  dashcams and alarms wired into CAN all count.
• Doors closed, lights off, keep the electrical load down, and do not touch the key.
• Take and save a full original read before you change anything.

What to send us

Open a ticket on the dealer portal and attach the log file from the session that failed and any
read files you have, including the original if you took one. Tell us the vehicle, the ECU hardware
and software numbers, which tool and connection method you used, and how far through the write it
got. The log tells us what the ECU was actually doing when it stopped, which the error message on
its own does not.