I had 3.2 + homebrew running fine on my NTSC (WiiKey 1.9s) for quite a while. Those were great times. However I had to go and ruin it.
I let my friend play a Shaun White Snowboarding disc that I knew was PAL, but thought for sure was properly region'friid and brick-blocked. Long story short, I wasn't paying attention when it prompted to do a system update and he accepted it. Sheesh that's a lesson learned the hard way ! So I inevitably screwed up big time, and know good and well just how big of a careless mistake that really was. No excuses.
Anyway, my system was semi-bricked, and I started getting the "System Files are Corrupt" message about 75% of the time. I could still boot the Wii normally, get past the A screen, and see all the Channels. I could even get homebrew working still. I could also get past the corrupt message altogether when I booted in maintenance mode. However I couldn't get to some areas of the system menu, and could no longer get it to connect online no matter what settings I changed.
I tried a LOT of troubleshooting. The system menu wads for NTSC (v289) didn't work to fix it. I was getting ready to install Starfire (which would have likely rescued me in the end), however I was distracted when I found a game disc from my NTSC region that had a newer firmware than mine (WiiMusic NTSC) and decided to go ahead and run that update, figuring that it would fix my corrupt system menu. Since there was a Zelda patched save for 3.3 out at that point, I figured I'd be able to get homebrew installed again and get back to 3.2 once repaired.
The update went through fine, but the system menu is still corrupt. I don't think it repaired the system menu due to the explanation in THIS thread by WiiCrazy. Now the system menu is at 3.3, so I can no longer use homebrew. I went ahead and formatted my Wii as well, but that doesn't fix the corrupt menu issue. However, I still have a working modchip, and can still boot games. I also tried the SaveMii (Gamecube 4-directional controller) method, and can get the Wii to boot into that recovery mode. And I have confirmed I can autoboot discs.
But here's the kicker... I can autoboot Zelda, and I can even save my progress, and reload my save file when I replay the game later. BUT I cannot get into the Wii Save Data or the SD save data because of the "system files corrupt" system menu issue. So although I have the Zelda 3.3 patch gamesave on my SD I cannot get into the menu path to transfer it to my Wii.
So here's where I have questions...
Mainly, any ideas ?!
I believe that Animal Crossing NTSC is the only game out there with the very next newest system firmware update built into the game. Should I try creating an autoboot disc of this game, and boot the Wii in SaveMii recovery mode to automatically load this game + system update? I'm wondering if letting the system update from recovery mode would properly and thoroughly upgrade/repair my system menu, whereas it didn't properly repair last time from standard boot mode.
Even if this upgrades me to 3.4, that won't be a problem IF my system menu gets properly repaired. (Since I can always use the 3.4 Zelda patch to initiate the procedure to downgrade back to 3.2.)
But before I tried that, I wanted some feedback from here, and certainly any other recommendations.
I let my friend play a Shaun White Snowboarding disc that I knew was PAL, but thought for sure was properly region'friid and brick-blocked. Long story short, I wasn't paying attention when it prompted to do a system update and he accepted it. Sheesh that's a lesson learned the hard way ! So I inevitably screwed up big time, and know good and well just how big of a careless mistake that really was. No excuses.
Anyway, my system was semi-bricked, and I started getting the "System Files are Corrupt" message about 75% of the time. I could still boot the Wii normally, get past the A screen, and see all the Channels. I could even get homebrew working still. I could also get past the corrupt message altogether when I booted in maintenance mode. However I couldn't get to some areas of the system menu, and could no longer get it to connect online no matter what settings I changed.
I tried a LOT of troubleshooting. The system menu wads for NTSC (v289) didn't work to fix it. I was getting ready to install Starfire (which would have likely rescued me in the end), however I was distracted when I found a game disc from my NTSC region that had a newer firmware than mine (WiiMusic NTSC) and decided to go ahead and run that update, figuring that it would fix my corrupt system menu. Since there was a Zelda patched save for 3.3 out at that point, I figured I'd be able to get homebrew installed again and get back to 3.2 once repaired.
The update went through fine, but the system menu is still corrupt. I don't think it repaired the system menu due to the explanation in THIS thread by WiiCrazy. Now the system menu is at 3.3, so I can no longer use homebrew. I went ahead and formatted my Wii as well, but that doesn't fix the corrupt menu issue. However, I still have a working modchip, and can still boot games. I also tried the SaveMii (Gamecube 4-directional controller) method, and can get the Wii to boot into that recovery mode. And I have confirmed I can autoboot discs.
But here's the kicker... I can autoboot Zelda, and I can even save my progress, and reload my save file when I replay the game later. BUT I cannot get into the Wii Save Data or the SD save data because of the "system files corrupt" system menu issue. So although I have the Zelda 3.3 patch gamesave on my SD I cannot get into the menu path to transfer it to my Wii.
So here's where I have questions...
Mainly, any ideas ?!
I believe that Animal Crossing NTSC is the only game out there with the very next newest system firmware update built into the game. Should I try creating an autoboot disc of this game, and boot the Wii in SaveMii recovery mode to automatically load this game + system update? I'm wondering if letting the system update from recovery mode would properly and thoroughly upgrade/repair my system menu, whereas it didn't properly repair last time from standard boot mode.
Even if this upgrades me to 3.4, that won't be a problem IF my system menu gets properly repaired. (Since I can always use the 3.4 Zelda patch to initiate the procedure to downgrade back to 3.2.)
But before I tried that, I wanted some feedback from here, and certainly any other recommendations.
