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 (https://www.tzirf.com/nintendo-consoles-handhelds/video-tutorial-to-diagnose-repair-wii-u-with-bad-emmcerror-code-160-0103/) 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 (https://www.tzirf.com/nintendo-consoles-handhelds/how-to-diagnose-and-repair-a-wii-u-with-no-output-using-defuse/).
Seems iv hit another wall. When attempting to delete the mlc, it doesn't really do much, and I'm met with this screen.
20250617_222824.jpg
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 (https://h2testw.org/). 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?
No you don't have to format the SD Card before installing it. When you select the option to Erase the MLC within the minute menu this is what formats it properly with the proprietary format the Wii U uses.
I have managed to format an sd card via the mlc delete. When attempting the next step to delete the scfm, I get a failed message 20250619_211151.jpg
I'm assuming if this fails, it means it's not there as I may have already done this.
I have then attempted to patch the mlc, and i dont get a flashing blue light. All I'm getting is a solid blue light.
20250619_211753.jpg
That is correct, if you have already deleted the scfm.img you will get this error.
Lets check the SD Card you are putting in the front of the Wii U. Can you take a picture of the file/folder structure so we can verify that you have everything required to rebuild the MLC?
Also you did select the options "Patch SD and boot IOS slc" correct?
Edit: By the way since you installed defuse, you can use the serial console to see the output. Which can provide valuable information when you run into issues like this.
1.png2.png3.png4.png5.png
Edit: the root of the sd also had the opt.bin on it as well.
currently in the serial console and noticed "Firmware not 5.5.x! All you get is the OTP patch, sorry." does that mean it wont read the wafel_install folder? is there a work around for this?
SC.MLCPatch.txt
The root can have otp.bin on it, that doesn't matter.
Do you have the SLC Titles in the wafel_install directory? If not you should grab them and place them there. With both MLC and SLC titles there should be a total of 57 folders.
Your SD Card appears to be setup correctly. Its possible that some title files are corrupt. Download another copy of them and try again.
Also you are downloading the correct region for the MLC and SLC titles, correct?
What SD Card are you using with Defuse? 2GB card is required to rebuild the MLC and it cannot be SDHC.
I do have 57 folders in the wafel folder for mlc and slc, the region is pal so iv setup accordingly for this. I'm using a 2gb sd card which is from a 3ds and I still have to boot from the sd card as the console isn't happy taking the isfshax it tells me it's installed but it won't boot into anything without the boot on the sd card.
20250620_070914.jpg20250620_070923.jpg
Quote from: KXD on Jun 19, 2025, 05:25 PMcurrently in the serial console and noticed "Firmware not 5.5.x! All you get is the OTP patch, sorry." does that mean it wont read the wafel_install folder? is there a work around for this?
SC.MLCPatch.txt
Would this be an issue?
Quote from: KXD on Jun 20, 2025, 02:32 AMQuote from: KXD on Jun 19, 2025, 05:25 PMcurrently in the serial console and noticed "Firmware not 5.5.x! All you get is the OTP patch, sorry." does that mean it wont read the wafel_install folder? is there a work around for this?
SC.MLCPatch.txt
Would this be an issue?
Yes that is an error message, so its an issue.
QuoteI still have to boot from the sd card as the console isn't happy taking the isfshax it tells me it's installed but it won't boot into anything without the boot on the sd card.
This sounds normal. ISFShax still requires the SD Card to be present in the Wii U with the correct files to work.
SD Card should be fine. I wouldn't think it is the problem, unless you didn't format it using FAT
Is there a work around for the firmware issue as all I'm finding is the system can only be updated to 5.5.X when it's working.
Quote from: KXD on Jun 20, 2025, 04:49 PMIs there a work around for the firmware issue as all I'm finding is the system can only be updated to 5.5.X when it's working.
Firmware is too old. If memory serves me correctly, you need to use JNUSTool (https://github.com/Maschell/JNUSTool/releases) to download the latest version of OSv10. I believe the command to do this is
java -jar JNUSTool.jar 000500101000400AYou will need your common key from the otp.bin put in the config file for JNUStool to work. You can use this tool (https://github.com/GaryOderNichts/WiiUCommonKeyExtractor/releases) to extract the common key.
You will have to rename the fw.img file from OSv10 to ios_orig.img. and put it on root of your SD Card.
Then you need to use option "Patch (sd) and boot sdmc:/ios_orig.img". After it finishes you can use "Patch (sd) and boot IOS (slc)" and it should rebuild the MLC
Edit: Added a picture to show the fw.img file you need to download in JNUSTool. I know it was confusing for me the first time so figured a picture would make it easier to understand.
JNUSTool.JPG
I will give this a try in a couple of days. Thank you again for all your help so far.
Hopefully, this will be the last thing I need to finally get this sorted. This is my first time dealing with a wii u, let alone diving this deep into something, and I definitely wouldn't have got this far without your knowledge.
Sorry if iv been a pain in ass 😉
I would imagine you would have smooth sailing after this step. The only issue I see in your logs is that your firmware is too old. Once that is fixed you should be able to rebuild the MLC and get the Wii U working again.
Also no worries. I created this website to help others. ;)
so I have run the patch (sd) and boot sdmc:/ios_orig.img and I seem to get the same error as trying to do the mlc "Firmware not 5.5.x! All you get is the OTP patch, sorry." and then end up with a solid blue light on the console and no more progress. I have tried running the "Patch (sd) and boot IOS (slc)" just in case it did work but I get the same result here.
SCIOS_orig.txt
I have added the read out from Serial console.
SCBoot Log.txt
The Above is what I see when turning the console on I don't see any issues here but iv added it just in case I'm missing something.
Edit:jnustool.png
sdcardroot.png
Your memory card looks correct and based on the logs everything seems fine.
When you select patch (sd) and boot sdmc:/ios_orig.img, what does the front light on the console do?
Just shows a blue light no flashing and a white light above the eject button.
I'm assuming it wouldn't make a difference if I changed the sd card to just have the opt and ios on it.
Quote from: KXD on Jun 22, 2025, 09:45 AMJust shows a blue light no flashing and a white light above the eject button.
I'm assuming it wouldn't make a difference if I changed the sd card to just have the opt and ios on it.
no just having the OTP.Bin and IOS on it wouldn't help. We would have other errors because than critical files for these operations to run would be missing.
Do you have the disc drive connected to the console?
No i don't that crossed my mind as i sent that message now setting up with it installed
It doesn't have to be connected to rebuild the MLC. I was just asking because sometimes the drive has an error and it causes problems during rebuild when it is connected. I don't see those errors in the logs, so I assumed it was disconnected. However figured I would ask just to be sure.
You can certainly try with it connected, but I wouldn't expect a different result.
No difference only change is the white light on the eject button went away.
At this point I am not sure where the issue might be. Its strange because its just stopping at the firmware being older. I haven't seen one of these do that and then not being able to resolve it by patching the original firmware.
Do you know what firmware was installed on the console? I am curious if its really old and another method must be tried to get it updated.
You could try contacting SDIO. He can be found over on GBAtemp forums. Wouldn't hurt to have a second set of eyes to look at this. Its possible i missed something and SDIO knows more about the inner workings of this console than I do so he might have another solution you could try.
Edit: If you do find a solution to the problem. If you don't mind please make a post or message me. I will add it to the defuse guide I created that way if someone else comes cross the same issue they can hopefully find it and repair their console.
thank you for your help with this and if I can get a solution over at gbatemp I will come back here its the least I can do after all your help.
hey so SDIO suggested i remove the wafel_core from the sd card and that did the trick. i had a bit of issues with the wii u booting up i had to redo the patch a few times. at one point it was throwing up error 160-101 then it resolved that to finally allow me to setup the wii u.
QuoteSDIO said:
remove the wafel_core.ipx from the ios_plugins folder and then run the "patch (sd) and boot sdmc:/ios_orig.img" again.
I have done this and it's acting differently i got the blue flashing light for abit but now it has a flashing orange light.
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation Failure detected
- Error value: -196673
- Package:
</vol/mcp_rawpkg/wafel_install/0005001b10056000>
- Title: 0005001b-10056000 (0x0001)
- AppType: 1800001c
- Platform: Cafe
- Target dev: mlcsys01
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation failure log will be stored with error code '162-0000'
00:05:11:496: MCP: life time number of fatal errors - 1866
00:05:11:499: MCP: storing current logs as '/vol/system/logs/67.log'
00:05:11:991: MCP: Finished storing current logs as '/vol/system/logs/67.dsc'
install : fffcffbf
bspWrite begin
bspWrite done
WARNING WARNING WARNING WARNING WARNING WARNING
installinfo 0005001b10057000: 00000000
installtarget : 00000000
00:05:12:662: Cleaning /vol/storage_mlc01/sys/import/crash
00:05:13:095: MCP: discarding ramdisk cache for '/vol/storage_mlc01/sys/title/0005001b/10057000'
00:05:14:085: NET: Change admin state (2 -> 1)(iface:0 link:2)
00:05:14:087: [WD]>>>> Linkup msg from Net
00:05:14:097: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:05:14:103: NET: Change admin state (2 -> 2)(iface:1 link:2)
00:05:14:104: NET: Change admin state (1 -> 1)(iface:0 link:3)
00:05:14:213: [WD]>>>> Linkup msg from Net
00:05:14:223: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
WLC_E_SET_SSID: result 3 aid 0 bssid m
00:05:15:229: NET: Change admin state (1 -> 2)(iface:0 link:2)
00:05:18:231: NET: Change admin state (2 -> 1)(iface:0 link:2)
00:05:18:233: [WD]>>>> Linkup msg from Net
00:05:18:242: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
WLC_E_SET_SSID: result 3 aid 0 bssid m
00:05:19:248: NET: Change admin state (1 -> 2)(iface:0 link:2)
00:05:19:701: mdblk: err=-131094, mid=0x03, prv=0xa2, pnm=[SH64G80]
00:05:19:703: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:26, path:/sys
The above keeps getting repeated while the light is flashing orange.
Is this suggesting the folder has an issue and i should try running the mlcrestorer again? and replace the folders on the sd card?
Post automatically merged: Today at 8:48 PM
Iv repeated steps to delete the mlc and this time when running the patch it's gone to a solid blue like with a message on the serial console stating the mlc setup is complete.
Post automatically merged: 40 minutes ago
gone to boot the console with the wafel removed from the sd card it loaded the wii u logo after awhile and then its gone to a black screen the serial console has stopped with the last entry being "iosPanic(): PPC core 0 heartbeat failed!"
Post automatically merged: 32 minutes ago
now the console is showing error code 160-101
Post automatically merged: 27 minutes ago
Attached boot log which ends with error on screen 160-101
Post automatically merged: 23 minutes ago
attempted to boot it a couple more times now its allowing me to setup the console.
This console has been very strange to deal with.
final question now its gone through the setup process is this when i take the defuse off iv already unistalled the isfshax.
I went ahead and removed the defuse and its now working.
Again thank you for your help I have learnt alot.
Excellent! Glad you were able to get the Wii U repaired. Yes you can remove Defuse once the MLC is rebuilt. Once defuse is removed. You can still use UDPIH + ISFShax to do repairs. so it gives you the ability to use that in the future if you have to repair the console again. Of course the best case scenario is that you wouldn't have to do this.