Agreed and the issue/bug itself is also a bit special:
A corner-case, rather rare use case was buggy: the First Boot, that is executed exactly once during the lifetime of the device.
Whatever testing you do, it’s usually on a set-up, running phone going through all the commonly used functions.
It just happened now that a relatively large number of users were “forced” to execute that rarely-used function, so a large number were bitten by the bug (not all of them either!).
Of course the situation was escalated by the fact there was/is no way to recover “in the field”.
Imagine the same situation, but with the possibility to reset to factory state. People would have just tried again, succeeded and no-one would have given it a second thought.