It seems the identifying information of the ECU is written to the first
x number of bytes. How this data is marshalled varies between ECUs and if incorrectly marshalled data is written, the ECU is effectively bricked. I believe Woolich software validates this data and if the validation check fails (can't identify), it refuses to touch the ECU... which is a good thing and generally leaves the ECU in a recoverable state. A+ for Woolich here.
Between work and track day prep I didn't get time to get more details but it seems the attempted write put my ECU in a weird state in which Woolich or the dash could not init the ECU to identify it, hence why Woolich was throwing an error about reading the first memory location; but it was fortunately still recoverable.
I had already contacted Woolich but since it was Saturday and I was pressed for time I contacted a tuner in the US who was able to force write the correct image then flash their tune on to it... I got the ECU back with some euro velocity stacks too.
Woolich's initial trouble shooting step was to determine if the ECU could be identified. I mentioned to Woolich that since I had a track day approaching in a few days, I had already sent the ECU to a tuner (one they know and have worked with) for recovery. Didn't want to risk waiting till mid week to ship to Australia. Since the issue is resolved, I'm not expecting a reply... but I'm wondering if the next step would have been purchasing a recovery key which allows the stock image to be force written to the rom?
Either way, issue is resolved, Woolich has been great, and the new tune from the tuner hits hard and the throttle feels way smoother. Though I'm thinking of selling my woolich USB kit now and switching to their log box.
