hexFW - A custom firmware framework for the Wii U
Switch branches/tags
Nothing to show
Clone or download
Latest commit 0bb8cda Jan 14, 2018

README.md

hexFW

hexFW is an attempt to provide a user friendly CFW solution for the Wii U.

Summary

The code in this repository is divided into two main folders:

  • "firmware": IOSU patching framework
  • "launcher": exploit code chain responsible for injecting the patched IOSU image

Currently, iosuhax (by smealum) is the basis for the firmware patching framework. This project's goal is to build upon smealum's patching system to deliver a fully functional and customizable Wii U CFW. The exploit chain used to inject the firmware's code uses yellows8's wiiu_browserhax_fright and is a direct implementation of two distinct vulnerabilities documented by hykem, naehrwert and plutoo. The exploit is compiled using a stripped down version of the libwiiu project and is triggered from the Wii U's Web Browser.

Dependencies

Building

  • Open "Keys.txt" with a text editor and replace the dummy keys with the real ones;
  • Copy "armips(.exe)" to the root of the "firmware" folder;
  • Browse back to the main folder ("hexFW") and run "make" from a shell.

Usage

  • After building the project a new folder "bin" will be created in the root folder ("hexFW") as well as two sub-folders "www" and "sdcard".
  • Copy the "fw.img" file inside "sdcard" into the root of your SD card (FAT32 formatted, preferably).
  • Setup a server (e.g.: localhost:8080) and host the contents of "www". After inserting the SD card (with the firmware image) into the Wii U, browse to "wiiu_browserhax.php" and pass along your target system's version (e.g.: localhost:8080/wiiu_browserhax.php?sysver=550).
  • The launcher will run ("fwboot") and launch the firmware image from the SD card.

hexcore

hexcore is the default program distributed with hexFW. It's code is injected into IOS-MCP and runs in a dedicated thread, similar to how the old wupserver works. Upon launching the generated "fw.img", you will be presented with a barebones recovery console with the following options:

  • Dump OTP -> Dumps your console's OTP into the SD card
  • Dump SEEPROM -> Dumps your console's SEEPROM into the SD card
  • Dump SLC -> Dumps a raw image of the SLC into the SD card
  • Dump SLCCMPT -> Dumps a raw image of the SLCCMPT into the SD card
  • Dump MLC -> Dumps a raw image of the MLC into the SD card
  • Dump BOOT1+OTP -> Dumps your console's plaintext boot1 binary and the unlocked OTP
  • Launch wupserver -> Sets up wupserver and proceeds with booting sysNAND
  • Shutdown -> Simply shuts the console down
  • Credits -> Displays the credits page for 10 seconds

You can browse the options' list by pressing the "Eject" button and confirm by pressing the "Power" button. Please note that this is still a work in progress and is meant to showcase the potential for a complete CFW solution. More functionalities will be added in time and the general mode of operation may change at any time.

boot1 dumping

In order to dump your console's boot1 binary you have to boot hexFW twice. Launch hexFW and select the option "Dump BOOT1+OTP". This will reboot your console and you'll have to launch hexFW again. The second time you select the "Dump BOOT1+OTP" option, the actual binary will be written to your SD card.

Credits