Hacking Wii Menu 4.2 Released

mdp_1992 said:
acesniper said:
TiMeBoMb4u2 said:
PLEASE come back Waninkoko...WE NEED YOU!

biggrin.gif
I didn't even know that he left.

LoL You're Lucky, I don't even know who he is xD

I just feel like updating my Wii... Weird temptation :S
He's the guy who wrote cIOS.
 
gwiz210 said:
So quick question. My wii is not with me and is with a friend far away right now, if he were to update would I lose the capability of using the backup loader channel I have on my wii, it's the only real homebrew thing I have, I don't even have the homebrew channel. Would I lose that channel/would it still function? I use DVD-Rs for backups if that makes any difference.
most likely, if it deletes HBC, then why not any other custom channel?
you best get in contact with your friend.
 
Waninkoko wrote lots of stuff. Like WAD Manager, Wii Config, USB Loader, and a whole bunch more... He made the trucha bug relive again (but trucha bug restorer did that.)
 
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
smile.gif
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
smile.gif
 
zektor said:
DVDX installs to 202, Hermes installed to 202, and Mplayer_ce cIOS installs to 202. Those are the three...and they all pretty much function the same. Although, I find Hermes version to be the best of the three.

So do I, which is why it is so on my system.
smile.gif
 
Oh thank the lord... I come back in my room to find my brother about to update the wii....
QUOTE said:
IOSes 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 smile.gif

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 smile.gif

Good to know
smile.gif
 
zektor said:
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
smile.gif
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
smile.gif
phew hearing that bannerbomb can be fixed is a huge relief.
 
TiMeBoMb4u2 said:
System Menu v4.2 reeks of October 23, 2008!

Took them a whole 11 months to do it, too. Seems like we'll have this all worked out in a week or two and won't have to worry about much for another year.
 
xzxero said:
zektor said:
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
smile.gif
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
smile.gif
phew hearing that bannerbomb can be fixed is a huge relief.
Sweet, even more good news!
 
mdp_1992 said:
Oh thank the lord... I come back in my room to find my brother about to update the wii....
QUOTE said:
IOSes 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 smile.gif

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 smile.gif

Good to know
smile.gif


Nintendo called him.
tongue.gif
(UPDATE UR WIIZ FER NEW PRIZES! HURRY NOW~!) You showed him the light!

Im honestly not current to the scene and I updated to 4.1 with no clue as to what would happen. Luckily I was on GBATemp when this occurred
smile.gif
.
 
GameSoul said:
mdp_1992 said:
Oh thank the lord... I come back in my room to find my brother about to update the wii....
QUOTE said:
IOSes 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 smile.gif

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 smile.gif

Good to know
smile.gif


Nintendo called him.
tongue.gif
(UPDATE UR WIIZ FER NEW PRIZES! HURRY NOW~!) You showed him the light!

Im honestly not current to the scene and I updated to 4.1 with no clue as to what would happen. Luckily I was on GBATemp when this occurred
smile.gif
.
ROFL. thats funny. and Nintendo is probley laughing their heads off while pissing their pants because of no homebrew for a week.
 
Yyhhggtt said:
xzxero said:
zektor said:
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
smile.gif
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
smile.gif
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!
 
I got a second wii today, figured I'd update it to the latest then hack it. Since my other wii didn't have an upgrade showing, I didn't realize a new one was out until it was too late.

I can confirm that SSBB Smashstack 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.
 
this is so stupid... i'm not going update my wii... and my wii's not flashing blue for some reason... i'll be damned if nintendo would stoop lower by forceing auto update on wiiconnect 24 man that would piss all of the pirate's off and then i would go to the nintendo usa headquaters and fuk there couchs!!
 
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?
 
vladus2000 said:
I got a second wii today, figured I'd update it to the latest then hack it. Since my other wii didn't have an upgrade showing, I didn't realize a new one was out until it was too late.

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.

Awesome. Have you tried running the Trucha Bug Restorer from SSBB or something? If not, do so and see how that works.
 
Wow... 191 users reading at time of this writing...

Anyways, if they do force update your Wii, well, I won't care... My Wii isn't on 24/7... I actually haven't used it in a while...

Also, good to hear that SmashStack still work.
 

Site & Scene News

Popular threads in this forum