Hardware How I fixed 160-0103 system memory error

[Ysecond]

It doesn't appear like you have any corrupted files at all, yet there are MEDIA ERRORS.
Huh.

I really have no idea about media errors.
I tried to modify cafe.xml to initiate factory reset, but it will freeze in the factory reset too.
I realize the media errors, but I don't know what it means.

 

[SDIO]

Could still be a mlc problem. Maybe the error is just in some fs metadata, that isn't used when the mlc check runs runs. The error seems to only convern this one LBA: 131072

Also it methions only

path:/

so the root directory and not a file.

There is a procedure to format the mlc through the recovery. I mentioned it somewhere but there is no real tutorial and everything has to go right on the first try.
@Lazr1026 did this procedure a few times I think.

 

[Ysecond]

The error seems to only convern this one LBA: 131072

Perhaps I can try blindly installing all titles.

I mentioned it somewhere

Yes, I have already read it. It requires de_ Fuse, and more pi pico. To welcome it, I designed a PCB，and the PCB looks very stupid， It hasn't been finalized yet.
Thank you for everything.

 

[SDIO]

No you can do it without defuse if the recovery works.
It's basicly launching the recovery with wupserver early enough (before display inits) and then using a custom wupclient to format the mlc, create essential folders and reinstalling all the mlc titles.

 

[Ysecond]

No you can do it without defuse if the recovery works.

Ohhh, I'm like a fool, I should wait for further good news.

 

[SDIO]

Can you do a dump with the recovery an report on the number of errors and badblocks?

 

[Ysecond]

on the number of errors and badblocks

What should I do? Using the MOD recovery menu?

 

[SDIO]

Do a backup using the modfied recovery.

For the format part I don't have capacity right now to guide you through it. Especially as there is no room for errors.

 

[Ysecond]

Is that this version "recovery_menu_dumper_hynix" well be report errors and badblocks?

 

[SDIO]

that's with the code optimized for hynix.
For this console I would use the older one, without the hynix optimizations

 

[Ysecond]

Okay, get it, let me search for the old one.
Good night !

 

[Ysecond]

Do a backup using the modfied recovery.

I used the old modfied recovery for dumping and received this reply, and the console will get stuck.
I can't waste too much of your time, SO I'll put this console aside for now, maybe well try using de_ Fuse rebuild MLC later.
Thanks !

 

[SDIO]

Just wait a little longer till you start the dump. Maybe the mlc was still accessed and thus preventing the unmount

 

[Ysecond]

I just successfully dumped MLC ，have no errors（errors 0，bad sectors 0）.
I tried using wupclient to delete some titles，like ：

delete_title("/vol/storage_mlc01/usr/title/00050000/10105700")
delete_title("/vol/storage_mlc01/usr/title/00050000/10136100")

Then enter “ w.ls( ) ” confirms that they have been successfully delete, but when I restarted the console, those titles appeared again, as if they had never been deleted.
I am trying to install some title, SLC title successfully installed, but MLC title never succeeded.
I think MLC is read-only state.

 

[V10lator]

when I restarted the console, those titles appeared again, as if they had never been deleted.

You forgot flush_mlc() at the end, didn't you?

MLC title never succeeded.

Try to delete_title() them before reinstalling but make sure to delete and reinstall in the same session.

 

[Ysecond]

flush_mlc()

I do it everytime，super sure.
I can't delete a sys title:

>>> delete_title("/vol/storage_mlc01/sys/title/00050030/1001600A")
0x152044
delete title : 0xfffbfffbL
0x0
>>> flush_mlc()
0x153044
0x0
0x0
>>> w.ls("/vol/storage_mlc01/sys/title/00050030")
     10010009/
     1001000a/
     10011009/
     1001100a/
     100110ff/
     1001200a/
     1001300a/
     1001400a/
     1001500a/
     1001600a/
     10017009/
     1001700a/
     1001800a/
     1001900a/
     1001a10a/
     1006d00a/
>>> w.ls("/vol/storage_mlc01/sys/title/00050030/1001600A")
     code/
     content/
     meta/
>>>

 

[SDIO]

Can you show the logs?

 

[Ysecond]

This is the console and logs https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/post-10204383

 

[SDIO]

this block probably holds some important fs metadata. I don't think this can be solved without formatting the mlc.
Maybe if you overwrite that LBA, the eMMC won't report an error, but then I would expect the wfs to produce a DATA CORRUPTION error.

For now we have the tutorial for using defuse with stroopwafel to format and rebuild the mlc, but it can also be done from recovery. It just needs some good preparation or else it will brick and you would need to defuse anyway.

Maybe the ISFShax, that exists for years, but was released todays publicly would be a good alternative to defuse for your usecase, but there isn't a installer for it that you can use right now. It is thinkable to add that to the recovery but it would need some work.

 

[Ysecond]

Just let De_ Fuse save this console! That's a reassuring plan.