Repository navigation
Conversation
The guided installer finds the phone's factory image through device/cheetah/factory-builds.json and stops without it. This adds the Pixel 7 Pro's file with two builds, metadata only (build id, the bootloader and baseband each requires, the zip's name, size and SHA-256, its address on Google's servers): nothing of Google's is in it. CP2A.260705.006 is marked tested with 2026.11.08: that release's test install was provisioned from it (device/cheetah/NOTES.md). CP3A.261005.002.A1 is listed and not marked, so the installer won't use it until a release has been tested with its firmware. Each entry was made by tools/factory-index from the owner's own zip. For both, Google's download server answers for the address and reports the same size, and the zip's name carries the first eight digits of its SHA-256, as Google's names do. The SHA-256 could not be compared with Google's page itself, which shows its table only after its terms are acknowledged in a browser: the maintainer does that by eye before a release ships this file. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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
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.
The guided installer finds the phone's factory image through
device/cheetah/factory-builds.jsonand stops without it. This adds the Pixel 7 Pro's file with two builds, as metadata only: the build id, the bootloader and baseband each requires, the zip's name, size and SHA-256, and its address on Google's servers. Nothing of Google's is in it.device/cheetah/NOTES.md)Each entry was made by
tools/factory-index addfrom the owner's own zip.tools/factory-index checkandtests/factory-indexpass.Checked: for both, Google's download server answers for the address and reports the same size as the index, and the zip's name carries the first eight digits of its SHA-256, as Google's names do.
Not checked: the SHA-256 against Google's factory images page itself. The page shows its table only after its terms are acknowledged in a browser, so that comparison is the maintainer's to do by eye before a release ships this file. The two digests are in the file.
🤖 Generated with Claude Code