Tutorial  Updated

Fixing system memory error 160-0103 (failing eMMC) without soldering | using redNAND with ISFShax

What is this for?



If you are encountering Error Code 160-0103 "There is a Problem with the system memory" or your Wii U is freezing at bootup or during Factory Reset it is likely that the eMMC Chip is failing.
This tutorial goes into fixing this Error 160-0103, by using the SD card in the front slot as replacement for the failing eMMC.
In this tutorial we will rebuild the MLC, which means it is empty, whithout your data. In the end I show how to salvage savegames from the failing eMMC.

Please note there are other possible causes for the 160-0103 error (like a CBHC brick). Also there are other possible solutions to this problem. To see if this Tutorial is right for you, check out the Ultimate Wii U Troubleshooting Guide

1690709917882.png


What this will do


We will first install ISFShax, which is an early exploit that runs before the operating system loads. This allows us to patch the OS to redirects the reads and writes, that normally go to the eMMC, to a partition on the SD card. So you will need to have the SD card in the Wii U to use it, as that is now it's new internal memory.
Also you need to keep the standby servcies (and with that the Quickstart menu) disabled as they don't work with ISFShax. (Your Wii U will hang once you turn it off till you remove power if standby services are enabled).
In this tutorial we are only redirecting the MLC. If you plan to try some dangerous things in the future, you can still mess up your system SLC and SLCCMPT. If you want to use this for such experiments consider using full redNAND, where all 3 devices get redirected.

Update


28.01.2024 - Wii VC games (from he eShop or VC Injects) now works from the redNAND internal memory. Keep in mind that Wii VC is more picky about the SD card. So far Sandisk cards worked for me, but Samsung cards didn't. If the card is incompatible, it will hang on a black screen after the silver Wii logo.

Choosing an SD card


I highly recommend to use an SD card, which is designed to sustain lots of writes, like Sandisk Max Endurance or at least High Endurance or Samsung Endurance. The absolute minimum size is 8GB using, 1,5GB for the FAT32 partition and the rest for the MLC partition, but it is recommend for the the card should have at least 16GB, so you can have at least 8GB for the MLC partition. The Maximum size of SD you can use is 2TB.

Since the Wii U Discs suffering from Disc rot and also for convenience, you probably want to dump all your Game Discs and install the Games from these Dumps You find detailed instructions on how to do that here: https://wiiu.hacks.guide/#/dump-games (do it after you completed this guide)
Later in that guidel you will create a second partition, which replaces the Internal Memory. You won't be able to resize that partition, without rebuilding again, so you better size everythng properly the first time.
The first partition is where all the Homebrew goes to and also where the dumps of the Wii U games go to. So this partition needs to have at least enough space to store your largest Wii U game with some extra space. If you want to use a USB Loader with vWii, you can also store the (OG) Wii games on the FAT32 partition.
The second partition (the MLC partition, which you format initally with NTFS) is where you install all your Wii U games (eShop and dumped Disc games, updates, DLC, saves...) to, including the VC Injectes. Also 5GB are used up by the Wii U system.
Make sure the the SD card can fi both these partitions.

Installing ISFShax


For installing ISFShax follow this tutorial: https://gbatemp.net/threads/how-to-set-up-isfshax.642258 but skip the "Autoboot" part for now.

Optional: Backing up savegames


If your Wii U can still run Tiramisu or Aroma: https://wiiu.hacks.guide/#/ you can use SaveMii to back up your save games.
If it can't you then you probably already used UDPIH to install ISFShax. Launch the recovery again using UDPIH and then use the Dump SLC + MLC option. Your SD card needs to have at least 64GB for that (for a 32GB console). You then need to merge mlc.bin.part files in the right order and can then extract the savegames using wfs-extract.

You can also backup your saves after setting up redNAND, even if your old system isn't booting anymore, see this post for more details: https://gbatemp.net/threads/fixing-...ing-rednand-with-isfshax.642268/post-10417998

If you lost the password to your NNID and can't recover it because the email doesn't exist anymore, you can transfer it. This is only a last resort option. If you still have the email address, it would be better to use the "Forgot Password" option now, as you won't have it on the new system.
There is also the option to use a password reset option on the PC. For that you need to create a Nintendo Account and then link the NNID to it. When linking it will ask for the password and give a reset option using the email.

Keep in mind this transfer only works on the same console and only if you don't do a Factory Reset.
To transfer the NNID It's enough to copy the account.dat file over.
You can use ftpiiu everywhere to save it to the PC for now. Just copy the whole /storage_mlc/usr/save/system/act/ folder to the PC. In that folder you find one subfolder for each user and in that subfolder you find an account.dat (it's a plain text file, you can open it with notepad). The folders are numbered in the order the users were created.

On the new rebuild mlc the numbering will start again with 80000001. If the user with the NNID had a larger number just create new users on the new system until you reach that number. Then you can copy the account.dat back and reboot.
After that you should be able to access the eShop and download the games again.


Partitioning the SD card


On Windows you need to use a third party tool like Minitool Partition Wizard or easeus, on Linux you can use gparted.
You need to have two primary partitions on the card:
  1. FAT32 - (in gparted set lba flag). This is what the PC will see and all your homebrew goes
  2. NTFS - This partition will be the MLC replacement, it should have at least 8GB. (don't assign a drive letter)
Shrink the existing FAT32 partition to make room and then create the NTFS partition after it. It's recommended to align the Partitions on 64MiB boundaries and use a multiple of 64MiB for the size. The MLC (NTFS) partition should be at least 8GB but other than that you can choose whatever sizes you like.

Configuring redNAND


Create a file minute/rednand.ini on the sdcard with the following content:
INI:
[partitions]
slccmpt=false
slc=false
mlc=true

[scfm]
disable=true
allow_sys=false

Rebuilding the MLC


  1. Download all the mlc system titles for your region from NUS. This can be done conveniently with MLCRestorerDownloader by @Xpl0itU. To use the MLCRestoreDownloader, you need to extract it and then copy the otp.bin from the SD card to it's directory. Then start the Downloader and select mlc and then your consoles region.
    You will get the output/MLC/{region} directory, which contains a directory for each title. In total there should be 52 titles totaling ~1.1GiB.
    If your console has an older firmware it might also be necessary to get the latest SLC titles.

  2. On the root of your SD card 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. Put the wafel_setup_mlc.ipx on the SD card in /wiiu/ios_plugins.

  4. Select Patch (sd) and Boot ios redNAND 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 inital setup on the next boot.

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

  6. Select Patch (sd) and Boot ios redNAND again. If everything worked, the initial setup should launch.

  7. Follow through with the initial setup. After the "settings" part of the setup, it will drop you back into minute, just select Patch (sd) and Boot redNAND again. (no longer required with latest minute)
  8. (Optional) delete the wafel_install folder to free up space

Setting up autoboot


To automatically boot into redNAND create the file sd:/minute/minute.ini with the following content:
INI:
[boot]
autoboot=2
autoboot_timeout=1

Installing minute to SLC


If you haven't already installed minute (fw.img) to the SLC, you should do that now so In case the SD get's lost the Wii U displays at least the minute menu. Follow the "Booting without SD" section from the ISFShax tutorial for that. You only need to install the fw.img and can skip the ios_plugins part as you probably don't want to to boot the eMMC anyway.


Credits


  • smealum and WulfyStylez for redNAND
  • @shinyquagsire23 for minute, stroopwafel
  • @rw-r-r_0644 for finding and implementing isfshax
  • @GaryOderNichts and @QuarkTheAwesome for their direct contributions and help to the mlc setup
  • @V10lator for implementing Quota support and some improvements
  • @Xpl0itU for MLCRestorerDownloader
  • @vgmoose for all the support and for the Wii U that replaced the one Idestroyed during early isfshax testing
  • @Maschell for his help and all other contributions to the Wii U scene
  • @Lazr1026 for testing and some fixes
  • hexkyz for the warmboot boot1 exploit which made all of this possible
  • Salt Team for the original minute CFW
  • dimok789, FIX94 and others for the iosuhax CFW
  • fail0verflow for mini
  • and all other contributors to the Wii U scene!
 
Last edited by SDIO,

Mr_Marr

Active Member
Newcomer
Joined
Oct 5, 2024
Messages
34
Trophies
0
Age
33
XP
46
Country
United Kingdom
The files inside are not important at all. I've been trying to fix it for a month with many methods. I've tried everything. I even replaced the HDMI chip because I couldn't get a picture. I was very impatient. I even broke my disk drive in the process. :D

I followed the steps below.

* Downloaded the MLC and SLC files using MLCRestorerDownloader (EUR)
* I installed the MLC and SLC files into the "wafel_install" folder on the SD card.
* I installed the "wafel_setup_mlc.ipx" file in the "/wiiu/ios_plugins" folder on the SD card.
* I booted my WiiU using "re_fuse".
* Backup and Restore -> Delete scfm.img
* "Backup and Restore" -> "Delete MLC
* "Patch (sd) and boot IOS (slc)"
* I turned off the device when the blue light stopped blinking.
* I deleted the file "wafel_setup_mlc.ipx" in the folder "/wiiu/ios_plugins" on the SD card.
* I restarted my WiiU using "re_fuse".
* "Patch (sd) and boot IOS (slc)".

And I loop back to where I started. The HDMI minute_minute stays at "Go Go Go". The log file resumes writing. No AV picture. But the good thing is that I can now get into the recovery menu. I think it's the de_Fuse method. I paired the tablet in the recovery menu, but it gave me an error that it couldn't connect to the wiiu.

What else can I try? I have attached the log files.
How did you get into recovery through minute?
 

Mr_Marr

Active Member
Newcomer
Joined
Oct 5, 2024
Messages
34
Trophies
0
Age
33
XP
46
Country
United Kingdom
After the de_fuse method, after entering the "Patch (sd) and boot IOS (slc)" menu, "go go go" appears at the end. After that I wait 10 seconds and insert the usb. Recovery menu comes up.

I will try this as soon as I get home. I didn't realise you could do that, thank you.
 
  • Like
Reactions: multimesut

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
2,996
Trophies
2
Age
29
XP
2,309
Country
Germany
Hm try disabeling the Disc drive in the SEEPROM (you can do that in the Backup and Restor esubmenu of minute). A missing Disc drive shouldn't cause this, but on the serial console we can see it constantly complaining about it. At least the log won't be spammed with that message so we might see the real problem better.

Also make sure to not have the UDPIH pico connected when you try to boot manually.
 

Mr_Marr

Active Member
Newcomer
Joined
Oct 5, 2024
Messages
34
Trophies
0
Age
33
XP
46
Country
United Kingdom
Will 30 gauge wire be okay for the nand aid? It is all I have right now.
Post automatically merged:

Will 30 gauge wire be okay for the nand aid? It is all I have right now.

I got a new wii u. I can get it into recovery but isfshax will not install. The wii u will shut down with blinking blue light. Does this mean I need to defuse?
 
Last edited by Mr_Marr,

Mr_Marr

Active Member
Newcomer
Joined
Oct 5, 2024
Messages
34
Trophies
0
Age
33
XP
46
Country
United Kingdom
probably.

and when do you get the blinking blue light?
The blinking blue is on a different wii u. When I try to install isfshax from the recovery menu, the wii u will shut off with a blue blinking light. I have tried multiple fw.img but nothing changes.
The original issue was that the wii u was stuck trying to delete content.
 

SDIO

Well-Known Member
OP
Member
Joined
Feb 13, 2023
Messages
2,996
Trophies
2
Age
29
XP
2,309
Country
Germany
you need the non encrypted fw.img and the boot1.img on the SD. But it seems like PRSHhax isn't working for some reason. You can use the recovery to set Inital bot to 0. That might get you far enough to use a different exploit like DNSpresso during the Network setup part.
 

multimesut

Member
Newcomer
Joined
Aug 16, 2024
Messages
18
Trophies
0
Age
37
XP
72
Country
Turkey
Hm try disabeling the Disc drive in the SEEPROM (you can do that in the Backup and Restor esubmenu of minute). A missing Disc drive shouldn't cause this, but on the serial console we can see it constantly complaining about it. At least the log won't be spammed with that message so we might see the real problem better.

Also make sure to not have the UDPIH pico connected when you try to boot manually.
1729003139655.png


I set it up as you said. Again, no result. I'm about to give up :) I need to at least see a Wii logo. I think it might be a bad GPU. The fact that I can't get an image on AV makes me think. I think the NAND is bad because it gives a lot of errors during backup. But the Rednand doesn't work either. I can't see anything in the error logs, do you see anything? Or if you have any ideas that we can try one last time, I'd really appreciate it. I don't want to throw my Wiiu away.
 

Attachments

  • putty.txt
    55.5 KB · Views: 6
  • logs.zip
    734.4 KB · Views: 7
Last edited by multimesut,

Guettto

New Member
Newbie
Joined
Oct 28, 2024
Messages
3
Trophies
0
Age
26
XP
7
Country
Canada
Hello I’m completely new to this i’ve never modify a console but recently i had this error message on my wii u. I follow this tutorial and thought i did pretty good but in the end when i try to patch sd and boot ios rednand i have a long text appearing with the end message “jumping to ios… go go go” and nothing happening. If someone could help me i would be forever grateful :)
 

Attachments

  • IMG_0091.jpeg
    4.4 MB · Views: 3

Data2405

New Member
Newbie
Joined
Oct 28, 2024
Messages
1
Trophies
0
Age
36
XP
14
Country
United States
Thanks for the tutorial! It brought my wii u back to life. Now I'm wondering if is possible to mod the wii u further with homebrew and stuff (my wii u was never modded before this fix). I'm just afraid to follow any tutorial and also break what I currently have.
 

Guettto

New Member
Newbie
Joined
Oct 28, 2024
Messages
3
Trophies
0
Age
26
XP
7
Country
Canada
I had this message in a previous try but it looks like i fix it but i still see sdmc:/redotp.bin… NOT FOUND!
Hello I’m completely new to this i’ve never modify a console but recently i had this error message on my wii u. I follow this tutorial and thought i did pretty good but in the end when i try to patch sd and boot ios rednand i have a long text appearing with the end message “jumping to ios… go go go” and nothing happening. If someone could help me i would be forever grateful :)
 

Attachments

  • IMG_0090.jpeg
    2.7 MB · Views: 5

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • SylverReZ @ SylverReZ:
    @realtimesave, It isn't really the same as it was. I think that the games that are coming out result in a buggy mess and it doesn't seem to appeal well to a wider audience. If you look at games from over a decade ago, you will notice how better they are, like GTA V for example.
  • realtimesave @ realtimesave:
    I used to play 007 and cod4 a lot
  • realtimesave @ realtimesave:
    and test drive unlimited
  • BigOnYa @ BigOnYa:
    Pretty much all the games that come out buggy get patched soon after anyways. Not to many that I've noticed are game breaking bugs. Of course I mostly only game on Xbox seriesx.
  • kijetesantakalu042 @ kijetesantakalu042:
    @BigOnYa It's still unacceptable
  • realtimesave @ realtimesave:
    I wonder if anyone actually uses a PS5 these days
  • BigOnYa @ BigOnYa:
    Game updates are a norm today, deal with it. They only make games better. GTAV gets weekly updates still today.
  • realtimesave @ realtimesave:
    mine just sits
  • kijetesantakalu042 @ kijetesantakalu042:
    @BigOnYa Game updates are a good thing. But shouldn
  • kijetesantakalu042 @ kijetesantakalu042:
    be a crutch for releasing a working game
  • BigOnYa @ BigOnYa:
    I have not played a game in years that had a game breaking bug on launch, so I wouldn't say a crutch.
  • kijetesantakalu042 @ kijetesantakalu042:
    Scarlet and voilet
  • BigOnYa @ BigOnYa:
    Maybe different on PC, who knows, since I'm in the Xbox ecosystem.
  • kijetesantakalu042 @ kijetesantakalu042:
    Fallout 76
  • kijetesantakalu042 @ kijetesantakalu042:
    No mans sky
  • BigOnYa @ BigOnYa:
    Yep, been playing fallout76 for years, since launch, I never had any game breaking bugs, or corrupted saves. Don't play No Mans Sky, its boring.
  • kijetesantakalu042 @ kijetesantakalu042:
    At launch there were some issues
  • BigOnYa @ BigOnYa:
    Issues? All games have issues, but not game breaking.
  • BigOnYa @ BigOnYa:
    Again don't play on PC, nor would play that. And who knows, some those "issues" could just be your PC.
  • realtimesave @ realtimesave:
    usually issues are a shitty PC
    +1
  • realtimesave @ realtimesave:
    I haven't had a crappy pc in years and when I did, I promptly got rid of it
  • kijetesantakalu042 @ kijetesantakalu042:
    KSP 2 did suck and the entire staff team got laid off
    kijetesantakalu042 @ kijetesantakalu042: KSP 2 did suck and the entire staff team got laid off