LATEST MAJOR EDIT: Added sections "Manhole/pullout switch location data" and "Coordinates"
POST STATUS: Messy
Note that these facts and theories are based on a few hours of research and comparing files. I'm still working on this and some facts may be incorrect.
Also, please remember that I'm not an experienced hacker, I just wanted to analyze these QR codes (and share my findings) because it seems like nobody else has yet.
The facts:
The theories:
To-do list:
Manhole/pullout switch location data
Coordinates
Downloads
easy_fixed.bin
easythree_fixed.bin
easy.bin - including QR data
easythree.bin - including QR data
POST STATUS: Messy
Note that these facts and theories are based on a few hours of research and comparing files. I'm still working on this and some facts may be incorrect.
Also, please remember that I'm not an experienced hacker, I just wanted to analyze these QR codes (and share my findings) because it seems like nobody else has yet.
The facts:
- The file is always 718 bytes (722 including common QR data)
- 512 of these contain block data and locations
- Each block is encoded into a half-byte, 0-9 based on block colour (up to 1024 blocks per level - 32x32)
- Half-byte [0xA] = No block
- Each level has specific values for "locked" and "unlocked" states
- Every byte after the QR header needs to be moved 4 bits to the right (for example, [0x4C, 0x86, 0xB2] --> [0x04, 0xC8, 0x6B, 0x20]), thanks elisherer
The theories:
- The file might contain an obfuscated timestamp (pretty sure these are random values though)
- The locked/unlocked values are based on those values
- There is a byte tells the 3DS how long the level name is somewhere
To-do list:
- Fix the pictures...
Manhole/pullout switch location data
Coordinates
Downloads
easy_fixed.bin
easythree_fixed.bin
easy.bin - including QR data
easythree.bin - including QR data









