To sideload an OTA on a Pixel, you boot the phone into recovery mode, choose Apply update from ADB and send Google’s full OTA file from a computer with the adb sideload command. It installs official Pixel software without wiping your data or unlocking the bootloader, so it is the safest manual way to update or repair a Pixel. Below are the requirements, the exact steps, and what each error message means.

What OTA Sideloading Does

Google’s Full OTA Images page has a complete update package for every Pixel build. Google says applying one “has the same effect” as flashing the matching factory image, but without wiping the phone or unlocking the bootloader. Google also says sideloading a full OTA is typically easier and safer than using a factory image.

Use it when:

  • an over-the-air update failed or keeps failing;
  • a new update has not reached your phone yet and you do not want to wait;
  • the phone has a software problem and you want to reinstall the same build (recovery allows a full update to the version you already run).

This is different from sideloading apps. Installing APK files is covered in our guide to developer verification and sideloading apps.

Requirements

  • A computer with the latest SDK Platform-Tools. The latest stable release is 37.0.1 (July 2026). Recovery refuses to sideload with adb older than version 1.0.32, so do not rely on an old copy of adb.
  • A USB driver on Windows. Google says the Google USB Driver is required for adb on Windows with Google devices. macOS and Linux need no driver. See also our Windows 11 USB driver guide.
  • A good USB data cable.
  • Charge of at least 75%. This is Google’s advice before any Pixel update.
  • The correct OTA file for your exact model (see below).
  • A backup. Sideloading does not wipe the phone, but back up anything you cannot lose.

You do not need an unlocked bootloader. USB debugging is only needed if you want to start recovery with an adb command instead of the buttons.

Step 1: Download the Right OTA File

  1. Open Full OTA Images for Nexus and Pixel Devices. Read the terms and tap Acknowledge to show the downloads.
  2. Find your phone’s codename in the table below. File names start with the codename.
  3. Pick the newest build for your phone. If a month has more than one build, read the label next to each and choose the one for your region or carrier.
  4. Download the ZIP and move it into your platform-tools folder. Do not unzip it.
Pixel model Codename
Pixel 6 / 6 Pro / 6a oriole / raven / bluejay
Pixel 7 / 7 Pro / 7a panther / cheetah / lynx
Pixel Fold / Pixel Tablet felix / tangorpro
Pixel 8 / 8 Pro / 8a shiba / husky / akita
Pixel 9 / 9 Pro / 9 Pro XL / 9 Pro Fold / 9a tokay / caiman / komodo / comet / tegu
Pixel 10 / 10 Pro / 10 Pro XL / 10 Pro Fold / 10a frankel / blazer / mustang / rango / stallion
Pixel 11 / 11 Pro / 11 Pro XL / 11 Pro Fold cubs / grizzly / kodiak / yogi

Check the file (optional but smart)

Google’s download tables list a SHA-256 checksum for each file. Calculate the checksum of your download and compare the two. In Windows PowerShell (SHA-256 is the default):

Get-FileHash .\your-ota-file.zip

On macOS:

shasum -a 256 your-ota-file.zip

If the values do not match, the download is damaged. Download it again.

Step 2: Boot the Pixel into Recovery Mode

With the buttons (works even if Android does not start):

  1. Switch the phone off.
  2. On the Pixel 6 and later, press and hold Volume Down + Power for up to 30 seconds until the Fastboot mode screen appears. Older Pixels use Volume Up + Power.
  3. Press the volume keys until Recovery mode is shown, then press Power.
  4. When you see “No command”, hold Power, press Volume Up once and release both quickly. The recovery menu opens. If you hold too long and the phone restarts, try again.

With adb (phone switched on, USB debugging enabled and the computer allowed):

adb reboot recovery

Step 3: Sideload the OTA

  1. In the recovery menu, use the volume keys to highlight Apply update from ADB and press Power. The phone tells you to send the package with adb sideload <filename>.
  2. Connect the phone to the computer and open a terminal in the platform-tools folder. On Windows, type cmd in the folder’s address bar and press Enter.
  3. Check the connection:
    adb devices

    You should see a serial number followed by sideload.

  4. Start the install, using your real file name:
    adb sideload your-ota-file.zip

    In PowerShell, type .\adb instead of adb. On macOS and Linux, use ./adb if platform-tools is not in your PATH.

  5. Wait and do not touch the cable. The computer shows serving: ... (~X%). When the phone finishes, the computer prints a line starting with Total xfer, and the phone shows Install from ADB completed with status 0.
  6. Select Reboot system now. Then check Settings > About phone > Android version for the new build.

Shortcut: with the phone switched on and USB debugging allowed, adb reboot sideload reboots straight into recovery and starts sideload mode. adb reboot sideload-auto-reboot does the same and reboots after the install.

After an anti-rollback update: sideload twice

Some Pixel updates raise the bootloader’s anti-rollback version. Google names the May 2025 update for the Pixel 6, 6 Pro, 6a, 8, 8 Pro and 8a, and the May 2026 update for the Pixel 10, 10 Pro, 10 Pro XL and 10 Pro Fold. After the first successful boot on such a build, Google advises sideloading the same full OTA again and rebooting, so that both system slots hold a bootable build. Otherwise a later failed update could fall back to the old slot and leave the phone unable to boot.

Common Errors and Fixes

adb devices shows nothing

  • Make sure the phone is on the Apply update from ADB screen, not the main recovery menu.
  • Try another USB port and cable. On a Mac, unplug and replug the cable after the phone enters recovery.
  • On Windows, install or update the Google USB Driver, then reconnect.

“You need adb 1.0.32 or newer to sideload to this device”

Your adb is too old. Download the latest Platform-Tools from Google and run the command from that folder.

Progress stops at about 47% or 94%

This is normal. The percentage on the computer is only an estimate. adb’s source code calculates it as if the file will be read about 2.13 times, so it can stop near 47% or 94% even when the install succeeds. Watch the phone screen instead.

“adb: failed to read command”

adb lost contact with the phone before it received the final result. Look at the phone. If it says the install completed with status 0, the update worked. If not, return to Apply update from ADB and run the command again.

“Installation aborted” on the phone

  • Package is for product … but expected …: the file is for a different Pixel model. Download the file with your phone’s codename.
  • Update package is older than the current build … downgrade not allowed: you cannot go back to an older build with an OTA. Use the same build or a newer one.
  • Signature verification failed: the file is damaged or not an official Google package. Download it again from Google and check the SHA-256 value.

The phone still does not start

Repeat the sideload once more with the newest build. If that fails, try Google’s Update and Software Repair tool at pixelrepair.withgoogle.com (Pixel 4a and later), or see our boot loop fixes. Flashing a factory image is the last software option, and it erases all data.

Related Guides

FAQ

Does sideloading an OTA erase my Pixel?

No. Google says a full OTA image does the same job as a factory image without wiping the device. Back up anyway, in case something else goes wrong.

Do I need to unlock the bootloader to sideload an OTA?

Not for the stable full OTA images on Google’s page. For Android beta OTA images, Google’s developer site recommends unlocking the bootloader if possible, and unlocking wipes the phone.

Can I use adb sideload to downgrade my Pixel?

No. Recovery checks the build date and stops with “downgrade not allowed” if the file is older than the build on your phone. Going back to an older version needs a factory image and a full wipe, and anti-rollback updates can block some older builds completely.

What is the difference between a full OTA and a factory image?

A full OTA installs through recovery, keeps your data and works with a locked bootloader. A factory image is flashed with fastboot or Android Flash Tool, needs an unlocked bootloader and erases everything. Use the factory image only when the OTA cannot fix the phone.

https://droid-developers.com/wp-content/uploads/2026/11/sideload-ota-pixel-adb-featured-1024x538.jpghttps://droid-developers.com/wp-content/uploads/2026/11/sideload-ota-pixel-adb-featured-150x150.jpgFahim MahmudFirmwareFlash ToolsHow ToTo sideload an OTA on a Pixel, you boot the phone into recovery mode, choose Apply update from ADB and send Google's full OTA file from a computer with the adb sideload command. It installs official Pixel software without wiping your data or unlocking the bootloader, so it is...Android Help,Troubleshooting  & Stock Rom