Skip to content

device/husky: say what slot B reads on Lef's phone, and the DEVICES Boot cell wording - #488

Merged
derekross merged 2 commits into
derekross:mainfrom
Somnius:husky-docs-followup-1107
Nov 8, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
Somnius:husky-docs-followup-1107

Conversation

@Somnius

@Somnius Somnius commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

@derekross these are the two optional things from your comment on #472. The roadmap now says my slot B is still marked from the unit's last write (0x35 reads 06), what that means until my next flash (a push costs no try, a broken pushed image means fastboot by the buttons), that a flash clears the bit, and that I won't clear it by hand. The DEVICES Boot cell says "Lef's phone" instead of "this phone". Docs only, tools/pr-check passes.

…oot cell wording

Two optional points from the review of derekross#472. The roadmap now says Lef's slot B
is still marked from the local unit's last write (0x35 reads 06), what that
means until his next flash, that a flash clears the bit, and that the bit is
not cleared by hand. The DEVICES Boot cell says Lef's phone, not this phone.

Signed-off-by: Lef <me@lefteros.com>
@derekross

Copy link
Copy Markdown
Owner

@Somnius thank you for picking up both optional points so quickly. The wording
is exactly what I meant, and "Lef's phone" reads much better in the matrix.

One thing has moved since you wrote it, though. On #252 tonight you said that
since the unit was stopped you've flashed about a dozen times, that
slot-retry-count:b reads 3 after each set_active and 2 after a boot, and
that nothing marked B. A boot spending a try means slot B isn't marked any
more, so the roadmap's "is still marked … until his next flash" describes a
state that ended this afternoon. Could you make it a dated record instead?
Something like: B stayed marked (0x35 06) from the unit's last write until
the first flash after the unit was masked on 11-07; since then a boot spends
one of B's tries (3 after set_active, 2 after one boot), so the
flash-before-the-last-try routine applies. If you have one, a fastboot getvar slot-successful:b after a flash would let the notes say "cleared" from the
bootloader's own answer. And since every one of those flashes was followed by
set_active b, "a flash (which also sets B active) clears the bit" is the
exact version.

A heads-up on merging: #494 changes the 9a row right above the 8 Pro row, so
whichever of the two lands second will need a one-line resolve. I'll handle it
if it's this one.

Thanks again for keeping the record this careful.

@Somnius

Somnius commented Nov 8, 2026

Copy link
Copy Markdown
Contributor Author

Thanks, that's a better line. I rewrote it as a dated record: B stayed marked (0x35 06) until the first flash after the unit was masked on 11-07, when it read 04. Since then, about a dozen flashes that day, each followed by fastboot set_active b, gave slot-retry-count:b: 3 after set_active and 2 after one boot, so a boot spends a try. I used your wording that a flash, which also sets B active, clears the bit.

I didn't read fastboot getvar slot-successful:b after those flashes, so I wrote that "cleared" rests on the retry count and byte 0x35, not on the bootloader's own answer. I'll read it after the next flash and add it. Pushed to this branch. Fine with me if you take the one-line resolve with #494.

@derekross
derekross merged commit 7832cc9 into derekross:main Nov 8, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…oot cell wording (derekross#488)

Two optional points from the review of derekross#472, and the record of slot B on
Lef's phone. The roadmap dates the marked state: B stayed marked (0x35
read 06) from the local unit's last write until the first flash after the
unit was masked on 2026-11-07, when it read 04. Since then a boot spends
one of B's tries (retry count 3 after set_active, 2 after one boot), so
the flash-before-the-last-try routine applies. slot-successful:b was not
read after those flashes; Lef will add it after the next one. The bit is
not cleared by hand. The DEVICES Boot cell says Lef's phone, not this
phone.

Signed-off-by: Lef <me@lefteros.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