Question about update blocker function in chips.
I just purchased the Wasabi DX for my new wii. I've been reading around for a week making sure to answer each question that I could think of before I actually open the wii up. I would really like to have some in depth info about the update blocker function, how it does what it does and what it doesn't do.
So, to my understanding, if you put in an import game that requires an update, the DX will stop that update. But how does it do that? Does it just stop the game from being played at all? Does it skip the update and play the game as if it had been brickblocked?
Here's another question. If you put in an import game which requires you to update your system, yet your system is already up to date with the firmware required by the game, will it not ask you to update at all?
Reworded: If you put in an import game that was made when the current update you have now was the most up to date FW, such as 3.4, then will the game still require you to update, even though you are up to date?
Lastly, to my understanding, these updates from import titles are regular FW updates, so shouldn't having your system completely up to date with the game eliminate the worry of bricking your wii, and completely eliminate the need for these games to update at all? Or are these updates specific to certain games?
1 User Says Thank You joeleoleol For This Useful Post
Can't speek for the Wasabi Dx but for soldered chips if your game has an update that is out of region you will get a black screen. You will see the game but when it is selected it will give you a black screen. Correct me if I am wrong someone but I believe that is what will happen. I always just make sure the back up is of the same region.
Black screen can mean many things but blocking an update usually results in this.
1 User Says Thank You Balaberda For This Useful Post
Thanks for the reply.
After a long while of research and reading in many different sites, I have come to conclusions on many of my issues. I would like to list them here, and IF ANYONE CAN TELL ME IF ANY OF THE FOLLOWING STATEMENTS ARE FALSE, then PLEASE DO SO. Some of these statements are logical guess's that I've come to after putting together a lot of scrambled information. If this doesn't get many answers, then I think I'll post it in a more populated area of the forums. I'm posting it here because I already have a thread here.
Keep in mind my only interest is in playing imports like Fatal Frame 4, Disaster, Fragile, etc... I'm not interested in pirating at all, yet I'll include info about loading backups here just to organize my thoughts.
And here we go...
My wii is brand new, 3.4U, LU650...
-The 4th generation modchips (drivekey, wasabi dx, flatmod) work on any and all drives on the market today.
-These chips allow the wii to play backup disks and some import games. Other imports need to be loaded through other methods, such as GeckoOS.
-Some, NOT ALL, import games have system updates built into the game disk.
Upon booting the import, backup or original, it will promptly ask you to update your system. This UPDATE is a SYSTEM UPDATE. The way it works is it checks your system to see if you have the update installed already. Since it is trying to install an update that is OUT OF YOUR REGION, your wii probably doesn't have that certain update installed already, even if the wii is currently UP TO DATE WITH ALL UPDATES FROM YOUR REGION. So, if an import game wants to install 3.4J (the JAPANESE version of 3.4), and your wii already has 3.4U (the USA version of 3.4), then the game will STILL WANT TO INSTALL THE UPDATE due to the fact that you DO NOT HAVE 3.4J INSTALLED. This means an import game that requires an update is unplayable without bricking your wii, unless you take other measures...
-If an import game doesn't have an update on it, then there's no problems.
-It is perfectly safe to update your wii with an update FROM YOUR REGION. However, in updating past 3.2, you will LOSE much of the functionality and options you have in homebrew.
-Some newer games have updates on the disk that ARE NOT system updates, but are just IOS files that the game needs to install to be able to run. Thus, doing this update will not update your firmware. If you don't want to let the game just update, which you probably shouldn't if it's out of region, then you can install the IOS's and CIOS's (custom IOS) needed through Wad Manager, thus updating the wii without actually updating the firmware. Most only work in 3.2, yet their mostly only needed in 3.2.
If this update is blocked or skipped through means of skipping updates, and the wii doesn't have the necessary IOS files to play the game, it WILL RESULT IN A BLACK SCREEN.
-The wii update blocker function on a modchip functions very similarly to the STARFALL wiibrew program. Thus, if it is set to block updates from other regions, it will detect when an import game, backup or original, is inserted into the drive, and WILL SKIP THE UPDATE CHECK PORTION OF BOOTING THE GAME.
-STARFALL is a wiibrew program that will reformat your system, changing many things such as the background BGM on the wii menu, changing the heath warning when booting, and most importantly, making your wii skip update checks when booting games. BUT, STARFALL WILL ONLY WORK ON 3.2, AND WILL NOT WORK ON 3.4.
-TRUCHA SIGNED BACKUPS, (AKA iso files that have been modified such as changing their region with wiigeonfree, or removing the update portion of the disk with wiibrickblocker) CANNOT be played on ANY system 3.3 or higher, including 3.4, due to the trucha sign fix included in those updates.
-The wiibrew program GeckoOS can be used to load original import games that normally WOULD NOT be able to load in the disk channel. This program DOES WORK in 3.4, and can be installed via Homebrew Channel, or simply installing the GeckoOS channel via Twilight Hack, which DOES work in 3.4. This program WILL SKIP THE UPDATE STEP WHEN BOOTING THE IMPORT GAMES.
-HOWEVER, BACKUPS CANNOT BE LOADED IN GeckoOS, unless a mod chip is installed. The dvd drive has the job of checking if the game is an original copy or not, thus if the mod chip overrides this function, GeckoOS will believe that the import inserted IS AN ORIGINAL DISK, and it will load, SKIPPING THE UPDATE CHECK. ANY VERSION of GeckoOS WILL run backups WHEN A MODCHIP IS INSTALLED.
Source: http://www.gbatemp.net/index.php?showtopic=139163 (Wiipower's comment)
-Another great thing about GeckoOS, IT CAN LOAD TRUCHA SIGNED GAMES ON 3.3 AND UP SYSTEMS.
-Gamma 03 is a backup loader that ONLY WORKS IN 3.2.
-GeckoOS 1.6 Backup Loader combines GeckoOS functionalities with a backup loader. Thus you DON'T need a modchip to run backups in GeckoOS
Not sure if it works in 3.4.
-Wiigator can be run on 3.4 after you install IOS16-64-v257-prod.wad and cIOS249r7.wad through use of Wad Manager, yet this is NO LONGER POSSIBLE on systems with serial number LU64... and up.
-The newest wiis, serial code LU64... and up, no longer allow the Wad Manager to work due to a change in the boot2 portion of the wii, thus IT IS IMPOSSIBLE, as of now, TO DOWNGRADE FROM 3.4 TO 3.2 on these new wiis.
Last edited by joeleoleol; 06-03-2009 at 07:50 PM.
2 Users Say Thank You to joeleoleol For This Useful Post
I guess the complete lack of any replies gives me reason to believe that all this info is correct...
Joe, I think you're pretty much correct with everything you've said, and also you've inadvertently created a document that would probably answer a lot of people's questions about Wii hacking.
I have a Wasabi Zero and the update blocker works pretty similarly to BrickBlocker; I can't vouch for Starfall as I have never used it. If the game includes an update and it's not actually needed by your system the game will play without a black screen. There are a few games that require cIOS to be installed on 3.2U to compensate for this, like Mad World and Animal Crossing.
The only reason I have ever had to patch an ISO before burning when playing with the Zero is because it was PAL formatted. RegionFrii takes care of this.
1 User Says Thank You botulismo For This Useful Post
Thanks for the reply man, I'm happy to see some life here. =D
Originally Posted by botulismo
I have the Wasabi DX on my desk right now, I just want to know for sure that I understand everything that will happen before I put it in the wii, I don't want any surprises... Your reply helps A LOT.
I'll update the list a little more, and maybe if a few more people tell me that it's all correct, then I'll post it in the tutorials.
Last edited by joeleoleol; 04-17-2009 at 11:58 PM.
Sorry it's taken a while to reply, I don't check Wiihacks daily. Since it's been a couple of weeks, how has the DX worked out for you? Have you installed it?
I don't think (if you haven't yet installed the chip) that the DX should give you any unwanted surprises as long as it's a good chip (this seems to be the cause of most people's errors with any modchip), and Wasabi generally has pretty solid build quality on their chips so I wouldn't worry about that.
Hey, Joeleoleol here. I'll probably get banned for making a new account after Modderman suspended me for asking detailed, thoughtful, and specific questions that appear nowhere else on the forums (and if they do then they are horribly written and confuse a new hacker even further), but I'll do it anyway.
Anyway, I did install the Wasabi DX, turned out great. Installation went perfectly, but it won't load original imports. So, I just started up the Twilight Hack and got the homebrew channel running, then ran up some GeckoOS and Fatal Frame 4 loads beautifully! So basically I didn't need the chip... =D but thats alright. Thx for the help butulismo.
Homebrew is freaking neato if I may say so =D, and Fatal Frame is scarier than balls.
@ chucky... Now that finals are over, yes, I do have some time on my hands. =D
Last edited by mapleler; 06-03-2009 at 07:45 PM.
1 User Says Thank You mapleler For This Useful Post