Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > News > Mac News > Apple issues iOS update to fix iPhones bricked by Error 53

Apple issues iOS update to fix iPhones bricked by Error 53
Thread Tools
NewsPoster
MacNN Staff
Join Date: Jul 2012
Status: Offline
Reply With Quote
Feb 18, 2016, 03:53 PM
 
Apple has released an update for iOS 9.2.1 that fixes the "Error 53" bug that recently became a major problem for some users after repairing their Touch ID-equipped devices via unofficial means, leaving the iPhones non-functional and unrepairable. The updated version of iOS 9.2.1 is able to restore the "bricked" iPhones, with Apple also issuing an apology to affected users, as well as offering reimbursement to some users who ended up paying for out-of-warranty replacements of their devices.

According to the support page, the update takes place via iTunes, with users needing to force restart and then restore their devices to carry out the fix. Users who usually perform over-the-air updates via iCloud are unaffected, and the fix does not apply to them.



A statement from Apple issued to TechCrunch advises the Error 53 code was designed to check "whether Touch ID works properly before the device leaves the factory," with the update preventing the error from appearing again. "We apologize for any inconvenience; this was designed to be a factory test, and was not intended to affect customers," writes Apple, before suggesting that customers "who paid for an out-of-warranty replacement of their device based on this issue should contact AppleCare for reimbursement."

While the update does revive an iPhone from being bricked, it will not re-enable Touch ID sensors if they were replaced as part of a third-party repair. This is due to the need to keep the Secure Enclave as safe as possible, and replacement parts from an unknown source could pose a security risk if it is allowed to access the data.

Customers who saw the error after a repair by an Apple Store, Service Center, or Authroized Service Provider are asked to contact Apple Support for a presumably-free or low-cost fix. Those affected following a third-party repair or one performed themselves are also advised to contact Apple Support "about pricing information for out-of-warranty repairs."
( Last edited by NewsPoster; Feb 18, 2016 at 03:57 PM. )
     
Ham Sandwich
Guest
Status:
Reply With Quote
Feb 18, 2016, 04:20 PM
 
Well at least it could help Apple avoid the whole lawsuit since they're doing something proactive. Though it doesn't fix the "Set the date to September 1, 1970" bug that also bricks your iPhone. Although I think a fix for that is coming.
     
panjandrum
Dedicated MacNNer
Join Date: Dec 2004
Location: West Michigan
Status: Offline
Reply With Quote
Feb 18, 2016, 11:51 PM
 
This is great news and a good compromise for Apple to take (getting the phones to work again; refunding money, but not re-enabling the touch-id on these phones). Maybe in the future they can just provide a dialogue when they detect a non-Apple sensor, something basic allowing the user to enable the non-Apple sensor with a warning that it might not be secure.
     
   
Thread Tools
 
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Top
Privacy Policy
All times are GMT -4. The time now is 11:38 AM.
All contents of these forums © 1995-2017 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2017, Jelsoft Enterprises Ltd.,