Your original statement was hyperbole without any substance to this. No one is debating that error - 53 exists, the debate is if apple is justified in protecting it's ecosystem. My opinion is yes yours was hyperbole.So is yours. Only an opinion of one person on a biased rumors website, compared to hundreds of thousands of users on twitter whose devices Apple have bricked.
Apple has zero responsibility to allow or consider non- Apple parts being put into their product.
While I understand the vitriol against Apple for this error, it makes sense from a security standpoint.
Are you guys actually listening to yourselves? You are literally justifying Apple's actions in that they should be allowed to DESTROY someone's phone if they get it repaired at a 3rd party repair shop and then upgrade to the latest OS.
What the wut???
That's really F'd up guys. I mean, people refer to us as mindless sheep for this very reason. Come on.
First off, I'm not buying this excuse from Apple in the first place. No way they would brick someone's phone for getting it repaired at a non-Apple Store repair shop. If they are doing this on purpose, this should be reason enough for people to walk away...no, run away from Apple because this is pretty much illegal. I wouldn't want to be on the **** end of that stick.
But this has to be something that that was brought to their attention as a bug and their solution was to turn it into a feature and say customers are SOL (typical). And you guys are buying into it hook line and sinker. Sheesh.
Second, if Apple did do this on purpose, all Apple had to do was maybe disable the phone if it detects parts that are not "Apple made", or give you periodic notifications that you can't disable, and then remove them once the correct parts are installed. They don't have to brick the damn thing and make someone buy a new phone because of it. But, with that said, that's still horribly shady and majorly douchey, but at least they aren't destroying your ***** phone.
It's absolutely no different than the SS coming into your home in 1940's Germany and burning it down because you didn't have an approved "official" photo of Da Fuhrer on display. Well, same concept anyway.
If I want to get MY iPhone 6 repaired at a 3rd party shop, I should be able to do so at MY OWN RISK, without worry of Apple's iron fist coming down and smashing my phone from the heavens (or from hell, pick your poison). Apple has no right to tell me where I have to get my phone fixed and what brand parts I have to put in it. They are within their rights to void the warranty if the phone is still under warranty, I get that, but they can't be bricking people's phones over it. That is insane!
If I live 500 miles away from an Apple Store or an authorized repair center (if those even exist), then what? I have to ship it off and wait weeks to get it back? Or I have to drive 500 miles to get it fixed? That's just stupid if I have a phone repair shop in my town.
That 1984 ad that Apple is sooooo proud of, in no way shape or form represents the Apple of today. Talk about role reversal. Wow.
I don't believe Apple for a second in this. Surely this is a bug that they are trying to turn into a feature. If not, then this is reason enough to run away from Apple and never come back. We'll see if anything comes of this.
Aside from the fact that Apple's EULA clearly states that they do have the right to brick your phone for using third party parts,
the button on the iPhone 6 is an integral part of the highly sophisticated security system of the phone. Placing a third party button on the phone compromises the relationship between the user's fingerprint, the OS and the secure enclave on the phone.
If Apple were to allow the use of the third party button and have compromised phones walking around they could conceivably be liable for identity theft, etc. At best they risk having a tarnished reputation.
Now, having said that Apple should offer to repair this person's phone (at his expense) by replacing the third party button with an Apple approved one.
Aside from the fact that Apple's EULA clearly states that they do have the right to brick your phone for using third party parts
The moral is, always take your device to an authorized repair center so if you have a heart condition, DVT or think you might be pregnant you can be assured of placing an emergency call. As unauthorized repairs can jeopardize your ability to use your device, when needed.Moral: If you have a heart condition, a history of DVT, or are or think you might be pregnant, don't let unauthorized people repair your iPhone.
If you think you may ever need to place an emergency call do NOT buy iPhone.
The moral is, always buy from a manufacturer which doesn't milk it's customers by making them use their own repair services or bricking if they don't.The moral is, always take your device to an authorized repair center so if you have a heart condition, DVT or think you might be pregnant you can be assured of placing an emergency call. As unauthorized repairs can jeopardize your ability to use your device, when needed.
Does not
Then it should be checked every time, not just during an OS update.
It's a required legal risk in the USA, and I believe there's something similar in the EU.
People with brains do not blame their car maker for the failure of a third party brake shoe or battery.
However, they would rightfully blame the car manufacturer if it deliberately built a car to crash simply because you used non-OEM parts.
This Warranty does not apply: ...(e) to damage caused by operating the Apple Product outside Apple’s published guidelines; (f) to damage caused by service (including upgrades and expansions) performed
Home button is core functionality. It's core how you use and navigate . Your using optional features to tailor your user journey.
The moral is, always take your device to an authorized repair center so if you have a heart condition, DVT or think you might be pregnant you can be assured of placing an emergency call. As unauthorized repairs can jeopardize your ability to use your device, when needed.
That would be illegal in the USA.Wow. So now Apple is Nazis? What a ridiculous diatribe.
Aside from the fact that Apple's EULA clearly states that they do have the right to brick your phone for using third party parts,
Security updates are always forward. When a security risk is found it's the next update that gets the fix. Based on the information known at this point, you can't conclude it's a money grab any more than a security update. I guess the world will have to see how this plays out.The do NOT buy iPhone was mine. I tried to quote someone else and the multiple quote did not work out well. Te person I was quoting had the DVT, heart condition etc.
Bottom line. This is a money grab. Apple (Cook) is greedy. Innovation is dead. Changing the size of a device is all they seem to have. I have not seen a watch in the wild so until I do [or Cook reveals reveals figures] I will continue to consider it a flop.
If Apple seriously considered this a grave security risk the phone would not function immediately after third party repair. Waiting for an iOS update is worthless from a security standpoint. If the phone was in the wrong hands the miscreant would simply not update.
Exactly. I don't see why Apple hasn't been called out on this before. The more I read about Apple over the last few years the less I want to have anything to do with them.That would be illegal in the USA.
http://images.apple.com/legal/sla/docs/iOS91.pdfThat would be illegal in the USA.
Sure you can do that also. Whatever works for you and makes you happy.The moral is, always buy from a manufacturer which doesn't milk it's customers by making them use their own repair services or bricking if they don't.
Um...wow. Wrong.
If you take the most recent version of iOS and Android, both are pretty secure. There isn't much of a difference, so long as people update their apps and OS in a timely manner.
If you have a cheaper Android phone running a 4 year old OS, well, yeah...security might be an issue if you install apps that aren't trustworthy...but that goes for any operating system on any platform. Old, unsecured software can cause problems on any device.
With Android (like anything else)...keep your apps updated and don't install apps from shady .ru sites (you can't by default, you have to enable this ability to bypass that security feature)...and don't user "password" as your password (did some of you *gasp* because I just posted your password?) if you practice that, you'll be 100% fine.
So in short, don't be stupid.
The moral is, always buy from a manufacturer which doesn't milk it's customers by making them use their own repair services or bricking if they don't.
Security updates are always forward. When a security risk is found it's the next update that gets the fix. Based on the information known at this point, you can't conclude it's a money grab any more than a security update. I guess the world will have to see how this plays out.
Does too
This Warranty does not apply: ...(e) to damage caused by operating the Apple Product outside Apple’s published guidelines; (f) to damage caused by service (including upgrades and expansions) performed by anyone who is not a representative of Apple or an Apple Authorized Service Provider (“AASP”); (g) to an Apple Product that has been modified to alter functionality or capability without the written permission of Apple...
I, nor you have any idea what proprietary interaction goes on in between the home button/fingerprint sensor and the secure enclave that may be (probably likely) at risk of compromise by using a third party home button. If you look at the situation with a bit of pragmatism, instead of the "Apple is Evil and Wants to Squeeze Every Last Dime From Us" mentality it makes little sense for them to go through the trouble to make this happen unless there is a real risk to them. Fact is that a scant few of their customers are going to run into this issue, and the loss of revenue for them to allow third party buttons is relative pennies to their bottom line.
Agreed. But since we don't know all of the facts we don't know whether this was just a byproduct of the fact that this was a security "fix" instituted in iOS9 that was not included in earlier iOS versions.