Hacking Wii - System Files Corrupt (non-modded Wii)

[KingMob75]

First - I've done lots of reading, searching, trying things, etc. I've also modded a few Wii's in my time but never came across this.

I acquired this Wii (I do not know it's history but as far as I can tell no attempts to mod this were made) that was getting the system files corrupt message when selecting anything from the menu. After some research I found maintenance mode. I formatted the system memory (as suggested in a few different pages that I came across in my research) and almost couldn't make it through the initial setup without getting the error again. Finally I was able to complete the setup and get to the health warning screen but as soon as I pressed A to continue I got the error again.

Back into maintenance mode and was able to install HBC and BootMii using the Return of the Jodi exploit. I haven't been successful in finding out what exactly I should be doing next. Will be doing some more research but any tips would be appreciated.

This is a US Wii. System menu is 4.3U

 

[stomp_442]

were you able to install bootmii as boot2?

 

[KingMob75]

were you able to install bootmii as boot2?

Correct, Bootmii installed a boot2. Wii loads to the bootmii menu successfully. I can launch the HBC from that menu but when I try to access the Wii menu same results.

Something else I noticed is while in maintenance mode the wifi isn't working. More specifically doesn't see my wifi network. Even when I put in SSID, network security type, etc, it doesn't work. Not sure if this is something that doesn't work in maintenance mode.

 

[stomp_442]

well, I think there are methods to rebuild the NAND.BIN, and with bootmii installed as boot2 you are able to restore the NAND of the Wii.

Have a look around for ohneswanzenegger, I think you can rebuild your NAND dump with that, and then reinstall it via bootmii.

There may be easier methods to repair your Wii, I'm no brick repair expert, so don't quote me on any of this.

 

[Heran Bago]

Start BootMii.

Back up your NAND. If you have a previous NAND backup, rename it or save it somewhere else first.

You may get lucky and just this process can fix bad sectors for you.

If it doesn't try restoring from your old (or failing that, new) NAND backup. Again this only might work.

 

[stomp_442]

Yea, it might fix it, but I think that the nand dump will be corrupted, and then when it's reinstalled bootmii will reinstall the corrupted dump around the bad sectors.

 

[elricorico]

I had the exact same experience with a wii I picked up a couple years back. I thought for sure I had ruined any chance of recovery after failing to make it through the setup a couple of times.

Once I did get it set up I stumbled across det1re's mailbox fix. It doesn't seem to get much attention, but it worked for me. There is a how-to file in the rar.

http://det1re.de/d/hb/mailbox_brick_fix-det1re.rar

 

[stomp_442]

If the op has access to the hbc, maybe just reinstalling the system menu will fix the problem.

 

[KingMob75]

I don't have a backup of the NAND. Since it was already malfunctioning when I received the Wii I didn't think there would be much use for a corrupted backup. But I'll be sure to get a copy before going any further.

I'd like to get one thing clarified since I never had to restore a NAND before : After I make the backup of the NAND, lets say I do something to make matters worse (ie: can't even get into maintenance mode) restoring the NAND I backed up I'll at least be able to get back to the point I am at now (able to access maintenance mode before the sys files message comes up). Correct? I understand I'll still have the problem with the sys files being corrupt.

Thanks for all the suggestions. Most likely I will not get the time to sit down and work on this for a few days, but I'll update with progress and/or fix.

 

[stomp_442]

The first thing you should do is make a nand backup, it's hard to say if it will get your wii back to where it is now if you mess it up more, but at least you will have that nand backup, even if the nand is corrupted it can still be repaired.

 

[KingMob75]

Tried re-installing the system menu with DOP-Mii, no luck.

Then I tried det1re's mailbox fix but didn't get too far with that. I selected the option for continuing without IOS reload and I also used IOS 36 (as suggested by the app) and received the error ES_Identify (ret = -1017) Identify as SU failed, press any button to continue

 

[icebrg5]

When you boot into maintenance mode are you able to go into the system settings?

I have read that some channels installed on the wii can cause this error as well as some game saves as well.

You can try deleting them 1 by 1 and see if that fixes the issue.

 

[KingMob75]

When you boot into maintenance mode are you able to go into the system settings?

I have read that some channels installed on the wii can cause this error as well as some game saves as well.

You can try deleting them 1 by 1 and see if that fixes the issue.

Only channel that comes up in System Settings is HBC

 

[icebrg5]

are there any game saves showing up?

 

[KingMob75]

are there any game saves showing up?

No, no save games either.

 

[DarkMatterCore]

Well, considering that you did a System Format, I think it is safe to assume that the det1re MailBox Brick fix will not work for your case; as far as a I know, the WC24-related files under /shared2 also get wiped. But I guess you wouldn't lose anything for trying again: you gotta choose IOS236 or a cIOS. FSToolBox is old, really old, back then it was normal to have a fakesigned IOS36. Not anymore.

The behaviour you describe when you're in Maintenance Mode is completely normal. Most WC24-related functions (if not all) get disabled; that includes Wi-Fi connection the System Menu. It also explains why some channel banners (for example, Mario Kart Channel) get all "messy" when this mode is enabled.

You don't really have any channels that could be generating the problem... And the HBC is just out of the question. You reinstalled the System Menu, but that didn't quite do the trick.

If nothing else works, I'd say ohneswanzenegger is the way to go, just like SickPuppy said. You can't lose what you don't have, since the Wii is basically "empty." Just make sure you create a new NAND backup; it is necessary for the process, because the program needs to have an exact copy of your console keys, your bad blocks and even boot1 and boot2 data.

 

[KingMob75]

If nothing else works, I'd say ohneswanzenegger is the way to go, just like SickPuppy said. You can't lose what you don't have, since the Wii is basically "empty." Just make sure you create a new NAND backup; it is necessary for the process, because the program needs to have an exact copy of your console keys, your bad blocks and even boot1 and boot2 data.

Totally forgot about ohneswanzenegger! Rebuilt the NAND and that fixed the problem! No more system files corrupt message.

Thanks for all the help everyone