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.
image.png
image2.png
image3.png
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..
IMG_1323.jpgIMG_1324.jpgIMG_1321.jpgIMG_1319.jpg
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?
IMG_13214.jpg
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.
All done. But im pretty sure I did solder that point the first time around tho... I have deleted all the LOGS, erased MLC, and SCFM.img thingy. I am redoing the MLC process again to see if this changes anything. When the system is all done i will dump the logs again and see if anything changes
edit: oh btw, idk if its normal. But the light on my Wii U is always purple. It only turns blue during the installation phase where it blinks blue. Other than that my light is purple during initial setup of the Wii u too. Just wanted to mention that.
Good luck! ;)
Quote from: Frankish424 on Feb 13, 2026, 10:39 AMI 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
Yes a mistake was made in the video. I corrected this using a pined comment on the video as someone else pointed it out previously. I will add it to the description of the video so that hopefully others see the mistake and don't get confused.
I have soldered the point on the NAND-AID to the r26 trace. I erased MLC and the scfm.img and installed the MLC from ground up. I processed through the inital setup like normal. But like the other times, I got stuck in a infinite loading after pressing "next" after being prompted to create a Mii... I Shutdown the console after a while and dumped the logs. I will include the .zip of the logs on this post. Hopefully there's something there giving away the problem.
Quote from: Frankish424 on Feb 13, 2026, 11:07 AMAll done. But im pretty sure I did solder that point the first time around tho... I have deleted all the LOGS, erased MLC, and SCFM.img thingy. I am redoing the MLC process again to see if this changes anything. When the system is all done i will dump the logs again and see if anything changes
edit: oh btw, idk if its normal. But the light on my Wii U is always purple. It only turns blue during the installation phase where it blinks blue. Other than that my light is purple during initial setup of the Wii u too. Just wanted to mention that.
Purple LED is normal. You have ISFShax installed. If you remove it the LED will go back to its factory setting of blue.
Logs are identical. So either they are the same log or nothing has changed.
Have you validated the SD Card is working by putting it into a computer?
This is a European Wii, you downloaded the European SLC/MLC Titles correct?
Since it still shows 32GB, I am suspicious that its not detecting the MicroSD Card you installed into the NAND-AID.
Quote from: tzirf on Feb 13, 2026, 11:51 AMLogs are identical. So either they are the same log or nothing has changed.
Have you validated the SD Card is working by putting it into a computer?
This is a European Wii, you downloaded the European SLC/MLC Titles correct?
Since it still shows 32GB, I am suspicious that its not detecting the MicroSD Card you installed into the NAND-AID.
I did connect the NAND aid sd to my pc to see what it would say. And it says that the PC cannot read the SD before i format it. The first time i put it in the system i did format it to LargeFat32.
Yes, i followed your instructions on the video about downloading the files to my specific Wii U system (EU). I did the same with SLC titles.
Could it be the legs on the MicroSD reader are badly soldered? In the video you mention that EVERY LEG SHOULD MAKE THE MULTIMETER BEEP ()When touching the top of the card reader). is this true? Atleast thats how I understood it.
Based on your pictures I don't think the legs are the issue. When you insert the SD Card into the NAND-AID is it sticky feeling or does it go in smooth? Often times what happens is flux gets inside and prevents a good connection.
Quote from: tzirf on Feb 13, 2026, 12:06 PMBased on your pictures I don't think the legs are the issue. When you insert the SD Card into the NAND-AID is it sticky feeling or does it go in smooth? Often times what happens is flux gets inside and prevents a good connection.
I usually dont add too much Flux so hopefully that shouldn't be the case. The SD-card goes in without issues and goes out. Its snappy and clicks with the locking mechanism.
The Wii U uses a proprietary file system. When you erase the MLC within the minute menu it should setup the SD Card & format it. Since it is a 64GB you don't need a plugin to use it in the Wii U. You can verify if this is working by formatting it on your PC to NTFS, make sure it shows the full 64GB size. Then install it in the Wii U and erase the MLC. When you place it back in your computer it will say it cannot read it. This tells us the Wii U is writing to your SD Card in the NAND-AID.
If this is true, then I don't think there is anything wrong with your NAND-AID. The issue must lie elsewhere. Try re-downloading the MLC/SLC Title files and placing them back on your setup SD Card. Perhaps there is corruption in one of the title files causing the console to hang at the Mii creation screen.
I will try that then. Can i skip the SLC files? Since i can just update the wii u with internet right?
Quote from: Frankish424 on Feb 13, 2026, 12:15 PMI will try that then. Can i skip the SLC files? Since i can just update the wii u with internet right?
Grab both and include them.
I took a look at some other log files and there seems to be an issue with the Wireless. You did mention lag to the gamepad.
Did you unplug any of the 3 wireless modules from the console when you installed the NAND-AID?
My mistake, I overlooked an error. It would seem the Bluetooth Module is defective. Log file contains following error
00:00:11:319: BT: [Err] OHCI initialization failed - rv=0xfffffff6
Quote from: tzirf on Feb 13, 2026, 12:36 PMI took a look at some other log files and there seems to be an issue with the Wireless. You did mention lag to the gamepad.
Did you unplug any of the 3 wireless modules from the console when you installed the NAND-AID?
Yes I did actually. I unplugged the two that has wires running along the black plastic cover. It was in the way so i removed both of the module. They should be correctly installed but what do i know. Is that a huge problem?
Yes console will freeze during boot if the Bluetooth Module is defective or missing. I would suggest making sure its fully seated in the socket and if it is and your still getting the same error then try using a known good one.
Bluetooth module is the one at front of console with no wires. Easy to accidentally knock out of socket while working on the board.
Quote from: tzirf on Feb 13, 2026, 12:47 PMYes console will freeze during boot if the Bluetooth Module is defective or missing. I would suggest making sure its fully seated in the socket and if it is and your still getting the same error then try using a known good one.
I don't have more Wii U parts to test with sadly :(.. I will double check it again and see.
I did the full MLC and SLC titles install again and I get stuck on the same Mii maker screen. So my last hope here i guess is the modules if one of them are loose.
Yeah we need to fix that Bluetooth error in order to proceed. I think your NAND-AID is installed and working properly. I think the rebuild is also successful. I don't see anything in these logs that suggests otherwise.
If you do not have any spare parts, you can either see if you can find a broken Wii U to harvest the Bluetooth module out of or see if anyone is selling just that part. The good news is you can easily replace the module because its not paired or soldered to the Wii U board.
Good news are, I found something broken inside. Bad part is.. I Don't know if this is a paired part. It was not one of the cable connected modules. It was the short little one connected to the FRONT PART of the motherboard.. it says MODEL:WML-C68 on it.
Its not paired and that is the Bluetooth module. Explains the error in the logs.
Well. Im cooked. All the pads on the module are ripped. impossible to repair. I'd have to buy a new one. But where can I find one xD Ebay sells them for $10 and shipping is $40. I bought this whole system for $40. The bluetooth module will cost more than the unit
Might be better to buy a broken Wii U console. Whole console may not cost as much. Which pads on the module are ripped?
IMG_1328.jpg
that is some bad damage. Best to look for a replacement.
Quote from: tzirf on Feb 13, 2026, 02:31 PMthat is some bad damage. Best to look for a replacement.
I managed to snag up a parts console for only $12. Hopefully when it arrives, the Bluetooth module is fully functional.
Excellent! Sounds like a bargain. Best of luck I hope the Bluetooth module is working. In my experience they don't go bad very often and the consoles I have come across that had issues with the Bluetooth module were all because it was physically damaged. Albeit I admit my sample pool of consoles is small compared to all of them out there. Take care installing it. I have big hands and find the Bluetooth module particularly difficult to align before pushing it in place.
I got it up and running. The Bluetooth module was the cause of the issue. Really weird issue tbh but hey, it worked out in the end. Thanks for all the help and troubleshooting!
Quote from: Frankish424 on Feb 25, 2026, 02:10 PMI got it up and running. The Bluetooth module was the cause of the issue. Really weird issue tbh but hey, it worked out in the end. Thanks for all the help and troubleshooting!
You are welcome! Glad you were able to get it working. Cheers