Repository navigation
omamobile-device-husky 0.1.8: the radio partitions for tools/nv-backup - #449
Conversation
The Pixel 8 Pro's descriptor had no NV_PARTS, so tools/nv-backup refused it. Now NV_PARTS is efs, efs_backup, modem_userdata, persist, modem_a and modem_b (each found once by PARTNAME) in both copies of the descriptor, and NV_BACKUP_EXTRA is devinfo plus trusty_persist and trusty_userdata: Trusty's storage, which only Android's storageproxyd writes, so a --check that reports them different says Android's storage proxy ran. Ran `tools/nv-backup -d husky --check` on my 8 Pro against my backup of 2026-11-03: the six NV partitions, trusty_persist and trusty_userdata are the same (devinfo differs, as expected). That backup was taken after the phone had last booted GrapheneOS; nothing since then, the AoC and Trusty work on slot B included, changed them.
|
@Somnius thank you, this is just what I asked for. I checked both lists against I'll merge this first of your husky package PRs, as 0.1.8. #453 also bumps device-husky to 0.1.8, so it will take the next free version when it lands. I'll sort that out at merge, so there's nothing for you to do here. |
…up, and #456's notes (#509) From the review of #456: - device.conf (and the package's copy): NV_BACKUP_EXTRA adds trusty_persist and trusty_userdata next to devinfo, as husky's package does since #449, so tools/nv-backup --check shows when Android has written Trusty's storage. - NOTES.md: trusty_userdata in the list of per-phone partitions, and the provenance row for the new value. - BRINGUP-M2.md: don't use Suspend in M2.7 until husky's U6; linux-omarchy-mobile#206 spelled out; tools/phone-smoke's report from the M2.6 root (test 18). - ufs-probe.dtso: "If the board file's bootargs change". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch's changes to the package (the hang marker start, the sound card found by its driver name, no aoc.bin write to an AoC that already runs) were 0.1.8 here too. Both ended up on the same number after the merge, so they are 0.1.9 now. Signed-off-by: Lef <me@lefteros.com>
derekross#449) NV_PARTS lists the 8 Pro's radio and calibration partitions for tools/nv-backup, as on the 7 Pro, the Pixel 7 and the 9a, all found by PARTNAME and none on husky's UFS_RW allowlist. NV_BACKUP_EXTRA adds devinfo, trusty_persist and trusty_userdata, which --check only reports.
…up, and derekross#456's notes (derekross#509) From the review of derekross#456: - device.conf (and the package's copy): NV_BACKUP_EXTRA adds trusty_persist and trusty_userdata next to devinfo, as husky's package does since derekross#449, so tools/nv-backup --check shows when Android has written Trusty's storage. - NOTES.md: trusty_userdata in the list of per-phone partitions, and the provenance row for the new value. - BRINGUP-M2.md: don't use Suspend in M2.7 until husky's U6; linux-omarchy-mobile#206 spelled out; tools/phone-smoke's report from the M2.6 root (test 18). - ufs-probe.dtso: "If the board file's bootargs change". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Derek asked for this on #1:
device/husky/device.confhad noNV_PARTS, sotools/nv-backuprefused the 8 Pro. This adds them, the same six as the 7 Pro, the 7 Pro's Pixel 7 and the 9a (efs efs_backup modem_userdata persist modem_a modem_b), in both copies of the descriptor, with the package at 0.1.8.I also put
devinfo,trusty_persistandtrusty_userdatainNV_BACKUP_EXTRA. The two Trusty partitions are what Android'sstorageproxydwrites, so if a--checkever reports them different, Android's storage proxy has run on that phone. Say if you'd rather keep the list to what #407 and #418 have and I'll drop them.What I ran on my 8 Pro (USB, slot B, Omarchy):
tools/nv-backup -d husky --checkagainst my backup of 2026-11-03. The six NV partitions,trusty_persistandtrusty_userdataare the same,devinfodiffers as expected.tools/pr-checkpasses. That backup was taken after the phone had last booted GrapheneOS (on slot A, after slot B ran out of boot retries on 2026-11-01); the NV partitions andtrusty_persistdiffer between my backups from before and after that boot, so Android did write them then. Since the 11-03 backup nothing changed them, with all the AoC and Trusty work on slot B in between.