Hardware Should I fix my half bricked WII U？

[Ysecond]

HELLO ，everyone！！！
I have a WII U，it can turn on and runing games。 But when running any game, it will randomly generate 160-0103 errors.

Its characteristics：
1，5.5.3J
2，It has the HYINX nand，and the HYINX emmc.
3，When I launch ”System settings“ ，it will show me （160-2215） errors.
4，When I launch any game, it will randomly generate （160-0103） errors.
5，Unable to search for WIFI hotspots, any hotspots（103-1605 ，Triggered from launch game) .
6，I don't have a backup of it before it was bricked.

I did：
I backed up slc、mlc，download the Logs。Transfer MLC to SD card，But the problem is the same，no changes。
By the way ，The 128GB sd is not working，The 32GB（sandisk 32GB EDGE）working well。

Next step，Should I fixing the title about ”System settings“ ? But I'm not very sure about the title number。May I can learn from @Serjio193 “ fixing-error-160-0103” ？ but my system is 5.5.3.
Please give me the way, Thank you very much. I enjoy trying it out。

At last
I would like to thank all those who have shared their experiences and tools for fixing game consoles！Thanks！！！
Including but not limited to：
@SDIO @pulterbit @GaryOderNichts @Leeful@EyeKey @V10lator @Lazr1026 ...........

 

[SDIO]

Good Job making it this far. I am pretty confident we will be able to fix the remaining problems.
Can you run the MLC Checker from this recovery and post the mlc_checker.txt logfile here? Then we know which files are broken.
EDIT:

00:00:42:464: mmc_core card err: idx=3, lba=56006400, blks=128, xfer=0x1, ret=0x00200b40
00;00;42;349: ------------------PROCESS 1 LOST FOREGROUND--------------------
00;00;42;349: DIAG: PhysAlloc(2, 0x40000000, 0x00000000, 0x00000000, 0x02000000, 0x00000001)
00;00;42;349: DIAG: InitAddrSpace
00;00;42;350: DIAG: Switch(New)
00;00;42;350: DIAG:+Loader(1, 7)
00;00;42;350: DIAG:+KiRPLLoaderSetup
00;00;42;350: DIAG:-KiRPLLoaderSetup: before no-return call to KiLoadContext (0xEFE09400) (0x01003FFC)
00;00;42;350: Title Loc is 0
00:00:42:486: mmc_core card err: idx=3, lba=56006400, blks=128, xfer=0x1, ret=0x00200b40
00:00:42:486: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:42:487: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:42:518: mmc_core card err: idx=3, lba=56005632, blks=1024, xfer=0x1, ret=0x00200b40
00:00:42:559: mmc_core card err: idx=3, lba=56005632, blks=1024, xfer=0x1, ret=0x00200b40
00:00:42:559: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:42:694: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:42:695: failed to read file /vol/storage_mlc01/sys/title/00050010/10047000/code/set.rpx, err -196673
00:00:42:696: MCP: preload of '/vol/storage_mlc01/sys/title/00050010/10047000/code/set.rpx' not completed, err -196673

And yes the eMMC was really bust

 

[Ysecond]

Good Job making it this far. I am pretty confident we will be able to fix the remaining problems.
Can you run the MLC Checker from this recovery and post the mlc_checker.txt logfile here? Then we know which files are broken.
EDIT:

00:00:42:464: mmc_core card err: idx=3, lba=56006400, blks=128, xfer=0x1, ret=0x00200b40
00;00;42;349: ------------------PROCESS 1 LOST FOREGROUND--------------------
00;00;42;349: DIAG: PhysAlloc(2, 0x40000000, 0x00000000, 0x00000000, 0x02000000, 0x00000001)
00;00;42;349: DIAG: InitAddrSpace
00;00;42;350: DIAG: Switch(New)
00;00;42;350: DIAG:+Loader(1, 7)
00;00;42;350: DIAG:+KiRPLLoaderSetup
00;00;42;350: DIAG:-KiRPLLoaderSetup: before no-return call to KiLoadContext (0xEFE09400) (0x01003FFC)
00;00;42;350: Title Loc is 0
00:00:42:486: mmc_core card err: idx=3, lba=56006400, blks=128, xfer=0x1, ret=0x00200b40
00:00:42:486: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:42:487: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:42:518: mmc_core card err: idx=3, lba=56005632, blks=1024, xfer=0x1, ret=0x00200b40
00:00:42:559: mmc_core card err: idx=3, lba=56005632, blks=1024, xfer=0x1, ret=0x00200b40
00:00:42:559: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:42:694: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:42:695: failed to read file /vol/storage_mlc01/sys/title/00050010/10047000/code/set.rpx, err -196673
00:00:42:696: MCP: preload of '/vol/storage_mlc01/sys/title/00050010/10047000/code/set.rpx' not completed, err -196673

And yes the eMMC was really bust

Thank you for reply. I will run it, but it will take some time, and I will reply here.

 

[SDIO]

EDIT2: I got these broken files from the logs

17.log:00:01:53:880: failed to read file /vol/storage_mlc01/sys/title/00050010/10047000/code/set.rpx, err -196673
19.log:00:09:31:852: failed to read file /vol/storage_mlc01/sys/title/00050010/1004e000/code/safe.rpx, err -196635

00050010-10047000 is System Settings
00050010-1004E000 Is Health and Safety

The first one is what you already expected and the latter one will become relvant for Aroma or Tiramisu.

But I expect there to be more files broken. The mlc checker will show them all.

You could try to download the System Setting from NUS and reinstall it with the recovery Menu. After that you might be able to setup internet and run the Browser exploit. From there you can then use FTP to replace the other broken files or reinstall broken titles with WUPInstaller (or maybe NUSpli, but I am not sure if it would generate fake tikets and mess something up)

Post automatically merged: May 3, 2023

I just looked at the picture of your the SD card replacement and it certainly looks a lot cleaner than what I did, but I noticed you copied the mistake I made. You get the 3V3 from the Disc Drive, which will cause problems in the recovery, as it powers of the disc drive and with that the SD card. You should get the 3V3 from the upper left leg of the transistor not the middle leg,
EDIT: see https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/page-16#post-10119405

 

[Ysecond]

EDIT2: I got these broken files from the logs

17.log:00:01:53:880: failed to read file /vol/storage_mlc01/sys/title/00050010/10047000/code/set.rpx, err -196673
19.log:00:09:31:852: failed to read file /vol/storage_mlc01/sys/title/00050010/1004e000/code/safe.rpx, err -196635

00050010-10047000 is System Settings
00050010-1004E000 Is Health and Safety

The first one is what you already expected and the latter one will become relvant for Aroma or Tiramisu.

But I expect there to be more files broken. The mlc checker will show them all.

You could try to download the System Setting from NUS and reinstall it with the recovery Menu. After that you might be able to setup internet and run the Browser exploit. From there you can then use FTP to replace the other broken files or reinstall broken titles with WUPInstaller (or maybe NUSpli, but I am not sure if it would generate fake tikets and mess something up)

Post automatically merged: May 3, 2023

I just looked at the picture of your the SD card replacement and it certainly looks a lot cleaner than what I did, but I noticed you copied the mistake I made. You get the 3V3 from the Disc Drive, which will cause problems in the recovery, as it powers of the disc drive and with that the SD card. You should get the 3V3 from the upper left leg of the transistor not the middle leg,
EDIT: see

code/set.rpx, err -196673，

safe.rpx, err -196635

OHHH! Nice! I got this!
I will try downloading from NUS and fixing system settings.

code/

but I noticed you copied the mistake I made.

Thanks,It‘s very important for me，It explains why “could not find a wii u Menu title installed on this system” in recovery Menu.

I run the MLC Checker ,got the logs. But I don't understand what it means ,It's that all the broken files ? unbelievable !
thanks a lot.

 

[Serjio193]

When downloading tikits via nus, we get tikits from the latest firmware, which is currently 5.5.6.J.
I think it's worth completely updating all tikits to the latest firmware using the recovery menu.

 

[V10lator]

unbelievable

You probably should run the MLC checker after fixing the 3.3 V power issue.

I am not sure if it would generate fake tikets and mess something up

It shouldn't use fake tickets as system titles are considered free software and as such legit tickets are downloadable from the NUS.

When downloading tikits via nus, we get tikits from the latest firmware

Not true, one can download older software versions, too.

 

[Ysecond]

When downloading tikits via nus, we get tikits from the latest firmware, which is currently 5.5.6.J.
I think it's worth completely updating all tikits to the latest firmware using the recovery menu.

Got it！I would like to first try repairing the system menu and using the system upgrade function.

Post automatically merged: May 4, 2023

You probably should run the MLC checker after fixing the 3.3 V power issue.

I think I had already fixing 3.3V before running the MLC checker。Because in the recovery menu, "Debug system region" appears with green text but not red。 I forgot the text.

 

[SDIO]

Lines that are not ending with -00000000 arent errors.

I filtered it and there is still a lot of corruption 2341 (you can also see that in the last line) 0x925 is 2341. Sadly there are also damaged foders, we won't be able to completely get rid of them, but we can rename them, so they don't get in the way.

If you want to make sure to get the right version, you can extract the app.xml of the title and look up the version there.
I am not sure if it would be a good idea to try to run an update with corrupted folders. I don't have time now to look up which are all the titles that are corrupted.

 

[Ysecond]

@SDIO I have some news, you may be interested . At the same time, I also want to remind everyone, If you have a 160-0103 console ,please don't casually restore factory settings.

I installed titel 0005001010047000, the system settings are working. I run restore factory settings, now I know that is a mistake.

When the recovery process was running, it told me there was an error in the storage , reboot the console to do it again.
I reboot the console,it show me information like "Restoring factory settings", Not long ago, console well be crashed。
So,i got a bricked now.

After that，I written the backup of EMMC to SD Card（This backup comes from before installing the title）.
And now, I have a console that information160-0103 on startup. It can still launch the recovery menu, but no gamepad connect,and no TV display.

 

[Serjio193]

@SDIO I have some news, you may be interested . At the same time, I also want to remind everyone, If you have a 160-0103 console ,please don't casually restore factory settings.

I installed titel 0005001010047000, the system settings are working. I run restore factory settings, now I know that is a mistake.

When the recovery process was running, it told me there was an error in the storage , reboot the console to do it again.
I reboot the console,it show me information like "Restoring factory settings", Not long ago, console well be crashed。
So,i got a bricked now.

After that，I written the backup of EMMC to SD Card（This backup comes from before installing the title）.
And now, I have a console that information160-0103 on startup. It can still launch the recovery menu, but no gamepad connect,and no TV display.

You received an error as there were errors in your operating system.
You need to reinstall even one title 00050010-1004E000 as a minimum.

Although I still insist on reinstalling all headers through the recovery menu.

 

[V10lator]

Not long ago, console well be crashed。
So,i got a bricked now.

This was caused by the Wii U trying to remove the corrupted folders while doing the factory reset and could have been fixed by UDPIH with ease but this:

I written the backup of EMMC to SD Card

Messed up the contents of the SLC cache and the eMMC. Did you take a new backup before writing in the old one? If so restore that new backup. If not: Do you have a SLC backup taken at the same time you took the eMMC backup?

 

[Ysecond]

Did you take a new backup before writing in the old one?

YES！before writing in the old one，I made a backup again。How can ifixed by UDPIH？could you give me some tips？
Thanks！

Post automatically merged: May 5, 2023

Although I still insist on reinstalling all headers through the recovery menu.

Right! In fact, I agree with your suggestion. Later, I will also try installing title 00050010-1004E000.
I am glad that I have carried out these operations. I believe it can give some inspiration to others.
Thanks!!!

 

[SDIO]

Even a backup done before restoring the backup probably can't undo the damage, as you already booted with the restored sdcard. Now the SLC cache is consistent with nothing.

We can try it, but I wouldn't be surprised if the file system is now even more damaged.

What Backups do you have? How were the backups taken and do the backups include SLC and MLC?

Post automatically merged: May 5, 2023

You received an error as there were errors in your operating system.

No, the error was probably caused by one of the corrupted directories, as @V10lator already mentioned. When the Factory tries to delete them it will hang as corrupted directories can't be deleted. For a directory to be deleted the OS needs to know whats inside the directory, so it can be delted to. But because the directory is unreadable it can't know. The only option we have right now to deal with them is to move them somewhere, where they don't cause trouble or if that isn't possible to rename them.

You need to reinstall even one title 00050010-1004E000 as a minimum.

That isn't the problem right now.

Although I still insist on reinstalling all headers through the recovery menu.

I don't know what you mean by headers, but it sounds wrong. Randomly replacing stuff could make it much worse.

YES！before writing in the old one，I made a backup again。How can ifixed by UDPIH？could you give me some tips

The only way right now to fix a inconsistent SLC cache is to flash both the SLC and the MLC back from a consitent backup.
In theory there could also be possibility to flash a backup back through FSA if and only if it was also done created through. FSA is used by the Dumper option in my modified recovery menu. All other options that I know of don't use FSA. That's why I was asking how the backup was created. But I don't have a restore option implemented right now, so this was never tested.

You can, like @V10lator suggested try to restore the last state of the sdcard, but since you tried to boot with a different state, in factory reset mode, which causes heavy writing, there is a good chance the cache is now too messed up. Maybe the is the slim chance that the missmatched state of the SD caused the OS to crash early enough before any writes happened.
Please also see my post https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/ read the inital post fully and make sure you understand the SLC cache (SCFM) and all of it's implications.

The factory reset can be canceled by setting initialLaunch to 0 in the /sys/proc/prefs/cafe.xml in the SLC (so restorying the MLC won't even stop the factory reset). This can be done though wupserver. @V10lator can give more details on it, since he needed to do exactly that to his Wii U.

Right! In fact, I agree with your suggestion. Later, I will also try installing title 00050010-1004E000.

No, thats not our priority right now and it could make things worse with the mismatched cache.

I would suggest the following next steps:
1. Restore the SD Card back to the state before you overwrote it with the older backup.
2. Run the MLC checker again, so we can see if there are new errors.
3. wait for the next steps and don't try anything else

 

[Ysecond]

Please also see my post https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/ read the inital post fully and make sure you understand the SLC cache (SCFM) and all of it's implications.

Yes！a few days ago，I have read your article, understand that MLC needs to match SLC cache.
So when I have the earliest backup(SLC&MLC)，I don't feel worried。Because I can still use the NAND programmer（like Teensy 2.0 ++ ?,nando?).

1. Restore the SD Card back to the state before you overwrote it with the older backup.

OK,I have already done it. it show me "Restoring factory settings" again.
Next, I will Run the MLC checker again, and I will learn to use wupserver to canceled factory reset.
Thanks a lot!

 

[V10lator]

Here's how to fix the factory reset:

1) Run MLC Checker.
2) Use wupserver / wupclient to make a new folder (like w.mkdir("/vol/storage_mlc01/corrupt", 0)).
3. Use wupserver/wupclient to move all folders (but not the files!) MLC Checker reported as corrupt into that new folder (w.mv(oldPath, newPath)).
4. Use wupserver/wupclient to remove all none system titles (like games, updates and DLC. Use delete_title(path) but check the title IDs against https://wiiubrew.org/wiki/Title_database to make sure to not remove system software).
5. In case there are still corrupted files left reinstall the corresponding software with UDPIH.
6. In case there are still corrupted files left tell us which ones but in case all corrupted files are gone:
7. Do

setting initialLaunch to 0 in the /sys/proc/prefs/cafe.xml in the SLC

So w.dl("/vol/system/proc/prefs/cafe.xml") then edit the file as told and w.up it back to the Wii U.
8. Execute flush_mlc() and reboot.

This should reboot you into the initial settings to finish the factory reset.

Note that the folder from step 2 will bring any new factory reset to crash, too, so try to avoid resetting the Wii U again.

 

[Ysecond]

Here's how to fix the factory reset:

1) Run MLC Checker.
2) Use wupserver / wupclient to make a new folder (like w.mkdir("/vol/storage_mlc01/corrupt", 0)).
3. Use wupserver/wupclient to move all folders (but not the files!) MLC Checker reported as corrupt into that new folder (w.mv(oldPath, newPath)).
4. Use wupserver/wupclient to remove all none system titles (like games, updates and DLC. Use delete_title(path) but check the title IDs against https://wiiubrew.org/wiki/Title_database to make sure to not remove system software).
5. In case there are still corrupted files left reinstall the corresponding software with UDPIH.
6. In case there are still corrupted files left tell us which ones but in case all corrupted files are gone:
7. Do

So w.dl("/vol/system/proc/prefs/cafe.xml") then edit the file as told and w.up it back to the Wii U.
8. Execute flush_mlc() and reboot.

This should reboot you into the initial settings to finish the factory reset.

Note that the folder from step 2 will bring any new factory reset to crash, too, so try to avoid resetting the Wii U again.

Thank you very much！It is already detailed enough.If still not working, I will double check my work。

 

[SDIO]

Can you share the log from the mlc checker?

 

[Ysecond]

Can you share the log from the mlc checker?

Yes！take a look，please。

 

[SDIO]

Looks like you created new corruption:

'OpenDir;/vol/storage_mlc01/usr/save/00050010/10040000/user/80000001;-0003001B',
 'ReadDir;/vol/storage_mlc01/usr/title/00050000/10102200/content/motions/;-0003001B',
'ReadDir;/vol/storage_mlc01/usr/title/00050000/10102200/content/movie/game_mov_d06.h264;-0003001B',
 'ReadDir;/vol/storage_mlc01/usr/title/00050000/10102200/content/samu/dog_icon/;-0003001B',
 'ReadFile;/vol/storage_mlc01/sys/title/00050010/10047000/code/title.fst;-0003001B',
 'ReadFile;/vol/storage_mlc01/sys/title/00050010/10047000/code/title.tmd;-0003001B',
 'ReadFile;/vol/storage_mlc01/sys/title/00050010/10047000/content/JpJapanese/Message/AllMessage.szs;-0003001B',
 'ReadFile;/vol/storage_mlc01/sys/title/00050010/10047000/meta/bootLogoTex.tga;-0003001B',
 'ReadFile;/vol/storage_mlc01/sys/title/00050010/10047000/meta/meta.xml;-0003001B'

One of them is the Settings App again. Probably because you reinstalled it, it was still in the cache. But at least there only seem to be files corrupted and not directorys, so you should be able to reinstall it.

But you created additional corrupted directories in the usr folder. You will have to live with them, the only thing you can do with them is to move them.

When you are now deleting and replacing stuff you can expect that there will be more errors emerging, because there are probably some messed up inodes now.
For example look at

'ReadDir;/vol/storage_mlc01/usr/title/00050000/10102200/content/movie/game_mov_d06.h264;

The Parent directory thinks it's pointing to a directory, thats why an ReadDir was attempted. But it looks like the inode it is pointing to belongs now to a file somewhere else (going by the name).

Good look with that...

What Backups do you have and by what method where they taken?

You can try to reinstall the settings app and cancel the Factory Reset, but I would prefer to restore an consistent backup to SLC AND MLC, if one is available, but first tell us what you have.

I attached a list of the rest of the corruption (including the one that was there before)