Fixing a Slow, Unresponsive, Crashing iPad by Restoring from a Backup

My pertinent experience for this blog post is with an iPad (specifically a "the new iPad" which is generally referred to as the iPad 3) but I expect that these same results would be experienced for any iOS device (iPhone, iPod Touch, etc.). No matter what your device, if you have direct experience with using this technique with a device that is slow, unresponsive, and/or crashing, please post a comment about your experience (whether or not it helped, anything you did different, etc..) as that will very much help other readers.

My iPad had become very unreliable: it crashed (or perhaps I should say it spontaneously rebooted) regularly and when it was running, it was very slow to respond and at times downright unresponsive. The condition got worse and worse to the point where I simply couldn't use it because it just wouldn't respond for more than a few seconds before automatically restarting of its own accord.

The good news is that I was able to get my iPad back working like new by restoring it from a backup; the bad news is that by the time I tried this approach, it had become very hard because the first step in the process is to do a full backup of the device and that was very, very difficult because of my iPad's propensity for spontaneous reboots (but fortunately, with a lot of patience and persistence, I was able to get my iPad to backup).

Now, to be clear, when the iPad was merely painfully slow, I had considering doing a restore from a backup but, though it's easy and straightforward enough, doing a restore from a backup does take a bit of time and so I was reticent to do it without some indication that it might help. For that reason, I searched for guidance and I wasn't seeing people prominently pointing to doing a restore from backup as a troubleshooting step to try and so I didn't jump to do it; as I said already, that that proved costly because things go so bad that I almost couldn't successfully backup the iPad. And that then is the reason I'm writing this post: my hope is that when others search in the future for what to do about extremely slow-to-respond (and even entirely unresponsive) iPads, iPhones, and iPod Touches that crash and/or spontaneously and automatically reboot, they'll find this blog post and be encouraged to try restoring from a backup--and then of course I further hope that those who do try this approach will get the same results that I did: iOS devices that work like new. Please let me know in a comment if it does or doesn't work for you.

Now as to the process of doing a backup and restore: I won't get terribly detailed here because you can find the key details on Apple's Support website. But some notes:

  1. As I mentioned, this process is easy and straightforward but it does take some time; accordingly, make sure you'll be able to dedicate your device to this task for an extended period of time (in other words, don't expect to start this and be able to then take your iPhone somewhere a half hour later).
  2. To do the backup and restore, I used iTunes, not iCloud and I recommend that you do the same as it will certainly be faster. However, I don't know any reason that it wouldn't work using iCloud.
  3. Since what you're going to be doing is reinitializing your device from a backup, the first thing you need to do is backup your device so that the backup you're using for the reinitialization is current.
  4. Then you need to erase your device; this is mentioned but not actually described in the link above. You can do this via iTunes or you can do it directly on the device. I believe these are not entirely equivalent approaches but rather a factory reset via iTunes is a more extensive reset than merely erasing the content and settings directly on the device. I erased the content and settings directly on the device and that worked great for me. Note that the information on erasing the content and settings directly on the device does not mention turning off Find My iPad (or Find my iPhone or whatever is appropriate for your device) but to keep yourself out of trouble, I recommend turning that setting off. I turned it off prior to doing the backup (step 2 above) so that Find My iPad was completely out of the picture and couldn't cause any issues.
  5. Once your device has been erased/reset, you need to restore it from your backup. This part will take the longest. Fortunately, you can just let it run while you do other things.
  6. Once you've restored the backup, if all goes well, you should hopefully be in really good shape with your device! Specifically, your device should work like new. If it doesn't then unfortunately, you are probably dealing with issues that this approach won't fix. But if your device is working well at this point, you'll want to go back and turn on Find My iPad (or Find my iPhone or whatever is appropriate for your device). In addition, if you're an iCloud Keychain user, check the iCloud Keychain setting (it's on the same screen as the Find My iPad setting): I found that it was off and needed to be turned on (but fortunately, so far that's the only setting I've found unexpectedly changed during this process).

So what exactly was wrong with my iPad that the backup and restore appears to have rectified? Well, I had thought all the issues I was seeing (in addition to the poor performance and reliability, I had one app update that just wouldn't finish, leaving the app in a sort of state of limbo; I couldn't remove it by clicking and holding and hitting the "x" to delete it, I had to delete it via the Manage Storage area of the Usage area of the General area of the Settings app) were perhaps because some of my iPad's solid state storage had gone bad (and I was hoping that upon the backup and restore, iOS would avoid using the bad parts of the storage) but after the restore I noticed that my iPad gained around 3 GB of additional free space. Interestingly, when my iPad was misbehaving so badly, the amount of free space reported for the iPad in iTunes did not match the amount of free space reported by the iPhone itself; however, after the backup and restore, the 2 reports matched. I checked my iPhone, which doesn't have performance issues, and the report of its free space in iTunes matches what the iPhone itself reports. This all leads me to believe that mismatches (at least significant mismatches) between the reports of the free space provided by an iOS device and iTunes may be a good indicator that something is seriously amiss with that iOS device. Certainly in the case of my iPad it seems there were some serious "cobwebs" in there that were cleared out by the backup and restore. But regardless of exactly what was going on, I'm just glad it seems to be better now and I hope it stays that way!

As they say, your mileage may vary but I very much hope your results are as good as mine have been!

Comments
Mark's Gravatar Hi, same iPad, same problem, same solution and same memory issue. I restored my iPad a few weeks ago as a last resort (there is a lot to restore inside your apps too) with success but today it started all over again... I don't have a clue what to do next. Any ideas? Mark
# Posted By Mark | 3/3/15 2:45 AM
Josh Adams's Gravatar @Mark: well, I too have had a less-than-perfect experience since my restore with the occasional random crash and delayed response time. However, my experience has remained very good overall, certainly as compared to my experience prior to the restore. So I haven't had any need to take any further action after doing the restore.

Why is there a lot of restoring to do within the apps for you? If you're restoring from a backup, everything should just be there: it should be exactly as it was when you made the backup. If you did a complete teardown where you reset the iPad and then started from scratch setting up the apps then yeah, you would have to do a ton of work getting everything configured properly--and it was this very thing that I wanted to make sure to avoid! That said, it's conceivable that some or all of the "cobwebs" could be related to settings or something of that type which would be in the backup and in that case, doing a complete teardown could be the only way to get rid of those. But if you've done a complete teardown and you're still hitting the issues then either the reconfiguration you did brought the cobwebs back or the issues are something related to the hardware and I would think that the biggest possibility there would be memory issues. You could do a full reset of the iPad and then not install or configure anything and see if you hit issues; if you don't hit issues, you won't know for sure what was causing the issues you saw previously but if you do hit issues, you will have a pretty darn good idea that they are caused by hardware issues (again, I would think those would most likely be memory issues).

My understanding is that the iPad is supposed to be able to isolate bad memory and not use it. If bad memory is your problem, either the isolation of bad memory is not working well for you or you've had yet more memory go bad since you did the full restore. It seems then that since it could be that you've had more memory go bad, you might benefit from doing another full restore.

Next time I buy an iPad, I'm going to ask if they have a way in the Apple Store to check whether or not some memory has gone bad. If they do, I'm going to pop the $99 for AppleCare and then take the iPad back to the Apple Store just under 2 years after buying it to have its memory checked because at that point if any has gone bad, they'll provide a replacement iPad.
# Posted By Josh Adams | 3/3/15 9:23 AM
mep's Gravatar Restoring to factory settings did the trick for me. Since the update to ios 8, my ipad mini had been slow, unrespnsive, freezing, and randomly going to the "apple" screen even when simply playing music (a song would suddenly stop in the middle). I hesitated to do the factory reset; so many sources indicated that it would be a giant hassle, but it was actally quie simple, and, so far, my ipad is working like new again. I recommend this process.
# Posted By mep | 11/14/15 11:02 PM
BlogCFC was created by Raymond Camden. This blog is running version 5.9.002. Contact Blog Owner