UPDATED 22:57 EDT / FEBRUARY 18 2016

NEWS

Apple eats humble pie, apologizes over Error 53 and issues a fix

Apple, Inc. has eaten some humble pie and apologized for the Error 53 issue while at the same time issuing a fix.

If you’ve not been following the news, iPhone users who had the Touch ID sensor in their phones repaired by a third party, or even by themselves, found their iPhone’s bricked with an Error 53 message.

Originally Apple said that the error message was a security measure, in effect implying that users could only have their phones fixed by an authorized repairer, or Apple itself.

Speaking to TechCrunch, Apple released the following statement:

Some customers’ devices are showing ‘Connect to iTunes’ after attempting an iOS update or a restore from iTunes on a Mac or PC. This reports as an Error 53 in iTunes and appears when a device fails a security test. This test was designed to check whether Touch ID works properly before the device leaves the factory.

Today, Apple released a software update that allows customers who have encountered this error message to successfully restore their device using iTunes on a Mac or PC.

We apologize for any inconvenience, this was designed to be a factory test and was not intended to affect customers. Customers who paid for an out-of-warranty replacement of their device based on this issue should contact AppleCare about a reimbursement.

A support document published on Apple’s website details how to fix the Error 53 issue:

  1. Make sure that you have the latest version of iTunes.
  2. Force restart your device.
  3. Try to restore your device again.
  4. If you still see error 53 when you try to restore your device, contact Apple Support. If the restore won’t finish and you see a different error code, learn what to do.

Of note, though, the fix for Error 53 does not restore Force Touch versus unbricking the phone.

Pathetic

The control-freakery of Apple is the thing of legend, so the whole Error 53 shouldn’t be a great surprise, but that doesn’t make it any less pathetic.

If you buy a phone you have a reasonable expectation that the phone will work, even in the event of an otherwise perfectly fine repair, and that’s the thing here: at no stage is it suggested that these repairs were killing the phones, it was Apple’s software that was causing the issue.

Some credit is due to Apple for at least apologizing and eventually fixing the issue, although when you’ve got a gun to your head amazing things do occur, and the gun, in this case, is a class action lawsuit over the matter.

photo credit: via photopin (license)

 


A message from John Furrier, co-founder of SiliconANGLE:

Your vote of support is important to us and it helps us keep the content FREE.

One click below supports our mission to provide free, deep, and relevant content.  

Join our community on YouTube

Join the community that includes more than 15,000 #CubeAlumni experts, including Amazon.com CEO Andy Jassy, Dell Technologies founder and CEO Michael Dell, Intel CEO Pat Gelsinger, and many more luminaries and experts.

“TheCUBE is an important partner to the industry. You guys really are a part of our events and we really appreciate you coming and I know people appreciate the content you create as well” – Andy Jassy

THANK YOU