This was my point too. If Apple is now changing their conversation - then it stands to reason that TouchID wasn't as secure as they stated, right? Now they believe it's hackable? What does that say for Apple Pay then?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Facing Class Action Lawsuit Over 'Error 53' iPhone 6 Bricking
- Thread starter MacRumors
- Start date
- Sort by reaction score
This was my point too. If Apple is now changing their conversation - then it stands to reason that TouchID wasn't as secure as they stated, right? Now they believe it's hackable? What does that say for Apple Pay then?
This issue is no different the the original Xbox... The motherboard and hard drive had to have matching ID's or it would fail to boot and not work. (Not using mod chips)
The morons should have purchased Apple care.
A persons stupid Mistake always ends up being blamed on somebody else....
Next some moron will sue because the Apple phone won't install android software.
Companies have a right to protect their product and end user. If that 3rd party Touch ID did keep working after the update how does that person know their finger print data and information wasn't being sent out to a botnet or host collecting data... With the way stuff has been nowadays... Maybe the 3rd party Touch ID has a new encrypting malware with would lock the phone down on its own...
Everybody whines about closed systems and proprietary equipment but there is a reason for it in today's world of data breaches and security issues.
The morons should have purchased Apple care.
A persons stupid Mistake always ends up being blamed on somebody else....
Next some moron will sue because the Apple phone won't install android software.
Companies have a right to protect their product and end user. If that 3rd party Touch ID did keep working after the update how does that person know their finger print data and information wasn't being sent out to a botnet or host collecting data... With the way stuff has been nowadays... Maybe the 3rd party Touch ID has a new encrypting malware with would lock the phone down on its own...
Everybody whines about closed systems and proprietary equipment but there is a reason for it in today's world of data breaches and security issues.
Considering some of the users complainingg went to authorized repair locations and/or didn't even perform a repair, your rant is pretty much invalidated.
the repair causes the device to reboot so u have to put in the owners passcode anyway so whats the big deal?
i mean the TouchID and AppStore require your passcode / AppleID password after a reboot before you can use your TouchID so Apple clearly thinks a Passcode is more secure. In that case they could simply disable TouchID and still give access if you know the passcode. no need to brick the whole device
Yes, because this is such a widespread occurrence. And, for the few that have rolled the dice going to Fast Freddies Fone Fix, those walking away with disabled phones will be extremely pleased and motivated to go out and purchase another iPhone.
Indeed, a huge money grab for Apple. Such a huge money grab that Apple put this system in place solely to encourage unhappy phone owners to continue to be loyal Apple customers for decades into the future. I sense several billion dollars worth of new revenue from happy customers due to this custom-designed money grab alone due to the extraordinary goodwill it will engender!
I smell some lacking the ability to think things through.
I think there is a general misunderstanding because the previous article was so poorly worded. The error is occurring when either A) the phone is repaired with a 3rd party part that is not OEM and, thus, does not meet Apple's security standards, or B) The phone was not properly calibrated by the repair facility (Apple or AASP), and the sensor was not paired with the MLB of the phone. The fact that it can hit many months later is certainly frustrating, especially considering there is no warning for this new behavior in the update logs, but, from Apple's standpoint, I can see why they do it. If this can become a threat to the security enclave, they want to nip it in the bud before the snakes realize it and come up with ways to expose the loophole. It's more than "Oh Apple just wants you to pay for their service."
Thanks for adding some clarity and logic to the thread!
Man, what a lot of dumb fanboys in this thread. These are Apple users being screwed over here, you know, people like you. The fact remains that Apple are such liars with this error 53 bricking. If my passcode supersedes my finger print in all cases (which it does) then why brick a phone when the fingerprint sensor is compromised? My fingerprint is not required after a reboot and not required after 48 hours.
I like the security but it´s not too much to ask that they inform about it..
My old Nintendo Wii had a warning about mod chips and soft mods before you could accept the software update.
Apple could insert a line of text in the iOS update info.
"Non original parts might cause the phone to become unusable"
Do you accept? Y/N
My old Nintendo Wii had a warning about mod chips and soft mods before you could accept the software update.
Apple could insert a line of text in the iOS update info.
"Non original parts might cause the phone to become unusable"
Do you accept? Y/N
After the lawyers take 80% of the cut, Apple will send out $25 vouchers toward the purchase of a new iPhone to those affected.
The only people who win in a class action are the lawyers.
That is not factually correct. Look at my post above. Errors occurred three years ago if the tech didn't pair up the new sensor with the A7 chip. Only an Apple tech could do that.
But you would pay the dealership for the proper key that must be used. Same with those named in the Lawsuit... they should pay Apple to fix the error because the phone should not have been opened in the first place.
[doublepost=1455288928][/doublepost]
So then those people, would go to Apple and have the phone fixed free of charge. This suit is fighting for those who went to a third party repair location, that are not authorized to work on Apple devices, and trying to get their phone fixed.
I'm 50/50 on this, maybe its a bug I dont know. I will say this though, Apple is so big that they will be wrong no matter what they do. It comes with the territory. Look what happened because Tim Cook took a blurry picture.
No, you are wildly misinformed. Lawyers take is about 15%. The $ seems high because it's going to one source whereas the remaining 85% is being divided up by thousands, even hundreds of thousands, of class members. Keep in mind they lawyers filing the suit are paying 100% of costs and fees out of their own pocket. If they lose it's on them. They, not the class members are taking the risk. Also, any class member can opt-out from the suit and file their own suit, and also bear the costs involved.
Also - and correct me if I am wrong - the settlement may or may not cover the devices. Apple may be forced to replace phone and pay for damages. I'm not saying it's likely - but the outcome may not just be cash.
This lawsuit is a complete joke. Apple will just do whatever it takes to make the lawsuit go away because of the bad publicity. But look, it's simple folks...
Say Apple had a condition where if (X == Y), the result of that is true. This means the validity of the pairing between the Touch ID sensor and the CPU is okay. And in a later update, increases the strength of that condition by changing it to:
if (X == Y) && (A == B) && (C == D), which makes the result that used to be true, now false.
Then there is no case. That is how security is improved. And if the updates Apple releases are that strict to reject third-party Touch ID sensors to prevent "fake" parts, then I'm all for it.
I've witnesses first hand "Error 53." My cousin replaced his screen using a third party service. His home button worked but the Touch ID did not. When he updated his iPhone to iOS 9, he was displayed a "Connect to iTunes" screen which resulted in iTunes displaying "Error 53."
We took it to Apple and they said they would not be able to repair it, and instead they would need to replace the phone paying the replacement fee. They said the Warranty on the phone has been voided and repairs could not be made because the iPhone was opened by a third party. I ended up paying for a replacement phone for him.
Say Apple had a condition where if (X == Y), the result of that is true. This means the validity of the pairing between the Touch ID sensor and the CPU is okay. And in a later update, increases the strength of that condition by changing it to:
if (X == Y) && (A == B) && (C == D), which makes the result that used to be true, now false.
Then there is no case. That is how security is improved. And if the updates Apple releases are that strict to reject third-party Touch ID sensors to prevent "fake" parts, then I'm all for it.
I've witnesses first hand "Error 53." My cousin replaced his screen using a third party service. His home button worked but the Touch ID did not. When he updated his iPhone to iOS 9, he was displayed a "Connect to iTunes" screen which resulted in iTunes displaying "Error 53."
We took it to Apple and they said they would not be able to repair it, and instead they would need to replace the phone paying the replacement fee. They said the Warranty on the phone has been voided and repairs could not be made because the iPhone was opened by a third party. I ended up paying for a replacement phone for him.
Last edited:
Not to mention that 'authorized parts' aren't available for a very long time, and could be unavailable very soon after the item goes off the market. These people are literally arguing for hardware rentals.
Not everywhere. http://www.apple.com/uk/legal/statutory-warranty/
Under consumer laws in the UK, consumers are entitled to a free of charge repair or replacement, discount or refund by the seller, of defective goods or goods which do not conform with the contract of sale. For goods purchased in England or Wales, these rights expire six years from delivery of the goods and for goods purchased in Scotland, these rights expire five years from delivery of the goods.
I have already corrected you in a different thread, so I'm really surprised you haven't taken in that information, as it comes directly from Apple.
For the love of God, read https://www.apple.com/business/docs/iOS_Security_Guide.pdf
You are spreading misinformation.
The secure enclave does FAR MORE than authenticate fingerprints.
Some quotes:
"ACLs are evaluated inside the Secure Enclave and are
released to the kernel only if their specified constraints are met."
"When a file is opened, its metadata is decrypted with the file system key, revealing
the wrapped per-file key and a notation on which class protects it. The per-file key
is unwrapped with the class key, then supplied to the hardware AES engine, which
decrypts the file as it is read from flash memory. All wrapped file key handling occurs
in the Secure Enclave; the file key is never directly exposed to the application processor.
At boot, the Secure Enclave negotiates an ephemeral key with the AES engine. When
the Secure Enclave unwraps a file’s keys, they are rewrapped with the ephemeral key
and sent back to the application processor."
"To further discourage brute-force passcode attacks, there are escalating time delays after
the entry of an invalid passcode at the Lock screen. If Settings > Touch ID & Passcode >
Erase Data is turned on, the device will automatically wipe after 10 consecutive incorrect
attempts to enter the passcode. This setting is also available as an administrative policy
through mobile device management (MDM) and Exchange ActiveSync, and can be set
to a lower threshold. On devices with an A7 or later A-series processor, the delays are enforced by the
Secure Enclave. If the device is restarted during a timed delay, the delay is still
enforced, with the timer starting over for the current period."
"The One-time Unlock Token for attended software updates expires after 20 minutes.
This token is exported from the Secure Enclave and is written to effaceable storage. A
policy timer increments the counter if the device has not rebooted within 20 minutes."
So, from these examples, the secure enclave handles ACL enforcement, disk encryption, password enforcement, even with TouchID disabled, and software updates.
A compromised Secure Enclave compromises the entire phone.
Please inform yourself.
Last edited:
A perfect example for epidemic Stockholm syndrome of "extreme Brand Loyalists"…
have a look:
https://en.wikipedia.org/wiki/Stockholm_syndrome
...
Heh. I bet they would feel even more safe if Tim Cook kept them in a cage and watched over them so they didn't do something stupid with their iPhones