Why verify firmware hashes?
A mismatched hash can mean a truncated download or a tampered package. Flashing bad firmware can soft-brick a device.
Firmware checksum verifier
Answer first
This GSMSharing tool computes MD5 and SHA-256 of a firmware package before flashing.
The selected file stays on the technician PC. Nothing is uploaded to GSMSharing.
Expected-hash comparison is described in the initial HTML even before a file is chosen.
| File Name: | Firmware checksum verifier |
|---|---|
| Flashing Tool Required: | Use after verifying the package, then flash with the OEM tool |
| Download Requirement: | No upload. Hashing runs in the browser after the HTML page loads |
Compute MD5 and SHA-256 of a firmware package in your browser before flashing. Files stay on your PC — nothing is uploaded to GSMSharing.
← All tools · Flash tools · USB drivers · Firmware files
- File
- —
- Size
- —
- MD5
- —
- SHA-256
- —
- Compare
- —
Checksum FAQ
Is my firmware uploaded?
No. Hashing runs locally with the Web Crypto API and a local MD5 implementation in this page.