This is a full video tutorial that shows from start to finish everything that needs to be done in order to diagnose a Wii U console with the error code 160-0103 and ultimately repair the console back to a functioning state. This video also pertains to Wii U consoles with error code 160-2215, 105-0644, consoles with corrupt data, consoles that won't factory reset, consoles stuck in the factory reset loop as well as consoles that freeze on the Wii U logo menu. The assumption behind error code 160-0103 is that the console has a bad eMMC and it needs to be repaired using a NAND-AID or redNAND. For the purpose of this video I am focusing solely on the NAND-AID repair, as this is a permanent fix for the console, whereas the redNAND is more of a temporary fix that has some hiccups/limitations that can be encountered when launching Wii Virtual Console games.

The written tutorials for using the tools in this video are linked below and can be used along side the video I have created. I am not the creator of these tools or these guides, with the exception of the NAND-AID installation guide/video. 

This video is using the most updated recovery tools as of 2/15/2025. So if you are following this video to repair a Wii U console please make sure you are using updated recovery tools. In order to make this easier I have attached all the recovery tools I used to this post called "Allfiles.zip". The zip contains wafel_setup_mlc, ISFShax, Recovery Menu and the additional files necessary to make these tools work. To try and be as clear as possible, UDPIH & MCLRestorerDownloader, including the 52 mlc title files and 5 slc title files are not include in the zip, you can download those separately. The reason for this is because those tools haven't changed anything on how they are used. You can download the zip at the bottom. I am doing this because these tools are maintained by other individuals and as they get updated things sometimes change and this can lead to confusion. 

Links used in this video are below:

UDPIH
ISFShax Install guide
Zip File for all files required
Hex editor
hexadecimal to decimal converter
Modulo Calculator**
NAND-AID Installation guide
wafel_setup_mlc
MLCRestorerDownloader

** There is an error in this video about how to read the meta.bin in order to identify which log file is the newest. The hex editor gave us 00000006 which converted to decimal is 6 and because of the low number I never showed how to use a modulo 100 to find the remainder. The link above is for doing that calculation. You want to put the decimal in the dividend box and 100 in the modulus box.

If you find an error in my video please let me know so that I can correct it. I am not perfect and creating long videos like this means I am probably going to overlook a mistake or error in the video.

The full video tutorial can be viewed below:
Note: Due to the limit of the description allowed on youtube I couldn't add this. A bit disheartening after the amount of effort I put into this video, but for some reason the 4K version of it, which provides far better visual clarity especially during the minute menu scenes isn't available on youtube. I don't currently know why this is, as I have previously uploaded 4K footage. The only difference this time is the length of the video. I don't know if youtube has limits for smaller channels. This is something I will have to look into and hopefully I can find a solution to the problem. I believe this video will still provide plenty of value to those wanting to repair Wii U consoles. Its just unfortunate that I created it in 4K because I wanted to make sure the minute menu was easy to see and read after being uploaded to youtube. I am well aware of the youtube compression and how it effects overall fidelity of videos. In my opinion 1080P for this video has poor fidelity.

Saved for future revisions

I have no idea how consistent or not this is across the log files of different Wii U consoles throwing errors, but on one I was trying to diagnose each log file had, in the last line, something like the following:

MCP: life time number of fatal errors - 2074

I just found the file with the largest number, because in my case it was incrementing by one in each successive file until suddenly the number dropped. In this/my particular case, 77.log had the largest number, so I figured that was the most recent file.

I don't know, but if that is fairly common, at least it may be another way to determine the latest log file if meta.bin is corrupt.

Quote from: tr7oy on Feb 26, 2025, 07:46 PMI have no idea how consistent or not this is across the log files of different Wii U consoles throwing errors, but on one I was trying to diagnose each log file had, in the last line, something like the following:

MCP: life time number of fatal errors - 2074

I just found the file with the largest number, because in my case it was incrementing by one in each successive file until suddenly the number dropped. In this/my particular case, 77.log had the largest number, so I figured that was the most recent file.

I don't know, but if that is fairly common, at least it may be another way to determine the latest log file if meta.bin is corrupt.

I don't know. I have always used the standard way of calculating the newest log file using the meta.bin. My most recent video was incorrect. There was nothing wrong with the meta.bin. I just made a mistake and forgot how to calculate it. If the meta.bin is missing, which I have seen multiple times when repairing these consoles, then your method may also work. That being said you can also aggregate all log files into one and just search for the media error that indicates the eMMC is failing. I think when this becomes a hassle is if your trying to diagnose a problem that is occurring during the rebuild of the MLC and you end up having 99 log files and cannot determine which one is the newest.   

Edit: I took a look at a bunch of logs and it would appear that what you found is correct. The hassle is having to look through all the logs to find the largest number. Definitely not the ideal way to do it, but if meta.bin is missing it appears to work. I only checked logs from 4 consoles, so its possible that there is a situation where this might not work.