Hi, I have tried to boot isfshax and keep getting the same issue. The console goes to a black screen and the LED on the front will just blink blue. it will load the recovery menu just fine. this happens with v0.6 and v0.5.

When attempting to copy the MLC (v0.5 Menu) every step seems to be failing I am yet to open the console up as I have a nand aid on its way but could the MLC failing every step cause the isfshax to not load?

I have prepared the MLC and SLC via the MLCrestorer would it be possible to get it working without the isfshax?

Any idea why it wouldn't boot the boot1 payload? Any help would be great. (I have also left it running with the blinking blue light for about an hour with no change)

To answer your question, yes there are reasons ISFShax will fail to load. This can happen when the eMMC is in such a poor state that its not being detected. There are other instances where it will fail to load as well which requires Defuse to fix.

Make sure your using HDMI cable as ISFShax cannot output on anything but HDMI. Aside from that if its still doing it you would need defuse to fix the console. I have had a handful of these consoles and everyone had the hynix eMMC in a failing state.

My recommendation is to rebuild a fresh MLC. I know there are still guides sitting here for how to backup the MLC, but this really isn't the ideal way to go. The problem with this is it will backup corrupt data, and that corruption will need to be fixed before the console is going to work. What is the current state of the console? Does it boot into the Wii U menu or is it throwing an error immediately?

Based on the information you are providing it would seem that you have already dumped the log files and validated that the eMMC is failing?

The console displays the wii u logo then straight to error code 103 and in a couple of boots it displayed 2215.

I will try the defuse method see if I get anywhere with that.

I'm using hdmi to display on my tv.

And yes iv dumped the opt and logs and used the mlc restore.
I gave up on the MLC dump as it was giving bad sectors on very step acting like the mlc is missing. When it displayed unmounting mlc it showed an error there aswell think it was fffcfffxd or something like that.

I followed your guide for finding the log i needed and it displayed the media error.


Thank you for getting back to me.

It sounds like the consoles that I have used Defuse to repair. Based on what you have stated about the MLC Dump and the errors, I suspect the eMMC in your console has degraded to the point that causes ISFShax to fail to load. Usually this means there is corruption within the filesystem on the SLC that effects boot1.

From a technical standpoint, ISFShax exploits the filesystem of the SLC in the Wii U. It is launched before IOSU (Wii U Operating System) is launched. However it cannot be used to repair issues with boot1, seeprom or issues with the superblock itself.

Defuse would be the last resort to repair the console. Based on your information I have had a couple consoles like yours that exhibit similar behavior. I ended up using defuse to repair both of them. I am curious if your console will end up having the same SLC corruption that requires the OSv10 fw.img to be replaced.

If it does you will see this in the log file after rebuilding the MLC, or you can see it on the serial console while using defuse

FSA: ### DATA CORRUPTION ERROR ###, dev:slc01, err:-524315, cmd:2, path:(null)
iosPanic(): Thread 91, owned by IOS-FS(5), has corrupted stack 0x115e9d08 of size 2048!

Thank you so much for this information. Once I get everything together for this, I will leave an update on whether iv been successful or not. May be a week or so while I wait for stuff to turn up.

One last question will the pico have to stay in, or will I be able to remove everything but the nand aid? So making it almost stock again. (If I'm successful)

Quote from: KXD on Jun 08, 2025, 01:20 PMThank you so much for this information. Once I get everything together for this, I will leave an update on whether iv been successful or not. May be a week or so while I wait for stuff to turn up.

One last question will the pico have to stay in, or will I be able to remove everything but the nand aid? So making it almost stock again. (If I'm successful)

Defuse/Pico can be removed once you repair the console. While not required, you can leave the wires soldered to the Wii U and put an inexpensive bread board on the other end of the wires if you want to save time should you need to use them in the future. Alternatively you can just remove the wires and leave them soldered to the Pico for use in another console that needs Defuse to repair, which is what I usually do. 

So I have installed the defuse on the wii u and it is booting into the minute menu with no issues, but I cannot remember or find what I need to do next to build the mlc onto the nand aid.

The rebuild process is identical whether your using Defuse or UDPIH + ISFShax. The post here covers it. Where I go through the steps of getting the SD Card setup properly and then I show the rebuild process.

Some further information that might be useful to you is a post/video I made about Defuse located here.

Seems iv hit another wall. When attempting to delete the mlc, it doesn't really do much, and I'm met with this screen.


I have checked that the nand aid is installed correctly, and it seems to be seeing the sd card.

I have seen this many times. Most often the cause is a NAND-AID that isn't soldered properly. If you have tested and verified this isn't the problem then it could be a NAND-AID where the SD Card slot is either missoldered or has been damaged during installation. If the SD Card doesn't push into the slot easily or eject easily but it doesn't appear to be flux residue (sticky when inserting or ejecting) than it could be that the SD Card slot was damaged during soldering. This is rather easy to do when holding a hot iron on the ground tabs for too long as it melts the plastic inside. Also double check the pins on the SD Card slot are soldered in place and there is no bridging as this can cause the SD Card to show up but will cause errors when erasing the MLC.

Something else to double check, did you verify with a multi-meter that you cut the trace on R26 so that the original eMMC is disabled?   

Some Less often causes could be a few things. The SD Card slot is full of flux residue and needs a good cleaning with 100% IPA. This is easy to test. If the SD Card when ejecting moves out slowly or feels sticky is flux residue. Clean it up until it doesn't do this.

Lastly, it could be the SD Card itself. I have had 3 systems that the SD Card was the problem. Again this is easy to test by grabbing a different SD Card and using it. For reference I have used dozens of SD Cards successfully, both 32GB and 64GB that were Samsung or SanDisk brand.

Additionally you might want to check your SD Card using H2testW . Of the 3 SD Cards I ran into issues with 1 of them was counterfeit and this utility showed that the advertised size and actual size were not the same, which is why the SD Card failed to work in the NAND-AID. The other 2 SD cards were genuine products, but defective which was easy to identify by using h2testw.
 

I have tested all solder joints with a multimeter to make sure they are going where needed. The trace is cut. I did miss the DSB solder point but that has made no difference.

I have cleaned everything with IPA and a brushed.

The Micro SD card clicks in and out without an issue. I will try to inspect the port later today to see if the port is melted or not And I will test the SD card.

Does the micro SD need to be formated before installing it?