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
- Bootloader unlockYes, one command
- Waiting periodNone
- Data wipeYes, when unlocking
- Image to patchinit_boot.imgboot.img on Phone (1) and Phone (2)
- Updates with rootYes (A/B slots)
- Firmware sourceCommunity archiveNo official download page
Rooting a Nothing Phone: the whole job
- Step 1 · 5 minutesUnlock the bootloader
- Step 2 · 10 minutesGet the image for your build
- Step 3 · 2 minutesPatch the image in the Magisk app
- Step 4 · 2 minutesFlash the patched image
- Step 5 · 2 minutesFinish setup and check root
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.
-
Phone (4b)
SuperContra· Snapdragon 6 Gen 4Checked in official firmware: SuperContra_B4.1-260703-1843 (how)Launched withAndroid 16Patchinit_boot.img -
Phone (4a), Phone (4a) Pro
Frogger, FroggerPro· Snapdragon 7s Gen 4 / 7 Gen 4Checked in official firmware: FroggerPro_B4.1-260323-1635 (Phone (4a) Pro) (how)Launched withAndroid 16Patchinit_boot.img -
Phone (3)
Metroid· Snapdragon 8s Gen 4Checked in official firmware: Metroid_B4.1-260814-1733 (how)Launched withAndroid 15Patchinit_boot.img -
Phone (3a), Phone (3a) Pro
Asteroids, AsteroidsPro· Snapdragon 7s Gen 3Checked in official firmware: Asteroids_B4.1-260810-1153 (Phone (3a)) (how)Launched withAndroid 15Patchinit_boot.img -
Phone (3a) Lite
Galaxian· MediaTek Dimensity 7300 ProLaunched withAndroid 15Patchinit_boot.img -
CMF Phone (2) Pro
Galaga· MediaTek Dimensity 7300 ProChecked in official firmware: Galaga_V3.2-250507-1139 (how)Launched withAndroid 15Patchinit_boot.img -
Phone (2a), Phone (2a) Plus
Pacman, PacmanPro· MediaTek Dimensity 7200 Pro / 7350 ProLaunched withAndroid 14Patchinit_boot.img -
CMF Phone (1)
Tetris· MediaTek Dimensity 7300Checked in official firmware: Tetris_U2.6-240910-1735 (how)Launched withAndroid 14Patchinit_boot.img -
Phone (2)
Pong· Snapdragon 8+ Gen 1Noinit_bootpartition despite launching with Android 13.Checked in official firmware: Pong_V3.2-250708-2227 (how)Launched withAndroid 13Patchboot.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 12Patchboot.img
No match. Run magiskboot extract payload.bin: it extracts init_boot.img when the phone has one, otherwise boot.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.
| Model | Official package | init_boot partition | Ramdisk in boot.img | Patch |
|---|---|---|---|---|
| Phone (4b) | SuperContra_B4.1-260703-1843 Android 16 | Yes | — | init_boot.img |
| Phone (4a) Pro | FroggerPro_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) Pro | Galaga_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 | No | Yes | boot.img |
| Phone (1) | Spacewar_U2.6-241031-1818 Android 14 | No | Yes | boot.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):
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.
-
Unlock the bootloader
5 minutes- Open Settings → About phone, tap the build number seven times, then in System → Developer options turn on OEM unlocking and USB debugging.
- 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 unlockSome guides add
fastboot flashing unlock_critical. Magisk does not need it, and the LineageOS and Nothing archive guides leave it out. -
Get the image for your build
10 minutesNothing 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-bootarchive whose build tag matches your phone exactly. If you have the update zip instead, extract the image from itspayload.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 -
Patch the image in the Magisk app
2 minutesCopy
init_boot.imgto 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 -
Flash the patched image
2 minutesReboot 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 -
Finish setup and check root
2 minutesOpen 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
- 1Restore ImagesMagisk → Uninstall. Don't reboot
- 2Install the updateDo not restart
- 3Install to Inactive SlotMagisk app → Install
- 4Reboot from MagiskNew build, still rooted
Nothing phones have A/B slots. Turn off automatic system updates, then for each update:
- In the Magisk app tap Uninstall → Restore Images. Do not reboot.
- Install the Nothing OS update, but do not restart.
- 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
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.
- Magisk installation guide (topjohnwu)
- Magisk tools: magiskboot extract (topjohnwu)
- Magisk OTA installation guide (topjohnwu)
- Nothing archive: devices, codenames and launch builds (community)
- Nothing archive: firmware images and partitions (community)
- Nothing archive: unlocking, rooting and restoring stock (community)
- Nothing Phone (2) install guide (LineageOS)
- Nothing terms of sale (Nothing)
- payload-dumper-go (ssut)
- Play Integrity verdicts (Android Developers)
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