I understand the point.
And the hardware is welcome to stop trusting that sensor if it detects a possible problem.
However, it is not necessary to brick the entire phone.
Last edited:
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
I understand the point.
And the hardware is welcome to stop trusting that sensor if it detects a possible problem.
However, it is not necessary to brick the entire phone.
There have been no reports and all documentation (person reports, law offices, reporting agencies, and Apple) has only mention 6 and 6S. There has been no mention of any other affected models. If you know different, kindly put forth that info.
Once again you roll out that specific Apple statement like it is the end all of knowledge. It isn't and right now this is only surmised as being part of the Error 53 issue. Apple is the only one who can show or prove it and they are not saying, only alluding. Very careful wording.
[doublepost=1455739125][/doublepost]
Especially when the said function is strictly an optional use item put in place to allow users to minimize passcode entry.
Last edited:
Apple's statement regarding Error 53:
If your iOS device has Touch ID, iOS checks that the Touch ID sensor matches your device’s other components during an update or restore. This check keeps your device and the iOS features related to Touch ID secure. When iOS finds an unidentified or unexpected Touch ID module, the check fails. For example, an unauthorized or faulty screen replacement could cause the check to fail.”
Like I said, tied to TouchID and the secure pairing. Seems like it checks more than just a match between the CPU and the sensor.
If its going over board of bricking a phone after non-Apple store has done the work and iOS update, what's to stop the same repairer also modifying how the re-validation works (it we assume it's in the phone in the first place).
Apple should have not bricked it, but still allowed DPU mode.. this way, while the re-validation doesn't have to be in hardware (to prevent it from being overridden by third party), the fact u can just use DPU mode, and IOS update would introduce/re-validate it.
My point is, why must it be in hardware ? Can't be be in software as long as Apple controls it ..
The same reason why a restore takes you back after a JB IOS device.
Yes. Sorry for the delay. Was out of town. I paid the "out of warranty" fee: USD $299
Common sense prevails, at last:
http://techcrunch.com/2016/02/18/ap...-ios-to-restore-iphones-disabled-by-error-53/
http://techcrunch.com/2016/02/18/ap...-ios-to-restore-iphones-disabled-by-error-53/
Or basically a bug/issue that was discovered in relation to it all and got fixed.
All the people cheering on Apple for disabling are gonna be pissed
<kicks tumbleweed out of the way to type>
Probably on to yet another sword to fall on.
Mike
Replying because this absurdity is the top comment
Hahahaha, ridiculous, can you even imagine how stupid this makes you look? Do you know what Error 53 does? It destroys the data on your phone. All of it. Yep. All of it.
So, because you fixed your phone at someone other than Apple because Apple, quite seriously, loves screwing over their customers at a frightening level. Don't think that I hate Apple or something. I don't hate. I can't comprehend how someone could hold such an emotion. Just because of that Apple has the right to release an update that completely ****s over the users data?
Apple does not own a device they already sold. Learn some law. Stop embarrassing yourself.
Of course, you might have been sarcastic and I made a fool of myself instead.
Hahahaha, ridiculous, can you even imagine how stupid this makes you look? Do you know what Error 53 does? It destroys the data on your phone. All of it. Yep. All of it.
So, because you fixed your phone at someone other than Apple because Apple, quite seriously, loves screwing over their customers at a frightening level. Don't think that I hate Apple or something. I don't hate. I can't comprehend how someone could hold such an emotion. Just because of that Apple has the right to release an update that completely ****s over the users data?
Apple does not own a device they already sold. Learn some law. Stop embarrassing yourself.
Of course, you might have been sarcastic and I made a fool of myself instead.
You should always keep a backup of your data in the event that something happens to your device. This is not Apple related, this is common sense. You can't send your device in for repair and expect nothing to happen. Apple doesn't guarantee your data when you bring your device to them either. It's up to you to take the responsibility to back up your data ... because ... things do happen.
1. Backup your data for repairs
2. Apple shouldn't purposely wipe your data
These events are not mutually exclusive. Yes you should backup your device before you take it in for repairs. And yes you should expect that Apple won't purposely wipe and brick your device.
However, your post doesn't address the fact that after this Error 53 event doesn't just wipe your data, which you correctly point out should've been backed-up in the first place, but it also bricks the device. You can no longer use it.
It's one thing to take your phone in for repairs and it gets wiped. At least you still have a phone that works. It's completely another to not only have lost all your data, but your device is also no longer usable.
Yes, we all know what it does. That doesn't take away from what I said. You should back up your data as often as necessary, not just when taking it in for repairs. You should have a back up before something happens. That's the point of having a back up.
Again, that has nothing to do with what I said. We are all aware of what this error did.
A bit late to this conversation, eh?
However, you have to understand getting your electronic device, whatever the brand, 'repaired' by an unauthorized 3. party has never been a great plan. Every kid with a screwdriver and iFixIt can hang a shingle and claim to know what they're doing but this incident nicely illustrates how this goes wrong.
There were times when devices or things had user or service-replaceable parts, like your TVs vacuum tubes, the graphics card in your beige PC or the alternator in your car, but these days if your Xbox breaks you have two options, official repair or replacement.
Apparently this has occured due to some repairs being performed by apple authorized repair centres as well on or off warranty. I can understand the phone itself and the finger print reader being matched at a hardware level. However when a part is installed it is up to apple to advise the user / technician that a process is needed to update the hardware record so the 2 parts can work correctly. This seems to be what was missed on Apple's part. Look at it this way. You have an apple computer (laptop desktop whatever) you want to upgrade from the 4 GB of ram and the standard video card to new hardware (high performance ram and a better video card). Though the hardware in particular video card is not OEM and supported by Apple does it seem right that after an operating system update because that video card / RAM is not the original that absolves apple of any responsibility? The Windows 10 did this right by checking the hardware in the computer before allowing the update and communicating to the various hardware manufacturers regarding compatibility. Seems to me Apple missed this hardware checking step prior to allowing an upgrade on their own equipment / software. Apparently thinking that no one can fix their stuff but them.
First, I haven't read a single article verifying a claim that this happened at authorized repair centers. Second, this is not a graphics card or RAM. The touch ID sensor has no published specification, cannot be considered anything other than a proprietary part, connected to a proprietary connector, performing an internal and proprietary security task. Nothing about the iPhone's internals is considered or advertised as upgradable or user repairable. It is perfectly reasonable that when you start changing parts inside your phone, you're very much out-of-warranty.
Furthermore, you wouldn't expect to upgrade or repair your big flat-screen TV, Xbox, or PS4. It isn't even 100% reasonable that your can personally install or repair your washer or dishwasher, depending on country and insurance stipulations. So, yes, there was a time when people could 'build' a computer or fix your car. Those times have largely passed, and the world is better off for it.
Last edited:
I hear what you're trying to say, but a part working for a time and then failing due to incorrect installation, regardless of the cause, was never installed correctly. You can say it was a deliberate attempt by Apple to disable 3. party components although plenty of other gray market installed components work, it was clear to me they really never considered this possibility and the invalid pairing was triggered with a software update. The is 100% the fault of the service provider offering services they were not qualified to provide.
The automotive analogy is TERRIBLE. First, I completely disagree that people should be allowed to modify their car to perform outside the specs of the EPA certified ones. Second, the analogy is terrible because cars are historically analog devices.
Being able to replace whole systems that are bolt on, like a water pump, is very different than say repairing the cars computer. Still, the car analogy, as bad as it is, is changing. Cars today are much less serviceable today than the past and only going to become more so as we transition to non-ICE alternatives.Your coffee maker... A subsidized coffee maker financed by the sale of pods (environmental disaster) is clearly a choice that is unappealing to some, in the same way an Xbox or Playstation (subsidized devices) using cryptographic lock-in is also unappealing. I own a Delonghi bean-to-cup espresso machine ($5000 starting cost but I've owned it now for 7 years and had it repaired once), because I cannot stand the thought of buying pods or what have you from vendor X and disposing or 'recycling' of it. I want to choose the beans and throw out only compostable grounds. There are choices for people that want choice, they should apply that mindset to purchasing electronics, although it will basically mean they'll have high-maintenance electronics (read Linux).
The reason - if you wanted to allow user repair you should have avoided a world of miniturization. SoC designs are your mortal enemy. Software bundled with hardware should tell you, no, we don't want you futzing around and we didn't plan on it. I write software and work with SoC hardware professionally. It is difficult to write good software and I promise you that while we attempt to write completely robust software, nobody has ever suggested I should account for the possibility that someone has replaced a component incorrectly, with a faulty component, or fake component. Well, not entirely true, but not in a direct, first priority way. I'll tell you, in my business, I can't imagine someone thinking that was a good idea, but you know, some guy trying to save a buck might just do it and complain subsequently that we were trying to lock him out and we're just trying to make the thing work without bugs.
Last edited:
Seems like all of this has been rehashed many times over 20 pages of this thread...not sure there was a need to bring up the same thing yet again given that all of it is already here in the thread many times over.
Looks like the lawsuit was dismissed: https://www.macrumors.com/2016/06/21/apple-error-53-lawsuit-dismissed/
And Apple's muscle power wins.Hopefully the declining sales teaches them a thing or two