Hacking Possible to Repair Wii U System Memory Error Code 160-0103?

LED2000 · Mar 31, 2023

Hello, so since this has got bumped again:

Last week i booted up my Wii U to grab a few things from the eshop and unfortunately it also shows the 160-0103 Error...
Although the console boots up just fine, it always crashes on specific occasions.
It seems to primarily have a problem with some text input boxes. Because when i was in the eshop everything worked but as soon i clicked on the search bar - it crashed. And i actually bought a few games so on the next day i wanted to play Xenoblade X. And as soon i got th the Name input screen, it crashed again. Also the internet browser and parental controls don't work, but at least most other things do, like the system Settings.
I wondered if reformatting would help, but since i read that it could actually completely brick it, i didn't do it. Also there is still data that i want to preserve, and there is another user profile on it which i don't want to delete if possible.

So i would like to backup the NAND at least but i don't know how.

Yesterday i finally got my Pico and tried to use the recovery menu with UDPIH. And it turned out i actually have a hynix chip, although my console is from 2015. Because actually i had this error before in 2018 when it was completely bricked i think, and since it still had warranty it just got replaced, but now i got this problem again...

SDIO · Mar 31, 2023

Download the nandDumper Payload from https://github.com/wiiu-env/wiiu-nanddumper-payload/releases/tag/v0.1 and extract it to the SD card. There should then be a folder named "wiiu" on the SD card with the payload.elf inside. Safely eject the SD card and insert it into the Wii U. Then, in the Wii U browser, go to wiiuexploit.xyz and click on "Exploit". The nanddumper should start. Here, make sure that everything is set to "yes" (including the mlc, which is set to "no" by default) and start the dump with A.

You will need a 64GB FAT32 formatted SD card for that.
A board to replace the eMMC is currently in development: https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/post-10115383

You might want to not use your Wii U till you replaced the bad eMMC. If it dies or corrupts to badly you might also need to flash the SLC.

LED2000 · Mar 31, 2023

SDIO said:
Download the nandDumper Payload from [forbidden URL] and extract it to the SD card. There should then be a folder named "wiiu" on the SD card with the payload.elf inside. Safely eject the SD card and insert it into the Wii U. Then, in the Wii U browser, go to wiiuexploit.xyz and click on "Exploit". The nanddumper should start. Here, make sure that everything is set to "yes" (including the mlc, which is set to "no" by default) and start the dump with A.

Well the Problem is: As i said, the internet browser doesn't work... It crashes as soon as i open it...

SDIO · Mar 31, 2023

Oh sorry. I will send you later a recovery menu, which can do the dump. if I forget it please remind me tomorrow or so.

And don't do the factory reset.

LED2000 · Mar 31, 2023

SDIO said:
Oh sorry. I will send you later a recovery menu, which can do the dump. if I forget it please remind me tomorrow or so.

And don't do the factory reset.

Ok thank you, that'd be very nice. Although i then still need to do something, but then at least i'd have a backup.

So in worst case i'd actually have to open up the console and somehow try to replace the chip, but that will not happen soon at least...

Also i just tried looking at the syslogs that were copied using the recovery-menu but what is the structure of the naming? Because when i open 1.log it's one from 2 days ago, then inbetween i have some old ones from 2018 and then the ones at 98 and 99 are again from 2 days ago.

Or does nintendo actually still do repairs/replacements? Because somone I've read that they still have support but most say they don't

SDIO · Mar 31, 2023

There is a meta.bin, it saves the number of logs in binary. Because it wraps around at 100, you have to use modulo 100 of that (the last two places in decimal)
In the logs you want to watch out for MEDIA ERROR and DATA CORRUPTION concerning the mlc (not odd)

LED2000 · Mar 31, 2023

SDIO said:
There is a meta.bin, it saves the number of logs in binary. Because it wraps around at 100, you have to use modulo 100 of that (the last two places in decimal)
In the logs you want to watch out for MEDIA ERROR and DATA CORRUPTION concerning the mlc (not odd)

Yes i've found one although it's from 2 days ago:

00:04:56:873: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:04:56:874: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, pathnull)
00:04:56:886: mmc_core card err: idx=3, lba=55709952, blks=128, xfer=0x1, ret=0x00200b40
00:04:56:904: mmc_core card err: idx=3, lba=55709952, blks=128, xfer=0x1, ret=0x00200b40
00:04:56:904: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:04:56:904: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, pathnull)
00;04;56;785: FS: READ_FILE upid:[15] sts:[MEDIA_ERROR] hnd:[0x3960b9f] dst:[0x1a5bb780] size:[1] cnt:[9844] pos:[0]
00;04;56;785: SystemFatal(core0)

and

<><><><><><><> fatal error process called <><><><><><><>
00;04;57;626: TYPE: Corruption(2)
00;04;57;626: CODE: 1600103
00;04;57;626: Process: 15
00;04;57;626: Internal Code: 269274536
00;04;57;626: Function __FSCheckAndSwitchErrorProc, Line:107

And i actually even found an error from 2021. So the error already occured there an i remember that i had some error already back then, but i used the console pretty rarely and then forgot about it.

V10lator · Apr 1, 2023

@LED2000 Sorry to say but this is indeed a damaged NAND. Please use the attached build from @SDIO to first dump OTP and SEEPROM, then dump SLC + MLC. After that turn the console off and do not turn it on again untill you replaced the eMMC chip inside the console.

Have a look at
https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/ about how to replace the hardware damaged eMMC chip with an SD card with basic soldering skills (no need to solder out the eMMC chip). Also note that @Voultar is currently designing a QSP to make this even more simple, see https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/post-10115383

LED2000 · Apr 1, 2023

V10lator said:
@LED2000 Sorry to say but this is indeed a damaged NAND. Please use the attached build from @SDIO to first dump OTP and SEEPROM, then dump SLC + MLC. After that turn the console off and do not turn it on again untill you replaced the eMMC chip inside the console.

Have a look at
XXXXXXX about how to replace the hardware damaged eMMC chip with an SD card with basic soldering skills (no need to solder out the eMMC chip). Also note that @Voultar is currently designing a QSP to make this even more simple, see XXXXXX

Thank you very much.
But how do i get a 64GB SD formatted with FAT32? Windows can only format FAT32 up to 32GB...

SDIO · Apr 1, 2023

there is a tool called gui format: http://ridgecrop.co.uk/index.htm?guiformat.htm

LED2000 · Apr 1, 2023

SDIO said:
there is a tool called gui format: http://ridgecrop.co.uk/index.htm?guiformat.htm

Nevermind i've already done it with linux now, but thanks anyways,

But i have another problem: I got some error while unmounting the MLC. Now the SLC is dumping but there ere a lot of errors occuring. When it's over i will try if i can get to dump the MLC again maybe.

SDIO · Apr 1, 2023

just wait a few minutes before starting the dump. I have to change it to retry if it fails the first time, but I didn't have the time for that.

LED2000 · Apr 1, 2023

SDIO said:
just wait a few minutes before starting the dump. I have to change it to retry if it fails the first time, but I didn't have the time for that.

Actually it seems like it did that by itself, after the SLC Dump was complete it dumped the MLC again. So of course there were a lot of errors now. Also there were errors with the SLC, should i be concerned about that?

So now what can i do with the Dump before i can eventually write it on a new NAND someday in the Future? Ist this Image now still encrypted?

Also i tried copying the system logs again but somehow i always got an error in this recovery menu that it couldn't open the folder.

Post automatically merged: Apr 1, 2023

Ok so now i've tried extracting the contents from the dump and yes, seems like a lot of files are corrupted... So now where can i get a replacements to replace the corrupt system files? Do i now need another Wii U where i can extract them or is it possible to download them somewhere?

SDIO · Apr 1, 2023

don't worry about the SLC errors, they are a problem of the dumper.
But the MLC errors are true and expected after seeing the errors in the logs.

You can get replacements from NUS. Buf before attempting a repair, you should first replace the eMMC or you will just be playing whack a mole till the eMMC completely dies.

EDIT: if you would need to restore the dump, you would need to flash both, SLC and MLC and SLC flashing is a lot more complicated so bet to avoid that. Besides that you shouldn't trust this dump to be able to restore the console. It is still work in progress and has problems with the SLC. Also when you did the dump, the MLC was still mounted, so the mlc dump could be inconsitent

LED2000 · Apr 1, 2023

SDIO said:
don't worry about the SLC errors, they are a problem of the dumper.
But the MLC errors are true and expected after seeing the errors in the logs.

You can get replacements from NUS. Buf before attempting a repair, you should first replace the eMMC or you will just be playing whack a mole till the eMMC completely dies.

EDIT: if you would need to restore the dump, you would need to flash both, SLC and MLC and SLC flashing is a lot more complicated so bet to avoid that. Besides that you shouldn't trust this dump to be able to restore the console. It is still work in progress and has problems with the SLC. Also when you did the dump, the MLC was still mounted, so the mlc dump could be inconsitent

Ok thanks. If possible i just wanted to have the replacement files already downloaded so how can i get them from NUS? Also i thoguht that i can write them into the image file or should i first write back the original NAND Dump to the new one when i replaced it? And how can i then replace the broken files?

Also you said that i'd need to flash the SLC, but i can avoid it somehow, so what do you mean, what do i have to do so i don't have to flash the SLC?

Sorry for the inconveniences...

SDIO · Apr 1, 2023

The Wii U has two chips for persistent storage. The MLC, which contains most of your data and parts of the OS and the SLC, which has the Bootloader and IOSU and other Firmware stuff. The logical MLC is physically the eMMC chip.
As the SLC holds a cache for the MLC the state of both is linked. So if you restore one, you have to restore the other.
If you replace the eMMC before it is to late, we can get the current state of the eMMC and transfer it to the SD or a new eMMC. Meaning you then don't have to restore the SLC as we transfered the matching state of the MLC.

You can get the replacement files with JNUS Tool from the Nintendo Servers, but I think you need to use the command line to specify the title id of the broken titles. You get the titleid from the path. But we worry about that after the Hardware side is fixed.
We will get them on your console trough the recovery menu. It is possible to inject files in the mlc image, but I wouldn't recommend that, as it bypasses the SLC cache.

LED2000 · Apr 1, 2023

SDIO said:
The Wii U has two chips for persistent storage. The MLC, which contains most of your data and parts of the OS and the SLC, which has the Bootloader and IOSU and other Firmware stuff. The logical MLC is physically the eMMC chip.
As the SLC holds a cache for the MLC the state of both is linked. So if you restore one, you have to restore the other.
If you replace the eMMC before it is to late, we can get the current state of the eMMC and transfer it to the SD or a new eMMC. Meaning you then don't have to restore the SLC as we transfered the matching state of the MLC.

You can get the replacement files with JNUS Tool from the Nintendo Servers, but I think you need to use the command line to specify the title id of the broken titles. You get the titleid from the path. But we worry about that after the Hardware side is fixed.
We will get them on your console trough the recovery menu. It is possible to inject files in the mlc image, but I wouldn't recommend that, as it bypasses the SLC cache.

Oh ok.

Yes i already looked through the title IDs and a lot of titles are affected, for example the Internet browser and "Software Keyboard Applet", which would explain the crashes on text input boxes. Also a few other things are corrupted like the Karaoke and also Files from Mario Kart and Super Smash Bros. So it looks like all affected titles are some that have been installed a long time ago, when i just got the console. With the titles that i just installed last week when i didn't really knew that my memory has a defect, it seems that they are fine. (Although i've copied them to USB afterwards so they don't have to be on the emmc anymore but now i don't want to change anything on it until it's fixed).

But the first thing is, i've already contacted the nintendo support, i don't think they do repairs anymore but i've wanted to try it before i try to screw with it, so if they say that they really don't to it anymore then i'm gonna repair it myself.

So ideally, of course i would want to replace the eMMC with a new one but i assume that this will be probably impossible with BGA to do by myself... So do you think i should just solder an SD into there or is there some way to do a 1:1 Chip replacement?

SDIO · Apr 1, 2023

If you don't feel comfortable with BGA rework juste go with an SD. Zhe limiting factor for performance is anyway the SDIO of the Wii U, which tops out at 25MB/s. Todays SD cards can easily achieve that, but don't go for the cheapest one. You don't want one that fails after a few hours and also write speed and random IO performance can vary.
There are also adapters where you can solder an eMMC to and put them into a SD slot, but they are quite expensive at 10€ a piece and then you also need an eMMC which is also more expensive than a SD.

LED2000 · Apr 1, 2023

SDIO said:
If you don't feel comfortable with BGA rework juste go with an SD. Zhe limiting factor for performance is anyway the SDIO of the Wii U, which tops out at 25MB/s. Todays SD cards can easily achieve that, but don't go for the cheapest one. You don't want one that fails after a few hours and also write speed and random IO performance can vary.
There are also adapters where you can solder an eMMC to and put them into a SD slot, but they are quite expensive at 10€ a piece and then you also need an eMMC which is also more expensive than a SD.

Hmm well i mean i could try it but i've never done something with BGA before (except maybe desoldering some Chips from old Motherboards with a hot air gun xD) but then i'd need the equipment for it. I mean, as long as it doesnt costs hundreds of Euros and if you say it's possible i could try it. But i don't know, if you say it's complicated and maybe there's danger that i'd might damage other components then it's probably not worth it.
But if possible i would at least like to remove the old chip so it isn't connected to the System anymore in any way
10€ a piece would be no Problem actually, i'd have maybe to look for something like that.

And of course i wouldn't take the cheapest SD Card, my choice would probably be a SanDisk Extreme Pro which is definitely faster than 25MB/s and it only costs around 10€.

SDIO · Apr 1, 2023

I wouldn't risk it. You also have components on the other side of the board, which could fall of and a new eMMC isn't as cheap as an SD either. Maybe it even has under fill and then it could get really nasty.
You can leave the old eMMC in the system, if the clk signal is capped an ideally grounded on the eMMC side the eMMC won't do anything. You could also remove the 4 resistors if you don't want to cut the clk trace, then the eMMC would be seperated from all the data signal lines.

Hacking Possible to Repair Wii U System Memory Error Code 160-0103?

Active Member

Well-Known Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Attachments

Active Member

Well-Known Member

Active Member

Attachments

Well-Known Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Similar threads

Popular threads in this forum