Skip to Main Content
PCMag editors select and review products independently. If you buy through affiliate links, we may earn commissions, which help support our testing.

How Apple Missed the Boat on Error 53

Error 53 isn't a bug, it's a security feature. But Apple screwed up and didn't get out ahead of it.

February 17, 2016
Touch ID

Lawyers' phones are lighting up. Message boards are jammed with complaints. Apple is being condemned. All sorts of tales of woe are being exchanged. Your phone is now permanently bricked. Ladies and gentlemen, Error 53!

Opinions If you're not aware, Error 53 bricks your iPhone 6 and above once the phone discovers that someone, usually a third-party repair operation, has tried to fix a busted (usually) Touch ID-enabled home button. Couple that with an upgraded mobile operating system, and you might see the dreaded Error 53.

I do not have an iPhone 6 and can only read the thousands of reports. Apparently the bricking is permanent because taking your phone to an unauthorized dealer voids your warranty so Apple won't fix it. But while everyone is complaining about this abomination, as they see it, I commend Apple for doing the right thing. Error 53 is exactly what should happen on a device that is supposed to be secure.

If you have a smartphone that stores your credit cards and other secure data, then it better actually be secure.

It's a phone that uses your fingerprint to boot. A phone that even the NSA cannot crack (supposedly). Thus, if the phone is stolen, a criminal should not be able to crack the case, jigger the home button fingerprint reader, and unlock the phone before using the touch-to-pay feature all over town.

The phone needs to be locked down immediately. It should indeed be bricked. The users should assume the phone has been stolen and there should be no way anyone can get at anything. This is security at its finest.

What is not clear in all the reports is what happens to a phone that is purposely unsecure. Let's say you disable the security features, including the fingerprint reader AND the passcode. Do you also end up with a bricked phone under the same circumstances? Nobody is asking or answering this question.

If, in fact, the unsecure iPhone is bricked for security reasons when no security was desired, then Apple has a legal problem. This is the direction this investigation should turn.

Recommended by Our Editors

The Apple support forums are of little value, and the company should take them more seriously. Numerous unanswered questions stagnate there. Here is an example page where a simple question dating back to September of last year remains unanswered. The question is kind of answered elsewhere but why it is allowed to languish like this? It should be addressed by Apple.

Users solicit answers to sometimes complex questions on the Apple forums. Exactly why the company cannot afford a crew of perhaps a dozen full-time people offering answers is a mystery. The company is one of the biggest in the world and it lets this amateurish forum exist in this form? Why?

Ultimately, Error 53 was first addressed in a February piece from The Guardian. But Apple should have addressed it long ago. If this is a security feature, as I believe it to be, why not report to the user something other than the vague "Error 53." How about the truth? Like, "The security systems built into this iPhone have been breached and now this phone is unusable. Have a nice day." Much better.

Like What You're Reading?

Sign up for SecurityWatch newsletter for our top privacy and security stories delivered right to your inbox.

This newsletter may contain advertising, deals, or affiliate links. Subscribing to a newsletter indicates your consent to our Terms of Use and Privacy Policy. You may unsubscribe from the newsletters at any time.


Thanks for signing up!

Your subscription has been confirmed. Keep an eye on your inbox!

Sign up for other newsletters

TRENDING

About John C. Dvorak

Columnist, PCMag.com

John C. Dvorak is a columnist for PCMag.com and the co-host of the twice weekly podcast, the No Agenda Show. His work is licensed around the world. Previously a columnist for Forbes, PC/Computing, Computer Shopper, MacUser, Barrons, the DEC Professional as well as other newspapers and magazines. Former editor and consulting editor for InfoWorld, he also appeared in the New York Times, LA Times, Philadelphia Enquirer, SF Examiner, and the Vancouver Sun. He was on the start-up team for C/Net as well as ZDTV. At ZDTV (and TechTV) he hosted Silicon Spin for four years doing 1000 live and live-to-tape TV shows. His Internet show Cranky Geeks was considered a classic. John was on public radio for 8 years and has written over 5000 articles and columns as well as authoring or co-authoring 14 books. He's the 2004 Award winner of the American Business Editors Association's national gold award for best online column of 2003. That was followed up by an unprecedented second national gold award from the ABEA in 2005, again for the best online column (for 2004). He also won the Silver National Award for best magazine column in 2006 as well as other awards. Follow him on Twitter @therealdvorak.

Read John C.'s full bio

Read the latest from John C. Dvorak