Here I am again,

I started the process of fixing my 2nd Wii U that had no video output,
I was unable to use UDPIH, it just didn't work.
So the next thing what I did was to open Wii U and saw it had the famous Hynix chip.
After that I soldered a Pico to the mainboard of the Wii U and I was able to
use the minute menu.

After grabbing the logs I tried to find the last log file with the (video) tutorial on this site (youtube), from hex to decimal but I was unable to find it that way.

Because I failed here I did this my way and because I was using a linux system I entered this command:

grep -r "media" /home/user/Desktop/Wii_U/logs/
That output gave me one log file, 35.log

After inspecting it more, I don't see the "Media Error" but other things...


See log file

Can you upload all the logs and the meta.bin file? You can create a zip and attach it to your next post.

Made a zip from the logs map.

It would appear the SLC cache is corrupt or not accessible. Also based on the logs the console appears to have an issue with an update that is corrupt.

Since we have limited information to go on, I would recommend trying to rebuild the MLC because you have Defuse installed in the console there is no risk. Rebuild the MLC, then pull the new logs and check them for media errors related to the eMMC.

As a reference, you were correct that log 35 is the newest log file.

I just did an MLC rebuild after that I dumped the logs and after that I tried to start the Wii u (Patch (slc) and boot IOS (SLC).
But it's not continuing.

This is the output of the serial monitor:

minute

 Main menu

> Patch (slc) and boot IOS (slc) <
  Patch (sd) and boot IOS redNAND 
  Patch (sd) and boot IOS (slc) 
  Patch (sd) and boot sdmc:/ios_orig.img 
  Patch (sd) and boot sdmc:/ios_orig.img redNAND 
  Patch ISFShax and boot IOS (slc) 
  Boot 'ios.img' 
  Boot IOP firmware file 
  Boot PowerPC ELF file 
  Backup and Restore 
  Interactive debug console 
  PRSH tweaks 
  Display crash log 
  Clear crash log 
  Restart minute 
  Hardware reset 
  Power off 
  Credits 
Mounting slc...
ancast: no patch file `ios.patch`, stubbing...
ancast: reading 0xdfd200 bytes from slc:/sys/title/00050010/1000400a/code/fw.img
ancast: ...00000000 -> 01000000
ancast: ...00100000 -> 01100000
ancast: ...00200000 -> 01200000
ancast: ...00300000 -> 01300000
ancast: ...00400000 -> 01400000
ancast: ...00500000 -> 01500000
ancast: ...00600000 -> 01600000
ancast: ...00700000 -> 01700000
ancast: ...00800000 -> 01800000
ancast: ...00900000 -> 01900000
ancast: ...00a00000 -> 01a00000
ancast: ...00b00000 -> 01b00000
ancast: ...00c00000 -> 01c00000
ancast: ...00d00000 -> 01d00000
ancast: done reading
ancast: decrypting slc:/sys/title/00050010/1000400a/code/fw.img...
ancast: fini
ancast: IOS image is prod 5.5.5+
ancast: failed to open plugin `slc:/sys/hax/ios_plugins/wafel_core.ipx` for pre-parsing!
ancast: failed to open plugin `slc:/sys/hax/ios_plugins/wafel_core.ipx`!
Exception 4 (DATA ABORT):
Registers (0x1031cd80):
  R0-R3: 27f00000 65667301 ffffffff 27efffff
  R4-R7: 27f00000 00000000 10149b33 00000000
 R8-R11: 10164010 10164004 1016400c 10164014
R12-R15: 0000000a 1029cc70 10100994 10100b60
SPSR: 6000005f
CPSR: 200000d7
CR:   000530ff
TTBR: 101f8000
DACR: ffffffff
Abort type: Alignment
Address: 0x27f0001b
Code dump:
10100b50:  e59a3000 e59f11ac e5932018 e0833002
10100b60: *e593201c e1520001 0a000012 e59f0198
10100b70:  eb001723 e3e00001 e8bd8ff8 e5993000

EDIT: My bad I selected the wrong option in the minute menu. It had to be "Patch (sd) and boot IOS (slc)"
Now I see the start up of the Wii U.

EDIT2: Logs dumped after setting up Wii U.

The Logs after the MLC rebuild and set up of the Wii U.

Is the Wii U working now?

The log files you provided are identical to the original log files. Are you positive you uploaded the new log files? If you did that means the console didn't log anything new, which is strange because during a rebuild of the MLC the log files are cleared at the beginning of the process.

Indeed the Wii U is working now and I thought the same, it looks like the logs are the same.
I just took the SD card and removed the previous log files, I ejected the SD card and inserted it back in my computer to be sure all log files were gone. Ejected it back and put it in the Wii U, plugged in the Pico in my computer (USB) and connected the power to the Wii U and pressed the on button, but the weird thing I now have is that it takes a long time the Wii U boots up, nothing happens and suddenly it just starts. maybe 30 seconds (didn't really time it).

Then I dumped the sys crash logs and again it looks like they are the same.

Try playing a game that requires an update to be installed on the Wii U. If there is a problem with the eMMC it should end up generating an error and the log file may get updated.

Alternatively you can also try doing a factory reset, which should clear the log files. 

Well I did a factory reset, I tried some games I had here on disc but there were no updates it did.
After the factory reset the Wii U automatically shutdown. So when I booted it I immediately dumped the sys logs but there were 0 files on the SD card in the logs folder.

So I Booted the Wii U again and proceeded to set it up, afterwards I shut it down and booted again and dumped the sys logs but again no files.

Does this mean the MLC memory (Hynix) is OK ?

Although I have a NAND-Aid here, bought one from v10lator.

No it doesn't mean the eMMC is okay. Many of these failing Hynix chips degrade slowly over time. I have had a few of these consoles with similar symptoms that I rebuilt the MLC and used for a few weeks through a month or so and sure enough all 3 of them eventually ran into a system error because the Hynix chip was bad.

Now this doesn't mean your specific chip is problematic. However I would suggest further testing to validate it. At this point you can use the recovery menu and test the MLC as well. Which may shed some light on the situation for you.

In my opinion it's not worth testing the MLC memory because it has the Hynix chip and like you say it will degrade after some time.
It's maybe better if I solder the NAND-Aid on the motherboard, it's some extra work but if all goes well this console is "future-proof". 

Quote from: andlinux on Feb 04, 2026, 02:18 PMIn my opinion it's not worth testing the MLC memory because it has the Hynix chip and like you say it will degrade after some time.
It's maybe better if I solder the NAND-Aid on the motherboard, it's some extra work but if all goes well this console is "future-proof". 

I agree, replacing the chip with a NAND-AID is the best way to go. Its a permanent or near permanent fix. At some point the reality is all Wii U consoles will no longer work because these NAND chips have a finite lifespan.

I've been busy with this Wii U a whole afternoon, I soldered the NAND-AID to the board, inserted the SD card in the NAND-AID and booted with the Pico (defuse).
Then the weird things already started to happen, it booted in minute but I was only able to control the menu a few times with the serial connection and then nothing.
I switched over to the HDMI output and there was also the menu so I was able to continue from there with the push buttons on the Wii U.

I then tried to rebuild the MLC but it was complaining about the OTP, maybe I made here a mistake by putting the defuse_otp.bin on the SD card, although I changed it to otp.bin but that didn't work either.
After using an otp.bin from a previous dump of the system it did more. When the rebuild started the LED of the Wii U was still purple and not flashing... and it was as if the Wii U restarted, I heard the disc drive like when it boots up. On the picture you see what it puts out when it's going to start the rebuild.

The weird thing is that my raspberry pi is acting weird, the moment I plug it out and back in the Wii U restarts.

Is there also a way to check if the NAND-AID is installed correctly?

Are you seeing any information on the serial console output while trying to rebuild?

As for checking that the NAND-AID is installed properly. You can determine this by seeing if you can properly erase the MLC. When you go into the backup/Restore menu, go down to Erase MLC and select it. If the MLC erases properly you should see a message at the end that says "MLC Erase Complete"

For reference you can see this part in my video here

If the erase is successful, then what is the LED doing when you try to rebuild? If its not blinking Green or Orange there is likely a file missing on the SD Card and the rebuild cannot start.