Haha no they won't lol....
-Mike
Unless you put DDR4 inside and it blows up... Whelp I guess Apple kinda bricked your device.
Haha no they won't lol....
-Mike
You seem to be getting lost trying to get to where the car analogy makes sense. Bringing up leases just takes us further away from the analogy even trying to make sense.Well, seems like the why might be material--not because you use OEM parts, no, but if there is some sort of an issue with those parts that rises to some sort of safety level perhaps, then there might be additional avenues that the manufacturer has. (That's not even factoring in leased or financed vehicles and additional conditions that might be in play there in relation to ownership and all that.)
Or something along the lines of what's mentioned below:And they can certainly tell you there's a new update to the software in the car to patch some security issues--perhaps even attached to a recall of some sort--which pretty much anyone will agree to do.
Do we know how many people have encountered this error?
Jyby. What story are you talking about? Reverse engineered part? Not cool just making up stuff. You're wrong about the car too.If a company designs a part that is proprietary... And you install a reverse engineered part... And it bricks your device is it the companies fault or your own??
I say it's your fault...
Also cars have proprietary parts, the computer for one thing... You have to buy the manufacturers computer otherwise you'll have big trouble and then ItS YOUR FAULT...
Cars don't work without computer fyi
some of you are so desiolusial about apple, there is not hardware damage, is not like some of you are saying: If I buy a car. And change the immobilizer to an aftermarket one. And the car stops working. The car company isn't liable" that is something really different sir, the iphones are bricked because of the software, there was no hardware damage caused by the unofficial pieces,the damage was intentionally made by apple with the software, i can't believe yall can be so blind about it, it's amazing how some of you defend everything apple does, this is ********, i still love apple tho.
Jyby. What story are you talking about? Reverse engineered part? Not cool just making up stuff. You're wrong about the car too.
What I was saying is that when you are at the dealership and they are performing a service and they tell you that a software update has been issued to address some security and other issues and you agreed to install it, then something unexpected can potentially result if there is some part that is present that is identified as not being compatible for some reason. Of course not just any reasoning would apply, and of course what it is that ends up happening because of it is another thing to address, but those aren't the parts I was addressing, which is basically the flow of things leading up to it as can potentially happen.You seem to be getting lost trying to get to where the car analogy makes sense. Bringing up leases just takes us further away from the analogy even trying to make sense.
For the sake of clarity, can we just go with phone ownership and car ownership. No matter what we go with the analogy will fall apart. The manufacturer can't make you do anything, even on a lease. Even if it rises to the level of safety, the manufacturer cannot compel you to do anything. They can issue a recall, which as a consumer, you can choose to ignore. Discussing recalls and reasons takes us even further from the analogy making sense. Suffice it to say, there's no way to make it work. Besides, the fact that outside of Tesla, manufacturers don't sell cars, really makes this an exercise in futility.
Apple's got a problem. They should have handled this differently. The phones are not theirs to brick. Disable Touch ID and give a notification for the reason. There would be no issue right now.
Please, please, please read up on the issue. You are making up way too much stuff, and apologies, but seem to understand even less about the Error-53 issue. It's not about an oem part. Error-53 can be triggered by switching home buttons between iPhones. Please also stop with the car analogies. OEM parts are not required on cars, least of all starters. You can walk into any auto parts store and buy any number of starters made by companies other than Ford or Chevy.The software does its job, detecting potentionally dangerous components and shutting them down. The TouchIDs being installed are not the same TouchIDs Apple designed... So basically it's like installing a Ford starter in a Chevy... It might work but who knows...
Why would you installed a part that someone fabricated anyway? Yeah it's cheaper but do you trust it?
Do these customers even know what they are doing? Do these authorized guys even know what they are doing? Probably not... Not Apples fault.
You're wrong because that's not what happened in the Error-53 issue so the analogy is flawed from "How" to the ellipsis.So you're saying he TouchIDs are OEM? Straight off the Apple floor?
How am I wrong about the car? If you install something into your vehicle and you break it its your fault not the companies...
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.
Doesn't everything you wrote take us further from the car analogy being relevant to the topic of Error-53? None of those circumstances are comparable.What I was saying is that when you are at the dealership and they are performing a service and they tell you that a software update has been issued to address some security and other issues and you agreed to install it, then something unexpected can potentially result if there is some part that is present that is identified as not being compatible for some reason. Of course not just any reasoning would apply, and of course what it is that ends up happening because of it is another thing to address, but those aren't the parts I was addressing, which is basically the flow of things leading up to it as can potentially happen.
You're right, this is the time that you go to Apple and say, sync my damn sensor and flash the phone so I can use it again.People are sue crazy. Sheesh... I'm all for suing when warranted but this isn't the time.
I believe the guy who tried to get his iphone repaired passed his warranty time. Ethic wise, it's wrong to brick someone's phone just because this person needed to get his phone fix.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?
Seems fairly analogous--as in similar in concept, not similar in specifics/details: a replacement of an integral part of the car, a software update, an important incompatibility between what is addressed in the update and the replacement part, and some sort of a resulting consequence. Now, again, the importance and details of the incompatibility can certainly be questioned, just as the resulting consequence.Doesn't everything you wrote take us further from the car analogy being relevant to the topic of Error-53? None of those circumstances are comparable.
But to answer your dealership hypothetical. Dealerships have to warranty their work (this is separate from the warranty on your car). If you bring them a running car, they have to return a running car. 1. They can refuse to work on your car if there are aftermarket parts on it. 2. They can agree to work on your car with aftermarket parts but not have the work covered under your warranty. 3. They can cover it all under the warranty. They cannot force any work to be done.
Yeah but this bit on security and modifications nails it in the coffin... Case closed guys... The law firm that filed this suit didn't even read this document..
"4 Security; Lost or Disabled Devices
Apple Pay stores virtual representations of your Supported Payment Cards and should be protected as you would protect your physical credit and debit cards. Providing your device passcode to a third party or allowing a third party to add their fingerprint to use Touch ID may result in their ability to make payments and receive or redeem rewards using Apple Pay on your device. You are solely responsible for maintaining the security of your device and of your passcode. You agree that Apple does not have any responsibility if you lose or share access to your device. You agree that Apple does not have any responsibility if you make unauthorized modifications to iOS (such as by way of a “jailbreak”). "
Apple isn't responsible for anything you do to your phone...
If the programming of that key is also used to authenticate you to the car, let's say to start it, then you'd seemingly have issues with that too.Actually I think, and someone tell me if I'm off, I think I have a good car analogy:
Programmable car remote key: the remote is convenient but not required to access your car, since you can still use the physical key to open a door.
Touch-ID: touch-id is convenient but not required to access your phone, since you can still use the pin code to access it.
So if you try to get a car remote key via 3rd party and for whatever reason the pairing/programming doesn't work (it's actually happened to my brother), you'd still be able to access your car.
This makes sense since a 'convenient' access feature such as a remote shouldn't brick your car.
Similarly, Apple should still let you use your phone, you'd just not be able to access it via touch-id.