Purchased another Wii U console that isn't working. This one was 10 dollars because it has no audio/video output according to the seller. I figured I would take a crack at it and see if I can fix it. So far I have 2 fully working Wii U that had bad eMMC. I don't know if this one has a similar problem or if its entirely something else. Lets dive into it.

Its a model WUP-101(02) 32GB



Based on the ports on the back its an earlier model from the first production of the Wii U. The later models are all black in the ports. This doesn't mean it necessarily has a defective eMMC, but without system information dump, logs or opening the unit up right now I wouldn't know if it has one of the notorious Hynix chips. Before we go that route I want to see if its actually booting and we are just getting a black screen or is the console not booting at all.

Plugged the Wii U into power & HDMI. All I got was no signal on my tv, but the console does boot with a steady blue light on the front, which is interesting. I shut it down and tossed in the recovery memory and used a UDPIH and got the most beautiful display out!!!



Yikes, not sure what the problem is. I am going in blind here so I am going to attempt to navigate the recovery menu and get a log file dump to see what might be going on. If I get a log file dump, that proves the console is booting and just not displaying an output properly.

Recovery Menu I am using is attached to this post.

In order to get logs I have to press Eject 8 times and Power 1 Time. Problem is sometimes pressing the eject button doesn't move the cursor in the recovery menu.

Well I was able to dump the logs, but unfortunately there are no logs. This isn't looking good at all. However on the other hand it proves that the recovery console is indeed working so I wonder if this is a hardware problem. I am going to try to blindly dump the SLC/MLC. If I can dump those and they are intact mostly, we may be able to salvage this console and fix it. If I cannot dump those then this console probably isn't fixable.   

I decided to run the MLC Checker instead since it creates a log file. I did interrupt it after nearly 9 hours. It didn't finish as the log file doesn't stay Finished near the end. It has alot of corruption from what it did make it through. I don't have any way of knowing if this is 10% of the MLC or 90%. I might run it again and let it go for a couple days.

Here is what the log shows:

ReadDir;/vol/storage_mlc01/sys/title/00050010/10040100/;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10041100/code/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10043100/code/cos.xml;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10043100/code/title.tmd;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10043100/content/drc_fw.bin;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10044100/content/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/code/updater.rpx;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10045100/content/layout/;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/EU_Dutch/;-0003001B
ReadDir;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/EU_English/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/EU_German/updater.msbt.zlb;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/EU_Italian/updater.msbt.zlb;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/EU_Portuguese/updater.msbt.zlb;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/JP_Japanese/updater.msbt.zlb;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/US_French/updater.msbt.zlb;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/US_Portuguese/updater.msbt.zlb;-0003001B
ReadDir;/vol/storage_mlc01/sys/title/00050010/10045100/content/message/US_Spanish/;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10045100/content/shaders/;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/content/sound/SE_BAR_WAITING.dsp;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/meta/bootDrcTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/meta/bootMovie.h264;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/meta/bootTvTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10045100/meta/iconTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/code/set.rpx;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/content/Common/Package/Set.pack;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/content/Common/Package/Set2.pack;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/content/Common/Sound/Set/cafe_barista_set.bfsar;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10047100/content/Common/Sound/Set/stream/;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/content/Us/Model/ConfigTvCap_Us.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/content/UsEnglish/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/content/UsFrench/Message/AllMessage.szs;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10047100/content/UsPortuguese/;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/content/UsSpanish/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/meta/bootDrcTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/meta/bootMovie.h264;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10047100/meta/bootTvTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/code/pcl.rpx;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/content/Common/Package/Pcl.pack;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/10048100/content/Common/Sound/Pcl/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/content/Us/Layout/ParentalRating_usa_fr_Us.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/content/Us/Model/ParentalTvCap_Us.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/content/UsEnglish/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/content/UsFrench/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/content/UsPortuguese/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/content/UsSpanish/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/meta/bootDrcTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/meta/bootLogoTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/meta/bootMovie.h264;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/meta/bootTvTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10048100/meta/iconTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/code/acs.rpx;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/code/app.xml;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/code/cos.xml;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/code/title.fst;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/code/title.tmd;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/content/Common/Package/Acs.pack;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/content/Common/Sound/Acs/cafe_barista_acs.bfsar;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/content/Us/Model/AccountTvCap_Us.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/content/UsEnglish/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/content/UsFrench/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/content/UsPortuguese/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/content/UsSpanish/Message/AllMessage.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/meta/bootDrcTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/meta/bootLogoTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/meta/bootMovie.h264;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/meta/bootTvTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/meta/iconTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10049100/meta/meta.xml;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/1004a100/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libfont4_sdk20000.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libjpeg.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libopenssl.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libpixman.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libwk_peer.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libwk_peer_access.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libwkc.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libxml2.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/mvplayer.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/title.fst;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/title.tmd;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/wave.rpx;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/content/browser/effective_tld_names.dat;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/content/browser/MediaControls.css;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/content/browser/rootca.pem;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/content/browser/Skin.dat;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/content/browser/UserCss.dat;-0003001B
ReadDir;/vol/storage_mlc01/sys/title/00050010/1004b100/content/font/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/content/initial.oma;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/1004b100/content/layouts/;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/1004b100/content/mediaplayer/;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/1004b100/content/message/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/content/preload.oma;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/1004b100/content/shader/;-00030041
ReadDir;/vol/storage_mlc01/sys/title/00050010/1004b100/content/sound/;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/meta/bootDrcTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/meta/bootLogoTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/meta/bootMovie.h264;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/meta/bootTvTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/meta/iconTex.tga;-00030041

When I attempt to check the SLC it creates no log file even after running for over 10 hours. So there may be  something wrong with the SLC. I don't know if this means the console isn't repairable but its looking that way. My understanding is that if the SLC is missing and there is no backup there is no way to repair it because it has to stay in the synced state with the MLC. I still have to open it up and inspect it. I will have to do that another day.

I took the console apart and it is indeed a Hynix chip. See picture



I inspected the HDMI Port and the rest of the board under a microscope to see if there was any obvious signed of damage. There was nothing I could find except a small section with cracked solder joints on 2 components, a fuse and a capacitor. Marked in the picture below:



My camera isn't good enough to see the cracked solder joints. The naked eye cannot see them either. They are obvious under a microscope though. I repaired them and plugged the console back in to see if the HDMI output was fixed. Its not. I believe this is a software issue.

I was able to blindly load Minute on the console, by hitting eject 18 times, power 1 time, eject 1 time and power 1 time.


I was able to dump SEEPROM & OTP from Minute and I am currently dumping the SLC-RAW. I am also going to dump the SLCCMPT-RAW. 


Perhaps this is a good sign that this console may be fixable. I am going to install ISFShax and see how far I can get.

YES!!! Alright with the minute menu I was able to dump the log files and the console does indeed have them. 99 in total actually. Added to this post.

Look at what we have in them too....the curse of the Wii U console...Another bad eMMC
01:48:35:267: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
01:48:35:323: mmc_core card err: idx=3, lba=8798208, blks=1024, xfer=0x1, ret=0x00200b40
01:48:35:358: mmc_core card err: idx=3, lba=8798208, blks=1024, xfer=0x1, ret=0x00200b40
01:48:35:359: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
01:48:35:359: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
01;48;35;236: FS: READ_FILE      upid:[15] sts:[MEDIA_ERROR] hnd:[0x3b72240] dst:[0x18e97940] size:[1] cnt:[1048576] pos:[0]
01;48;35;236: SystemFatal(core1)

I think I am going to install a NAND-AID to this console and see if I can rebuild the MLC. Perhaps the eMMC in the console is so far gone that it cannot load even the basic requirements to get video out. I will do some more testing and then move forward with a NAND-AID and just rebuild the file system.

Did some testing, eMMC is def too far gone to recovery data from. So I installed the NAND-AID and this time I tossed in a 64GB SD Card. It turns out the Wii U without any modifications actually supports up to 64GB cards as a replacement eMMC. If you want larger cards you have to install and permanently run an ISFShax mod. I am going to rebuild the file system and see if we can get this Wii U working again.

NAND-AID installed successfully. The rebuilding of the file system went without a hitch. That being said, Long story short, it was working great until I went to install an update for a game and got Error 105-3016. The video shows exactly what happen. In a nut shell I tried to delete some corrupt data towards the end and after 20 minutes of it sitting on the deleting data screen I decided to pull the plug. This was clearly a mistake. The console turns on with a solid blue light. It will not boot into the Wii U menu. It will not load the recovery menu using the UDPIH. I am unable to get it to do anything.

A video of everything that happen is below. Sorry for the loud Wii U Menu audio among other audio issues, its the first video I have created and there is much room for improvement. 


I will have to do some research and see if I can somehow get the console to come back to life. I am not entirely sure what happen from unplugging it from power. Maybe it corrupted the SLC, if that is possible. At this point it appears to be bricked.   

I am unable to get the Wii U to do anything. Blue light turns on, it doesn't respond to UDPIH/Recovery Menu. Disc drive does something interesting if I hit the eject button it will spit out a disc if there is one in there. Doesn't matter how long I leave it on light stays blue and eject continues to work.

Its a confusing situation as the console was on for 3 hours while I rebuilt the MLC, Configured the Wii U Menu and then attempted to install an update/troubleshoot Error 105-3016. All it took was that single pulling of the power adapter after 20 minutes of it sitting on deleting data do not power off screen to apparently brick/kill the console. In hindsight I should have let it run for a couple hours to see if the delete message would clear. I can only assume that pulling the power plug damaged the SLC or something else happened. At this point I am going to move on to another console.

Hi tzirf,

just saw this. An interesting problem indeed.
This is probably either a problem with the SD card or the scfm.img on the SLC. Can you sent me the latest logs you dumped, they might give a hint which one it is. The SLC checker in the recovery doesn't check the scfm.img (which isn't possible for several resons)
The 105-3016 error probably has nothing to do with the 105-3015. At least the cause seems to be a completely different. 105-3015 is caused by just wrong permissions while 105-3016 were corrupted data. The Wii you probably couldn't delete the download because either it Filesystem Metadata of that file (and not the data in the file itself) became corrupt or because there was a corrupted folder (which is also FS Metadata)

When it hung, waiting longer wouldn't have helped. It hung because something went wrong with the mlc which also is the cause why it doesn't boot anymore.

In addition to looking at the latest logs (which isn't always the one with the highest number, because it wraps around at 99), you could try to image the SD in a PC to see if that gives any errors and then also if you can writ back to the SD. Also I would recommend checking the soldering of the NAND.
If the problem isn't just the SD card failing and going ro, then you might need to defuse since you removed ISFShax. That shouldn't be a problem with your soldering skilly, it's just a little annoying. But first we should check out the other things.

A few small things:
You will always get a orange blinking LED during the setup, if the mlc was already setup, even if there is no corruption. It will try to create some folders, that will fail, because they already exist then that turns the LED orange. You can see what exactly failed in the log written by the installer to the SD.

UDPIH works with ISFShax installed, you just need to boot and insert the pico at the right time. If you modified the Pico formware with a sleep, so you don't have to do the timing manually and just plug it in before, the timing with and with out ISFShax will even be the same, as USB power only gets turned on by IOSU and from that point the time is constant.

I found your voice very quiet, especially in relation to the Wii U sounds, maybe you can increase the volume in the future.

Maybe put a warning before the flickering or cut it out, because it can cause seizures for some people.

Hello SDIO,

I assume you are the one who created these wonderful tools and made them available. Thank you for sharing them with everyone online. Without them I wouldn't have been able to repair any of the Wii U consoles that I have repaired and so far I am up to 10 consoles fixed and only 1 not fixed. Some of these I haven't posted because they were completed before I started documenting the repairs.

I appreciate the suggestions. I have the console put back together, unfortunately I removed the NAND-AID already, and in doing so I tore a couple pads off at the resistors in front of the NAND. I cannot take a picture of it right now as the console is still assembled. I don't think I can get logs or anything at this point. The console doesn't respond. I did run wire from the traces to the resistors and verified with a multi-meter that they were connected.

As for the video, yeah its my first video ever, its rough. Thanks for the feedback. I should be able to make better videos in the future.

I didn't have plans on cracking this Wii U back open, but if it can be saved using Defuse, I am willing to go back to working on it. The only logs I have are in a post above. Unfortunately I wasn't able to get log files to dump after the console stopped responding to the recovery menu/UDPIH. 

When you say

QuoteUDPIH works with ISFShax installed, you just need to boot and insert the pico at the right time. If you modified the Pico formware with a sleep, so you don't have to do the timing manually and just plug it in before, the timing with and with out ISFShax will even be the same, as USB power only gets turned on by IOSU and from that point the time is constant.

Does this mean you can have ISFShax installed and still get to the recovery menu by inserting the Pico at the correct time?

You dumped the logs in the video, after the error happened the first time. If you still have them, they might tell us what was failing.
What did you do with the SD card, after you removed NAND-AID? If you didn't image it and overwrote it, you would have to defuse in any case.

Quote from: SDIO on Feb 12, 2024, 07:52 PMYou dumped the logs in the video, after the error happened the first time. If you still have them, they might tell us what was failing.
What did you do with the SD card, after you removed NAND-AID? If you didn't image it and overwrote it, you would have to defuse in any case.

Yes I believe these are the log files. I have attached them to this post. Also no the SD Card I believe I wiped and used in another Wii U as its been difficult for me to find Micro SD Cards for these consoles and I needed one at the time. I am okay with trying to do defuse. I don't know anything about it. Sounds like it requires a bunch of micro soldering though based on what you said in your previous post.

Hm the zip is missing the meta.bin, which tells us, which is the latest log.

For defuse have a look here: https://github.com/shinyquagsire23/wii_u_modchip/tree/main/pico_defuse The testpads are all fairly large and easy to solder to.