Unbrick a Nexus 7 (2013) Wi-Fi or Mobile

Updated 8 November 2026 · Standard formula, shown below

This guide helps recover a Nexus 7 (2013) that is stuck at the Google logo, caught in a boot loop, or unable to start Android after a failed update or ROM flash. It covers the Wi-Fi model (flo) and mobile model (deb); the safest route is to identify the exact model, then restore its matching factory image. A factory restore erases user data, and hardware failure cannot be fixed with software.

What You’ll Need

A Windows, macOS, or Linux computer and a reliable USB data cable.
Android Platform Tools, including adb and fastboot, downloaded from the official Android developer site.
The official factory image specifically for Nexus 7 (2013) Wi-Fi (flo) or mobile/LTE (deb), obtained from Google’s factory-image archive if available. Read its included instructions.
Enough battery charge to avoid shutdown during recovery. If the tablet will not charge or power on, resolve that first.
Optional: a micro-USB OTG adapter and compatible USB keyboard if you need to navigate recovery but the touchscreen does not work.

Factory images and recovery operations can erase all local files. If data matters, stop before unlocking the bootloader or flashing, and consult a qualified repair service; unlocking normally wipes the tablet, and a non-booting device may not permit data recovery.

Step-by-Step

Identify the exact device. Check the rear label, original packaging, or the product name shown in the bootloader. The Wi-Fi model is flo; the mobile/LTE model is deb. Do not choose based only on the tablet’s appearance. A wrong image can prevent booting and may affect radio-related components.
Charge and inspect the connection. Charge the tablet for at least 30 minutes with a known-good charger. Use a data-capable cable, connect directly to the computer rather than a hub, and try another USB port if the computer does not detect it.
Install Platform Tools. Extract the download to a simple folder. Open a terminal or command prompt in that folder. On Windows, use the included command prompt or PowerShell; on macOS or Linux, use Terminal. Keep the factory-image files in a separate folder and extract them as directed by their archive instructions.
Enter the bootloader. Turn the tablet off. Hold Volume Down and press Power until the bootloader screen appears. Use the volume buttons to move and Power to select. If the tablet is already frozen, hold Power for about 10 seconds to force a restart, then try again.
Check that fastboot can see it. Connect the tablet and run fastboot devices. A device serial should appear. If the list is empty, do not continue: troubleshoot the cable, port, driver, or computer setup first. On Windows, install or correct the USB driver using a trusted, device-appropriate source; avoid random driver bundles.
Choose a recovery approach. If the bootloader screen reports that it is locked, and Android will not start, Google’s factory-image instructions may require unlocking it. Unlocking erases user data. If you can still enter Android and have USB debugging enabled, back up accessible files first. To unlock, use the bootloader’s on-screen confirmation flow and the documented fastboot flashing unlock command if supported. Older devices may use fastboot oem unlock. Follow the exact instructions for this device and stop if the command is rejected; do not guess or use an unofficial bypass.
Flash the matching factory image. Read the archive’s README before running anything. Confirm that every image and script belongs to your model code. The official archive commonly includes a flash-all script; run it from the extracted image folder as instructed. If doing the commands manually, follow Google’s documented order and use only files supplied for your exact model. Do not mix images from different releases or use a deb image on flo, or vice versa.
Watch the process without disconnecting. Keep the cable connected and the computer awake. Wait for every command to finish and for the script to report completion. Do not close the terminal or unplug the tablet during a write. If an error appears, record the full text and stop rather than repeatedly rerunning different flash commands.
Restart and allow the first boot. Use the bootloader’s Start option or the documented reboot command. The first startup after a factory restore can take several minutes. Leave it connected to power and wait before deciding it is still stuck. Complete Android setup only after the welcome screen appears.

Common Mistakes

Flashing flo on deb, or the reverse. Verify the model code before extracting or running the image.
Using an OTA update package as if it were a factory image. They are different packages with different installation requirements.
Starting a flash with a locked bootloader or assuming an unlock will preserve files. Unlocking wipes data.
Unplugging during flashing, using a charge-only cable, or running commands from the wrong folder.
Mixing individual partition files from different releases, or using a script downloaded from an unknown forum.

Tips

Download tools and images from official sources, verify the model code and archive contents, and keep a copy of any important files before making changes.
Use the factory image’s included instructions rather than relying on a generic command list; filenames and supported commands can vary by release.
If Android still starts, back up photos and documents before attempting recovery. A factory restore returns software to a clean state but does not repair damaged storage, a worn battery, or a broken USB port.
After recovery, install system updates offered by Android and restore apps gradually. If boot loops return immediately, suspect a hardware fault or an incompatible modification rather than repeating flashes indefinitely.

Troubleshooting

Bootloader will not open: Hold Power until the tablet shuts down or restarts, then press and hold Volume Down while pressing Power. Try charging first if buttons seem unresponsive. A failed power or volume button may require repair.

fastboot devices shows nothing: Change the cable and USB port, avoid hubs, and check drivers on Windows. Confirm the bootloader screen is visible. Restart the computer and try another computer if possible; do not flash until fastboot consistently detects the tablet.

Unlock command fails: Check the on-screen lock state and use the command specified by the device’s official instructions. A command may not be available in a particular bootloader state. Do not try exploit tools or unofficial lock bypasses.

Flash reports a partition or image error: Stop. Recheck the model, archive extraction, file paths, and that the image is complete. Do not substitute a file from another build. If the same error persists with the correct official package, seek experienced repair help.

It still loops after a successful flash: Give the first boot adequate time, then use the bootloader to enter recovery and try a factory reset if the official instructions recommend it. This erases data. Persistent failure, repeated write errors, or inability to charge may indicate failing storage or other hardware; software flashing is not a reliable fix for that.

Frequently Asked Questions

Can I unbrick the Nexus 7 without losing data?
Possibly, if Android still boots or files remain accessible. Unlocking the bootloader and restoring a factory image generally erase data. Do not proceed if preserving files is the priority.

How do I tell Wi-Fi and mobile models apart?
Check the model code: flo is Wi-Fi and deb is mobile/LTE. Use the exact matching factory image.

Will a factory image fix a tablet that will not power on?
No. Software restoration requires the device to power up and enter bootloader or recovery. Check charging and buttons; a dead battery, port, or board needs hardware diagnosis.

Is a black screen always a hard brick?
No. Try a known-good charger, a forced restart, and the bootloader button combination. If the computer never detects the device and no screen appears, software recovery may not be possible.

Can I use a custom ROM to recover it?
A custom ROM is not the safest first recovery step. Restore the matching official factory image first, then consider other software only if you understand the device-specific risks.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.