Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There is no bug in the software. It worked exactly as it intended. Apple introduced this error 53 because it wants customers who have faulty home buttons to buy new iPhones or charge them exorbitantly for the home button replacements instead of going to independent phone repair technicians. This is how Apple makes its money- by selling new hardwares.

Those people who went to the 3rd party repair shops were happy to lose the TouchID function after the home button replacement, and their phones were working fine before the update. Therefore the bricking is a conscious attempt, not an accident. Why else are those affected solely people whom had their home buttons replaced by 3rd party repair shops?

This is Apple's way of showing the middle finger to independent repair shops because as long as customers can repair their iPhones cheaply, who else's gonna buy their sparkling new iPhones? It makes sense as a business, but not from a consumer's perspective.
 
There is no bug in the software. It worked exactly as it intended. Apple introduced this error 53 because it wants customers who have faulty home buttons to buy new iPhones or charge them exorbitantly for the home button replacements instead of going to independent phone repair technicians. This is how Apple makes its money- by selling new hardwares.

Those people who went to the 3rd party repair shops were happy to lose the TouchID function after the home button replacement, and their phones were working fine before the update. Therefore the bricking is a conscious attempt, not an accident. Why else are those affected solely people whom had their home buttons replaced by 3rd party repair shops?

This is Apple's way of showing the middle finger to independent repair shops because as long as customers can repair their iPhones cheaply, who else's gonna buy their sparkling new iPhones? It makes sense as a business, but not from a consumer's perspective.
Yup, that's why Apple addressed the issue. It all makes sense.
 
  • Like
Reactions: NicolasLGA
Well not really. I can write an app that is completed free of bugs. The chance of bugs being introduced as the app gets larger does increase. However we are not just talking about a simple little bug here we are talking about a complete catastrophic failure of an OS rendering a device completely failed.
This is not true. There will never be a case where the software is 100% stable. It is fundamentally impossible. There are numerous factor before, during, and after that can cause issues.
In addition to that, we are not talking about an bug here. We are talking about an security precaution that went over board. The OS did exactly what it was intended to do. Apple shouldn't have backed off and resolved this. The Home Button should not in anyway be tempered wth no matter what. Any of those replacements could've been used maliciously to gain personal information.
 
  • Like
Reactions: I7guy
This could've been all avoided if Apple just ensured that it's software release was suitable and fit for purpose. It clearly wasn't and now Apple is enduring the consequences of broken software pushed out to users. One would think that Apple would have learnt from this experience but clearly it hasn't with its most recent releases.

This is why I'm completely reluctant to install any new software from Apple.

Apple charges customers a premium as if it is industry perfection, but it clearly isn't through experience.

Pay compensation properly Apple and move on to your next big project. Customers are everything Apple, treat them properly, be completely proactive by helping customers.

Can you imagine if Apple pushed a software update that was buggy to one of its future automobiles? Something mission-critical like that with some software that bricks when driving. It could be catastrophic. That's why Apple needs to get this quality up to par and learn these lessons now.
[doublepost=1464156257][/doublepost]
It's the software that's rendering the products useless.


Just to clarify.

1. It's Apple's fault people took their device to some repair shop who used knockoff parts and didn't understand the complexities of Touch ID but replaced it anyway. That makes sense blame Apple.

2. Apple isn't proactive enough to somehow know what someone does to their device. I don't realistically see how anyone could expect Apple to know that. It would be foolish to think Apple or any company is going to post the refund process as their entire main page and every corner of their website. This issue effects such a small amount of users if they have a problem they literally just have to google it or call Apple.

3. A Touch ID sensor is absolutely nothing like car security. I would damn sure hope my car would not start if there was a security issue or a chance of something not working properly. Imagine if on a Tesla the boot process was like oh I see something is wrong and these numbers don't make sense to me. Ah **** it let them drive the car and turns out the breaks don't work. 10/10 times I would want my car not start than bypass critical elements and security checks.
 
Last edited by a moderator:
One of the worst things that America ever gave the UK was the idea of 'no win no fee lawyers'.
Lawyer in the UK is a term for anyone who has read a law book and fancies having a go. 'No win No fee' could have been great for those wronged on low income, it had the effect of just filling up the courts with Hawks and Chancers.

In the past one would have to been upset enough to visit a solicitor and commit to seeking justice.

All too often we see situations such as this where those who have been slighted demand money. Our society is definitely the poorer for it.
 
Just to clear some confusion. Changing the home button and fingerprint sensor will not bypass Apple's security. Apple had made sure of that via their OS. However that said, it shouldn't brick the phones either. Like I said earlier, those who had their home buttons and fingerprint sensors replaced fully knew what they were getting, that of TouchID not working after the repair. They can only use passcodes as their login method. That is all. Hence the idea of bypassing Apple's security measure strictly from using a third party home button and fingerprint sensor standpoint is never an issue. It just won't work that's all. But it won't render the iPhone useless either. So by consciously delivering a software update that bricks a phone without any warning to the consumers either via their changelog or even a prompt during the update, Apple is essentially sabotaging these users, whom may not have any other viable alternative of repairing their phones economically in the first place due to i.e., out-of-warranty issue, and no Apple Stores in close proximity to where they live.

So why fault these consumers where independent repair shops may be their sole logical and viable options? Bring your war directly to these repair shops instead, and not make the consumers as collateral damage whilst trying to bring across your agenda. Don't brick our phones when they were working perfectly fine a minute prior to the update, and completely useless after just because you detest the fact users have chosen to have their iPhones repaired by independent repair shops. Build more Apple Stores instead and lower your repair bills. That will absolutely get more people to service their phones with you.

Certainly there are better ways to treat your most loyal customers with more respect than biting the hands that feed you instead.

I have never had any problems with iPhone repairs with Apple. I am one of the lucky ones who has Apple authorized repair centers around where I live, and Apple's service has always been top-notch. No complaints with that. But I keep asking myself, WHAT IF, just what if my iPhone is out of warranty, and the nearest Apple Store or Apple Authorised repair center is 200 miles away from where I live, and there it is, just cross the street from where I am is a small independent repair shop that can solve my iPhone misery... What would I do?

What would you do?
 
Just to clarify.

1. It's Apple's fault people took their device to some repair shop who used knockoff parts and didn't understand the complexities of Touch ID but replaced it anyway. That makes sense blame Apple.

2. Apple isn't proactive enough to somehow know what someone does to their device. I don't realistically see how anyone could expect Apple to know that. It would be foolish to think Apple or any company is going to post the refund process as their entire main page and every corner of their website. This issue effects such a small amount of users if they have a problem they literally just have to google it or call Apple.

3. A Touch ID sensor is absolutely nothing like car security. I would damn sure hope my car would not start if there was a security issue or a chance of something not working properly. Imagine if on a Tesla the boot process was like oh I see something is wrong and these numbers don't make sense to me. Ah **** it let them drive the car and turns out the breaks don't work. 10/10 times I would want my car not start than bypass critical elements and security checks.
I didn't say any of those things. You have reinterpreted my comments and gone to the extreme.
Apple should have anticipated that a user might go to a third party for a repair. And on the occasion that there is an issue with that repair, provide a more thoughtful response in the system software.
If there's a problem with a product, the refund/return/exchange process should be as easy as the purchase process.
When Apple pushes buggy OS software, it knows exactly who has installed it using their Apple ID. Apple should recall the OS and get in contact with all affected users notifying them how they can get their devices corrected. That's good service and taking care of the customer, not leaving them to search for an answer.
If Apple can't get its act together with all the billions in cash provided from its customers, there's no helping Apple long term.
 
Last edited by a moderator:
I didn't say any of those things. You have reinterpreted my comments and gone to the extreme.
Apple should have anticipated that a user might go to a third party for a repair. And on the occasion that there is an issue with that repair, provide a more thoughtful response in the system software.
If there's a problem with a product, the refund/return/exchange process should be as easy as the purchase process.
When Apple pushes buggy OS software, it knows exactly who has installed it using their Apple ID. Apple should recall the OS and get in contact with all affected users notifying them how they can get their devices corrected. That's good service and taking care of the customer, not leaving them to search for an answer.
If Apple can't get its act together with all the billions in cash provided from its customers, there's no helping Apple long term.
Not everyone uses AppleID/iCloud. Not sure Apple connects that personally identifiable information with update installations either.
 
No, the iPhones fixed by third party should be bricked when parts are replaced with not approved ones. The best example is that case. By putting an inferior Touch ID sensor, the third party repair is lowering the security of the phone there opening a huge hole in security. It is mostly for security reason and I agree with a concept trying to protect my infos.
Phones were bricked by more than 3rd party parts. They were also bricked at Apple stores when stores didnt calibrate them correctly using Apple parts. It was a known issue internally.
[doublepost=1464223517][/doublepost]
Just to clarify.

1. It's Apple's fault people took their device to some repair shop who used knockoff parts and didn't understand the complexities of Touch ID but replaced it anyway. That makes sense blame Apple.

2. Apple isn't proactive enough to somehow know what someone does to their device. I don't realistically see how anyone could expect Apple to know that. It would be foolish to think Apple or any company is going to post the refund process as their entire main page and every corner of their website. This issue effects such a small amount of users if they have a problem they literally just have to google it or call Apple.

3. A Touch ID sensor is absolutely nothing like car security. I would damn sure hope my car would not start if there was a security issue or a chance of something not working properly. Imagine if on a Tesla the boot process was like oh I see something is wrong and these numbers don't make sense to me. Ah **** it let them drive the car and turns out the breaks don't work. 10/10 times I would want my car not start than bypass critical elements and security checks.
Phones were also bricked using Apple parts when getting in store repairs. Not just by 3rd party parts.
 
There is no bug in the software. It worked exactly as it intended. Apple introduced this error 53 because it wants customers who have faulty home buttons to buy new iPhones or charge them exorbitantly for the home button replacements instead of going to independent phone repair technicians. This is how Apple makes its money- by selling new hardwares.

Those people who went to the 3rd party repair shops were happy to lose the TouchID function after the home button replacement, and their phones were working fine before the update. Therefore the bricking is a conscious attempt, not an accident. Why else are those affected solely people whom had their home buttons replaced by 3rd party repair shops?

This is Apple's way of showing the middle finger to independent repair shops because as long as customers can repair their iPhones cheaply, who else's gonna buy their sparkling new iPhones? It makes sense as a business, but not from a consumer's perspective.

You are ridiculously quick to assign malicious intent to things. These phones getting locked was in no way malicious. Your logic is circular ("why else are those affected solely people whom had their home buttons replaced by 3rd party repair shops" - maybe because these are the very people who had modification improperly made on their phones? - it's not like the phone is consulting its GPS and saying, "ah, yes, the home button was just replaced, but I can tell I was at Joes Cheap Phone Repair and not an Apple Store" - if the modification had been perfect, the phone wouldn't have known any different - if a car repair shop replaced the wheels on your car and you didn't notice until later when you had to stop that the brakes didn't work, would you blame the car manufacturer, or the repair shop?).

Apple put in an error message for something they didn't expect would ever happen. That's why the error message wasn't particularly informative (as a software developer, I have written many error messages for situations that "can't possibly happen"). It affected people who had their hardware improperly modified, when the next update did a simple sanity check to ensure all the bits necessary to keep the phone secure were working as intended and it found that something was broken.

But I can see why Apple would have to work hard to kill off any possible factor keeping people from having to buy new phones - after all, sales plummeted to a mere 51 million iPhones last quarter (that's 390 iphones every minute of every hour of every day, all quarter long). Not sure how Apple can survive on so little money.

This is the kind of logic one comes up with when one starts with the conclusion/conviction that Apple is gleefully looking for people to run over in their quest for more profit, and then works backwards to find evidence supporting said conclusion. Smh. On a side note, what kind of tin foil do you find works best for your hats?
 
Last edited:
Like I said earlier, those who had their home buttons and fingerprint sensors replaced fully knew what they were getting, that of TouchID not working after the repair.

Ha ha, really? No. They absolutely did not know what they were getting. They GUESSED. They were wrong.

The repair shops are at fault here: they said, "yes, we can fix this for you, we know what we are doing." When what they meant was, "we THINK we can fix this for you, but we are guessing about how all this stuff works." In effect, they defrauded their customers, advertising a cure that turned out to be defective.

So by consciously delivering a software update that bricks a phone without any warning to the consumers either via their changelog or even a prompt during the update, Apple is essentially sabotaging these users, whom may not have any other viable alternative of repairing their phones economically in the first place due to i.e., out-of-warranty issue, and no Apple Stores in close proximity to where they live.

There was NEVER a bullet point on Apple's ToDo list that said, "if the user has replaced their home button, brick the phone." There was a series of checks added to the software to ensure every bit of the hardware that contributes to the security of the phone was working properly. The bullet point was more likely "write checks to test EVERYTHING related to the security of the user's data to ensure that all the parts are working properly." To a security-conscious engineer, a TouchID sensor that isn't reporting back properly is cause for considerable concern, but since it is highly unlikely to happen, they write a test, but it simply locks up if the test fails. They didn't anticipate the case of folks having their home buttons replaced improperly (that is, with ones that no longer had functional TouchID capability).

How much engineering effort do you suppose car companies put into making sure their car works properly under all driving conditions, even if the owner has intentionally removed one of the wheels? Even if the owner thinks doing so is okay, or they can't afford a fourth wheel, or there isn't a dealership nearby, or it worked okay for a little while. If a problem arises, is it the manufacturer's fault, because they failed to consider the case where someone decides to take off a wheel? Or the user's fault, for expecting 100% proper behavior from a device they've effectively damaged by modifying in a way the designer never intended?

So why fault these consumers where independent repair shops may be their sole logical and viable options? Bring your war directly to these repair shops instead, and not make the consumers as collateral damage whilst trying to bring across your agenda. Don't brick our phones when they were working perfectly fine a minute prior to the update, and completely useless after just because you detest the fact users have chosen to have their iPhones repaired by independent repair shops.

Where on earth do you get this idea that Apple detests independent repair shops? Did you hear that one bit Tim Cook as a child or something? What proof do you have of this supposed "agenda"? Apple is not out to hurt its customers. It wants them to be happy with Apple, so the next time they need a new phone or computer, they'll be a repeat customer (which gets Apple lots more money). I'm guessing Apple doesn't really care one way or another about independent repair shops - their day-to-day effect on Apple is vanishingly small. They do, however, care about security -- even the most cynical view would hold that they want to retain the selling point of having phones that even the government can't break into easily. They've been constantly working to improve security. They added checks for a whole slew of things that could harm the security of the phone. A non-functioning TouchID sensor on a phone that left the factory with a working TouchID sensor is, to the OS, clearly a sign of something wrong. The error message wasn't more elaborate because they never anticipated anyone seeing it. Turns out a whole bunch of people did. Should Apple apologize for this? Sure. Should they be punished in court? Absolutely not, given that we got here because folks had improper repairs done on their phones (to be clear, the repairs WERE NOT improper simply because they'd been done by a third party, the repairs were improper because they DID NOT WORK).

But I keep asking myself, WHAT IF, just what if my iPhone is out of warranty, and the nearest Apple Store or Apple Authorised repair center is 200 miles away from where I live, and there it is, just cross the street from where I am is a small independent repair shop that can solve my iPhone misery... What would I do?

What would you do?
If Apple didn't have service readily available to you, and you bought an iPhone, you made your mistake way back at purchase time, not when some repair loomed on the horizon. Availability of service and support is always something that one should consider before plunking down multiple hundreds of dollars on some device. Even if the device is really shiny and you really want it. Then again, seven seconds of googling brought me to this text on one of Apple's support pages:

"Send in for repair. Start a service request online or by calling Apple Support and we'll send a box right away to collect your iPhone. You can then arrange to ship it to an Apple Repair Center at your convenience. We'll deliver your iPhone back to you in approximately one week."​

Is this hypothetical place where you found yourself in iPhone misery also 200 miles away from the nearest post office?
 
Last edited:
There is no bug in the software. It worked exactly as it intended. Apple introduced this error 53 because it wants customers who have faulty home buttons to buy new iPhones or charge them exorbitantly for the home button replacements instead of going to independent phone repair technicians. This is how Apple makes its money- by selling new hardwares.

Those people who went to the 3rd party repair shops were happy to lose the TouchID function after the home button replacement, and their phones were working fine before the update. Therefore the bricking is a conscious attempt, not an accident. Why else are those affected solely people whom had their home buttons replaced by 3rd party repair shops?

This is Apple's way of showing the middle finger to independent repair shops because as long as customers can repair their iPhones cheaply, who else's gonna buy their sparkling new iPhones? It makes sense as a business, but not from a consumer's perspective.
And the more consumers opt to buy their phones outright and unlocked, the more Apple will drive a wedge between customers and third party vendors who will continue to undercut Apple at every turn. In the end, the consumer gets burned when Apple takes a stand to "protect its self interests" as in Error-53.
 
I didn't say any of those things. You have reinterpreted my comments and gone to the extreme.
Apple should have anticipated that a user might go to a third party for a repair. And on the occasion that there is an issue with that repair, provide a more thoughtful response in the system software.
If there's a problem with a product, the refund/return/exchange process should be as easy as the purchase process.
When Apple pushes buggy OS software, it knows exactly who has installed it using their Apple ID. Apple should recall the OS and get in contact with all affected users notifying them how they can get their devices corrected. That's good service and taking care of the customer, not leaving them to search for an answer.
If Apple can't get its act together with all the billions in cash provided from its customers, there's no helping Apple long term.

I think Apple did anticipate that customers would go to third parties (something it does not expressly forbid). Hence the Error 53. Designed to force them back to Apple for repairs. This has NOTHING to do with iphone security since I can turn off the touch id.

I will admit that this could have been a honest mistake by a developer putting in code that should not have been there but Apple ignored, the fought it pretty hard so I am more inclined to think this was a conscious design decision.
 
  • Like
Reactions: smacrumon
I think Apple did anticipate that customers would go to third parties (something it does not expressly forbid). Hence the Error 53. Designed to force them back to Apple for repairs. This has NOTHING to do with iphone security since I can turn off the touch id.

I will admit that this could have been a honest mistake by a developer putting in code that should not have been there but Apple ignored, the fought it pretty hard so I am more inclined to think this was a conscious design decision.
The error isn't the issue per se, it's what happened with that error in one of the updates where it was treated as unrecoverable basically, when it shouldn't have been, as Apple themselves pointed out and corrected.
 
The error isn't the issue per se, it's what happened with that error in one of the updates where it was treated as unrecoverable basically, when it shouldn't have been, as Apple themselves pointed out and corrected.

Are you kidding me? The error is absolutely the issue. Apple pointed nothing out. They fought the issue and fought the issue until a lawsuit forced them to change their tune.
 
Are you kidding me? The error is absolutely the issue. Apple pointed nothing out. They fought the issue and fought the issue until a lawsuit forced them to change their tune.
The error is the error, it just wasn't supposed to disable the whole device, which was confirmed, explained, and corrected by Apple.
 
The error is the error, it just wasn't supposed to disable the whole device, which was confirmed, explained, and corrected by Apple.

Except that Apple insisted that bricking the phone was intended. The lawsuit changed that. You have such an apple centric revisionist view.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.