I soldered a NAND-Aid on the device because I got the eMMC failure error when trying to get past Mii maker on the initial setup.

I erased the MLC, installed new MLC and SLC files. I can get into the initial setup again. But exactly at the same time for some reason, when getting prompted to create a Mii on the initial setup the Wii u is stuck on infinite loading???

I can hear the sound going in the background so its not FROZEN but its just stuck on infinite loading??? Idk what to do... What are the odds that it gets stuck exactly where I got stuck before soldering on the NAND-aid too? Except before the nand aid the error came up, now its just infinite loading

edit: Thanks for the very in depth tutorial on youtube btw.I have followed pretty much all your guides. From installing the NAND-AID, diagnosing Wii U, and full MLC erase and repair guide!

update: I erased the MLC again because idk thought it would make it work. But now my Wii U is suuuupper laggy (on the gamepad) and I actually get "system memory error" sometimes when booting into the normal menu and my gamepad is far away from the Wii U

Very strange behavior. Did you test to validate the NAND-AID was being detected and the original eMMC was disconnected? The last time I saw someone run into the same error they had before installing a NAND-AID the issue ended up being they failed to fully cut trace R26, which disabled the eMMC in the Wii U.

Also can you dump your logs and upload them?

I did test the cut trace with a multimeter and got no beep... I tested it later on with the nand-aid installed too and still heard no beep. I will be stripping the WII U a little later to double check the trace and cut it further to be extra sure. Just to make it clear tho, im not running into the same ERROR. Im just getting STUCK on the same screen as last time.

Im not too sure what logs you want so I'll just put it my latest "LOG14". I cant send files for some reason and i cant paste my whole log code in there because its too long so i send only the last part of the log and the beginning of the log. When trying to send .txt file it says im not allowed to send that type of file.

2014-04-02 03:37:08
Cafe OS SDK Version 2.13.01 Build 69088 Branch sdk_2_13
Espresso:       0x0000700100000201
Latte:          0x0000409f
System mode:    0x100000
Boot flags:     0x84010000
Security Level: 0x1e
Key Type:       0xfffffffc
Prod Version:   0x5
Serial:         107474353
Model:          WUP-101(03)
Prod Area:      0x4
Game Area:      0x4
5GHz Code:      0x18
DRH:            0x190c
BOOT1:          0x20b9
+0x000500301001120a:0x00000064
+0x000500301001020a:0x000000b4
+0x0005001010040200:0x00000101
ace: DevFsm: There are now a total of 1 connected devices.
00:00:02:017: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.014 s.
00:00:02:020: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.017 s.
00:00:02:023: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.020 s.
00:00:02:026: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.023 s.
00:00:02:029: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.026 s.
00:00:02:032: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.029 s.
00:00:02:035: UHS1 Trace: CltIfFsm(V057e|P0341|IF6): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.032 s.
00:00:02:037: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.035 s.
00:00:02:040: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.038 s.
00:00:02:043: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.041 s.
00:00:02:046: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.043 s.
00:00:02:049: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.046 s.
00:00:02:051: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Acquired by client in pid 6.
00:00:02:053: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Enable endpoints 0x00080000.
00:00:02:093: __ccr_hid_attach_add_interface: idx 0 ep 3
00:00:02:095: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Acquired by client in pid 6.
00:00:02:097: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Enable endpoints 0x00100000.
00:00:02:137: __ccr_hid_attach_add_interface: idx 1 ep 4
00:00:02:139: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Acquired by client in pid 6.
00:00:02:142: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Acquired by client in pid 6.
00:00:02:144: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Activating bAlternateSetting 0.
00:00:02:148: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Acquired by client in pid 6.
00:00:02:150: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Acquired by client in pid 6.
00:00:02:152: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Activating bAlternateSetting 0.
00:00:02:155: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Acquired by client in pid 6.
00:00:02:157: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Enable endpoints 0x08001000.
00:00:02:160: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Acquired by client in pid 6.
00:00:02:162: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Acquired by client in pid 6.
00:00:02:164: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Activating bAlternateSetting 0.
00:00:02:169: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Acquired by client in pid 6.
00:00:02:171: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Acquired by client in pid 6.
00:00:02:173: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Activating bAlternateSetting 0.


00;02;32;405: ErrEula: thread=0x100457e0, stackSize=      63 KB, stackBase=0x1069b4f8, stackEnd=0x1068b500 (ErrEulaCalc)
00:02:32:535: CSC: Product Code: WUP-N-HASP, Title Version (major): 16
00:02:32:540: CSC: Repaired: FALSE, Wagon: FALSE
00:02:32:544: CSC: InitialLaunch stage: 0
00:02:32:546: CSC: USB Storage Connected: FALSE, Device Type: NAND
00:02:32:579: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00:02:32:584: CSC: TV Port: HDMI, TV Aspect Ratio: 16:9
00:02:32:590: CSC: TV Resolution: TV_1080P
00:02:32:590: CSC: CODE: [HASJ-001X-X375]
2026-02-12 17:28:33 - log collection event from pid 21
00;02;32;471: (1)5.5.5 E
00;02;32;471: (2)WUP-101(03)
00;02;32;471: (3)FEH107474353
00;02;32;471: (4)HASJ-001X-X375
00:02:32:594: MCP: life time number of fatal errors - 12
00:02:32:595: MCP: storing current logs as '/vol/system/logs/13.log'
00:02:33:095: MCP: Finished storing current logs as '/vol/system/logs/13.dsc'
00;02;33;015: ErrEula: thread=0x100457e0, stackSize=      63 KB, stackBase=0x1069b4f8, stackEnd=0x1068b500 (ErrEulaDrawTV)
00;02;33;015: ErrEula: thread=0x100457e0, stackSize=      63 KB, stackBase=0x1069b4f8, stackEnd=0x1068b500 (ErrEulaDrawDRC)
00;02;35;959: ErrEula: thread=0x100457e0, stackSize=      63 KB, stackBase=0x1069b4f8, stackEnd=0x1068b500 (ErrEulaDisappearError)
00:02:42:084: NET: >>> Received request to kill all sockets.
00:02:42:084: NET: Socket binding (resource: 0x00001a80)
00:02:42:084: NET: Change admin state (2 -> 2)(iface:0 link:2)
00:02:42:085: NET: Change admin state (2 -> 2)(iface:1 link:2)
00:02:42:192: NET: >>> Received request to kill all sockets.
00:02:42:192: NET: Socket binding (resource: 0x00001a80)
00:02:42:192: NET: Change admin state (2 -> 2)(iface:0 link:2)
00:02:42:193: NET: Change admin state (2 -> 2)(iface:1 link:2)
00:02:42:684: NET: Change admin state (2 -> 1)(iface:0 link:2)
00:02:42:685: [WD]>>>> Linkup msg from Net
00:02:42:693: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:02:42:697: NET: Change admin state (2 -> 2)(iface:1 link:2)
00:02:42:697: NET: Change admin state (1 -> 1)(iface:0 link:3)
00:02:42:796: [WD]>>>> Linkup msg from Net
00:02:42:804: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:02:43:809: NET: Change admin state (1 -> 2)(iface:0 link:2)
00:02:46:809: NET: Change admin state (2 -> 1)(iface:0 link:2)
00:02:46:810: [WD]>>>> Linkup msg from Net
00:02:46:819: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:02:47:823: NET: Change admin state (1 -> 2)(iface:0 link:2)
00:02:50:823: NET: Change admin state (2 -> 1)(iface:0 link:2)
00:02:50:823: [WD]>>>> Linkup msg from Net
00:02:50:832: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:02:51:836: NET: Change admin state (1 -> 2)(iface:0 link:2)
00:02:51:894: NET: >>> Received request to kill all sockets.
00:02:51:894: NET: Socket binding (resource: 0x00001a80)
00:02:51:894: NET: Change admin state (2 -> 2)(iface:0 link:2)
00:02:51:895: NET: Change admin state (2 -> 2)(iface:1 link:2)
00:02:55:302: CSC: Product Code: WUP-N-HASP, Title Version (major): 16
00;02;55;177: ErrEula: thread=0x100457e0, stackSize=      63 KB, stackBase=0x1069b4f8, stackEnd=0x1068b500 (ErrEulaAppearError)
00;02;55;177: ErrEula :ErrorCode = 1031601
00:02:55:307: CSC: Repaired: FALSE, Wagon: FALSE
00:02:55:311: CSC: InitialLaunch stage: 0
00:02:55:313: CSC: USB Storage Connected: FALSE, Device Type: NAND
00:02:55:346: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00:02:55:351: CSC: TV Port: HDMI, TV Aspect Ratio: 16:9
00:02:55:357: CSC: TV Resolution: TV_1080P
00:02:55:357: CSC: CODE: [HASJ-001X-X375]
2026-02-12 17:28:56 - log collection event from pid 21
00:02:55:358: MCP: life time number of fatal errors - 13

Ill send pictures of different logs from inside minute menu, if they help.

You can zip up the entire log directory with meta.bin and attach that to your post. Before dumping the logs, remove the current logs directory from your SD Card and then dump them. Let me know if the same errors above shows up about "error copying slc: /sysl/logs/4.log" for example. 

What SD Card are you using in the NAND-AID? Size, Make and Model?

The SD card is a- "Kingstone CANVAS select plus", MicroSDXCi, 64GB

SD Card is fine.

Do you have the Disc drive connected? Console doesn't see it and you cannot properly boot the Wii U without it.

Quote from: tzirf on Feb 13, 2026, 09:53 AMDo you have the Disc drive connected? Console doesn't see it and you cannot properly boot the Wii U without it.

I actually can't even boot in without the Disc drive connected. I get an error message telling me about a disc drive error. With the Disc drive connected i can get all the way to the first mii maker thing. When the Wii U logo comes up and load its infinite loading from there on.

edit: I have opened the console up again and cut the trace further. Do I need to solder both sides of that cut trace connector to the NAND-aid? I noticed in your installation guide you only put a little solder on the copper pad but never actually connected it to the NAND-aid. (I know you connected the Left side to the NAND-aid, but im talking about the Right side)

Well perhaps this log file is from when there was no disc drive connected. I don't see anything else that stands out. Just to be clear, this is the original drive that came with this console? I am asking because they are paired and you cannot swap them out.

Quote from: tzirf on Feb 13, 2026, 10:00 AMWell perhaps this log file is from when there was no disc drive connected. I don't see anything else that stands out. Just to be clear, this is the original drive that came with this console? I am asking because they are paired and you cannot swap them out.

I am the first to open up and work on this system... And yes i did try to start it without disc drive, that should explain the log about disc drive error.

Is there really nothing else to check??? I have pictures of my soldering if thats of help..

I saw your edit above, we can rule out R26 as you stated you checked it for continuity and got nothing. So we know that is good.

I see in the log its detecting a 32GB SD Card, but you told me you have a 64GB SD Card in the console. So that means its probably seeing the original eMMC which explains the issue.

I looked over your pictures and your missing solder on the NAND-AID to connect it to the console. R26 trace where you cut must be soldered to the NAND-AID on both sides. See attached picture, I have circled it in blue   

You said in my guide I made a mistake, where? I would like to correct it if that is the case. Is it the video or written guide?

 

I followed this guide! https://youtu.be/rvxdtk7mOCE?si=wC5djO86IO32Y3yA&t=676
You can see in the video that you do put some solder on the pad, but it never looks connected to the R26 trace. So I just figured it doesn't need to be connected

edit: Where exactly am I missing solder? Or did you refer to the R26 trace? because I have tried the system with and without solder on that point

edit: Ok sweet, so the problem is that the system for some reason still detects the eMMC right? What could be the cause for that?

In the picture I posted, you must have solder connecting the NAND-AID to the Wii U pad. It is trace R26 that must be connected to the NAND-AID on both sides. Be careful not to bridge the cut you made as its a small area and easy to do if too much solder is used.