I recently bought a "non-working" Wii U and have been going through the process of repairing. Initially, it did not power on at all. After tearing it down, I found that one of the ferrite beads after the power fuse was completely blown up. I replaced that and now it turns on.

However, the new issue is I have no video output, whether on HDMI or analog. I was able to boot with UDPIH (again, no video) and get the logs dump. No mentions anywhere in the most recent (or any other logs) of Media Error that I could find, so it doesn't appear to line up with the typical MMC/NAND needing a NAND-AID at least from what I can tell. So I blind installed isfshax and now when I turn the console on, it goes straight to the purple light. However, I still have no video output (plugged in HDMI now, confirmed we're on a display that supports 1080p).

Not really sure how to proceed at this point. From what I can tell, things seem to be semi functional but with no display at all, I don't want to blind fire some power/eject combinations without knowing what I'm doing. Looking for any suggestions you or others may have.

Can you zip the logs up and upload them? They can be used to see if some other issues exist with the console.

Do you remember what the LED on the console was doing before you installed ISFSHax?

QuoteStaying red

    Try turning on using the eject button and remote
        Still red -> SLC Failure / boot1 corruption / SEEPROM corruption

Red blinking after some time -> Overheating / VRMs failing
Red Blinking on cold boot -> Short on one of the Power Rails
Blue blinking -> SLC Corruption (system.xml / fw.img) or bad RAM
Orange blinking -> ISFShax SD card missing
static blue

    Wait 1m, try turning off by shortly (less than 1s) pressing power
        Still on -> OS crash
        Turns off -> Display Problem

Since we do not know the state of the OS on the console, we don't know if its working enough to display anything at all. Keep in mind that an eMMC can be working but if the OS is badly corrupt the console may not display anything at all. I have had a few consoles that did just this. The likely reason for this is probably either someone interrupt an OS update or they tried homebrew and they deleted something they shouldn't. 

You can use UDPIH to sync a game-pad to the console and see if that displays so you can further diagnose the console. If you want to use UDPIH I am attaching the recovery menu that will automatically dump the PIN when loaded. Then you can extract the pin from the SD Card on a computer, power off the Wii U, Power it back up, wait a few seconds and press the sync button twice and then enter it on the gamepad to get it connected.   

Perfect, I will give the gamepad sync up a try as well (once I get my gamepad in finally). Before installing ISFShax I had a static blue status LED when powering on the console, just no display at all. I've attached the zip of the log files. Appreciate the help! I've been fixing up old consoles for a while now but this is my first dip into the Wii U world, so learning as I go.

Quote from: kromaey on Jul 25, 2026, 08:58 PMPerfect, I will give the gamepad sync up a try as well (once I get my gamepad in finally). Before installing ISFShax I had a static blue status LED when powering on the console, just no display at all. I've attached the zip of the log files. Appreciate the help! I've been fixing up old consoles for a while now but this is my first dip into the Wii U world, so learning as I go.

So a static blue like either the OS crashed or there is a display problem. Since you are past the point of testing that, without removing ISFShax and going back lets just keep that information in the back of our minds.

I took a look at the log files. No eMMC errors are found, so you are correct the eMMC appears to be just fine. The console was originally setup to display over Composite at 480I. If you are trying to use this console on a TV that doesn't support this format than the screen will remain black and appear to display nothing at all. I would recommend syncing a game-pad with the console. If it loads the OS you can go into the settings and adjust the TV settings to match your display. In most cases this means HDMI 1080P.

That being said based on the log files, it appears the OS isn't functioning. So the problem might just be an OS Crash and the MLC needs to be rebuilt.

Just to be sure, Minute menu will only display over HDMI 1080P. Have you tried that?   

When I first got it to power up, I had connected it over component to an older TV with no output, so that's what kicked off the whole troubleshooting. Good to know that it's set at 480i right now though. To your last question - I've tried hooking up to a couple of displays over HDMI (also tried different HDMI cables just to be on the safe side) but still no display. For reference, I have an older 20 something inch LCD tv on my desk that I use for testing consoles that has AV/Component/HDMI since it seems to work with all the resolutions. With that being said, I am NOT sure if it'll do interlacing with 480i as I've only tested with 480p, so that's a good call if the Wii was trying to output 480i.

Is there a number of power/reset presses I can use in minute menu to get to MLC rebuild? I do have the actual tablet now, but I'm assuming if I can't see the output from the console, it'll be hard to get it paired without seeing what the pairing code is that it's spitting out.

Again, really appreciate your help with this!

In my first reply to you, I gave you the recovery menu that you can use with UDPIH and it will automatically record the pairing code to the SD Card. You can follow those instructions and use that if you want to try pairing the gamepad.

Otherwise you could attempt to blindly rebuild the MLC or this console would need Defuse to repair it.

I created a video showing the full process. You can follow the video and attempt to do it without a display output.   

Ah completely missed the attached recovery file for dumping the pin. If I already have isfshax installed, is there still a way to boot from the udpih to get into the recovery menu instead of minute menu?

I found earlier some of the hurdles I was running into were due to the Wii U not liking the micro SD in SD adapter I was using. Once I switched to another SD card, I was able to get dumps of otp.bin and SEEProm and SLC.raw. With the otp.bin I was able to use the MLC Restorer Downloader to download all the packages and put them on my SD card under the wafel_install folder. I've also ensured to add wafel_setup.mlc.ipx into the wiiu/ios_plugins folder on there as well.

However, the new issue I'm running into is when I go to the menu option for Patch (sd) and boot IOS (slc), but as soon as I hit eject, the Wii U goes to a flashing red light. I even tried leaving it for ~30 min but nothing changed. No logs or anything ended up on the SD card either.

The only discrepancy I noticed was several guides mentioned having a wafel_core.ipx, but the stroopwafel git repo (and my SD card) only have 00core.ipx. Am I meant to rename or grab that somewhere else?

Quote

Quote from: kromaey on Jul 29, 2026, 03:46 PMAh completely missed the attached recovery file for dumping the pin. If I already have isfshax installed, is there still a way to boot from the udpih to get into the recovery menu instead of minute menu?

I don't recall if you can do this or not. I think you can and at one point it was easier. However now I think the easiest way to do it is to remove the ISFShax. That being said I don't think its neccessary at this point. You said you already tried to Patch (sd) and boot IOS (slc). Did you erase the MLC prior to doing this? If you did erase the MLC, then pairing a gamepad would be a waste of time as the OS on the console is missing. If you didn't its still likely a waste of time because we don't know what was changed from using Patch (sd) and boos IOS (slc).

QuoteHowever, the new issue I'm running into is when I go to the menu option for Patch (sd) and boot IOS (slc), but as soon as I hit eject, the Wii U goes to a flashing red light. I even tried leaving it for ~30 min but nothing changed. No logs or anything ended up on the SD card either.

Flashing red light means there is a critical error. Usually this indicates something besides a missing file. Dump the logs from the console and upload them. They may hold some clue as to what it happening. If you didn't erase the MLC, try erasing it first. You can see if it works by checking the log file it creates on the SD Card. Since there is no video output, just give the console a good 20-30 seconds to erase and then power it off and check the SD Card in your computer for the log.   

QuoteThe only discrepancy I noticed was several guides mentioned having a wafel_core.ipx, but the stroopwafel git repo (and my SD card) only have 00core.ipx. Am I meant to rename or grab that somewhere else?

No you do not have to rename the 00core.ipx. The tools are created by another individual and they have been updated since my guides and other guides out there. If you aren't certain about the file structure of your SD Card, you can compare it to the one I created for my defuse guide:

D:.
│   fw.img
│   ios.img
│   superblock.img.sha
│   superblock.img
│   tree.txt
│ 
├───wiiu
│   │   .DS_Store
│   │ 
│   └───ios_plugins
│           .DS_Store
│           00core.ipx
│           wafel_debug_exts.ipx
│           fw.img
│         
└───wafel_install
    ├───0005001010004000
    │     
    │     
    ├───0005001010004001
    │     
    │     
    ├───0005001010004009
    │     
    │     
    ├───000500101000400a
    │     
    │     
    ├───00050010100040ff
    │     
    ├───0005001010040100
    │     
    │     
    ├───0005001010041100
    │     
    │     
    ├───0005001010043100
    │     
    │     
    ├───0005001010044100
    │     
    │     
    ├───0005001010045100
    │     
    │     
    ├───0005001010047100
    │     
    │     
    ├───0005001010048100
    │     
    │     
    ├───0005001010049100
    │     
    │     
    ├───000500101004a100
    │     
    ├───000500101004b100
    │     
    │     
    ├───000500101004c100
    │     
    │     
    ├───000500101004d100
    │     
    │     
    ├───000500101004e100
    │     
    │     
    ├───000500101005a100
    │     
    │     
    ├───0005001010062100
    │     
    │     
    ├───0005001010066000
    │     
    │     
    ├───0005001b10042300
    │     
    │     
    ├───0005001b10042400
    │     
    │     
    ├───0005001b1004f000
    │     
    │     
    ├───0005001b10050000
    │     
    │     
    ├───0005001b10051000
    │     
    │     
    ├───0005001b10052000
    │     
    │     
    ├───0005001b10053000
    │     
    │     
    ├───0005001b10054000
    │     
    │     
    ├───0005001b10056000
    │   
    │     
    ├───0005001b10057000
    │     
    │     
    ├───0005001b10058000
    │     
    │     
    ├───0005001b10059100
    │     
    │     
    ├───0005001b1005c000
    │     
    │     
    ├───0005001b1005f000
    │     
    │     
    ├───0005001b10063000
    │     
    │     
    ├───0005001b10065000
    │     
    │     
    ├───0005001b10067100
    │     
    │     
    ├───0005001b10068000
    │     
    │     
    ├───0005001b10069100
    │     
    │     
    ├───0005001b1006c000
    │     
    │     
    ├───0005003010010109
    │     
    │     
    ├───000500301001010a
    │     
    │     
    ├───0005003010011109
    │     
    │     
    ├───000500301001110a
    │     
    │     
    ├───00050030100111ff
    │     
    │     
    ├───000500301001210a
    │     
    │     
    ├───000500301001310a
    │     
    │     
    ├───000500301001410a
    │     
    │     
    ├───000500301001510a
    │     
    │     
    ├───000500301001610a
    │     
    │     
    ├───0005003010017109
    │     
    │     
    ├───000500301001710a
    │     
    │     
    ├───000500301001810a
    │     
    │     
    ├───000500301001910a
    │     
    │     
    ├───000500301001a10a
    │     
    │     
    └───000500301006d10a