So I've searched seemingly endlessly to see if someone else had encountered this problem, and, it seems people have had similar issues, but none of the fixes they used seem to work for me.
Background: Friend installed HBC initially over a year ago. Didn't use it that often, eventually (stupidly) updated from Nintendo (to 4.1u, I think) so I could play Mario Bros./Sports Resort/Mario Galaxy 2. So that removed HBC, and I figured I was A-OK. A few months later, I was getting the "Health and Safety Screen" brick... managed to get around it consistently with Maintenance mode, which was adequate until the system menu started freezing up a few seconds after boot (most times).
Since I didn't understand anything about wii-hacking at the time, I thought maybe the newest update from Nintendo would solve the problem. Hence I ended up with 4.3u, and at this point probably 75% of the time can boot to system menu with maintenance mode. Then I started seeing issues with the Netflix channel, hanging when using search function, shows/movies not showing up on the queue.
So at this point I was thinking, I need to figure out what's the issue and either fix it or "virginize" the wii.
Things I've tried:
**After the update to 4.3u, tried formatting the system memory through the wii settings menu, but each time it just would hang (frozen hand-cursor) as soon as I initiated the format. It must not have even started, because nothing was any different upon reboot.
**Ran through Mauifrog's softmod any wii guide (several times) since I was running 4.3u SM. Was able to get bootmii installed as boot2, made a NAND backup, priiloader installed, ios updated etc.
**Tried det1re's Mailbox fix several times, no effect.
**Tried NAND formatter MANY times, both pre-mauifrog's guide and post-mauifrog's guide (i.e. immediately after restoring to initial 4.3u SM and after mauifrog's guide on 4.1u SM). I made my custom setting.txt file successfully and had it read it from the SD and not the NAND. Thing is, it always hangs installing one of the wads. Usually the first one (ios17 or ios31), but sometimes it makes it to the "RVL" wads and hangs on one of those instead. Each time this fails, I have a more severe brick where I can't even get the health and safety screen. I can still get into bootmii to do a NAND restore from my backup, and I'm back where I started (although one time, I had trouble even getting into bootmii... only able to after several tries).
Oh and one time I went outside for ten minutes while the formatter was running, came back and the screen was black so I assumed it had finished successfully and shut down, but when I booted the wii it was still bricked. Since I haven't actually seen it run all the way through, anyone know how long it's supposed to take in general?
Also I should add that when I do a NAND restore through bootmii, it shows many many "unprocessed blocks" (no "bad blocks" though)... sometimes even as many as 50%... Not sure what the difference between unprocessed and bad is, or if this just means that the formatting didn't change much and bootmii "knows" this and only replaces the missing/altered blocks.
**Tried different SD cards (sandisk 2gig, sandisk 128mb) formatted in FAT and FAT32
**Tried re-downloading NAND formatter package (with the wads).
**Tried putting the wad folder on the SD card separately and first. Even tried putting the wads themselves on one by one.
** I'm on a Mac, so I installed "blueharvest" which is program to prevent the OSX from putting these extra "hidden" "fork" files on the FAT-formatted cards. (i.e. the SD card looks exactly like it's supposed to based on the guide). Also installed checksum program for the Mac and confirmed checksums all ok (as it says to do in mauifrog's guide).
So it would seem to be a banner brick or mailbox brick, in that it boots into maintenance mode usually (although, weirdly, never have seen the "system files corrupt" message), right? I know that this means I'm supposed to try to remove the offending wad file(s), the problem is, I have no idea which wad might've bricked it (also hadn't been installing any wads initially... all the problems started once I did the initial update from Nintendo). Also, I didn't try to install any wads/channels other than the ios wads as part of the various steps in mauifrog's guide. And I would assume going through mauifrog's guide would overwrite any bad wads anyway, is that correct?
Also, it looks like wiiconnect24 is ON, and I can't turn it off even in wii settings menu because it's not accessible in maintenance mode. I thought perhaps the "ignore standby" priiloader hack would work, but it didn't seem to make a difference (and the orange light would be on half the time when wii is shut down).
Basically nothing I do seems to get rid of the health+safety screen issue. I can usually get into the system menu with maintenance mode, but the wii is unstable in general, lots of issues with the netflix channel not loading or freezing... can't go "back" to the system menu once I'm in a channel without it hanging. Sometimes it won't boot up for several days at all and then suddenly will work.... After mauifrog's guide, it seemed to be a bit more stable (but still only able to boot with maintenance mode), except that I turned it off and then in the morning it was bricked to the point of no health and safety screen.
All very annoying-- so my goal at this point is trying to get the wii back to factory-state, and/or fix it if possible. I'd be fine with either result.
Apologies for the length of the post, I wanted to be as thorough as possible in terms of anticipating questions I might be asked.
So does anyone have any ideas?? I suspect I've just overlooked something, but perhaps it could be a hardware issue? Thanks in advance for your help.
Also- Here is my syscheck report (post-following-mauifrog's-softmod-any-wii-guide):
sysCheck v2.1.0b7 by Double_A
...runs on IOS58 (rev 6176).
System Menu 4.0/4.1U (v54449)
Homebrew Channel 1.0.8 running on IOS58
Console ID: 33893640
Found 115 titles.
Found 51 IOS on this console. 5 of them are stub.
IOS4 (rev 65280): Stub
IOS9 (rev 54321): Trucha Bug
IOS10 (rev 768): Stub
IOS11 (rev 54321): Trucha Bug
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 54321): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS17 (rev 1032): No Patches
IOS20 (rev 54321): Trucha Bug
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 54321): Trucha Bug
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 54321): Trucha Bug
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 54321): Trucha Bug
IOS61 (rev 5662): No Patches
IOS70 (rev 54321): Trucha Bug
IOS80 (rev 54321): Trucha Bug
IOS90 (rev 54321): Trucha Bug
IOS202 (rev 65535): Trucha Bug, NAND Access, USB 2.0
IOS222 (rev 65535): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223 (rev 65535): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224 (rev 65535): Trucha Bug, NAND Access, USB 2.0
IOS236 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS247 (rev 65535): Trucha Bug, NAND Access, USB 2.0
IOS248 (rev 65535): Trucha Bug, NAND Access, USB 2.0
IOS249 (rev 17): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS250 (rev 65535): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
Report generated on 2011/05/09.