Hacking Wii Menu 4.2 Released

Nice thing is that applications that offer the "Return to system menu" actually DO return to the system menu. So, that is a good alternative. Everything works great on this end. Let me try to install a VC game and move it to SD now...
 
You'd think Nintendo would give us a reason to update. There is no reason for anyone to update if it gives no new features. I bet the only "behind the scenes update" is adding IOS70 (besides overwriting cIOS's, boot2, and deleting the HBC) I'm staying on 4.0U.
 
I am very happy to report that DOP-IOSv8 trucha patching of IOS70 works fine as well
wink.gif
 
ften said:
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.
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

Cool. My only question, you used NUSD to make the wad initially, then wwpacker or something to repack it after making that edit?

I just want to make sure. I'd rather not mess up a wad at this point.

Edit:

Also, what is the checksum of your end wad, if you don't mind sharing?
 
Stating the obvious (after 54 pages of reading). Some game exploits still work and it’s possible to run homebrew on 4.2. The hackmii installers don’t work as they can’t find a vulnerable IOS. Wad Manager and TBR still run. So the two problems dealing with a virgin 4.2 are :-
1) Stop the System Menu from deleting HBC etc (preloader info suggests the patch is known).
2) Find a way of downgrading an IOS to get the bug back in.

My spare Wii is 15 hours away (7 year old relative got a Wii for birthday, failed 3 hours after first switch on, spare went hand carried as temporary replacement until the retailer re-opened to be hand carried back at Christmas) so I can’t play safely to answer my outstanding questions.

When TBR was tested it failed to downgrade IOS 15. TBR defaults to download from network so I would upgrade my servers to return something that would not work for the old IOS as there is no other reason to want it. Has it been tried with a wad from a game (e.g. Wii sports shipped with a 3.2) ?

If you did NUS Downloader, patch system menu, create WAD … could the WAD Manager load it before the bug had been re-introduced ?
 
I'm supposed to use NUSD for my System Menu with Wad Pack... I've never used it so might someone help me?
 
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.
So does Preloader use boot1? My understanding was the whole point of Preloader was to load before the system menu to avoid any updates like this causing irreversible issues down the road. It's the whole reason I installed it in the first place. Basically my questions is can Nintendo disable Preloader as well?
 
ften said:
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:
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

Guess this would be the best solution so far...
Although it's highly dangerous.

Would be nice if someone could write down the correct offsets for the different regions of the sysmenu...

BTW
It feels good to be back in the scene ^^
 
a member of a french forum suggested to use the TitleID of a crappy VC game for the HBC , so Nintendo can't block it (or they would face to many complaints about a VC game not working).
 
Benjay said:
a member of a french forum suggested to use the TitleID of a crappy VC game for the HBC , so Nintendo can't block it (or they would face to many complaints about a VC game not working).


that's quite (obviously) clever
 
We need the OP or mods to keep the first post of this thread updated. Ridiculous to have to distill it from 55 pages, mostly filled with banter, or posts by people who misread, or didn't read, because there's 55 pages

Should definitely be a rule to have the first post of threads like this up to date.
 
Benjay said:
a member of a french forum suggested to use the TitleID of a crappy VC game for the HBC , so Nintendo can't block it (or they would face to many complaints about a VC game not working).




That's EXACTLY what I was thinking! Good work number 2!
cool.gif









EDIT: Then again, they would just make an update to that game, changing its name.
cry.gif
 
s3phir0th115 said:
Cool. My only question, you used NUSD to make the wad initially, then wwpacker or something to repack it after making that edit?

I just want to make sure. I'd rather not mess up a wad at this point.

Edit:

Also, what is the checksum of your end wad, if you don't mind sharing?
Yeah I used NUSD to make the WAD initially, then wwpacker to repack it.
I should have mentioned, I'll correct it, In the post that I was using the v481 file, so the offset will be different for different regions.
My checksum is MD5 : 9b2547f68ad8f71096990d9332ad948c

-FTen
 
Ssseth said:
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.
So does Preloader use boot1? My understanding was the whole point of Preloader was to load before the system menu to avoid any updates like this causing irreversible issues down the road. It's the whole reason I installed it in the first place. Basically my questions is can Nintendo disable Preloader as well?
Well you understood wrong. Preloader gives itself the name of the system menu and renames the system menu. So preloader gets loaded and it loads the system menu. has nothing to do with boot2. And preloader is mainly there to prevent bannerbricks and patch the system menu. It has nothing to do with updateprotection and gets automatically overwritten with every update.
 
Patching the menu itself would appeal more to me personally than a HBC title id mod. I'd rather not deal with half my homebrew apps failing to return to the HBC, and with BootMii I'm more than willing to trust that I won't patch it incorrectly.
 

Site & Scene News

Popular threads in this forum