Repository navigation
device/husky: NOTES, a third phone (Samsung 128 GB, UFS 3.1, locked) - #552
Conversation
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>
|
Welcome, @gitColinX, and thank you for the third phone and for writing it up before touching 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>
|
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). |
…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>
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 getpropwhile the phone was booted on GrapheneOS and fromfastboot getvar allon the locked bootloader:ripcurrent-17.0-15681527), baseband and anti-rollback counters (all 3) as the second.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
2026110201. No build of ours has booted on it yet.uname -r): none on the phone (docs only)Checks (no phone needed)
tools/pr-check origin/mainpassestests/allpasses: 466 ok, 0 failed, 7 skipped (noarchlinux:latestimage, no AOSP mkbootimg underSRC_DIR, norepo-add, no node)tests/packages: no package touchedversionbumpCo-Authored-By:trailerOn the phone
tools/phone-smokereportuserdata, weakens the storage guard, or reads registers from userspace (docs only)