Unbricking a Wii U booting to Master Title 10066000 instead of 10040100

[Degenx]

So I bought a Wii U over the weekend at a thift store, and when I got it home, I found out it was bricked. It hangs on the Wii U boot screen.

I was able to dump the system logs using Recovery Menu and I noticed that the Master Boot section, shows it's booting to 1006000 instead of the stock 10040100. Anyone have any idea what 100600 may be? I'm trying to figure out what they did to brick, so I can figure out how to fix it. Any leads of what 1006000 is and how I may go about fixing this would be appreciated. I've attached the system logs anyone wants to take a peak at those.


00;00;07;354: TEST COOKIE: YOSHI-1992-11-21-00-00-00
00;00;07;356: DIAG:Issued KiPrepareTitleAsync(0x0005001010066000)
00:00:08:236: MCP: did not find 'preload.txt' at '/vol/storage_mlc01/sys/title/00050010/10066000/code', rval -196631
00:00:08:236: MCP: Preparing eco_process.rpx
00:00:08:242: MCP: Mapping /vol/content to /vol/storage_mlc01/sys/title/00050010/10066000/content

 

[godreborn]

It's in the system.xml, the default title id. This is in /slc/config

 

[Degenx]

Thank you! I had the WUPServer up and running and was poking around in Wii U, but it looks like that only gives me access MLC unless I'm just dense.

I've never used python scripts before today and my Wii U will not actually display the recovery menu, so between teaching myself Python scripts on the fly and using recovery menu blind, I'm kinda happy I got this far.

 

[godreborn]

Thank you! I had the WUPServer up and running and was poking around in Wii U, but it looks like that only gives me access MLC unless I'm just dense.

I've never used python scripts before today and my Wii U will not actually display the recovery menu, so between teaching myself Python scripts on the fly and using recovery menu blind, I'm kinda happy I got this far.

Hmm, not sure what to do in this event. There's a script that will fix a cbhc brick, but that 00050010 should be a system title.

 

[Degenx]

I'm currently looking at everything in the sys/title/00050010/1006600/ folder. If I backup everything there, I wonder what would happen if I just copy everything from the 10040100/ to 1006600/ folder. At least that way startup is pointing to the right folder?

 

[godreborn]

I'm currently looking at everything in the sys/title/00050010/1006600/ folder. If I backup everything there, I wonder what would happen if I just copy everything from the 10040100/ to 1006600/ folder. At least that way startup is pointing to the right folder?

Nm, it's not.

Post automatically merged: Jan 18, 2023

You could try it.

 

[Degenx]

Well I'm doing a full backup of the mlc via the WUPclient, so it's gonna take awhile to download. Just gonna let it do it's thing overnight and start messing around with the files once I know I have a full backup.

 

[godreborn]

@GaryOderNichts might have a solution.

 

[GaryOderNichts]

I'm not at my PC right now. I can check through the logs later.

I'm currently looking at everything in the sys/title/00050010/1006600/ folder. If I backup everything there, I wonder what would happen if I just copy everything from the 10040100/ to 1006600/ folder. At least that way startup is pointing to the right folder?

This is not a good idea. Changing the startup title id would be a better idea, if that's the case.

 

[V10lator]

I wonder why nobody looks up that title ID, so I did: 00050010-1006600 is the ECO process. As gary said you should not overwrite this. Instead wait for someone experienced to read your logs.

 

[GaryOderNichts]

Ended up looking through your logs. The logs which start the eco process are all from within eco mode, so this is intended behaviour.

00;00;07;354: TEST COOKIE: YOSHI-1992-11-21-00-00-00
00;00;07;356: DIAG:Issued KiPrepareTitleAsync(0x0005001010066000)
00:00:08:236: MCP: did not find 'preload.txt' at '/vol/storage_mlc01/sys/title/00050010/10066000/code', rval -196631
00:00:08:236: MCP: Preparing eco_process.rpx
00:00:08:242: MCP: Mapping /vol/content to /vol/storage_mlc01/sys/title/00050010/10066000/content

A bit further upwards in that logs you'll find

00:00:01:076: MCP: System is in ECO Mode

The latest few logs (6-10.log) all fail to load the set.rpx due to a data corruption error. It does load the Wii U menu successfully first though, so I don't see why it would be stuck on a Wii U screen.
Unfortunately if data corruption is the actual issue this is a hardware issue.

00:00:33:219: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)

mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]

 

[godreborn]

Didn't look at the log, but I wouldn't know what I was looking at if I did. Thanks @GaryOderNichts and @V10lator .

 

[Lazr1026]

@Degenx would you be interested in sending the console to me? ive been wanting a console i can experiment with, in this case replacing the eMMC with a new one.

 

[Degenx]

Thank you @GaryOderNichts, @V10lator and @godreborn !
Trying to understand what was going on in the logs, I was comparing the brick Wii U logs to the logs of a working Wii U I own, and that's why I though the Eco mode had something to due with bricking as my working Wii U did not have eco mode in the same spot of the log. I got hung up on the first difference I saw and completely glossed over the big honking data corruption!

I really do appreciate everyone taking time to chime in and offer guidance on this!

Post automatically merged: Jan 19, 2023

@Degenx would you be interested in sending the console to me? ive been wanting a console i can experiment with, in this case replacing the eMMC with a new one.

I already have someone that has expressed interest in the console, but if they no longer want it, I'll be in touch!

 

[Lazr1026]

I already have someone that has expressed interest in the console, but if they no longer want it, I'll be in touch!

insert thumbsup emoji here (why isnt there just a plain thumbsup emoji?)

 

[godreborn]

Thank you @GaryOderNichts, @V10lator and @godreborn !
Trying to understand what was going on in the logs, I was comparing the brick Wii U logs to the logs of a working Wii U I own, and that's why I though the Eco mode had something to due with bricking as my working Wii U did not have eco mode in the same spot of the log. I got hung up on the first difference I saw and completely glossed over the big honking data corruption!

I really do appreciate everyone taking time to chime in and offer guidance on this!

Sorry it couldn't be better news. I didn't look up the title id, since my laptop is down atm, but it's not like I know enough to figure out a log file. Lol. Anyway, I knew Gary would know how to decipher it.

 

[Degenx]

Sorry it couldn't be better news. I didn't look up the title id, since my laptop is down atm, but it's not like I know enough to figure out a log file. Lol. Anyway, I knew Gary would know how to decipher it.

It's all good! I got this Wii U with all hookup, manual, gamepad, pro controller and 2 generic controllers for $50, so I still got a good deal on it. The console being bricked is fine, as I still got a deal on all the hookups. It was more about learning about the Wii U as I've never owned one before.

Mostly I've worked on the various Xboxs and Playstations, so I'm familiar with how things work those systems. The Wii U is was something new, so I jumped at diving head on into a brick.

 

[N7Kopper]

The latest few logs (6-10.log) all fail to load the set.rpx due to a data corruption error. It does load the Wii U menu successfully first though, so I don't see why it would be stuck on a Wii U screen.
Unfortunately if data corruption is the actual issue this is a hardware issue.

00:00:33:219: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)

mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]

It's such a waste really - all that it would take to recover from such errors is a recovery mode baked into the bootrom that accepts signed update files off of the SD card or something, like what the Xbox One and Series have - maybe theirs aren't baked into the bootrom, but "baked into bootrom" is the best place for such failsafes.

 

[Lazr1026]

It's such a waste really - all that it would take to recover from such errors is a recovery mode baked into the bootrom that accepts signed update files off of the SD card or something, like what the Xbox One and Series have - maybe theirs aren't baked into the bootrom, but "baked into bootrom" is the best place for such failsafes.

That would not help an already dying NAND.