Have another Wii U console. This one turns on, gets to the Wii U menu and will play games. You can even do a factory reset. However if you attempt to update the console, it will begin the firmware update and then you get error 162-4065, then the console freezes and a hard reset is required to get back to the Wii U menu. If you attempt to do a download of the update through the download management app, it will throw error 105-0644. Pictures of the errors below:




System information. Once again its a Hynix chip. Early production as well.



I am going to do some further testing of the console. I have made it a habit to check the MLC and to rebuild the MLC before concluding its a failed eMMC and installing a NAND-AID.

I took a look at the log files and the typical error we see on these problematic consoles is present:

00:01:00:633: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:01:00:647: mmc_core card err: idx=3, lba=55199488, blks=128, xfer=0x1, ret=0x00200b40
00:01:00:666: mmc_core card err: idx=3, lba=55199488, blks=128, xfer=0x1, ret=0x00200b40
00:01:00:666: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:01:00:666: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)

Full log files are attached.

Did an MLC Check and the following came back as errors. Not nearly as bad as others I have worked on.

ReadFile;/vol/storage_mlc01/sys/title/00050010/10044100/content/lang_00.bin;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004b100/code/libwkc.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004c100/content/Common/Sound/Ply/stream/BGM_PLY.bfstm;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1004e100/code/safe.rpx;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1005a100/code/doors.rpx;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/1005a100/content/art/FE/FEGroupMainUI_res.data;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10062100/content/Common/audio/wagonU_sound.bfsar;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10062100/content/Common/Layout/btnServ_00.szs;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050010/10062100/content/Common/Layout/Cursor.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050010/10062100/content/Common/lodging/convert_test/WagonMap2/WagonMap2.szs;-00030041
ReadFile;/vol/storage_mlc01/sys/title/0005001b/1004f000/content/00/Common/Iwnn/dic/JA/32/njubase1.a;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/0005001b/1004f000/content/00/Common/Iwnn/dic/JA/32/njubase2.a;-0003001B
ReadFile;/vol/storage_mlc01/sys/title/00050030/10010109/content/Common/Package/Hbm.pack;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050030/1001310a/code/libwkc.rpl;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050030/1001510a/content/Common/Package/Frd2.pack;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050030/1001510a/meta/bootTvTex.tga;-00030041
ReadFile;/vol/storage_mlc01/sys/title/00050030/1001910a/content/memo/memo.arc;-00030041
OpenFile;/vol/storage_mlc01/usr/save/system/pdm/80000006/PlayEvent.dat;-00030015
ReadFile;/vol/storage_mlc01/usr/title/00050000/10105700/content/fonts/DroidSansFallbackFull.ttf;-00030041
ReadFile;/vol/storage_mlc01/usr/title/00050000/10105700/content/fonts/DroidSansJapanese.ttf;-0003001B
finished;/vol/storage_mlc01;-00000014

I went ahead and rebuilt the MLC on this console. At the same time I upgraded the firmware to version 5.5.6U. As seen in the picture below the firmware updated successfully. 


Its important to understand that a firmware ( Wii U System Software) upgrade doesn't mean the MLC is working. As the firmware is stored in the SLC, where the operating system known as IOSU and CafeOS are stored along with tickets for installed titles and some configuration files. Now you might be asking yourself, well then why does a firmware update fail if its stored in the SLC. The reason for that is because it downloads to the MLC. Often what happens is the file downloads and saves, but then when the installation actually happens the MLC reports that it cannot read data error free and things come to a screeching halt.

I did use the recovery menu to check the SLC/MLC after I rebuilt the MLC and there are 0 errors with both. Additionally the logs show no error on the MLC currently. All this really means is that the rebuild was indeed successful and currently there is no corrupt data.

I have been testing this Wii U by playing games as well as installing games & updates. Everything has worked without a hitch so far. It is possible that this console didn't have a failing eMMC and and the problem was corrupt data. Just because its a Hynix early production doesn't mean its failing. I will continue testing it for a few days to see if any corrupt data errors show up in the log files. I might actually keep this console and continue running it for weeks or months. I am mostly curious if the eMMC is fine or if the corruption will show back up in time as it is possible to rebuilt a MLC on a failing eMMC and have it appear to be fixed but after a few weeks or months it runs into the same problem, albeit usually worse. The reason for this is the MLC doesn't know there is an issue until it tries to read data back. So writing data to the MLC may appear to work, but then when the MLC is asked to read that data back by the system it finds out there are errors present. 

This console has a bad eMMC. I want to thank SDIO for providing the information to understand the MLC Checker log.

Quote-30041 is MEDIA ERROR
-3001B is DATA CORRUPTION ERROR

you have lots of 30041, so bad eMMC for sure. The 3001B might be the result of the corruption becomming so bad that the ECC in the eMMC couldn't even detect the errors anymore, or the eMMC just returned bad data (I noticed that happening on single block reads, on multiblock it would fail because of ECC errors, but on single block it would still return something)

I have looked over the MLC Checker log and there are many 30041 errors, so this indicates the eMMC is bad. I will be installing a NAND-AID in this console to provide a permanent fix.

Finally got a NAND-AID to install in this console. I will be installing it in the next couple of days.

If you are going to rebuild the MLC, try the new wafel_setup_mlc and see if that fixes the Game Update problem when ISFShax is removed.

Quote from: SDIO on Mar 13, 2024, 05:41 PMIf you are going to rebuild the MLC, try the new wafel_setup_mlc and see if that fixes the Game Update problem when ISFShax is removed.

I didn't plan on it. However I can certainly test it for you.

Hello Hynix chip....


Lets get this NAND-AID soldered in place....


Looking much better now! All that is left is to rebuild the MLC. Going to be using the new version 2.0 wafel_Setup_mlc that SDIO released, which can be downloaded here. I am going to test to see if the folder permission error related to ISFShax being removed after rebuilding the MLC has been fixed. 

Wii U is fully repaired now. I installed a NAND-AID and rebuilt the MLC. I decided to do this twice on this console in order to test and confirm that the folder permission error related to ISFShax being removed after rebuilding the MLC has been fixed. The error didn't show up either times I tested it. So I believe its been fixed, which is great news!

I was able to rebuild the MLC, start the console and do the initial setup, then remove ISFShax and download and install and update for Hyrule Warriors as well as download and install The Lost Reavers Notice and Wii Sports Club demo that download automatically when you connect any Wii U to the internet and enable spotpass.




Console shows the replacement MLC and that it has been updated to 5.5.6U. Another working Wii U 

I created a video showing the rebuilding of the mlc using version 2.0 wafel_setup_mlc and then uninstalling ISFShax. In the video you see that Hyrule Warriors update, downloads and installs successfully, which indicates that the folder permissions are intact. I have tested this now a half dozen times and I cannot get error code 105-3105 (this is the error you will receive if the folder permissions are missing) to show up after removing ISFShax.