Talk:Homebrew status

FAQ

I'd like to translate this article into German.

The question "Will it allow me to run trainers or backups from SD/(USB-)HDD?" is answered simply with 'No.' Is there any more detail that can be given here? Is it saying that it's impossible and it will never happen, even with this tool's assistance? I figured that things like that WERE technically possible, and that this hack or one like it is exactly how someone would install that kind of tool for the first time.

• The answer 'no' is all you'll get here. The people here interested in homebrew, are not interested in helping you steal games from the internet, or cheat in multiplayer. You'll have to find someone else who cares, sorry. Anonymous 17:21, 12 February 2008 (PST)
  • The Wii already has ways to ""steal games from the internet"". You're not striking a back against people who copy games by being pissy about ISO loaders and trainers on a wiki talk page. Besides, ISO loaders are homebrew (and they load homebrew), so homebrew enthusiasts are interested in them, and putting something fraudulent (or at best ambiguous) into a FAQ because you're angry isn't going to solve anything.
    • "ISO Loader" usually refers to loading R0Mz. Anyway the question specifically says trainers or backups. 142.59.172.116 15:00, 13 February 2008 (PST)
      • I'm going to replace "and it never will" with "that's not the objective at least". It's a more neutral stance and most seem to see it as possible in the future.Taboo Tongue 22:26, 18 February 2008 (PST)
        • This isn't Wikipedia -- we don't have an NPOV mandate, and as one of the authors, I can stipulate that our loader will never do that. Bushing 01:20, 19 February 2008 (PST)
          • I fully understand the general dislike for "backups" and cheating on the homebrew scene, and I myself am just as opposed to this kind of stuff as anyone, but I still find it a little immature to try to make a point on an otherwise open and informative page by intentionally being vague and evasive. In general, one word answers should never be an acceptable response to any technical question. If you want to make it clear that you don't support such unethical activities, then by all means say just that. But you should not confuse others who are just trying to understand how this all works with your "I hate you, go die!" attitude. A better explanation would be similar to this: "While progress in homebrew development may eventually lead to programs being written that would allow the unauthorized loading of copyrighted content or unfair competition in online play, finding a way to do so will never be one of the goals of this community." PunMaster 14:14, 30 March 2008 (CST)

Also I'd like to suggest more FAQ items such as:

• Is there a known exploit that can be developed to turn off the security checks? (so that this exploit doesn't need to be used every time you want to run homebrew)
• How much access to the Wii functionality does this give us? (Is it cracked wide open? Can we access all peripherals, install a custom main menu by flashing the NAND, etc? Or are there more layers of security yet to crack?)
• Can Nintendo patch this exploit in future firmware releases? (We can explain that we can use this hack to dump the memory of other Wiis, and extract their private key w/ nintendo signature, so now that pandora's box is openened there's no way for the Wii firmware to tell what saves are fabricated, without playing key revokation whack-a-mole. Although, are there other ways to plug these holes? Can Wii firmware dynamically patch security flaws contained within game discs? Also, is it possible that they may just put an end to loading game saves created on other Wiis? Not likely, but technically possible. And obviously future re-releases of Twilight Princess are not going to be quite so hackable.)
  • I don't see why they couldn't soft-patch the games, but depending on the way they're designed, it may not be easy. If the game is calling some routine loaded from firmware to read files from the SD card, then they should be able to add a check to that routine that blocks access to files containing the exploit. Or if they're using such a routine for disc access, that routine could patch the vulnerable executable when it gets loaded. If neither of those is the case then they'd have to patch the initial executable that gets loaded from the disc at boot-time to do these things. If the DS is any indication, Nintendo doesn't seem to like resorting to such low-level hacks. Supposedly online DS games download and run some signed code (mainly for piracy checking) when they connect, which could easily be used to patch a few crash bugs, but they haven't done so.
  • Also, I wouldn't be surprised if a program is released very soon that displays your console's key on the screen. The key should be in memory already, and they clearly have no trouble displaying things on the screen at this point. I'm not quite up on how the encryption works, but I imagine Nintendo could revoke or blacklist the key they extracted, making future firmwares reject files that use it. Having your own key in advance so that you could re-encrypt the file would prevent this.142.59.172.116 01:49, 13 February 2008 (PST)
    • If they blacklist one key, all we have to do is get another key and sign it with. It's easier for the homebrew community to get new keys (every Wii has one!) than it is for Nintendo to blacklist it whenever a new exploited save comes out.

Also on a more general topic of homebrew status (Not specifically related to the twilight hack):

• From what we've recently learned about the Wii, is it possible to unbrick a Wii that will not boot? (I think flash is signed with a key that's specific to your Wii somehow? I don't know the details on this, but I'd like to!)
  • No, the Wii will have to boot in order to run the TP exploit. The TP exploit could possibly be used to extract a key to decrypt the flash and re-encrypt it with working data (of course, that would require you to take the flash memory out of the Wii, and put it in an external reader/writer)

Boom Blox Update - No Problems with the EU Version

Have anyone, anyother experience with the patch. Or does anyone know what have been patched?

MadWorld problems

I don't know too much about this, but when you boot-up MadWorld for the first time there is a small mandatory update. Now I can't boot the game with GeckoOS nor Ocarina. Other games still work, but not MadWorld. Also, I could not get the Wiird GUI to work with Pikmin.--FUNKAMATIC ~talk 01:00, 12 March 2009 (UTC)

Gamecube Homebrew

"3.2 obviously being the best (unless you want gamecube homebrew, in which case less than 3.0 is advised)."

Are there not apps that let you run Gamecube homebrew on any version? .Hyper//Hacker 22:39, 4 May 2009 (UTC)

redundant

do we really need both of these sections? Homebrew status#Compatibility Homebrew status#Updates that affect homebrew -- Bushing 07:56, 15 August 2009 (UTC)

LetterBomb

LetterBomb needs added —Preceding unsigned comment added by PCFreak2 (talk • contribs) 12:04, 17 September 2011 (CEST)