Problem 1: Autotuner managed to brick a Delphi DCM3.5 from a Ford S max today through OBD, Was starting to write file then error comes up and the autotuner software closed itself. now left with a bricked ECU.
Problem 2: Peugeot_Expert__Traveller_2006(II)_2.0_HDI_128_hp_Delphi_DCM3.5. While writing with the autotuner via OBD, the ECU dcm3.5 bricked.
Problem 3: Car is Peugeot expert 2014 2.0d. Read and write Dcm3.5 ecu with Autotuner.
Its flashed with error. Now car not starting and cannot read ecu, even with diagnostics.
Dangerous software, you can brick with all tools.
Autotuner does not have boot for this ecu . You need another tool to recover.
Recover with a different tool because they only offer OBD.
We are able to recover the data and bring it back to life using the Flex/KESS3/Foxflash/Xhorse multi prog/Dimsport etc in boot mode. Sometimes genuine tools fail to recover in boot, foxflash does it without problem.
You need to read in JTAG mode and merge OBD read with JTAG read to bring Ecu back to life.
It’s an MPC55xx so it’s not bricked as long as you boot mode it. Write original from database.
The OBD read is a partial file. If you were flashing in OBD mode, you should in theory be able to keep hammering the file on it and hopefully it will write it on. On the delphi ECUs that once it’s bricked the immobiliser doens’t link up, so then you can flash a file in OBD mode but only connected to Can Hi Lo on the ECU on the bench.
If that doens’t work then take a boot mode backup, I can fix the autotuner backup file so when you do a restore it writes the full file.
