Hacking Giantpune's Wii NAND Tools For Mac OS X

[wiisixtyfour]

Giantpune has made some very useful tools that allow you to do many things with a BootMii NAND dump. Check out the wiiqt project page here. I have compiled the latest versions of the four of giantpune's NAND tools for use on Mac OS X.
EDIT: In order to run these you need to install the Qt libraries from here: [qt.nokia.com] or install the Qt SDK from here: [qt.nokia.com]

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. Note: You must run nandBinCheck from a Terminal window. You can find Terminal in Launchpad in the Utilities folder.
Get nandBinCheck here.

The next tool is "ohneschwanzenegger". It is a program for creating, formatting, & writing to a nand.bin. It allows you to create a nand.bin on your Mac 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. 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. Note: You must run punetwiin from a Terminal window. You can find Terminal in Launchpad in the Utilities folder.
Get punetwiin here.

Of course all credit for these apps goes to giantpune all I did was compile them for Mac OS X.

 

[giantpune]

did you build the Qt libraries to link statically? and did you use the static libs to link to these binaries? and did you have it build universal mac binaries?

if you didnt built the Qt libraries statically, and use the static libs to build these, then people will need to have, at least, the necessary .so files in the right path. and if you didnt change the .pro file to build a universal binary, then i think it wil only be for the intel or ppc, but not both. I built Qt statically for OSx 1 time and it took about 4 hours to compile, even after you figure out all the right configure switches. And then I had something still missing, so I never did get it to build a universal binary the way i wanted it to.

If you are dynamically linking to the Qt libs, you can run "otool -L /path/to/binary" and it should tell you what libs people will need to be able to use these without having to install the full Qt framework.

Also, I never had a chance to try these out on a big endian machine. everything SHOULD be right, but people using such processors should be extra cautious with these since they are in uncharted waters.

 

[wiisixtyfour]

I didn't build the Qt libs or change the .pro file. All I did was download the Qt Creator and then compile your apps with it. They work for me, but I haven't really done testing or anything. I really don't know much about Mac nor do I know about coding.
If anyone could try these and see if they work without any libs or external files that would help. If anything else is needed then I'll update the post.

 

[giantpune]

the reason they work for you is because you installed all the required libraries. if somebody using a mac without these libraries tries to run them, it will just spit out an error and not start.

 

[PsyBlade]

imho: just list qt as a dependency

static linking is dreadful from a security pov

 

[tueidj]

That might be relevant if anyone was going to set up a server giving remote access to these tools but otherwise I can't see how it matters.