Samsung Galaxy Boot Loop Fix: Practical Ways to Stop the Restarting

A step-by-step order of operations for a Galaxy that won’t get past the logo — starting with the fix that costs nothing and ending with when to stop touching it yourself.

By Oyekale Olawale

⚡ Quick Answer

Hold Volume Down + Power (or Side key) for 10 seconds to force a reboot first — this alone clears a huge share of Galaxy boot loops with zero data loss. If that fails, boot into Safe Mode to rule out a rogue app, then try Wipe Cache Partition in Recovery Mode. Only move to a factory reset or Samsung’s Emergency Software Recovery tool if none of that works, and stop entirely if the phone shows liquid or impact damage — that’s a hardware job, not a software one.

A Samsung Galaxy boot loop is when the phone restarts on its own, over and over, usually stalling at the “Samsung” or “Samsung Galaxy” logo before the screen goes black and the cycle starts again. It’s not the same as a phone that’s simply frozen on the logo once — a true loop repeats. The good news: on a phone with no physical or water damage, this is almost always fixable without a repair shop, and the fixes below are listed in the order I’d actually try them, cheapest and least risky first.

Is It a Boot Loop, or Just Stuck at the Logo?

These get confused constantly, and the fix path is slightly different for each. Use this to figure out which one you actually have before you start:

Symptom	What’s Happening	Start With
Logo appears, screen goes dark, logo comes back — repeating	True boot loop	Force restart → Safe Mode
Logo just sits there, never moves, no repeats	Stuck at logo (system hang)	Force restart, wait 15 min first
Loop started right after a software update	Update-triggered bootloop	Wipe cache → Smart Switch recovery
Phone was dropped, got wet, or feels hot to the touch	Likely hardware fault	Skip to the damage-check section

The Troubleshooting Order, Visually

Follow this path top to bottom. Each box only leads somewhere else if the one above it didn’t work — don’t skip ahead to a factory reset if you haven’t tried Safe Mode yet.

Fix 1: Force a Restart (Try This First, Always)

Samsung’s own US support page lists this as step one for exactly this symptom, and it’s the fix I reach for before anything else. It doesn’t touch your data, and on phones where the loop was caused by a hung process rather than corrupted data, it works outright.

Check battery is above 5% (charge 15 min if fully dead)

Hold Volume Down + Power/Side key together for ~10 seconds

If a menu appears, keep holding until the Samsung logo shows

Select Normal Boot if a Maintenance Mode screen appears

Newer flagships use the Side key instead of a dedicated Power button, but the combo is the same. If the phone genuinely won’t hold a charge through this, that’s a separate problem worth checking against our Android phone not charging fix before you go any further with the loop itself.

Fix 2: Boot Into Safe Mode to Isolate a Bad App

This is the step people skip, and it’s the one that most often saves you from a factory reset. Safe Mode loads only the software your phone shipped with — no third-party apps — so if the loop stops here, something you installed is the actual cause, not the OS.

Press and hold Power until the Power menu appears (or open Quick Settings and tap the Power icon on button-less models)
Touch and hold Power off until a “Safe mode” option pops up, then tap it
You’ll see “Safe mode” watermarked at the bottom of the screen once it’s active
If it boots and stays stable, uninstall whatever you added most recently, one at a time, restarting normally after each removal

One thing worth knowing: this is also the mode Samsung recommends for a phone that has a screen or camera acting up but not necessarily looping — if your display is also unresponsive to taps, our Android touch screen not responding fix covers that specific combination.

Fix 3: Wipe Cache Partition From Recovery Mode

Wiping the cache partition clears leftover system and app cache files without touching your photos, messages, or app data — it’s a much smaller hammer than a factory reset, and it’s fixed genuine bootloops caused by a corrupted update cache in my own testing.

Power the device off completely
Press and hold Volume Up + Power/Side key (older removable-battery models use Volume Up + Home + Power) until the logo appears, then keep holding Volume Up until the Recovery Mode screen loads
Use Volume keys to highlight Wipe Cache Partition, then the Power key to select it
Confirm with Yes, wait for the process bar to finish, then select Reboot System Now

A quirk I ran into on recent One UI builds

On some current-generation Galaxy models, the button combo alone won’t reliably get you into Recovery Mode — Samsung’s own community moderators have confirmed you need the phone connected via a USB-C cable to a computer first, then hold Volume Up + Power once the charging icon shows. On a few newer devices, users report the Wipe Cache Partition option has been removed from the recovery menu entirely, reportedly to cut down on accidental data wipes by regular users. If your recovery menu looks different from the steps above, that’s most likely why — it’s a real, reported inconsistency, not something you’re doing wrong.

Fix 4: Check for a Software Update Through Smart Switch

If the loop started right after an OTA update, an interrupted or corrupted install is a likely culprit, and re-running the update from a computer via Smart Switch can push a clean copy of the firmware. Install Smart Switch on a Mac or Windows PC, connect the Galaxy with its original USB cable, open the app, and let it detect the device — if an update is pending, an Update button appears. Select it and don’t disconnect the cable until it finishes. If your PC isn’t recognizing the phone over USB at all, that’s a separate and fairly common snag — our USB device not recognized in Windows 11 fix walks through the driver and port checks that usually clear it, and if you’re on a desktop without built-in Wi-Fi, our USB Wi-Fi adapter setup guide will get the PC itself online so Smart Switch can pull the firmware.

Fix 5: Emergency Software Recovery and Initialization

This is Samsung’s official last-resort software tool, documented on its firmware recovery portal, and it’s a step up from a normal update: it reflashes the phone’s firmware from scratch. In Smart Switch on your computer, go to More → Emergency Software Recovery and Initialization, select your device from the list, read the warning carefully (this typically wipes the device), and confirm. In my testing and in reports from Samsung’s own community forum, this sometimes needs two or three attempts before it takes — if it fails silently the first time, unplug, restart Smart Switch, and try again rather than assuming it’s broken.

Fix 6: Factory Reset From Recovery Mode

This erases everything on the phone and reinstalls the OS clean, so treat it as a last software step, not a first one. From the same Recovery Mode screen described in Fix 3, select Wipe Data/Factory Reset instead of Wipe Cache Partition, confirm, then Reboot System Now.

If there are photos or messages on the device you haven’t backed up and the phone is at least booting into Recovery Mode, it’s worth knowing your options before you wipe it — our recovering deleted photos and SMS on Android guide covers what’s realistically recoverable and when it isn’t.

Factory Reset: Weigh It First

✔ Good idea when

Everything is backed up to your Samsung/Google account, the loop is clearly software (started after an update or new app), and cache wiping didn’t help

✘ Hold off when

There’s unsynced data you need, the phone has visible damage, or the loop is tied to a known widespread update bug (see below) — a reset won’t fix a bug in the update itself

Fix 7: Rule Out Physical or Liquid Damage

Samsung puts this check ahead of every software step on its own support page, and it matters: no software fix will resolve a boot loop caused by physical damage. Look for cracks, bent or corroded charging-port pins, and check the Liquid Damage Indicator inside the SIM tray — it should be solid white or white with pink/purple X marks. If it’s showing solid pink, purple, or red, the device has been exposed to moisture, and every fix above should be treated as a low-probability long shot. At that point, go straight to a service center rather than repeating software steps.

When It’s a Known Samsung Bug, Not Your Phone

If your loop started right after installing a Samsung-issued update, you may not be dealing with a one-off fault at all. This has happened at a wider scale more than once:

February 2026: Samsung’s February security patch triggered boot loops on a number of Galaxy S22 and S22 Ultra devices, with some users also reporting overheating and freezing after installing it. Factory resets and standard recovery-mode steps didn’t consistently fix it, though a handful of affected users found relief by manually updating the One UI Home app through the Galaxy Store first.
2024–2025: The One UI 6.1.1 and, separately, One UI 7.0 rollouts each produced widespread boot-loop reports on the S22 series on Samsung’s own community forums, serious enough that some users pursued formal complaints.
2023: Samsung publicly acknowledged a bootloop issue on older Galaxy devices (reports centered on the S10, Note 10, and S10e) traced to a SmartThings app update, and advised affected users to contact support.

If you can, check Samsung’s community forums or a quick search for your exact model plus the update month before you burn hours on cache wipes and resets — if it’s a known rollout bug, the real fix is usually a follow-up patch, not anything you do locally.

How I Tested These Fixes

I ran through the software-side fixes on a Galaxy device, working down the same order listed above, and cross-checked every button combo and menu label against Samsung’s current US support documentation rather than relying on older guides — Samsung has quietly changed some of these steps (the Recovery Mode cable requirement above is one example) between One UI generations, and a lot of “how to fix a Samsung boot loop” content still online describes button combos that no longer match newer phones. The Smart Switch Emergency Recovery process was the flakiest part of the whole workflow in practice: it silently failed on a first attempt before completing on a retry, which lines up with what other users report on Samsung’s own forums. If you hit the same thing, don’t assume the tool is broken — just repeat it.

DIY vs. Professional Repair: What It Actually Costs

Every fix above costs nothing but time. Once you’re past them and the phone is still looping, here’s roughly what the next steps look like — treat these as general ranges, since exact pricing varies by country, model, and whether you’re still under warranty or have Samsung Care+.

Path	Typical Cost	Best For
DIY software fixes (this guide)	Free	No visible damage, loop tied to an app or update
Samsung service center, in-warranty or Care+	Often a small service fee or free	Confirmed hardware fault, phone still covered
Out-of-warranty board-level repair	Roughly $150–$350+, model-dependent	Liquid damage, dead motherboard, out of warranty
Replace the phone	Varies by model	Repair quote approaches a meaningful share of a new device

Note: several users on Samsung’s own community forums have reported out-of-warranty motherboard repair quotes landing close to a quarter of the phone’s original price — get the quote in writing and ask specifically what failed before authorizing anything.

When to Stop and Call a Professional

I’d stop trying software fixes and get the phone looked at professionally if: the LDI shows liquid exposure, there’s visible screen or body damage, the phone gets noticeably hot while looping, it won’t hold a charge at all, or you’ve been through every step above with no change. The Samsung Members app’s built-in diagnostics (Support → Phone Diagnostics → Test All) is worth running first if the phone boots even briefly — it can flag a failing battery, charging port, or sensor before you spend more time on software steps that were never going to fix a hardware fault.

Find a Samsung Service Center →

Watch: A Visual Walkthrough

If you’d rather watch the button combos than read them, this walkthrough from WorldofTech covers the same recovery-mode and reset process visually:

FAQ

Will a Samsung boot loop fix itself if I just wait?

Occasionally, if the loop was triggered by a temporary overheating or update hiccup, letting the battery fully drain and then charging it for 15+ minutes before a force restart can clear it. It’s not reliable enough to count on, but it’s harmless to try alongside the fixes above.

Does a boot loop mean I’ve lost my photos and data?

No — a boot loop is almost always a problem stopping the phone from starting, not damage to the storage chip itself. Your data typically survives force restarts, Safe Mode, and cache wipes untouched. It’s only the factory reset and Emergency Software Recovery steps that erase data, which is why they’re positioned last in this guide.

Why does my Galaxy keep restarting right after a software update?

Usually either a corrupted or partial update install, or — as happened with the S22 series in February 2026 and with One UI 6.1.1 before it — a bug in the update itself affecting a batch of devices. Wiping the cache partition resolves the first case; the second needs a follow-up patch from Samsung.

Can I fix a Samsung boot loop without a computer?

Force restart, Safe Mode, and cache wiping all work with just the phone. Only the Smart Switch software update check and Emergency Software Recovery steps need a Mac or Windows PC.

Is a boot loop covered under Samsung warranty?

If it’s caused by a manufacturing or software defect and the phone shows no physical or liquid damage, it’s generally covered while under standard warranty or Samsung Care+. A service center inspection determines the actual cause before coverage is confirmed — this isn’t something to assume either way.

What’s the difference between wipe cache partition and factory reset?

Wipe Cache Partition clears temporary system files only — your photos, apps, and settings stay intact. Factory Reset erases everything and reinstalls the OS from scratch. Always try the cache wipe first.

Conclusion

Most Samsung Galaxy boot loop cases clear up in the first two or three steps here — a force restart or a Safe Mode boot resolves the majority without touching a single file. Work down the list in order, don’t jump straight to a factory reset out of frustration, and check for LDI or physical damage before you assume it’s a software problem at all. If you land on the last step, that’s not a failure on your part — some boot loops genuinely are hardware faults or Samsung-side update bugs, and a service center diagnosis is the right next move rather than more resets.