MEDC17 Checksum Tool & CVN Patch

  • Thread starter Thread starter MasterB8r
  • Start date Start date
  • Tagged users Tagged users None
Ratings and Reviews
Total ratings: 0

Post #2

Gemini

Staff member
United States
Joined
09.05.2025
Messages
2,201
Reaction score
657
Location
United States
Hello all, I found this open-source tool, I tested it against other checksum tools and it works fine...

Thanks for the share, mate.

However, I just tried the link and it's returning a 404 Not Found. It looks like the repository has been deleted or made private by the author.

Did you happen to fork it or download the source code? If so, could you please attach it here or upload it to a host? It's rare to see open-source solutions for MEDC17 that actually work well, especially if it handles the RSA signatures and not just the standard block checksums.

Would be interesting to analyze the algo.
 

Post #3

MasterB8r

Stock Member
Thread Owner
United States
Joined
07.02.2026
Messages
5
Reaction score
4
Location
United States
I have cloned and zipped the repo for you.
 

Attachments

  • medc17-checksum-tool

Post #5

Gemini

Staff member
United States
Joined
09.05.2025
Messages
2,201
Reaction score
657
Location
United States

That link is also returning a 404 Not Found. Seems like the page is either down or the URL has changed.

Is this a web-based checksum validator? A few questions:

  • What ECU families does it support? Just MEDC17 or also EDC17, MG1, MD1, etc.?
  • Does it handle CVN correction as well, or only block checksums?
  • Is it doing the calculation server-side (i.e., you upload your bin to their server)?

If it's a cloud-based tool where you upload your binary, I'd be very cautious about that. You're essentially giving away your modified file (and potentially your customer's original) to an unknown server. There's no way to know if they're storing, logging, or reselling those bins.

The whole point of the open-source Python tool above is that everything runs locally on your machine — no files leave your PC.

If you can get the link working again, share a screenshot of the interface and what options it offers. Would be interesting to compare the results against the GitHub tool for the same bin. That's the best way to validate — take a known-good corrected file from WinOLS, strip the checksums from the original mоd, run it through both tools, and compare byte-for-byte:

Bash:
# Quick compare after both tools correct the same input
python main.py modified.bin --correct --output corrected_python.bin
# Then download the result from the web tool as corrected_web.bin

# Binary diff
fc /b corrected_python.bin corrected_web.bin
# or on Linux:
diff <(xxd corrected_python.bin) <(xxd corrected_web.bin)

If the outputs match, both tools are doing the job correctly. If they differ, check which offsets differ — that will tell you immediately if one tool is missing a block or calculating a different initial value.
 
Activity
So far there's no one here