Hardware How I fixed 160-0103 system memory error

Sidoudou · Mar 21, 2023

V10lator said:
Nope, they updated to Tiramisu and you should, too. See, you can't stay on old, outdated technology and at the same time complain that new, modern things won't work on your setup. That's somehow like asking why you can't play GTA 5 on your old Pentium II Windows 98 PC.

Alright, where did that come from??? When did you hear me complain? I'm well aware of all what Tiramisu brings (and its caveats). I'm really happy with Haxchi that serves perfectly my use case while Tiramisu does not (cf. the numerous homebrew apps that I use). There is no extra benefit -for my use case- in moving to Tiramisu. There's no "should" in this situation. The only "should", should it exist, is you should assess things for what they really are and you should respect others' choices in using a "different" (not outdated) technology that proved its stability and still compatible with loads of things versus another technology that has yet to propose a full alternative to the previous one. It's like buying the new new iPhone 200 extra pro large ++ that comes without SD card slot, without jack, without charger, then without loudspeakers, without battery and without screen just to go with the time. I'm barely exagerating the trend here. Come on, show some manners young thing! How old are you anyway?

rcpd said:
Update to Tiramisu. It is not difficult. I just did it last week. Bonus: you get your DS game back and it’s playable after reinstalling it from the eShop.

Dr Kawachima Brain age ? not a great loss. I have it on actual DS anyway

IngeniousDefault said:
I temporarily ran Tiramisu via the browser exploit to get it to work. No need for me to switch entirely. After all I only use it for save file backups.

That's what I'm talking about. I'll try that. Thanks a lot!

V10lator · Mar 21, 2023

Sidoudou said:
cf. the numerous homebrew apps that I use

Which one isn't compatible with Tiramisu?

Sidoudou said:
a "different" (not outdated) technology

Sorry to say but software which didn't see a bugfix since 6 years, which has been abandoned by its developer and which is known to be builded upon old, buggy dependencies is old.
Also with having a better alternative which is completely compatible with all the software out there (Tiramisu. Again: Name a single homebrew not running on Tiramisu) it is outdated, too.

//EDIT: See, I don't want to disrespect you or anything, I just say you're like still running Windows 98 while anyone else uses Windows 11 these days and I wonder why you do this while at the same time you ask how to run mdinfo on that.

martindrengen · Mar 21, 2023

Just in case it helps narrow down the bad chips, here is the mdinfo from my console.

PAL WIi U Premium - bought 1 or 2 months after launch, but I'm pretty sure it was from the very first batch of console the store got.
Samsung eMMC. No errors or retrys. Have done 2 complete backups one week apart. In between I tried filling up the NAND storage, apps, games and updates worked fine, and then I moved it off to USB again. No errors.

My console hasn't been connected to power when it wasn't used. At one point there was almost two years between powering it on IIRC

.

Voultar · Mar 21, 2023

OK. The software side is going to have to catch up, but I'm in the process of designing hardware that's going to make replacing the eMMC much, much, MUCH easier.

I'm also considering designing a break-out QSB that makes soldering to the SLC much easier to dump if you can't do it in software (because of a bad MLC).

Would anyone like to try these once finished and test?

wavebeam · Mar 21, 2023

Voultar said:
OK. The software side is going to have to catch up, but I'm in the process of designing hardware that's going to make replacing the eMMC much, much, MUCH easier.

I'm also considering designing a break-out QSB that makes soldering to the SLC much easier to dump if you can't do it in software (because of a bad MLC).

Would anyone like to try these once finished and test?

wow, what timing. I've been wondering about this just now. I've got a functional wii u right now with a hynix chip and a dumped NAND. I'd love to help out testing a QSB to replace the NAND with an SD card or something so i can keep it working for years to come.

edit: FWIW, i'm not a dev and can't give you much more constructive info other than how easy it is to install for someone with moderate modding skills. if other folks would better serve the effort, please work with them first!

rcpd · Mar 21, 2023

Voultar said:
OK. The software side is going to have to catch up, but I'm in the process of designing hardware that's going to make replacing the eMMC much, much, MUCH easier.

I'm also considering designing a break-out QSB that makes soldering to the SLC much easier to dump if you can't do it in software (because of a bad MLC).

Would anyone like to try these once finished and test?

WOW! Fantastic work! My immediate thought was "Sure, I'll be glad to test!" but realistically I would rather see these go into the hands of better developers like @SDIO or @V10lator and for that reason, I'll gladly opt out so that they can get one.

wavebeam · Mar 21, 2023

Here's my Sys Info from UDPIH for record keeping purposes. once i get my other, vanilla, wii u back from a friend i'll dump it for safe keeping and get a sys info shot from it as well.

SDIO · Mar 21, 2023

I am currently working on adding the NAND Dumper to the recovery menu. When that is done I will look into writing a tool to write back a NAND Dump in software.
Also I think I found something problematic how the retrys are handled in the the original NAND dumper, which I suspect caused my first NAND Dump to become more corrupt than it needed to be.

I would have a second Wii U with bad eMMC, where I could try out this hardware which would make a replacement much easier.

I am currently also looking out for a Wii U hat doesn't produce a screen output and has a static blue LED. I think this could be caused by eMMC with went read only, but thats just a vague hypotheses which I want to check. But till now I didn't find one for a reasonable price.

@PressLeft September 2013 this is outside the suspected range. Did you check the mlc dump and the logs for corruption?

wavebeam · Mar 21, 2023

SDIO said:
@PressLeft September 2013 this is outside the suspected range. Did you check the mlc dump and the logs for corruption?

i didn't, not sure how. there doesn't appear to be a log file on the sd card.
i did watch the dump process, MLC had 0 retries

Voultar · Mar 21, 2023

Can we tristate the eMMC on the Wii-U and/or make it go HI-Z so that we can leave it on the Wii-U?

SDIO · Mar 21, 2023

PressLeft said:
i didn't, not sure how. there doesn't appear to be a log file on the sd card.
i did watch the dump process, MLC had 0 retries

I meant the logs in the slc in /sys/logs. You can either extract them from the slc backup you did with the Wii U NAND Extractor or copy them from your Wii U with FTPiiU everywhere

Voultar said:
Can we tristate the eMMC on the Wii-U and/or make it go HI-Z so that we can leave it on the Wii-U?

I didn't have any problems with leaving it on the board and just cut the clk trace. The data and cmd lines are still connected through the resistors. I would recommend grounding the clock, then it should do nothing and have the all the I/Os as inputs configured, which shouldn't interfere.
Cutting the clk trace is necessary anyway, if you want to dump through Hardware. The alternative would be to also remove the resistors on the data and cmd line, that would isoloate it completely, but for me it wasn't necessary and I kept the resistors in case I ever need to access the eMMC again.
The eMMC doesn't drive the bus, without being asked to by the host with a command. If the eMMC doesn't get a clk it can't get commands

V10lator · Mar 21, 2023

Voultar said:
Would anyone like to try these once finished and test?

Would love to get my hands on this but will it be possible to switch between eMMC and replacement? Asking as my Wii U is in good condition with a Toshiba...

Beside that CC @GaryOderNichts (dev of UDPIH and stuff), @Maschell (who I'm sure has one or two bad Wii Us in storage to test with) and @Lazr1026 (who did a lot in diagnosting such issues as well as collecting data).

MLConian · Mar 21, 2023

Just dumped my NAND and ran mdinfo. Even though I bought my 32GB PAL Wii U late 2013 (got it for Wind Waker HD) my eMMC seems to have been produced late August 2012. Nintendo really had issues selling these units, didn't they?

Had no errors dumping, as is to be expected by now without Hynix memory. I'll run it through wfs-extract just to be sure.

EDIT:

Seems clean to me.

Lazr1026 · Mar 21, 2023

@Voultar I have a dead Hynix console i wouldnt mind sacraficing.

pulterbit · Mar 22, 2023

@SDIO I might have a spare WiiU if you need one for testing. Just let me know and I can send it over.

MLConian · Mar 22, 2023

SDIO said:
I meant the logs in the slc in /sys/logs. You can either extract them from the slc backup you did with the Wii U NAND Extractor or copy them from your Wii U with FTPiiU everywhere

When I try to extract the SLC.bin with wfs-extract, I get an "unexpected WFS version (bad key?)" error.

Is there anything specific I'm doing wrong? I figured extracting the SLC was the same as the MLC, and I've only got the 1 dump. Should I be calling the seeprom here as well?
Just trying to get the process clear for newbies like myself - and I've got access to some other Wii Us that I'd like to check.

It's a shame we don't seem to be able to pin-point which batches have Hynix modules yet, it's still very much a case-by-case investigation, even if the console itself isn't affected by the issue (yet). Is there perhaps some logic to the serialnumbers?

godreborn · Mar 22, 2023

MLConian said:
When I try to extract the SLC.bin with wfs-extract, I get an "unexpected WFS version (bad key?)" error.
View attachment 360642
Is there anything specific I'm doing wrong? I figured extracting the SLC was the same as the MLC, and I've only got the 1 dump. Should I be calling the seeprom here as well?
Just trying to get the process clear for newbies like myself - and I've got access to some other Wii Us that I'd like to check.

It's a shame we don't seem to be able to pin-point which batches have Hynix modules yet, it's still very much a case-by-case investigation, even if the console itself isn't affected by the issue (yet). Is there perhaps some logic to the serialnumbers?

Slc doesn't need seeprom. Try using wiiu nand tools for slc and slcmpt.

MLConian · Mar 22, 2023

godreborn said:
Slc doesn't need seeprom. Try using wiiu nand tools for slc and slcmpt.

Thanks, that worked like a charm. Seems my Wii U has had 71 critical failures in its life, and came to life on 1 October 2013, more than a year after its eMMC was produced. @SDIO - still interested in the logs, even though it's not a Hynix Wii U?

Ghassen-ga · Mar 22, 2023

i got a hynix chip sadly , can anyone help me dump my nand ?

MLConian · Mar 22, 2023

If you've already homebrewed your system, run NANDdumper from the homebrew channel.

If you haven't, you can do it as part of the Tiramisu loader. Most guides explicity state the dump as an essential part, and you can still load the exploit to run the NAND dumper from there after you put any other CFW on your Wii U. Just make sure your SD card is bigger than your Wii U's memory (so for the 8GB version, you get a 16GB card, for the 32GB version, you get a 64GB card).

Hardware How I fixed 160-0103 system memory error

New Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Attachments

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Member

Welcome to the Machine

Member

Well-Known Member

Member

Similar threads

Popular threads in this forum