Nothing and CMF

How to root a Nothing Phone or CMF Phone with Magisk

Nothing and CMF phones are among the easiest to root after Pixels: the bootloader unlocks with one fastboot command, there is no waiting period, and we found no regional or carrier lock. Nothing does not publish a firmware download page, so you take the image from the update package for your exact Nothing OS build.

Last updated 10 sourcesHow we check pages

Rooting a Nothing Phone: the whole job

  1. Step 1 · 5 minutesUnlock the bootloader
  2. Step 2 · 10 minutesGet the image for your build
  3. Step 3 · 2 minutesPatch the image in the Magisk app
  4. Step 4 · 2 minutesFlash the patched image
  5. Step 5 · 2 minutesFinish setup and check root
Each stage links to its full instructions below, where you can tick steps off as you go.

Find your model

Every Nothing and CMF phone uses init_boot.img except the Phone (1) and Phone (2). The Phone (2) launched with Android 13 but has no init_boot partition, so it uses boot.img.

10 of 10
  • Phone (4b)SuperContra · Snapdragon 6 Gen 4Checked in official firmware: SuperContra_B4.1-260703-1843 (how)
    Launched withAndroid 16
    Patchinit_boot.img
  • Phone (4a), Phone (4a) ProFrogger, FroggerPro · Snapdragon 7s Gen 4 / 7 Gen 4Checked in official firmware: FroggerPro_B4.1-260323-1635 (Phone (4a) Pro) (how)
    Launched withAndroid 16
    Patchinit_boot.img
  • Phone (3)Metroid · Snapdragon 8s Gen 4Checked in official firmware: Metroid_B4.1-260814-1733 (how)
    Launched withAndroid 15
    Patchinit_boot.img
  • Phone (3a), Phone (3a) ProAsteroids, AsteroidsPro · Snapdragon 7s Gen 3Checked in official firmware: Asteroids_B4.1-260810-1153 (Phone (3a)) (how)
    Launched withAndroid 15
    Patchinit_boot.img
  • Phone (3a) LiteGalaxian · MediaTek Dimensity 7300 Pro
    Launched withAndroid 15
    Patchinit_boot.img
  • CMF Phone (2) ProGalaga · MediaTek Dimensity 7300 ProChecked in official firmware: Galaga_V3.2-250507-1139 (how)
    Launched withAndroid 15
    Patchinit_boot.img
  • Phone (2a), Phone (2a) PlusPacman, PacmanPro · MediaTek Dimensity 7200 Pro / 7350 Pro
    Launched withAndroid 14
    Patchinit_boot.img
  • CMF Phone (1)Tetris · MediaTek Dimensity 7300Checked in official firmware: Tetris_U2.6-240910-1735 (how)
    Launched withAndroid 14
    Patchinit_boot.img
  • Phone (2)Pong · Snapdragon 8+ Gen 1No init_boot partition despite launching with Android 13.Checked in official firmware: Pong_V3.2-250708-2227 (how)
    Launched withAndroid 13
    Patchboot.img
  • Phone (1)Spacewar · Snapdragon 778G+End of life on Nothing OS 3.2.Checked in official firmware: Spacewar_U2.6-241031-1818 (how)
    Launched withAndroid 12
    Patchboot.img

Codenames, launch builds and partition lists are from the community-maintained Nothing firmware archive, which reconstructs images from Nothing's official update packages. Chipsets are from Nothing's product pages and launch coverage.

What we found in the official firmware

We read the partition list of each phone's official full update, straight from the file on Google's update servers that Nothing uses, without downloading the whole package. The package's own fingerprint (post-build) confirms which phone and build it is. Links come from the community Nothing Archive index. Checked October 27, 2026.

ModelOfficial packageinit_boot partitionRamdisk in boot.imgPatch
Phone (4b)SuperContra_B4.1-260703-1843
Android 16
Yes—init_boot.img
Phone (4a) ProFroggerPro_B4.1-260323-1635
Android 16
Yes—init_boot.img
Phone (3)Metroid_B4.1-260814-1733
Android 16
Yes—init_boot.img
Phone (3a)Asteroids_B4.1-260810-1153
Android 16
Yes—init_boot.img
CMF Phone (2) ProGalaga_V3.2-250507-1139
Android 15
Yes—init_boot.img
CMF Phone (1)Tetris_U2.6-240910-1735
Android 14
Yes—init_boot.img
Phone (2)Pong_V3.2-250708-2227
Android 15
NoYesboot.img
Phone (1)Spacewar_U2.6-241031-1818
Android 14
NoYesboot.img

Every result matches the model finder above. We couldn't find a full package on Google's servers for the Phone (4a), Phone (3a) Pro, Phone (3a) Lite or Phone (2a), so those rows rely on their launch Android version. For the Phone (1) and Phone (2), which have no init_boot, we also extracted boot.img and opened it with Magisk's own tool: both hold a ramdisk, so boot.img is the right image (output). The complete output for all eight phones, and the tool we used: nothing.txt. Here is the Phone (3):

Phone (3) official update: package fingerprint and partition list
# Metroid, Nothing OS 4.1, build Metroid_B4.1-260814-1733 (full OTA, link from the Nothing Archive firmware index) $python3 payload_parts.py https://android.googleapis.com/packages/ota-api/package/1825643456d6973c5ea22aff7c29d871cc071c04.zip ota-type=AB post-build=Nothing/Metroid/Metroid:16/BQ2A.250721.001-BP2A.250605.031.A3/2608141733:user/release-keys|Nothing/MetroidEEA/Metroid:16/BQ2A.250721.001-BP2A.250605.031.A3/2608141733:user/release-keys|Nothing/MetroidIND/Metroid:16/BQ2A.250721.001-BP2A.250605.031.A3/2608141733:user/release-keys|Nothing/MetroidJPN/Metroid:16/BQ2A.250721.001-BP2A.250605.031.A3/2608141733:user/release-keys|Nothing/MetroidTUR/Metroid:16/BQ2A.250721.001-BP2A.250605.031.A3/2608141733:user/release-keys post-security-patch-level=2026-08-01 pre-device=Metroid package size: 7305756246 bytes; payload.bin: 7305747538 bytes, format version 2, manifest 268062 bytes 41 partitions: abl 958464 aop 335872 aop_config 24576 bluetooth 372736 boot 100663296 cpucp 241664 cpucp_dtb 16384 devcfg 57344 dsp 67108864 dtbo 50331648 featenabler 106496 hyp 1667072 imagefv 32768 init_boot 8388608 keymaster 458752 modem 173076480 multiimgoem 16384 multiimgqti 12288 odm 259624960 product 2399854592 pvmfw 1048576 qupfw 65536 recovery 104857600 shrm 151552 soccp_dcd 16384 soccp_debug 147456 system 1148342272 system_dlkm 7622656 system_ext 695418880 tz 4218880 uefi 2797568 uefisecapp 204800 vbmeta 8192 vbmeta_system 4096 vbmeta_vendor 4096 vendor 4489609216 vendor_boot 100663296 vendor_dlkm 57806848 xbl 1175552 xbl_config 282624 xbl_ramdump 847872 init_boot present: yes | boot present: yes | vendor_boot present: yes

Lines 1 to 50 of the unedited output. Full log · how it was made

Before you start

You will need

  • A computer with Google's SDK Platform-Tools.
  • Your exact Nothing OS build from Settings → About phone. The image you patch must come from this build; a different build causes bootloops.
  • A backup. Unlocking erases the phone.
  • The Magisk app from the official GitHub release.

What you give up

  • HD streaming on Snapdragon models. Widevine drops from L1 to L3 while the bootloader is unlocked, so Netflix and similar apps stream in lower resolution.
  • Strong Play Integrity. An unlocked bootloader fails the device verdict on Android 13 and later. See Play Integrity and root.
  • Possibly warranty repairs. Nothing's terms exclude damage from modifications and let it refuse service on modified products. They do not mention unlocking specifically.

Root your Nothing Phone step by step

Each step has a Done box so you can keep your place. Your progress is saved in this browser only.

  1. Unlock the bootloader

    5 minutes
    1. Open Settings → About phone, tap the build number seven times, then in System → Developer options turn on OEM unlocking and USB debugging.
    2. Reboot to the bootloader (or power off and hold Volume Down + Power), unlock, and confirm with the volume and power keys. This erases all data. From now on the phone shows an orange warning at boot; that is normal.
    Unlock
    $adb reboot bootloader $fastboot devices $fastboot flashing unlock

    Some guides add fastboot flashing unlock_critical. Magisk does not need it, and the LineageOS and Nothing archive guides leave it out.

  2. Get the image for your build

    10 minutes

    Nothing has no public firmware page. The community Nothing archive links official update packages from Nothing's servers and offers per-build image archives; download the -image-boot archive whose build tag matches your phone exactly. If you have the update zip instead, extract the image from its payload.bin:

    Extract from payload.bin
    # with Magisk's own tool (picks init_boot or boot automatically) $magiskboot extract payload.bin # or on a computer $payload-dumper-go -p init_boot payload.bin
  3. Patch the image in the Magisk app

    2 minutes

    Copy init_boot.img to the phone. In the Magisk app tap Install → Select and Patch a File, pick it, then copy the patched file back with adb.

    Copy the patched image to the computer
    $adb pull /sdcard/Download/magisk_patched-XXXXX_YYYYY.img
  4. Flash the patched image

    2 minutes

    Reboot to the bootloader and flash the patched file to init_boot.

    Flash
    $adb reboot bootloader $fastboot flash init_boot magisk_patched-XXXXX_YYYYY.img $fastboot reboot
  5. Finish setup and check root

    2 minutes

    Open the Magisk app and accept the additional setup. A version number on the Magisk card, for example 31.1 (31100), means root works. Don't go by the App card: its Installed line shows the app's own version even when Magisk isn't running. Then use Install → Direct Install once so Magisk keeps a backup of the stock image for future updates.

Keeping root after updates

System update, keeping root

  1. 1Restore ImagesMagisk → Uninstall. Don't reboot
  2. 2Install the updateDo not restart
  3. 3Install to Inactive SlotMagisk app → Install
  4. 4Reboot from MagiskNew build, still rooted
Magisk's documented method for A/B phones. Magisk's documentation only vouches for it on Pixels; if it fails, flash the new build's patched image instead.

Nothing phones have A/B slots. Turn off automatic system updates, then for each update:

  1. In the Magisk app tap Uninstall → Restore Images. Do not reboot.
  2. Install the Nothing OS update, but do not restart.
  3. In Magisk tap Install → Install to Inactive Slot (After OTA) and reboot.

The Nothing archive notes that a rooted phone may fail to update unless the stock images are restored first. For an offline update, dial *#*#682#*#* and place the official full package in /sdcard/ota/; it only accepts Nothing-signed packages and cannot downgrade. Full steps: keeping root after an update.

If the phone does not boot

Recovery

Reboot to the bootloader (Volume Down + Power from off) and flash the untouched init_boot.img from the same build: fastboot flash init_boot init_boot.img. To return fully to stock, the Nothing archive lists the images to restore: on Snapdragon models boot, init_boot, vendor_boot, recovery and vbmeta; on MediaTek models init_boot, vbmeta and lk. Module bootloops: see fixing a Magisk bootloop.

Errors and fixes

The messages people most often hit on this brand, and what they mean.

The phone bootloops right after flashing

Almost always a wrong partition (boot instead of init_boot) or an image from a different Nothing OS build. Flash the stock image from your exact build back, then patch the right one.

The Magisk app shows Not Installed (v31.1) or Installed: N/A (v30.7)

The patched image did not load. Check the finder above for your model's image and re-patch it from your exact build.

fastboot devices shows nothing

Update Platform-Tools, try another cable and USB port, and on Windows install a fastboot driver. The phone must show the bootloader screen.

The offline update is rejected

The package does not match your phone, is not signed by Nothing, or is older than your build. Use the official full package for a newer build.

Netflix plays in SD, or a banking app refuses to open

Expected while the bootloader is unlocked: Snapdragon models fall back to Widevine L3, and the device integrity check fails.

Questions people ask

Does unlocking void the Nothing warranty?

Nothing publishes no rooting policy. Its terms of sale exclude damage from modifications and allow it to refuse service on modified products, so expect repairs caused by rooting not to be covered.

Do I patch boot.img or init_boot.img?

init_boot.img on every model except the Phone (1) and Phone (2), which use boot.img.

Is there an official firmware download?

No. Use the update package for your build, or the community Nothing archive, which links Nothing's own servers.

Can I relock the bootloader later?

Yes, with fastboot flashing lock, but only after returning every partition to stock. Locking wipes the phone.

Do I need fastboot flashing unlock_critical?

Not for Magisk. It only matters if you plan to flash low-level firmware partitions yourself.

Sources

This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.

Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.

Report a problem with this page