error 53

Apple Sued by Australian Regulator Over ‘Error 53’ iPhone Shutdowns

An Australian consumer watchdog has started legal proceedings against Apple over claims that the company refused to service "Error 53" affected devices which have been previously touched by a third party repairer. The Australian Competition and Consumer Commission (ACCC) alleges Apple violated Australia’s consumer law by shutting down or “bricking” the devices, and then telling customers...

Apple Fixes iPhone ‘Error 53’ with New iOS 9.2.1 Release

The controversy around “Error 53” code may end today: alongside issuing a software update (iOS 9.2.1, build 13D20), Apple has publicly apologized for the inconvenience caused by this “factory test” that bricked the iPhones, as first reported by the Guardian. You may recall from earlier reports that the error was caused by a third-party repair...

Apple Faces Class Action Over “Error 53” iPhone 6 Controversy

Seattle-based law firm Pfau Cochran Vertetis Amala PLLC (PCVA) has moved forward filing a class-action lawsuit against Apple over the “error 53” iPhone 6 and 6 Plus controversy. The “error 53” was first reported by the Guardian last week, it is an error code iPhone 6 owners receive after a third-party repair was made on...

Apple Faces Possible Class Action Over Touch ID “Error 53”

Law firms are already gearing up for lawsuits against Apple following news that the iPhone maker bricks iPhone 6 and 6 Plus units following third-party Touch ID repairs, the Guardian reports. It all started with a report from late last week about the “Error 53” code, which renders the handsets unusable. What makes the cases...

“Error 53” Bricks iPhone 6 Units After Unofficial Touch ID Repairs

Users who had their iPhone 6 unit repaired by third-party technicians have started reporting a mysterious "error 53" problem which bricks their handset (via the Guardian). The issue seems to be specific to iPhone 6 users who have had their Touch ID repaired by a "non-official" company or individual. Interestingly, the problem appeared only after iOS 9 was...