Now that more people are hacking their DSi's, it would be nice if people could start preservation efforts, ie. making backups of their original firmware before hacking the console. Having the backup would be a good idea for being able to unbrick the console if something goes wrong.
And for preservation, you couldn't release the whole 240MByte firmware dump for copyright reasons. But you could post the directory tree with CRC32's for each file - so one could see which file(s) the different firmware packages did consist of, and if there have been any old file versions prior to the first firmware update, and if the korean consoles did have different font files, etc.
I haven't created such tree's with crc's myself yet. But in theory, it should work as so:
- dump the eMMC memory (via hardmod or via dsiware exploits)
- also obtain your CID and ConsoleID
- decrypt the dump with twltool and then mount it as virtual disc drive
- use some compression tool to compress all files from the mounted drive (best make two .zip's, one per partition)
and then... not sure how that works nowadays... in msdos days one could view the contents (and CRC32's) for .zip files and redirect the screen output to a txt file (eg. via "pkunzip -v file.zip >file.txt"). I guess modern tools like 7zip should still support similar commandline interfaces.
Please also post some information about the DSi console (as far as known):
- the version/region shown in system settings
- did you (or somebody else) ever connect it to DSi Shop?
- did you (or somebody else) ever install a firmware update on it?
- did you (or somebody else) ever buy dsiware titles, or does it only have pre-installed titles on it?
- confirm that the dump comes from a console that wasn't messed with (ie. no manual system downgrades where you've replaced some files by older versions, or installed a patched whitelist, or such stuff)
And for preservation, you couldn't release the whole 240MByte firmware dump for copyright reasons. But you could post the directory tree with CRC32's for each file - so one could see which file(s) the different firmware packages did consist of, and if there have been any old file versions prior to the first firmware update, and if the korean consoles did have different font files, etc.
I haven't created such tree's with crc's myself yet. But in theory, it should work as so:
- dump the eMMC memory (via hardmod or via dsiware exploits)
- also obtain your CID and ConsoleID
- decrypt the dump with twltool and then mount it as virtual disc drive
- use some compression tool to compress all files from the mounted drive (best make two .zip's, one per partition)
and then... not sure how that works nowadays... in msdos days one could view the contents (and CRC32's) for .zip files and redirect the screen output to a txt file (eg. via "pkunzip -v file.zip >file.txt"). I guess modern tools like 7zip should still support similar commandline interfaces.
Please also post some information about the DSi console (as far as known):
- the version/region shown in system settings
- did you (or somebody else) ever connect it to DSi Shop?
- did you (or somebody else) ever install a firmware update on it?
- did you (or somebody else) ever buy dsiware titles, or does it only have pre-installed titles on it?
- confirm that the dump comes from a console that wasn't messed with (ie. no manual system downgrades where you've replaced some files by older versions, or installed a patched whitelist, or such stuff)
