Google Pixel Bricked After Update? Data Recovery Options
Our founder and lead technician, Joseph Montanti, handles cases personally.
A Google Pixel stuck at the logo after an update is failing during Android startup. Its files may still be present, and getting the original phone to boot and unlock can make them accessible again. A Pixel 6 that bricked after a factory reset needs a different approach, because a completed reset erases the old local data.
On this page
Pixel 6 bricked after a factory reset
Google acknowledged a factory-reset problem affecting Pixel 6, 6 Pro and 6a devices in 2024. Its Pixel Support notice advised owners of working phones to wait at least 15 minutes after a system update before resetting. In its July 19, 2024 update, Google said it had identified a solution and directed affected owners to Pixel support by phone or chat. For a phone already bricked by that incident, ask support which options are currently available for that device.
If the reset completed, recover your old photos, recordings and other information from copies made before it. Google explains that a factory reset removes the phone's data. Getting Android running again afterward allows setup and restoration of backups; it does not bring back the previous local files.
If the reset failed partway through and you never saw confirmation that it completed, leave the phone in its current state for recovery advice. Another wipe would change that state further. Check Google Photos and your Google Account backups from a different device while the phone remains off.
Check how far the Pixel can start
Do not charge a wet or visibly damaged Pixel, and disconnect one that becomes unusually hot. End a copying attempt if the phone repeatedly disconnects, freezes or heats up abnormally.
For a dry, undamaged phone, a flat battery, a bad cable or a frozen screen can look like a failed update. The checks below preserve the existing files and help separate those problems from a phone that consistently fails to load Android.
- Try the appropriate power-button action. Google's frozen-screen instructions say to hold Power for about 60 seconds when the screen is on but unresponsive. For a phone that is off, Google's normal power-on check is a 5–7 second press.
- Check the charger and cable. Use a compatible, working supply and a working outlet. Google's charging guidance lists a 30 W PPS adapter or a USB Power Delivery adapter rated at least 15 W. A completely drained battery left unused for a long time can take up to 25 minutes to show a response; continued silence after that needs repair attention.
- Inspect the USB-C port. Look for moisture, debris or visible damage. Google's port instructions say to put nothing inside it. For loose debris, face the port down and gently tap the phone against your hand.
- Check Fastboot on Pixel 6 and later. With the phone off, hold Power and Volume Down together for up to 30 seconds, releasing when Fastboot appears. This opens a boot menu; it is separate from selecting a wipe or flashing software.
- Check the computer connection. Try a known-good USB data cable and another computer port. A cable that charges the phone may still lack a working data connection.
Google documents the Fastboot button sequence on its manual-reset page. Opening Fastboot or Recovery is distinct from choosing Wipe data/factory reset, the destructive command further down that procedure.
| What the Pixel shows | What is running | What to do next |
|---|---|---|
| Google logo, then repeated restarts | Startup begins but fails to finish. System software, storage or power can interrupt it. | Try Safe Mode if the startup animation appears; preserve the phone if it still loops. |
| FASTBOOT MODE | The bootloader can display its menu and communicate through its supported interface. | Keep the current firmware and lock state while choosing the recovery route. |
| Android Recovery or “No command” | The recovery environment has started; “No command” can precede its menu. | Keep away from the wipe command while files are still needed. |
| Black screen, but the phone rings | The phone is operating with a display problem. | Restore display access so you can unlock and copy files. |
| No response after the power checks | The phone has no usable startup or display response. | Have its power, display and board checked. |
To try Safe Mode, turn on the phone and hold Volume Down when the startup animation begins, keeping it held until startup finishes. Safe Mode disables downloaded apps. If the phone becomes usable there, save the files before removing apps or making other changes.
An OTA update, a factory image and a reset do different things
A full OTA package is Google's signed software-update package. Google provides full OTA images for failures to take an update and says they do not require a data wipe or an unlocked bootloader. Sideloading a compatible OTA through Recovery is different from flashing a factory image. It still writes firmware, so preserve accessible files or backups before choosing that repair.
Google's factory-image instructions explicitly erase device data. Bootloader unlocking also triggers a factory reset under Android's bootloader security rules. Entering the PIN on the lock screen and unlocking the bootloader are entirely different operations.
The Pixel Update & Software Repair tool can offer an update without a reset, as well as a reset/reinstallation route. Read which operation it proposes. When needed files exist only on the non-starting phone, get advice on preserving that copy before applying firmware changes.
Why changing the active slot can make things worse
Android's A/B update design maintains a bootable system while preparing an update. Modern Virtual A/B updates use snapshots of changing system data, then merge the changes after a successful boot. Two slot names therefore do not amount to two independent backups of your apps and photographs.
The older slot must also satisfy security checks. Google documents a concrete example: the May 2025 bootloader update for Pixel 6 and Pixel 8 families increased the rollback-protection version. An older bootloader in the inactive slot could then leave a device unbootable when fallback occurred. That model-specific rollback restriction is why “switch to the old slot” is not a general recovery instruction.
Fastboot provides boot and flashing functions; reaching its screen does not unlock credential-protected files. Ordinary ADB access also requires USB debugging and computer authorization. A PC recognizing the phone is useful, but a complete copy of private app storage is a separate access problem.
Tensor, Titan M2 and access to your files
Pixel security uses several components together. Google's Pixel 6 security explanation describes Titan M2 working with the Tensor security core to protect keys. The phone's storage holds encrypted data, and the working security system supplies the authorized route to it.
Android distinguishes data available during early startup from credential-encrypted storage, which becomes available after the user unlocks. That explains how a phone can reach a menu or lock screen while its personal files remain inaccessible. The storage chip, original security hardware, encryption information and unlock credentials all matter.
A UFS chip is the flash-storage package on these Pixels. Reading or moving that package to a donor board does not recreate the original phone's authorized access. For a damaged board, the recovery objective is to restore that original path long enough to start Android, authenticate and retrieve accessible data.
If you have forgotten the screen lock, check your existing backups and Google's supported lock-recovery options. Android's Weaver authentication system protects the secret used to unlock credential-encrypted data and limits repeated attempts. A Google Account password serves account access; it does not replace the phone's PIN for this local unlock.
| Pixel generation | Processor | Security hardware in Google's specifications |
|---|---|---|
| Pixel 6, 6 Pro, 6a | Google Tensor | Titan M2 |
| Pixel 7, 7 Pro, 7a | Tensor G2 | Titan M2 |
| Pixel 8, 8 Pro, 8a | Tensor G3 | Titan M2 |
| Pixel 9, 9 Pro, 9 Pro XL, 9a | Tensor G4 | Titan M2 |
The table follows Google's hardware specifications. Pre-Tensor Pixels also use Android security and encryption; an older model needs its own supported access method. The absence of Tensor is no reason to treat a removed storage chip as readable files.
When a non-starting Pixel needs recovery work
If the basic checks do not restore Android, the next step is to separate a software startup failure from a power, display or storage fault. A phone that never reaches Fastboot may have a firmware or hardware problem. A device that repeatedly disconnects during reading needs that fault addressed before a longer extraction attempt.
For files that have no other copy, choose a repair plan that preserves the original storage and required security components. A display fault may need a working screen for authentication. Power or board damage may require restoring the original board sufficiently to use the phone. The broader Google Pixel recovery guide covers those hardware cases.
| Fault | MDrepairs price | Work involved |
|---|---|---|
| Post-update startup failure; Fastboot works | $1,500 - $2,000 | A compatible route back to Android and authorized file access. |
| Hardware fault preventing startup | $1,500 - $2,000 | Repairing the original read and power paths. |
| Cracked screen | $1,500 - $2,000 | Restoring display access for unlocking and copying. |
| Power-management component failure | $1,500 - $2,000 | Board repair to restore the required power supplies. |
| Liquid damage | $1,500 - $2,000 | Addressing damage while preserving the original storage and security components. |
| CPU Swap (Severe Cases) | $3,500 | Complex original-hardware recovery; a UFS-only transplant cannot replace the required security path. |
At MDrepairs, the diagnostic costs $100 and is credited toward successful recovery; recovery work follows your approval of the estimate. Standard recovery is estimated at 4–6 weeks, varying with the case.
Google's Repair Mode can protect user data during supported repairs, but it requires a functioning phone to enable it. Google says storage-affecting repairs can still require erasure. If files are trapped on the device, resolve the data-recovery plan before authorizing a reset or storage replacement.
2023 Android 14 update bug on Pixel 6 and later with multiple user profiles
Google's Android 14 storage notice concerned Pixel 6 and later devices with multiple user profiles. Some affected owners lost access to media storage, while others encountered a reboot loop. The November 2023 update and Google's recovery support addressed that particular fault; an unrelated November update needs its own diagnosis.
Find the files that already have another copy
Google Photos, device backup and Recorder backup cover different information. Sign in to Google Photos from another device to check whether your recent pictures and edits were uploaded. A preview visible somewhere else is less useful than a downloadable copy of the photograph you need, so open and save the files before relying on them.
Google's Pixel backup documentation separates photos and contacts from device backups. Supported messages, settings and app data can restore during setup on another phone, but app support varies. Existing WhatsApp, Signal or other app backups follow that app's own restore process; unlocking the Pixel does not automatically export every private database.
For recordings, check Recorder on the web under the account used in the app. Google's Recorder instructions distinguish synced recordings from those kept only on the phone. When the phone becomes accessible, Recorder's sharing and backup options provide a supported way to save recordings and transcripts.
For local camera files, Documents and Downloads, unlock the working Pixel, connect a data cable, tap the USB notification and select File transfer. Google's USB transfer instructions cover that path. Copy to the computer and check that the files open; private app content needs its own export or backup feature.
Get help with data recovery
Bring your device to our Lincroft lab during opening hours, or mail it in.
How to mail your deviceThe $100 diagnostic is non-refundable once diagnostics start, and donor drives or replacement parts you approve are non-refundable once ordered, even if recovery fails.
Published by MDrepairs
MDrepairs is a data recovery and electronics repair lab in Lincroft, New Jersey. Our founder and lead technician Joseph Montanti films real cases for our YouTube channel, showing tools, repair steps and recovery outcomes.
Keep reading
- Google Pixel Dead or Bricked? Data Recovery Guide
- Motorola Stuck in Boot Loop? Stop and Recover Your Data First
- OnePlus Won't Turn On: How to Recover Your Data