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 the SLC, as we can’t rebuild it easily. (a backup 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. [not needed if you just reinstall to the existing eMMC] 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. Check that the wafel_setup_mlc.ipx deleted itself from /wiiu/ios_plugins folder on the SD.

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

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

  11. (Optional) delete the wafel_install folder to free up space

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

Last edited by SDIO,
TLDR: Hynix console, resurrected with PTB, title installation process never finishes - blue light never stops flashing.

Hi. If anyone can, I need some help with the console I'm currently working on. During the process of reinstalling the MLC & SLC titles, the blue light never stops flashing.

First of all, I'd like to say that in my first few years of repairing consoles, I bought 5 WiiUs because it was a console that I didn't have in my collection, and I really wanted one. At the time, I wasn't able to fix them (I presumed the no videos were problems with the HDMI IC and the HDMI circuit in general tbh). Now, thanks to the work of guys in this community, I've managed to repair three of them using tools like recovery menu, paid the break, NANDAID, isfhax, minute and so on, so I really appreciate the effort that went into helping us resurrect our dead WiiUs. Thanks.

The console that I'm currently working on is the fourth of those five WiiUs. It's a 32gb European WiiU with a Hynix chip (of course).

When I got it, the issue it had was that it froze on the WiiU splash screen. At the time, I didn't know what the issue was, and I actually used it as a little bit of a donor console. I took off the HDMI IC and one capacitor near the CPU. Fast forward a few years, and with my success with the other WiiU consoles, I decided to get back to this one too. I replaced the HDMI IC and the capacitor. I tried reocvery_menu with no luck. I used the PAID THE BREAK exploit to acess minute. The first time I loaded it, there was output on the screen. All subsequent times there was no output, which was a little concerning, seeing as I had replaced the HDMI IC. However, I could tell that the exploit worked because the LED was purple. I blindly navigated the menu and was able to install ISFHAX which then worked fine with video output from then on. Which brings us to now....

I've installed a NANDAID. I believe my work is good and the ERASE MLC option in the backup & restore menu completes with no problems. I downloaded the MLC & SLC titles using the otp.bin from this console, went to install them and it seems the console is not on 5.5.5 (according to the output on the screen), so I went the install IOS_ORIG route. That was the first time that the title install process didn't finish; the LED just kept on blinking blue. After an hour or so (not sure exactly how long I waited), I turned off the console to try again, it seems that the IOS update installed at least because now it recognises that it's on 5.5.5 ["IOS img is prod 5.5.5+"]. However, every time i try to install the fresh titles, the process never finishes. It just keeps on blinking the blue LED. The setup log shows that sometimes it stops after three, five, seven title installs. Where it stops seems a bit random. The last entry is almost always an installinfo entry - which seems like it gets to that point but then doesn't finish installing that title. Sometimes, I'll wait 2 hours, and it only installed 3 titles in all that time.

I've checked the NANDAID's SD card (it's a 64gb High Endurance micro SD card - the same as I've used in two other consoles) with H2 Test, and the card is good, and the SD card in the front slot is the same one that I used with the other consoles too - so that should be fine. Does anyone have any ideas what might be the problem? I've tried only installing the SLC and only installing a few at a time, but the result is always the same (flashing blue LED non.stop). One peculiar thing that I noticed is that even if I put one or two titles on in the wafel_install folder, the blue light won't stop flashing EVEN though the log file shows thati nstalled all of the titles successfully.

I'd really appreciate it if someone could offer me some assistance with this. Thanks



Code:
OpenDir /vol/sdcard/wafel_install: 0
OpenMCP /vol/sdcard/wafel_install: 0
InstallInfo 0005001b1006c000: 00000000
Install 0005001b1006c000: 00000000
InstallInfo 0005001b10042300: 00000000
Install 0005001b10042300: 00000000
InstallInfo 0005001b10042400: 00000000
Install 0005001b10042400: 00000000
InstallInfo 0005001b10050000: 00000000
Install 0005001b10050000: 00000000
InstallInfo 0005001b10051000: 00000000
Install 0005001b10051000: 00000000
InstallInfo 0005001b10052000: 00000000
Install 0005001b10052000: 00000000
InstallInfo 0005001b10053000: 00000000
Install 0005001b10053000: 00000000
InstallInfo 0005001b10054000: 00000000
Install 0005001b10054000: 00000000
InstallInfo 0005001b10056000: 00000000
Install 0005001b10056000: 00000000
InstallInfo 0005001b10057000: 00000000
Code:
OpenDir /vol/sdcard/wafel_install: 0
OpenMCP /vol/sdcard/wafel_install: 0
InstallInfo 0005001b1006c000: 00000000
Install 0005001b1006c000: 00000000
InstallInfo 0005001b10042300: 00000000
Install 0005001b10042300: 00000000
InstallInfo 0005001b10042400: 00000000
Install 0005001b10042400: 00000000
InstallInfo 0005001b10050000: 00000000
Install 0005001b10050000: 00000000
InstallInfo 0005001b10051000: 00000000
Install 0005001b10051000: 00000000
InstallInfo 0005001b10052000: 00000000
Install 0005001b10052000: 00000000
InstallInfo 0005001b10053000: 00000000
Install 0005001b10053000: 00000000
InstallInfo 0005001b10054000: 00000000
Install 0005001b10054000: 00000000
InstallInfo 0005001b10056000: 00000000
Code:
OpenDir /vol/sdcard/wafel_install: 0
OpenMCP /vol/sdcard/wafel_install: 0
InstallInfo 00050010100040ff: 00000000
Install 00050010100040ff: 00000000
InstallInfo 000500101000400a: 00000000
Install 000500101000400a: 00000000
InstallInfo 0005001010004000: 00000000
Install 0005001010004000: 00000000
 
Make sure you have all 3 Wireless modules connected. If that doesn't help try swapping them with the ones from abother console (Especially the 5GHz one)
 
  • Like
Reactions: RadGrav
Thanks for the reply SDIO. I think it may well be a problem with the 5ghz wireless module. That would make sense too. I've got one which is busted for sure (gets hot, must have a short on it). The other spare one I have seems okay, but I get some unexpected resistance readings when it's pluggedi n and the console is on. I'll try with a known working one from another console, and hope that the problem is on the module itself and not on the board. Thanks again.
 
Okay. This is where I am now: I've tested all my modules on a working consoles, and I've discovered which ones work and which ones don't. So, I've eliminated any faulty modules, and I now have three known working wirless modules to work with. I've checked the mb as best I can, and actually everything, as far as I can tell, is normal - comparing it to a working board. Nothing is alarmingly out of spec.

The installation still hangs with a blue flashing light and an interrupted install process. But, I've discovered that I can install three at a time with success. Every title installs that way. Maybe even five at a time (although I didn't want to push my luck). Any more than, say, 5 at a time, and the installation process stalls and never finishes. However, I have to delete the scfm.img and replace the setup plugin each time - to install the next 3, and I'm not sure if that's correct or not. If I don't delete the scfm.img before continuing, the new installation doesn't start - it just gives me a static orange LED. Having said that, even with all the titles seemingly installed (doing what I described: 3 at a time and deleting the scfm each time) , the system still doesn't boot. It will just sit there on a purple LED.

Is there a way to print on the screen or to a txt file which titles are installed on the MLC - or something like that?

I put my SLC dump through nandbincheck, and it seems correct to me :

Code:
** nandBinCheck : Wii nand info tool **
   from giantpune
   built: Mar 24 2017 23:49:06
NAND Type: SLC (WiiU)
checking boot1...
Boot1 hash: "3806d41a5c5f139f5b09bbe5b74a5ec45e0f5507"
Boot1 OK!
checking for lost clusters...
total used clusters 1ee9 of 0x8000
found 0 lost clusters
UNK ( 0xffff ) 1ab (43d, 43e, 43f, 449, 44a, 44b, 44c, 44d, 44e, 44f, 560, 561, 562, 563, 564, 565, 566, 567, dd0, dd1, dd2, dd3, dd4, dd5, dd6, dd7, e88, e89, e8a, e8b, e8c, e8d, e8e, e8f, 19e8, 19e9, 19ea, 19eb, 19ec, 19ed, 19ee, 19ef, 2ca0, 2ca1, 2ca2, 2ca3, 2ca4, 2ca5, 2ca6, 2ca7, 2cb2, 2cb3, 2cb4, 2cb5, 2cb6, 2cb7, 4b08, 4b09, 4b0a, 4b0b, 4b0c, 4b0d, 4b0e, 4b0f, 53e8, 53e9, 53ea, 53eb, 53ec, 53ed, 53ee, 53ef, 5894, 5895, 5896, 5897, 58e2, 58e3, 58e4, 58e5, 58e6, 58e7, 590d, 590e, 590f, 5a50, 5a51, 5a52, 5a53, 5a54, 5a55, 5a56, 5a57, 5b71, 5b72, 5b73, 5b74, 5b75, 5b76, 5b77, 5bda, 5bdb, 5bdc, 5bdd, 5bde, 5bdf, 5ca8, 5ca9, 5caa, 5cab, 5cac, 5cad, 5cae, 5caf, 5cb8, 5cb9, 5cba, 5cbb, 5cbc, 5cbd, 5cbe, 5cbf, 5cd0, 5cd1, 5cd2, 5cd3, 5cd4, 5cd5, 5cd6, 5cd7, 5d00, 5d01, 5d02, 5d03, 5d04, 5d05, 5d06, 5d07, 5dd2, 5dd3, 5dd4, 5dd5, 5dd6, 5dd7, 5e11, 5e12, 5e13, 5e14, 5e15, 5e16, 5e17, 5f48, 5f49, 5f4a, 5f4b, 5f4c, 5f4d, 5f4e, 5f4f, 5f50, 5f51, 5f52, 5f53, 5f54, 5f55, 5f56, 5f57, 5f68, 5f69, 5f6a, 5f6b, 5f6c, 5f6d, 5f6e, 5f6f, 5f70, 5f71, 5f72, 5f73, 5f74, 5f75, 5f76, 5f77, 6188, 6189, 618a, 618b, 618c, 618d, 618e, 618f, 61c0, 61c1, 61c2, 61c3, 61c4, 61c5, 61c6, 61c7, 6350, 6351, 6352, 6353, 6354, 6355, 6356, 6357, 6358, 6359, 635a, 635b, 635c, 635d, 635e, 635f, 63d0, 63d1, 63d2, 63d3, 63d4, 63d5, 63d6, 63d7, 63d8, 63d9, 63da, 63db, 63dc, 63dd, 63de, 63df, 65a8, 65a9, 65aa, 65ab, 65ac, 65ad, 65ae, 65af, 65b0, 65b1, 65b2, 65b3, 65b4, 65b5, 65b6, 65b7, 6628, 6629, 662a, 662b, 662c, 662d, 662e, 662f, 6630, 6631, 6632, 6633, 6634, 6635, 6636, 6637, 67b8, 67b9, 67ba, 67bb, 67bc, 67bd, 67be, 67bf, 6978, 6979, 697a, 697b, 697c, 697d, 697e, 697f, 6990, 6991, 6992, 6993, 6994, 6995, 6996, 6997, 6c28, 6c29, 6c2a, 6c2b, 6c2c, 6c2d, 6c2e, 6c2f, 6c40, 6c41, 6c42, 6c43, 6c44, 6c45, 6c46, 6c47, 6c48, 6c49, 6c4a, 6c4b, 6c4c, 6c4d, 6c4e, 6c4f, 6c58, 6c59, 6c5a, 6c5b, 6c5c, 6c5d, 6c5e, 6c5f, 6c70, 6c71, 6c72, 6c73, 6c74, 6c75, 6c76, 6c77, 6c78, 6c79, 6c7a, 6c7b, 6c7c, 6c7d, 6c7e, 6c7f, 6c80, 6c81, 6c82, 6c83, 6c84, 6c85, 6c86, 6c87, 6c88, 6c89, 6c8a, 6c8b, 6c8c, 6c8d, 6c8e, 6c8f, 6c90, 6c91, 6c92, 6c93, 6c94, 6c95, 6c96, 6c97, 6c98, 6c99, 6c9a, 6c9b, 6c9c, 6c9d, 6c9e, 6c9f, 6cb8, 6cb9, 6cba, 6cbb, 6cbc, 6cbd, 6cbe, 6cbf, 6cc0, 6cc1, 6cc2, 6cc3, 6cc4, 6cc5, 6cc6, 6cc7, 6cc8, 6cc9, 6cca, 6ccb, 6ccc, 6ccd, 6cce, 6ccf, 6cd0, 6cd1, 6cd2, 6cd3, 6cd4, 6cd5, 6cd6, 6cd7, 6d58, 6d59, 6d5a, 6d5b, 6d5c, 6d5d, 6d5e, 6d5f, 6d60, 6d61, 6d62, 6d63, 6d64, 6d65, 6d66, 6d67, 6d68, 6d69, 6d6a, 6d6b, 6d6c, 6d6d, 6d6e, 6d6f, 7934, 7935, 7936, 7937)
free            585c
verifying ecc...
0 out of 644864 pages had incorrect ecc.
they were spread through 0 clusters in 0 blocks:
 ()
0 of those clusters are non-special (they belong to the fs)
verifying hmac...
verifying hmac for 304 files
hmac bad (1)
"scfm.img" is 4004000 bytes ( 1001 ) clusters

00000000  ff000000 00000000 00000000 00000000  ................
00000010  00000000 00000000 00000000 00000000  ................
00000020  00000000 00000000 00000000 00000000  ................
00000030  00000000 00000000 00000000 00000000  ................

00000000  ff000000 00000000 00000000 00000000  ................
00000010  00000000 00000000 00000000 00000000  ................
00000020  00000000 00000000 00000000 00000000  ................
00000030  00000000 00000000 fa08fa08 be0d4102  ..............A.

00000000  c879afc6 aa07b858 cd93a067 91381449  .y.....X...g.8.I
00000010  8d012c60                             ..,`
bad HMAC for "/scfm.img"
1 files had bad HMAC data
checking HMAC for superclusters...
hmac bad (1)
supercluster 7cf0

00000000  ffffffff ffffffff ffffffff ffffffff  ................
00000010  ffffffff ffffffff ffffffff ffffffff  ................
00000020  ffffffff ffffffff ffffffff ffffffff  ................
00000030  ffffffff ffffffff ffffffff ffffffff  ................

00000000  ffffffff ffffffff ffffffff ffffffff  ................
00000010  ffffffff ffffffff ffffffff ffffffff  ................
00000020  ffffffff ffffffff ffffffff ffffffff  ................
00000030  ffffffff ffffffff ffffffff ffffffff  ................

00000000  22343b71 446ac5be 993729c8 a10cb4f1  "4;qDj...7).....
00000010  49cb8c97                             I...
1 superClusters had bad HMAC data
(31984)

Oh, and also, I tried the micro SD card that I'm using in another WiiU, and that finished installing with no isses. So I can rule out the SD card being a problem.

Any ideas as to what I should try next?
 
If you delete the SCFM, then you also need to erase the MLC, else you just end up with a corrupted file system and the last changes lost.
 
Makes sense. I guess I thought that maybe the scfm gets rebuilt or something at the end of the installation process. My bad.

So. I finally managed to get everything installed. The system boots and everything works as it should (I need to test it further, but everything so far worked properly). The wireless modules are all fine, so the installation issues weren't caused by any of them.

I'll leave the process that I used to get all the titles installed here, in case it helps someone with a continuously flashing blue LED in the future. I found that I could only install a few titles at a time. Sometimes 3, sometimes 5, sometimes 7 etc. At first, I tried to get all the titles installed by only putting a few titles at a time in the folder. However, if the install process successully completes (ie. if I only put three titles in the wafel_install folder, and all three of them install successfully) then I cannot install any more titles after that point. Trying just gave me an orange LED failure. I think the reason is because of this : SetInitialLaunch 0: 1. At the end of a successful installation process -regadless of how many titles were installed- the plugin tells the console to prepare itself to be turned on for "the first time". I might be totally wrong about this, but I suspect that you can't install any titles with that mode activated - even if you replace the setup plugin in the ios_plugins folder. Or maybe it was just in my case, I don't know. My solution was to start by erasing the MLC and scfm, and then just put all of the titles in the wafel_install folder, start the process, wait around 10-20 minutes for it to get as far as it could, power off the console, check the log file to see which titles successfully installed, delete those titles from the folder, and restart the process until all titles are installed (only deleting the mlc and scfm the very first time). The last entry in the log file after an incomplete install will be an installinfo entry for a title - that's where the process hung. That title still needs to be installed, so don't delete that one. Only the ones before it which say 'installed' after them.

(of course, if you have this issue, the first step should be checking that the three wireless modules are connected properly and working)

That's what worked for me. No idea why the install didn't ever complete in one swoop on this console.
 
If you delete the SCFM, then you also need to erase the MLC, else you just end up with a corrupted file system and the last changes lost.
I didn't bother erasing the scfm for this reason, thanks to your efforts, parts of the emmc can simply be blocked from being accessed; and the mlc routed to a any other destination of choice.
Very handy!
 
My Kingston 64GB ndurance Card is not formatted to 64GB but 32GB. Did I miss a discussion on that? With wafel_unlimit it of course works fine. But I wanted a somewhat vanilla system. Does that meen it does not have "really" 64GB but a bit less?
 
Last edited by classiphil,
Then your card probably isn't making it over the threshold of 60948480 sectors to be considered a 64gb card by IOSU, making it fall back to 32gb.
That could also be an indication that this isn't the best card, as they likely hat to allocate more blocks for spares or factory bad blocks
 
wrong thread
Could USBMLC be configured to allow booting from port 1 instead of port 0? I want to save the top usb slot for vWii drive and hub for their accessories.

I'll mess with the code myself if you're not feeling it, as always I am grateful to your constant innovation in the Wii U space.
 

Site & Scene News

Popular threads in this forum