Phone Stuck in Boot Loop? How to Save Your Data Without Factory Reset

Your phone keeps restarting. It shows the logo, starts to load, then crashes and does it all over again. You're panicking because everything is on that phone. Photos, messages, contacts. The common advice is factory reset. Don't do that. A factory reset wipes everything. If your data matters, there are ways to get it back without destroying it. We deal with boot loops constantly at our lab. iPhones, Samsungs, Pixels, everything. Most of the time the data is completely intact. The phone just can't get past the startup process. That's a fixable problem.

This guide covers exactly why boot loops happen on both iPhone and Android, what you can safely try at home, and when you need professional help to save your data.

What Causes a Phone Boot Loop?

A boot loop happens when your phone tries to start up, hits a problem it can't get past, crashes, and restarts automatically. Then it tries again. And again. It can loop like this for hours until the battery dies.

There are two categories: software and hardware. The fix depends entirely on which one you're dealing with.

Software Causes

Failed system update. This is the most common cause we see. An iOS or Android update gets interrupted, maybe the battery died mid-install, maybe you lost Wi-Fi, maybe the download was corrupted. Now the operating system is half-old, half-new, and the phone can't figure out which version to boot.

Corrupted operating system. Sometimes the OS just breaks. Files get corrupted. System partitions develop errors. The phone can't load critical startup files, so it crashes and restarts. This happens more on older devices running newer software that pushes the hardware to its limits.

Bad app or malware. A rogue app that runs at startup can crash the entire system. On Android this is more common because of sideloaded apps and third-party app stores. On iPhone it's rarer, but jailbroken devices are vulnerable.

Storage completely full. When your phone has zero free space, the OS can't write temporary files it needs during boot. It crashes. Restarts. Can't write temp files again. Crashes again. This is a surprisingly common boot loop trigger on iPhones because iOS doesn't warn you aggressively enough about low storage.

Hardware Causes

Failing NAND flash storage. The storage chip itself is degrading. Bad blocks are accumulating. The phone tries to read critical boot files from damaged sectors and fails. This is more common on phones that are 3 or more years old or devices that have been heavily used.

CPU or power management failure. If the processor overheats, gets damaged, or the power management IC (the chip that regulates voltage to different components) is failing, the phone can crash repeatedly during the power-hungry boot process.

Water damage. Corrosion on the logic board can cause intermittent short circuits. The phone might boot partway, hit a corroded trace, short out, and restart. This can start weeks or months after the initial water exposure as corrosion slowly spreads.

Physical damage. A hard drop can crack solder joints or break tiny connections on the logic board. If the damage is severe enough, you may be dealing with a broken phone recovery situation rather than just a boot loop. The phone might work fine until it cools down or heats up, then connections shift and the boot process fails.

iPhone Boot Loop

iPhones are locked down tight. That's great for security. Terrible for recovery options when things go wrong. We cover iPhone data recovery in depth on our dedicated page, but here's the boot loop breakdown.

Common iPhone Boot Loop Causes

Failed iOS update. Apple pushes major iOS updates (iOS 18, iOS 17) that sometimes don't play nice with older hardware. The iPhone 8, iPhone X, and iPhone 11 are the models we see most often with update-related boot loops right now. The update process gets stuck, the phone reboots, and now it's trapped in a loop because the OS is half-installed.

Jailbreak gone wrong. Jailbreaking modifies system files that Apple never intended to be touched. One bad tweak, one incompatible package, and the phone can't boot. We see this a lot with older iPhones running Checkra1n or Unc0ver exploits that were applied carelessly.

Storage full. iPhones with 64GB of storage are the worst offenders. iOS needs about 2-3GB of free space to function properly during boot. When you're at 63.8GB out of 64GB, the phone can enter a boot loop because it literally can't create the temporary files it needs to start up.

Hardware failure. The iPhone's NAND storage, Tristar/Hydra charging IC, or the CPU itself can fail. On iPhone 7 specifically, the "audio IC" issue (a design flaw where the chip loses contact with the board) can cause boot loops. On iPhone 8 and X, the NAND controller can fail, causing the phone to loop endlessly.

What Apple Will Tell You

Apple's solution is almost always a DFU restore. Connect to iTunes (or Finder on macOS Catalina and later), put the phone in DFU mode, and restore. Clean slate. Brand new software. Problem solved.

Except all your data is gone.

A DFU restore wipes everything and installs a fresh copy of iOS. If you had an iCloud backup, you can restore from that. But iCloud backups don't include everything. They skip some app data, they don't include your call history, and if your last backup was months ago, everything since then is gone. And if your phone ends up locked out with "iPhone Unavailable" after too many failed passcode entries during the chaos, that's a whole separate problem.

Apple Stores won't attempt data recovery. It's not a service they offer. Their Genius Bar solution for a boot-looping iPhone is: restore it, or buy a new one.

What a Recovery Lab Can Do

We take a different approach. Instead of wiping the phone, we figure out why it's looping and try to fix the root cause while keeping your data intact.

For software boot loops, we can sometimes access the filesystem directly through specialized tools that communicate with the phone at a lower level than iTunes. On certain iPhone models (iPhone 5s through iPhone X), the Checkm8 bootrom exploit gives us read access to the storage even when iOS won't boot. We can pull your data off without ever restoring the phone.

For hardware boot loops, we do board-level diagnosis. Thermal imaging to find shorts. Multimeter readings on power rails. Microscope inspection of solder joints. If the issue is a failed component, we replace it. If the NAND chip itself is damaged, we perform chip-off recovery, removing the storage chip and reading it directly.

Android Boot Loop

Android is more open than iOS. That openness gives you more tools to work with during a boot loop. It also means more ways to get into trouble.

Common Android Boot Loop Causes

Failed system update. Samsung, Google, OnePlus, Motorola. Every manufacturer pushes updates that can go sideways. Samsung's One UI updates are the ones we see fail most often, particularly on the Galaxy S21 and S22 series. A power loss during update is almost guaranteed to cause a boot loop.

Custom ROM or root gone wrong. Flashing a custom ROM (LineageOS, Pixel Experience, etc.) carries real risk. Wrong ROM for your model, incompatible kernel, corrupted flash. Any of these can brick the phone or put it in a loop. Rooting with Magisk is generally safer, but a bad module can still cause startup crashes.

Corrupted system partition. Android stores its OS files on a dedicated partition. If that partition gets corrupted, the boot loader can't find what it needs and the phone loops. This happens with storage degradation, power loss during writes, or bad app behavior on rooted devices.

Incompatible app. Some apps request permissions or modify system settings in ways that crash the boot process. This is especially common with automation apps, custom launchers, and anything that uses device administrator privileges.

Safe Mode: Your First Move

Before anything else, try booting into Safe Mode. Safe Mode starts Android with only the core system apps, disabling all third-party apps. If the boot loop is caused by a bad app, Safe Mode will bypass it.

The exact button combination varies by manufacturer. On Samsung phones, the method above works. On Google Pixel, it's the same. On some Motorola and OnePlus devices, you might need to hold Volume Down during the boot animation instead of at the logo. Check Google's official safe mode instructions for your specific model.

If Safe Mode works and the phone boots normally, your data is safe and the problem is a bad app. Back up everything immediately, then start removing recently installed apps one by one until the boot loop stops in normal mode.

If Safe Mode doesn't work, the problem is deeper. System-level software corruption or hardware failure.

What a Recovery Lab Can Do for Android

Android devices are generally more recoverable than iPhones. Several reasons for this.

First, many Android phones store data on eMMC or UFS chips that can be read using standard protocols when removed from the board. The data is encrypted on newer devices (Android 10+), but the encryption is often tied to the user's lock screen credentials rather than a hardware security module. That gives us more paths to decrypt.

Second, Android's recovery and bootloader modes give us more options. ADB access, fastboot commands, custom recovery environments. Even if the OS is toast, we can sometimes access the data partition through these side doors.

Third, many Android phones have removable storage (SD cards) where photos and videos might be saved. If the boot loop only affects the internal storage, the SD card data is completely unaffected.

For hardware failures, the process is similar to iPhone. Board-level diagnosis, component replacement, or chip-off extraction if needed. The success rate on Android is generally higher because we're not fighting the Secure Enclave.

Why Factory Reset Is the Wrong Answer

Every forum. Every subreddit. Every "tech support" YouTube video. The advice is always the same: factory reset. Wipe the phone and start fresh.

That advice makes sense if you don't care about your data. But you're reading this article, so you obviously do.

Here's why factory reset is the wrong move when your data matters.

It destroys all your data. A factory reset erases everything. Photos, videos, messages, contacts, app data, saved passwords, notes, health data. Gone. On modern phones with encryption, a factory reset doesn't just delete files. It destroys the encryption keys, making the data mathematically unrecoverable. There is no undo button.

It doesn't fix hardware problems. If your phone is boot-looping because of a failing NAND chip, a corroded power IC, or a cracked solder joint, a factory reset won't help. The phone will either fail to complete the reset (because the hardware can't write properly) or it will reset successfully and then boot-loop again within hours or days because the underlying hardware issue is still there.

It should be the absolute last resort. Factory reset is what you do after you've recovered your data, not before. Get your photos and messages off the phone first, then wipe it if you need to.

What a Data Recovery Lab Does Differently

The goal of a recovery lab is the opposite of a phone repair shop. A repair shop wants to make the phone work again. We want to make the data accessible. Sometimes those are the same thing. Often they're not.

Board-Level Diagnosis

We start by figuring out exactly why the phone is looping. Not guessing. Diagnosing. Thermal cameras show hot spots (short circuits). A multimeter checks voltage on every power rail. A microscope reveals cracked solder joints, corrosion, and damaged traces invisible to the naked eye.

This matters because the fix depends on the cause. A software boot loop gets a completely different treatment than a hardware one. Applying the wrong fix can make things worse.

NAND Extraction Without Wiping

On many devices, we can read the data directly from the NAND storage chip without booting the phone's operating system at all. The phone doesn't need to fully start up. We bypass the OS entirely and talk to the storage chip through debug interfaces, bootloader exploits, or by removing the chip and reading it on specialized equipment.

The critical point: the data is never wiped during this process. We're reading, not writing. Your files stay on the chip exactly as they were.

Chip-Off Recovery

When the logic board is too damaged for board-level repair, we go to chip-off. This means physically removing the NAND storage chip from the circuit board using a rework station (basically a very precise heat gun). The chip is then placed in a reader that communicates with it directly.

Chip-off is a last resort because it's destructive to the board (the phone won't work after this). But the data on the chip is preserved. For iPhones with Secure Enclave encryption, chip-off is more complicated because we need the board's secure element to decrypt. For Android devices, chip-off recovery is generally more straightforward.

Data Extracted Without Booting

The key difference between what a lab does and what you can do at home is this: we don't need the phone to boot. A boot loop means the OS can't start. That's a problem for the phone. It's not necessarily a problem for the data. With the right tools and expertise, we can access the storage without ever loading the operating system.

Think of it like a house with a jammed front door. You can't walk through the door. But a locksmith can come around the back, open a window, and carry everything out. The stuff inside the house was never in danger. The door was the problem.

Can You Fix a Boot Loop at Home?

Honest answer: sometimes. If it's a software-only issue, you might be able to fix it yourself without losing data. If it's hardware, you need a lab. Period.

Android: Safe Mode and Recovery Mode

We covered Safe Mode above. If that works, great. Back up your data and uninstall the problem app.

If Safe Mode doesn't work, you can try Android's stock Recovery Mode. This is different from a factory reset. Recovery Mode gives you a few options that might help without wiping data.

Wiping the cache partition fixes boot loops caused by corrupted temporary files about 30% of the time. It's completely safe for your data. The phone clears its cache and rebuilds it on the next boot.

If wiping cache doesn't work, don't touch "Wipe data/factory reset" in that menu. That's the nuclear option and it's irreversible.

iPhone: Recovery Mode (With Caution)

Apple's Recovery Mode is more limited. You can try a "Update" instead of a "Restore" when connected to iTunes/Finder.

The Update option works about 40% of the time for software boot loops. When it works, all your data is preserved. When it doesn't work, the only Apple-supported option left is Restore, which wipes everything. That's when you bring it to a lab instead.

When Home Fixes Won't Work

Stop trying home fixes if any of these apply:

• The phone gets extremely hot during the boot loop
• You see distorted or garbled graphics on screen
• The boot loop started after water exposure or a drop
• The phone was working fine one day and boot-looping the next with no update or app install
• Safe Mode, cache wipe, and iOS Update all failed
• The phone smells burnt or shows visible damage to the charging port

These all point to hardware failure. No amount of button-pressing or software tricks will fix a damaged component. You need someone with a microscope, a soldering iron, and experience reading phone schematics.

How Much Does Boot Loop Recovery Cost?

Phone boot loop data recovery typically costs between $300 and $1,500. The range is wide because the difficulty varies enormously depending on the device and the failure type.

At MDrepairs, we do a diagnostic first. We'll tell you exactly what's wrong, what it will cost, and what data we expect to recover before you commit. If we can't recover your data, you don't pay. That's our no-data-no-charge policy. Check our pricing page for more details.

For context, the average person has 2,000+ photos on their phone. Years of memories. The cost of recovery is a fraction of what those memories are worth. You can't re-take your kid's first birthday photos.

iPhone vs Android: Which Is Easier to Recover?

Android is generally easier to recover from a boot loop. Not always, but most of the time.

Why Android Is Usually Easier

Less encryption complexity. Android uses file-based encryption tied to the user's lock screen credentials. If we know the passcode (or the phone has no lock screen), decrypting the data after extraction is straightforward. The encryption keys are derived from credentials, not locked in a hardware security module.

More access points. Android's bootloader, fastboot mode, ADB, and download mode give us multiple ways to communicate with the phone without booting the OS. Some manufacturers (Samsung, Xiaomi) even have proprietary modes that provide low-level access.

Standardized storage chips. Most Android phones use eMMC or UFS storage chips that follow industry-standard protocols. Our chip readers can communicate with these chips using well-documented commands.

SD card fallback. Many Android phones have expandable storage. If your photos were saved to the SD card, recovery is trivial. Pull the card out and read it on a computer.

Why iPhone Is Harder

Secure Enclave. Starting with the iPhone 5s, Apple added a dedicated security processor that holds the encryption keys. Even if we remove the NAND chip and read every byte on it, we can't decrypt it without the Secure Enclave on the original logic board cooperating. The encryption is AES-256. Without the key, the data is a wall of random numbers.

No debug modes for consumers. There's no equivalent of ADB or fastboot on iPhone. Apple doesn't expose low-level access. The only exception is the Checkm8 bootrom exploit (iPhone 5s through iPhone X), which gives forensic tools like Cellebrite and GrayKey partial access. Newer iPhones (XS and later) don't have this vulnerability.

Tightly paired components. Apple pairs the NAND chip to the CPU. You can't move the chip to another board. The encryption keys are unique to that specific CPU and NAND combination.

Bottom line: boot-looping Samsung Galaxy? Excellent recovery odds. Boot-looping iPhone 13 or newer with a hardware fault? Harder, but still possible with the right lab. Get it to a specialist fast, before corrosion spreads or you accidentally wipe it.

Real Recovery in Action

We recover data from boot-looping phones every week. Here's a look at a recent recovery from our lab.

Frequently Asked Questions

Can a boot loop fix itself?

Rarely. If the boot loop is caused by a temporary glitch (like a one-time software crash), the phone might eventually boot after several cycles. But if it's been looping for more than 10-15 minutes, it's not going to fix itself. The underlying problem, whether software corruption or hardware failure, will persist until it's addressed. Letting it loop for hours just drains the battery and generates heat that can make things worse.

Will I lose my data if I enter Recovery Mode?

Not if you're careful. On Android, "Wipe cache partition" in Recovery Mode does not delete personal data. It only removes temporary system files. On iPhone, choosing "Update" in Recovery Mode reinstalls iOS without erasing data. The danger zone is "Wipe data/factory reset" on Android and "Restore" on iPhone. Those will erase everything. Read the screen carefully before you select anything.

My phone boot loops after a water spill. What should I do?

Stop trying to use it. Seriously. Power it off and don't try to charge it. Water causes corrosion that creates short circuits, and pushing power through corroded pathways kills components permanently. We go deep on this in our water damaged phone recovery guide. Don't put it in rice (that's a myth and rice dust makes things worse). Pat the outside dry, put it in a sealed bag with silica gel packets if you have them, and get it to a recovery lab as quickly as possible. Time is the enemy with water damage. Corrosion starts within hours and spreads aggressively within days.

Can I recover data from a phone that's been boot-looping for weeks?

Yes, usually. The data on the NAND chip doesn't degrade from the boot loop itself. The chip just sits there holding your files whether the phone boots or not. The concern with extended boot loops is battery drain (a completely dead battery can sometimes cause additional complications) and heat. If the phone has been running hot for days, that heat can accelerate component degradation. But the data itself is almost always fine. We've recovered data from phones that sat in drawers boot-looping for months.

Does a boot loop void my warranty?

A software boot loop doesn't void your warranty. If the boot loop is caused by a manufacturing defect or a failed official update, Apple and Samsung will typically service it under warranty. However, boot loops caused by jailbreaking, rooting, custom ROMs, physical damage, or water damage are not covered. Also, if you open the phone yourself or take it to a third-party repair shop, some manufacturers consider the warranty voided. Check your specific warranty terms.

Is boot loop recovery covered by insurance?

Phone insurance (AppleCare+, Samsung Care+, carrier insurance) typically covers device replacement, not data recovery. They'll give you a new or refurbished phone, but they won't recover data from the old one. Data recovery is a separate service. Some homeowner's or renter's insurance policies may cover data recovery under personal property protection, but that varies by policy. It's worth checking, especially for recoveries over $500.

How long does boot loop data recovery take?

Software-related recoveries typically take 1-3 business days. Board-level repairs take 3-5 business days. Chip-off recovery can take 5-10 business days because of the precision work involved. We also offer mail-in service with free shipping labels, so you can send the phone from anywhere in the US. Rush service is available for urgent cases.

Can you recover WhatsApp messages and app data from a boot-looping phone?

Yes. When we recover data from a phone's storage, we get everything that was on the device. That includes WhatsApp messages and media, Instagram DMs, text messages, call logs, notes, health data, saved passwords, and app-specific data. The recovery is comprehensive because we're accessing the raw storage, not going through the phone's interface. If it was stored on the phone, we can typically recover it.