OFFLINE UPDATE WII U - Brick 160-0103 - Access recovery menu 0.4

Serjio193

Member
Newcomer
Joined
Dec 18, 2022
Messages
10
Trophies
0
Age
39
XP
107
Country
Estonia
Sorry for the late answer.
You have to create manually the firmware and install tickets with option in recovery menu.
Firmware to create depends on which firmware the nintendo Wii U is bricked.

I don't know if I can upload the file here?

Because you need title key for create this file.
Ticket must be installed 1by one for that work, because recovery menu can't take more than 1 file on the sd card to install.
Wii u 5.5.5E I have access to recovery menu . The installation of wup is available through it, but there is a problem with the creation of wup. I was only able to get it to download from the Nintendo server "menu 00050010-10040200" but the file format is not wup. I can't figure out how to reconvect it in wup.
 

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
1,974
Trophies
0
Age
28
XP
1,266
Country
Germany
Please make first sure to dump the otp. Also please dump the logs and send them to me so we can see whats wrong before doing anything, which might make it worse.
 

Serjio193

Member
Newcomer
Joined
Dec 18, 2022
Messages
10
Trophies
0
Age
39
XP
107
Country
Estonia
Wii u after hard reset, when setting up after choosing that there is no account, I get error 1060-0103. By the syllables in the rekoveri it is clear that something is with nand. Nand I have already changed. But I get the same error. Otp I saved. I'll post the logs tomorrow.
 

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
1,974
Trophies
0
Age
28
XP
1,266
Country
Germany
So you replaced the eMMC chip with another eMMC and cloned the content over?
Do you have a matching (done at the same time, without boot in between) backup of the slc and mlc?


Code:
00;01;09;943: SWKBD: thread=0x100457e0, stackSize=      63 KB, stackBase=0x105dc2b8, stackEnd=0x105cc2c0 (SwkbdCreate)
00:01:10:471: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:529: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:587: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:645: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:703: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00;01;10;584: FS: READ_FILE      upid:[15] sts:[DATA_CORRUPTED] hnd:[0x3b606e4] dst:[0x2b130f80] size:[1] cnt:[1048576] pos:[0]
00;01;10;584: SystemFatal(core0)
this seem to be your problem. I am not sure if that is really caused by a bad eMMC, it could also be caused by a power outage or so.
The real problem is, it doesn't specify a file, so we don't know what to fix. Maybe the problem is even in the file system metadata and not the data of the file, which would be really bad.

If you have a dump of the mlc on the PC, could you run wfs-extract on it and post the errors here?
 

Serjio193

Member
Newcomer
Joined
Dec 18, 2022
Messages
10
Trophies
0
Age
39
XP
107
Country
Estonia
I changed emmc.
Logs
logs
So you replaced the eMMC chip with another eMMC and cloned the content over?
Do you have a matching (done at the same time, without boot in between) backup of the slc and mlc?


Code:
00;01;09;943: SWKBD: thread=0x100457e0, stackSize=      63 KB, stackBase=0x105dc2b8, stackEnd=0x105cc2c0 (SwkbdCreate)
00:01:10:471: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:529: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:587: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:645: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:01:10:703: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00;01;10;584: FS: READ_FILE      upid:[15] sts:[DATA_CORRUPTED] hnd:[0x3b606e4] dst:[0x2b130f80] size:[1] cnt:[1048576] pos:[0]
00;01;10;584: SystemFatal(core0)
this seem to be your problem. I am not sure if that is really caused by a bad eMMC, it could also be caused by a power outage or so.
The real problem is, it doesn't specify a file, so we don't know what to fix. Maybe the problem is even in the file system metadata and not the data of the file, which would be really bad.

If you have a dump of the mlc on the PC, could you run wfs-extract on it and post the errors here?
wfs-extract didn't work for me. I have repaired my Wii u. Even made a guide.
 

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
1,974
Trophies
0
Age
28
XP
1,266
Country
Germany
Glad you got it working again, good job!
why didn't wfs-extract work for you? did you use your consoles otp?
You might want to still try it to make sure, there are no corrupted files left.
Also it would be nice if you could run mdinfo (or System Information from the recovery menu) to see what emmc your console has and when it was made.
 

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
1,974
Trophies
0
Age
28
XP
1,266
Country
Germany
I wouldn't post that publicly or someone might be able to steal the Nintendo account or something like that.

wfs-extract worked, and showed me these files as corrupted:
Code:
wfs-extract --otp otp.bin --mlc --input 12345.img --output extract
Dumping...
Error: Failed to read /"sys/title/00050010/10044200/content/lang_04.bin"
Error: Failed to read /"sys/title/00050010/10044200/content/lang_05.bin"
Error: Failed to read /"sys/title/00050010/10044200/content/lang_06.bin"
Error: Failed to read /"sys/title/00050010/10044200/content/lang_07.bin"
Error: Failed to read /"sys/title/00050010/1004a200/content/arclayout/layout.sgarc.cmp"
Error: Failed to read /"sys/title/00050010/1004a200/content/sound/stream/BGM_STR_BARISTA_ACS_SUGAR_DRC.dspadpcm.bfstm"
Error: Failed to read /"sys/title/00050010/1004a200/content/sound/stream/BGM_STR_MII_EDIT_ORCH_DRC.dspadpcm.bfstm"
Error: Failed to read /"sys/title/00050010/1004a200/meta/bootSound.btsnd"
Error: Failed to read /"sys/title/00050010/1004b200/content/sound/stream/BGM_ACCOUNT_MAIN_TV.bfstm"
Error: Failed to read /"sys/title/00050010/1004c200/content/Common/Sound/Ply/stream/BGM_PLY.bfstm"
Error: Failed to read /"sys/title/00050010/1004d200/content/Common/Package/Inf.pack"
Error: Failed to read /"sys/title/00050010/1004d200/meta/bootTvTex.tga"
Error: Failed to read /"sys/title/00050010/1005a200/code/doors.rpx"
Error: Failed to read /"sys/title/00050010/1005a200/content/art/Audio/stream/DOORS_LOBBY_DRC.dspadpcm.bfstm"
Error: Failed to read /"sys/title/00050010/1005a200/content/art/Audio/stream/DOORS_LOBBY_TV.dspadpcm.bfstm"
Error: Failed to read /"sys/title/00050010/1005a200/content/art/FE/FEGroupMainUI_res.data"
Error: Failed to read /"sys/title/00050010/10062200/content/Common/Layout/caution_00.szs"
Error: Failed to read /"sys/title/00050010/10062200/content/Common/lodging/convert_test/WagonMap2/WiiBg01.szs"
Error: Failed to read /"sys/title/0005001b/1004f000/content/00/Common/Iwnn/dic/FR/CA/regular/njubase3.a"
Error: Failed to read /"sys/title/00050030/10011209/meta/bootTvTex.tga"
Error: Failed to read /"sys/title/00050030/1001120a/meta/bootTvTex.tga"
Error: Failed to read /"sys/title/00050030/1001420a/code/libwkc.rpl"
Error: Failed to read /"sys/title/00050030/1001420a/content/sound/stream/BGM_WOOD_SETTING.dspadpcm.bfstm"
Error: Failed to read /"sys/title/00050030/1001520a/content/Common/Sound/Frd/stream/BGM_FRD.bfstm"
Error: Failed to read /"sys/title/00050030/1001720a/code/recipe.rpx"
Error: Failed to read /"sys/title/00050030/1001720a/meta/bootDrcTex.tga"
Error: Failed to read /"sys/title/00050030/1001720a/meta/bootTvTex.tga"
Done!

So these titles seem to be corrupted:
Code:
00050010-10044200
00050010-1004a200
00050010-1004b200
00050010-1004c200
00050010-1004d200
00050010-1005a200
00050010-10062200
0005001b-1004f000
00050030-10011209
00050030-1001120a
00050030-1001420a
00050030-1001520a
00050030-1001720a

If you didn't reinstall all of them anyway, I would recommend using FTPiiU everywhere to replace these files. When I replaced the broken files on my console I did so by first deleting them and then upload the new one. But the safer way would be to upload them with a new name and then rename them and overwrite the old file with that. I had a full backup and the wires for unbricking already soldered, that's why I chose the riskier way.
You can extract the wups on your PC to get these files.

Maybe it would be a good Idea to get a fresh backup of the current state with the nand dumper and see if there are still errors or if you already fixed all of them by reinstalling.

EDIT: also note that if wfs-extract reports a file as corrupted it could still be fine if it was just recently written and a part of it is still in the slc cache. But these system files usually don't get written to, so it is pretty safe to assume that they are corrupt.

Here you can see what each of the title is: http://wiiubrew.org/wiki/Title_database
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    AncientBoi @ AncientBoi: Accidently ok. :tpi: