Cluster report
Everything here is derived from the file and cannot be edited. The odometer in particular is shown for verification only — this tool has no code path that writes it.
ROM patch module
Executable code the cluster copies into RAM at boot. It is verified here and only ever replaced as one verbatim, version-matched block — never edited byte by byte.
Decoded fields
Every value below is read straight from your file. The badge on each field says how well its meaning is established — treat unverified as an experiment, not a setting.
Pending changes
Computed by the server from your actual file. Nothing else in the image is touched.
Compare with another dump
Load a second 2048-byte image to see exactly where the two differ. Differences in bytes this tool cannot name are listed separately — that list is how you work out what an unknown byte does: change one setting with VCDS, re-read, and compare.
Hex view
Hover or click a byte to identify it.
Keep the original dump. Writing a bad image to a cluster can cause a DEF display, a no-start immobiliser fault, or a cluster that no longer communicates.