I recently discovered that the family Wii U isn't functioning right.
A few years ago it was dying but nobody was repairing them and Nintendo had just stopped. It worked to play games but trying to enter the settings menu would cause an error. I don't recall which one, but it was not 160-0103.
A week ago I found that when it starts up to the Quick Menu you can select a game, then a Mii, but it hangs forever on the white Wii U screen.
I have tried to use udpih, but no attempt at plugging the pico in works. I see the white Wii U screen, the power led turns purple but the screen just goes black.
What would you all suggest next? I gotta fix this one. It was the kids favorite console, the one they grew up with.
Mike
What is the quick menu? Are you just referring to the Wii U menu?
I am going to toss this information out just to make sure that this isn't where your problem is. If the Wii U menu freezes when launching anything that means you have a defective WiFi Module. If all games freeze on the splash screen you have a defective Bluetooth module.
Now if neither of these things are happening we can ignore them and move on. If the power LED turns Purple with UDPIH, that tells me its working. Since all you get is a black screen you have 2 options. You can try to blindly load ISFShax or use Defuse to repair the console.
To blindly load ISFShax, make sure you have boot1now.img on your SD Card and use UDPIH. This will cause boot1 to automatically load into the minute menu. Then you will have to press Eject 3 times, Power 1 Time and Eject 3 times. I recommend going slow when pressing the eject/power button. It doesn't have to be fast. If done correctly this will install ISFShax and the console will turn off if successful.
If you are able to get ISFShax installed this usually will fix the no video out with UDPIH. Keep in mind that Minute menu will only display over HMDI at 1080P. If this doesn't fix the output then you will have to use Defuse to repair the console.
The guide for ISFShax is here (https://gbatemp.net/threads/how-to-set-up-isfshax.642258/)
By quick menu I mean the menu on the gamepad. In the top corner it says "Quick Start" Sorry for the awful image.
https://freeimage.host/i/FZ6Etta
If I select a game and then a Mii the game hangs forever on the Wii U screen you can see on the monitor in the image. This image also appears on the gamepad. Does this mean dead wifi card? If so, how to fix?
By using the recovery_menu_dc_init and renaming it to recovery_menu I am able to get some output when trying to run udpih, but it is all garbled.
I've ordered a NAND-AID and my soldering skills are easily up to the task of installing it and defuse. I'll probably have more questions in the future.
Doesn't appear to be a defective WiFi module. If it were the video would freeze and the audio would continue playing. If it were a defective Wifi module, you simply replace it. It doesn't require soldering to replace either. Its the module that the black and white wires inside the console connect located on the back of the motherboard.
I suspect the eMMC is bad and there might be corrupt data on the SLC. In my experience consoles with SLC corruption are the ones that UDPIH wouldn't work on. Although if the eMMC is in really bad shape this can also cause UDPIH to fail.
Did you try blindly loading ISFShax?
A bit of clarification.
If I run udpih on its own with it's recovery_menu the Wii U hangs on the white Wii U screen. Purple LED
If I run udpih on its own with recovery_menu_dc_init renamed to recovery_menu I get garbled output. Purple LED
If I follow the isfshax guide and the sd card contains the files for isfshax I get a black screen. Flashing Purple LED continues forever. Doesn't the led need to be solid purple to try blind loading?
In my first post I didn't notice the purple LED flashing vs solid because I hadn't read the part on the github for udpih for the colour code.
I suppose I need to wait for my NAND-AID to arrive and should solder in a pico while I wait.
Flashing Purple LED suggests that its trying to load the minute menu. However if it doesn't go solid then it must be hanging at some point. Defuse is necessary to repair. You can go ahead and solder the PICO into the console.
You don't have to wait for the NAND-AID to do this and you should install defuse before and make sure you can get into the minute menu and at least backup the necessary files and dump the logs to validate the eMMC is bad.
Well I finally got around to it. The Pico is soldered onto the Wii U board. My NAND-AID arrived but I have not installed it yet.
Was just preparing the SD card, but the files over at https://github.com/StroopwafelCFW/wii_u_modchip/releases for v1.1 do not contain the referenced file boot1.img and only boot1_slccmpt.img
Is this a case of the release getting ahead of the instructions? I'm not sure what to copy over to the sd card.
Any pointer would be appreciated.
Are you sure you downloaded the correct zip? You can get it here (https://github.com/StroopwafelCFW/wii_u_modchip/releases/tag/v1.1) and I checked the zip and it does contain the boot1.img and boot1_slccmpt.img.
Weird.
On the main wii_u_modchip page if you click on the link in the right hand column that says
Releases LATEST
v.1.1
it takes you to a different page than the one you included. On that page it quickly has a link
You can download everything here: defuse_release.zip
It is the file above that does not include boot1.img
Turned me around, thank you for your link which directs to the correct page.
DeFuse booted up. Thanks.
Now to read and watch more guides.
You are welcome. Excellent work! Glad you were able to get it working. Best of luck with your repair. ;)
I could use a hand.
isfshax will not install from defuse. It hangs at the GO GO GO.
I've dumped the SLC.raw, otp.bin, seeprom but am unable to dump the mlc because the defuse sd card is so tiny.
Is there a way to accomplish this?
You need to use a 2GB SD Card with Defuse to dump the MLC. That being said, there is no reason to install ISFShax. With Defuse you have all the tools you need to rebuild the eMMC. Dump the logs and post them so we can validate the eMMC is failing.
If the eMMC is failing your next step is to install a NAND-AID and then you can move on to rebuilding the MLC. As for dumping the MLC. Its really not necessary anymore and you can skip this step. The only reason you would need to dump it is if you want to recover some data
Oh, that is all? I had assummed that the mlc was 32gb in size. I thought the mlc was the size of the system memory.
I'll track down a 2GB SD card. I will post the crash log file shortly.
The meta.bin file contains 00 00 00 57
Here is log 87
2013-01-03 06:10:59
Cafe OS SDK Version 2.13.01 Build 68939 Branch sdk_2_13
Espresso: 0x0000700100000201
Latte: 0x0000409f
System mode: 0x100000
Boot flags: 0x84810000
Security Level: 0x1e
Key Type: 0xfffffffc
Prod Version: 0x5
Serial: 409311851
Model: WUP-101(02)
Prod Area: 0x2
Game Area: 0x2
5GHz Code: 0x7
BOOT1: 0x20b9
DRH: 0x190c
BT: 0x205
----------- Starting System Log -----------
00:00:00:181: TEST Info: crossProcessHeap OK.
00:00:00:182: AUXIL Info: crossProcessHeap OK.
00:00:00:183: AUXIL Info: Net OK.
00:00:04:109: USB Trace: Activating root hubs @ uptime 4.109 s with options 0x40000.
00:00:04:119: UHS0 Trace: DevFsm(EHCI-0/L0/P0): Creating device, speed=HIGH.
00:00:04:121: UHS0 Trace: DevFsm(OHCI-0:0/L0/P0): Creating device, speed=FULL.
00:00:04:121: USB Info: UhsServerAddHc 0 OK.
00:00:04:130: UHS0 Trace: DevFsm(EHCI-1/L0/P0): Creating device, speed=HIGH.
00:00:04:132: UHS0 Trace: DevFsm(OHCI-1:0/L0/P0): Creating device, speed=FULL.
00:00:04:132: USB Info: UhsServerAddHc 1 OK.
00:00:04:146: UHS0 Trace: Powering on root hub group 0.
00:00:04:160: UHS0 Trace: Powering on root hub group 1.
00:00:04:161: AHCI_MGR Trace: Turning on drive power.
00:00:04:165: AHCI_MGR Trace: Initializing phy.
00:00:04:166: AHCI_DRV Trace: Initiating cold open.
00:00:04:166: AHCI_DRV Trace: Resetting HBA.
00:00:04:216: AHCI_DRV Trace: HBA Reset OK.
00:00:04:264: ISFS: FAT INFO (ch WUP): slot 11 / seq 1857229 (Each FAT slot has been updated 29019 times in avr)
00:00:04:264: FSA: [uptime 4.264 s]: Attached volume to slc01 (isfs): Capacity 511 MB, 262016 logical blocks of size 2048 B.
00:00:04:355: ISFS: FAT INFO (ch RVL Compat): slot 14 / seq 267760 (Each FAT slot has been updated 16735 times in avr)
00:00:04:355: FSA: [uptime 4.355 s]: Attached volume to slccmpt01 (isfs): Capacity 511 MB, 261632 logical blocks of size 2048 B.
00:00:04:359: SCFM:Start init. BUILD_TIME:[19:23:46]
00:00:04:362: SCFM:FSAInit
00:00:04:363: SCFM:AddClient
00:00:04:363: SCFM:scfmMountSlc
00:00:04:364: SCFM:scfmLoad
00:00:04:364: SCFM:Done init.
00:00:04:365: PCFS: Disabled because we are in PROD mode.
00:00:04:365: MCP: booting from NAND
00:00:04:365: MCP: Boot PM flags - PON_COLDBOOT PON_POWER_BTN PON_SMC POFF_4S
00:00:04:383: MCP: Cafe OS SDK Version 2.13.01 Build 68939 Branch sdk_2_13
00:00:04:383: MCP: Booting on Espresso (0x0000700100000201), Latte (0x25100028), RTC (0x21)
00:00:04:384: MCP: Platform - boardType(CF), boardRevision(11), devicePresence(0x00000000), sataDevice(3), consoleType(1)
00:00:04:386: ISFS: FAT block entries check start
00:00:04:390: ISFS: FAT block entries check finished.
00:00:04:395: FSA: [uptime 4.395 s]: Attached volume to ramdisk01 (raw): Capacity 127 MB, 131070 logical blocks of size 1024 B.
00:00:04:400: MCP: Formatting Device ramdisk to wfs
00:00:04:544: FSA: [uptime 4.544 s]: Attached volume to ramdisk01 (wfs): Capacity 127 MB, 131070 logical blocks of size 1024 B.
00:00:04:544: MCP: Format Complete
00:00:04:571: FSA: [uptime 4.571 s]: Attached volume to mlc01 (wfs): Capacity 29760 MB, 60948480 logical blocks of size 512 B.
00:00:04:692: ISFS: FAT block entries check start
00:00:04:695: ISFS: FAT block entries check finished.
00:00:04:793: FSA: [uptime 4.793 s]: Attached volume to sdcard01 (raw): Capacity 961 MB, 1968128 logical blocks of size 512 B.
00:00:04:829: MCP: File loading from ramdisk cache is enabled
00:00:04:838: MCP: Master title 0005001010040100 os 000500101000400a from mlc01 flags 0004
00:00:04:848: MCP: no valid title list found, rebuilding...
00:00:04:854: MCP: os version 10 NDEBUG (0x000500101000400a)
00:00:04:854: MCP: FSA volume on device /dev/mlc01 (wfs) attached @ uptime 4.854 s.
00:00:04:868: MCP: found master title 5001010040100 on mlc01 at 4.868 s
00:00:04:872: MCP: FSA volume on device /dev/ramdisk01 (wfs) attached @ uptime 4.872 s.
00:00:04:872: MCP: Titles scanned (dev_state 0006) on device /dev/ramdisk01 (wfs) @ uptime 4.872 s.
00:00:04:873: MCP: FSA volume on device /dev/sdcard01 (raw) attached @ uptime 4.873 s.
00:00:04:873: MCP: Titles scanned (dev_state 0006) on device /dev/sdcard01 (raw) @ uptime 4.873 s.
00:00:04:873: MCP: FSA volume on device /dev/slc01 (isfs) attached @ uptime 4.873 s.
00:00:04:873: MCP: FSA volume on device /dev/slccmpt01 (isfs) attached @ uptime 4.873 s.
00:00:04:874: MCP: Titles scanned (dev_state 0006) on device /dev/slccmpt01 (isfs) @ uptime 4.874 s.
00:00:05:129: ISFS: fs_ops.c(3733)Can not change the owner Id of a non-empty file
00:00:05:129: ISFS: fs_ops.c(6719)Could not set attribute, rc=-524312
00:00:05:148: MCP: Titles scanned (dev_state 000e) on device /dev/slc01 (isfs) @ uptime 5.148 s.
00:00:05:285: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/0005001b/10065000/code/app.xml
00:00:05:511: MCP: ECO mode is enabled
00:00:05:511: [+-* DK is ready for console input *-+]
00:00:05:511: MCP: syslog mask is set to 0xffffffff
00:00:05:520: W2C: Does not need W2C-reflection
00:00:05:591: MCP: Titles scanned (dev_state 0004) on device /dev/mlc01 (wfs) @ uptime 5.591 s.
00:00:05:593: MCP: Titles scanned (dev_state 000c) on device /dev/mlc01 (wfs) @ uptime 5.593 s.
00:00:05:595: MCP: Titles scanned (dev_state 0006) on device /dev/mlc01 (wfs) @ uptime 5.595 s.
00:00:05:904: UHS1 Trace: DevFsm(EHCI-2/L0/P0): Creating device, speed=HIGH.
00:00:05:906: UHS1 Trace: DevFsm(OHCI-2:0/L0/P0): Creating device, speed=FULL.
00:00:05:906: CCR_MAIN: activating root hub.
00:00:05:957: FS_MAIN: UMS Server Created.
00:00:05:959: AUXIL Info: resumed.
00:00:06:209: UHS1 Trace: DevFsm(EHCI-2/L1/P1): Creating device, speed=HIGH.
00:00:06:209: UHS1 Trace: DevFsm: There are now a total of 1 connected devices.
00:00:06:225: BT: BTA/BTE/STACK now operational
00:00:06:241: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.241 s.
00:00:06:241: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.241 s.
00:00:06:242: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.242 s.
00:00:06:242: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.242 s.
00:00:06:242: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.242 s.
00:00:06:242: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.242 s.
00:00:06:243: UHS1 Trace: CltIfFsm(V057e|P0341|IF6): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.242 s.
00:00:06:243: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.243 s.
00:00:06:243: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.243 s.
00:00:06:243: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.243 s.
00:00:06:243: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.243 s.
00:00:06:244: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.244 s.
00:00:06:244: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Acquired by client in pid 6.
00:00:06:244: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Enable endpoints 0x00080000.
00:00:06:284: __ccr_hid_attach_add_interface: idx 0 ep 3
00:00:06:285: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Acquired by client in pid 6.
00:00:06:285: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Enable endpoints 0x00100000.
00:00:06:325: __ccr_hid_attach_add_interface: idx 1 ep 4
00:00:06:325: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Acquired by client in pid 6.
00:00:06:325: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Acquired by client in pid 6.
00:00:06:326: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Activating bAlternateSetting 0.
00:00:06:328: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Acquired by client in pid 6.
00:00:06:329: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Acquired by client in pid 6.
00:00:06:329: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Activating bAlternateSetting 0.
00:00:06:331: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Acquired by client in pid 6.
00:00:06:331: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Enable endpoints 0x08001000.
00:00:06:332: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Acquired by client in pid 6.
00:00:06:333: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Acquired by client in pid 6.
00:00:06:333: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Activating bAlternateSetting 0.
00:00:06:335: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Acquired by client in pid 6.
00:00:06:336: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Acquired by client in pid 6.
00:00:06:336: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Activating bAlternateSetting 0.
00:00:06:338: DRH chip revision 00000040
00:00:06:338: DRH firmware version 190c0117
00:00:06:339: DRH cdc version 00080000
00:00:06:339: DRH wifi module id a8e502d0
00:00:06:339: DRH SPL id 00001c58
00:00:06:483: NET: Applied interface MTU (wl0:1400 eth0:1400).
00:00:06:498: USBETH Trace: Created interface 100.
00:00:06:566: MCP: boot1 version 2.11.09
00;00;05;891: COSREPORT: Set level:1 from syslog level
00;00;05;891:
----------------------------------------------- BPERF: (0/5891441) PPC Init.
00;00;05;891: Cafe OS SDK Version 2.13.01 Build 68939 Branch sdk_2_13
00;00;05;891: PPC NDEBUG Kernel Build date - Jul 28 2015 19:55:58
00;00;05;891: BUILT AS OS_VERSION_MAJOR 000500101000800A MINOR 0x3D56
00;00;05;891: core=1 COLD BOOT
00;00;05;891: SOFT INTERRUPT MODE
00;00;05;891: -----------------------------------------------
00;00;05;891: KiCblRegisterBlocks() completed with status 0:-4.
00;00;05;891: PROD Mode - don't even try to load kdebug.elf
00;00;05;892: title id: 5001010040100, app type 90000001
00;00;05;892:
00;00;05;892: ---------------------------------------
00;00;05;892: OS VERSION ID 0x000500101000400A
00;00;05;892: MASTER TITLE ON FLASH
00;00;05;892: ---------------------------------------
00;00;05;892:
00:00:06:596: MCP: loaded and parsed 'preload.txt' at '/vol/system/title/00050010/1000400a/code'
00:00:06:612: MCP: Wake 0 signal
00;00;06;612: DIAG:+KiRPLLoaderSetup
00;00;06;612: DIAG:-KiRPLLoaderSetup: before no-return call to KiLoadContext (0xEFE09400) (0x01003FFC)
00:00:06:815: DRH using runtime generated WLAN data
00:00:06:815: Setting DRH to Normal mode
00:00:06:816: setting DRH system time to 06:11:01
00:00:06:817: sending DRC WOWL wake
00:00:06:838: ccr_admin_wowl_wake_drc() returned 0
00:00:06:844: WUD_BCMFWCheck ==> chipname 20702A1 build 517 from SERIAL FLASH
00:00:06:846: BT: BTRM now Active (WUD Operational)
00:00:06:850: ACT: Current account is #1.
00;00;07;514: DIAG:+KiProcess_FinishInitAndPreload
00;00;07;514: KiCblRegisterBlocks() completed with status 0:-4.
00;00;07;531: Kernel is loading shared data...
00:00:09:332: AHCI_DRV Warning: link not ready ready with status 16:-531.
00:00:09:332: AHCI_DRV Trace: Resetting HBA.
00:00:09:383: AHCI_DRV Trace: HBA Reset OK.
00:00:09:520: CDC_SIGNAL_STA_ASSOCIATED_NOTIFY
00:00:10:238: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:10:248: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:10:249: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/0005001b/10042400/content/CafeCn.ttf
Process 1, Error 0xCAFEBADD
*** LoadShared times out loading shared data.
--Core1-UPID1--- Exception Context 0xFFE442D8 ------RAMPID 1------
CR = 0x00000000
CTR = 0x00000000
LR = 0x00000000
SRR0 = 0x00000000
SRR1 = 0x00000000
r0 = 0x00000000 ( 0) r16 = 0x00000000 ( 0)
r1 = 0x00000000 ( 0) r17 = 0x00000000 ( 0)
r2 = 0x00000000 ( 0) r18 = 0x00000000 ( 0)
r3 = 0x00000000 ( 0) r19 = 0x00000000 ( 0)
r4 = 0x00000000 ( 0) r20 = 0x00000000 ( 0)
r5 = 0x00000000 ( 0) r21 = 0x00000000 ( 0)
r6 = 0x00000000 ( 0) r22 = 0x00000000 ( 0)
r7 = 0x00000000 ( 0) r23 = 0x00000000 ( 0)
r8 = 0x00000000 ( 0) r24 = 0x00000000 ( 0)
r9 = 0x00000000 ( 0) r25 = 0x00000000 ( 0)
r10 = 0x00000000 ( 0) r26 = 0x00000000 ( 0)
r11 = 0x00000000 ( 0) r27 = 0x00000000 ( 0)
r12 = 0x00000000 ( 0) r28 = 0x00000000 ( 0)
r13 = 0x00000000 ( 0) r29 = 0x00000000 ( 0)
r14 = 0x00000000 ( 0) r30 = 0x00000000 ( 0)
r15 = 0x00000000 ( 0) r31 = 0x00000000 ( 0)
OSContext is unused (NULL)
Kernel Stack Trace 0xFFE43E68 ----
CoreId: 1 Stack: 0xFFE43E68
Address: Back Chain LR Save
0xFFE43E68: 0xFFE43EA0 0xFFF0F07C +0x0
0xFFE43EA0: 0xFFE43EE8 0xFFF14F6C +0x0
0xFFE43EE8: 0xFFE43EF0 0xFFF15198 +0x0
0xFFE43EF0: 0xFFE43F00 0xFFF129A0 +0x0
0xFFE43F00: 0x00000000 0xFFF01FCC +0x0
00;00;10;149: KiCblRegisterBlocks() completed with status 0:-4.
00:00:10:289: COS encountered unrecoverable error...
Pending Resource Request for COS processes...
Title Id Process Id -> RM Path
00:00:10:387: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:10:422: NET: Change admin state (2 -> 1)(iface:0 link:2)
00:00:10:422: [WD]>>>> Linkup msg from Net
00:00:10:431: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:00:10:435: NET: Change admin state (0 -> 2)(iface:1 link:2)
00:00:10:435: IFNET_ETH: Configuring link adminState to DOWN.
00:00:10:435: NET: Change admin state (1 -> 1)(iface:0 link:3)
00:00:10:535: [WD]>>>> Linkup msg from Net
00:00:10:543: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:00:10:820: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:10:857: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:10:909: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:10:954: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:000: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:045: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:103: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:155: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:156: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:10, path:/sys/title/0005001b/1005c000/content/country.txt
00:00:11:167: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:168: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:10, path:/sys/title/0005001b/1005c000/content/language.txt
00:00:11:199: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:240: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:268: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:11:269: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
Failed to initialize resources. reason = 0xa0407580
00:00:11:556: mdblk: err=-131090, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:14:390: AHCI_DRV Warning: link not ready ready with status 16:-531.
00:00:14:390: AHCI_DRV Trace: Resetting HBA.
00:00:14:441: AHCI_DRV Trace: HBA Reset OK.
00:00:15:296: MCP: life time number of fatal errors - 86
Quote from: mpatl on Aug 28, 2025, 11:22 PMOh, that is all? I had assummed that the mlc was 32gb in size. I thought the mlc was the size of the system memory.
I'll track down a 2GB SD card. I will post the crash log file shortly.
My apologies. I meant 32GB SD Card. You are absolutely correct when you said the MLC is 32GB in size. That was a typo and I didn't even notice it. Even so its incorrect because you need extra space to hold the necessary tools to dump the MLC so you would have to use something larger than 32GB. I use a 64GB SD Card.
00:00:11:269: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null) is found in your log file, which indicates the eMMC is bad and the console needs a NAND-AID.
So that's what I don't understand. How do you use a 64gb sd card with defuse when the sd card has to be 1gb.
Is it the format redNAND option?
I would like to try and save the MLC if I can. Mostly for the kids Miis. They created them as small children and played them all the way to teens without modifying them. They made ones for my wife and I as well. They are nostalgic.
No its not the format redNAND Option. redNAND is a different recovery method. Its similar to the NAND-AID but redirects reading/writing to an SD Card in the front of the Wii U and uses that as a replacement eMMC.
Well since you want to recover data than you would have to get ISFShax installed and use that to dump the MLC.
I have been very busy and responding to your posts late at night and again I have to apologize because it appears I misread your post about isfshax will not install from defuse. It hangs at the GO GO GO. It sounds like you selected the option to rebuild the MLC, which means the data on there might be destroyed. Do you have the 52 Titles on the SD Card you are using with defuse?
You are not selecting the correct options if you are seeing this. ISFShax should look like this, check out my video. https://youtu.be/XgN_S1PgbGU?t=588
You need to select Boot ios.img, which should start ISFShax installation then just follow the onscreen prompt to get it installed.
KF4njYg.jpg
The option that I tried first was:
Patch Isfshax and boot IOS (slc).
It hung at GO GO GO
I then tried the following after watching your video (I had watched three about defuse before contacting you again for help).
Boot ios.img
I got the error message
ancast: failed to open ios.img (2).
Failed to load 'ios.img'!
I was worried that perhaps I had wiped out info, but my console will still start the quick start menu on the gamepad and I can still see the Miis for selection
KF4nh3F.jpg
I do have the 52+5 titles from MLSRestorerDownloader with this console's otp.bin
It appears you are missing the ios.img file or its not located in the correct directory on the SD Card you setup.
Did you download the ISFShax (https://isfsh.ax/) zip from their website? If not download it.
Extract the contents and move everything inside the "sd" folder to the root of your SD Card. If you are asked if you want to merge/replace existing files select yes.
Then go back and try installing ISFShax again. I have attached a picture of what your SD Card should look like, kindly make sure the files in the picture are in the root directory of your SD Card. Also if there are extra files for Defuse, leave them on the SD. They will not show up in the picture below as I am only showing the files that are included with ISFShax.
SDCardSetup.JPG
I did have the directory structure wrong. Unfortunately that was not the problem.
KKziXB2.jpg
Is redNAND an option to get a image of the MLC if isfshax won't install? I noticed in a response in one of your guides that SDIO says there are 3 ways to image the MLC and number 2) was with redNAND.
https://freeimage.host/i/KKzyU9p
I suppose I can give up on the MLC. I believe all the eshop games were stored on the USB SSD drive that we had attached to the system which as far as I know is still healthy.
Based on your picture it doesn't look like an error at all. After the IOS GO GO GO the Wii U should output on the display the ISFShax Installer. You won't see this on the serial console.
Do you have your Wii U plugged into a monitor or tv? As a reminder minute only outputs over HDMI at 1080P.
If you have no output lets try to blindly load ISFShax. So to do this you want to select the boot ios.img option and then once you see IOS GO GO GO in the serial console lets wait a few seconds and then push Eject 3 times followed by Power Button 1 time, then Eject 3 more times. If done successfully the console should turn off.
With ISFShax installed. The Wii U should start with the minute menu without defuse and the power LED on the console will be purple.
To answer your other questions. Yes the redNAND can be used to get an image of the MLC depending on the state of the console. I don't know the specific instructions to make this happen off the top of my head, so I recommend you ask SDIO how to do that.
As for the eshop games. All the consoles I repaired had no issue downloading games that were previously purchased on them, so getting those back isn't a problem. I don't think that has changed in the last couple of months.
Sweet.
I remember you clearly saying that isfshax only outputs on HDMI. I had gotten so used to putty that I didn't even have the monitor on.
MLC is dumping now.