I'm an iPhone 8 Plus user and about 3 weeks ago I had my screen replaced at a local repair shop after cracking it. I'm assuming they used a 3rd party screen. It was working great until the 11.3 ios update of 3/28/18. I woke up in the morning to find a message saying my phone had been updated. Quickly found out my touch screen was dead when I attempted to enter my passcode. Made several hard resets to no avail. Also tried restoring from my most recent iTunes backup and also used iTunes to reset phone to factory settings. Touch screen still dead.
I took my phone back to the repair shop and they said it was definitely due to the most recent update as they'd already had a "flood" of recent repair customers come in for the same reason. They said there was little that could be done until Apple issued another update/fix. The only suggestion they had was to "downgrade" my ios to the previous version. I see no option to do this in iTunes and in any case I don't like it because it's just a temporary fix.
So, I saw this problem pop up a few times in the forums back in September of 2017 following an ios update, but it seems everyone proclaimed the problem solved after Apple issued a fix. Now this seems to be a new/old problem concerning the same issue. Any ideas on things I can try, or am I stuck waiting until Apple recognizes the problem and issues a fix?
I took my phone back to the repair shop and they said it was definitely due to the most recent update as they'd already had a "flood" of recent repair customers come in for the same reason. They said there was little that could be done until Apple issued another update/fix. The only suggestion they had was to "downgrade" my ios to the previous version. I see no option to do this in iTunes and in any case I don't like it because it's just a temporary fix.
So, I saw this problem pop up a few times in the forums back in September of 2017 following an ios update, but it seems everyone proclaimed the problem solved after Apple issued a fix. Now this seems to be a new/old problem concerning the same issue. Any ideas on things I can try, or am I stuck waiting until Apple recognizes the problem and issues a fix?