Hacking Bricked wiiu, flashed backup SLC.bin now stuck on wiiu boot screen

instanoodless

New Member
OP
Newbie
Joined
Jul 26, 2021
Messages
2
Trophies
0
Age
37
XP
10
Country
Canada
Hi everyone, I have read all I can but I think I am now stuck and am hoping for some guidance.

I picked up a bricked wiiu, they had it soft modded but wanted to factory reset it to sell it. The system failed its factory reset and was stuck booting into the factory reset menu when you turned it back on. From what I understand he didnt used CBHC as he said his softmod wasnt permanent and you had to activate it after turning the system on. I got a USB flash drive from him that contained his SLC.bin and OTP.bin file backups so I ran SLC.bin through the nandbincheck program and it came up clean (bad block in a temp file, consensus was its fine). I soldered up my Teensy and flashed the copy of the SLC.bin to the system and everything programmed fine then I removed my Teensy but left the wires soldered on. Now when you turn the system on the blue light comes on quickly, turns off then comes back on again with the white eject led on too and the system just sits at the white wiiu boot screen.

I tried running the SLC.bin through nandCBHCremover just in case but there was no syshax.xml found. I opened up the system.xml file using nand extractor and it appears to be trying to load the right title id's if I am understanding everything. The default OS title id is 000500101000400a which seems to be inside SLC.bin and the default title is the home menu @ 0005001010040100 which also seems to be right but it must be saved on the MLC? Since the system failed its factory reset is it possible that the system menu on the MLC is corrupt and cant load? If it is would it be possible to change the default_os in my system.xml to the system updater OS "00050010100040FF" and some how recover the home menu or and I way off in my understanding of how this thing works?

I have my Teensy from doing a crap load of hardware downgrades on PS3's but I am not very familiar with wiiu's and was wondering if anyone could help me out with getting this thing working again.

Appreciate any help, Thanks.
 

godreborn

Well-Known Member
Member
Joined
Oct 10, 2009
Messages
20,843
Trophies
1
XP
12,875
Country
United States
don't know, but the mlc uses the otp.bin as well. only the usb device uses seeprom. I don't know if you can flash it directly though. whenever I tried decrypting the mlc with the otp.bin, it error'd on the same file. could be a bug with what I was using, but the mlc is far more a pita than the slc. the slc -- I have no issues with.

--------------------- MERGED ---------------------------

it sounds like a cbhc brick if the title id is wrong. I'd have to open my slc to see what it is. the system.xml and syshax.xml are nearly identical as you probably know. the only difference is the title id. the system.xml is copied to syshax, then the system.xml is modified. you can look up the title id if you suspect that it's cbhc related.

--------------------- MERGED ---------------------------

I just looked up that alphanumeric, yes, it does seem to go with the usa wii u menu. iirc 00050010 is a system title while 00050000 is a game.

--------------------- MERGED ---------------------------

that's what I have in my syshax, and I'm USA, so no cbhc brick:

upload_2021-7-26_14-53-29.png
 

instanoodless

New Member
OP
Newbie
Joined
Jul 26, 2021
Messages
2
Trophies
0
Age
37
XP
10
Country
Canada
don't know, but the mlc uses the otp.bin as well. only the usb device uses seeprom. I don't know if you can flash it directly though. whenever I tried decrypting the mlc with the otp.bin, it error'd on the same file. could be a bug with what I was using, but the mlc is far more a pita than the slc. the slc -- I have no issues with.

--------------------- MERGED ---------------------------

it sounds like a cbhc brick if the title id is wrong. I'd have to open my slc to see what it is. the system.xml and syshax.xml are nearly identical as you probably know. the only difference is the title id. the system.xml is copied to syshax, then the system.xml is modified. you can look up the title id if you suspect that it's cbhc related.

--------------------- MERGED ---------------------------

I just looked up that alphanumeric, yes, it does seem to go with the usa wii u menu. iirc 00050010 is a system title while 00050000 is a game.

--------------------- MERGED ---------------------------

that's what I have in my syshax, and I'm USA, so no cbhc brick:

View attachment 271339

I guess I will forget about the MLC stuff then. My system.xml line for default_os_id is the same as yours and the next line is "<default_title_id type="hexBinary" length="8">0005001010040100</default_title_id>" which appears to be the home menu.

Oh well, I figured that having the backup of the SLC was going to make this fairly easy. Back in the box it goes until I have more time to play around with it.

Thanks for your help
 

godreborn

Well-Known Member
Member
Joined
Oct 10, 2009
Messages
20,843
Trophies
1
XP
12,875
Country
United States
the title id (what you just posted) is what's changed. my system.xml has the one for brain age. the syshax.xml (the original system.xml) has the same title id (same as yours), so the system must not have cbhc installed.

--------------------- MERGED ---------------------------

what's odd is that logically, that slc.bin should work, as long as it's not cbhc, which it's now confirmed. he couldn't have accidentally deleted a game to cause this to happen, and the system obviously worked when the person dumped the slc.bin. the otp.bin is just to modify the flash, so it's not really needed for this instance unless something has been modified in the flash. it's a needle in a haystack sort of thing here, because there's no telling what's been modified or what the person did.
 
General chit-chat
Help Users
    Psionic Roshambo @ Psionic Roshambo: Lol