Apple has released an iOS update to fix iPhones disabled by Error 53 that resulted from a damaged or replaced Touch ID sensor in the smartphones' home button. It usually resulted from unauthorized third-party repairs. The tech giant's updated iOS version is now available on the iTunes store and will restore bricked handsets shut down by error code 53.
Apple rolled out a new version of iOS 9.2.1, according to CNET. It will not only fix iPhones disabled by Error 53 but will also prevent future replacements of home buttons by third-party repair shops from getting bricked, according to Tech Crunch. However, it is not a new iOS version.
Apple smartphone owners who update their phones through iTunes can get the iOS update from the online store. That is also true for people with bricked smartphones.
However, the update is not for iPhone users who get over the air (OTA) updates through iCloud. In theory those people should never have experienced bricked phones due to error code 53.
Apple issued a statement to Tech Crunch explaining that a "Connect to iTunes" message appears when iOS users try to update the Apple OS on a PC or Mac. It appears after a security test fails. The test was designed to check if Touch ID works on a device after it leaves an Apple factory.
The company also apologized for any problems Error 53 caused its customers and claimed it was only designed as a factory test. Customers who replaced devices not under warranty can receive a refund from AppleCare.
Apple's iPhone update will not re-enable Touch ID. It is a big security risk to allow a malicious third-party repair shop or corrupt part to allow access to a handset or its data.
Apple is now facing a class-action lawsuit about the Error 53 issue. Its iOS update could help to resolve some of the claims made by angry customers.
iPhone users will have to get Touch ID functionality back by having an official Apple repair shop replace the home button. They can also now get a new home key without Touch ID via a third-party shop without risking a bricked phone.
Here's an explanation of Error 53: