|Posted by wiisixtyfour on May 10, 2011 at 3:05 AM|
Giantpune has released some very useful tools that allow you to do many things with a BootMii NAND dump. Check out the project page here. I have compiled the latest (updated to r106 as of June 5, 2011) versions of the four of giantpune's tools for use on Windows. I may get around to doing the OSX version if I can figure that out later...
Update: For Mac OS X versions see here.
In order to use any of these 4 tools, you will need a set of DLL files (place them in the same folder as the exe).
Get the DLL files here.
The first tool is "nandBinCheck" which is used to display information about a nand.bin for the Wii. "nandBinCheck" is a Command Line Interface (CLI) program, so there's no fancy GUI. It is able to display information about boot1 & 2, nand filesystem, permissions, ecc, hmac, SFFS, detect causes of many different types of bricks ( opera, 003, unbootable IOS ). With this program, you are almost guaranteed that a nand.bin is safe to install on a Wii. Giantpune has also used it many times to diagnose an otherwise unknown cause of brick.
Get nandBinCheck here.
The next tool is called "ohneschwanzenegger". It is a program for creating, formatting, & writing to a nand.bin. It allows you to create a nand.bin on your PC that you can then install with bootmii or a flash programmer. It accepts WADs or can download titles and full updates from NUS. It is still recommended that you check the contents of a nand.bin before installing it to a Wii.
Get ohneschwanzenegger here.
The third tool is "nandExtract" which can extract some or all files from a nand.bin, as well as examine its contents. You can see all the blocks of the NAND dump as well as info about the boot sector and such.
Get nandExtract here.
The final tool is "punetwiin". It's basically like betwiin which converts a NAND.bin to use on a different Wii with the different keys. It works slightly different though; It takes a full nand.bin for both done files. It pulls the files and filesystem from the first NAND, and it pulls boot1 and boot2, the keys and the bad block map from the second NAND. When its done, you will have the contents from the filesystem in the first NAND mixed with everything else from the second NAND. The full process should take about 2 minutes. Bad blocks are taken into account, so it should be safer that Betwiin. Anybody using punetwiin is encouraged to verify the content of the output file before installing it.
Get punetwiin here.
Of course all credit for these apps goes to giantpune and all the people who originally figured this stuff out (Team Twiizers) all I did was compile them for Windows.