Skip to content

device/husky: NOTES, a third phone (Samsung 128 GB, UFS 3.1, locked) - #552

Merged
derekross merged 2 commits into
derekross:mainfrom
gitColinX:husky-third-phone-notes
Nov 9, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
gitColinX:husky-third-phone-notes

Conversation

@gitColinX

@gitColinX gitColinX commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

What and why

I offered a third Pixel 8 Pro in #1, and this records it in husky's NOTES the way #209 did for the second phone. It's notes only: one new section at the top of device/husky/NOTES.md, and nothing else changes.

The section has the read-only facts so far, from adb shell getprop while the phone was booted on GrapheneOS and from fastboot getvar all on the locked bootloader:

  • Same SKU (G1MNW), storage vendor and size (Samsung 128 GB, UFS 3.1) and partition sizes as the first phone.
  • Same bootloader (ripcurrent-17.0-15681527), baseband and anti-rollback counters (all 3) as the second.
  • It starts from GrapheneOS on slot a, with slot b unbootable: the second phone's starting state with the slots swapped.
  • GrapheneOS cuts USB data while the phone is locked, so after a reboot into it, adb only comes back once the phone is unlocked.

Each fact is marked [V] with its source, or [I] where it's an inference, like the rest of the file. There's no serial, IMEI or MAC in it. Nothing has been unlocked or flashed yet; that waits on the slot A and backup questions in #1.

Device and build

  • Phone: Pixel 8 Pro (husky), locked, GrapheneOS 2026110201. No build of ours has booted on it yet.
  • Kernel release (uname -r): none on the phone (docs only)
  • Packages changed, with versions: none

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes: 466 ok, 0 failed, 7 skipped (no archlinux:latest image, no AOSP mkbootimg under SRC_DIR, no repo-add, no node)
  • tests/packages: no package touched
  • No package changed, so no version bump
  • The commit has an area prefix and a body that says why; AI help is a Co-Authored-By: trailer

On the phone

  • I ran this on my own phone, booted into this build: not applicable, docs only. The facts were read on my own phone on 2026-11-08.
  • Runbook steps passed: none yet; these are read-only stage 0 facts
  • What I did not test: nothing of ours has run on this phone, so there's no tools/phone-smoke report
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (docs only)

A third Pixel 8 Pro, offered in derekross#1, recorded as Brett suggested for
the second one: the read-only facts so far (getprop while booted and a
locked fastboot getvar all), before any unlock. Same SKU, storage
vendor and size and partition sizes as the first phone; bootloader,
baseband and starting point (GrapheneOS, one slot unbootable) as on
the second. Also noted: GrapheneOS cuts USB data while the phone is
locked, so a reboot into it needs an unlock before adb comes back.

No serial, IMEI or MACs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Welcome, @gitColinX, and thank you for the third phone and for writing it up before touching
anything. This reads well: it follows the second phone's entry, every fact has its source and
a [V] or [I], and I found no serial, IMEI or address in the diff, the commit or your comment
on #1. The values line up with the first two phones' entries (SKU, storage and partition sizes
with the first, bootloader, baseband and anti-rollback with the second).

Two small optional things, if you'd like to push again (otherwise I'm happy to merge as is):

I'll approve the CI run (first PRs wait for that) and answer your two questions on #1.

…level

From the review on derekross#552: the clause about what a GrapheneOS update
leaves behind is an inference, so it is marked [I] now, and it says
which update (2026-11-06). And a line on the patch level: GrapheneOS's
2026-11-01 is newer than the 2026-10-05 our husky images carry, which
the second phone (at 2026-10-05) never met; whether that matters once
unlocked is not known.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross
derekross merged commit 05a8b66 into derekross:main Nov 9, 2026
0 of 2 checks passed
@gitColinX

Copy link
Copy Markdown
Contributor Author

Thanks, @derekross. Both done in 9e28a77: the update clause is an [I] now and names the 11-06 update, and there's a "Patch level" line (GrapheneOS's 2026-11-01 against our 2026-10-05, with an [I] on whether it matters once unlocked).

robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…erekross#552)

* device/husky: NOTES, a third phone (Samsung 128 GB, UFS 3.1, locked)

A third Pixel 8 Pro, offered in derekross#1, recorded as Brett suggested for
the second one: the read-only facts so far (getprop while booted and a
locked fastboot getvar all), before any unlock. Same SKU, storage
vendor and size and partition sizes as the first phone; bootloader,
baseband and starting point (GrapheneOS, one slot unbootable) as on
the second. Also noted: GrapheneOS cuts USB data while the phone is
locked, so a reboot into it needs an unlock before adb comes back.

No serial, IMEI or MACs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* device/husky: NOTES, third phone: the update inference marked, patch level

From the review on derekross#552: the clause about what a GrapheneOS update
leaves behind is an inference, so it is marked [I] now, and it says
which update (2026-11-06). And a line on the patch level: GrapheneOS's
2026-11-01 is newer than the 2026-10-05 our husky images carry, which
the second phone (at 2026-10-05) never met; whether that matters once
unlocked is not known.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

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