Repository navigation
device-panther 0.1.6: AVB footers on boot and init_boot - #396
Conversation
Stock's vbmeta on the Pixel 7 chains boot and init_boot, as on the Pixel 7 Pro (the factory image's vbmeta.img). On a phone whose vbmeta_b is stock's, footer-less slot B images never start: libavb reads a chained partition with no footer as invalid metadata, which an unlocked bootloader doesn't let through. A second Pixel 7, with a full OTA on both slots, showed it (issue derekross#342): a black screen, no USB, and stock recovery on slot A after about 72 s. The first unit boots without footers because its vbmeta_b dates from the OS it ran before. So the descriptor gets cheetah's AVB_FOOTERS, padded to getvar's partition sizes, with stock CP3A.261005.002.A1's rollback index and security patch (its own boot and init_boot footers, matching OS_PATCH_LEVEL). The package's copy of the descriptor follows, so omamobile-boot-update writes the footers too. Rebuilt from the same kernel output, vendor_boot, vendor_kernel_boot, dtbo and dtb.img are byte for byte the same, and boot and init_boot match up to their padding and footer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, @nesmeck, and thanks to @angelrenefm for the test. The diagnosis is solid: the factory Checks: On the version: I'll merge this one first as 0.1.6, and #281 then becomes 0.1.7. Its Two small questions, neither blocking:
Thanks for turning this around within a day of the report. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks! On the installed package: I've added angelrenefm's smoke report to the second unit's bullet in NOTES ( 🤖 Generated with Claude Code |
…1.6 is derekross#396's, 0.1.7 is kept for derekross#281)
|
Thank you, @nesmeck, for the answer and the NOTES line. That settles both questions: the 0.1.7 was your local build and didn't take part in the test, and the second unit's smoke report is now in the record. The new commit touches only that line, CI is green, and the branch still merges cleanly onto Merged as 0.1.6, ahead of the other Pixel 7 pull requests (#281 becomes 0.1.7, as you've already set it). Thanks again. |
Stock's vbmeta on the Pixel 7 chains boot and init_boot, as on the Pixel 7 Pro. On a phone whose vbmeta_b is stock's, footer-less slot B images never start: a second Pixel 7 with a full OTA on both slots showed a black screen, no USB and stock recovery on slot A after about 72 s (issue derekross#342). The descriptor gets cheetah's AVB_FOOTERS, padded to getvar's partition sizes, with stock CP3A.261005.002.A1's rollback index and security patch, and the package's copy follows, so omamobile-boot-update writes the footers too. Rebuilt from the same kernel output, the other images are byte for byte the same. The footer images boot on both units (NOTES, with the second unit's smoke report).
What and why
Fixes #342. Slot B images for the Pixel 7 now carry AVB hash footers on
bootandinit_boot, as the Pixel 7 Pro's do (issue #11).vbmetaon the Pixel 7 chainsboot(rollback index location 2) andinit_boot(location 4); I checked the factory image'svbmeta.imgwithavbtool info_image. libavb reads a chained partition with no footer as invalid metadata, which an unlocked bootloader doesn't let through. So on a phone whosevbmeta_bis stock's, slot B never starts. angelrenefm's unit, with a full OTA on both slots, showed it: a black screen, no USB, and stock recovery on slot A after about 72 s.vbmeta_bdoesn't chain them.device/panther/device.confgets cheetah's three keys, with the values from the factory image's ownboot.imgandinit_boot.imgfooters. Both units run that build (CP3A.261005.002.A1) on slot A, and the values matchOS_PATCH_LEVEL:getvar partition-size:boot_bandinit_boot_b.omamobile-boot-updatewrites the footers on the phone too.device/panther/NOTES.mdrecords the finding and both units' results.The version. This is device-panther 0.1.6, and omarchy-mobile#281 is also set to ship as 0.1.6 when it merges. Whichever goes in second should be 0.1.7. Edits are allowed if you'd rather do that here.
Device and build
uname -r):7.3.0-rc6-omamobile-push1-gdb341d1e29e7;7.3.0-rc6-omamobile-push1-g4cf2c8be1705.Checks (no phone needed)
tools/pr-check upstream/mainpassestests/allpasses.tests/images-layoutcoversAVB_FOOTERS, and the package's test checks that its descriptor matchesdevice/panther/device.conf.tests/packagespassesversionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
vendor_boot,vendor_kernel_boot,dtboanddtb.imgare byte for byte the same, andbootandinit_bootmatch up to their padding and footer. Their footers carry rollback index 1791158400,security_patch2026-10-05 andos_version17, padded to 64 and 8 MiB, as stock's do.vbmeta_bnot chaining them):bin/omamobile flashof those images. It booted as before: the same kernel,systemctl is-system-runningrunning, and one retry spent.tools/phone-smokeis below.vbmeta_b, #342): his tree with 81b8d63 on top.bin/omamobile imagesprinted both footer lines, thenbin/omamobile flash. The USB gadget appeared 24 s after fastboot dropped off and stayed, bound ascdc_ncm. Before this, nothing reached USB in 72 s.tools/install-phonewith this change (angelrenefm'suserdatawas already installed);omamobile-boot-update;phone-smokeon angelrenefm's unit, which he'll post on Pixel 7 (panther): a second unit available for testing #342.userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)tools/phone-smokereportThe two
not oklines don't come from this change:omamobile-bt-addr@hci0:Nstarted for the Bluetooth connection devices of yesterday's headset test. The udev rule'shci[0-9]*also matcheshci0:N. The script refuses them ("not a controller"), so nothing changes, but the units show as failed. The rule is the same in the cheetah, raven and tegu packages; I'll send a separate fix.phone-smoke: panther
Kernel
7.3.0-rc6-omamobile-push1-gdb341d1e29e7, tools atdf53d0d, 2026-11-03T13:42Z.Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.21, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-panther 0.1.7-1, omamobile-firstboot 0.1.2-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.28-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1
🤖 Generated with Claude Code