The issue is probably a missing A/B firmware update for the config section. If a firmware update needs to alter the calibration data or other rather static con

The issue is probably a missing A/B firmware update for the config section. If a firmware update needs to alter the calibration data or other rather static config, and that update process is interrupted by an empty battery then it can't recover. It should of course be more conservative in killing all of the config section... Or could reset to some sane default. Or have a copy of the old known good data around and restart the procedure