Tutorial  Updated

How to setup USBMLC to fix system memory error 160-0103 (failing eMMC) without soldering

What is this for?



If you are encountering Error Code 160-0103 "There is a Problem with the system memory" or your Wii U is freezing at bootup or during Factory Reset it is likely that the eMMC Chip is failing.
This guide goes into fixing this Error 160-0103, by using a USB HDD to replace the failing eMMC, in a similar way redNAND does by using the SD card.
This guide will reinstall the system files to the USB HDD. If the HDD is already Wii U formatted and you already have games and saves on the USB HDD they *should* be preserved, but if something goes wrong, data might get lost.
It can also be used together with the USB Partition plugin.

This is a new Method, although I did some testing, there might still be some bugs lurking, if you want something more tried and tested, then I recommend redNAND

System updates don't seem to work, so please don't use vWii Decaffienator with this


Please note there are other possible causes for the 160-0103 error (like a CBHC brick). Also there are other possible solutions to this problem. To see if this Tutorial is right for you, check out the Ultimate Wii U Troubleshooting Guide

1751761597303.png


What this will do


We will first install ISFShax, which is an early exploit that runs before the operating system loads. This allows us to patch the OS to redirects the reads and writes, that normally go to the eMMC, to a USB HDD. So you will need to have the SD card in the Wii U to use it, as that is now it's new internal memory.
In this tutorial we are only redirecting the MLC. If you plan to try some dangerous things in the future, you can still mess up your system SLC and SLCCMPT. If you want to use this for such experiments consider using full redNAND, where all 3 devices get redirected.

What you need


  • SD card with at least 2GB (If you really need to there is a way to do it with a smaller SD; but this guide requires 2GB for simplicity)
  • Reliable USB Storage Device (Flash drives are notoriously unreliable, if they are not branded for endurance)

It is recommended to only have one USB Storage device connected, since this plugin will simply use the first one it finds. Generally USB devices in the back seem to be detected first, but as HDDs need some time to spin up it's a race between them. If you want to have a HDD for vWii I recommend you look into the USB Partition plugin to consolidate both on one HDD. Connecting another USB storage for data management after boot is still fine.

Installing ISFShax


For installing ISFShax follow this tutorial: https://gbatemp.net/threads/how-to-set-up-isfshax.642258 but skip the "Autoboot" part for now.
If you already have ISFShax installed, make sure to update the ISFShax files on the SD to the latest version.

Optional: Partitioning the HDD


If you want to partition the HDD to use part of it for vWii or Homebrew:
  • follow the instructions for partitioning the USB disk here: USB Partition
  • copy the 5usbpart.ipx to wiiu/ios_plugins on the SD card
  • copy the 5usbpart.ipxor 5upartsd.ipx(for the SD emulation) to hax/ios_pluginson the SD card

Optional: Backing up savegames


If your Wii U can still run Tiramisu or Aroma: https://wiiu.hacks.guide/#/ you can use SaveMii to back up your save games.
If it can't you then you probably already used UDPIH to install ISFShax. Launch the recovery again using UDPIH and then use the Dump SLC + MLC option. Your SD card needs to have at least 64GB for that (for a 32GB console). You then need to merge mlc.bin.part files in the right order and can then extract the savegames using wfs-extract.

You can also backup your saves after setting up redNAND, even if your old system isn't booting anymore, see this post for more details: https://gbatemp.net/threads/fixing-...ing-rednand-with-isfshax.642268/post-10417998

If you lost the password to your NNID and can't recover it because the email doesn't exist anymore, you can transfer it. This is only a last resort option. If you still have the email address, it would be better to use the "Forgot Password" option now, as you won't have it on the new system.
There is also the option to use a password reset option on the PC. For that you need to create a Nintendo Account and then link the NNID to it. When linking it will ask for the password and give a reset option using the email.

Keep in mind this transfer only works on the same console and only if you don't do a Factory Reset.
To transfer the NNID It's enough to copy the account.dat file over.
You can use ftpiiu everywhere to save it to the PC for now. Just copy the whole /storage_mlc/usr/save/system/act/ folder to the PC. In that folder you find one subfolder for each user and in that subfolder you find an account.dat (it's a plain text file, you can open it with notepad). The folders are numbered in the order the users were created.

On the new rebuild mlc the numbering will start again with 80000001. If the user with the NNID had a larger number just create new users on the new system until you reach that number. Then you can copy the account.dat back and reboot.
After that you should be able to access the eShop and download the games again.

Installing the USBMLC plugin


Download the 4usbmlc.ipxof the latest release from here: https://github.com/StroopwafelCFW/wafel_usb_mlc/releases and copy it to both wiiu/ios_plugins and hax/ios_plugins on the SD card.

Rebuilding the MLC


  1. Download all the mlc system titles for your region from NUS. This can be done conveniently with MLCRestorerDownloader by @Xpl0itU. To use the MLCRestoreDownloader, you need to extract it and then copy the otp.bin from the SD card to it's directory. Then start the Downloader and select mlc and then your consoles region.
    You will get the output/MLC/{region} directory, which contains a directory for each title. In total there should be 52 titles totaling ~1.1GiB.
    If your console has an older firmware also get the latest SLC titles.

  2. On the root of your SD card 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. Put the wafel_setup_mlc.ipx on the SD card only in wiiu/ios_plugins.

  4. Make sure only the USB HDD you want to use is connected.
    If the HDD isn't already formatted by your Wii U, then the setup will format it, erasing all data on it

  5. 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. (shouldn't take longer than 30 mins)
    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 inital setup on the next boot.

  6. Check that the wafel_setup_mlc.ipx deleted itself from wiiu/ios_plugins folder on the SD.

  7. Select Patch (sd) and Boot ios (slc) again. If everything worked, the initial setup should launch.

  8. Follow through with the initial setup.

  9. (Optional) delete the wafel_install folder to free up space

Copy the plugins to the SLC


For now you need to have the SD card inside the console to boot the USBMLC. Without the SD it would just boot your old system from the internal memory.
To copy the files to the SLC so it also works without the SD in go back to the ISFShax guide and follow the instructions there for setting up Aroma and then copying the plugins to the SLC.
**Keep in mind, this will be undone by a factory reset**

Setting up autoboot


To not have to navigate the minute menu on every boot create the file sd:/minute/minute.ini with the following content:
INI:
[boot]
autoboot=1
autoboot_timeout=1

This will automatically load the plugins installed to the SLC. You can also set autoboot to 3 to load the plugins from SD, which is nice for testing new plugins.
 
Last edited by SDIO,
I test this and found that if use wafel_sd_usb.ipx in same time, the Wii vc will not work,just reboot back to wiiu system,when I delete wafel_sd_usb.ipx the Wii vc work again.
The wiivc app was installed on nand(usb-mlc).

 
you also have the sdusb plugin, that might cause problems with vWii when combined with the others
 
One question here:
System updates don't seem to work, so please don't use vWii Decaffienator with this

Is Rednand also affected by this "restriction"? Or only if you use USB MLC plugin and install the CafeOS on USB? I'm asking because I have a bricked console revived by PTB, and also some issues under vWii...:wacko:
 
OK, then this console needs redNAND~~ thank you.
Post automatically merged:

Annnd another question: Since SDD/HDD is used, is there any size limit for the system partition? , I remember on redNAND it has to be the multiple of 64MB, is this requirement gone for USBMLC?
 
Last edited by neverendsDull,
No, updates should work on redNAND
Tried this on another PTB revived JPN console, basic info:

01 board, black 32GB, Hynix MLC, minute reported 5.5.0-5.5.4 IOSU version, so first time of OS install I use "ios_orig.img" method and it worked.

Tried on a parted USB SSD (240GB, 1st partition FAT32+32k, 80G, 2nd NTFS, all the left space, with a Y-cable proved to be working on another WiiU console) and a parted USB HDD (250G, similar 2-partition setup, with individual power supply also proved to be working on another console), both failed:

No matter what version of MLC (SLC titles already updated during first setup) OS I installed (tried USA for region change, but went wrong so also tried JPN), mlc_setup.log shows no error during setup, and these two:
Set region to 1: 0
SetInitialLaunch 0: 1


all other are either 0 or 00000000, so install finished without issue. But it got stuck during initialization:

First stuck when finished time and network setup and is about to jump to Mii maker for profile setup, if force reboot it can continue,

Second stuck when finished Mii maker and returned to WiiU menu, it stucked at "Please wait..."
stuck_pls_wait.png


Which part was wrong? Should I assign space a multiple of 64GB to 2nd OS partition? Nope, tried that, this is not the cause.

ios_plugins used (all are latest version):
00core.ipx
4usbmlc.ipx
5isfshax.ipx
5usbpart.ipx

tried also 5payldr.ipx to enter Aroma directly, result is the same.
Post automatically merged:

No, updates should work on redNAND
Tried redNAND on the same console and it worked...
Apparantly at the first stuck timing, OS will black out and load mii maker, and at 2nd stuck timing, the OS will first suggest power saving feature then went back to main menu.

No idea why USBMLC can not go beyond these two points...
 
Last edited by neverendsDull,
Using the working redNAND SD card, I did some tests on the parted USB HDD (250G, similar 2-partition setup):
It can be recognized and formatted in system settings
install1.png

used wup installer installed Kirby and Angrybirds on to it, played fine
kirby.png

finished vwii mod stuff, placed Kirby Wii on the first FAT32 partition, can be recognized by USB loade GX, entering and saving is OK.
kw2.png

Post automatically merged:

Wierd,on another console, the same setup worked, system initialization finished without problem. Similar hardware, 01 board, Hynix MLC... but this time it can go over the setup the first time even minute complaining ios is 5.5.0-5.5.4
Post automatically merged:

Does the HDD work when you use it normally on that console?
Ok did some more experiments.

On console A that can use USBMLC, it is totally fine, can finish initialization without issue. I mentioned it was on 5.5.0-5.5.4, then I tried update SLC titles on it and retry USBMLC process, still OK, zero issue.

On console B, I tried USA/JPN/EUR MLC titles, even reinstalled SLC titles, changed USB ports, same symptom: stuck at entering mii maker, if force power off, then mii maker passed, but will hung at displaying "Please wait..." indefinitely, for a normal console the following screen will be displayed and then enter main screen, if using redNAND on console B, it will also display the following and finish initialization, tried USA and JPN MLC titles:

faultscreen.png


off topic, after trying several USBMLC setup on the 250G HDD, when I switched back to redNAND on console B (had to go another redNAND process to enter the OS), the two games (Kirby rainbow and Angry birds) are still there with save intact...
and now I have two icons for every system apps except the optic drive, all of these system apps works however.

mainscreen.png
 
Last edited by neverendsDull,
Probably you have the system titles installed for two differnet reasons. The Disc app, is part of the menu and no extra title.
Do oyu have a flash drive you could try on console B?
 
Tried a 256GB TF card reader as USB media on console B, still no juice, same pattern, stuck at entering mii maker, if force power off, can pass mii maker then stuck again at "Please wait..."

Is it possible to extract maybe syslog under this stat? I tried recovery menu it did not work, strange.
 
You could dump the logs twice and let it run into the problem in between, maybe it writes a log.

Also if you have a compatible USB serial adapter, you could use the aroma usb serial plugin to try to see whats going on.
 
  • Like
Reactions: DolphinPussy
You could dump the logs twice and let it run into the problem in between, maybe it writes a log.

Also if you have a compatible USB serial adapter, you could use the aroma usb serial plugin to try to see whats going on.
Damn I forgot minute! Dumped syslog and factory log from it, file attached FYR.

A bit strange, the most recently is on 7.31 of #84, and #83 is in 2017? seems no log is written when system hangs?
Post automatically merged:

I compared the hash of every log files before and after the mii maker hung, and confirmed no sys log is written in between... :wacko:

and the meta.bin stays the same.
 

Attachments

Last edited by neverendsDull,
Hello, I apologize if this is a dumb comment or question, I only recently hacked my system but started getting errors while trying to do things on the console so I was attempting to use this method in order to solve those. I followed this guide along with isfhax and partitioning the hard drive and I have gotten stuck on step 5 of rebuilding the MLC. When I select patch sd and boot slc it does not seem to do what it is supposed to and gives me the screen attached. I'm not very knowledgable in this sort odlf stuff so I wpuld appreciate help or suggestions.
 

Attachments

  • 20250817_195909.jpg
    20250817_195909.jpg
    975.2 KB · Views: 59
did you make sure the USB HDD is partitioned correctly? Did you use it partitioned before? If not you could try to first do it without the partition plugin to see ifthat works and if that worked you can try again partitioned
 
did you make sure the USB HDD is partitioned correctly? Did you use it partitioned before? If not you could try to first do it without the partition plugin to see ifthat works and if that worked you can try again partitioned
I had not used it partitioned before. I was able to rebuild the MLC without the partition plugin and successfully get to the system setup but I'm not sure how I would use the hard drive as partitioned if the setup seems to format the whole drive, unless i'm misunderstanding something.
 
ok, so we know the drive and the mlc setup work for you, now we can add the partition plugin back and you can try again partitioning the drive and running the setup again
 
ok, so we know the drive and the mlc setup work for you, now we can add the partition plugin back and you can try again partitioning the drive and running the setup again
Thank you for your patience and help! It seems to have worked now and I was able to rebuild the mlc while keeping the other partition in tact. I suppose it was because of an issue with my formatting and partitioning of the hard drive or because I had not used it on an actual wii u before. Thank you again :)
 

Site & Scene News

Popular threads in this forum