Sunday, February 7, 2016

Apple “kills” iPhones, which was repaired in unauthorized sites. Users are furious – Gazeta.pl

For several weeks, iPhone users around the world are flooding online forums warnings concerning the mysterious message “Error 53″, which flashed on their phones, and then it completely blocked. Some cases have two common factors:

a) you to repair the damaged iPhone in unauthorized service

b) You did recently updated iOS to version 9.3

Read also: How much Google knows about you? You will be surprised

What is the mysterious “Error 53″? This error is closely related to the fingerprint reader TouchID, in which are equipped with the latest mobile Apple, starting with the iPhone 6. On the official website of the Cupertino company says that the occurrence of “error 53″ means that the biometric reader is damaged or made his unauthorized replacement.

Employees GSM services often are exchanged between the reader TouchID, during the repair of the “Home” or damaged screen of the iPhone. So far, such substitution is not associated with any problems for the users themselves. Changed is the latest update iOS to version 9.3. Now, because of non-genuine iPhone TouchID simply not run.

It turns out that after the exchange TouchID, iOS verifies the compatibility of installed reader with other components iPhone. If the software detects that used unoriginal TouchID, the result on the phone screen will display “Error 53″ and it will be immediately blocked.



Good decision Apple?

Criticism from frustrated users He forced the giant from Cupertino reaction. “We take customer safety very seriously, and Error 53 is the result of security control, which is to protect our customers,” – said in a statement Apple.

Apple explains that in this way protects its customers against fraud. And this argument can in some way understand. It is no secret that the biometric reader is used not only to unlock the phone’s screen, but also, among others, the financial operations within Apple Pay. Replacing TouchID in unauthorized service creates a real threat so that our biometric data could fall into the wrong hands. And that the Cupertino giant would like to avoid.

On the other hand, Apple is not without fault. The company never advised users that an independent exchange reader TouchID or the “Home” may result in the total “sacrifice” of the phone. Such warnings were also in the Communication on updating iOS, which is after all one of the main perpetrators of “Error 53″.

Apple also forget about the people who bought the iPhone in use, and which the seller did not inform about replacing one of the components of the phone. Such people, after installing the latest update of the system, from day to day will be deprived of your iPhone and all of the data that is stored on it.

To make matters worse, experts point out that the launch of the iPhone with non-genuine TouchID is virtually impossible. “There are no components that can be swapped, there is no magic software, nor is there any guide, that could solve this problem,” – notes Mike Wehner DailyDot.com the site.



Comment representative of Apple for the ” the Guardian “

Protecting stored fingerprints in a safe enclave, which is paired with the sensor TouchID. When the iPhone is repaired at an authorized site or the Apple store, and repair of this has an impact on the functioning of TouchID, evaporation is re-validated. This test ensures that the device functions and iOS-related TouchID remain safe. Without evaporation access to the protected enclave could be obtained using the “malicious” reader TouchID. When iOS detects that the pairing is incorrect, TouchID (along with Apple Pay) is deactivated, the device remains secure.


When the iPhone is repaired by unauthorized service, defective screens or other abnormal components which may affect TouchID to the reader, may lead to an error, by which the pair will be impossible. At the next upgrade or restored can then display the “error 53″. If our client encounters this error, we suggest to contact technical support Apple.

Sources: The Guardian, WSJ

LikeTweet

No comments:

Post a Comment