Shuny said:
So I would like to know, how a semi brick is supposed to full brick the Wii ? That's something that bother me, if this tool could full brick some Wii, why no one has full bricked it yet ?
If you install a System Menu from the wrong region, you'll either get a semi-brick or a full-brick. Why?
I don't have a complete answer for that question, but I can tell you *how* the full-brick happens. When you turn on your Wii and it loads the menu, before it gets to the "press A" warning screen, it loads your settings from NAND -- specifically, /shared2/sys/SYSCONF, setting.txt, and maybe some others. If it detects that that file is corrupt, it deletes it.
Then, if there's no SYSCONF file there, it tries to regenerate it by putting you through the initial setup again (date, time, console name, etc). When it tries to do that, it can't find the HTML files for the setup code, so you get the Opera error message. Otherwise, you finally get the warning screen.
What we don't understand is why this happens sometimes, and sometimes it doesn't. It doesn't seem to be a simple region-mismatch, or else we would never see half-bricks! However, I've verified that deleting the SYSCONF file will force you to repeat the setup on a normal system, and will brick a semi-bricked system.
I learned this the hard way, when I was trying to help dCiSo unbrick his Wii -- I had him a program that loaded the menu into memory, patched it to fix the paths to the HTML, and run it. The idea was that he could then just go to settings and do a system update.
He hadn't had Internet enabled, so he went to the settings menu and re-enabled it, and then got some error message (maybe about wc24?). He power-cycled the Wii, and it was fully bricked; that puzzled me at the time, but now it's clear.
So ... as long as your settings don't get corrupted, your semi-brick will stay a semi-brick.