Skip to content

omamobile-device-husky 0.1.8: the radio partitions for tools/nv-backup - #449

Merged
derekross merged 1 commit into
derekross:mainfrom
Somnius:husky-nv-parts
Nov 7, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
Somnius:husky-nv-parts

Conversation

@Somnius

@Somnius Somnius commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Derek asked for this on #1: device/husky/device.conf had no NV_PARTS, so tools/nv-backup refused 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_persist and trusty_userdata in NV_BACKUP_EXTRA. The two Trusty partitions are what Android's storageproxyd writes, so if a --check ever 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 --check against my backup of 2026-11-03. The six NV partitions, trusty_persist and trusty_userdata are the same, devinfo differs as expected. tools/pr-check passes. 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 and trusty_persist differ 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.

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.
@derekross

Copy link
Copy Markdown
Owner

@Somnius thank you, this is just what I asked for. I checked both lists against tools/nv-backup. Every name is found by PARTNAME, none is on husky's allowlist, and NV_PARTS matches the 7 Pro, the Pixel 7 and the 9a. Keeping devinfo and the two Trusty partitions in NV_BACKUP_EXTRA, where --check only reports them, is a good call, and I'm happy to keep them. They're in the set your NOTES already proposed for husky. One thing to keep in mind for later: if a husky fingerprint port ever maps storageproxyd onto trusty_persist and trusty_userdata, the way the 9a's plan does, the "only Android writes them" comment will need to change with it.

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.

@derekross
derekross merged commit e2aadbb into derekross:main Nov 7, 2026
2 checks passed
derekross pushed a commit that referenced this pull request Nov 8, 2026
…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>
Somnius added a commit to Somnius/omarchy-mobile that referenced this pull request Nov 8, 2026
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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
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.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants