If any OTA update brick a product, it is the firmware developer's fault (I'm a firmware guy). Period.
There should always be a procedure that would verify a copy of firmware before switching from an old to new version and always have to anticipate corruption in any step of the way. If that is not taken into consideration it should not be released.
No, you don't blame it on the user when you push something like that even if they have partially broken hardware. You should always throw an error in update and ask them to call a customer service if something like that happen, instead of bricking their stuff and then call it "pre-existing condition" like a typical German Engineering company would do (I used to work for one, they always blame the customers and they believe they never make mistakes). You abort the update when anything is suspicious in the process, you don't force your way forward.
This kind of behavior gets us fired in our field.
In my search for a fun to drive but not too powerful car I discovered GLI with the EA888 engine. I was kind of excited and was about to ask about reliability then I see this.... nevermind.