rom@guard:~#

Hash records

This site hosts no ROM files. It records which URL served which file, with which hash, on which date. That carries less legal risk than mirroring and is more useful than mirroring.

Records

2 records. Every one was computed from a file downloaded here — none are transcribed from an upstream page.

ROMSHA-256SizeVerified
HyperOS 3.0.302.0 (global fastboot)
peridot_global_images_OS3.0.302.0.WNPMIXM_20260527.0000.00_16.0_global_a36d19114e.tgz
0f281b61cd0fff12631d7a5760a517009a3e0683827f2428ee70f62596d31681 8.58 GB 2026-08-10
HyperOS 3.0.5.0 (global fastboot)
rothko_global_images_OS3.0.5.0.WNNMIXM_20260509.0000.00_16.0_global_3ef927a6c1.tgz
5ca20c5cedcdcbde8b681eee6f24739894f756880e362a8b50e041ae71b5d99a 8.43 GB 2026-08-10

Checking a file

macOS / Linux

shasum -a 256 <file>
# or
sha256sum <file>

Windows (PowerShell)

Get-FileHash .\<file> -Algorithm SHA256

Windows (cmd)

certutil -hashfile <file> SHA256

What this catches, and what it does not

CatchesCorruption in transit, substitution by an intermediate mirror, and files from sites impersonating the distributor. Flashing a corrupted ROM is a common way to end up in the EDL case, and this removes most of it.
Does not catchA compromised upstream. If what was distributed was already malicious when recorded, the hash matches. For a build produced by a small independent team, no third party can extend a signature chain down to your machine.

A hash secures the path from the distributor to you. Whether the distributor deserves that trust is a separate question, and not one this site can answer for you.

Record format

/data/roms.json is the data. One entry looks like this.

{
  "id": "…",
  "device": "…",
  "rom": "…",
  "file": "…",
  "source_url": "https://(upstream URL)",
  "sha256": "(64 hex)",
  "size": 0,
  "verified_at": "2026-08-09"
}

mirror_url and hashes transcribed from upstream are rejected by scripts/validate.mjs — the policy lives in code because policies get forgotten. Records are produced by scripts/hash-rom.sh, which streams the file through sha256 without storing it, so a 9 GB ROM costs no disk.