Phone Stuck on the Logo / Boot Loop? Causes & Fixes (iPhone & Android, 2026)

Few things make your stomach drop like a phone that powers on, shows the Apple or Samsung logo… and then just sits there – or flashes the logo, goes black, and repeats forever. This is a boot loop (or a phone "stuck on the logo"). The good news: most cases are software problems you can fix at home without losing a thing – provided you work through the steps in the right order.

Order matters: some fixes are completely safe, others wipe everything. This guide walks you up a fix ladder for both iPhone and Android – gentlest step to most drastic, data risk flagged at every rung – and tells you honestly when it's hardware that needs a repair bench.

Direct answer: A phone stuck on the logo or boot looping is usually caused by a failed or interrupted software update, corrupt system files, or a misbehaving app – and a force restart, a full charge, or reinstalling the operating system (an iPhone recovery-mode update, not a restore) fixes most of them without erasing your data. If those steps fail, the cause is more likely hardware – failing storage, a battery that can no longer sustain a boot, or liquid/board damage – which needs professional repair. Only a factory reset or DFU restore erases your data, so leave those until last and back up first.

Why your phone gets stuck on the logo or boot loops

A boot loop means the phone is failing partway through start-up and restarting to try again. Working out why is mostly about asking what changed just before it started. The causes split into two camps.

Software causes (usually fixable at home)

• A failed or interrupted update – the phone lost power, Wi–Fi, or space partway through an update, leaving the system half-written.
• Corrupt system files – a glitch damaged a file the phone needs to finish booting.
• A bad app or app update – one that crashes the system as it loads (more common on Android).
• Critically low storage – with no free space, the system can't create the files it needs to boot.
• A failed jailbreak or root – modifying system software is a classic loop trigger, and makes the fix harder.

Hardware causes (need the repair bench)

• Failing storage (NAND) – the chip holding the OS is developing bad sectors, so it can't load reliably.
• A worn or faulty battery – booting draws a heavy current spike a degraded cell can collapse under, resetting the phone.
• Liquid or board damage – corrosion or a failed component (a power-management IC, say) interrupting the boot.
• A loose or damaged connector after a drop or a previous DIY repair.

The practical test: software faults respond to the steps below; hardware faults don't. Climb the whole ladder, and if the phone still won't boot, it's almost certainly hardware. If it won't even show the logo or react to charging, that's a different problem – start with our guide on a phone that won't turn on.

Before you start: the one rule about your data

The safe fixes below don't touch your photos, messages, or apps; the drastic fixes erase everything. We label each step clearly – stop at the right rung, resist the urge to panic-reset, and your data is usually safe.

If the phone is currently booting at all – even into safe mode – back it up before anything else; a boot loop can deteriorate. Our guide to backing up your device before a repair covers iCloud, Google, and computer backups. If it won't boot far enough to back up, don't force a reset – skip to the data recovery section below.

The fix ladder: safest steps first

Work down this list in order. Try each step, then check whether the phone boots normally before moving on. Most loops are resolved by step 1 or step 4.

Step 1 – Force restart (no data risk)

A force restart cuts the power and reloads the system from scratch. It clears a temporary glitch, deletes nothing, and fixes a surprising number of "stuck on the logo" cases.

• iPhone 8 and later (including SE 2020 and newer): press and quickly release Volume Up, press and quickly release Volume Down, then hold the Side button until the screen goes black and the Apple logo reappears.
• iPhone 7 / 7 Plus: hold Volume Down + the Side button until the logo reappears.
• iPhone 6s, SE (1st gen) and earlier: hold the Home button + the Side/Top button until the logo reappears.
• Most Android phones (Samsung, Pixel, etc.): hold Power + Volume Down for around 10–20 seconds until it restarts; some Samsung models need a little longer.

If it reboots and stays on, you're done. If it loops straight back, move on – but don't keep hammering the force restart; repeated failures mean something more is wrong.

Step 2 – Charge it fully on a known-good cable (no data risk)

A weak battery is a common, overlooked cause: if it can't deliver the current spike a boot needs, the phone browns out and resets, looking exactly like a software loop. Plug it into a wall charger (not a laptop port) using a cable and adapter you know work, and leave it for 30–60 minutes before trying again. This is safe and changes nothing. If it makes no difference and the phone is older, suspect a battery or board issue.

Step 3 – Boot into safe mode, Android only (no data risk)

Safe mode starts Android with only the built-in software and none of your downloaded apps. If the phone boots fine in safe mode, a third-party app is the culprit – almost always one installed or updated just before the trouble began. Safe mode deletes nothing.

• With the phone off, power it on, and as soon as the maker's logo appears, press and hold Volume Down until it finishes booting. You'll see "Safe mode" in a corner of the screen.
• If it reaches the home screen, uninstall the most recently added or updated apps one at a time, then restart normally. Uninstalling removes only that app's data, not your photos or messages.

iPhones have no safe mode – Apple doesn't allow it – so iPhone users skip to step 4.

Step 4 – Reinstall the operating system without wiping (low data risk)

iPhone – recovery-mode UPDATE (not Restore): connect the iPhone to a computer. On a Mac (macOS Catalina or later) open Finder; on Windows or older Macs open the Apple Devices app or iTunes. Put the iPhone into recovery mode using the same button sequence as the force restart, but keep holding until you see the recovery screen (a cable pointing to a laptop), not the Apple logo. The computer offers Update or Restore – choose Update. This reinstalls iOS and repairs the system files while keeping your data; only choose Restore as a last resort, because Restore erases everything. If the download passes 15 minutes and the iPhone leaves the recovery screen, repeat and choose Update again.

Android – clear the cache partition (where available): many Android phones boot into a recovery menu (typically powered off, then Power + Volume Up – the combination varies by maker). If the option exists, choose "Wipe cache partition", which clears temporary system files without deleting your photos, apps, or accounts. Be very careful not to select "Wipe data/factory reset" here – that's the next, data-erasing step.

Step 5 – Factory reset / DFU restore (ERASES ALL DATA – last resort)

Data-loss warning: A factory reset (Android) or DFU/Restore (iPhone) wipes the phone completely – every photo, message, and app. Do this only if you have a backup, or if you genuinely accept losing the data to revive the phone. If your photos aren't backed up, stop here and read the data recovery section first.

A clean wipe and reinstall is the most reliable software fix, but the most destructive – which is why it sits last. Resetting first is how most people lose perfectly recoverable data.

• iPhone: connect to a computer, enter recovery mode as in step 4, and choose Restore (or perform a DFU restore for a deeper reinstall). The phone downloads a fresh copy of iOS and erases the device.
• Android: from the recovery menu choose "Wipe data/factory reset", confirm, then reboot. You'll need the Google or Samsung account that was last signed in to set the phone up again afterwards.

If a full wipe still doesn't produce a clean boot, the verdict is clear: the problem isn't software at all.

When it's hardware, not software

If you've worked through the ladder and the phone still loops or hangs on the logo, the fault is hardware – most often the failing storage (NAND), worn battery, or liquid/board damage listed earlier. A loop that survives even a factory reset is the classic sign of a degrading storage chip. These need diagnosis with proper equipment – reading boot logs, measuring power rails, and sometimes micro-soldering or storage work. No button combination will solve them, so this is the point to hand it to a workshop.

"But my photos aren't backed up!"

This is the situation that causes the most avoidable data loss. If the phone won't boot far enough to back up and nothing is saved elsewhere, do not perform a factory reset or DFU restore – those steps overwrite exactly the data you're trying to save.

The reassuring news: a phone stuck on the logo very often still has perfectly intact storage – the data is sitting there safely; the phone just can't finish loading the system around it. The files can frequently still be recovered on the bench, even when the phone won't boot at home. Our guide on data recovery from a dead phone explains what's possible.

When to let a workshop take over

Bring in professional help when the phone loops even after an OS reinstall or factory reset, has been near liquid, failed after a drop, or holds data you can't risk losing. More home tinkering only tends to make things worse.

celltech diagnoses and repairs boot-loop faults as a UK-wide, mail-in-only specialist – tracked and insured both ways, with pricing published up front rather than hidden behind a quote form. Diagnostics are free on standard repairs, and standard repairs carry a 27-month guarantee – more than double the 12 months most independent UK repairers offer, and far longer than a manufacturer's typical 90 days. Because we repair rather than swap the storage where we can, recovering your data is part of the conversation, not an afterthought.

Frequently asked questions

What does it mean when my phone is stuck on the logo?

It means the phone has power and starts to switch on but can't finish loading its operating system, so it hangs at the logo (or restarts repeatedly – a "boot loop"). Usually that's software, like a failed update or a corrupt file; sometimes it's hardware, like failing storage or a worn battery.

Will I lose my data fixing a boot loop?

Not with the safe steps. A force restart, a full charge, safe mode, an iPhone recovery-mode update, and clearing the Android cache partition all leave your data untouched. The only steps that erase data are a factory reset and a Restore or DFU restore – which is why they sit last.

What's the difference between "Update" and "Restore" in iPhone recovery mode?

It's the difference between keeping and losing your data. Update reinstalls iOS and repairs the system files while preserving your photos, messages, and apps; Restore wipes the iPhone and installs a fresh copy of iOS. Always try Update first; only use Restore if it fails and you have a backup.

My phone boot-looped right after a software update – what do I do?

One of the most common – and most fixable – scenarios; the update was likely interrupted or left half-written. Force restart, charge the phone well, then reinstall the OS via the iPhone recovery-mode Update (not Restore) or, on Android, clear the cache partition – repairing the update without erasing your data in most cases.

Can a bad battery cause a boot loop?

Yes. Booting draws a sharp current spike, and a degraded battery can sag below the voltage the phone needs, resetting it just as it powers up – mimicking a software loop. It's more common on older phones. If charging fully on a known-good cable helps, or the battery is years old, a battery or power fault is a strong suspect.

Can you recover my photos if the phone won't boot at all?

Often, yes. A phone stuck on the logo frequently still has fully intact storage – the data is fine; the system just can't load around it. As long as the storage chip isn't physically destroyed, recovery is frequently possible on the bench. The key is to avoid factory resets and restores, which overwrite the very data you want back.