If your Galaxy S22 is stuck in a boot loop, start with Safe Mode. If it still restarts, go to Recovery and wipe the cache partition, then try a factory reset only after every data-preserving step fails. Skipping that order can turn a fixable software fault into permanent data loss. This guide gives you a Galaxy S22 decision tree with safe mode, recovery, cache wipe, reset, and when to stop and escalate.
Spot the boot loop pattern and run these quick checks
A boot loop is repeated restarting before the phone reaches the lock screen. On the Galaxy S22, that can look like a logo loop, a lock-screen flash loop, a recovery loop, or a download-mode screen. The most common pattern is a logo loop.
Keep the first checks simple. Charge the battery, swap in a known-good USB-C cable and charger, and force a restart before opening Recovery or changing settings.
Common patterns to recognize
- Logo loop: Samsung logo appears, then the phone restarts again.
- Lock-screen flash loop: the lock screen appears briefly, then vanishes and the phone restarts.
- Recovery loop: the phone boots into Recovery instead of Android.
- Download-mode screen: the phone stays on the download-mode screen.
Likely causes, from most common to less common
Failed OTA updates can cause the same pattern, and an interrupted software update can trigger it as well. If an app, setting, or system file is the problem, the phone may still be recoverable without erasing data. If software steps fail repeatedly, storage or board damage becomes more likely.
Say your S22 showed a “Installing system update” screen, then restarted three times and never reached the lock screen again. That points you toward Recovery steps first, not a factory reset.
Failed update or interrupted install
- Plug the phone into a wall charger for at least 15 minutes.
- Press and hold Side + Volume Down for about 7–10 seconds to force a restart.
- If it loops again, go straight to Recovery instead of repeating the restart.
- Choose Wipe cache partition before any reset option.
Problem app, bad settings, or system corruption
- If the lock screen appears even for a moment, try Safe mode first.
- Once the phone stays up, remove the most recent app installs under Settings > Apps.
- Disable apps that were updated just before the restart problem began.
Storage or hardware failure
- Try Recovery mode and run Wipe cache partition.
- If the loop returns right after cache wipe, check whether the phone can enter Download mode.
- If Recovery and Download mode both fail, stop and arrange service.
- Do not move to a factory reset if the device cannot stay powered or cannot complete basic menu navigation.
How do I get my Galaxy S22 out of a boot loop without losing data?
Start with the least destructive path: forced restart, Safe Mode if the lock screen appears, then Recovery mode and cache wipe. Those steps can solve app faults, temporary update errors, and some system startup problems without erasing personal files. If the phone will not stay on long enough to reach those menus, stop and seek service before any reset.
Check for a brief lock-screen window
- Watch for even a short lock-screen flash during startup.
- If it appears, press and hold Side + Volume Down until the phone restarts.
- Try to reach Safe mode once the device stays awake.
- If the lock screen never appears, skip Safe Mode and move to Recovery.
Use backups only if the phone stays up
- If the phone holds on, copy files to a computer with USB cable transfer.
- Check Settings > Accounts and backup for Samsung Cloud or Google backup status.
- Finish the backup before any reset or wipe.
- If the phone drops back into the loop before the backup completes, stop.
Try safe mode if the lock screen flashes
Safe mode disables third-party apps, so it is the right branch when the phone briefly reaches the lock screen. If Safe Mode holds steady, the cause is often a rogue app rather than deeper system damage.
What to do after a successful safe-mode boot
- Open Settings > Apps.
- Remove apps installed or updated just before the restart problem started.
- Clear storage-heavy launchers, battery savers, or overlay apps first.
- Restart normally after each removal to see whether the loop is gone.
When Safe Mode points away from apps
- If the phone still restarts in Safe Mode, the issue is less likely to be a third-party app.
- Move to Recovery mode next.
- Do not keep uninstalling apps if the device cannot remain on.
- That pattern points more toward update damage or deeper system trouble.
Recovery mode and cache wipe
Recovery mode is a separate mini-OS. It can wipe cache, factory reset, and apply firmware updates. For a Galaxy S22 boot loop, Wipe cache partition is the safest recovery step because it does not delete personal data. If that fails, a factory reset becomes a last-resort software fix.
How to enter recovery mode on a Galaxy S22
- Power the phone off if possible.
- Connect a USB-C cable to a computer.
- Hold Volume Up + Side until Recovery appears.
- Use the volume keys to move and the Side key to confirm.
Why cache wipe comes before reset
- Choose Wipe cache partition.
- Confirm the selection.
- After it finishes, choose Reboot system now.
- If the loop returns, only then consider a factory reset.
When cache wipe is unlikely to help
- If Recovery itself loops, cache wipe may not be enough.
- If the phone restarts immediately after rebooting from Recovery, suspect a larger software fault.
- If the device cannot enter Recovery at all, stop data-destructive steps.
- Repeated failure after cache wipe points toward reset or service.
If an update triggered the loop
A failed OTA update can trap the Galaxy S22 in startup before Android finishes loading. That is one reason update-related boot loops often show up right after a reboot or installation bar. If the update was interrupted, repeated forced restarts usually are not helpful; switch to Recovery and work down the list instead.
Suppose the phone rebooted during an overnight update and now only shows the Samsung logo. That is the moment to stop guessing and move to cache wipe, not a blind factory reset.
What to do next
- Force restart once with Side + Volume Down for about 7–10 seconds.
- If the loop continues, enter Recovery mode.
- Run Wipe cache partition first.
- If the update still blocks startup, choose Factory reset only after backing up any data you can reach.
Why factory reset is last, not first
- Factory reset removes personal data.
- It is the right move only after cache wipe fails.
- Use it when the phone is otherwise stable enough to finish the process.
- Do not use it as a quick fix if your files are not backed up.
When does it point to hardware damage?
No display, no vibration, or no response to charging are warning signs that the problem may not be software. If Recovery and Download mode both fail, or if the phone cannot hold a charge long enough to show any menu, storage failure or board damage is on the table. At that point, repeated resets may be unhelpful.
Signs to stop at home troubleshooting
- The screen stays black even with a known-good charger.
- The phone never vibrates during forced restart.
- Recovery mode will not appear.
- Download mode also fails to appear.
When firmware reflash is the next step
- If the phone can enter Download mode but not boot Android, firmware reflash becomes a possibility.
- This is specialist-level repair, not a casual next step.
- A wrong recovery attempt can trigger an irreversible factory wipe.
- A bad flash can hard brick the phone if it is done wrong.
Galaxy s22 stuck decision table
| Symptom | Safest next action | Data-loss risk | Stop-here warning |
|---|---|---|---|
| Logo loop after a restart or update | Force restart once, then enter Recovery and run Wipe cache partition | Low for cache wipe; high if you jump to reset | Stop if the phone cannot stay on long enough to reach Recovery |
| Lock-screen flash loop | Try Safe mode first, then remove recent apps if it holds | Low | Stop if Safe mode also restarts |
| Recovery loop | Run Wipe cache partition once, then reboot | Low for cache wipe; medium to high if reset is needed | Stop if Recovery itself keeps cycling or fails to open |
| No display, no vibration, no charging response | Test a known-good charger, then try Download mode only if the phone responds | Low if you only test; high if you force reset repeatedly | Stop and seek service if the phone remains dead |
Frequently asked questions
Why is my phone stuck in a boot loop?
The usual causes are a failed update, a bad app, or system corruption that stops Android from finishing startup. On the Galaxy S22, begin with a forced restart, then Safe Mode if the lock screen appears, then Recovery and cache wipe. Do not jump straight to a factory reset.
What should I try first if my Samsung S22 keeps restarting?
Check the charger and cable, then perform a forced restart with Side + Volume Down for about 7–10 seconds. If the phone briefly reaches the lock screen, try Safe Mode next. If it does not, go directly to Recovery and clear the cache partition.
Will wiping the cache partition fix a Galaxy S22 boot loop?
It can, especially after an update or a temporary system fault, and it does not erase personal data. Choose Wipe cache partition in Recovery and reboot afterward. If the loop returns, the next step is a factory reset or service, depending on whether the phone can still hold a stable boot.
How do I enter recovery mode on a Galaxy S22?
Power the phone off, connect a USB-C cable to a computer, then hold Volume Up + Side until Recovery appears. Use the volume keys to move and the Side key to select. From there, try Wipe cache partition before any reset.
Should I factory reset my Galaxy S22 if it is stuck in a reboot loop?
Only after Safe Mode and cache wipe fail, because a factory reset removes personal data. If the phone will not stay on long enough to back up files, stop first and protect what you can. A reset is a last-resort software fix, not the starting point.