In this tutorial I will go over how to build iosuhax from either my branch (for wupserver only) or dimoks branch (for rednand and signature patches) without having anything related installed yet.

Getting python
The first thing you want to do is download python, for this guide you will click download python 3.5, this will give you the current 3.5 32bit installer of python. If you already have a python 2 installation and you dont want to uninstall for python 3 then skip this step but note that you may have to add the python installation path into the PATH variable yourself if you didnt do that during that installation.
After opening the 3.5 32bit installer make sure to enable "Add Python 3.5 to PATH" because we want to be able to call python from anywhere, now let it install.

Installing pycrypto
To easly install pycrypto we will install it from this github page for the current 3.5 or this page for 2.7 if you have that. Open up a command prompt by for example pressing windows+r and typing in "cmd", in this command prompt you want to enter the following (just copy paste this depending on your python version):

Spoiler

PYTHON 3
Python 3.5 32bit:

pip install --use-wheel --no-index --find-links=https://github.com/sfbahr/PyCrypto-Wheels/raw/master/pycrypto-2.6.1-cp35-none-win32.whl pycrypto

Python 3.5 64bit:

pip install --use-wheel --no-index --find-links=https://github.com/sfbahr/PyCrypto-Wheels/raw/master/pycrypto-2.6.1-cp35-none-win_amd64.whl pycrypto

PYTHON 2
Python 2.7 32bit:

pip install --use-wheel --no-index --find-links=https://bitbucket.org/alexandrul/wheels/downloads/pycrypto-2.6.1-cp27-none-win32.whl pycrypto

Python 2.7 64bit:

pip install --use-wheel --no-index --find-links=https://bitbucket.org/alexandrul/wheels/downloads/pycrypto-2.6.1-cp27-none-win_amd64.whl pycrypto

If you have any older python 2/3 version then maybe just consider upgrading to the current version of python 2/3.

This will automatically install pycrypto for your python version, just let it finish up.

Getting devkitARM
Download the devkitpro updater from here and start it up, it will give you quite a few options on things to install, all you need to select is "Minimal System" and "devkitARM", you can uncheck everything else. Now just let it download and install everything.

Getting armips
For armips you can just download my pre-compiled exe and put it into "C:\devkitPro\msys\bin" so it can be directly used on compilation.

Downloading and preparing iosuhax
Depending on what you want head over to my branch or dimoks branch, click on "Clone or download" and if you have git then clone it, if you dont have git just click "Download ZIP" and extract the contents of it into a new folder on your computer. Make sure that new full folder path does not contain any spaces, a wrong path would be "C:\my folder\iosuhax", a correct folder would be "C:\my_folder\iosuhax".

Now if you have "the 2 keys" already you can edit the getfwimg from the little guide below:

Spoiler

Go into the "bin" folder, right click on getfwimg and select "Edit with IDLE", put the 2 keys in like this:

wiiu_common_key = "D7000000000000000000000000000000"
starbuck_ancast_key = "B5000000000000000000000000000000"

Of course these are not the full keys but only their first 2 digits. Now just save it.

If you dont have "those 2 keys" you can easly get them from your wiiu itself like this without having to edit any scripts:

Spoiler

Go grab otp2sd and start it via the homebrew launcher, it will just restart you and place a otp.bin on your wiiu sd card. Copy that otp.bin one folder above the iosuhax one so in our example let iosuhax be in "C:\my_folder\iosuhax", so you copy otp.bin into "C:\my_folder", iosuhax will find that otp.bin and use it automatically, you dont need to edit any scripts this way.

Now that you finally prepared iosuhax its time to compile it! Shift-right click in the iosuhax main folder, click on "Open command window here" and just type in "make" and press enter, this will get you a fw.img as output which you can put on you sd card root and use in cfw booter! If it failed to compile because of commands being unknown you may have to reboot your computer to make sure it properly installed all of the software.

I hope with this you were able to successfully compile iosuhax, now have fun with it

Note by Cyan:
Dimok branch can now build both CFW with and without NAND redirection to SD card, while Fix94 branch only compile a SysNAND CFW.

Fix94 branch : sysNAND. doesn't have latest cfw patches, but fix94 version contain new wupserver command instead.
Dimok branch : sysNAND and redNAND. This branch has currently more features than fix94 branch (allows HBL channel version installation, unrestricted NAND FTP access, NAND to SD dump, FAT32 USB mount support, etc.)

When you are at the compiling step,
fix94 sysNAND, type : make
dimok sysNAND, type : make cfw
dimok redNAND, type : make redNAND
by default, typing only "make" on dimok branch, it will build redNAND

 

[tHciNc]

I get error on Pycrypto install, i have both 2.7 and 3.5 python installed

 

[Cava]

@FIX94 @dimok I can't compile dimok's new repo just yours. The old one worked. Can u please help in this?

Well.. i just copied dimok's repo to the C:\ drive and it worked too but FIX94 repo worked from drive e:\ interesting.

 

[FIX94]

I get error on Pycrypto install, i have both 2.7 and 3.5 python installed

pip in this case probably is from python 2.7 instead of 3.5 so you end up in this version conflict. Now if you REALLY want to keep 2.7, you can use the adjusted links in the guide, I've updated it to include some commands for people who want to keep their existing 2.7 installation.

 

[pietempgba]

ImportError: cannot import name 'main'

 

[barak06]

May i aske again :
Last questions @FIX94
- is the fw.img needs to be patched to be used in wiiU ? Because i found lot og .img on forums : fw_dumper, iosuhaxsigpatched, NANDDUMPER... with not the same size as my fw.img nor the same crc32 sig
- what's fw.img.full for ?
THX

 

[Supster131]

is the fw.img needs to be patched to be used in wiiU ?

It has to be patched, yes.

what's fw.img.full for ?

Ignore that. The only important file is the fw.img file that's created on the root of your folder after you compiled it.

 

[barak06]

It has to be patched, yes.

So how do i patch it before use it in rednand install ? thx

 

[x65943]

So how do i patch it before use it in rednand install ? thx

See below

Now that you finally prepared iosuhax its time to compile it! Shift-right click in the iosuhax main folder, click on "Open command window here" and just type in "make" and press enter, this will get you a fw.img as output which you can put on you sd card root and use in cfw booter!

Running "make" patches it, and creates a patched copy in the folder "iosuhax".

 

[Cyan]

- is the fw.img needs to be patched to be used in wiiU ? Because i found lot og .img on forums : fw_dumper, iosuhaxsigpatched, NANDDUMPER... with not the same size as my fw.img nor the same crc32 sig
- what's fw.img.full for ?

I'll answer in the reverse order as it makes more sense :

- fw.img is the official encrypted firmware from the WiiU. it's extracted from a System update file downloaded from Nintendo's update servers.
- fw.img.full is the official firmware from the WiiU in its decrypted form. it has no changes and if you boot this one, you will just boot the console normally (from sysNAND, etc.).
- fw.img.full needs to be patched to add features and functions, like WUPserver or signature patches.

the final, patched fw.img.full with added features, is then called "fw.img" again, which could be confusing as it's the same name than the official file used by the console.
I don't know if it's re-encrypted to let the console loads an encrypted fw.img, or if the console can boot a decrypted fw.img


The CRC32 and size of the "official" 5.5.1 files are always the same. ( fw.img CRC32 d674201b and fw.img.full.bin CRC32 9f2c91ff)
The CRC32 and size of the "patched" files are different based on 1) the version of the hack (fix94, dimok, which fork and revision, etc.), 2) the ARM compiler version you use or its install path.
So, you could find different files on the forum (which is illegal to share! if you encounter any, please report the message to be deleted!), it's not necessarily a wrong file, but you don't know if it's a good one either, you will never know which version that compiled file is from, unless the user who compiled it provided the version of github he used.

as there's no official version release, and anyone can branch and mod IOSUHax, it's probably better to get used to provide a link or the github version checksum used to compile shared files!

 

[Bimmel]

When I click right on getfwimg.py, Edit with IDLE won't show up.

What did I do wrong?

Edit: I give up. Will use the uploaded one. Shouldn't make a difference.

 

[Beeldoway]

I have this :

C:\wiiu\iosuhax>make
/bin/sh: python: command not found
make: *** [bin/fw.img.full.bin] Error 127

C:\wiiu\iosuhax>

Help

 

[muddog23]

So I followed it step for step and everything went great. I have everything I need. Now what? Can someone point me to a thread about the installation of FIX94's FW.IMG

 

[x65943]

So I followed it step for step and everything went great. I have everything I need. Now what? Can someone point me to a thread about the installation of FIX94's FW.IMG

Download cfw booter from here http://wiiubru.com/appstore/zips/cfwbooter.zip (place this in your sd card)

Place fw.img on the root of your sd card

Load the homebrew launcher by visiting loadiine.ovh on your wiiu browser (if you don't have it you can download the starterpack from here http://www.wiiubru.com/appstore/starterkit/starter_pack.rar)

 

[muddog23]

Do I need to format the SD card into two separate partitions?

I'm all set up for homebrew using loadiine.ovh

 

[x65943]

Do I need to format the SD card into two separate partitions?

Are you using Dimok's build or FIX94's?

You don't need to partition your sd for either. Dimok's will partition it for you, and FIX94's works without emunand.

 

[muddog23]

Thank you!

 

[buhdiego]

What's the difference between dimok's and fix94's?

 

[iAqua]

What's the difference between dimok's and fix94's?

fix94's is scripts, dimok's actually the stuff for nand dumping.

 

[buhdiego]

fix94's is scripts, dimok's actually the stuff for nand dumping.

Thanks man =D

 

[Ataloumpak]

I have this :

C:\wiiu\iosuhax>make
/bin/sh: python: command not found
make: *** [bin/fw.img.full.bin] Error 127

C:\wiiu\iosuhax>

Help

It seems that the make command is unable to get every windows paths for some reasons. I got it fixed by adding in the makefile the complete path of python.exe surrounded by quotes. That's the only way i found.
To find it, i simply went in the "environment variable" windows panel.

For me, it was "C:\Users\UserName\AppData\Local\Programs\Python\Python35\python"