Hacking Wii Menu 4.2 Released

[Yyhhggtt]

cIOSes are not what we need to worry about. They can be modified (as long as the author is around, or the source is available) to install to other slots. Then, it would be up to the loaders to add the ability to adjust to use the new slot(s) for use. IE: 224/225

Hermes has always made his source available fortunately...and his cIOS is everything Waninkoko's is and then some.

The real issue is getting a bannerbomb (or Indiana/SSBB exploit) working in v4.2.....and I have already read a confirmation that bannerbomb has been fixed. Next, we have to hope that TT is on this and will fix the boot2 overwrite. That shouldn't be too hard, since the flawed boot1 is the reason we can install it....and since it is a ROM, the flaw will exist in those old boot1 chips forever.

Then, finally, TT would have to install the HBC to a different location.

I don't think we have too much to worry about, except for the fact that all of this will take TIME. So, don't update now unless you would like to be without all of the fun for a few weeks or months

phew hearing that bannerbomb can be fixed is a huge relief.

Sweet, even more good news!

NONONO...I mean "fixed" as in NINTENDO fixed it! We need confirmations that the other exploits still work!

oh. )=

 

[xzxero]

cIOSes are not what we need to worry about. They can be modified (as long as the author is around, or the source is available) to install to other slots. Then, it would be up to the loaders to add the ability to adjust to use the new slot(s) for use. IE: 224/225

Hermes has always made his source available fortunately...and his cIOS is everything Waninkoko's is and then some.

The real issue is getting a bannerbomb (or Indiana/SSBB exploit) working in v4.2.....and I have already read a confirmation that bannerbomb has been fixed. Next, we have to hope that TT is on this and will fix the boot2 overwrite. That shouldn't be too hard, since the flawed boot1 is the reason we can install it....and since it is a ROM, the flaw will exist in those old boot1 chips forever.

Then, finally, TT would have to install the HBC to a different location.

I don't think we have too much to worry about, except for the fact that all of this will take TIME. So, don't update now unless you would like to be without all of the fun for a few weeks or months

phew hearing that bannerbomb can be fixed is a huge relief.

Sweet, even more good news!

NONONO...I mean "fixed" as in NINTENDO fixed it! We need confirmations that the other exploits still work!

ahhh! in that case aahhhh!
you know the word fixed is usually good.
not today.

 

[techboy]

however the homebrew installer cannot install cause it cannot find a known vulnerable IOS. Perhaps if you have 250 installed, it can work around it.

Did you try using 0.4 installer from here: http://bootmii.org/snapshots/hackmii_insta..._v0.4-test1.zip

If that doesn't work, looks like waiting for 0.5 is the best option...

 

[Dr. Clipper]

If there's anybody out there with a Wii that had a recent cIOS38 (hence IOS250) installed with the ability to do either SmashStack or Indiana Pwns? If so, can you try to run Configurable USB Loader with config.txt including "ios=250" to see if it works?

 

[illinialex24]

Wiibrew says the lego thing works and stack smash should work, but don't quote me on that. Homebrew can be reinstalled but it should boot2v4 your Wii and thats not good.

Posts merged

Oh and bootmii doesn't work atm.

 

[zektor]

I can confirm that SSBB Stacksmash works, however the homebrew installer cannot install cause it cannot find a known vulnerable IOS. Perhaps if you have 250 installed, it can work around it.

*Perfect*. As long as that works, we are in business. Now just have to wait for TT to update the HBC/Bootmii installer. I wonder if TBR will work loaded directly from the stacksmash (and actually add trucha back into IOS36). If that is the case, you can then use smashstack to run a modified Hermes cIOS installer and install to a non-used slot or slots...like 224 and 225. Then finally, someone can update a loader to use these slots. I see no reason why it wouldn't work...except for maybe adding trucha back in...

 

[FenrirWolf]

Does anyone know if it removed BootMii from Boot2?


I'm looking to do some testing like:

Update all IOS and SM to latest 4.2 and use the following method on a NTSC Wii and see how it goes

Wii updated with all new stuff, IOS249 Uninstalled, HBC removed and all.

Use SSBB exploit, using LoadMii, load Trucha Bug Restorer, Downgrade to IOS 15, restart, Installed hacked IOS36 (downgrading in this case since it was upgraded), restore IOS15
Not sure if this IOS36 (newer one) Will allow Trucha Bug Restorer to work, hmmmm....

After that, Take WAD Manager and install all old IOS (not so old, but the last that worked fine), install IOS60 again so it's not stubbed, and SM 4.1U.

It should do the trick to DOWNDATE to 4.1U.


Now my question is, what about IOS70, will that affect in any way?
cIOS is removed, but it should be able to install again with the DOWNDATE.
Install PreLoader, Install HBC using the HackMiiInstaller 0.4 Beta (just for testing)
and Load homebrew.



All I need to know really is the risk of loosing BootMii from Boot2 and not being able to restore my NAND with a .bin I got.

Anyone?

Yes, it did remove BootMii/boot2. But in theory IOS250 (IOS249 clone) should have stayed behind so you might be able to simply load Wad Manager, run it off of IOS250, and reinstall the old IOS's.

 

[s3phir0th115]

I wonder how marcan will react to this. It doesn't look like we can follow his impeccable logic and use only pristine official IOS's if we want to run the homebrew channel, at least until they find a new exploit.

....jackass. And not long after he makes a comment like that too.

 

[Yyhhggtt]

xzxero is see you changed your avatar, nice.

cIOSes are not what we need to worry about. They can be modified (as long as the author is around, or the source is available) to install to other slots. Then, it would be up to the loaders to add the ability to adjust to use the new slot(s) for use. IE: 224/225

Hermes has always made his source available fortunately...and his cIOS is everything Waninkoko's is and then some.

The real issue is getting a bannerbomb (or Indiana/SSBB exploit) working in v4.2.....and I have already read a confirmation that bannerbomb has been fixed. Next, we have to hope that TT is on this and will fix the boot2 overwrite. That shouldn't be too hard, since the flawed boot1 is the reason we can install it....and since it is a ROM, the flaw will exist in those old boot1 chips forever.

Then, finally, TT would have to install the HBC to a different location.

I don't think we have too much to worry about, except for the fact that all of this will take TIME. So, don't update now unless you would like to be without all of the fun for a few weeks or months

phew hearing that bannerbomb can be fixed is a huge relief.

Sweet, even more good news!

NONONO...I mean "fixed" as in NINTENDO fixed it! We need confirmations that the other exploits still work!

ahhh! in that case aahhhh!
you know the word fixed is usually good.
not today...

Everything in this thread is bad news.... exsept for cIOS202 remaining

 

[illinialex24]

But we got an IOS already in 250 from the update so yeah.... It stubs over it...

 

[Yyhhggtt]

QUOTE(illinialex24' date='Sep 28 2009, 10:10 PM) Wiibrew says the lego thing works and stack smash should work, but don't quote me on that. Homebrew can be reinstalled but it should boot2v4 your Wii and thats not good.

Posts merged

Oh and bootmii doesn't work atm.
Boot2v4 on a lu32? Thats not good.

 

[techboy]

The stub does not replace the IOS250. The wii thinks the cIOS installed in IOS250 is newer than the stub it wants to install, so the update skips IOS250...poor planning on Nintendo's part.

 

[mdp_1992]

Crap...I was supposed to buy an HDD this Wednesday... now what's the point ?

Screw you nintendo!

 

[mpg187]

System Menu v4.2 reeks of October 23, 2008!

What is that supposed to mean?

 

[FenrirWolf]

But we got an IOS already in 250 from the update so yeah.... It stubs over it...

The IOS250 in the update is version 0xFF00 while apparently the one installed by Waninkoko is 0xFFFF. Therefore it should have been unaffected.

 

[wchill]

What would boot2v4 do on a pre-LU64 Wii...
But that is bad.

 

[illinialex24]

Oh ok cool that is good news

.

At least they screwed up.

 

[Yyhhggtt]

The stub does not replace the IOS250. The wii thinks the cIOS installed in IOS250 is newer than the stub it wants to install, so the update skips IOS250...poor planning on Nintendo's part.

isn't a stubed ios means it can't be downgraded?

 

[techboy]

Boot2v4 on a lu32? Thats not good.

Every wii an "LU64+"...forget the good old days, until someone learns how to downgrade boot2 (brickmii anyone?)

The good news is that Bootmii will still run once its updated.

Bad news is 3.2 is dead for anyone who officially updates as of now. Tools like ARC now pose more of a brick risk than ever.

 

[s3phir0th115]

The stub does not replace the IOS250. The wii thinks the cIOS installed in IOS250 is newer than the stub it wants to install, so the update skips IOS250...poor planning on Nintendo's part.

isn't a stubed ios means it can't be downgraded?

It can still be downgraded if you have an exploit, but you can't use that IOS to downgrade because a stub, by definition, is an IOS that no longer is functional.