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 > US District Court drops 'Error 53' case for lack of standing, evidence

US District Court drops 'Error 53' case for lack of standing, evidence
Thread Tools
NewsPoster
MacNN Staff
Join Date: Jul 2012
Status: Offline
Reply With Quote
Jun 21, 2016, 06:50 PM
 
A lawsuit borne of the short-lived "Error 53" issue that happened to some iOS devices where the Touch ID button had been replaced or repaired by unauthorized non-Apple personnel was dismissed on Tuesday by a US District Court judge, who rejected both the plaintiff's original complaints and their amended claims following Apple's release of a tool to restore iPhones bricked by the anti-tampering feature, which was designed to prevent third-parties from altering or hacking into the Touch ID sensor.

The error only ever occurred to users who had damaged their Touch ID home buttons on the iPhone 6 or newer, and had them replaced by non-Apple service outlets. Even if the authentic replacement parts were used and the repair restored functionality, users would see the iPhone offer an "Error 53" message and refuse to be restored or operate following an iOS update or restore, where the part would fail a validation check. Apple later admitted the error was meant to be a factory test designed to prevent tampering.



The plaintiffs in the case originally claimed that Apple had failed to warn customers about security features that could render their iPhones inoperable, and claimed the problem caused "permanent data loss." They also accused the company of false advertising, saying the company knew of the "Error 53" problem inherent in the design of the device. After Apple offered a fix that restored the bricked iPhones and compensated iPhone owners who had paid for third-party repairs, the plaintiffs amended the claims to maintain that Apple hadn't offered consumers a blanket fix, and hadn't done enough to warn customers of the potential risk.

The judge dismissed all the claims, noting that "the mere fact that a company has designed a product doesn't mean it automatically knows about all of that product's potential design flaws," and "with regard to Apple's alleged omissions, the plaintiffs' position seems to be that Apple should have 'disclosed that their devices would be destroyed by embedded features if they had repaired devices using an independent service and then updated to certain iOS versions." But the plaintiffs haven't plausibly alleged that Apple actually knew of this alleged risk,' but the plaintiffs haven't plausibly alleged that Apple actually knew of this alleged risk."

He went on to note that the plaintiffs were unable to prove any permanent data loss as a direct result of the error 53 issue, and could not prove that Apple had engaged in any false advertising. He further dismissed the claim that Apple hadn't done enough to address the problem, since the company both restored bricked iPhones, and ensured that all users affected by the issue eventually got repairs that restored the iPhones to working order, as well as issued a software update to prevent the bricking issue from happening in similarly-altered iPhones in the future, though the validation check will still disable Touch ID.
     
sgs123
Junior Member
Join Date: Dec 2005
Status: Offline
Reply With Quote
Jun 22, 2016, 11:11 AM
 
Copy/paste error end of 2nd paragraph.
     
   
 
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 05:41 PM.
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.,