Tutorial  Updated

How To: Upgrading / Rebuilding Wii U Internal Memory (MLC)

Warning

This tutorial is only for advanced users and has a serious risk of bricking the console. Make sure you read it completely before executing any step and that you understand every step and its implications. With de_Fuse everything should be unbrickable if you know how.

You should at least have a backup of SLC and SLCCMPT, as we can’t rebuild them at the moment. (can be done in minute_minute, so there is no excuse). We had two cases where the SLC corrupted for an unknown reason, so a backup is essential.

What is this for?

This tutorial goes into rebuilding the MLC from scratch on a clean media. This can become useful, if
  • the MLC (eMMC) chip died or corrupted the filesystem
  • the SCFM (SLC cache for MLC) became inconsistent
  • you want to upgrade the capacity of the internal storage.
  • you want to set up a redNAND without SCFM
If you have a bad eMMC chip, but the recovery still works (which is most likely), then there are also ways to fix it without a complete reformat.
If the LED is blinking blue, you have a SLC problem and not a MLC problem, so this tutorial won't help with that.

It will format your MLC, so all data on the internal Wii U memory will be lost.

Update

13.03.2024 - The wafel_setup_mlc.ipx now uses a built in IOSU function to create system folders, that should make sure the permissions are right, which caused problems with game updates in the past. It will also recreate the update folder (so system updates won't be blocked by that)

Prerequisites

Backing up save games


Do a backup of what you want to preserve, like savegames and Miis.
For Backing up Save games, it is recommended to use SaveMii. That requires that you have Tiramisu or Aroma running.
You can also move your savgames (or whole games) to USB, which should still be readable. When recreating the users after the rebuild, you just have to be carefull to create the users in the right order, to make the ID’s match. A backup by other means (Like savemii) is still recommended.
If you are using this tutorial to fix a failing eMMC you might not be able to use the other Backup options. In that case use the Dump MLC option in the Recovery. You can extract your data from there using wfs-extract.

Storage Options

The Wii U has two ways of connecting internal memory, each with its own drawbacks:
  • SDIO – On retail consoles the internal memory is a eMMC chip connected through an internal SDIO bus to the Latte chip. This SDIO bus can also use SD cards (hence the name SD IO). Access to media connected on the SDIO is cached through a file on the SLC, presumably to reduce writes on the MLC. This cache is called SCFM and it is the reason why you always need to backup / restore SLC and MLC together and doesn’t allow easy swapping of multiple SDs.
    IOSU also only supports 3 sizes of media on this bus: <=8GB, 32GB and 64GB. The size will be limited to the biggest it fits, the rest is unusable. This bus is limited to 26MB/s (4bit@52Mhz). For replacing the eMMC with an micro SD you can use MLC2SD or a similar Interposer. Soldering and micro SD adapter using wires, works too.
    It is recommended to use a 64GB Sandisk Max Endurance card (But similar card should also be fine), since the Wii U is known for writing much.

  • SATA – The Disc drive is connected through SATA, the connectors are different but the electrical signals are still the same. Some Kiosk consoles used this Interface to connect to a HDD. The type of the SATA device can be configured in the SEEPROM, so we can configure our retail consoles to also use a SATA HDD / SSD.
    NOTE: @QuarkTheAwesome is building an SATA adapter for that purpose, available soon™.

    The advantage of using this interface is, that the size isn’t limited (well WFS is limited to 2TB) and it doesn’t use SCFM, which makes some things easier and improves performance in some circumstances. The obvious disadvantage is that you can’t use your disc drive anymore. Without the Disc Drive vWii System Menu doesn't work. vWii Injectes / Wii VC from the eShop can still be used, but only when installed to USB. Also you still might need to disable the MLC on the SDIO bus, or else the wii u might still use the SDIO one if the SATA device takes too long to init.

  • redNAND – redirects the read / writes to one or more of the internal storage devices to paritions on the SD card. You can create an arbitrary size MLC partition on the SD card and set it up using this tutorial. SCFM can be easily disabled for the redNAND. The 64GB limit does not exist for redNAND if the SCFM is disabled. For redNAND we have a dedicated Tutorial here: https://gbatemp.net/threads/fixing-...-soldering-using-rednand-with-isfshax.642268/

Does that mean we can’t get more than 64GB on the SDIO bus? No, BUT it requires ISFShax / defuse to boot the console every time. @GaryOderNichts created a patch to remove the limits and always use the maximum size of the SDIO media and it also disables SCFM, because SCFM doesn’t work with more than 64GB and disabling SCFM improves performance and reduces wear on the SLC, at the cost of increasing wear of the MLC media. I packaged this patch in wafel_unlimit_mlc.

Rebuilding the MLC

Now that you decided what media you want to use as MLC, we can start with the actual process:
  1. Download all the mlc system titles for your region from NUS. This can be done conveniently with MLCRestorerDownloader by @Xpl0itU. Copy the otp.bin from the SD to the folder with the MLCRestorer Downloader so it can get the common key from there.

    You will get the output/MLC/{region} directory, which then contains a directory for each title. In total there should be 52 titles totaling ~1.1GiB.

    If your console has an old firmware it might also be necessary to get the latest SLC titles.

  2. On the root of your SD card (the one that will go in the front slot, not the MLC replacement) create a folder wafel_install. Then copy all 52 titles to the wafel_install folder, so it now contains the 52 subfolders, one for each title. If you want to reinstall / update SLC titles, you would also put them there.

  3. Attach your MLC media of choice. (If you are using SATA got to Backup and Restore, then at Set SATA Device in SEEPROM select GEN2-HDD (Kiosk CAT-I with HDD)).
    For installing MLC2SD look here: https://gbatemp.net/threads/using-n...emmc-fix-160-0103-system-memory-error.636361/ at the Soldering section.

  4. If you install to eMMC / MLC2SD, got to Backup and Restore and select Erase MLC and Delete scfm.img. If the Erase MLC fails, you can ignore that if it wasn't formatted as MLC before (from a failed install or so).

  5. Put the wafel_setup_mlc.ipx on the SD card in /wiiu/ios_plugins. If you want more than 64GB on SDIO you also need to put the wafel_unlimit_mlc.ipx there. If you install with wafel_unlimit_mlc.ipx, it will be permanently required and therefore also permanently requires ISFShax or defuse.

  6. [Optional, only when using defuse] Open the serial monitor on the PC (Putty / minicom) for defuse to see the setup progress. There will be no display output in the Wii U itself. I attached the whole serial log of a successfull install as a reference.

  7. Select Patch (sd) and boot IOS (slc) in minute to start the setup of your fresh MLC.During the setup you won't see anything on the screen. You have to go by the power led.
    The power LED will flash blue, while it is installing the titles.
    if something goes wrong the LED will turn orange, but it will continue as long as it is blinking.
    The LED will become static once it finished. You can now power off the console.
    If the led is blinking red, something fatal happend. Ask for help.
    During the setup a short log gets written to the SD: wafel_setup_mlc.log.
    In the end it will enable the initial setup on the next boot.

  8. Remove the wafel_setup_mlc.ipx from /wiiu/ios_plugins on the SD.

  9. Boot the console. Patch (sd) and boot IOS (slc)

  10. If everything worked, the initial setup should launch.

ISFShax only: Finalizing

If you are using the wafel_unlimit_mlc.ipx you need to keep ISFShax installed. If you haven't done already complete the "Booting without SD" step form the ISFShax tutorial but also add the wafel_unlimit_mlc.ipx renamed to 9unlimit.ipx to the /storage_slc/sys/hax/ios_plugins directory.
If you are not using the wafel_unlimit_mlc.ipx you can either uninstall ISFShax or keep it as a brick protection. If you keep it complete the "Booting without SD" step form the ISFShax tutorial.
The Wii U should now boot automatically if you don't have an SD in.
You probably also want to enable the autobooting now.

See Also

https://gbatemp.net/threads/wii-u-internal-storage-upgrades-are-possible.635629/

Pictures

512 GB SD card:
img_20230702_021647-jpg.381270


@QuarkTheAwesome 120 GB SSD:
img_2709-jpg.381271


Thanks

 

Attachments

  • serial-log.txt
    87.6 KB · Views: 47
Last edited by SDIO,

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
try to use the unlimit plugin without rednand and see if that changes something.
What brand/model are the sd cards?
I tried with and without unlimit, multiple times, even went to an older version of the setup file just in case...

In the nand-aid I have tried a San Disk 64 Max Endurance, a 128 Samsung Evo, a micro center 64 I had laying around.

In the front for redNand, I have tried a Trancend 64, the 64 Microcenter card, and two 32 San Disc cards I have as well.

I dumped the OTP again, and and redownloading titles, including SLC as well (though I have tried with and without already, and done multiple OTP files dumps already)... I think this thing just has some weird super brick.
 

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
2,263
Trophies
0
Age
28
XP
1,382
Country
Germany
I don't have an explanation. I don't think it has anything to do with the eMMC.
Maybe the dram has an error and that location gets used when you try to boot as a buffer for the mlc read or something like that.

What happens when you try to use wfs-extract against the nand aid SD or the mlc partition for the redNAND?
 

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
I don't have an explanation. I don't think it has anything to do with the eMMC.
Maybe the dram has an error and that location gets used when you try to boot as a buffer for the mlc read or something like that.

What happens when you try to use wfs-extract against the nand aid SD or the mlc partition for the redNAND?
I haven't done this before, is there a good resource to learn about it?
Post automatically merged:

I don't have an explanation. I don't think it has anything to do with the eMMC.
Maybe the dram has an error and that location gets used when you try to boot as a buffer for the mlc read or something like that.

What happens when you try to use wfs-extract against the nand aid SD or the mlc partition for the redNAND?


ok I think I figured something out. I used Win32Disc Imager to make an image of the SD card, this is my result running wfs-extract. The first 2 are attempts to read the SD card directly, but that didn't work so I made an image to try that, on the third attempt here:
1707435376100.png

Any ideas?
Post automatically merged:

Made and image of the MLC of redNand as well. same issue... even checked against our first dump of OTP and Seeprom, before we did ISFXhax.

1707438688106.png
 
Last edited by TheSunnyMachine,

V10lator

Well-Known Member
Member
Joined
Apr 21, 2019
Messages
2,635
Trophies
1
Age
36
XP
5,494
Country
Germany
This might be an extemely stupid question but @TheSunnyMachine you didn't but all these card on eBay or some shady side but from a trusted source, correct?
a San Disk 64 Max Endurance, a 128 Samsung Evo, a micro center 64
a Trancend 64, the 64 Microcenter card, and two 32 San Disc cards
Just asking cause even the wfs-extract result looks like the cards are damaged/faked but seeing you tried around 6 different cards...

Another thing that just pops into my mind is that maybe the SD card reader on your PC is bad, hence it corrupts all images you try to write on the cards and shows this weird result from wfs-extract. Do you have another card reader to test?

Also open the otp.bin in a hex editor, please, and confirm it's not all zeroes. The thing with wfs-dump might be a bad OTP dump, too...
 

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
This might be an extemely stupid question but @TheSunnyMachine you didn't but all these card on eBay or some shady side but from a trusted source, correct?


Just asking cause even the wfs-extract result looks like the cards are damaged/faked but seeing you tried around 6 different cards...

Another thing that just pops into my mind is that maybe the SD card reader on your PC is bad, hence it corrupts all images you try to write on the cards and shows this weird result from wfs-extract. Do you have another card reader to test?

Also open the otp.bin in a hex editor, please, and confirm it's not all zeroes. The thing with wfs-dump might be a bad OTP dump, too...
lol.

I feel you here. No I bought all these cards off Amazon. I use this SD card reader daily, and I used it just to Soft mod a Wii and my Wii U just the other day with no issues.

The cards are either brand new or ones I used to use for 4k video recording, so I know they are good. The only one that might be slightly sketchy is the Micro Center one, but I bypassed that and ruled out that card as the source of the issue by trying multiple other cards.

I did order some new SD card ports I am going to try and switch out the one on the front of the Wii U because it was slightly damaged, but I did test it with an extension and a ribbon cable and all the pins are making a connection.

My opt looks fine in hex
1707447299652.png
 

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
2,263
Trophies
0
Age
28
XP
1,382
Country
Germany
The SD card works fine during the install so I would rule out problems with the connection.
For wfs-extract you need to use the --mlc flag and you don't need to specify the seeprom.
In Windows accessing the raw drives is a little tricky , it doesn't work over the drive letter. You need to access it over the physical device https://stackoverflow.com/questions/327718/how-to-list-physical-disks
 

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
The SD card works fine during the install so I would rule out problems with the connection.
For wfs-extract you need to use the --mlc flag and you don't need to specify the seeprom.
In Windows accessing the raw drives is a little tricky , it doesn't work over the drive letter. You need to access it over the physical device https://stackoverflow.com/questions/327718/how-to-list-physical-disks
Ok I was only able to get a dump of the 128GB card for some reason. Everything else is giving me the bad key error.

What should I look for in the dump?
Post automatically merged:

quick update: I am not sure about this behavior... If I try to launch redNand without an SD card in the Nandaid, it will not boot...

Do I need to remove CLK from Ground for it to work .. does the original Nand need to be connected for redNand to boot?
 
Last edited by TheSunnyMachine,

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
Do you get errors during the extract?
No
Post automatically merged:


So, I have ordered another wii U that has faulty disc drive. I will swap in a good one, and move this nandaid + card over there. That will at least help eliminate some of the potential issues. The nandaid I am using has a burnt edge connector for the CLK to ground trace, but I just put a 0.1mm wire in on the trace. I even confirmed the wire was making a connection by restoring it to the original CLK trace.

It seems rednand won't boot without an SD card because some sort of nand memory needs to be present. I removed the SD card and moved the wire to the original clk line using the original nand chip and rednand at least tried to boot. But I no matter what all I get is the same memory error.
Post automatically merged:

Could the slc and mlc be going out of sync after each attempt? Maybe they've been out of sync the entire time?

I'm not sure. There was also 2 attempts to restart the OS from recovery menu apparently before the NandAid was installed. But the otp and seeprom were grabbed fresh from before I downloaded titles, programed, and booted .. but since then I've been using the same opt, except once, I attempted to use the pre mod opt.

Do I need to redump the otp and seeprom, program the mlc with the new otp titles, then boot?

Could something be out sync, I don't totally understand what could be going wrong and want to make sure that all this 'fixing' hasn't thrown things out sync somehow. I read that the slc and mlc have to be in sync and wonder if that's the issue.
Post automatically merged:

.. or is this only important when trying to rebuild the original nand on the NandAid SD card?

Does the sync issue not matter when building a fresh nand from the downloaded titles?
 
Last edited by TheSunnyMachine,

V10lator

Well-Known Member
Member
Joined
Apr 21, 2019
Messages
2,635
Trophies
1
Age
36
XP
5,494
Country
Germany
So, I have ordered another wii U that has faulty disc drive. I will swap in a good one
That won't work as the Wii U and the disc drive exchange some keys and if they don't match... AFAIK there's still no method to exchange the disc key in the SEEPROM.

You should be able to use ISFSHax or something to completely disable the disc drive through, so the Wii U doesn't check the key, but ofc. you also can't use the disc drive that way / it will be dead.
Maybe you could replace the disc drive with a SATA HDD/SSD to make a Wii U with 2 TB internal storage, not needing any USB drive at all (see https://github.com/ashquarky/usata but keep in mind that this is still in development).
 

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
That won't work as the Wii U and the disc drive exchange some keys and if they don't match... AFAIK there's still no method to exchange the disc key in the SEEPROM.

You should be able to use ISFSHax or something to completely disable the disc drive through, so the Wii U doesn't check the key, but ofc. you also can't use the disc drive that way / it will be dead.
Maybe you could replace the disc drive with a SATA HDD/SSD to make a Wii U with 2 TB internal storage, not needing any USB drive at all (see https://github.com/ashquarky/usata but keep in mind that this is still in development).


My plan was to board swap the drives or see if I can just repair the drive with parts from a known working drive. I know the board for the disc drive is married to the console, but as long as the issue is not that board or the chip, I should be able to swap.
 
  • Like
Reactions: V10lator

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
2,263
Trophies
0
Age
28
XP
1,382
Country
Germany
So, I have ordered another wii U that has faulty disc drive. I will swap in a good one, and move this nandaid + card over there. That will at least help eliminate some of the potential issues. The nandaid I am using has a burnt edge connector for the CLK to ground trace, but I just put a 0.1mm wire in on the trace. I even confirmed the wire was making a connection by restoring it to the original CLK trace.
Why move the NAND-AID over, if the new one has a good eMMC. When removig the NAND-AID you will probably rip some traces.

It seems rednand won't boot without an SD card because some sort of nand memory needs to be present. I removed the SD card and moved the wire to the original clk line using the original nand chip and rednand at least tried to boot.
Yes redNAND needs the mlc device to be oresent to redirect the rw from it.

I have another stroopwafel plugin, which replaces the mlc with the whole sd (so not just a partition) and the SD with USB.


But I no matter what all I get is the same memory error.
I bet on bad DRAM. Maybe I still have the memory test code fro minute somewhere


Could the slc and mlc be going out of sync after each attempt? Maybe they've been out of sync the entire time?
It doesn't matter with the unlimit plugin or redNAND as that bypasses SCFM.

I'm not sure. There was also 2 attempts to restart the OS from recovery menu apparently before the NandAid was installed. But the otp and seeprom were grabbed fresh from before I downloaded titles, programed, and booted .. but since then I've been using the same opt, except once, I attempted to use the pre mod opt.

Do I need to redump the otp and seeprom, program the mlc with the new otp titles, then boot?
The otp never changes, it is read only you need to dump it only once for each console. Also for the download only the common key is needed from the OTP, which is the same for all retail consoles.
SEEPROM is only changes for boot1 updates (it has the boot1 version) or during factory reset, the usb key gets changed or when you change the SATA type.


Could something be out sync, I don't totally understand what could be going wrong and want to make sure that all this 'fixing' hasn't thrown things out sync somehow. I read that the slc and mlc have to be in sync and wonder if that's the issue.
Post automatically merged:

.. or is this only important when trying to rebuild the original nand on the NandAid SD card?

Does the sync issue not matter when building a fresh nand from the downloaded titles?
When the mlc get's formatted the new file system is consistent, not matter what was there before.


That won't work as the Wii U and the disc drive exchange some keys and if they don't match... AFAIK there's still no method to exchange the disc key in the SEEPROM.
I think just no one has bothered trying it so far. In theory you would only need to swap the disc drive key in the decrypted seeprom and recrypt it
 

V10lator

Well-Known Member
Member
Joined
Apr 21, 2019
Messages
2,635
Trophies
1
Age
36
XP
5,494
Country
Germany
and move this nandaid + card over there.
Oh, I completely overlooked that. Thanks for highlighting it Jan.

I would also advise to not desolder the NAND-AID from where it is now. Desoldering it is a really rough job. In case the new console really has a bad eMMC, you need a second NAND-AID and purchased the old one from me (either at the trading area here or on eBay) I'm willing to send you a second one free of charge. Just send me a message on whatever site you used to purchased the NAND-AID, so I know you're really one of my customers and am able to grab the old adress for the new letter. :)

//EDIT: Also you will have to reformat the card as it's encrypted with keys from the old console so the new one won't be able to decrypt/read the data on it. In case you want to backup your savegames there's wfs-extract: https://github.com/koolkdev/wfs-tools
 

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
Why move the NAND-AID over, if the new one has a good eMMC. When removig the NAND-AID you will probably rip some traces.


Yes redNAND needs the mlc device to be oresent to redirect the rw from it.

I have another stroopwafel plugin, which replaces the mlc with the whole sd (so not just a partition) and the SD with USB.



I bet on bad DRAM. Maybe I still have the memory test code fro minute somewhere



It doesn't matter with the unlimit plugin or redNAND as that bypasses SCFM.


The otp never changes, it is read only you need to dump it only once for each console. Also for the download only the common key is needed from the OTP, which is the same for all retail consoles.
SEEPROM is only changes for boot1 updates (it has the boot1 version) or during factory reset, the usb key gets changed or when you change the SATA type.



When the mlc get's formatted the new file system is consistent, not matter what was there before.



I think just no one has bothered trying it so far. In theory you would only need to swap the disc drive key in the decrypted seeprom and recrypt it


Thank you, I understand now.

If there is a memory test that might help.

..

Can I try that stroolpwafel that replaces the mlc with the full SD card?

...

Also, I have already removed the nand-aid a couple of times using low melt solder and patience. I'm pretty good at soldering so I know how to carefully do this stuff without breaking anything, even if I did tear some traces, this system is basically dead and I could restore them pretty easily.


But I understand your concern.
...

I got this NandAid from voultar when he first started selling them. I might order 5 off jlcpcb if I need some more. I actually have a second one already as well.

If I can get this console working I was going to just restore the original nand connection and use rednand on it after I remove the NandAid.

I figured it would be best to upgrade the nand on the other console even if the emmc is fine right now as emmc won't last forever anyway and it will be easier to do it now since I'll be in the console repairing either filters or the disc drive board.
Post automatically merged:

Oh, I completely overlooked that. Thanks for highlighting it Jan.

I would also advise to not desolder the NAND-AID from where it is now. Desoldering it is a really rough job. In case the new console really has a bad eMMC, you need a second NAND-AID and purchased the old one from me (either at the trading area here or on eBay) I'm willing to send you a second one free of charge. Just send me a message on whatever site you used to purchased the NAND-AID, so I know you're really one of my customers and am able to grab the old adress for the new letter. :)

//EDIT: Also you will have to reformat the card as it's encrypted with keys from the old console so the new one won't be able to decrypt/read the data on it. In case you want to backup your savegames there's wfs-extract: https://github.com/koolkdev/wfs-tools


I appreciate the offer but I didn't buy them from you. Thank you!

My plan was to use the minute delete mlc option, will that cover the reformat or should I write 0's to the drive?
Post automatically merged:

Oh, I completely overlooked that. Thanks for highlighting it Jan.

I would also advise to not desolder the NAND-AID from where it is now. Desoldering it is a really rough job. In case the new console really has a bad eMMC, you need a second NAND-AID and purchased the old one from me (either at the trading area here or on eBay) I'm willing to send you a second one free of charge. Just send me a message on whatever site you used to purchased the NAND-AID, so I know you're really one of my customers and am able to grab the old adress for the new letter. :)

//EDIT: Also you will have to reformat the card as it's encrypted with keys from the old console so the new one won't be able to decrypt/read the data on it. In case you want to backup your savegames there's wfs-extract: https://github.com/koolkdev/wfs-tools
BTW, your link in your profile for the Nand-aid is giving errors:
1707591025925.png


I went ahead and bought your stock on ebay, because I do plan on finding broken consoles and fixing them up, so having a few more on hand will be helpful.

I will probably just treat this wii U that is throwing memory errors no matter what as a donor board, unless I can figure out which ram module is bad, but I don't have a scope and I don't think thermals will show that. I could use some parts from this Wii U anyway to fix up some other consoles, so it's not a total loss.

I appreciate the help overall. I will most likely be buying more Nand-aids from you as well when you have more in stock. My overall goal is to find broken consoles, fix them up, and re-sell them.

I bought the last of your 3.0 versions, can you let me know where to double check for a possible short with these boards vs the 4.0 version? Should I just stick with the ground arm instead of the hole for this version?
 
Last edited by TheSunnyMachine,

V10lator

Well-Known Member
Member
Joined
Apr 21, 2019
Messages
2,635
Trophies
1
Age
36
XP
5,494
Country
Germany
your link in your profile for the Nand-aid is giving errors
That's a security feature of GBATemp, see:
In order to reduce scams and for other reasons, only confirmed GBAtemp members are able to access the Trading Area. To become a confirmed member, you must have a minimum of 100 valid posts on the forums. Posts in the Edge of the Forum section do not count towards this, and neither do deleted posts. Do not spam in order to reach 100 posts just to gain access; if you do, your access will be permanently revoked. Once the needed 100 posts are reached, your member group will automatically be changed from "Newcomers" to "Members", and the Trading Area will be listed under the Site Discussions section (in place of the link to this wiki page).
(Source: https://wiki.gbatemp.net/wiki/Trading_Area )

I'm really sorry about this. Had discussions with GBATemp moderators and admins in the past but rules are rules and they won't relax them for me.

can you let me know where to double check for a possible short with these boards
It's a short with the PCB itself and the micro SD slot. This short happens when a card is inserted only through so it's not simple to measure, esp when the slot is not soldered to the PCB.

To fix this I'm adding a small piece of transparent tape to each SD slot before packaging. This tape acts as an insulation layer between the PCB and the slot. So just don't remove that tape and you'll be fine. ;)
Would show you a picture of a slot with piece of tape added but I ran out of tape when packaging the last 3 NAND-AID v3s yesterday for (I guess) you.

//EDIT: Don't get me wrong, all slots I packaged have this added. So yours have it, too. I just don't have any more tape to add it to an unpacked slot and packed ones are shipped already.
 
Last edited by V10lator,

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
That's a security feature of GBATemp, see:

(Source: https://wiki.gbatemp.net/wiki/Trading_Area )

I'm really sorry about this. Had discussions with GBATemp moderators and admins in the past but rules are rules and they won't relax them for me.


It's a short with the PCB itself and the micro SD slot. This short happens when a card is inserted only through so it's not simple to measure, esp when the slot is not soldered to the PCB.

To fix this I'm adding a small piece of transparent tape to each SD slot before packaging. This tape acts as an insulation layer between the PCB and the slot. So just don't remove that tape and you'll be fine. ;)
Would show you a picture of a slot with piece of tape added but I ran out of tape when packaging the last 3 NAND-AID v3s yesterday for (I guess) you.

//EDIT: Don't get me wrong, all slots I packaged have this added. So yours have it, too. I just don't have any more tape to add it to an unpacked slot and packed ones are shipped already.
I see, it's probably the exposed pins under the micro sd card slot and the surface of the board. Good to know. Thank you.
 

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
Good news! The console I bought with the faulty Disc Drive just needed the filters on the drive line replaced. Took them from the wii U that wouldn't boot with the nand-aid, etc... and moved the nand-aid + the SD cards over to the new console and go that one working with the 64GB card. I did have an error when trying to save the SLC to the 32GB card, so I swapped the Micro SD card Adapter I was using for a different one and that fixed it.... Not sure if the Adapter I was using is the issue, but I was having errors writing to the card.

I bought a stencil and some solder balls, gonna reball the memory on the other wii U and see if we can't get it working.
 

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
2,263
Trophies
0
Age
28
XP
1,382
Country
Germany
I don't think reballing the memory works help was it seems to mostly work else it wouldn't boot that far
 

TheSunnyMachine

Active Member
Newcomer
Joined
Feb 6, 2024
Messages
33
Trophies
0
Age
43
XP
74
Country
United States
I don't think reballing the memory works help was it seems to mostly work else it wouldn't boot that far
Yea, it's a long shot, but without a way to test for memory errors, and without finding some donor or replacement memory, reflowing or re-balling them is my only way to see if it's just a possible loose connection. I will look for replacement memory or wait till I have a donor.

Either way, I want to try and get to the bottom of this issue eventually.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Lol rappers still promoting crypto