Broken & Smashed Phones: Why Encryption Makes Recovery So Hard

Written and maintained by the Desert Data Recovery lab team. · Updated July 1, 2026

When a phone is dropped, crushed, or water-damaged, the instinct is to think of it like any other broken gadget: fix the parts and get the data back. But a modern smartphone encrypts everything it stores in hardware, all the time — and that changes the entire problem. On today's phones, recovery is far less about reading the storage and far more about getting the device itself alive enough to unlock its own encryption.

A cracked screen is not data loss

First, the good news, because it's the most common case: a smashed screen is a display problem, not a data problem. The glass, the digitizer, and the panel have nothing to do with where your data lives. If the phone still powers on and you can enter your passcode — even on a phone you can barely see — the data is intact and can almost always be copied off. A broken screen alone is never a reason to think your photos are gone.

The difficulty starts when the damage reaches the logic board — the processor, the storage, and the power circuitry — and the phone will no longer turn on at all.

Why a phone isn't like a hard drive

With a failed hard drive or even a dead SSD, a lab can often bypass broken electronics entirely: image the platters on donor hardware, or read the raw flash chips directly. The data sitting on the media is the data. Phones broke that model on purpose.

Every current iPhone and virtually every modern Android phone encrypts its storage by default, in hardware. The data written to the memory is ciphertext, and the keys that turn it back into your files are not stored with the data — they live in a dedicated security chip and are released only when the right passcode is entered. Pull the memory out and read it, and you get encrypted noise.

The layers of encryption in a modern phone

• iPhone (Secure Enclave). Since the Secure Enclave was introduced, every iPhone encrypts its flash with a key derived from a hardware key fused into the processor and your passcode. The storage is cryptographically tied to that one specific device — the flash and the processor are a matched pair.
• Android (File-Based Encryption + hardware keystore). Modern Android encrypts each file with keys protected by a hardware-backed keystore — a Trusted Execution Environment or a dedicated security chip (such as Titan M or a StrongBox element). As on iPhone, the keys are bound to the hardware and unlocked by your PIN, pattern, or password.
• The passcode is part of the key. On both platforms the encryption isn't unlocked by the hardware alone — your passcode is mixed into it. That's why a locked phone with an unknown passcode is, by design, extremely difficult to get into even for the manufacturer.

Why "just do a chip-off" usually doesn't work anymore

Chip-off recovery — desoldering the memory and reading it directly — is a genuine technique, and on older, unencrypted phones it worked well. On a modern phone it usually doesn't, for one reason: the memory is paired to the phone's own processor and security chip. Reading the raw flash gives you the encrypted data, but the keys to decrypt it never leave the security chip, and that chip only cooperates inside its original device with the correct passcode. Move the flash to another board and it can't be decrypted. The chip-off succeeds; the decryption doesn't.

What recovery actually involves

Because you can't simply read the data out, recovering a dead phone is really a repair problem first. The realistic path is to fix the device itself — at the board level — until it powers on and boots normally, and then let the phone decrypt and hand over its own data the way it was designed to. That can mean:

• Board-level micro-soldering to repair damaged traces, power circuitry, or connectors after a drop or crush.
• Replacing failed components so the processor and storage can power up and communicate again.
• Careful drying and corrosion treatment on water- or liquid-damaged boards before any power is reapplied.
• NAND-level work in cases where the storage itself is damaged but the processor and security chip survive.

The goal throughout is the same: get the original hardware working together again, because that original hardware is the only thing that holds the keys.

The passcode still matters

Even a flawless repair doesn't skip the encryption. Once the phone boots, it still needs the correct passcode, PIN, or biometric to release the keys and decrypt the data — exactly as it would on any working phone. If you know your passcode, a repaired phone will unlock and give up its data normally. If the phone is locked and the passcode is genuinely lost, the hardware encryption holds, and that's the part no lab can simply switch off.

When a broken phone is genuinely unrecoverable

Honesty matters more than a sales pitch here. A phone crosses into truly unrecoverable territory when the parts that hold or unlock the keys are destroyed — a shattered processor, a dead Secure Enclave or security chip — or when the device is locked and the passcode can't be provided. In those situations the keys are simply gone, and encrypted data with no key is unrecoverable by anyone. Physical destruction of the storage cells themselves (crushed or burned memory) is the other clear-cut case. We'd rather tell you that up front than take a case we can't win.

If your phone is broken, do this

• If it still powers on, back it up immediately — even with a shattered screen, get the data off before the phone deteriorates further.
• Don't keep trying to power on a dead or wet phone. Repeated power-ups and charging a liquid-damaged board can turn a repairable fault into a destroyed one.
• Skip the rice and DIY fixes. Rice does nothing useful for corrosion, and home repairs can damage the very board that holds your keys.
• Keep your passcode. Recovery from a repaired phone almost always needs it — make sure you know it before anything else.
• Get it evaluated. Whether a dead phone is repairable enough to recover comes down to exactly what was damaged, which is what an evaluation is for.

This is the same hardware-encryption problem that shapes recovery elsewhere — see how it plays out on Apple T2 and Apple Silicon Macs and on self-encrypting drives. For the wider picture of what does and doesn't respond to recovery, read our data recovery challenges page.