Hacking Wii Menu 4.2 Released

Helsionium said:
They never said boot2 can't be overwritten. boot1 can't be overwritten, even by Nintendo, and you (as well as many other guys) are confusing the two.
Wait... ok, so it was a boot1 issue that prevented writing to boot2, correct? Then why would the new boot2 update prevent bootmii from being installed?

In other words, it would be possible for a wii with a vulnerable boot1 with the new boot2 to restore bootmii, but it's impossible to get bootmii on a system without a vulnerable boot1?
 
Link5084 said:
First of all guys, why would you download 4.2 since it contains no new features at all? WHY!?!
Well it probably actually has a few enhancements in the background, like the Nintendo update dialouge claims. Otherwise they wouldn't have used a new IOS for the System Menu. And it's just fun.
I sadly don't have my Wii here or I ould toy aroung with it a little. As long as I don't do the official Nintendo update I can always go back with bootmii.
 
WiiShizzza said:
In addition, there are some behind the scenes enhancements that do not affect any prominently-used features or menus but will improve system performance.

Sorry to stop your enthusiasm, but this is Nintendo's standard sentence. You'll find it in a lot of updates which didn't have any advantages — just like this one. So you can give a shit on this sentence, it's just platitudinous "bla bla".
 
zektor said:
Ok, so the method to take that technically should work fine to update to v4.2 (should you want to):

1. Load DOP-IOSv8 and install IOS56, IOS57, IOS70 (trucha IOS70)
2. Load NUSD and download the system menu for your region (Mine is USA, so v481) and wad pack
3. Boot wad manager and install the system wad you created, and install the "Love" HBC
4. Reboot

You should now be in v4.2 and everything will still be functional. Only drawback is that you will be able to load the HBC and load apps, but you will have to cycle power when you exit an app. More the apps fault than the HBC, as all apps seem to look for the "HAXX" title to reload the HBC.

This method will NOT remove your cIOSes, bootmii on boot2, or your previous trucha'd IOSes (like IOS36)

So with this we'll be able to use HBC and BootMii on 4.2? Could you tell me how to make the HBC Channel from HAXX to "love"
 
mdp_1992 said:
zektor said:
Ok, so the method to take that technically should work fine to update to v4.2 (should you want to):

1. Load DOP-IOSv8 and install IOS56, IOS57, IOS70 (trucha IOS70)
2. Load NUSD and download the system menu for your region (Mine is USA, so v481) and wad pack
3. Boot wad manager and install the system wad you created, and install the "Love" HBC
4. Reboot

You should now be in v4.2 and everything will still be functional. Only drawback is that you will be able to load the HBC and load apps, but you will have to cycle power when you exit an app. More the apps fault than the HBC, as all apps seem to look for the "HAXX" title to reload the HBC.

This method will NOT remove your cIOSes, bootmii on boot2, or your previous trucha'd IOSes (like IOS36)

So with this we'll be able to use HBC and BootMii on 4.2? Could you tell me how to make the HBC Channel from HAXX to "love"


Yes. You don't have to make it either. Look a few pages back where I uploaded the modified channel.
 
zektor said:
Ok, so the method to take that technically should work fine to update to v4.2 (should you want to):

1. Load DOP-IOSv8 and install IOS56, IOS57, IOS70 (trucha IOS70)
2. Load NUSD and download the system menu for your region (Mine is USA, so v481) and wad pack
3. Boot wad manager and install the system wad you created, and install the "Love" HBC
4. Reboot

You should now be in v4.2 and everything will still be functional. Only drawback is that you will be able to load the HBC and load apps, but you will have to cycle power when you exit an app. More the apps fault than the HBC, as all apps seem to look for the "HAXX" title to reload the HBC.

This method will NOT remove your cIOSes, bootmii on boot2, or your previous trucha'd IOSes (like IOS36)


Anyway, that's a somehow dirty workaround. I would consider it twice, before I do it.
Best choice is just to wait for a new HBC version or updated exit code in Homebrew...
But only the real Gurus can decide.

U still can install IOS56, IOS57, IOS70 (trucha IOS70) with DOP-IOS and stay on your old sysmenu, bootmii, cios, boot2.
that'll to for the moment...

//EDIT:
Det1re said:
QUOTE(WiiShizzza @ Sep 29 2009, 11:23 PM) In addition, there are some behind the scenes enhancements that do not affect any prominently-used features or menus but will improve system performance.

Sorry to stop your enthusiasm, but this is Nintendo's standard sentence. You'll find it in a lot of updates which didn't have any advantages — just like this one. So you can give a shit on this sentence, it's just platitudinous "bla bla".

Maybe... I didn't investigate the sysmenu 4.2, yet...
Playing around with title ids is not my thing. So I would stay on 4.0 but with new IOS.
 
WiiShizzza said:
marc_max said:
WiiShizzza said:
@marc_max

Thx man for dop-ios. It's pretty cool.
Can you confirm ios70 can properly be "trucha patched" I read somewhere ios70 is a bit different than the old ioses...
Sorry, I can't confirm anything right now
frown.gif

I just added IOS70 to the list to keep Dop-IOS updated.
The only way to know it is to find someone with BootMii and NUSD'd 4.2 without boot2v4 and a way to load homebrew.
Hmmm, I can try tomorrow... or maybe zektor can check it, he's one step ahead...
And then try if fake-signed channels load from SD menu, and trucha discs aswell
smile.gif
 
zektor said:
Ok, so the method to take that technically should work fine to update to v4.2 (should you want to):

1. Load DOP-IOSv8 and install IOS56, IOS57, IOS70 (trucha IOS70)
2. Load NUSD and download the system menu for your region (Mine is USA, so v481) and wad pack
3. Boot wad manager and install the system wad you created, and install the "Love" HBC
4. Reboot

You should now be in v4.2 and everything will still be functional. Only drawback is that you will be able to load the HBC and load apps, but you will have to cycle power when you exit an app. More the apps fault than the HBC, as all apps seem to look for the "HAXX" title to reload the HBC.

This method will NOT remove your cIOSes, bootmii on boot2, or your previous trucha'd IOSes (like IOS36)
Well I would do it this way:

1. Make yourself a loadmii channel and always keep it on the last page as a backup
2. Load SysMenu4.2 with NUSD
3. Install patched IOS70 with DOP-IOS
4. Install SysMenu4.2
5. Install preloader
6. reboot
7. activate the preloader hacks

Your HBC shouldn't be deleted as you never go back to the system menu before enabling the preloader hacks. But should it be deleted you have the loadmii channel as a backup. ^^


Disclaimer: I haven't tested this as I don't have my Wii here so if you fuck up it's not my fault, but it should work without a problem.
 
@zektor
If I mess up by any chance with you're method (Not blaming you or anything) would I be able to go back to 4.1 with BootMii if I have a Nand Backup?
 
metroid4life14 said:
Also, what about nand emulation...? Can we use that to run games that require 4.2?
We won't even need to do that. Just install IOS57 or whatever other new ones come out and you'll be golden. Some people are still on 3.2 and have been manually installing IOS's for a year at this point.
 
I just tested my own install instructions and am now on v4.2U (settings menu works now), all of my loaders work (222/223/249) and homebrew works of course. The HBC is deleted immediately after installing the system menu and running it of course, but that's where the install for the modified HBC comes in.

That wasn't too hard to hack
smile.gif
Off to make a nand backup with v4.2.....and check if trucha on IOS70 works (for VC/Wiiware on SD)
 
metroid4life14 said:
Also, what about nand emulation...? Can we use that to run games that require 4.2?
There have never been, nor will there ever be, a game that requires a certain System Menu. -.-
 
I just wanna make clear again, that messing with systemmenu can brick your wii.
Use the dirty workaround only if you know what you're doing
 
WiiShizzza said:
I just wanna make clear again, that messing with systemmenu can brick your wii.
Use the dirty workaround only if you know what you're doing
And preferably have bootmii...
 
zektor said:
I just tested my own install instructions and am now on v4.2U (settings menu works now), all of my loaders work (222/223/249) and homebrew works of course. The HBC is deleted immediately after installing the system menu and running it of course, but that's where the install for the modified HBC comes in.

That wasn't too hard to hack
smile.gif
Off to make a nand backup with v4.2.....and check if trucha on IOS70 works (for VC/Wiiware on SD)

...Alright I'm going to try it out.
But where can I get DOP-IOSv8
 
Slowking said:
WiiShizzza said:
I just wanna make clear again, that messing with systemmenu can brick your wii.
Use the dirty workaround only if you know what you're doing
And preferably have bootmii...


Definitely have bootmii. Since my method is not touching any cIOS slots OR boot2, your bootmii on boot2 will still be there
smile.gif
 
I just tested hard coding my System 4.2 WAD with the HAXX/DVDX/RZDx check hack and the Homebrew Channel and DVDX are there after the upgrade with the Wad so I'd image it works fine. I Hard rebooted a few times to make sure.

Mini-Walkthrough:
The following was done on the v481 System File WAD. Just open up 00000008.app in a hex editor go to offset 4AC0 and change the next 8 characters to F (see pic) save the file and pack it back into a wad. Update your ISOs using Dop-IOS and then use the wad you created... Tada

Someone else can write a better walk through.
Oh and make sure your using Bootmii with a backup before trying this.

EDIT: I suppose I should say THIS WILL BRICK YOUR WII if you mess it up, lol

hex.jpg


-FTen

EDIT: All Region Offsets;

The correct Offsets for all Regions;

Offsets taken from Preloader Hack;
USA v481 = 4AC0
EUR v482 = 4B30
KOR v486 = 3FBC

Found on my own;
JAP v480 = 3FBC
 

Site & Scene News

Popular threads in this forum