Blog / Operating systems & apps /

Rolling back or delaying an iPhone update

You updated your iPhone, and now something is worse. The battery drains faster, an app crashes, or the new design irritates you. The first question is always the same: can I go back?

The honest answer is usually “not easily, and not for long”. So most of this post is about what you can do before you update, and what to do if you’re already stuck.

Rolling back: the hard truth

Apple generally lets you install only the latest version of iOS, or versions it is still “signing”. After a new version arrives, Apple stops signing the older one, usually within a couple of weeks. Once the signature is gone, your iPhone will refuse to install it.

So a rollback is possible only in a narrow window, and only if Apple is still signing the older version.

It’s also not a one-tap process. It means connecting the iPhone to a computer, putting it into recovery mode, and restoring a downloaded firmware file for the older version. The restore erases the phone.

And there is a catch that trips people up: a backup made on a newer iOS can’t be restored onto an older iOS. If you updated, then made a fresh backup, then went back, that new backup won’t load. You’d need an older backup, which you may not have. That means you can lose recent photos, messages and app data.

For that reason, I would not recommend rolling back for a minor annoyance. Weigh it carefully:

  • Do it only if the update has seriously broken something you need, and Apple’s support doesn’t have a fix.
  • Don’t if the complaint is a changed look or a small bug. A later patch often fixes those.

If you decide to try, Apple’s support pages describe the official process for restoring with a computer. Follow those, not instructions from forums that point to unofficial downloads. Fake firmware is a classic way to get malware, or a bricked phone.

Betas are a different story

If you installed a beta (a public or developer preview), Apple does provide a way back to the current public release, because betas are meant to be temporary. In Settings, look for the beta updates option under Software Update and switch it off, then wait for the next public release, or restore through a computer. Apple documents the steps on its support site.

The lesson: don’t put betas on the phone you can’t afford to lose. Use a spare device, or wait.

Delaying an update

Delaying is much easier than rolling back, and it’s the better habit.

Turn off automatic installation

  1. Open Settings, then General, then Software Update.
  2. Tap Automatic Updates.
  3. You can switch off “Install iOS Updates” while leaving “Download iOS Updates” or security responses on. Menu names vary by version, so look around if yours is different.

This stops the phone installing a major update overnight when you didn’t expect it.

Stay on the previous major version for a while

In recent iOS versions, when a big new release arrives, the Software Update screen may offer you a choice: the new version, or the latest update to the version you’re already on. This lets you keep receiving security fixes without jumping to the new major release straight away. The choice appears for a limited period and depends on your phone.

Wait a week or two

My own rule for major updates is to let a week or two pass. Early adopters find the problems, Apple fixes the worst ones in a point release, and the experience is smoother. I wouldn’t wait much longer than that, because security fixes are the reason updates exist, as I explain in software updates: why “remind me tomorrow” is a security risk.

A checklist before you update

  1. Back up first. Use iCloud, or a computer. If your iCloud storage is full, free up some space or buy a little more before you start.
  2. Check your phone is supported for the new version.
  3. Check that key apps are ready. Your bank and work apps usually say on their App Store pages or websites if a new iOS causes problems.
  4. Charge the phone and use reliable Wi-Fi.
  5. Plan the timing: not before a flight, a trip or an important meeting.
  6. Keep the old backup. If you can, archive the last backup made on the old iOS before overwriting it. On a computer, you can do this in the backup settings.

That sixth point is the one that makes a rollback possible later. It’s easy to skip, and it’s the one people regret.

If something is wrong after updating

Before you think about going back, try the fixes that solve most problems.

  • Restart the phone. It sounds silly, and it works more often than it should.
  • Update the apps. App makers release fixes soon after a new iOS.
  • Wait a day or two for battery. After a big update, the phone re-indexes photos and files in the background, which uses power.
  • Check for a point release. Settings, General, Software Update.
  • Reset settings (not “erase all content”). Settings, General, Transfer or Reset iPhone, Reset, Reset All Settings. This keeps your data but resets preferences.
  • Contact Apple Support if something is badly broken.

Is it worth the stress?

For most people, the best defence isn’t a rollback plan at all. It’s a backup, a short delay and a bit of patience. Staying on an older iOS for months leaves security holes open. Rolling back is slow and risky. Updating a week or two late, after a backup, is the dull answer that works.

For the web admin

If your iPhone holds your authenticator codes, admin app logins and client contacts, a bad update at the wrong moment can cost you a working day. This is why I do major updates when I have time, not on the morning of a launch. And I keep my two-factor codes recoverable, as in transferring two-factor codes to a new phone.

Key takeaways

  • Apple signs only recent iOS versions, so rolling back is rarely possible and always erases the phone.
  • A backup from a newer iOS won’t restore onto an older one.
  • Delay by switching off automatic installs, or by staying on the previous version when Apple offers it.
  • Back up before every major update, and keep the old backup if you can.

Have you ever regretted updating a phone, and what broke?