Apple Facing Class Action Lawsuit Over 'Error 53' iPhone 6 Bricking

Discussion in 'MacRumors.com News Discussion' started by MacRumors, Feb 11, 2016.

  1. MacRumors macrumors bot

    MacRumors

    Joined:
    Apr 12, 2001
    #1
    [​IMG]


    [​IMG]
    Seattle-based law firm Pfau Cochran Vertetis Amala (PCVA) today followed through with plans to bring a class action lawsuit against Apple over the "Error 53" controversy that made headlines last week.

    "Error 53" is the error code that some iPhone 6 owners have received after third-party repairs that affect Touch ID were made to their iPhones, rendering the devices unusable. As explained by iFixit, repairs made by third-party services using components not sourced from the original device cause the iPhone to fail a Touch ID validation check because the mismatched parts are unable to properly sync. Parts that can impact Touch ID include the screen, flex cable, and Home button.

    When this Touch ID validation check fails during an iOS update or restore, Apple disables the iPhone, effectively "bricking" it in an effort to protect Touch ID and the related Secure Enclave that stores customer fingerprint information. Apple says that without the validation check, a malicious Touch ID sensor could be used to gain access to the Secure Enclave.

    PCVA attorney Darrell Cochran, who is leading the Error 53 lawsuit, claims that Apple's security argument is invalid because affected iPhones often work fine for several months following repairs as the validation check only occurs when downloading a new version of iOS. He also cites Apple's failure to give a warning about the consequence of an update as an issue that will be featured in the lawsuit.
    PCVA is aiming to get affected iPhone customers new, working devices to "provide immediate relief" to consumers. It is also seeking upwards of $5 million in damages and an update to eliminate the repair restrictions. PCVA is asking customers who have been impacted by Error 53 to get in touch.

    Aside from explaining the reasoning behind the Error 53 message and its consequences, Apple has remained quiet about the controversy. MacRumors has, however, heard from a retail source that certain Apple Stores have received the go ahead from Apple to replace third-party screens and other components to resolve the issue. It is not yet clear if this replacement policy will be extended to all Apple Stores or if Apple will make an official comment on the situation.

    Article Link: Apple Facing Class Action Lawsuit Over 'Error 53' iPhone 6 Bricking
     
  2. farewelwilliams macrumors 6502a

    Joined:
    Jun 18, 2014
    #2
    and then Apple pushes update to 9.3 to disable error and everything goes away.
     
  3. Markoth macrumors regular

    Markoth

    Joined:
    Oct 1, 2015
    Location:
    NYC
    #3
    So... They made third-party repairs, which annulled their warranty, and bricked their phone and now they're suing? Why does Apple owe them anything, exactly? Didn't they agree to Apple's terms when they purchased the device?
     
  4. ToroidalZeus macrumors 68020

    ToroidalZeus

    Joined:
    Dec 8, 2009
    #4
    Seems like they have legit case.

    There is a lot of misinformation on this subject. The "brick" happens when someone replaces the TouchID sensor--with a GENUINE OR 3rd party part. Apple is most likely within their right to disable TouchID when they detect a mismatched sensor as it's a security risk. However bricking the device and not giving any warning is probably going too far.
     
  5. Small White Car macrumors G4

    Small White Car

    Joined:
    Aug 29, 2006
    Location:
    Washington DC
    #5
    I agree that their Touch ID should be disabled, but is there some reason that's not possible?

    If they got a message saying "Touch ID disabled" I'd say these people have no case.

    But as it is, isn't this like making your iMac refuse to boot because you broke the DVD drive?
     
  6. goobot macrumors 601

    goobot

    Joined:
    Jun 26, 2009
    Location:
    long island NY
    #6
    It's more like a car not starting because you tried a cheap knockoff key.
     
  7. TouchMint.com macrumors 65816

    TouchMint.com

    Joined:
    May 25, 2012
    Location:
    Phoenix
    #7
    Thanks for doing us this great service lawyer! Can't wait for my pennies while the lawyer gets the millions.
     
  8. carrrrrlos macrumors 6502

    carrrrrlos

    Joined:
    Sep 19, 2010
    Location:
    PNW
  9. ToroidalZeus macrumors 68020

    ToroidalZeus

    Joined:
    Dec 8, 2009
    #9
    That's semi-true however there is no fix in case. In the case of the car you can get a proper key from the dealership. Plus you don't need TouchID for a functional phone as it's an extra feature and the phone works properly without it.
     
  10. Small White Car macrumors G4

    Small White Car

    Joined:
    Aug 29, 2006
    Location:
    Washington DC
    #10
    But if I go into setting and turn off Touch ID, my phone still works. Does it not?

    You make it sound like it's impossible to use the phone without Touch ID, but it's an option right there in the settings.
     
  11. lampwins macrumors newbie

    Joined:
    Feb 11, 2016
    #11
    It amazes me how little people actually care about their security (and do not confuse security with privacy here). Apple is trying to protect its users, but they are too stupid to realize.

    But on the other hand, Availability is a part of the CIA triad so bricking the phone does violate this premise.

    However, Apple is doing this because a piece of hardware inserted between the Touch-ID Sensor and the Secure Enclave could in theory either intercept scans or access the enclave.

    They are doing this to protect you, not as a "screw you for trying to fix your own phone." People will always see what they want to see though, I suppose.
     
  12. Rhonindk macrumors 68000

    Rhonindk

    #12
    iPhone 6/6+ are out of warranty unless you purchased Apple Care.
    Warranty has little to do with this for the 6/6+
     
  13. tranceme macrumors member

    Joined:
    Jan 10, 2006
    Location:
    California, US
    #13
    You can get proper fix from Apple. Not sure what you mean.
     
  14. btrach144 macrumors 6502a

    btrach144

    Joined:
    Aug 28, 2015
    Location:
    Redmond, WA USA
    #14
    People are sue crazy. Sheesh... I'm all for suing when warranted but this isn't the time.
     
  15. blackoutz macrumors member

    blackoutz

    Joined:
    Oct 12, 2015
    Location:
    Baltimore
    #15
    No. It's like the consumer uses a knockoff key and the manufacturer destroy the engine.
     
  16. Small White Car macrumors G4

    Small White Car

    Joined:
    Aug 29, 2006
    Location:
    Washington DC
    #16
    Disabling Touch ID would protect them. What function does killing the OS serve over that?
     
  17. tranceme macrumors member

    Joined:
    Jan 10, 2006
    Location:
    California, US
    #17
    So, you're saying if you had Apple replace with a GENUINE sensor, it's brick? I don't think that is the case.

    Also, in another life, I would reprogram chips for cars. The manufacturers were starting to reject these if modified. This is not new. The car would not start.
     
  18. Muzzakus macrumors member

    Joined:
    May 23, 2011
    #18
    Totally justified lawsuit. There is absolutely no reason to brick the phone for an optional feature such as touchid. Invalidate the fingerprints and allow the user to continue using the phone via the regular pin.
     
  19. garylapointe macrumors 65816

    garylapointe

    Joined:
    Feb 19, 2006
    Location:
    Dearborn (Detroit), MI, USA
    #19
    I agree. It seems simple enough to just disable the touchpad and give the warning message (with the added detail that it's possible things have been attempted to be compromised).

    Someone would still need the passcode to get in and if they had the passcode they could have just turned off the fingerprint scanner in the first place.

    But since we're really not in the know on there there're is a definite possibility that there is more to it that...

    Gary
     
  20. LogicalApex macrumors newbie

    Joined:
    Nov 13, 2015
    #20
    For Apple it is a lot more complicated that this. There is nothing saying that this cares if you have TouchID enabled or not, I suspect it doesn't care either way... The core of the issue is a major component of the security system of the device has been compromised. Since all of the security on your iOS device is done locally with all of the keys being stored on the device in the secure element it locks up when something is outside of expected parameters...

    The system is a lot like Secure Boot on Windows 10. Everything has to check out or everything fails. You can't trust anything when one part is out of line so you trust none. Otherwise, the whole system can be compromised.
     
  21. garylapointe macrumors 65816

    garylapointe

    Joined:
    Feb 19, 2006
    Location:
    Dearborn (Detroit), MI, USA
    #21
    I think it still needs to be properly synced/paired.

    They car would never ever start again?

    Gary
     
  22. Small White Car macrumors G4

    Small White Car

    Joined:
    Aug 29, 2006
    Location:
    Washington DC
    #22
    I would absolutely believe this.

    If so, though, Apple really should put out some kind of statement on this rather than just having people have to guess what the reasoning is.
     
  23. iParis macrumors 68040

    iParis

    Joined:
    Jul 29, 2008
    Location:
    New Mexico
    #23
    Not really warranty, but it invalidates Apple working on the screen for even a cost.
     
  24. kd5jos macrumors 6502

    kd5jos

    Joined:
    Oct 28, 2007
    Location:
    Denver, CO
    #24
    Could we just make it so that S versions of the iPhone are for those of us concerned about security, and make the C versions of the phone for Consumers?

    Then I get the security I require, and the average person that doesn't mind playing roulette gets to do so.
     
  25. garotemonkey macrumors newbie

    Joined:
    Mar 10, 2005
    #25
    Never ever ever!!!!
    Ever!!! (Raaaaaaaage!)

    Until the problem was fixed.
     

Share This Page