From 52a17d68c151b05197e93ae53228c4dc6af9ff11 Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Thu, 12 Nov 2026 09:42:25 -0500 Subject: [PATCH] omamobile-device-cheetah 0.1.53: reboot-to --help prints its usage on the Pixel 7 Pro too #459 made reboot-to print its usage for an option, where it used to take the option as the reboot reason and restart the phone. The other eight device packages got it with #696. The Pixel 7 Pro's waited, because its package carries the boot image, which has reboot-to in it. An image built from this tree booted on the phone on 2026-11-12, by the path a release phone takes. Against 0.1.52's initramfs exactly one file differs, usr/local/bin/reboot-to; init and the dtbo are the same. The hook found four of slot B's five images already there and wrote vendor_kernel_boot_b, verified. After a clean restart: system running, no failed unit, /run 0755, no UFS error-handler pass, the modem ONLINE, tools/phone-smoke passing. Then, on the phone with the modem up: reboot-to --help prints the usage and exits 0, -h exits 0, -z exits 2; the boot id is unchanged, no deliberate-restart note is written, and the modem stays ONLINE. 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 9c4d21fb3..a4c528cd5 100644 --- a/packages/omamobile-device-cheetah/version +++ b/packages/omamobile-device-cheetah/version @@ -1 +1 @@ -0.1.52 +0.1.53