From 4fa87e0f0e161a06748ea103f87a065d59cfd851 Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Thu, 12 Nov 2026 08:16:22 -0500 Subject: [PATCH] omamobile-device-cheetah 0.1.52: the boot image with #403's reboot-to and #562's init reaches installed phones The Pixel 7 Pro's package carries its boot image, and release phones write it to slot B at the update. Two of the image's inputs changed since 0.1.51: initramfs/init (#562: the optional root label check, development handover and RAM rescue keys, all unset for this phone) and reboot-to.c (#403: it notes a deliberate restart). 0.1.51 was held until an image built from this tree had booted on the phone. It has, on 2026-11-12, by the path a release phone takes: the package built with boot files staged from main on the release kernel (7.3.0-rc6-omamobile-g1a9d1d4e9289) and installed with pacman. Against 0.1.51's initramfs exactly two files differ, init and reboot-to; the dtbo is the same. The hook found four of slot B's five images already there and wrote vendor_kernel_boot_b, verified, with the previous slot B saved. After a clean restart the phone booted it: system running, no failed unit, /run 0755, the root filesystem mounted without recovery, no UFS error-handler pass, the modem ONLINE, and tools/phone-smoke passing. With this the 7 Pro's packaged reboot-to is #403's too. Co-Authored-By: Claude Fable 5.2 --- packages/omamobile-device-cheetah/version | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/omamobile-device-cheetah/version b/packages/omamobile-device-cheetah/version index c892edde5..9c4d21fb3 100644 --- a/packages/omamobile-device-cheetah/version +++ b/packages/omamobile-device-cheetah/version @@ -1 +1 @@ -0.1.51 +0.1.52