[ifoknr]

A new Samsung page. It works on Samsung firmware files and never talks to a phone in Download mode; flashing stays with Odin. Download mode (PIT, drivers) is stage 2, on its own branch later.

What it does

• Open AP, BL, CP, CSC and HOME_CSC. They can be the .tar.md5 files, the folder they are in, or the zip a firmware site gives (unpacked next to it first).
• MD5: each file is checked against its MD5 line. A file that doesn't match is shown as damaged, and nothing is taken from it.
• About the firmware: model, build (PDA), bootloader binary, build date, Android version and CSC, all read from the file names.
• Firmware against the phone, read over adb from the phone in Android:
  • model;
  • bootloader binary: an older one is a Block, since the phone would refuse it with SW REV CHECK FAIL;
  • Android version;
  • CSC (region);
  • a note that CSC wipes the phone while HOME_CSC keeps the data;
  • parts that come from different firmware.
• Extract the selected images with LZ4 undone. Files are streamed, so a 9 GB super never sits in memory. The output is checked against what the LZ4 frame records: header checksum, block checksums, content size and content xxHash32. .part files are removed on failure. An extracted super can be opened in Image Tools.
• Root with Magisk:
  • builds a small tar with init_boot (or boot) and vbmeta, still LZ4, instead of the whole 8 GB AP;
  • sends it to the phone's Download folder over adb;
  • once Magisk has patched it, fetches magisk_patched-….tar and checks that its boot image carries Magisk.
• Check a Magisk file and Tar for Odin, which packs any images into a .tar.md5 with its MD5 line.

Tests

• Core (17 new, 322 in total):
  • xxHash32 against reference vectors;
  • the streaming LZ4 decoder against the existing decoder on lz4-CLI fixtures, plus damaged and cut-short frames;
  • a real Samsung-style AP made with lz4, tar -H ustar and md5sum -t;
  • MD5 failure on a damaged file;
  • an entry over 8 GiB with a base-256 size;
  • build numbers and file names;
  • firmware against the phone: same model, older binary, other model or maker, newer binary, older Android, other CSC;
  • the Magisk tar and the patched-tar check.
• Checked by hand: GNU tar reads the tars written here, the real lz4 -d accepts the SampleGen frames, and every MD5 line matches.
• E2E (screenshots.ps1, run against the sample firmware SampleGen now writes, with FakeAdb playing a Galaxy S23 Ultra):
  • all five files MD5-checked;
  • the comparison says the firmware suits the phone;
  • boot images extracted byte for byte;
  • Magisk tar built and sent, and the patched tar fetched and found to carry Magisk.

---

Generated by Claude Code