What this is ------------ Which boot image to patch with Magisk depends on the partitions a phone has. On October 27, 2026 (UTC) magiskguide.com read that directly from 79 official update packages (40 Xiaomi, Redmi and POCO, 31 Google Pixel, 8 Nothing and CMF; some packages serve more than one model) instead of relying on launch Android versions. The .txt files are the unedited terminal output: each command is shown after "$ " and followed by exactly what it printed. Lines starting with "# " are our labels. Nothing was downloaded in full and nothing was flashed. No firmware image is published here, only logs and hashes. How it works ------------ An A/B update package is a zip that stores payload.bin uncompressed. payload.bin starts with a header and a manifest (update_metadata.proto) that lists every partition, its size and its SHA-256. payload_parts.py (included, standard-library Python) uses HTTP range requests to read only the zip's directory, the package metadata (META-INF/com/android/metadata, which names the device and build) and that manifest: a few hundred kilobytes instead of several gigabytes. With --extract it also rebuilds one partition (boot or vendor_boot) from the package's full-update operations, fetching only that partition's data, and compares the result with the SHA-256 in the manifest. Every extraction in *-images.txt printed "sha256 matches the hash in the update manifest". The extracted images were then opened with magiskboot built from the Magisk v31.1 source (see ../2026-10-27-magisk-v31.1-patch/README.txt). Before using it, we checked the tool against a full download: on the Pixel 7 package CP3A.261005.002.A1 it listed init_boot as 8,388,608 bytes and extracted an init_boot.img with SHA-256 fa9bcf68d5659bbf0513e3838e2ba763b94c675017ba19e633bfce4873c3e5b5, identical to the one magiskboot extracted from the complete 3.1 GB package (../2026-10-27-magisk-v31.1-pixel7-init-boot/1-extract-init-boot.txt). The tool gained retries, package metadata and the manifest hash check during the day. The partition lists in xiaomi.txt, pixel.txt and nothing.txt come from earlier versions of the same script; that part of its output is unchanged. All extractions (*-images.txt) were made with the included final version. Sources of the packages ----------------------- - Google Pixel: Google's full OTA images page, https://developers.google.com/android/ota (newest entry per device on October 27, 2026). Downloading them requires accepting Google's terms, which the site owner did; the files are for personal use and are not redistributed here. - Xiaomi, Redmi, POCO: Xiaomi's download servers. Package links come from the Xiaomi Firmware Updater tracker (github.com/XiaomiFirmwareUpdater/miui-updates-tracker, data/latest.yml), newest stable recovery ROM per model, global region where available. The tracker lists them on bigota.d.miui.com; that host served us at about 24 KB/s, so the reads were made from cdnorg.d.miui.com, Xiaomi's other download host for the same paths. Each package's metadata names the device (pre-device=...), shown in xiaomi.txt. - Nothing and CMF: full OTA packages on Google's update servers (android.googleapis.com/packages/ota-api/...), as listed in the community Nothing Archive firmware index (nothingarchive.tech/docs/firmware). Each package's metadata names the device. Not covered ----------- - OnePlus publishes no download links; the packages that community apps fetch come from a private API we did not use. - Motorola firmware is only offered through its Rescue and Smart Assistant Windows tool. - Samsung firmware is not an A/B OTA zip of this kind (it is an Odin AP tar), and Samsung phones are always patched as a whole AP file. Reading the results ------------------- "init_boot present: yes" means the phone has an init_boot partition, and Magisk patches init_boot.img (its script does so when the kernel is newer than Android 12's; we didn't check kernel versions here). Where it is "no", magiskboot unpack of boot.img shows RAMDISK_SZ: a non-zero size means boot.img holds the ramdisk; [0] means it doesn't, and *-images.txt then shows the ramdisk inside vendor_boot (exit code 3 from magiskboot unpack means a vendor_boot image; vendor_ramdisk/ lists its ramdisk fragments). Magisk's patch script handles a boot.img without a ramdisk by creating one ("No ramdisk found, create one from scratch" in scripts/boot_patch.sh), which is how the Pixel 6 is rooted; Magisk v30.3 and later can also patch vendor_boot.img. Corrections: hello@magiskguide.com