You press the power button, the familiar logo pops up like it’s about to boot normally, and then… nothing. It just sits there. Maybe it flickers and tries again a minute later, looping back to the same screen. It’s an unsettling moment, mostly because a frozen logo screen looks a lot like a dead phone, when in reality it’s usually something far more fixable: the operating system is failing partway through loading, caught in what’s commonly called a boot loop.
The good news is that in the vast majority of cases, this resolves without losing any of your data, and the steps differ a little depending on whether you’re dealing with an iPhone or an Android device.
First, Figure Out How Long It’s Actually Been Stuck
This matters more than people realize. If it’s been under ten minutes, this might just be a slow, normal boot after a recent update — the best thing to do is leave it alone rather than interrupting it. If it’s been ten to thirty minutes with occasional flickering or restarting, that’s more likely a genuine soft boot loop, and the steps below are worth trying. If it’s been hours with total silence — no vibration, no response to anything — that leans more toward a hardware issue, which we’ll get to.
If You’re on an iPhone
The first thing worth trying is a force restart, and the exact button sequence depends on your model. On an iPhone 8 or later, quickly press Volume Up, then Volume Down, then hold the Side button until the Apple logo appears. On a 7 or 7 Plus, it’s Volume Down held together with the Side button. On a 6s or earlier, it’s Home and the Side (or Top) button held together. This single step resolves the majority of logo-loop situations and doesn’t touch your data at all.
If that doesn’t do it, the next step is Recovery Mode. Connect the phone to a computer, open Finder on a Mac or iTunes on Windows, and use the same button combination as above — but this time, instead of letting go when the Apple logo appears, keep holding until you see a screen prompting you to connect to a computer. From there, choose Update rather than Restore. Update reinstalls the operating system while keeping your data intact; Restore wipes everything, so it’s worth treating as a genuine last resort rather than a first move.
One thing worth checking before you do any of this: look closely at the edges of the screen. If it looks slightly lifted or separated from the frame, that can indicate a swollen battery, and in that case, stop trying to power it on and get it to a technician — it’s a safety issue, not just a technical one.
If You’re on Android
Start the same way, with a force restart — usually Power and Volume Down held together for ten to twenty seconds, though some models just need the Power button alone held for a similar length of time.
If that gets it moving but it seems unstable, try booting into Safe Mode. This temporarily disables third-party apps, and if the phone runs fine there, you’ve likely found your problem: something you installed recently is the culprit, and uninstalling the most recent addition usually solves it. The exact way to reach Safe Mode varies a bit by brand, but on most phones it involves holding the Power button, then long-pressing the on-screen Power Off option until a “Reboot to Safe Mode” prompt appears.
If Safe Mode isn’t the fix, wiping the cache partition is the next reasonable step, and importantly, this is different from a factory reset — it clears out corrupted temporary files without touching your photos, messages, or app data. You’ll need to power the phone off completely, then hold a specific button combination (commonly Power and Volume Up, though this varies by brand) to enter Recovery Mode, navigate using the volume buttons, and select the option to wipe the cache partition before rebooting.
If none of that works and you’re still stuck, a full factory reset from Recovery Mode will almost always get the phone booting again, but it does erase everything on the device. This is genuinely a last resort — only worth doing if you have a backup, or if the alternative is a phone that simply won’t start at all.
When It’s Probably Not a Software Problem
Some signs point more clearly toward hardware rather than something you can fix yourself. If the phone doesn’t respond to any force-restart combination at all, if the issue appeared suddenly after a drop or water exposure, if you notice any discoloration or lines on the screen, or if even Recovery Mode won’t load, these all suggest something physical is going on — often a loose display connector or a damaged component on the motherboard. These are usually fixable by a technician, just not through software steps on your end.
A Couple of Habits That Prevent This
Keeping at least 15% of your storage free helps avoid failed updates mid-installation, which is one of the more common triggers for a boot loop in the first place. And it’s worth resisting the urge to interrupt a software update once it’s started, even if it seems to be taking a while — interrupting partway through is one of the more reliable ways to end up stuck on a logo screen. Regular backups, whether to the cloud or a computer, also mean that if a factory reset ever does become necessary, it’s a minor inconvenience rather than a genuine data-loss emergency.
Frequently Asked Questions
Will I lose my data if my phone is stuck on the logo screen?
Not necessarily. Force restarting and clearing the cache both preserve your data completely. It’s only a full factory reset or Restore that wipes everything, and that’s meant to be a last resort rather than a default step.
How long is too long for a phone to be stuck on the logo screen?
Somewhere past fifteen to twenty minutes without any progress, especially if you’re seeing repeated restart loops, is a reasonable point to stop waiting and start troubleshooting.
Can a low battery cause a boot loop?
Yes, it can. If the battery is critically low or beginning to fail, some phones will loop on the logo screen rather than booting normally. It’s worth plugging in and letting it charge for at least thirty minutes before assuming it’s a deeper issue.
Is this covered under warranty?
If the cause turns out to be software-related rather than physical damage, and the phone is still within its warranty period, this is typically covered at no cost by the manufacturer.