In This Guide

Use the specific controller identity

Start with a readable full label, registration, engine and current diagnostic identification. The brand or engine capacity alone does not establish an MD1CS003 application or its required access route.

Tell us whether the aim is calibration access, recovery after programming or replacement-data assessment. The operation should be checked separately from the broad controller family. Owning an access tool does not make every task on every variant supported.

Understand the published route without overextending it

Magicmotorsport’s Flex 8.23 announcement describes a Korhex Boot Glitch route for selected Stellantis Bosch MD1CS003 controllers using the TC298 processor, with subsequent bench programming. The release identifies the applicable access and memory operations for that protocol.

That announcement is an application reference rather than confirmation that your damaged original or proposed donor suits the complete job. Current support, available original data and the requested outcome still need checking before acceptance.

Access and cloning are distinct questions

An access operation prepares a supported controller for applicable work. A replacement-data job also needs the required original information, a compatible donor and a supported transfer procedure.

State original communication and condition. Include both labels for replacement and any logs or files for recovery. A calibration-only read should not be assumed to contain all the identity and configuration information needed by a donor.

Plan parts, files and appointments

For removed-unit access work, ask which parts are required and how they should be prepared and packed. Do not remove or post an ECU simply because the family appears in an announcement.

If a programming failure occurred, preserve original reads, attempted writes and error messages. Describe the tool, protocol and sequence. Recovery of damaged data cannot be guaranteed from the presence of a protected-access procedure alone.

Get an application-specific scope

Precision Remaps UK confirms the supported route, required work and arrangements for the identified application. Turnaround includes assessment and any further agreed work; the vendor’s connection or read time is not the whole customer-job timescale.

Include the full postcode and installer contact. The handover should state any remaining software, configuration and vehicle-side checks so the accepted controller work fits the complete repair or calibration plan.

Technical reference: Magicmotorsport: Stellantis MD1CS003 Korhex release. Reviewed 6 October 2026. Work and any remaining installation requirements are assessed for the exact application.

YOUR ENQUIRY CHECKLIST

Send the information that helps.

  • Complete controller label and diagnostic identity
  • Registration, engine and full postcode
  • Access, recovery or replacement goal
  • Original condition, files and previous operations
  • Donor label where relevant and installer contact

Questions about this enquiry

Does the published protocol guarantee my ECU can be cloned?

No. The requested transfer, original data and donor conditions need a separate support check.

Is the vendor’s read time the job turnaround?

No. Identification, preparation, assessment, agreed work, verification and arrangements all affect the customer timescale.