Actually when it first came out Apple said it was intentional enhanced security checks that disabled the phone for the user's safety.[1] Why brick the phone? The enclave is secure and the Touch ID doesn't work, it hasn't worked since it was repaired. Why suddenly decide the phone needs to stop working during an update? Why not just wipe the secure enclave?
When user's contact Apple for support, they were turned away and Apple recommended they replace the phones.
Apple later changed their story and said that it was intended for validation at the factory and mistakenly affected customers.[2] Bricking a device at the factory seems like an odd way to validate it. Wouldn't a JTAG or SPI bus be a better way to query the phone to perform validations?
> they reverted with a patch within weeks.
Weeks. Turn your phone off and don't use it for weeks then come back here and tell me how it was no big deal.
Actually when it first came out Apple said it was intentional enhanced security checks that disabled the phone for the user's safety.[1] Why brick the phone? The enclave is secure and the Touch ID doesn't work, it hasn't worked since it was repaired. Why suddenly decide the phone needs to stop working during an update? Why not just wipe the secure enclave?
When user's contact Apple for support, they were turned away and Apple recommended they replace the phones.
Apple later changed their story and said that it was intended for validation at the factory and mistakenly affected customers.[2] Bricking a device at the factory seems like an odd way to validate it. Wouldn't a JTAG or SPI bus be a better way to query the phone to perform validations?
> they reverted with a patch within weeks.
Weeks. Turn your phone off and don't use it for weeks then come back here and tell me how it was no big deal.
[1] https://www.theguardian.com/money/2016/feb/05/error-53-apple... [2] https://techcrunch.com/2016/02/18/apple-apologizes-and-updat...