Twenty minutes ago your iPhone said "Preparing Update." Now it's showing a progress bar that hasn't moved, or an Apple logo that's been sitting there long enough to worry you. This is one of the most-searched moments of every beta cycle, and it feels scarier than it actually is. Almost every stuck-update situation resolves cleanly, with no data loss, once you work through the right steps in the right order.
That order matters more than any individual fix. The biggest cause of real damage isn't the update itself — it's panicking at minute five and yanking the cable mid-write. This guide moves least destructive first, and asks you to rule out each step before moving to the next. If you haven't started the install yet, our developer beta install walkthrough covers setup; this one picks up once something's gone quiet.
First: is it actually stuck, or is it just slow?
Every stage of an iOS install has a normal amount of standing still. Here's roughly what to expect, based on how Apple's update process has behaved across every recent beta cycle:
- "Preparing Update" can sit unchanged for 20–45 minutes, especially in the first hours after a new beta releases, when Apple's servers see the heaviest load.
- Downloading should creep forward occasionally. Total silence for 45–60 minutes is worth a network check, not yet a restart.
- "Verifying Update" normally takes 5–15 minutes, stretching toward 30 on a congested day — it talks to Apple's servers, it doesn't write to storage.
- Installing, with the Apple logo and progress bar on screen, typically takes 10–30 minutes, longer with less free storage.
The concrete rule: give a stage at least 45 minutes of no movement before assuming trouble, as long as the phone still responds — screen wakes, a button press does something. Only escalate once a stage is frozen and unresponsive for two hours or more. If your device isn't expected to get iOS 28 at all, check our supported devices list first.
Stuck on "Verifying Update," or a network error
Frozen on "Verifying Update"
This step confirms the build is authentic before anything is written to storage, which makes it one of the safest stages to wait through. It's also the stage most affected by server load, so it runs slowest right after a WWDC keynote when huge numbers of devices verify at once. If it's stuck past 45 minutes: open Safari and confirm Wi-Fi actually loads a page, then toggle Wi-Fi off and back on or switch networks. Because nothing has been written yet, a normal restart (hold the side button, slide to power off) is safe here once you've genuinely waited it out.
"Unable to verify update because you are no longer connected to the internet"
This means exactly what it says — your connection dropped mid-verification, or Apple's server hiccuped, leaving a partially downloaded update file behind. Retrying without clearing that file just repeats the error. The fix: go to Settings → General → iPhone Storage, find the iOS 28 beta update entry, and delete it. Reconnect to strong, stable Wi-Fi — not a network you're about to walk away from — then go to Settings → General → Software Update and download it again from scratch.
Frozen on the Apple logo or a stalled progress bar
Once you've genuinely waited past the windows above and the screen is unresponsive to any button press, it's time for a force restart. This erases nothing — it's the same combination you'd use on a phone frozen in any ordinary app.
Face ID iPhones, and iPhone 8 / SE (2nd generation) and later
Apple standardized this sequence starting with the iPhone 8, and it covers every current model, Face ID or Home button: press and release Volume Up, press and release Volume Down, then press and hold the Side button until the Apple logo appears — usually 10–20 seconds — and release. The phone will either resume the install where it left off or boot back into your current iOS version if nothing had been written yet. Both outcomes are fine.
Recovery Mode: Update keeps your data, Restore erases it
If a force restart doesn't get you moving again, Recovery Mode is next: a low-level environment, separate from normal boot, that lets your Mac or PC reinstall iOS over a cable when the phone can't proceed alone.
To enter it: connect your iPhone to a computer and open Finder (macOS Catalina or later) or iTunes. Run the force-restart sequence — Volume Up, Volume Down, hold Side button — but keep holding past where the Apple logo would appear, until you see the connect-to-computer screen instead. Finder or iTunes will detect Recovery Mode and offer two buttons.
DFU mode: the true last resort
DFU (Device Firmware Update) mode sits one level below Recovery Mode — it bypasses even the boot loader, letting your computer write firmware directly to the device. It's only relevant if Recovery Mode itself fails: the computer doesn't recognize the phone, or neither Update nor Restore completes. Entering DFU mode isn't itself destructive to your hardware — it's an official Apple recovery path — but almost every DFU session ends in a full Restore, which erases everything. Don't reach for this first. Reserve it for when Recovery Mode has already genuinely failed, and only proceed once you know you have a usable backup.
This is all far less frightening with a backup already made
Every step above stays completely safe for your data as long as you took an archived backup before starting the beta install. That's why the backup step exists — it turns "Restore erases the device" into an inconvenience, not a disaster. If you skipped it, our backup guide walks through the ten-minute process, worth doing even mid-crisis if your phone is stable enough to sit for a few minutes. Remember the one-way door: a backup taken while already on iOS 28 won't restore onto iOS 27, so if you ever downgrade back to stable, you need a backup that predates the beta specifically. Still deciding if the beta's worth this risk? Our honest risk breakdown covers what's actually likely to go wrong.
Boot loop after a successful install — a different problem
If the update actually completed — you saw "Update Successful" or the phone briefly booted into iOS 28 — and it's now cycling between the Apple logo and a black screen, that's not a stuck update anymore. It's a boot loop, usually traced to a corrupted install file, a leftover configuration profile, or an app crashing during startup. Work through the same order as above: force restart first, since it clears most one-off startup crashes. If it loops again immediately, connect to a computer and use Recovery Mode's Update option to reinstall cleanly without erasing anything. If it continues after a clean reinstall, that points toward a storage or hardware fault, and a Restore — or a visit to Apple — becomes reasonable.
The bottom line
Wait, then force restart, then Recovery Mode's Update, then Restore, then DFU only if Recovery Mode has already failed — in that order, moving on only once the current step is genuinely ruled out. Follow it and the worst realistic outcome is a lost hour, not a lost phone. Nobody's iPhone gets bricked by an official Apple beta; what actually happens is people intervening before the wait was over. For the build-by-build stability picture heading into iOS 28, our main beta guide is the place to start, and you can get notified the moment a new build lands via our alerts page.
| Symptom | First action | Escalation if that fails |
|---|---|---|
| "Preparing Update" frozen | Wait 30–45 minutes, especially on launch day | Force restart once unresponsive for 2+ hours |
| Stuck on "Verifying Update" | Confirm Wi-Fi actually works; wait up to 45 minutes | Toggle Wi-Fi or switch networks, then a normal restart |
| "No longer connected to the internet" error | Delete the partial update in Settings → General → iPhone Storage | Reconnect to strong Wi-Fi and redownload |
| Frozen Apple logo or progress bar | Force restart (Volume Up, Volume Down, hold Side) | Recovery Mode → Update |
| Boot loop after a successful install | Force restart | Recovery Mode → Update, then Restore only if that fails |
Frequently asked questions
How long should I wait before I worry my iPhone is stuck updating to the iOS 28 beta?
Give "Preparing Update" up to 30–45 minutes, especially on beta-launch day, when Apple's servers see the heaviest load. Give "Verifying Update" up to 45 minutes and the installing/Apple-logo stage up to an hour. As long as the screen still responds to a button press, it's working, not stuck. Only treat it as stuck once a stage sits frozen, unresponsive, for two hours or more.
Will I lose my data if I use Recovery Mode?
Not if you choose Update. Update reinstalls iOS over your existing data and settings, so nothing is erased. Restore, by contrast, wipes the device and sets it up as new. Always try Update first, and use Restore only if Update genuinely fails — ideally with a backup already made.
Is DFU mode dangerous for my iPhone?
DFU mode itself doesn't damage the hardware — it's an official Apple recovery path. The real risk is that reaching for DFU almost always means the next step is a full Restore, which erases everything. Treat it as a genuine last resort, reserved for when Recovery Mode has already failed, and only proceed if you have a backup.