Repository navigation
Unlock the Dot again when the bootrom step lands in locked fastboot - #109
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bboe
force-pushed
the
locked-fastboot-fallthrough
branch
from
October 9, 2026 08:09
89f21c7 to
ee00a1c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A resumed run that comes back in v1's own locked fastboot now unlocks the Dot again and writes the chain from v2.0.0's recovery, rather than failing on the first flash a locked bootloader refuses. Reported from Windows, where a rerun recovered by hand. The sliced route to /system also stops announcing itself.
The failure
🤖 Generated with Claude Code