Skip to content

iPhone  ·  Procedure

Restart, Force Restart and Recovery

Three escalating operations on iPhone, and the last can erase the device. Which to use depends on what the screen is doing.

An iPhone that is misbehaving has three levels of intervention available. They are frequently confused, the button sequences look similar, and the most drastic one will offer to erase the device.

The three operations

Restart. An ordinary shutdown and power-on. The operating system closes things properly. Use this whenever the phone still responds.

Force restart. Cuts power to the processor and reboots, without asking the operating system. This is the equivalent of holding the power button on a computer. Nothing is erased and nothing is lost beyond unsaved work in open apps. Use it when the screen is frozen or unresponsive.

Recovery mode. Boots into a minimal state that talks to a computer, which can then restore or update the device. This is for a phone that will not boot at all. Restoring from recovery mode erases the phone unless an update succeeds first.

There is also DFU mode, a deeper variant used mainly for repair work. If you have not been told specifically to use it, you do not need it.

Which to use

The phone responds but an app is stuck. Close the app. Do not restart the phone.

The phone is slow or behaving oddly. Ordinary restart. This resolves a surprising share of transient problems and costs nothing.

The screen is frozen, touch does nothing, buttons do nothing. Force restart. This is what it is for.

The phone shows the logo and never gets further, or shows a black screen that will not wake after a force restart. This is the recovery mode case, and it means something is wrong with the system software.

The phone was mid-update when the power failed. Recovery mode, and try the update option before the restore option.

The force restart sequence

On current iPhones with Face ID and on recent home-button models, the sequence is: press and release volume up, press and release volume down, then hold the side button until the logo appears. Holding for around ten to fifteen seconds is normal, and people frequently release too early and conclude it did not work.

Older models with a home button use different combinations. If the sequence above does not produce a logo after twenty seconds, look up the sequence for your specific model rather than guessing — pressing the wrong combination on some models triggers the emergency call countdown.

Force restart is safe. It does not erase data. It is not a last resort. Trying it before anything more involved is correct.

Before entering recovery mode

Recovery mode leads to two options when connected to a computer: update, which reinstalls the operating system while preserving data, and restore, which erases everything.

Always try update first. It frequently works, and it keeps your data.

Restore erases the phone. Everything not backed up is gone. If you have no backup, exhaust every other option before restoring.

Check what backup you actually have before you get to this point. Not "backup is on" — check the date of the last successful backup. A backup that has been failing silently for four months is common.

When the phone will not charge or turn on

Before assuming a software problem, rule out the simple physical causes, in this order.

A different cable and a different adapter. Cables fail internally far more often than phones do, and the failure is invisible.

A wall outlet rather than a computer or a car. Low-power sources may not charge a deeply discharged battery.

Clean the port. Pocket lint compacts into the connector and prevents contact. This is an extremely common cause and it looks exactly like a dead phone. Use something non-metallic, with the phone powered off.

Leave it charging for thirty minutes before concluding anything. A fully discharged battery needs time before it will show anything at all.

Then force restart while connected. A phone that is charging but has crashed will show nothing until it reboots.

If none of that produces a charging indicator, the problem is hardware — battery, port or charging circuit — and it needs service.

What restarting does not fix

Storage that is full. The symptoms overlap — slowness, apps closing — but restarting frees nothing.

A degraded battery. Sudden shutdowns at a non-zero percentage are a battery symptom, not a software one. Check battery health.

An app that crashes consistently. Restart the phone once; if it persists, the app or its data is the problem.

Network problems. Restarting the phone is a reasonable first step, and if the problem is the network it will return immediately.

The maintenance question

Restarting a phone on a schedule is not necessary. iOS manages memory and background processes without help, and there is no accumulating state that a weekly restart clears.

If a phone genuinely needs frequent restarts to stay usable, that is a symptom worth investigating — usually failing storage, a failing battery, or an app misbehaving badly enough to destabilise the system.