What the automatic checker verifies
The public BIN checker confirms the required 1 MiB file size, looks for the exact 032HS 0008 identity at the verified software location and runs the same compatibility logic used by the available patch packages. It does not return patched bytes and does not create a payable order just because a filename looks correct.
When the identity matches but a protected source condition is different, the result is routed to manual review instead of forcing the patch. Already-patched, partially converted and unsupported files are also refused by the automated workflow.
Current 06A906032HS 0008 products
5-Map Switching — $59
The base package adds five LDRXN maps, five LDRXNZK maps, five KFZW maps and five KFZW2 maps, plus two KRKTE sets and tachometer map indication. New duplicated calibrations are seeded from the customer’s input tune. A matching non-5120 TunerPro XDF is included after payment.
5-Map + Guarded 5120 — $88
The 5120 package contains the complete current five-map architecture plus the verified guarded 032HS 5120 core and tune-sensitive scaling transforms. It includes a separate 5120-aware XDF. DSLGRAD and DSLOFS are intentionally left unchanged because they must match the physical MAP sensor actually installed.
Prepare first, pay second
The BIN is validated and the output is generated before Stripe Checkout becomes available. If the patch cannot prove compatibility, there is no payable order. A successful prepared file remains locked until payment is verified, after which the exact BIN, package-matched XDF and customer-safe patch report become available for the paid download window.
What the patch report shows
The automatic report records the order/package, software identity, input and output SHA-256 hashes when available, XDF name/hash, calibration architecture and a high-level verification summary. It deliberately does not reveal TunedByAB’s hook addresses, memory locations, code-cave addresses, byte signatures or patch offsets.
Need another ME7.5 revision?
Do not rename a different file or try to make it resemble 032HS. Use the software-version request form with the real ECU part number and software version. Requests are used to prioritize future reverse-engineering and validation work; support is added only after the new revision receives its own guarded patch workflow.