On This Page
Stop and record what happened
Keep the vehicle and controller in the state advised by the tool supplier or technician. Record the operation, selected protocol, file used, stage at which it stopped and messages shown. Repeated attempts with guessed files can change the information available for assessment.
Save tool logs, identification results, the original read and the attempted write as separate files. Do not overwrite a backup with a later read and assume that the later file is original. Tell us which files came from the vehicle and which were supplied elsewhere.
Identify the operation and the controller
Recovery support depends on the exact ECU or TCU, its current state and the accessible memory. An operation that was available over OBD before the failure may require another supported access method afterwards.
Send the label, vehicle specification and software identification where available. We assess whether an appropriate OBD, bench or boot route exists for the job. Protected-controller access and full-data work are quoted according to the required procedure.
Explain the surrounding conditions
Include any voltage warning, disconnection, tool interruption or previous software mismatch. These details are evidence for the technician, rather than proof of one particular failure.
A controller that has suffered electrical damage may need a different assessment from one with an interrupted application write. Recovery cannot be guaranteed from a file name or family designation. The original unit and available data need checking.
Agree recovery and verification separately
An accepted quote sets out the proposed recovery attempt, the files or parts required and how the result will be checked. Tell us if the intended outcome is original-software restoration, a corrected calibration or data preservation for replacement.
A successful controller write does not establish that the whole vehicle is fault-free. Your installer may need to complete configuration, adaptation and diagnostics. Ask about a postal route before arranging transport of a non-running vehicle.
The useful details.
- Exact tool, protocol and error messages
- Original read and attempted write kept separately
- Tool logs and identification results
- Controller label and vehicle registration
- Voltage events and every recovery attempt already made