Home Page » News » How To » How to Recover a Stuck Android System Update Using ADB Sideload (No Root)

Recover a Stuck Android System Update Using ADB Sideload

11 min read Step‑by‑step guide to fix a frozen OTA update on Android by using ADB sideload, without rooting the device. October 10, 2026 08:00

Before you start

When an over‑the‑air (OTA) update hangs, Android can get stuck in a boot loop or remain on the splash screen. The safest way to recover without wiping user data is to reinstall the exact OTA package that failed, using the adb sideload command. This method works on most stock Android devices (Pixel, OnePlus, Samsung, etc.) that support the standard recovery mode.

What you need:

A Windows, macOS, or Linux PC with a USB‑C or micro‑USB cable.
Developer options enabled on the phone (USB debugging turned on).
ADB installed on the PC (the platform-tools package from Google).
The exact OTA zip that your device attempted to install. You can usually find it on the manufacturer’s OTA server or by searching for device_codename_OTA_version.zip.
Battery charge of at least 50 % (preferably 80 %).

If you cannot locate the original OTA file, you can often download it from sites that mirror official firmware. Verify the file’s SHA‑256 hash against the hash published by the vendor to avoid corrupted or tampered packages.

1. Enable Developer Options and Install ADB

Open Settings → About phone → tap Build number seven times. You’ll see a toast saying “You are now a developer”.
Return to the main Settings page. Open System → Developer options (on some OEM skins it may be under Advanced).
Toggle USB debugging on. Confirm the prompt that appears.
On your PC, download the latest platform-tools zip from https://developer.android.com/studio/releases/platform-tools. Extract it to a convenient folder (e.g., C:\adb or ~/adb).
Open a terminal (Command Prompt, PowerShell, or macOS/Linux terminal) and navigate to the extracted folder:

cd path/to/platform-tools

Test the connection by running:

adb devices

If you see a device ID with the word unauthorized, unlock the phone and accept the RSA fingerprint prompt.

2. Locate and Verify the Correct OTA Package

The OTA file must match the exact build your device was trying to install. Installing the wrong version can cause a signature mismatch and the recovery will refuse to flash it.

Identify your device’s codename. In a terminal run:

adb shell getprop ro.product.device

Note the Android version and build number shown in the failed update screen (e.g., Android 13, build RQ3A.211001.001).
Search for the OTA zip using the pattern codename-version.zip. Example: pixel5-13-2023-09-15.zip.
After downloading, verify the integrity:
```
sha256sum your_ota.zip
```
Compare the output with the hash published by the OEM.

3. Boot the Phone into Recovery Mode

Stock recovery supports the adb sideload command. The exact key combination varies by manufacturer.

Power off the device completely.
Press and hold the required hardware keys:
- Pixel / Nexus: Power + Volume Down → release Power when the bootloader appears, then press Volume Up to enter recovery.
- Samsung (exhaustive): Power + Volume Up + Bixby (or Power + Volume Up on newer models) → release when the Android logo appears.
- OnePlus: Power + Volume Down → when the fastboot screen appears, press Volume Up to switch to recovery.
In the recovery menu, use the volume keys to highlight Apply update from ADB and press the Power button to select it.
The screen will change to “Waiting for ADB”. At this point the device is ready to receive the OTA file.

4. Sideload the OTA Package

On the PC, ensure the device is still listed:
```
adb devices
```
You should see something like XXXXXX sideload.
Start the sideload process (replace your_ota.zip with the actual file name):
```
adb sideload your_ota.zip
```
The terminal will show a progress bar. Do not disconnect the cable or power off the phone until the transfer finishes and the recovery reports “Install OK”.
When the install completes, the recovery will automatically reboot. If it does not, select Reboot system now from the menu.

5. Verify the Update and Clean Up

After the phone restarts, check that the system version matches the OTA you just installed.

Open Settings → About phone → Android version. It should display the version you sideloaded.
If the device boots normally, the recovery was successful. You can now delete the OTA zip from the PC and the phone to free space.

6. Troubleshooting Common Issues

Device not detected or stays in “unauthorized” state

Make sure USB debugging is still enabled. Some devices disable it after a failed update.
Try a different USB cable or port. Low‑quality cables can drop the data connection during sideload.
On Windows, install the appropriate OEM USB driver (Google USB Driver for Pixel, Samsung USB driver for Galaxy, etc.).

“Signature verification failed” or “Install failed” messages

Double‑check that the OTA zip matches your exact device model and build number. Even a small version mismatch triggers this error.
Some manufacturers ship “incremental” OTA files that must be applied in order. If you skipped an earlier incremental, download the full OTA package instead.

Recovery loops back to the “Apply update from ADB” screen

This usually means the sideload completed but the system could not flash the image, often due to a corrupted zip. Re‑download the OTA and verify the checksum again.
If the device has a locked bootloader, the stock recovery may reject the OTA. In that case you need to unlock the bootloader (which wipes data) or flash a custom recovery like TWRP – but that moves the tutorial out of the “No Root” scope.

Battery dies during sideload

Never start the process with a low battery. If the phone powers off mid‑install, the system can become unbootable and you’ll need to perform a factory reset.

7. Safety Warnings

While ADB sideload does not require unlocking the bootloader, flashing an OTA that does not match your device can brick the phone, requiring a full firmware flash via fastboot.
Always back up important data before attempting any system‑level operation. You can create a quick ADB backup of apps and data with adb backup -apk -shared -all -f backup.ab, though this method has limitations on newer Android versions.
Keep the device plugged into a charger during the entire procedure to avoid accidental power loss.

When to Consider a Full Firmware Flash

If sideload repeatedly fails, or if the device ends up in a boot‑loop after the OTA install, the safest fallback is to flash the full factory image using fastboot. That process wipes user data, so only use it as a last resort after backing up everything you can.

Summary

Recovering a stuck Android system update is often as simple as re‑applying the exact OTA package via adb sideload. By preparing the right files, enabling USB debugging, and following the step‑by‑step workflow above, you can avoid a full factory reset and keep your data intact. If you encounter verification errors, double‑check the OTA version and device codename; if the device refuses to flash, a full fastboot flash may be necessary.

User Comments (0)

Add Comment

No comments added yet.

Add Comment

Your Name: *

Comment Title: *

Your E-mail: * We'll never share your email with anyone else.

Your Comment: *

Comments will not be approved to be posted if they are SPAM, abusive, off-topic, use profanity, contain a personal attack, or promote hate of any kind.