Categories
AppleCare+ Hardware iPhone News Touch ID

Some iPhone 8 users experiencing errors after upgrading to iOS 11.3 after third-party screen repairs

A number of iPhone 8 owners who had their screens replaced with third party aftermarket screens have found that the iOS 11.3 software update essentially killed their devices.

Per a report published on Tuesday by Motherboard, the release of iOS 11.3 has killed the touch functionality in “thousands” of iPhone 8 devices with screens repaired by non-Apple third parties, when those phones had worked previously. One repair shop told the site that the issue has caused “over 2,000 reshipments” in the less than two weeks since the software update.

It’s unknown as to exactly what caused the glitch, or if a future software update will fix the issue. Apple has yet to comment on the issue.


According to Michael Oberdick, an Ohio repair shop technician, the “repair community” believes a certain microchip is responsible for powering the screens. Repair shops have figured out how to fix the phones, by opening them and “upgrading” the chips.

Another tech shop owner stated that two customers have come in complaining about the screen problem since the new update, while another customer complained of a voice recorder that stopped working.

In 2016, customers sued Apple over “Error 53” glitches, in which iPhones were bricked after third party repair personnel altered the Touch ID technology, which Apple acknowledged that year was part of Touch ID security.

In early 2017, Apple adjusted its long-standing policy and announced that third-party iPhone screen repairs would no longer violate standard warranties, as long as those repairs did not damage the casing or other related components. Apple also made the “Horizon Machine” calibration device available to authorized third party repair shops, in an effort to reduce lines at Apple Stores.

Apple presently charges AppleCare+ $29 for an iPhone 8 repair. This does not cover the back glass, which retails for $99 through Apple.

If you’ve seen this issue on your end, please let us know in the comments.

Via AppleInsider and Motherboard