Apple’s iOS 10 update hasn’t got the best start, unlike how Apple and the iOS device users might have expected. There are already a lot of users reporting about the issue of their devices getting bricked during the update process itself.
According to Techno Buffalo, it is not just the iPhones but the other devices as well that are compatible to update and run iOS 10, but most of them are iPhones, which is why it is wise to wait to see what the issue is and whether it could affect your iPhone as well. Not every iPhone is getting updated, as a couple of iPhone users already shared the screenshots with us saying that there was no issue with the OTA update they did on their iPhone, but it is reported by other users that during the update, the phone is entering recovery mode.
One of the users in them even went on to try the update manually through Apple iTunes and it was successfully done the next time. But that is not the case with everyone because they still see their devices bricked with no successful update. The solution for those who see this happening is to downgrade to the previous iOS version by manually doing so using the IPSW files.
Another user commented saying that it happened to him as well on the OTA update of iOS 10 and when he tried updating the iPhone through iTunes using the software update there using IPSW file, it was all good and happened without a problem. It could be that the software update file that is getting downloaded in the OTA update might be corrupted or incomplete and thus, the non-recognition of the file might be taking the users to recovery mode, but it is too early to say.
The solution for now is to download the IPSW file of iOS 10 for your particular device and fire it up manually through Apple iTunes. You won’t have to do even that if iTunes is already downloading the software update for you automatically after determining the current iOS version. Are you also facing the same issue? Let us know in the comments if you did, and if you found a solution for the same.
We’re sure Apple might be already addressing the problem and will be trying to fix it soon but till then, you should probably wait and not update to iOS 10 already.
