{"id":3181,"date":"2016-03-03T23:54:53","date_gmt":"2016-03-03T23:54:53","guid":{"rendered":"http:\/\/jolt.richmond.edu\/?p=3181"},"modified":"2019-03-08T19:52:18","modified_gmt":"2019-03-09T00:52:18","slug":"error-53-the-iphone-error-message-enraging-apple-users-worldwide","status":"publish","type":"post","link":"https:\/\/blog.richmond.edu\/jolt\/2016\/03\/03\/error-53-the-iphone-error-message-enraging-apple-users-worldwide\/","title":{"rendered":"Error 53: The iPhone Error Message Enraging Apple Users Worldwide"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-3182\" src=\"http:\/\/jolt.richmond.edu\/files\/2017\/03\/image-53-346x194.jpg\" alt=\"image 53\" width=\"346\" height=\"194\" \/><\/p>\n<p>By: Meghan Murphy,<\/p>\n<p>Shattered your iPhone 6 screen? Before having it fixed\u2014beware third-party repairs. iPhone users around the world are outraged at the \u201cError 53\u201d message appearing on their screens after updating to the newest iOS software.<a href=\"#_ftn1\" name=\"_ftnref1\">[1]<\/a> As The Guardian reported recently, iPhone 6, 6S and 6+ users are relating countless stories of needing their shattered screens fixed, and going to a local merchant to have the work done.<a href=\"#_ftn2\" name=\"_ftnref2\">[2]<\/a> Sometimes in the course of these repairs, the original home button was damaged and replaced.<a href=\"#_ftn3\" name=\"_ftnref3\">[3]<\/a> Repaired well, these phones worked for months\u2014until they attempted to update the iOS software as Apple recommends, and received the \u201cError 53\u201d message before their phones became unusable.<a href=\"#_ftn4\" name=\"_ftnref4\">[4]<\/a><\/p>\n<p>The problem appears to be in the hardware\u2014often within the course of screen repair, the hardware connecting the fingerprint sensor on the home button could be damaged.<a href=\"#_ftn5\" name=\"_ftnref5\">[5]<\/a> When the software attempts to update, it runs a diagnostic to make sure that all of the hardware is intact and working\u2014and if the diagnostic finds a non-original home button, it shuts the entire phone down.<a href=\"#_ftn6\" name=\"_ftnref6\">[6]<\/a> Apple claims this is a security measure, to make sure that no one can tamper with the home button or install another fingerprint sensor to gain access to someone else\u2019s phone.<a href=\"#_ftn7\" name=\"_ftnref7\">[7]<\/a> Even if this is the case, such an all-encompassing security measure seems extreme, especially considering customers had <em>no notice<\/em> that it would occur.<a href=\"#_ftn8\" name=\"_ftnref8\">[8]<\/a><\/p>\n<p>Seattle firm PCVA agreed\u2014and filed a class action lawsuit against Apple on February 5<sup>th<\/sup>, 2016.<a href=\"#_ftn9\" name=\"_ftnref9\">[9]<\/a> As a firm press release stated, \u201cWe believe that Apple may be intentionally forcing \u00a0\u00a0\u00a0users to use their repair services, which cost much more than most third party repair shops. Where you could get your screen replaced by a neighborhood repair facility for $50-80, Apple charges $129 or more. There is incentive for Apple to keep end users from finding alternative methods to fix their products.\u201d<a href=\"#_ftn10\" name=\"_ftnref10\">[10]<\/a> However, in the interim, business savvy Apple took a U-turn and now claims now that \u201c[diagnostic] test was designed to check whether Touch ID works properly before the device leaves the factory, and wasn\u2019t intended to affect customers.\u201d<a href=\"#_ftn11\" name=\"_ftnref11\">[11]<\/a> As of February 18<sup>th<\/sup>, Apple is now providing new software available in iOS update 9.2.1, which they say will restore previously \u201cbricked\u201d devices, and offering reimbursements to those who paid for out-of-warranty device replacements.<a href=\"#_ftn12\" name=\"_ftnref12\">[12]<\/a><\/p>\n<p>The future of the lawsuit is unclear at this juncture. While Apply has clearly attempted to mitigate the damage by restoring old devices and offering reimbursements, surely many loyal Apple customers are still angry at Apple\u2019s actions. It is possible that even with the software fix, miffed customers will still want to proceed with the lawsuit\u2014although perhaps with a different spin. Only time will tell.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"#_ftnref1\" name=\"_ftn1\">[1]<\/a> Miles Brignall, \u201c\u2018Error 53\u2019 fury mounts as Apple software update threatens to kill your iPhone,\u201d Guardian (Feb. 5, 2016, 1:59 PM), http:\/\/www.theguardian.com\/money\/2016\/feb\/05\/error-53-apple-iphone-software-update-handset-worthless-third-party-repair.<\/p>\n<p><a href=\"#_ftnref2\" name=\"_ftn2\">[2]<\/a> <em>Id.<\/em><\/p>\n<p><a href=\"#_ftnref3\" name=\"_ftn3\">[3]<\/a> Jack Nicas, \u201c\u2018Error 53\u2032: Your Repaired iPhone Is Dead,\u201d Wall Street J. Blog (Feb. 5, 2016, 4:07 PM), http:\/\/blogs.wsj.com\/digits\/2016\/02\/05\/apple-error-message-killing-iphones\/?mod=trending_now_4.<\/p>\n<p><a href=\"#_ftnref4\" name=\"_ftn4\">[4]<\/a> <em>Id.<\/em><\/p>\n<p><a href=\"#_ftnref5\" name=\"_ftn5\">[5]<\/a> Brignall, <em>supra<\/em> note 1.<\/p>\n<p><a href=\"#_ftnref6\" name=\"_ftn6\">[6]<\/a> <em>Id.<\/em><\/p>\n<p><a href=\"#_ftnref7\" name=\"_ftn7\">[7]<\/a> Chris Johnston, \u201cApple says iPhone &#8216;Error 53&#8242; is to protect customers&#8217; security,\u201d guardian (Feb. 6, 2016, 8:57 PM), http:\/\/www.theguardian.com\/technology\/2016\/feb\/06\/apple-says-iphone-error-53-is-to-protect-customers-security.<\/p>\n<p><a href=\"#_ftnref8\" name=\"_ftn8\">[8]<\/a> Nicas, <em>supra <\/em>note 3.<\/p>\n<p><a href=\"#_ftnref9\" name=\"_ftn9\">[9]<\/a> Miles Brignall, \u201cApple under pressure as lawyers pledge action over &#8216;Error 53&#8217; codes,\u201d Guardian (Feb. 8, 2016, 11:56 AM), http:\/\/www.theguardian.com\/business\/2016\/feb\/08\/apple-under-pressure-lawyers-error-53-codes.<\/p>\n<p><a href=\"#_ftnref10\" name=\"_ftn10\">[10]<\/a> \u201cClass Action Lawsuit: Apple IPhone \u2018Error 53,\u2019\u201d PCVA Law Firm (Feb. 5, 2016), http:\/\/www.pcvalaw.com\/apple-iphone-error-53-lawsuit\/ (last visited Feb. 23, 2016).<\/p>\n<p><a href=\"#_ftnref11\" name=\"_ftn11\">[11]<\/a> \u201cIf you see error 53 and your iPhone or iPad gets stuck on the \u2018Connect to iTunes\u2018 screen,\u201d Apple https:\/\/support.apple.com\/en-us\/HT205628 (last modified Feb. 19, 2016).<\/p>\n<p><a href=\"#_ftnref12\" name=\"_ftn12\">[12]<\/a> <em>Id.<\/em><\/p>\n<p>&nbsp;<\/p>\n<p>Photo Source: \u00a0http:\/\/rack.2.mshcdn.com\/media\/ZgkyMDE2LzAyLzA2LzI5L2FwdG91Y2hpZC44ZDU3Mi5qcGcKcAl0aHVtYgk5NTB4NTM0IwplCWpwZw\/18551a5a\/ba8\/ap-touch-id.jpg<\/p>\n","protected":false},"excerpt":{"rendered":"<p>By: Meghan Murphy, Shattered your iPhone 6 screen? Before having it fixed\u2014beware third-party repairs. iPhone users around the world are outraged at the \u201cError 53\u201d message appearing on their screens after updating to the newest iOS software.[1] As The Guardian reported recently, iPhone 6, 6S and 6+ users are relating countless stories of needing their [&hellip;]<\/p>\n","protected":false},"author":4287,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[51366],"tags":[],"class_list":["post-3181","post","type-post","status-publish","format-standard","hentry","category-blog-post"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/paMHOZ-Pj","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/posts\/3181","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/users\/4287"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/comments?post=3181"}],"version-history":[{"count":0,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/posts\/3181\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/media?parent=3181"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/categories?post=3181"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/tags?post=3181"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}