Warning

This tutorial is only for advanced users and has a serious risk of bricking the console. Make sure you read it completely before executing any step and that you understand every step and its implications. With de_Fuse everything should be unbrickable if you know how.

You should at least have a backup of SLC and SLCCMPT, as we can’t rebuild them at the moment. (can be done in minute_minute, so there is no excuse). We had two cases where the SLC corrupted for an unknown reason, so a backup is essential.

What is this for?

This tutorial goes into rebuilding the MLC from scratch on a clean media. This can become useful, if

• the MLC (eMMC) chip died or corrupted the filesystem
• the SCFM (SLC cache for MLC) became inconsistent
• you want to upgrade the capacity of the internal storage.
• you want to set up a redNAND without SCFM

If you have a bad eMMC chip, but the recovery still works (which is most likely), then there are also ways to fix it without a complete reformat.
If the LED is blinking blue, you have a SLC problem and not a MLC problem, so this tutorial won't help with that.

It will format your MLC, so all data on the internal Wii U memory will be lost.

Update

13.03.2024 - The wafel_setup_mlc.ipx now uses a built in IOSU function to create system folders, that should make sure the permissions are right, which caused problems with game updates in the past. It will also recreate the update folder (so system updates won't be blocked by that)

Prerequisites

• Have either ISFShax installed: https://gbatemp.net/threads/how-to-set-up-isfshax.642258/#post-10280366
  OR de_Fuse 0.7.1 (or later): https://github.com/shinyquagsire23/wii_u_modchip/releases
  Defuse requires some soldering, so ISFShax is probably right for you (if you can still launch the installer).
• A 5.5.x firmware is expected and the only configuration tested. It might work on older firmwares or might be adoptable to those, but it will require special care.

Backing up save games

Do a backup of what you want to preserve, like savegames and Miis.
For Backing up Save games, it is recommended to use SaveMii. That requires that you have Tiramisu or Aroma running.
You can also move your savgames (or whole games) to USB, which should still be readable. When recreating the users after the rebuild, you just have to be carefull to create the users in the right order, to make the ID’s match. A backup by other means (Like savemii) is still recommended.
If you are using this tutorial to fix a failing eMMC you might not be able to use the other Backup options. In that case use the Dump MLC option in the Recovery. You can extract your data from there using wfs-extract.

Storage Options

The Wii U has two ways of connecting internal memory, each with its own drawbacks:

• SDIO – On retail consoles the internal memory is a eMMC chip connected through an internal SDIO bus to the Latte chip. This SDIO bus can also use SD cards (hence the name SD IO). Access to media connected on the SDIO is cached through a file on the SLC, presumably to reduce writes on the MLC. This cache is called SCFM and it is the reason why you always need to backup / restore SLC and MLC together and doesn’t allow easy swapping of multiple SDs.
  IOSU also only supports 3 sizes of media on this bus: <=8GB, 32GB and 64GB. The size will be limited to the biggest it fits, the rest is unusable. This bus is limited to 26MB/s (4bit@52Mhz). For replacing the eMMC with an micro SD you can use MLC2SD or a similar Interposer. Soldering and micro SD adapter using wires, works too.
  It is recommended to use a 64GB Sandisk Max Endurance card (But similar card should also be fine), since the Wii U is known for writing much.
  
  
• SATA – The Disc drive is connected through SATA, the connectors are different but the electrical signals are still the same. Some Kiosk consoles used this Interface to connect to a HDD. The type of the SATA device can be configured in the SEEPROM, so we can configure our retail consoles to also use a SATA HDD / SSD.
  NOTE: @QuarkTheAwesome is building an SATA adapter for that purpose, available soon™.
  
  The advantage of using this interface is, that the size isn’t limited (well WFS is limited to 2TB) and it doesn’t use SCFM, which makes some things easier and improves performance in some circumstances. The obvious disadvantage is that you can’t use your disc drive anymore. Without the Disc Drive vWii System Menu doesn't work. vWii Injectes / Wii VC from the eShop can still be used, but only when installed to USB. Also you still might need to disable the MLC on the SDIO bus, or else the wii u might still use the SDIO one if the SATA device takes too long to init.
  
  
• redNAND – redirects the read / writes to one or more of the internal storage devices to paritions on the SD card. You can create an arbitrary size MLC partition on the SD card and set it up using this tutorial. SCFM can be easily disabled for the redNAND. The 64GB limit does not exist for redNAND if the SCFM is disabled. For redNAND we have a dedicated Tutorial here: https://gbatemp.net/threads/fixing-...-soldering-using-rednand-with-isfshax.642268/

Does that mean we can’t get more than 64GB on the SDIO bus? No, BUT it requires ISFShax / defuse to boot the console every time. @GaryOderNichts created a patch to remove the limits and always use the maximum size of the SDIO media and it also disables SCFM, because SCFM doesn’t work with more than 64GB and disabling SCFM improves performance and reduces wear on the SLC, at the cost of increasing wear of the MLC media. I packaged this patch in wafel_unlimit_mlc.

Rebuilding the MLC

Now that you decided what media you want to use as MLC, we can start with the actual process:

1. Download all the mlc system titles for your region from NUS. This can be done conveniently with MLCRestorerDownloader by @Xpl0itU. Copy the otp.bin from the SD to the folder with the MLCRestorer Downloader so it can get the common key from there.
   
   You will get the output/MLC/{region} directory, which then contains a directory for each title. In total there should be 52 titles totaling ~1.1GiB.
   
   If your console has an old firmware it might also be necessary to get the latest SLC titles.
   
   
2. On the root of your SD card (the one that will go in the front slot, not the MLC replacement) create a folder wafel_install. Then copy all 52 titles to the wafel_install folder, so it now contains the 52 subfolders, one for each title. If you want to reinstall / update SLC titles, you would also put them there.
   
   
3. Attach your MLC media of choice. (If you are using SATA got to Backup and Restore, then at Set SATA Device in SEEPROM select GEN2-HDD (Kiosk CAT-I with HDD)).
   For installing MLC2SD look here: https://gbatemp.net/threads/using-n...emmc-fix-160-0103-system-memory-error.636361/ at the Soldering section.
   
   
4. If you install to eMMC / MLC2SD, got to Backup and Restore and select Erase MLC and Delete scfm.img. If the Erase MLC fails, you can ignore that if it wasn't formatted as MLC before (from a failed install or so).
   
   
5. Put the wafel_setup_mlc.ipx on the SD card in /wiiu/ios_plugins. If you want more than 64GB on SDIO you also need to put the wafel_unlimit_mlc.ipx there. If you install with wafel_unlimit_mlc.ipx, it will be permanently required and therefore also permanently requires ISFShax or defuse.
   
   
6. [Optional, only when using defuse] Open the serial monitor on the PC (Putty / minicom) for defuse to see the setup progress. There will be no display output in the Wii U itself. I attached the whole serial log of a successfull install as a reference.
   
   
7. Select Patch (sd) and boot IOS (slc) in minute to start the setup of your fresh MLC.During the setup you won't see anything on the screen. You have to go by the power led.
   The power LED will flash blue, while it is installing the titles.
   if something goes wrong the LED will turn orange, but it will continue as long as it is blinking.
   The LED will become static once it finished. You can now power off the console.
   If the led is blinking red, something fatal happend. Ask for help.
   During the setup a short log gets written to the SD: wafel_setup_mlc.log.
   In the end it will enable the initial setup on the next boot.
   
   
8. Remove the wafel_setup_mlc.ipx from /wiiu/ios_plugins on the SD.
   
   
9. Boot the console. Patch (sd) and boot IOS (slc)
   
   
10. If everything worked, the initial setup should launch.

ISFShax only: Finalizing

If you are using the wafel_unlimit_mlc.ipx you need to keep ISFShax installed. If you haven't done already complete the "Booting without SD" step form the ISFShax tutorial but also add the wafel_unlimit_mlc.ipx renamed to 9unlimit.ipx to the /storage_slc/sys/hax/ios_plugins directory.
If you are not using the wafel_unlimit_mlc.ipx you can either uninstall ISFShax or keep it as a brick protection. If you keep it complete the "Booting without SD" step form the ISFShax tutorial.
The Wii U should now boot automatically if you don't have an SD in.
You probably also want to enable the autobooting now.

See Also

https://gbatemp.net/threads/wii-u-internal-storage-upgrades-are-possible.635629/

Pictures

512 GB SD card:

@QuarkTheAwesome 120 GB SSD:

Thanks

• @GaryOderNichts for IOSU patches and code I took from the recovery
• @shinyquagsire23 for defuse, minute and stroopwafel
• @QuarkTheAwesome for IOSU format patch and SATA Adapter
• @V10lator for implementing Quota support and some improvements
• @Xpl0itU for MLCRestorerDownloader
• @Lazr1026 for testing and some fixes

 

[peilezhang]

When you disabled the drive it doesn't matter if it's connected or not, you would have to re-enable it.

vWii doesn't work with disabled disc drive (Wii VC works through).

I have removed all the de_config soldered wires, is there any other way to re-enable the sata device,like UDPIH?

 

[V10lator]

is there any other way to redeemable the data device,like UDPIH?

Not right now, no.

This is btw the reason I suggest to leave the RPI Pico inside of the console. Currently there are some bugs (working on it as soon as a package from china arrives as I got some hardware damage I need to fix before) preventing you from doing that, so you would have to disconnect the 3.3 V line.


BTW: There's also this: https://www.waveshare.com/rp2040-tiny.htm
It needs code changes in de_fuse but then it works just great and uses less space than the pico + you can route the cable to the extension board through the housing of the Wii U.
You just need to add a diode to the 3.3 V line as else a part of the board gets really hot when you connect it to USB but the Wii U isn't connected to wall power. Also the diode will drop the 3.3 V (I used a cheap diode I had lying around, it dropped the voltage to 2.3 V) but that's no big deal: The chip on the board itself works with anything between (and including) 1.8 and 3.3 V and the data lines of the Wii U also seem to be pretty high tolerance. Only "issue" is that the power LED on the extension board is barely visible but for me that's not important anyway.

 

[fringle]

Not right now, no.

This is btw the reason I suggest to leave the RPI Pico inside of the console. Currently there are some bugs (working on it as soon as a package from china arrives as I got some hardware damage I need to fix before) preventing you from doing that, so you would have to disconnect the 3.3 V line.


BTW: There's also this: https://www.waveshare.com/rp2040-tiny.htm
It needs code changes in de_fuse but then it works just great and uses less space than the pico + you can route the cable to the extension board through the housing of the Wii U.
You just need to add a diode to the 3.3 V line as else a part of the board gets really hot when you connect it to USB but the Wii U isn't connected to wall power. Also the diode will drop the 3.3 V (I used a cheap diode I had lying around, it dropped the voltage to 2.3 V) but that's no big deal: The chip on the board itself works with anything between (and including) 1.8 and 3.3 V and the data lines of the Wii U also seem to be pretty high tolerance. Only "issue" is that the power LED on the extension board is barely visible but for me that's not important anyway.

Would one of these work since it has all of the connections and seems to be about the same size as the one you posted?

https://www.waveshare.com/wiki/RP2040-Zero

Just curious as I have a couple of these that I bought and was thinking about using one of them if I do another console. They do work for udpih loading of the recovery menu.

 

[V10lator]

I don't have the time to check right now but from a quick look it might work for de_fuse (with codechanges who aren't public yet). For UDPIH you don't need the pins, so that works anyway.

Here btw some pictures of the Tiny board in action:

 

[fringle]

I don't have the time to check right now but from a quick look it might work for de_fuse (with codechanges who aren't public yet). For UDPIH you don't need the pins, so that works anyway.

Here btw some pictures of the Tiny board in action:
View attachment 387580
View attachment 387581
View attachment 387582

Nice. The one I posted has all of the connections. Some of them are just solder pads on the underside rather than castellated hole connections. I may give it a try just to see if it works this weekend since I have another disassembled Wii U here and can easily be removed if it's a no go.

 

[SDIO]

You don't need defuse to enable the SATA drive.
You just need to built an encrypted Minute fw.img and then you can load it with the standard fw omg loader shipped with tiramisu.

EDIT: @peilezhang I just attached the encrypted minute fw.img. Put it on the SD card, then hold B when launching Tiramisu / Aroma and select fw_img_loader. This should launch minute, where you can change the SATA Type

 

[Tuner357]

Hey!

So i have a wii u that someone removed the emmc from. I defused it and got it to boot on the tv, and able to see it through puTTy. I soldered in a nand aid, followed this tutorial, and i keep getting (at the end):

wafel_core: found OTP read pattern 1 at 08120290...
wafel_core: found OTP read at 08120248.
Firmware not 5.5.x! All you get is the OTP patch, sorry.
calling kern_entry in plugin: 27f77000
we in here setup mlc plugin kern 0x27f77484
init_linking symbol at: 00000000
setup patches applied
stroopwafel kern_main done

when i run the first option, and it just sits there with purple light on. says firmware not 5.5.x, how would i go about fixing this? Sorry for all the pics, i just want to make sure im including all the info i have haha

using a 64gb samsung pro edurance and nandaid

 

[SDIO]

Use JNUSTool to download OSv10 (Title 000500101000400A) get the fw.img from that and put it on the SD as ios_orig.img.
Then use the MLCRestorerDownloader and download the SLC titles in addition to the mlc titles and put both the mlc and the slc ctitles in the wafel_install folder.

Then use the second option in minute "Patch and boot ios_orig.img"

This way we are loading the current 5.5.5 IOSU from SD, so all the patches work and also upgrade the titles on the SLC during the setup of the MLC. So after that your Wii U is on the latest firmware.

EDIT: how big is the SD you put in the NAND-AID? I would recommend at least 64GB to make sure it gets formatted and you don't run into problems with scfm.

 

[peilezhang]

You don't need defuse to enable the SATA drive.
You just need to built an encrypted Minute fw.img and then you can load it with the standard fw omg loader shipped with tiramisu.

EDIT: @peilezhang I just attached the encrypted minute fw.img. Put it on the SD card, then hold B when launching Tiramisu / Aroma and select fw_img_loader. This should launch minute, where you can change the SATA Type

You are so amazing! I'll go out for a few days, will try this when I back.Thank u for your help!

 

[Tuner357]

Use JNUSTool to download OSv10 (Title 000500101000400A) get the fw.img from that and put it on the SD as ios_orig.img.
Then use the MLCRestorerDownloader and download the SLC titles in addition to the mlc titles and put both the mlc and the slc ctitles in the wafel_install folder.

Then use the second option in minute "Patch and boot ios_orig.img"

This way we are loading the current 5.5.5 IOSU from SD, so all the patches work and also upgrade the titles on the SLC during the setup of the MLC. So after that your Wii U is on the latest firmware.

EDIT: how big is the SD you put in the NAND-AID? I would recommend at least 64GB to make sure it gets formatted and you don't run into problems with scfm.

Thanks for the reply SDIO

Im using a 64gb samsung pro endurance card that in trying to use in the nand-aid. I also have already aquired the slc and mlc files, so im good there!

but excuse my ignorance, how do i run jnustool? downloaded it but its a .jar file and i am not familiar.

Thank you, very excited to get this $20 Wii u going!

 

[SDIO]

You need to add the Wii U common key to the config file.
Then do:

java -jar JNUSTool.jar 000500101000400A

 

[Tuner357]

You need to add the Wii U common key to the config file.
Then do:

java -jar JNUSTool.jar 000500101000400A

awesome, got it. picked second option after renaming the new fw.img file and its doing its thing. but the led turned orange? i can still see stuff happening on puTTy though

 

[SDIO]

then wait till the led stops blinking and then show the install log, which got created on the sdcard

 

[Tuner357]

then wait till the led stops blinking and then show the install log, which got created on the sdcard

okay. it keeps scrolling this, its fine to turn off right now? solid orange light. just want to double check

 

[SDIO]

yes, turn it of and upload the log, so we can see what went wrong

 

[Tuner357]

yes, turn it of and upload the log, so we can see what went wrong

awesome, here you go

MakeQuota;/vol/storage_mlc01/sys;-00000000
MakeDir;/vol/storage_mlc01/usr;-00000000
MakeDir;/vol/storage_mlc01/usr/boss;-00000000
MakeDir;/vol/storage_mlc01/usr/save;-00000000
MakeDir;/vol/storage_mlc01/usr/save/00050010;-00000000
MakeDir;/vol/storage_mlc01/usr/packages;-00000000
MakeDir;/vol/storage_mlc01/usr/tmp;-00000000
Flush;MLC;-00000000
OpenDir;/vol/sdcard/wafel_install;-00000000
OpenMCP;/vol/sdcard/wafel_install;-00000000
InstallInfo;SLC;-FFFBF3E2
InstallInfo;MLC;-FFFBF3E2
Flush;MLC;-00000000
SetInitialLaunch;0;-00000001
Flush;SLC;-00000000

 

[V10lator]

OpenMCP;/vol/sdcard/wafel_install;-00000000
InstallInfo;SLC;-FFFBF3E2
InstallInfo;MLC;-FFFBF3E2

I guess you have MLC and SLC folders inside of wafel_install and then the titles inside of them? That's wrong, put the titles directly into wafel_install.

//EDIT: @SDIO I have codes for recursively searching for title.tmd files (and even for validating them), could probably be ported over to prevent such mistakes.

 

[SDIO]

Maybe you mad subdirectories there?
in the wafel_install folder you will have one subfoler for every title and this folder contains all the files. No other folders in between

 

[Tuner357]

@SDIO @V10lator def had them in mlc and slc folders. now i have this error log

MakeQuota;/vol/storage_mlc01/sys;-FFFCFFEA
MakeDir;/vol/storage_mlc01/usr;-FFFCFFEA
MakeDir;/vol/storage_mlc01/usr/boss;-FFFCFFEA
MakeDir;/vol/storage_mlc01/usr/save;-FFFCFFEA
MakeDir;/vol/storage_mlc01/usr/save/00050010;-FFFCFFEA
MakeDir;/vol/storage_mlc01/usr/packages;-FFFCFFEA
MakeDir;/vol/storage_mlc01/usr/tmp;-FFFCFFEA
Flush;MLC;-00000000
OpenDir;/vol/sdcard/wafel_install;-00000000
OpenMCP;/vol/sdcard/wafel_install;-00000000
InstallInfo;0005001010045100;-00000000
Install;0005001010045100;-00000000
InstallInfo;0005001010047100;-00000000
Install;0005001010047100;-00000000
InstallInfo;0005001010048100;-00000000
Install;0005001010048100;-00000000
InstallInfo;0005001010049100;-00000000
Install;0005001010049100;-00000000
InstallInfo;0005001010062100;-00000000
Install;0005001010062100;-00000000
InstallInfo;0005001010066000;-00000000
Install;0005001010066000;-00000000
InstallInfo;0005003010010109;-00000000
Install;0005003010010109;-00000000
InstallInfo;0005003010011109;-00000000
Install;0005003010011109;-00000000
InstallInfo;0005003010017109;-00000000
Install;0005003010017109;-00000000
InstallInfo;0005001b1004f000;-00000000
Install;0005001b1004f000;-00000000
InstallInfo;0005001b1005c000;-00000000
Install;0005001b1005c000;-00000000
InstallInfo;0005001b1005f000;-00000000
Install;0005001b1005f000;-00000000
InstallInfo;0005001b1006c000;-00000000
Install;0005001b1006c000;-00000000
InstallInfo;0005001b10042300;-00000000
Install;0005001b10042300;-00000000
InstallInfo;0005001b10042400;-00000000
Install;0005001b10042400;-00000000
InstallInfo;0005001b10050000;-00000000
Install;0005001b10050000;-00000000
InstallInfo;0005001b10051000;-00000000
Install;0005001b10051000;-00000000
InstallInfo;0005001b10052000;-00000000
Install;0005001b10052000;-00000000
InstallInfo;0005001b10053000;-00000000
Install;0005001b10053000;-00000000
InstallInfo;0005001b10054000;-00000000
Install;0005001b10054000;-00000000
InstallInfo;0005001b10056000;-00000000
Install;0005001b10056000;-00000000
InstallInfo;0005001b10057000;-00000000
Install;0005001b10057000;-00000000
InstallInfo;0005001b10058000;-00000000
Install;0005001b10058000;-00000000
InstallInfo;0005001b10059100;-00000000
Install;0005001b10059100;-00000000
InstallInfo;0005001b10063000;-00000000
Install;0005001b10063000;-00000000
InstallInfo;0005001b10065000;-00000000
Install;0005001b10065000;-00000000
InstallInfo;0005001b10067100;-00000000
Install;0005001b10067100;-00000000
InstallInfo;0005001b10068000;-00000000
Install;0005001b10068000;-00000000
InstallInfo;0005001b10069100;-00000000
Install;0005001b10069100;-00000000
InstallInfo;000500101004a100;-00000000
Install;000500101004a100;-00000000
InstallInfo;000500101004b100;-00000000
Install;000500101004b100;-00000000
InstallInfo;000500101004c100;-00000000
Install;000500101004c100;-00000000
InstallInfo;000500101004d100;-00000000
Install;000500101004d100;-00000000
InstallInfo;000500101004e100;-00000000
Install;000500101004e100;-00000000
InstallInfo;000500101005a100;-00000000
Install;000500101005a100;-00000000
InstallInfo;000500301001a10a;-00000000
Install;000500301001a10a;-00000000
InstallInfo;000500301006d10a;-00000000
Install;000500301006d10a;-00000000
InstallInfo;00050030100111ff;-00000000
Install;00050030100111ff;-00000000
InstallInfo;000500301001010a;-00000000
Install;000500301001010a;-00000000
InstallInfo;000500301001110a;-00000000
Install;000500301001110a;-00000000
InstallInfo;000500301001210a;-00000000
Install;000500301001210a;-00000000
InstallInfo;000500301001310a;-00000000
Install;000500301001310a;-00000000
InstallInfo;000500301001410a;-00000000
Install;000500301001410a;-00000000
InstallInfo;000500301001510a;-00000000
Install;000500301001510a;-00000000
InstallInfo;000500301001610a;-00000000
Install;000500301001610a;-00000000
InstallInfo;000500301001710a;-00000000
Install;000500301001710a;-00000000
InstallInfo;000500301001810a;-00000000
Install;000500301001810a;-00000000
InstallInfo;000500301001910a;-00000000
Install;000500301001910a;-00000000
InstallInfo;0005001010040100;-00000000
Install;0005001010040100;-00000000
InstallInfo;0005001010041100;-00000000
Install;0005001010041100;-00000000
InstallInfo;0005001010043100;-00000000
Install;0005001010043100;-00000000
InstallInfo;0005001010044100;-00000000
Install;0005001010044100;-00000000
InstallInfo;0005001010004009;-00000000
Install;0005001010004009;-00000000
InstallInfo;00050010100040ff;-00000000
Install;00050010100040ff;-00000000
InstallInfo;000500101000400a;-00000000
Install;000500101000400a;-00000000
InstallInfo;0005001010004000;-00000000
Install;0005001010004000;-00000000
InstallInfo;0005001010004001;-00000000
Install;0005001010004001;-00000000
Flush;MLC;-00000000
SetInitialLaunch;0;-00000001
Flush;SLC;-00000000

 

[SDIO]

this is fine. The folders were stimply created by the first run, but all the installs were successfull. The Wii U should now boot without defuse. (just remove power (3V3 and USB) from the pico)