Notes from inside your Wii

HackMii header image 2

3.4 and recent updates

November 19th, 2008 by marcan · 61 Comments

Nintendo released a recent update that once again tries to secure some existing bugs on the console, breaks some things, deletes others. This time they’ve also gone around and modified the TOS. As usual, mass panic ensues.

The people who are panicking can be divided roughly into two groups (non exclusive):

  • The pirates
  • The clueless

This should go without saying, but we don’t want to have anything to do with the former group. Nintendo is obviously going to fight piracy (and that’s going to hurt homebrew). We’ll have to deal with the homebrew part, but don’t expect that to help piracy in any way. It may, or it may not. And if it doesn’t, pirates will have to deal with fighting nintendo themselves. The usual messages about WADs, “backups”, and all that crap are going straight to /dev/null, and we’re seeing quite a few bans due to piracy on #wiidev recently. Don’t ask us about it, don’t talk to us about it.

The clueless are panicking because, well, that’s the thing to do (OMG, new update! What will we do!). Read the Wiibrew page about the update. To clarify some things: the Twilight Hack is gone and probably won’t be coming back. There are other game exploits on the table (which haven’t been announced yet). Given the ability to run PPC code, we can install stuff and exploit IOS, as the HBC beta9 installer already shows. In short, homebrew isn’t going to go away. We can “do anything” right now. But we do need to figure out what to do.

All we’re concerned with is the ability to run homebrew (from-scratch programs), not necessarily modify the existing system. This means that we’re not necessarily concerned with getting things like menuloader and DVDX working again. Menuloader involves hacking the system menu – which is pointless if it can be replaced. DVDX enables DVD use – which is pointless if there are other ways or you use an entirely new IOS. We’re also not big fans about installable stuff – the utopian homebrew ecosystem would be contained entirely on removable storage and involve zero changes to NAND (implausible, but hey). Either way, the ultimate goal is to have homebrew that is able to use the Wii’s features, period. How that is accomplished is irrelevant, so old methods of doing things aren’t necessarily going to work in the future, nor do we care about it (we’ll find alternatives if necessary).

You may be wondering what it is that we’re doing anyway. Basically, we’re looking at the current situation, moving on with existing projects, and trying to figure out what the best course for the future will be. Quickly releasing hacks as soon as they’re available might not be such a good idea for the future – it’s best if we think it through a bit. We’ve also got tons of stuff to do. Prognosis is good, and hacks will come out eventually, but you’ll have to wait it out. And you shouldn’t expect anything in particular. Remember, it’s about the end result (homebrew), not about how we get there. Also, don’t take some ideas that we’ve thrown out there previously as definitive – we’re rethinking things right now.

In short, calm the hell down and just wait. Don’t update if you don’t feel like “change” – you’ve got that option so far. And if you’ve updated, my suggestion is that you wait. Avoid hacky workarounds – they can be worse than the problems they purport to fix.

Tags: Wii

61 responses so far ↓

  • 1 HyperHacker // Nov 19, 2008 at 11:09 pm

    “the utopian homebrew ecosystem would be contained entirely on removable storage and involve zero changes to NAND (implausible, but hey). Either way, the ultimate goal is to have homebrew that is able to use the Wii’s features, period.”

    That’s not everyone’s goal. I’m more interested in hacks like BootMii and Starfall to tweak the way the system works, e.g. removing silly things like region coding and save file copy restrictions.

  • 2 marcan // Nov 19, 2008 at 11:28 pm

    But that’s our goal. Things are a lot easier to manage if you don’t have to hack into the existing system in every way, considering you have to deal with updates (if you didn’t everything would be a lot easier).

    I’m not saying there’s anything wrong with doing it, I’m saying that we’re not insterested in getting into a mess doing those things.

  • 3 senorclean // Nov 19, 2008 at 11:34 pm

    Thanks for the update marcan.

    Independent bootpaths for homebrew and ‘vanilla’ / as intended functions sound like a cool idea to me. I could see this panning out as homebrew card, rather than homebrew channel – and just bootmii to choose which direction to go in.

    I’m sure you guys know what you’re doing… all the best with your journey.

  • 4 magu // Nov 19, 2008 at 11:42 pm

    In that case I assume that in the future it could be possible having BootMii running something that would for example dynamically apply the patches in Menu Loader or similar. Thus doing patching not explicitly bound to a particular version of system menu on the fly.

    Am I correct in that assumption? As I’ve interpreted your old BootMii YouTube teaser, it looks for a particularly named binary on the SD and runs it if found.

  • 5 Hugh Isaacs II // Nov 19, 2008 at 11:45 pm

    I don’t know if this would require modifying the system or not (I agree that having to hack the system is a messy way to do it)

    but one idea I have is to design the Homebrew Channel with homebrew compatibility in mind designing your own modules that can be called by developers (such as a Homebrew specific Home Menu that only appears when using an app that runs from the Homebrew Channel) this would be useful in combating ISO loaders and the like yourself since every bit of code would have to go through the Homebrew Channel.

    The only problem with this idea is it would probably require more work than the existing design and as hacking goes, it’s bound to be broken in some way.

  • 6 rykin // Nov 19, 2008 at 11:46 pm

    I’m glad to see that current projects are still moving forward and not being pushed aside to fix the minor problems with 3.4.

    I’m not sure how many tricks the Team has up their sleeves; but to me, the logical progression of things is like this:
    Finish BootMii(Especially since it will probably have features preventing users from upgrading to a new menu that breaks homebrew).
    Save Future Exploits for installing BootMii.

    The reports of what 3.4 does is rather mixed, but as I understand it the HBC remains, so most users of homebrew have no worries. I think the panic started when some users posted “OMG! It deletes the HBC!” which appears to be unture.

  • 7 a // Nov 20, 2008 at 1:02 am

    Thanks for the update on this! I have a small question about this Wiimpersonator log…


    There appears to have been an error with the writing of this log, and it only shows IOS10 as being removed. I’m just curious, but what were the other two titles that were removed with this update?

  • 8 w11h4x0r // Nov 20, 2008 at 1:39 am

    giving up on the twilight hack huh?
    oh well, at least maybe now we can see that wii sports exploit i know you must have… :>
    come on, why force people to buy a game when they can use the one that came with the console?

    i guess it’s good that you waited to help future wii owners, but i don’t think nintendo can stop piracy or homebrew on current (and probably most future) wiis, try as they might.

    i would love to see a release of bootmii, at least for unbricking purposes if nothing else. i imagine some noobs could brick their wii by deleting ios50 after upgrading to 3.4, since there’s no check for it in current versions of anytitle deleter. besides, if the ios can also be loaded from sd card, aren’t the contents of the nand insignificant?
    of course, saving game exploits won’t mean anything once the bug used to install hbc beta 9 is fixed (could already be fixed as of ios50, only you/those who have an alternate way of launching the tp hack or other hack may know).

    i think the wii development scene still has a lot of growth ahead.

  • 9 cr08 // Nov 20, 2008 at 2:53 am

    Actually if I recall, the whole idea for Bootmii was not to keep system updates from happening, but keeping a hook permanently in the system to boot into, say, the HBC (or any other app if so desired) without having to worry about homebrew blocking code in the system updates. This not only accomplishes the homebrew goal for the team, but also blocks a few paths for pirates by, at least in a direct manner, keeping the updates untouched.

    Granted though, the pirates are just as crafty and will find their own way around it all with the help of Bootmii. But that’s already been a given thus far. One of those sad consequences of trying to to implement the use of homebrew on any commercial console: Your work eventually gets linked to pirating whether you like that or not.

  • 10 bugger // Nov 20, 2008 at 6:23 am

    Not to rain on your parade fellas, but Nintendo IS after homebrew with these updates. Look at what they target. The Twilight Princess hack. Why? That’s the gateway to running homebrew code on a non-modified system. Get rid of that and you cut off the infusion of new homebrew capable systems. Now, I know you think this is merely because of piracy, but let me give you this point. Nintendo is a company. Companies make money. Nintendo makes money by selling licenses to companies who make software for their system. Homebrew makers have purchased no such license. Thus, Nintendo is not making money off of homebrew software. So, what does that mean? Correct, Nintendo sees homebrew in the same light as piracy. Both cost them money. So please try to remember that next time you get on your pedestal and talk about the nasty pirates. Because to Nintendo, you are one.

  • 11 marcan // Nov 20, 2008 at 7:27 am

    Some of our ideas are similar to what you propose :)

    None, apparently. Something went wrong with that run of wiimpersonator, but the subsequent one didn’t show any removed titles. Note that removed here doesn’t mean it gets deleted – it means it’s not part of the update. In other words, it would mean that a title that was part of a previous update is no longer in a current update (it got removed from the update rotation) – not that it’s going to get deleted.

    My guess is that Nintendo was in the middle of setting up the update as wiimpersonator caught it, something went wrong. The next run shows what really happened. I ran a separate instance locally and it shows no titles removed since Oct 23.

    No wii sports exploit in sight. And yes, we did try. Sorry.

    blah blah blah. Nintendo isn’t going after homebrew because it costs them money in lost licensing fees. If homebrew didn’t exist then 99.9% of homebrew apps just wouldn’t exist – it’s not like we’d go ahead and be come official devs. It costs nintendo more money to stop homebrew than they gain from it. As opposed to piracy – nintendo doesn’t lose a sale for every pirated copy, but for an important fraction of them, they do.

    Piracy is most of the reason. They’re going after homebrew because it enables piracy. Nintendo sees homebrew in the same light of piracy because it’s equivalent to it – stop homebrew or stop piracy (via homebrew), both stop piracy. We’re the foundation for the pirates, and Nintendo is just as happy about demolishing any part of the building as long as the top falls down.

  • 12 I Twiizers circa l’aggiornameto del 19 Novembre ( 3.4 ) « Wii’s Temple - Tempio Dell’Hacking Wii. // Nov 20, 2008 at 7:45 am

    […] Notizia: http://hackmii.com/2008/11/34-and-recent-updates/ […]

  • 13 aguamelon // Nov 20, 2008 at 8:41 am

    We need Bootmii NOW to get rid off those updates or they will eventually terminate homebrew

  • 14 emailtoid.net/i/69fad7a4/ // Nov 20, 2008 at 9:33 am

    Thanks for commenting on it Maracan. I’m glad to hear that BootMii will probably implement some things like region free channels. Only reason I’ve not updated is because I need region free channel hacks to play a game I purchased from the Japanese Shop Channel. Well, plus I want to keep my options open. ^_^

  • 15 Auch Team Twiizers rät erstmals abzuwarten - Beitrag - Wii Will Rock You! // Nov 20, 2008 at 10:05 am

    […] Update 3.4 nicht zu installieren. Heute hat sich auch das Team Twiizers zu Wort gemeldet und ein Statement zur neuen Firmware Version […]

  • 16 Dykam // Nov 20, 2008 at 11:52 am

    So you try to get as much as possible with less possible ‘damage’ to the Wii…

    Will be nice to see how close you did get to your target.

  • 17 whodares // Nov 20, 2008 at 12:04 pm

    Mortal Kombat: Armageddon has to be one, it has plenty of text entry sections that might be susceptable to buffer overflows :-)

  • 18 Kyo // Nov 20, 2008 at 1:23 pm

    The only reason nintendo would have to go after homebrew if it wasn’t for piracy would be emulation. (As it might hurt virtual console sales)
    But I doubt that’s enough motivation for them to block it. Obviously piracy is what caused them to start doing more to block homebrew. And I’m not just talking about the various backup loaders here either, I bet pirated VC and WiiWare wads are part of the reason too.

    Either way, it’s out there and now homebrew is going to be more painful. Personally, I haven’t updated my system from 3.2 yet, I have no reason to. Let’s hope you guys come up with something clever as usually and everything will be good.

  • 19 Marcan Confident About Cracking 3.4 Update | NES Hacks // Nov 20, 2008 at 2:26 pm

    […] Source […]

  • 20 wowfunhappy // Nov 20, 2008 at 2:39 pm

    I understand not wanting to spend time trying to make old meathods work- there’s no point if the end product is the same. But… ARE you working on a way to make DVD’s work again? I don’t care how, I don’t care when, but is it being worked on?

    Several of my friends have installed the update and now can no longer use the Wii as a DVD player, which is a problem for them.

  • 21 Wii Update 3.4 Kills Homebrew... Again... - Page 9 - The Nintendo WiFi Community // Nov 20, 2008 at 2:43 pm

    […] Wii Update 3.4 Kills Homebrew… Again… – 1 Minute Ago 3.4 and recent updates if you have any questions about the new update read this or go to wiibrew.org […]

  • 22 jimi // Nov 20, 2008 at 2:46 pm

    please only run signed software via bootmii. perhaps give out sigs for trustworthy developers and sign other software individually. this sounds like much work, but homebrew on wii is not that big. include blacklist as well, if morons sign piracy software. everything else will mean piracy on bootmii and this means that ninty will not leave it alone.

  • 23 jairolas // Nov 20, 2008 at 2:52 pm

    Well, let’s forget about Wii Sports, but… what about super smash bros brawl?!

  • 24 Seth Merkley // Nov 20, 2008 at 3:21 pm

    I think marcan’s right about the licensing thing, if Nintendo cared that much then they would go after the people hacking up the wiimote for use with PC’s.
    Also you have to realize that what many people regard as simply homebrew is piracy. Mainly emulators, which directly take away from Nintendo’s virtual console sales. Since people call it homebrew, and Nintendo sees what it is – piracy – they then regard all homebrew as bad.

  • 25 mbayrakdar // Nov 20, 2008 at 3:33 pm

    I bought my wii on nov 18th, hooked it up internet and the system asked me to update it. Yeah why not?The next day I went to a Blockbuster store and rent a Zelda cd and tried to copy the file to the console.No luck! Now I realized that 3.4 does not allow you to copy the file from your sd to the console. What a luck!

  • 26 chungy // Nov 20, 2008 at 3:49 pm

    I was just thinking, has the team been entertaining an idea I said in an earlier comment (http://hackmii.com/2008/10/the-homebrew-channel-beta9/#comment-3294), about using BootMii to essentially downgrade the IOSes/System Menu?

    Of course the current updates won’t be any problem (BootMii obviously will install with it…), but in the case of future updates that hypothetically could delete HBC and prevent new installation, if BootMii is not overwritten (which afaik is not a guarantee), I could imagine using a game disc to downgrade to System Menu 3.4 or lower (or whatever the latest “safe” version is at that hypothetical time). As I mentioned in my other comment, it’s a risky operation, but it might be a nice precaution to think about.

  • 27 bootlegger // Nov 20, 2008 at 5:48 pm

    Thought i should chuck my 2 cents worth in

    we all know companies like microsoft, sony and nintendo produce their hardware at a loss and expect to get back their money from royalties via software houses, but look at it this way – if i couldnt hack a console in someway for homebrew capability, i would not be interested in it and wouldnt buy it.
    Because it is hackable in some way this means that as i have bought one, occasionanly i will buy the odd game that interests me and other people will buy me new hardware/software as presents and as this device is in a household it then also becomes utilised by other people who also buy software for it – so because it is hackable nintendo have still made money from me/my family that they would otherwise not have had. The same has applied to my PS2. My Nintendo DS and XBox this hasnt applied to because I only bought these items broken and on the cheap and repaired them. The DS is used as an MP3 player and homebrew system (like my GBA before that) and the XBox used purely for XBMC. Neither nintendo or microsoft lost money here as the hardware was faulty and was going to be disposed of anyway and I would have not bought them for full price as i am not a games player – i only want them to experiment with. The Xbox 360 is a step in the right direction with its development ability however not completely there yet.
    I suspect you dont do programming and dont understand the buzz you can get from programming on such a device that was not intended to be programmable. I can only dream of what marcan and co achieve on the Wii and much cudos to them for what they have achieved so far.

    Keep up the excellent work – look forward to you next release(s).

  • 28 Nighttro // Nov 20, 2008 at 6:48 pm

    ” the utopian homebrew ecosystem would be contained entirely on removable storage and involve zero changes to NAND (implausible, but hey). ” This quote really got me thinking of the possibility of having bootmii load off a usb mass storage device ala Nintendo Wii’s found in Hospitals.

  • 29 nightwatch // Nov 20, 2008 at 9:18 pm

    Have you considered using some kind of code obfuscator to slow Nintendo down and prolong the lifespan of each game hack? All you really have to obfuscate is the core exploit code. Normally such tools do little in the end against hackers skilled in reverse engineering, but Nintendo engineers might have a different skill set.

  • 30 modrobert // Nov 20, 2008 at 9:49 pm

    If you live to get old enough you will most likely realize that there is a difference between “control” and the “illusion of control”.

  • 31 Isaac356 // Nov 20, 2008 at 11:04 pm

    As far as game exploits go, you should definatly try to find something in Brawl. There are plenty of ways to crash it with modified stages/replays, and if you can run code from that, it will be the master of all exploits (think pandora). Unlike the Twilight Hack, a save file does not need to go through the Wii Menu before it can be used. Therefore, the only way to patch the exploit is a new version of the game, but so many people have it already, it would be pointless.

    As always, correct me if I’m wrong. :)

  • 32 morph // Nov 21, 2008 at 4:23 am

    Is supervisor/user mode still present in the ppc?

    (Crazy idea: resident piece of the HBC in supervisor mode -> launches homebrew app in user mode and traps privileged operations/IOS calls/etc.)

  • 33 marcan // Nov 21, 2008 at 4:54 am

    Yes, DVDs will make a comeback one way or another. Maybe even with a better player.

    That would be going Nintendo’s way. We’re not going to go spend all the effort in creating a “secure platform”. It would get cracked anyway.

    @jairolas, Isaac356:
    SSBB is definitely a suspect, but we don’t currently have an exploit for it (although one might be found).

    It’s much better if we can get stuff to work with current updates. Old versions only last so long after all.

    Nintendo does NOT produce the Wii at a loss. They actually make a nice profit off of every Wii used exclusively for homebrew. That’s why it’s even more pointless for them to go after non-piracy homebrew (unlike Microsoft or Sony).

    You’ll always require an SD card with BootMii (USB mass storage is too complicated to be worth implementing), but subsequently loaded software could be loaded from USB in the future.

    We already are obfuscating code. Try reverse engineering the exploit used to install HBC beta9. Though Nintendo will probably find it, with their SDKs and hardware debuggers. We were more concerned about pirates using it to install WADs.

    It’s an off-the-shelf PPC. We’ve considered ideas similar to that :)

  • 34 chuckthetekkie // Nov 21, 2008 at 6:23 am

    As I understand it, the reason that Nintendo can make a profit on the Wii console is because the technology behind the hardware is nothing new. Unlike the PS3 and Xbox 360 where lots of the hardware are custom and created specifically for that console and some of it was new technology and was more expensive to make.

    Correct me if I’m wrong.

  • 35 marcan // Nov 21, 2008 at 1:49 pm

    Sure. The Hollywood chip is custom but its innards are mostly off the shelf. And the technology is cheap and high-yield. As you go up in price, you hit diminishing returns in performance – the PS3 and the 360 might be a few times faster than the Wii, but their components are many times more expensive to make. By not going top-of-the-line, Nintendo could make the Wii for a very reasonable price and sell it at a profit.

  • 36 chungy // Nov 21, 2008 at 2:53 pm

    > It’s much better if we can get stuff to work with current updates. Old versions only last so long after all.

    Yes, I realize this, but the idea was only for downgrading systems at least temporarily until exploits for the newer versions are found and distributed. Exploiting the latest updates is always important, especially for the case of users who have not installed any homebrew previously and would like to try it (this isn’t even considering newer games/channels requiring new versions.

    Also, I don’t think there’s a whole lot of Wii games that can really be considered “safe” to exploit, since it requires that users have a copy of the game to use. Wii Sports is a pretty safe choice since almost all consoles come with it (except in Japan, or most previously-used consoles). Twilight Princess is fairly popular and it could be expected that quite a lot of people have it (though I know one person that rented the game for the express purpose of installing Homebrew Channel). Beyond that, I think Super Mario Galaxy and Super Smash Bros. Brawl are going to be the safest games to exploit for terms of their popularity… can’t think of any other game with anything as close of a potential userbase. (Shelling out $50 for a game copy, or $10 for a rental, just for installing HBC isn’t the most ideal thing in the world.)

    Are there any free games in Wii Shop Channel (I can’t use my Wii atm, TV is occupied)? If so, those might also be potential exploit candidates, but you’d also depend on users having a Wii connected to the Internet (which is less common, in my observation, than you might think).

  • 37 nightwatch // Nov 21, 2008 at 3:27 pm

    That would destroy performance. Not even the Xbox 360 does that – it uses the virtualization features of the Xenon to install a hypervisor instead. Correct me if I’m wrong here, but as far as I understand it the same effect, without the invasiveness, could be achieved by just modifying IOS to require authorization for things that could enable piracy: all of those functions have to go through IOS anyhow.

    Plus you don’t want to limit the clever things that homebrewers could think of. That’s the whole point of homebrew after all :)

  • 38 HyperHacker // Nov 21, 2008 at 5:17 pm

    I think a similar system could effectively brick-proof/”Nintendo-proof” the console though. You have to go through IOS to access anything in the NAND, don’t you? Patching those routines to block all access to boot2 (and of course any routines/exploits that allow running code on IOS) should ensure BootMii can never be removed, unless the user deliberately allows access somehow. (e.g. by holding certain buttons on a Gamecube controller.)

    Chungy, $10 for a rental? Where do you live?

    Brawl is definitely a candidate; there was a save exploit in Melee. Nobody really used it because it was found long after the Gamecube was broken wide open.

  • 39 roboprez // Nov 21, 2008 at 6:31 pm

    the way i see it is that since you aren’t going to release a quick fix for the twilight hack, you aren’t going to get new homebrewers. For instance, if you hadn’t heard of homebrew before, why wouldn’t you update your console? You need to find a way to get the twilight hack on.
    Oh and about trying to find buffer overflows in games, the most popular games are Wii Sports, Wii play, Zelda and Galaxy

  • 40 Wii update 3.4 | // Nov 21, 2008 at 9:19 pm

    […] latest update from Nintendo (3.4) apperantly put a end to the Twilight Hack.  marcan over at hackmii.com wrote a post to calm people down that are upset about the […]

  • 41 Mewkip // Nov 21, 2008 at 10:44 pm

    My brother got a hold of my Wii, deleted the Homebrew Channel because he thought it was illegal and then updated. He came up to me and said “I fixed your Wii” and I’m like “What?” and I go to check. I notice the disappearance of the HBC and try to re install it, but it doesn’t work! D= Will you fix this or convince Team Twiizers to fix this soon? I’ll be waiting.

  • 42 morph // Nov 22, 2008 at 8:03 am

    Yeah, running code in user mode would simply drive away an awful lot of homebrewers with it’s strict requirements on code behaviour (no privileged instructions, no direct I/O, can’t fool around with control registers, etc.), but ATM I can’t see any other way of keeping pirates away without touching IOS.

    I hope the fine guys here come up with a solution that doesn’t impair our ability to do whatever we want on the PPC – except piracy, of course (wii/VM? :P)

  • 43 morph // Nov 22, 2008 at 8:04 am

    s/it’s strict/its strict/

    Damn, I must still be asleep :)

  • 44 Wii/NDS - 任天堂破解資訊網站 - Dash Hacks Network » Blog Archive » Marcan 不懼怕Wii 3.4 更新…. // Nov 22, 2008 at 9:42 am

    […] 來源 […]

  • 45 Seth Merkley // Nov 22, 2008 at 2:33 pm

    How would an exploit to SSMB work, seeing as though you can’t backup/restore its saves?

    And as for having to go out and rent/buy a new game for the exploit, I’m sure there are at least a few people around who are willing to trade their games around for the sake of homebrew.

  • 46 Lucario // Nov 22, 2008 at 7:50 pm

    the update doesnt do anything to the homebrew i updated it and nothing happened.

  • 47 momo // Nov 22, 2008 at 9:47 pm

    Didn’t an old update mention the ability to load a save from sd card? A game featuring that would surely be ideal…that’s if irc in the first place!

  • 48 HyperHacker // Nov 22, 2008 at 10:31 pm

    “How would an exploit to SSMB work, seeing as though you can’t backup/restore its saves?”
    A hacked save file can have the “no copy” flag removed, so you’d be able to copy it, but I think you’d be forced to delete the existing file, if it won’t let you move it. However, screenshots and probably other files are read directly from the SD card, IIRC.
    I wonder if it’s possible to copy over a hacked save file that has the no copy bit cleared, but no actual content (just a header), and it would overwrite only the header of the existing save? Then you’d be able to move it, and hopefully repair it and move it back when you’re done with the exploit.

    I understand VC games can do save states that show up in the game saves list? I wonder if any of these are exploitable. N64 games load code to RAM, so you’d be able to take over the emulated N64, and possibly break out of the sandbox. Potentially these files could even contain state or code from the emulator itself. A save state being essentially a RAM dump, it seems more likely to be exploitable than an ordinary save file.

  • 49 tech3475 // Nov 23, 2008 at 4:52 am

    The way I see it, the only way to prevent piracy because of homebrew is to restrict access to the IOS. e.g. when using bootmii.

    However this also causes problems because those who want legit region free would need IOS access and (at least in the beginning) it will be a headache for programmers.

    Someone is going to loose.

    Personally I can see some form of CFW being released at some point because of the people who want e.g. Gecko OS. Of course I don’t know how Bootmii will work or how you will try to prevent the pirates from abusing homebrew.

    IMO If you want to pirate, get a modchip. Of course I am not saying they should pirate but leave homebrew alone!!!!

  • 50 HCK // Nov 23, 2008 at 7:55 am

    A SSBB hack using SD features would be awesome (hacked replays, pics and stuff), as it COULDN’ T BE FIXED 😛

    @Lucario: It does crap on the Homebrew, that’ s a FACT.

  • 51 BlackRayquaza21 // Nov 23, 2008 at 9:13 am

    There are so many posibilities with Homebrew as long as there are ways around the security updates. Personally I’m with the developers on this. Exploiting Wii to put in VC games on it IS pirating, and if yout hink you dont get caught, you do, because every time you play it, it logs it, and that log is sent to nintendo, and they can cross reference it with your IP address to see which titles you’ve downloaded.

    In actuality I’d like to see a hack FOR the Wii Menu, not exploiting it, but hacking into it, like… Wii Paint Menu or something where you can change the colors of the wii menu like the borders and that bland white color.

    And as for SSBB its possible to make hacked replays , but its just a series of character names and controller movements that are stored in the .bin file, not the entire replay. Hence the reason it cannot be converted like some people are trying to do which is sad…

    As for hacked pics, I use the free range camera to make those. and Ammo switching. Example being switching Super Scope shot with CD’s or Smash Balls… the things you see on youtube if you look hard enough.

    Anyway, to keep from boring you guys even more I’m going. So bye.

  • 52 tech3475 // Nov 23, 2008 at 11:31 am

    actually they could depending on the hack, all they would need to do is place an update in the IOS to block the game from running it.

    It would be tough but Nintendo hate allot of things including Homebrew.

  • 53 Link // Nov 23, 2008 at 1:07 pm

    From what I understand, all current channel installers use IOS functionality – the new HBC installer exploits the IOS again so that an installation succeeds.

    Generally: if you’d write your own Wii filesystem module and everything completely in C/PPC assembly – could you use that to install data directly into the filesystem bypassing all IOS?

  • 54 Seth Merkley // Nov 23, 2008 at 1:08 pm

    Yeah I’ve often wondered what hacking we can do with those save states, too. Like converting save states from PC emulators and using them on the Wii.
    But with N64 games, you don’t get save states, probably because they would be pretty large. But of course the ROM saves themselves could still be exploitable…

  • 55 HyperHacker // Nov 23, 2008 at 1:24 pm

    He probably meant HBC.

  • 56 3.3 menu update affecting YAOSM? - WiiNewz Forums // Nov 30, 2008 at 12:59 pm

    […] this page on HackMii as well as this one makes it seem less and less like the update was a total and 100% bad thing. […]

  • 57 TheGuy // Dec 2, 2008 at 9:36 am

    I just updated! Shouldn’t Nintendo just make peace with the homebrew secne and make things eaiser for the developers??? If Nintendo try to stop the hacks, it will anger the scene and make people want to fight back more. They should just accept that homebrew is here to stay. You guys at HackMii are brilliant! I was going to leave the scene because of having to avoid updates, but the sheer adactivieness (sorry about spelling) made it worth keeping the homebrew channel.

  • 58 metroid maniac // Dec 30, 2008 at 12:13 pm

    out of intrest, has there been a fakesign fix in boot2 yet?

  • 59 edy100 // Jan 1, 2009 at 9:12 am

    wii v3.3u – is it the same with v3.4?
    I can’t find anything working for this 3.3u – just some files from 3.4 can be seen – but not used or installed

  • 60 aledTH // Jan 3, 2009 at 11:14 am

    I don’t know what to do.
    I have bought a 2000 Wii Points Card, and the Wii Shop Channel has asked me to update. I have the Homebrew Channel on my system. Shall I install it? (Also, can you delete the Twilight Hack after you’ve used it?)

  • 61 metroid maniac // Jan 19, 2009 at 12:36 am

    wiibrew said bc and mios were updated. how were they changed?

You must log in to post a comment.