woolich tuning deep dive part 14: ECU Write failure recovery and investigating over revving

Faced with a persistent over revving on idle problem I set out to determine if it was the lack of o2 sensor causing the issue.
Many hours with a soldering iron and 3d printer and I had a test box allowing me to vary what the ECU thinks it's seeing from the ECU.
From experience we cannot take any setting at face value (Disable Closed Loop... i'm looking at you) so this was intended to answer the question once and for all.
Anyway... What was meant to be a quick 20 minute test turned into a nearly 2 hour ordeal as I was presented with a failed write to the ecu and a need to perform a "Recover ECU".
The recover ECU overwrote the bin file I had open so that after recovery when I wrote to the ECU I put stock settings into the ECU. This highlights the importance of a good versioning strategy with solid backups of every stage. For me I could just revert what woolich did to my bin file because i'm using git source control.
On the flip side I was able to easily do a back to back comparison of my map to stock... but I never should have needed to. Woolich should have never overwritten the open bin file with stock settings. Recovery is a discrete step. They have no excuses for not showing a warning as a minimum.
So my afternoon involved 1 failed write, a recovery, a write, a ride resulting in the realisation that the custom maps were gone, another write and another ride test as well as the installation and later removal of my o2 sensor test harness.
The previous video in the series outlines the actual cause of the over revving. This did prove that the Disable Closed Loop does what it claims... for the gen3 mt09 at least.

[@bagnasty7791]

Ive had the same write failure and had to do the recovery procedure a few times now. Scary stuff but seems to work. Would love to know the cause of the failure. 23 Sp

[@davidb3925]

My hypothesis is that they pushed out an update. Hence the login prompt. I find that the updates are multi step and can take up to 4 restarts and sometimes 2 logins to get back to normal.
I want to have a deeper look at the registry settings and see if there is anything there to help provide additional information regarding updates.