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

 

[SDIO]

Yes the recovery can remove parental control. I think it is selfexplanitory, when you are in the recovery. But if it has parental control, it can't be brand new...

I would remove the defuse only after the update, in case something goes wrong... (Back then there were lot's of bricks with the launch update)

 

[Ysecond]

EDIT: did you look from which manufacturer the SLC chip is?

Just providing feedback on some information. One of my consoles.

 

[SDIO]

I never saw that much corruption on a SLC...

Post automatically merged: Jul 30, 2023

I would to a slc backup and then delete all the corrupted files except (scfm.img, here a bad hmac is expected) and after that reinstall all slc titles

 

[Ysecond]

Maybe the IOSU on the SLC is to old. If you have a SLC dump, which you should have, you can extract it and look at the app.xml to see which version the iosu has.

If you just want to make it work fast, I would siggest downloading the latest iosu with jnus and put the fw.img from it as ios_orig.img on the sd. Then you can use the second option in minute `Patch and boot ios_orig.img`.
I wouid then suggest you download also the SLC titles and put them also in the wafel_install, so the titles on the slc will be updated to during the mlc rebuild

I completely followed this guide and this console was reborn.
This console has gone through a lot of trouble. I first posted it here，It has a Hynix MLC, I think it has emmc corruption, I try various methods，but there has been no progress. One day, I found that the resistance between CLK and GND was 0, SO I think the EMMC has internal short circuit，I removed the EMMC, but the motherboard still had a short circuit. Finally, it was found that there was an internal short circuit in the PCB. I cut off the CLK and connected the CPU bottom to the SD with a wire.
PCB short circuit is very rare，I wrote this down in the hope of helping some people.

Post automatically merged: Jul 31, 2023

I would to a slc backup and then delete all the corrupted files except (scfm.img, here a bad hmac is expected) and after that reinstall all slc titles

I have tried installing SLC titles，The serial console gives a prompt like 'Too many NAND errors'， I forgot the specific content，It's like saying, 'NAND is hopeless'，so I completely gave up on this console.

 

[SDIO]

You had SLC corruption and an internal short in the Mainboard in one console? Kudos for fixing that. If I had seen a short on the clk, with the eMMC removed I would have assumed that the Latte was dead.
I think we had some similar case in discord, where the Wii U was literally frying the NAND-AID and other replacement's we tried

Do you have pictures, where you cut the trace and how you patched it?

Post automatically merged: Jul 31, 2023

I have tried installing SLC titles，The serial console gives a prompt like 'Too many NAND errors'， I forgot the specific content，It's like saying, 'NAND is hopeless'，so I completely gave up on this console.

you maybe could have swapped the banks with the slccmpt and then reset the bad block markers. Or you could have used rednand to replace the the slc with rednand. Maybe the dying slc was just good enough to hold isfshax.

 

[Fabioperez]

@SDIO answering your question "EDIT: did you look from which manufacturer the SLC chip is?"
the SLC is a Samsung, I am going to ask something that can cause the error that a wii u at the moment of wanting to synchronize the game pad error appears is another console that I have when pressing the synchronization button 2 times an error without number appears and says You have to restart and try again and the same thing always happens, it will be software or hardware, I already changed the wireless module, and the gamepad is not because it works with other consoles

 

[Tbone182b]

I think we had some similar case in discord, where the Wii U was literally frying the NAND-AID and other replacement's we tried
(...)
Do you have pictures, where you cut the trace and how you patched it?

@Ysecond : that "similar case" would be me. I think I've got a similar situation as everything seemed to be shorted with no visible burns or components heating up, plus I'm missing current on some of the caps.
Very curious to the question SDIO asked you as well: where did you cut CLK and can you share some pictures of where you (re)connected?
I'm currently on leave, but eager to try in a few weeks - had already accounted this Wii U as e-waste.

 

[Ysecond]

Do you have pictures, where you cut the trace and how you patched it?

Sorry, I was a bit busy a few days ago.
I just rudely cut off the CLK from the CPU to the emmc, and connect the CPU and SD card with a flying wire.

Post automatically merged: Aug 2, 2023

plus I'm missing current on some of the caps.

We know that multiple voltages are required for the console to function properly, my situation only applies to the EMMC section, what is the situation with your console? Does it have a blue light?

 

[SDIO]

I am going to ask something that can cause the error that a wii u at the moment of wanting to synchronize the game pad error appears is another console that I have when pressing the synchronization button 2 times an error without number appears and says You have to restart and try again and the same thing always happens, it will be software or hardware, I already changed the wireless module, and the gamepad is not because it works with other consoles

not sure if I got yo correctly. But did you make sure the region of te gamepad and the console matches?
Can you try to pair in the recovery?

 

[Fabioperez]

not sure if I got yo correctly. But did you make sure the region of te gamepad and the console matches?

If both are from the same region, both wii u and gamepad,

Can you try to pair in the recovery?

It has been impossible for me to enter the recovery menu, I have tried to enter the raspberry pi pico at different time intervals and I have not been able to enter the recovery menu, I have done it on other consoles and it works perfectly but it does not work on this one

The problem is when you want to synchronize the gamepad with the wii u, you have to press the red button on the console 2 times, the first sample to pair wiimote and procontroller, until everything works fine, but when you press the red button a second time Pairing button on the console shows a message that it has not been possible, it asks to restart and try again.
There is no way to enter the wii u settings because it requests the connection of the game pad. Basically that is the problem, nothing can be done with that wii u, I am attaching a link to a video, it is not my responsibility but it shows the error in case you can take a look

 

[Ysecond]

Attach your MLC media of choice. (The SATA device can be disabled by going to Backup and Restore, then at Set SATA Device in SEEPROM select No Device (0x02)).

If I want to use a SATA hard drive, do I only need to set SEEPROM to No Device (0x02)? Prior to this, I had already removed the EMMC and SD card. Is that also require Wafel_ Unlimit_ mlc.ipx when Hard drive exceeding 64GB?

 

[fringle]

Finally got around to giving this a shot and for some reason I'm hanging at:

[pico] Changed state: WIIU_STATE_NEEDS_DEFUSE -> WIIU_STATE_DEFUSED
[pico] Changed state: WIIU_STATE_DEFUSED -> WIIU_STATE_MONITORING

Could it be my sd card? I'm using an old 2gb, I've got a solid purple led.

Replacing the Nand with a 64gb card.

 

[SDIO]

For HDD you need to either select GEN2-HDD or GEN1-HDD. Not sure which one exactly, as I havent tried that myself yet, but @QuarkTheAwesome should know.

For HDD you don't need the unlimit plugin. HDD is unlimited by default

Post automatically merged: Aug 3, 2023

Finally got around to giving this a shot and for some reason I'm hanging at:

[pico] Changed state: WIIU_STATE_NEEDS_DEFUSE -> WIIU_STATE_DEFUSED
[pico] Changed state: WIIU_STATE_DEFUSED -> WIIU_STATE_MONITORING

Could it be my sd card? I'm using an old 2gb, I've got a solid purple led.

Purple means that the custom code is running. Do you get any other ouput, like some numbers?

 

[fringle]

For HDD you need to either select GEN2-HDD or GEN1-HDD. Not sure which one exactly, as I havent tried that myself yet, but @QuarkTheAwesome should know.

For HDD you don't need the unlimit plugin. HDD is unlimited by default

Post automatically merged: Aug 3, 2023

Purple means that the custom code is running. Do you get any other ouput, like some numbers?

After I get those messages I get nothing else. Just sits there.

 

[SDIO]

Strange, can you try this boot1.img?

 

[fringle]

Strange, can you try this boot1.img?

Same thing. I assume that de_fuse is installed correctly or I wouldn't get this far. Does all of the hardware need to be connected, like the disc drive and wireless/bluetooth cards?

 

[SDIO]

You don't need the disc drive and I think you also don't need wireless and bluetooth, but not sure on that.
Maybe @shinyquagsire23 has an idea.

 

[fringle]

You don't need the disc drive and I think you also don't need wireless and bluetooth, but not sure on that.
Maybe @shinyquagsire23 has an idea.

I did pop them on but still no change. I'll see if I can find another sd card just to rule that out.

Post automatically merged: Aug 3, 2023

I actually have output over hdmi showing the rest of it. I thought it would be displayed in the serial console.

 

[SDIO]

It should also be displayed on the serial console... Maybe you have a problem with the connection from the PICO to the Wii U, but then I wouldn't expect defuse to work.

 

[fringle]

It should also be displayed on the serial console... Maybe you have a problem with the connection from the PICO to the Wii U, but then I wouldn't expect defuse to work.

Yeah me neither. It seems strange. I'll go with it for now. Just trying to figure out how to boot into stroopwafel as there is no option in the minute menu for it. Or is this something that's only display in the console? It also seems that when I resize my sd card to over 1gb I loose the hdmi output.

If I choose Patch and boot ISO I get that slc:/sys/title/00050010/1000400a/code/fw.img is not an ancast image. Failed to load IOS with matches.