NFSU2 Checksum & Corrupted Save Fix

Edited cash in HxD and hit Unable to load profile? Drop your damaged 54,966-byte 20CM file below to inspect broken CRCs and rewrite all three 0x04C11DB7 checksums in one click.

Polynomial0x04C11DB7 (MSB)
Block A CRCOffset 0x10 (4 B)
Block B CRCOffset 0x14 (4 B)
Header CRCOffset 0x18 (0x00..0x17)
Drop your 54,966-byte NFSU2 career file or nfsu2-web .zip archive here (100% local ArrayBuffer, zero server upload)
Ready: click Load Demo Save (treav0r) to test-drive, or drop your local 20CM career file.
Loaded profileNo file loaded (54,966 B 20CM)
CRC-32 status (0x04C11DB7)A: -- | B: -- | H: --

Inside the 28-byte 20CM header

Every career file opens with a 28-byte container header traced from native writer FUN_006FCE82. Because the Header CRC at 0x18 hashes bytes 0x00..0x17, updating Block B's CRC also requires updating the Header CRC.

Byte RangeSizeField Meaning & Verification Rule
0x00 - 0x034 BASCII Magic 20CM (32 30 43 4D, written as 0x4D433032 LE by FUN_006FC226).
0x04 - 0x074 BTotal file byte length, uint32 LE (54,966 = B6 D6 00 00).
0x08 - 0x0B4 BBlock A payload length, uint32 LE (8 bytes covering [0x1C, 0x24)).
0x0C - 0x0F4 BBlock B payload length, uint32 LE (54,930 bytes covering [0x24, 0xD6B6)).
0x10 - 0x134 BCRC-32 of Block A (0xF287C0BB on standard 54,966-byte saves).
0x14 - 0x174 BCRC-32 of Block B (changes whenever cash, cars, stages, or driver name change).
0x18 - 0x1B4 BCRC-32 of Header over bytes [0x00, 0x18), computed after writing 0x10 and 0x14.

Why standard ZIP CRC-32 tools fail

Most hex editors (including HxD's built-in CRC-32 generator and Python's zlib.crc32) compute reflected LSB-first IEEE CRC-32 using reversed polynomial 0xEDB88320. Pasting that value into 0x14 and 0x18 still triggers Unable to load profile.

SPEED2.EXE instead uses a 256-entry lookup table at executable offset 0x4145E0 built for un-reflected MSB-first CRC-32 (polynomial 0x04C11DB7): it loads the first four bytes big-endian, inverts the 32-bit register on entry, shifts each subsequent byte into the low bits while XORing TABLE[r >>> 24], and inverts the register on exit.

// Verified MSB-first 20CM checksum (SPEED2.EXE 0x4145E0)
function nfsu2Crc(data, start, end) {
  if (end - start < 4) return 0;
  const first = ((data[start] << 24) | (data[start + 1] << 16)
               | (data[start + 2] << 8) | data[start + 3]) >>> 0;
  let r = ~first >>> 0;
  for (let i = start + 4; i < end; i++) {
    r = (((r << 8) | data[i]) ^ TABLE[r >>> 24]) >>> 0;
  }
  return ~r >>> 0;
}

Repairing hex-edited saves in 1 click

When you drop a save with broken checksums into the editor at the top of this page, our structural validator checks the 20CM magic, file length (54,966 bytes), and block boundaries without rejecting mismatched CRCs. The telemetry bar flags which register failed (FIX), and clicking Download Patched Save writes freshly verified uint32 LE CRCs to 0x10, 0x14, and 0x18.

Note that if a crash truncated your save to 0 bytes or overwrote the 54,966-byte payload with zeros, checksum recalculation cannot reconstruct lost car records; keep Auto-download original .bak backup enabled before testing experimental edits.

Precision turbocharger compressor housing and actuator
Like boost control curves, all three chained 20CM header CRCs must agree to the bit before SPEED2.EXE dispatches the career loader.
Black Mazda RX-8 sports coupe
Verified reference save treav0r hashes to Block A 0xF287C0BB, Block B 0x0766B512, and Header 0x43EF00E3.
Steam Deck handheld beside external Linux screen
Drop damaged PC, Steam Deck, or Android saves into the browser to rewrite all three CRCs locally.

Gamepads for Bayview street tuning

Analog triggers and Hall-effect sticks give clean throttle control for manual Drag launches, Drift hairpins, and Android or PC sessions.

8BitDo Ultimate 2C Wireless Controller

Hall-effect sticks and linear triggers with low-latency 2.4G dongle for precision Drift, Drag, and URL throttle modulation on PC and Android.

View on Amazon

GameSir Super Nova Hall-Effect Gamepad

Drift-free electromagnetic sticks, Bluetooth 5.3 for Android nfsu2-recompiled phones, and swappable ABXY layouts with charging dock.

View on Amazon

8BitDo Pro 2 Bluetooth Gamepad

Symmetrical twin-stick grip with X-Input and Android modes plus rear programmable paddles for manual gearshifts and nitrous purge.

View on Amazon

GuliKit KK3 Max Wireless Controller

TMR electromagnetic sticks and 1000 Hz wired/wireless polling for crisp counter-steering through Jackson Heights hairpins on Windows and SteamOS.

View on Amazon

Affiliate disclosure: As an Amazon Associate, nfsu2saveeditor.com earns from qualifying purchases at no added cost to you.

Checksum & save repair FAQ

Answers on 0x04C11DB7 CRC math, endianness, and GARAGE.DAT fingerprints.

Why does Block A always show 0xF287C0BB on valid saves?

Block A is an 8-byte compatibility descriptor at [0x1C, 0x24) containing tag 0x0000010D and body size 0x0000D692. Because neither value changes on standard 54,966-byte saves, its CRC stays 0xF287C0BB.

In what byte order are the three CRCs written to the header?

Although nfsu2Crc seeds its shift register big-endian from the first four payload bytes, the resulting 32-bit unsigned integer is written into header offsets 0x10, 0x14, and 0x18 in standard x86 little-endian order.

What about nfsu2-web GARAGE.DAT checksums?

Slots 6-10 in nfsu2-web use a 64-bit FNV-1a fingerprint over career bytes [36, 39266) stored at GARAGE.DAT offset 0x08. Dropping a .zip into our editor recalculates both the three 20CM CRCs and the 64-bit FNV-1a fingerprint.

Can a wrong filename also cause profile load errors?

Yes. Even with valid CRCs, the extensionless save filename must match both its parent folder name and the profile expected by the loader.