回答“Top half screen don’t work only bottom”Came across the same issue tonight, I had two XS units and 3 OEM screens. I found that for some reason, when I swapped the screens over one worked fine on one XS (XS_A)while the other one the top 3 row of icons was dead(XS_B). Yet I could swap another screen on XS_B and the screen would work fine. This proves that the logic board was fine & when I put the supposed half dead screen back on XS_A (original paired phone) the screen worked fine. The only difference I could see was…XS_A was on iOS 13.6 and XS_B was on iOS 14.1. Makes me wonder does iOS 14 have software checks that disables part of the screen if it’s not it’s originally paired screen…
回答“also have the error 53”Sounds very similar to my error 53 issue. I swapped out a new LCD Shield plate which had the home button cable and was able to then restore. I assume that's what you also replaced when you are talking about the flex cable? If you have perhaps its related to the home button / Touch ID assembly which can't be replaced to restore the device.
回答“iPhone is dead after replacing battery and button”I know this is a dead thread (no pun intended) but I have the same issue. iPhone 5 dead, bought two new batteries thru iFixit, battery worked fine. Then over a week of charge/discharge cycles it finally went dead again when it gets down to 0%. So I chucked the second battery in, battery charged to 100% & since its fully discharged its dead again. Any thoughts guys?
回答“iTunes Error 53 - Please help!”I was given a water damaged iPhone 6, I tried DFU Restoring it and it would error 53 on both my Mac & Windows PC and with different cables & up to date iTunes clients. It had fried itself in the home button cable that continues behind the LCD Shield plate to touch ID/home button assembly connection. I thought I would try getting a new LCD Shield plate that includes the home button cable. I swapped out the LCD Shield plates out and SUCCESS with the DFU Restore! Error 53 in this instance was hardware related! Thanks for the some of the posts here that helped me pinpoint the likely cause which you only discover when trying to restore!