Short answer: what you should do depends entirely on *where* the update is stuck. Downloading, preparing and verifying are all recoverable — you can restart the phone if they genuinely stop moving. The Apple-logo progress bar is the one screen where touching anything can turn a slow update into a broken one.
What each screen actually means
| What you see | What is happening | Can you restart? |
|---|---|---|
| Downloading, or slowly gaining percent | Pulling the package from Apple | Yes — worst case you re-download |
| "Preparing update" | Unpacking and staging the files | Yes — it cancels preparation, nothing more |
| "Verifying update" | Checking the download is complete and genuine | Yes — installation has not begun |
| Apple logo with a progress bar | Writing the system partition | No — never interrupt this |
| Stuck after reboot, or a recovery screen | Installation did not complete | Via a computer, with data loss risk |
The line between rows three and four is the only one that really matters. Everything above it is preparation; everything below it is the system being replaced.
Download fails, stalls, or will not start
A download that fails usually has one of two causes, and both are fixable without drama.
Not enough space. iOS needs room to download *and* to unpack, roughly double the size of the update at peak. See the storage section below.
An unstable connection. A download that moves between Wi-Fi and cellular, or a network that drops mid-transfer, can fail repeatedly at the same point. The fix is boring and effective: join one stable network, stay on it, and leave the phone plugged in.
If the same download keeps failing, remove it and start clean — Settings → General → iPhone Storage → find the update → Delete Update. That reclaims the space it was holding and clears a possibly corrupted file.
Stuck on preparing or verifying
These two screens look alarming and are usually fine. Both are local, disk-heavy work: expanding a compressed package, checking it against Apple's published data, and staging what will be written. A phone with a lot of data and little free space can sit here far longer than feels reasonable.
Check three things, in this order:
- Wi-Fi — preparation talks to Apple's servers. A connection that drops can send progress backwards.
- Free space — the working rule is to keep 10–15% of total storage free. "A few GB free" is often not enough, because installation needs continuous contiguous space.
- Power — stay on the charger. A long preparation run draws power, and a low battery can make the system postpone the work.
If all three are fine and the screen is still changing, do nothing. Tapping around to check on it costs more than it looks like. If nothing has changed for a long stretch — plugged in, on Wi-Fi, space available — then a normal restart is reasonable: it cancels preparation work, but preparation can be redone. See iOS 27 update stuck on verifying for the same situation walked through in detail.
The Apple-logo progress bar: the one screen not to touch
Once the Apple logo appears with a progress bar underneath, installation has started and the system partition is being written. This is the phase where interruptions cause real damage.
Do not force restart. Do not let the battery die. Do not unplug it to "reset" anything. A progress bar that sits still for a while during this phase is not unusual — large writes pause. Give it real time.
If it stays there for an hour or more with no movement, then you are past what patience can fix, and the route is a computer: connect to a Mac or PC and either update or restore from there. Restoring means data loss if you do not have a backup, so this is a decision, not a step. If the phone is recoverable, this is exactly the moment to stop improvising and force restart a stuck iPhone properly rather than trying random combinations.
Storage headroom is the usual culprit
If you take one thing from this article, take this: most update failures that are not network failures are storage failures, and the phone's own message ("not enough storage") often does not appear until late.
Installation needs headroom that stays free throughout, not free space that is technically available but fragmented. Aim for 10–15% of total capacity before starting a major update. On a 128 GB phone that is roughly 13–19 GB, which is more than most people keep.
Where to look: Settings → General → iPhone Storage. The list is sorted by size, and the biggest wins are usually photos and videos, followed by apps you do not open. Offloading an app keeps its data and frees the binary; deleting is permanent. If space keeps filling for reasons you cannot see, the explanation is usually in Why is iPhone storage full?.
Can you downgrade?
This is the question people ask after the fact, and the honest answer is that it is usually not available to you.
Apple controls which versions a device will accept through signing. When a new release ships, Apple stops signing the previous one after a short period — in the iOS 27 cycle about a week (shipped 14 September 2026, reported closed 21 September), and Apple publishes no signing schedule. Once signing stops, the device will refuse the old version, and there is no supported workaround. Community sites track which versions are still signed; checking before you assume is the difference between a ten-minute process and an afternoon of frustration.
Two more things that catch people out:
- Downgrading means restoring, and restoring erases the phone. You can put a backup back afterwards, but if you have only backed up *since* updating, that backup belongs to the newer version — and a newer backup generally cannot be restored onto an older OS.
- The window closes quietly. There is no announcement. People usually discover it by trying and failing.
The practical conclusion: "I will update and downgrade if I hate it" is not a real plan. The choice you actually control is made before you tap Install — and if you are weighing that decision, Should I update to iOS 27? sets out the trade-offs, while how long an update takes to settle covers the days after.
Preventing the same failure
Every condition that lets an update finish is also a condition that stops it from stalling, and all of them are cheaper to arrange before you start than to repair afterwards:
- Plug in first, and leave it plugged in throughout
- Sit on one stable Wi-Fi network, not a hotspot or a congested one
- Free up to 10–15% headroom before starting
- Begin when you will not need the phone for a while — then a slow step is an inconvenience, not an emergency
- If it fails twice at the same point, change one thing (usually the network, then the space) rather than repeating the same attempt
The screens reward patience and punish curiosity. Identify the stage, fix the condition that is wrong, and then leave it alone.