Flashing / Upgrading Guide for arter97's NothingMuch ROM & Kernel

Last Updated: March '25

ESSENTIAL RESOURCES:

Stock OTA Images for Flashing: Spike's Nothing & CMF Archive | OR | arter97's Ph(2) Archive.(This guide has been composed with respect to spike0en's Git repository, but you can also use arter97's repository for reference.The only difference is the categorization of images; the authenticity of the images remains the same in both cases!)

STEPS TO FLASH arter97's NOTHINGMUCH ROM:

I. Clean Installation: [PC Access is Mandatory]

Data loss is inevitable while following this procedure. Take data backups and transfer it to PC/Cloud/External Drive and be prepared!

Applicable Scenarios:
This method is valid and mandatory as well for users coming from:
- Stock ROM (unlocked Bootloader) (Rooted / Non Rooted)
- Custom ROM(s)

** Pre-Requisites: Prepation of the the Master/Repacked Flashing Folder

Make a folder in your PC.
Download the "-image-boot.7z" and "-image-firmware.7z" file for the corresponding NOS Build on which the target NM ROM release is based on. [Refer to OTA Index under Supported Models section and Click on Phone (2) from dropdown list > Click on OTA Images for corresponding NOS build) from the respective github repo as stated in resources section above and extract both of them using 7zip.
2 folders will be created after extraction named -image-boot and -image-firmware. Move all the images to the root folder and you can delete the remaining empty folders and downloaded archive files from the same location.
Download and place the flashing script in same location.
Download, extract and move the super.img from the arter97's ROM release zip to the same folder location. vbmeta.img can be ignored in this case.
[Optional] If you want to use arter kernel replace the boot image (ksu / normal) in the folder
[Optional] If you want to use Ofox recovery replace the recovery image in the folder.
The final folder contents will have : 31 .img files (including arter97's super.img) + 1 .bat/.sh flashing script based on win/linux platform.

Flashing Procedure:

Reboot to bootloader manually or from system via adb (adb reboot bootloader)
Run the flashing script
Options to select: Wipe data: Y; Flash to both slots: N; Disable verified boot: Y (Must); Flash logical partitions: Y (if prompted); Reboot to system: Y [By default the script will flash the ROM to slot-A] || Please Note that using flags "--disable-verity --disable-verification" i.e, disabling verified boot via script needs the user to format data once after it's done for the first time. Once vbmeta is patched, you can move between NM versions as long as they are on the same NOS version by just flashing the super image.
Device will reboot to recovery. Then Format data > yes > Reboot to system. After booting:- Setup and sign in from Play Store, update apps
- [Optional] Do Google system update if available and reboot
- [Optional] Setup KSU / Magisk accordingly and flash required modules in case you are rooted. [PIF and Zygisk Next (for KSU) is recommended to bypass play integrity]
- Reboot

II. Dirty flashing: [For Users on Older NM ROM builds]

It is recommended and safe to backup your data via Swiftbackup and transfer it to PC or somewhere safe where you can access it later before proceeding in case something goes wrong !!

Case 1:
The target ROM release is based on same NOS version as the existing build running on your device. You can find this info in the release changelogs.

In this case simply flash over the new super.img file via fastboot or custom recovery like OrangeFox (Choose super image > Select super slot by scrolling down > Slide > reboot)
Since Android Verified Boot is already disabled just skip flashing the vbmeta provided in the NM ROM zip file!

Case 2:
The target ROM release is based on a different NOS version w.r.t the existing build runnning on your device.

Example: Suppose the user is running a NM ROM build based on Pong-V3.0-241226-2001 and the newer build is based on Pong_V3.0-250113-1723, then we need to flash the firmware based on the newer build first before flashing the super image itself. This can be achieved by either of the two methods stated below:

A. Using OrangeFox Recovery:

- This is probably the easiest and recommended method for dirty flashing!
- Since you are coming from a previous NothingMuch build it is safe to assume that your avb (android verified boot) is disabled. In this case you can skip flashing the vbmeta image provided by arter97 in his rom zip.

Fetch the recovery flashable firmware zip file corresponding to the target NOS build version from here.
Download the target NothingMuch ROM 7z and extract the super.img from it. arter97's kernel can be optionally downloaded based on user preferences. Move everything to one folder in the internal storage for ease of access.
Reboot to OrangeFox Recovery
Flash the firmware.zip and arter97's super.img in one go. Do not reboot yet!
[Optional] Flash the respective kernel boot.img if you want to use arter97's kernel (Choose ksu/ patch the normal variant via the same version of magisk as the previous installation). Following this step is important if you were rooted earlier and wish to retain your pre-existing modules
Reboot to system
If the steps were followed properly the dirty updation will be successful!

B. Using Fastboot Flashing Script:

Note:
- Since you are coming from a previous NothingMuch build it is safe to assume that your avb (android verified boot) is disabled. In this case you can skip flashing any vbmeta.img
- Delete the vbmeta.img file from flashing folder before proceeding and ignore any prompts related to missing image for the same while executing the script.
- Never ever reboot to system until all important partitions have been flashed properly. If you get stuck somewhere, reboot to bootloader from fastbootd or fastboot but not to system and run the script again after addressing possible causes of failure or ask in support chat.

Open the fastboot repacked folder (follow steps mentioned in (I.) Clean Installation >> Pre-Requisites Section) The aim is to upgrade / flash the ota images or firmware files without wiping data including the super in one go.
It is assumed your drivers (usb and adb/fastboot) ones are properly installed. Also make it sure that Android Bootloader Interface is showing up in device manager in bootloader mode.
Run the script and choose: Wipe data: N; Flash to both slots: N ; Flash logical partitions: Y (if prompted); Reboot: Y

MISC FAQ SECTION

A. DOWNGRADING NM ROM:

- Downgrading NM versions while retaining data is only possible when the current version from which you are downgrading is based on the same NOS version build as the target version you wanna flash.
- If the NOS build versions of two are different clean flashing is the only way as a switch in NOS version in opposite order will break encryption!

B. SWITCHING BACK TO STOCK ROM

- This requires a clean flash. Make data backups accordingly!
- Its not possible to dirty flash the stock logical partitions and switch back to stock rom by retaining data from NM rom as it will also break encryption.

STEPS TO FLASH arter97 KERNEL:

Fetch the corresponding version from here
Ksu version is prepatched. Normal version is open to be patched with magisk (optional)
Flash using any kernel flashing tool like Kernel flasher (Choose slot a > flash partition image > boot) / Franco Kernel Manager or via custom recoveries like Ofox available for Phone (2)
Alternatively you can also flash via fastboot by using: fastboot flash boot_a <arter97 kernel boot.img>
For upgrading to a newer kernel version, flash over the newer one accordingly. In order to return back to the stock kernel, flash the stock boot image via fastboot, recovery or any kernel flashing tool.

Support links:

Telegram: arter97 Ph (2) Support | Nothing Telegram Community
XDA Thread: NM ROM | arter97 Kernel