Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I feel they should still be running this check on every boot, not just when updating.

Otherwise you might get a 3rd-party to replace the sensor, they don't re-pair the components properly, and then some months later when you update TouchID suddenly stops working.

It would be better if it failed on first boot after the update, telling you that you need to re-pair in order to continue using TouchID.
There is no way TouchID will work if the sensor is replaced by anyone other than Apple. Moved to a new display? That will work fine, but new sensor? Nope.
Someone could however have been using the replaced sensor as a standard home button and then when they upgraded iOS it could have been bricked. In other words, if TouchID is operating you will not get this error.
 
If you got your screen replaced at a third party then Apple has no obligation to fix your device if it got bricked. It's nice to see Apple come out and issue an update for those affected.
 
Guess i'm going to have to wait for iOS 9.2.2 to fix my 5s Touch ID which was disabled by the iOS 9.2.1.
 
If you got your screen replaced at a third party then Apple has no obligation to fix your device if it got bricked. It's nice to see Apple come out and issue an update for those affected.
If that was what actually happened, I would agree with you completely. Since the 3rd party repair didn't brick the device, Apple did. Apple admitted culpability for the bricking and is rightfully applying the fix. It wasn't a security feature. It shouldn't have bricked the phones. Those are Apple's words, not mine.
 
  • Like
Reactions: Avalontor
well well well, there are some forum members that look damn silly right now, who were advocating this was the right move, it was for our own good etc etc . Sorry guys, but you need to think for yourselves at times and not take what ever apples tells you gospel.

Worryingly, apple gave no evidence and you all were adamant it was a security issue. Looks like apple was testing the waters to go after authorised repairs and nothing to do with security, and they quickly realised the press smelt BS.

Your phones are just as secure without a working touched.
 
If it's possible to restore a bricked iPhone via a software update doesn't that mean the San Bernardino terrorist phone can be accessed through a special update? One that stays within the hands of Apple to avert the privacy concern. Can and should are to different issues.
Bricked vs locked are different.
 
Glad they are fixing the problem as best they can but it would have been nice for them to be more open about what was going on

You mean the problem they created for an issue that did not exist. ;)
 
Bad time for Apple to start making firmware that weakens security
How does this update weaken security? Apple clearly stated it wasn't a security feature and it never should have been customer facing: "We apologize for any inconvenience, this was designed to be a factory test and was not intended to affect customers. "
I'm assuming it's still used at the factory for validation.
 
  • Like
Reactions: modemthug and MH01
If it's possible to restore a bricked iPhone via a software update doesn't that mean the San Bernardino terrorist phone can be accessed through a special update? One that stays within the hands of Apple to avert the privacy concern. Can and should are to different issues.

The San Bernadino phone can be restored, yes. It doesn't need a special software to restore it, just hook it up to a computer running iTunes, put it in DFU mode, and it would restore. But that would delete all info currently stored on the phone. The FBI doesn't want to use the iPhone, they want the information on it.

All bricked iPhones being restored by the newly released iOS update are having their memory wiped. Hopefully the user has a backup they can reload. If not, they'll be setting up their iPhone from scratch.
 
  • Like
Reactions: ActionJacksonHern
I'm not on either side of the "Apple's right" or "wrong" argument, but logically, this doesn't support your arguments (although admitting public pressure had a role is leaving a "backdoor").

Claiming negligence is just a superior position to be in during a legal proceeding, as being found intentionally damaging often results in greater punitive action.

It could just be a case of the legal team finally getting back to the PR team and saying, "Walk it back."
Of course it's a PR response. I never claimed it was anything but. It was a damn quick turnaround though. I don't know that I've seen one quite this fast, leading me to believe that the "brick" wasn't ever really the intended outcome of the error. Or, Apple overstepped and they are fixing that.

But my comment was more directed at the folks who thought bricking phones without warnings was a wise, honest, and great move from Apple. Those threads got downright hostile. Have a look, if you like.

As mentioned, in severely leaning towards this being an error that was operating in unintended ways and that the folks that claimed some crazy hacker was going to steal fingerprints and credit card information was not at all where Apple was going with this, if for no other reason, the fact that we've had Touch ID over two years and this "random" update is what happened to be the one causing issues.
 
Last edited:
I've had a bricked phone since Monday due to this issue. Just tried the update, and I can verify that it worked. I will still plan on taking it to the Apple Store to fix TouchID, but I expect they'll charge me the full $329. We'll see.

So I take it those lawyers are going to pack it up and go home?
 
Odds are good that a software update won't fix it. Have you taken it to Apple?

Yes they confirmed that the update to iOS 9.2.1 "uncovered a previously undetected problem" which not only disabled Touch ID, but also resulted in a significantly increased battery drain. All acknowledged by Apple Geniuses. Although, they could not explain the cause and correlation of the update. Since it has reportedly happened to other 5S owners, there's a chance, although I agree a slim one. I had hoped it was related to something similar to the Error 53 issue, despite the 5S not being bricked, merely Touch ID being disabled, as this patch permits for the 6.
 
Waiting for followup class action lawsuit: Apple wrongly disabled TouchID after screen was replaced by third party.
 
Apple is an utter joke of a company, so it goes from protecting you security by bricking your device because it said third party repair shops could hack their encrypted security, to being publically called out in it and threatened with court action, to now all of a sudden it's not a security risk and they won't block your device here's the fix.
Because they broke the law and would be called out in court of doing this to boost profits only.

So they lie to the public, shocker, and then backtrack.

It's the same with this FBI case where they clearly told Apple they could have the phone, they could install the software at their site, and then return the phone back, the FBI told Apple to not involve them at all and do it all at Apple HQ!

But we have BS public defensive statement from Apple.

And tons of followers blindingly following them including people on here.
You couldn't make it up.
Well I hope the case gets to the Supreme Court as I suspect they will side with the FBI and American security, and slap Apple down a peg.

Your pro-nanny state pro-big government stance is utter treason. The Court Order required Apple to turn over the modified OS to the FBI. Your assertion is false. You seem to be an Android user, so you wouldn't know about security. The FBI wouldn't even bother asking Google to do this because an 8 year old kid could hack any android phone.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.