ajs42548 wrote:
First of all my car analogy is a perfect one. One system has nothing to do with the other.
Secondly, the ID system was not affected by the 3rd party repair. The fact that others had the same Error 53 whenever a 3rd party repair was done to their phone and later exactly after the update happened, shows that it was the update that caused it. If 100 people have a 3rd party repair and all of the phones worked perfectly as before but then get an Error 53 exactly after the upgrade, then guess what, it was the upgrade that was responsible. As a technician you should know that.
If you use a product in a manner that is not intended, then the manufacturer isn't liable. Explain to me how you can use tires in an intended manner that can have an adverse effect on an engine. Answer: there's not.
The Touch ID system was INDIRECTLY affected by the third-party screen replacement, because the Touch ID is indirectly connected. The phone is looking for a proper pairing between the two systems. Because the repair was not done in the correct manner, that pairing fails to work. When the iOS checks for this pairing and it is wrong, then the error occurs.
Starting Point: Device has proper components and proper pairing. Any authentication (such as an iOS update or iTunes restore installing the same iOS version) sees the proper pairing, so the device operates properly.
First Change: One component is replaced improperly. The pairing is no longer proper. No authentication is made at that time. (Side note & personal opinion: There should be more regular checks of proper pairing in the device. If there were, then this error would occur much closer to the point of first change and be more obviously linked to the component change to the average user.) But the device still appears to operate normally.
Second Change: The iOS of the device is updated or reinstalled. At that time, a new authentication request was created. The pairing is not proper, back from First Change, and so the error takes effect.
The iOS update was a catalyst, not a cause.
Starting Point: Automobile driver has a valid drivers license. Any inspection of that license, such as being pulled over by a police officer, results in a positive check, and therefore there is no problem.
First Change: The driver's license expires on January 1, 2016. The license is no longer valid. No inspection is made at that time, because the driver doesn't encounter any situation in which it needs to be inspected. (Side note & personal opinion: There should be a system that update's police officer's vehicle computers to have a database of license plates associated with owners with expired licenses, and an officer should be able to pull over any vehicle that match, so they can inspect the driver's license.) But the driver can still operate the vehicle normally.
Second Change: The driver is pulled over for a minor traffic violation. At that time, the police officer inspects the license. It is not a valid license, back from the First Change, and so the police officer issues a ticket.
The police officer did not create the expired license. He did not decide to make the license invalid. He simply enforced the protocol. He is not the cause of the ticket. He is simply the catalyst.
I understand it's a difficult distinction for some people, especially when people get emotional and refuse to use logic. But the update doesn't cause the error. The update is simply the catalyst that forced the system to check for proper pairing (or authentication), and when that pairing is invalid, the error occurs.
A rock drops on a glass table and cracks it. Gravity is the reason the rock moved toward the glass table. But gravity did not cause the damage. The rock did. The iOS update is the reason that the authentication check occurs. But it is the improper pairing, that was present since the unauthorized service, that caused the error.
This is a hardware issue, not a software issue.
