Issues that arise while trying to restore your iPhone or iPad seem to pop up at the worst times. In this piece, we’ll talk about some of the most common iTunes restore errors and how to fix them so you don’t have to spend hours researching for solutions by yourself.
Shortly after releasing the new iOS 9.3 firmware, Apple was forced to stop signing the update following numerous complaints from owners of older iPhones and iPads, such as the original iPad Air and the iPhone 5s and older, that it was bricking their devices.
Monday, Apple re-released iOS 9.3 to fix an issue that prevented users from activating their device via Activation Lock if they couldn’t recall their Apple ID password used to originally set up their device with.
The re-released versions of iOS 9.2 carries a build number of 13E237 and is now available as an over-the-air download although those with a bricked device might want to apply the update through iTunes in DFU mode.
As we reported, numerous users took to Apple’s support forums to complain that some owners of older iPhone and iPad devices saw their hardware bricked after updating to the recently released iOS 9.3 firmware. Apple has since detailed the problem in a support document on its website and pulled the software update for select devices.
Today, the company has re-released iOS 9.3 for those devices. The new build of iOS 9.3 for the iPad 2 has version number “13E236” versus the now defunct iOS 9.3 build “13E234” for the iPhone and “13E233” for the iPad, as per 9to5Mac’s Chance Miller.
Apple has released a support document Wednesday night to address an issue where some iOS users are unable to activate their devices after updating to iOS 9.3, a software version released earlier this week.
Most reports of the issue seem to come from iPad 2 owners, although a quick search online shows that some iPhone users were also affected. In this support document, Apple offers a few options to try and remedy the problem.
Strange things started happening to my TV since first plugging in my new Apple TV a couple weeks ago, and while I didn’t immediately connect the dots, it quickly became apparent that the new device was the culprit. After a bit of digging and a lot of commonsense, I figured out my problems and how to fix them. As often, the solution was just at the click of a button.
Yesterday I decided to look at when my new iPhone 6s backed up to iCloud for the last time when I realized that it hadn’t actually been backed up since September 25, which coincidentally was the first day I got this new device.
I imagined it was just a small hiccup in iCloud, and proceeded to manually initiate an iCloud backup by tapping on “Back Up Now” in Settings > iCloud > Backup. At first, it appeared to work fine as it would show the “Backing Up…” status with the usual “Estimating Time Remaining” message. But after a few seconds, the backup would stop and it would show the following error message: “the last backup could not be completed.”
No matter what I’d do, it kept telling me my iPhone backup couldn’t be completed. The problem appeared to be a little more complex than a simple reboot, but I eventually figured it out.
In this post, I will highlight some of the steps you can take if you are seeing a similar error. Although I cannot guarantee it, I’m pretty confident these steps could actually fix most problems related to iCloud.