ajs42548 wrote:
I'm having a difficult time understanding why you can't understand that this problem only occurs after an upgrade. I'll repeat this again... When there is a common problem occurring after an event (in this case an upgrade), then the problem was caused by that event, in this case the upgrade. Any and all technicians will tell you to go back to the way the device was before the event, whether it's a hardware or software reversal. If the upgrade never happened then the phones would still be working perfectly. One second before the upgrade = working phone...One second after the upgrade = bricked phone. Diagnosis = upgrade caused the problem. There can be no other conclusion.
It does not only occur after an upgrade. If you were running iOS 9.2.1, then had unauthorized service performed, then had to restore via iTunes at any point (reinstalling a fresh, yet identical copy of iOS 9.2.1) then the issue can (and has been reported to) occur.
Once you have had unauthorized service performed on the device, there are absolutely no guarantees from Apple regarding current or future performance. And the terms f the iOS update agreement make it clear than that you, as the user, take sole responsibility for the quality & performance of the iOS on your device.
Updating is never mandatory. You could have an iPhone 4S still running iOS 5.1.1 if you wanted.
Your comment about how you have determined that it must have been the upgrade that caused the issue reminds me of the iPhone 4S greyed out wi-fi issue. So many people were convinced it was the software update that caused it. Whether it was from 5 to6, or from 6 to 7, or even from 7 to 8, people still insisted that because it happened immediately after the update, that the software of the update caused the problem,
Wrong. The issue was that those affected iPhone 4 S units had a faulty wi-fi chip that had a lower than standard heat tolerance. The heat generated by the processor during the software update exceeded the chip's tolerance, and it stopped working. It wasn't the 1s or 0s of the software; it was the heat generated by the processor. And the chip was defective.
Here, we have a 'faulty' Touch ID, and then there is a problem after the update. Stating that there can be only one possibility is extremely poor troubleshooting, and I'd write up or possible terminate any of my employees that used such erroneous logic (if they kept doing it of course).
If you don't understand in detail how the hardware interacts with the software, then your analysis of the situation is no more valid than medieval 'scientists' that believed that draining blood was a valid way to treat a fever.