MMY 2.2.5 recorded Get the file

MMY download checksum: compute the SHA-256

A SHA-256 is a 64 character fingerprint of every byte in a file. Compute it on the file you downloaded and compare it with the record.

Download MMY

The value to compare against

channel file, served when gz is set
filemmy.2rwkt.apk
bytes20,954,528
sha256b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421
packagecom.mmyuionn.opp02
versionName2.2.5
versionCode225
minSdk24 (Android 7.0)
abiarm64-v8a only
engineCocos 3.8.2

Copy the hash rather than retyping it. Sixty-four characters is enough room for a single mistyped digit to send you looking for a problem that is not there.

macOS

Open Terminal, type shasum -a 256, then a space, then drag the file into the window so the path is filled in for you, and press return. The first column of the output is the hash. It should read b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421 for the channel file.

Windows

Open Command Prompt, move to the folder that holds the file, and run certutil -hashfile mmy.2rwkt.apk SHA256. certutil prints the hash on its own line between two header lines. Ignore the headers and compare the middle line. Spaces in that line are cosmetic; strip them before comparing if you are doing it by eye.

Linux

sha256sum mmy.2rwkt.apk prints the hash, a space, and the file name. The same command exists on most BSD systems as sha256, with the columns reversed.

On the phone

Android does not ship a hash command in the stock file manager. Several file managers from the Play Store add one: look for a menu entry named checksum, hash, or properties that lists MD5, SHA-1 and SHA-256. Use the SHA-256 line. Computing it on the phone avoids moving the file to a computer, which matters because a cable copy can itself be the thing that truncates the file.

If no file manager on the phone offers it, the computer commands above are the fallback. Copy the file off the phone first, then hash the copy, and confirm the copy is still 20,954,528 bytes before trusting the result.

What a match proves

A match proves transport integrity. The bytes you hold are the bytes measured on 10 November 2026, with nothing added, removed or reordered. That is the whole of the claim.

What a match does not prove

What a mismatch means

First check the size. A file under 20,954,528 bytes was cut off, and re-downloading is the fix. A file of exactly 21,049,457 bytes is the second file on the same host, which has its own hash on the second file page. Any other size, or the right size with the wrong hash, is a file this record does not cover.

Do not install a file whose hash you cannot match against a record you trust. The check costs a minute and the alternative is trusting a download you have no way to identify.