Nothing Archive

Your ultimate source for Nothing OS firmware, stock OTA images, and comprehensive guides for Nothing & CMF by Nothing devices.

••••••••••••••••••••••

🌍 Available languages

English • Deutsch • Español • Français • हिन्दी • Italiano • 日本語 • Русский • Türkçe • 简体中文

••••••••••••••••••••••

If this project helps you, please consider starring the repository. It helps with discoverability and encourages maintenance. Thank you!

Nothing Archive is the most up-to-date Nothing OS firmware repository, offering official OTA updates, full firmware packages, and stock OTA images for Nothing and CMF by Nothing phones. All files are sourced directly from official OEM servers and archived for long-term preservation and easy access.

• Direct OTA Indexing: Tracks Nothing OS OTA update links from official servers, providing access to incremental and full updates.
• Manual Installation: Install firmware manually during staged rollouts or when updates fail using the built-in offline updater or via ADB sideload.
• Stock OTA Images: Provides unmodified images for upgrades, downgrades, and partition flashing when full packages are unavailable.
• Rooting & Unrooting Support: Provides stock boot images for Magisk, KernelSU, and Apatch, while allowing unrooting by flashing the original boot image.
• Device Recovery: Provides fastboot-flashable Nothing OS firmware to resolve boot loops, recover soft-bricked devices, and restore stock ROM.

By using this archive, users acknowledge and accept these terms:

• Authenticity: All firmware files are unaltered, unmodified, and sourced directly from the OEM.
• Flash at Your Own Risk: Installing firmware on an unlocked bootloader carries inherent risks. Follow instructions carefully to avoid bricking your device.
• Compatibility: Ensure the firmware matches your Nothing or CMF device variant before installation.
• No Warranty: This is a community-driven project, unaffiliated with Nothing. The author and contributors are not liable for bricked devices due to misuse or firmware modifications.
• Integrity: Redistribution is permitted only with proper attribution. Reselling freely available firmware is strictly prohibited.

• Releases for OTA images are tagged using the format <POST_OTA_VERSION>, as shown in the releases section.
• Region-specific releases are tagged as <POST_OTA_VERSION>-<GLO/EEA>, applicable to older Spacewar builds. GLO = Global; EEA = European Economic Area.
• Nothing OS Open Beta Test releases are denoted by OBT.
• Android Developer preview releases are tagged as 0.0.0-dev+<Device Codename>.<Incremental Date>.
• Unless stated otherwise, releases are compatible with all regional and color variants of the device.

The unmodified stock OTA image files are archived in .7z format and categorized into three groups: Boot, Firmware, and Logical.

Select your device model to access its Release Index.

Verify the integrity of downloaded files using the following commands:

sha256sum -c *-hash.sha256

certutil -hashfile <filename> SHA256

Users can also use open-source utilities like OpenHashTab.

Access detailed OTA update changelogs for each device, named after the corresponding Nothing OS build version number, below:

• Nothing Phone (1)
• Nothing Phone (2)
• Nothing Phone (2a)
• Nothing Phone (2a) Plus
• Nothing Phone (3a) / (3a) Pro
• Nothing Phone (3)
• Nothing Phone (3a) Lite

• CMF Phone (1)
• CMF Phone (2) Pro

A. Restoring Stock Partitions (For Rooted Users Only)

If your bootloader is locked, skip directly to Point B!

1. Check your current Nothing OS version:

   • Go to Settings > About phone > Tap the device banner.
   • Note down the build number.

2. Fetch stock images for your current firmware build:

   • Download the -boot-image.7z file.
   • Extract the archive to obtain .img files.

3. Identify the required partitions:

   • Qualcomm Devices: boot, init_boot vendor_boot, recovery, vbmeta
   • MediaTek Devices: init_boot, vbmeta, lk

4. Flash stock partitions in bootloader mode:

   Only modified partitions are required to be flashed. Also skip any missing partitions based on your SoC platform.

   fastboot flash boot boot.img
   fastboot flash recovery recovery.img
   fastboot flash vendor_boot vendor_boot.img
   fastboot flash vbmeta vbmeta.img
   fastboot flash init_boot init_boot.img
   fastboot flash --slot=all lk lk.img

5. Reboot to system and update via System Updater:

   • If the update fails, proceed with manual sideloading in the next section.

6. Restoring Root (Optional):

   • After updating, you may re-root by flashing a patched boot image for the updated NOS version.
   • Modules will remain intact after re-rooting.

B. Proceed with Sideloading

• Download the Correct Update Firmware File:

  • Find the correct OTA firmware file for your device from here.

• How to Select the Right File?

  • Navigate to the repository and select your device model.
  • Look for the Incremental OTA column.
  • Verify your current OS Build Number:
  • Go to: Settings > System > About Phone.
  • Tap the device banner and note the Build Number.

• Example:

  • Suppose your Phone (2) has the build number: Pong_U2.6-241016-1700
  • Assuming the latest available OTA update available being: Pong_V3.0-241226-2001
  • The corresponding update pathway would be: Pong_U2.6-241016-1700 -> Pong_V3.0-241226-2001
  • Ensure you select the correct pathway based on your device and OS version.
  • Refer to this for better clarity.

• Create the ota Folder:

  • Create a folder named ota in your device's internal storage, full path being:

    /sdcard/ota/
    

  • Move the downloaded <firmware>.zip file to this folder.

• Access the Nothing Offline OTA Updater:

  • Open the Phone app and dial:

    *#*#682#*#*
    

  • This will launch the built-in offline updater tool.
  • The UI may show NothingOfflineOtaUpdate or NOTHING BETA OTA UPDATE — both work.

• Apply the Update:

  • The updater will automatically detect the update file.
  • If not detected, manually browse and import the OTA file.
  • Tap Directly Apply OTA or Update (based on the app UI).
  • Wait for the update to complete —your device will reboot automatically.

• Note:

  • If the updater shows an unknown error, try using the "Browse" option instead of manually copying the file to the "ota" folder.
  • Full OTA firmware can be sideloaded if incremental OTA fails.
    • Full OTA cannot be used to downgrade — it can only update to the same or a higher build.
    • Unlocked bootloader users can flash full OTA via custom recoveries (e.g., OrangeFox for Phone (2)).
  • Not every release has a Full OTA file — use incrementals instead in such cases.

A. Prerequisites

• Backup your data (unlocking will erase everything).
• Install ADB & Fastboot tools – Download here.
• Install USB drivers – Google USB Drivers.
• Enable Developer Options:
  • Settings > About phone > Tap "Build number" 7 times.
• Enable USB Debugging & OEM Unlocking:
  • Settings > System > Developer options > Enable USB Debugging & OEM Unlocking.
• Remove Screen Lock/PIN/Password and Logged-in Accounts (optional but recommended)
  • Removing accounts before relocking the bootloader helps prevent Google FRP (Factory Reset Protection) lock. If FRP is triggered, the device will ask for the previously linked Google account after a factory reset. If you forget the credentials or can't access the account, you may be locked out of your device. To avoid this, it's recommended to remove all Google accounts before relocking.

B. Unlocking Process

• Connect your phone to a PC via USB.

• Open a command prompt in the platform-tools folder:

  • Windows: Shift + Right Click > Open Command Prompt/Powershell here.
  • Mac/Linux: Open Terminal and navigate to platform-tools.

• Verify device connection:

  adb devices

  If prompted, allow USB debugging on the phone.

• Reboot to bootloader:

  adb reboot bootloader

• Verify fastboot connection:

  fastboot devices

  If no device is detected, reinstall USB drivers.

• Unlock the bootloader:

  fastboot flashing unlock

• Confirm on your phone:

  • Use Volume Keys to navigate and Power Button to confirm.
  • Your device will erase all data and reboot.

C. Post-Unlock

• Set up your phone again.

• Verify bootloader status:

  Settings > System > Developer options > OEM Unlocking should be enabled.

• Bootloader is now unlocked and your device will show an Orange State warning at boot—this is normal.

A. Prerequisites

• Unlocked bootloader with USB Debugging enabled
• A PC with ADB & Fastboot
  or another Android phone with USB-OTG + ADB app (e.g. Bugjaeger)
  or a custom recovery (e.g. TWRP / OrangeFox / AOSP based recoveries)
• Basic familiarity with ADB / Fastboot
• Stock firmware matching your current build (for extracting images)
• Recommended root solutions:
  • Magisk | Installation
  • KernelSU (KSU) | Installation
  • KernelSU Next (KSUN) | Installation

B. Check Current Software Version

• On your phone, navigate to: Settings > About phone > Tap the Nothing OS banner.
• Note down the Build Number
• Example: Pong_B4.0-251119-1654
• Ignore any regional suffix like IND/EEA/TUR and so on.

C. Fetch Stock Boot / Init_boot Image

• Navigate to the release index.

• Select your device model

• Open OTA Images for your exact build

• Download the corresponding archive: *-image-boot.img.7z from release assets.

• Extract the archive and locate:

  • init_boot.img (preferred, if present)
  • boot.img (only if init_boot does not exist)

• Transfer the image to your device

  adb push init_boot.img /sdcard/Download/
  # or
  adb push boot.img /sdcard/Download/

D. Patch the Image

Magisk

• Install the latest Magisk APK on your device.
• Open Magisk → Install → Select and Patch a File.
• Choose the transferred init_boot (preferred) / boot image.
• Magisk will generate: magisk_patched-XXXXX.img

KernelSU / KernelSU Next

• Patching method is similar to that of magisk. From the KSU/KSUN manager tap on not installed > patch the init_boot.img and transfer the patched image to PC.

• Reboot to bootloader:

  adb reboot bootloader

• Flash the patched image

  fastboot flash init_boot <drag and drop patched_init_boot.img>

• Reboot to system:

  fastboot reboot

• The device should be rooted with KSU/KSUN.

A. Requirements

• Unlocked bootloader
• Root access (via Magisk/KSU/Apatch)
• Termux app (install via F-Droid or Play Store)
• Check Partition Paths:
  • Qcom devices: /dev/block/bootdevice/by-name/
  • MTK devices: /dev/block/by-name/

B. Backup Instructions

• For Qualcomm (QCom) Devices:

  • Open Termux and grant root access using:

    su

  • Copy and paste the following command in one go:

    mkdir -p /sdcard/partitions_backup
    ls -1 /dev/block/bootdevice/by-name | grep -v userdata | grep -v super | \
    while read f; do dd if=/dev/block/bootdevice/by-name/$f of=/sdcard/partitions_backup/${f}.img; done

    This will create image files of all partitions except super & userdata in the Internal Storage inside a folder named "partitions_backup".

  • [Optional] If the above command fails, try this alternative:

    mkdir -p /sdcard/partitions_backup
    for partition in /dev/block/bootdevice/by-name/*; do \
    [[ "$(basename "$partition")" != "userdata" && "$(basename "$partition")" != "super" ]] && \
    cp -f "$partition" /sdcard/partitions_backup/; done

• For MediaTek (MTK) Devices:

  • Open Termux and grant root access using:

    su

  • Copy and paste all the following commands in one go:

    mkdir -p /sdcard/partitions_backup/
    cd /sdcard/partitions_backup
    dd if=/dev/block/by-name/nvram of=/sdcard/partitions_backup/nvram.img
    dd if=/dev/block/by-name/nvdata of=/sdcard/partitions_backup/nvdata.img
    dd if=/dev/block/by-name/persist of=/sdcard/partitions_backup/persist.img
    dd if=/dev/block/by-name/nvcfg of=/sdcard/partitions_backup/nvcfg.img
    dd if=/dev/block/by-name/protect1 of=/sdcard/partitions_backup/protect1.img
    dd if=/dev/block/by-name/protect2 of=/sdcard/partitions_backup/protect2.img

C. Storing Backup

• Move the "partitions_backup" folder to your PC or secure storage.
• Do NOT share these backups! They contain unique device data like IMEI.

D. Restoring Partitions

• MTK Devices:

  fastboot flash nvram nvram.img
  fastboot flash nvdata nvdata.img
  fastboot flash nvcfg nvcfg.img
  fastboot flash persist persist.img

  Reboot to recovery mode → Perform factory reset → Reboot to system.

• QCom Devices:

  fastboot flash persist persist.img
  fastboot flash modemst1 modemst1.img
  fastboot flash modemst2 modemst2.img

  Factory reset is not mandatory in this case.

A. Preparation of Flashing Folder:

• Download the following files for your device model and firmware build and place them in a dedicated folder:

  • image-boot.7z
  • image-firmware.7z
  • image-logical.7z.001-00x
  • -hash.sha256 - This is optional but recommended if you want to verify integrity of image files and also check for missing ones.

• Install 7-Zip from here.

• Extract files:

  • Windows: Right-click → Extract to "*"
  • Bash users: 7za -y x "*.7z*"
  • In rare cases, download managers may change file extensions for split logical files. Rename image-logical.7z.001.7z, image-logical.7z.002.7z, etc., to image-logical.7z.001, image-logical.7z.002, and retry extraction.

B. Proceeding with Flashing:

• Install compatible USB drivers from here.
• Ensure that Android Bootloader Interface is visible in Device Manager when the device is in bootloader mode.
• If the extraction script was used earlier, execute it directly. Otherwise:
  • Move all extracted image files into a single folder along with the Nothing Fastboot Flasher Script.
  • Place the -hash.sha256 file in the same directory.
  • Always download the latest script to ensure hotfixes are included.
• Run the script while connected to the internet (to fetch latest platform-tools) and follow the prompts:
  • Answer the confirmation questionnaire.
  • Skip or proceed with hash checks accordingly.
  • Choose whether to wipe data: (Y/N) [Clean Flash / Downgrade = Y | Dirty Flash / Upgrade = N]
  • Choose whether to flash to both slots: (Y/N)
  • Disable Android Verified Boot: (N) [Please note that if you choose Y here, bootloader cannot be unlocked later on!]
• Verify that all partitions have been successfully flashed.
  • If successful, choose to reboot to system: (Y)
  • If errors occur, reboot to bootloader and reflash after addressing the failure. Rebooting to system without doing so might result in soft/hard bricks.

A. Prerequisites

• Remove Screen Lock/PIN/Password and Logged-in Accounts (optional but recommended).
• Clean-flash the stock ROM following Flashing Guide. Relocking the bootloader with modified partitions without flashing stock firmware may brick the device!
• Backup all data (relocking will erase everything).
• Install ADB & Fastboot tools and USB drivers if not already set up.

B. Relocking Process

• If you are in the system, reboot to bootloader:

  adb reboot bootloader

• Verify fastboot connection:

  fastboot devices

• Initiate bootloader relocking:

  fastboot flashing lock

• Confirm on your phone:

  • Use Volume Keys to navigate and Power Button to confirm.
  • The device will be formatted and reboot with a locked bootloader.

C. Post-Relock

• Set up your device again.
• The bootloader is now locked!

Special thanks to:

• luk1337: For the AOSP OTA extraction tool.
• arter97: For adapting the archive for Phone (2).
• PhatWalrus & Daniel Springer: For self-hosted runner instances.
• LukeSkyD: For early build references.
• XelXen: For project branding and design.