After viewing and following the front half of the Full Video Tutorial on Diagnosing and repairing a Wii U (before NAND replacement) to troubleshoot to the point of getting the logs, I saw that the media was not bad.
I backed everything out to try and reload the OS banner in UDPIH. HOWEVER, I was not getting any video output (from UDPIH) BUT I was getting the purple light. I then did the steps blindly (power, eject, eject, power) to reload the OS. This did not resolve the issue. The device boots, Wii U splash screen displayed. Is there a way to reload/reset? I checked in the minute menu (print output- I forget which one) that showed its a hynix chip... I need a parts console for some others that have obvious failures (fan came off hub)- but I am reluctant to just write this one off if its an easy fix.
(a little snippit of the end of the log- full log folder attached)
00:12:49:224: CSC: Boss Storage Exist: FALSE, NetworkID Assigned: TRUE, System Network Connected: FALSE
00:12:49:249: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00:12:49:254: CSC: TV Port: HDMI, TV Aspect Ratio: 16:9
00:12:49:260: CSC: TV Resolution: TV_720P
00:12:49:260: CSC: CODE: [HNKC-0211-2373]
2018-01-15 04:21:57 - log collection event from pid 21
00;12;49;140: (1)5.5.2 U
00;12;49;140: (2)WUP-101(02)
00;12;49;140: (3)FW112374174
00;12;49;140: (4)HNKC-0211-2373
00:12:49:265: MCP: life time number of fatal errors - 1322 [/quote]
Greetings,
Based on your logs, the most current log file for your console is log 26. Within this log there are the following media errors:
DRMAPP:
00:00:15:289: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:15:318: mmc_core card err: idx=3, lba=55625728, blks=1024, xfer=0x1, ret=0x00200b40
00:00:15:375: mmc_core card err: idx=3, lba=55625728, blks=1024, xfer=0x1, ret=0x00200b40
00:00:15:375: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:15:388: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
This indicates the eMMC is failing and needs to be replaced with a NAND-AID. The symptoms you are experiencing after rebuilding are also evidence that the eMMC is bad.
Thank you! I tried the hex to decimal converter and it was coming up with 1326- I thought I did something wrong converting and picked around about 10 samples and didn't see the error. So the last 2 decimals are the log #? (0-99) I'll keep that in mind! Thanks again- and thank you for the videos and forum to iron these issues out!
Quote from: lanman on Jan 04, 2026, 08:52 PMThank you! I tried the hex to decimal converter and it was coming up with 1326- I thought I did something wrong converting and picked around about 10 samples and didn't see the error. So the last 2 decimals are the log #? (0-99) I'll keep that in mind! Thanks again- and thank you for the videos and forum to iron these issues out!
I don't know if the last 2 numbers always correspond with the log file. It is for this reason that the most accurate way to determine the most recent log file is plug that number in a modulo calculator (https://www.calculatorsoup.com/calculators/math/modulo-calculator.php) as the dividend and then put 100 in as the modulus.