View Single Post
Old 03-02-2015, 02:24 PM   #2
steve99
Banned
 
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,996
Thanks: 1,035
Thanked 4,998 Times in 2,985 Posts
Mentioned: 598 Post(s)
Not bricked my own however all known "bricks" due to use of incorrect definitions when editing rom or writing using incorrect definition .

Basicly its operator error. resulting in a corrupted rom that is checksum corrected being written to the ecu.

If you write a rubbish or corrupt rom with any system your going to brick the ecu.

Before anyone says system X will save you , I dont think it will, I will give you a checksum corrected rubbish rom with the correct CALID to write with system X and I am reasonably confident it will write it and its curtains.

Using OEM boot loader/mode or "recovery mode" as some systems refer to still requires the ECU to recognize CAN buss and respond to commands via the OBD port.

Once you write a complete rubbish rom that sends ecu off with the fairies or causes it to constantly reboot due watchdog timer, it no longer responds to commands via OBD port and your screwed with any system.

Then its remove ECU and soldering directly to board to write via serial interface of the SH72531 mirco controller, or possibly hardware bootstrapping the micro into user boot mode. I don't know of anyone who has successfully pulled this off yet.

Most systems will recover from a partial write as long as the ecu is still in programming mode, ie you don't turn off ignition. Or the ecu does not get into some kind of looping state and is still able to communicate via obd port.
steve99 is offline   Reply With Quote