I guess if you already have 3.1E firmware the update wont do nothing
Actually it will, game updates like this that don't seem to change the version number of the wii's firmware actually perform small updates.
Games such as boogie included support for microphones and metroid prime 3 also had a small update for something I don't know.
But this is most like to be the reason these games crash with wiibrickblocker. The update starts and adds some file updates to the wii's firmware and then resets. When the game tries to run now it can read the new files in the firmware and continue.
If you skip the firmware update it will try and look for the changed firmware, not find what it's looking for and simply crash. The reason it normally hardlocks is probably because the programmers have not coded in any sort of error message for not having the correct formware as you shouldn't be able to play without updating the firmware in the first place. So it just gets confused and hardlocks.
Hope this helps some.
I will surely buy it. I'm just trying to play it a month before it's outSome people shall just try to, hm, buy the game ? Let's say just to know how it feels like, as complaining about never be able to play SMG JUST because there's a supposed copy protection :/...
And this one deserves it, can't wait for the PAL release.
Hope this helps some.
Try to check your Wii config plz.
Mine goes to an Opera page.![]()
I have just un-rar this ware and use Brick Blocker....
I have a Pal Wii with Wii-key installed....
When I put in SMG it comes up with SUper Mario Galaxy picture and you here Mario says "Super Mario Galxy".......
You press "A" to continue and the screen goes black and the drive locks up....
So if you are a hacker all you check for is where the drive locks up and you by-pass that for it to continue to boot up.....And I think this will definately work on PAL since I got boot screen to come on.....
I wonder if it's what I speculated a while back as a method for defeating modchips, false positives. The disc may fire off an authentication for the disc that's supposed to fail but with modchips it comes back as OK. I'm very interested to see what develops from this.
I wonder if it's what I speculated a while back as a method for defeating modchips, false positives. The disc may fire off an authentication for the disc that's supposed to fail but with modchips it comes back as OK. I'm very interested to see what develops from this.
That seems like a very smart idea.
Just insert the disc id's that have the false positives in the firmware (the reguarly update anyway so in eacht .x version you can add a minor "fix" and add new id's. This will keep modchip builders bussy if you would do this at random, and there is virtually no way of knowing witch disc has it until it fails! Keeps m from automizing the process.
very interesting theory, but i don't see how it could work. i mean what kind of authentication request would the console ignore but the chip pick up?I wonder if it's what I speculated a while back as a method for defeating modchips, false positives. The disc may fire off an authentication for the disc that's supposed to fail but with modchips it comes back as OK. I'm very interested to see what develops from this.
perhaps something like region code authentication.I wonder if it's what I speculated a while back as a method for defeating modchips, false positives. The disc may fire off an authentication for the disc that's supposed to fail but with modchips it comes back as OK. I'm very interested to see what develops from this.
very interesting theory, but i don't see how it could work. i mean what kind of authentication request would the console ignore but the chip pick up?
once again, can't be a modchip detection since the original copies seem to run fine on modded wii systemsI think it's either a new support check, and they have started using new supports that aren't compatible with standard DVDs, or they have put in code to detect modchips by seeing if RAM is modified in real-time by a modchip on the support check.