An online operation can fail before any data is written to a vehicle. Save the exact message and determine whether the problem concerns login, entitlement, server availability, file selection or communication with the controller. Do not describe all of these as a “bricked ECU”.
Keep account support separate
Use the tool or manufacturer provider’s legitimate support route for account and subscription issues. Never send passwords or one-time codes with a workshop fault report. An expired entitlement does not establish a fault in the vehicle electronics.
Preserve the actual programming stage
If writing had begun, record the progress and any interruption carefully. Include the current module response and available logs. Avoid repeated attempts with different accounts or unsupported files simply to bypass an error. The correct recovery instructions depend on the application and stage reached.
For AXION, send a redacted screenshot and the tool details, together with the vehicle’s present symptoms. The assessment can then focus on supported vehicle or module work while provider-side access problems are addressed separately. Clarifying the stage early can prevent an unnecessary module replacement or a risky speculative write.
Related help
- Checking used ECU compatibility beyond the part number
- Why ECU hardware and software numbers both matter
Browse all fault guides or use the vehicle module finder to prepare your enquiry. Send your vehicle details, what has gone wrong and any scan or test results. Contact us before booking or posting a module so we can check whether we can help.