New Wii Firmware 4.2 Deletes Homebrew

as of Sept. 29th 2009 do not update your Wii. You will install System Menu 4.2 and this is dangerous for homebrew. Ive heard that a new 4.2 installer is currently being worked on but this is just rumors.

Tell everyone you know this will delete homebrew channel, update your boot2 v4, install stub IOS over cIOS. please do not update.

For now there is a new exploit using Lego Indiana Jones to hack your wii and install Homebrew channel. However not everything is still functional.

Version 4.2 of the System Menu was released on September 28, 2009.

Changes

[ul]
[li]Deletes most homebrew.
[/li][li]Now uses IOS70. (No Preloader due to that)
[/li][li]Wii Shop Channel updated. Use WiiSCU to update the shop channel.
[/li][li]Most of the IOS’s have been updated or stubbed.
[/li][li]Updates your boot2 to boot2v4 (what LU64+'s have). (That means no downgrading of any IOS, and due to that, you can’t revert back to your old System Menu. So BootMii as boot2 installed is removed.)
[/li][/ul]

Affected Homebrew

[ul]
[li]Bannerbomb - Doesn’t work.
[/li][li]BootMii - BootMii will cease to exist.
[/li][li]Homebrew Channel - It is uninstalled with this update.
[/li][li]cIOS - cIOS locations are stubed.
[/li][li]Preloader 0.29 - Not loaded any more due to IOS70 being used as the System Menu.
[/li][/ul]

North America

29/09/2009

Wii Menu version 4.2 is now available for your Wii console. To update your Wii Menu to the latest version, please select the Update button at the bottom of the screen or select the System Update option in the Wii System Settings.

This update provides behind-the-scenes fixes that will not affect features but will improve the overall system performance.

Because unauthorized modifications to save data or program files may impair game play or the Wii console, updating to Wii Menu version 4.2 will also check for and automatically remove such save data or program files.

**Please note: If you’ve updated your Wii Menu after 9/29/09, you may not need to update again.

Thank you for updating your Wii console!

Nintendo

This is a solely anti homebrew update, it will delete anything and essentially everything to do with hacks.

I have uploaded this immediately so people can make sure their Wii is not updated. The update was released today.

Ok, here is more technical information:

What the update does is:

Install boot2v4 on your Wii. This makes any Wii like the new Wii with serial starting with LU64+. This is the first time boot2 has been included on a Wii system menu update, it means if you update, you can no longer downgrade to earlier firmware safely and do many things including bootmii as boot2. Watch out.

It deletes the Homebrew channel. This is huge.

It switches the system menu IOS to IOS70 and patches most IOS’s to fix vulnerabilities and so they can no longer run bugs, making Homebrew hard to install. There is a Lego game fix that can install Homebrew.

It installs stubs on IOS222, 223, 249, and 250, which are all custom IOS’s for running backup games or bootmii. This makes it almost impossible with the current tools to use USB Loaders, but later updates should easily get around this.

However, the patch on IOS250 doesn’t work very well, which means that it won’t patch over the cIOS if you have it.

Here’s the good news, Team Twiizers has released a new exploit for installing Homebrew. i will post the Indiana Pwns instructions and download link below.

Direct Download link to Lego Indiana Jones Exploit - Indiana Pwns
http://www.mediafire.com/download.php?ylyjguzydry

youtube video

Required materials

* SD card (<= 2GB, not SDHC) formatted as FAT16 or FAT32. (The game, and therefore the exploit, can only read SD cards, not SDHC)
* SD card reader
* A LEGO Indiana Jones game that has been played at least once
* Some homebrew to load (e.g. the Homebrew Channel installer) 

Step by step

  1. Ensure your SD card is formatted as FAT. By default SD cards are formatted as FAT, so if you’re not sure you can skip this step.
  2. (Optional) If you have an existing Indiana save that you want to backup, do so before proceeding:
    1. Put your SD card in your Wii and turn it on.
    2. Go into Wii Options --> Data Management --> Save Data --> Wii
    3. Find your Indiana save, click on it, click “Copy”, and click Yes
    4. Put your SD card in your computer, and copy the “private” folder from the card to a safe place.
  3. Copy the “private” directory from the Indiana Pwns download to the root of your SD card.
  4. Take your homebrew Wii executable (ELF file) and save it in the root directory of your SD card as “boot.elf”.
  5. Put your SD card in your Wii and turn it on.
  6. Go into Wii Options --> Data Management --> Save Data --> Wii.
  7. Find your Indiana save, click on it, click “Erase”, and click Yes.
  8. Open the SD card and select the “Indiana Pwns” save that corresponds to your game region. Note: Some people are having problems with the Wii not “seeing” the save file on the SD card. If you are experiencing this, try setting the archive bit for the data.bin file - in Windows this can be either be done from the file’s properties dialog (right click on it in Windows Explorer and check the box) or from the command line using “attrib +a <path to data.bin>”. More info at #wiihelp on Efnet.
  9. Click copy and then yes. Now exit out of the menu.
  10. Insert LEGO Indiana Jones disc and run the game.
  11. Walk to the “art room” (find some walkthrough on the intertubes if you cannot find it), look at the second character.

the original hackmii installer i included will get deleted everytime you start your wii.

here is a new installer for use on SM 4.2, hackmii installer 0.5
http://www.mediafire.com/download.php?djeamn5nynj

this is safe to use on all versions of wii system menu. this gives the HBC and DVDx different title IDs thus playing games with nintendo to delete homebrew channel. another failed attempt by nintendo. none of the applications which use DVDx will work with the new DVDx but any of the good apps will get updated in the days to come.

im still interested if IOS249 is installable? will keep you updated.

okay here it is, everything here is for an offline install of every mod you need for your 4.2 wii.

i cant take the credit for this one. please read the readmii.
http://www.mediafire.com/download.php?ejkdynzzmmm

.

[QUOTE=troy512;2442933][*]Homebrew Channel - It is uninstalled with this update.[/quote] Strange. It still works here.

the title id HBC is installed under was HAXX which is deleted by system menu 4.2

[unless you have preloader installed with the correct hack.ini]

the new title id of HBC is J0DI, so if you have installed HBC 1.0.5 or 1.0.6 then SM 4.2 will not delete your HBC.

there are many more updated apps which are now compatible with SM 4.2 but screw it. there is still no real need to update past 3.2.

[unless you want sd card menu then you need 4.0, which i use because the Custom System Menu selection is better using 4.0]

My Wii is very rarely used these days, so i don’t really mind wether the homebrew channel works or not.

It seems though the channel works, but the program’s on the sd like the homebrew browser don’t. Oh well.

Just updated the entire homebrew system on my wii via automatic update system. These guys are AWEsome.

Now on to update the wii, i wonder if it will still work by then…

Hmm, seems it still works… maybe because i have one of the first Wii’s ? :slight_smile:

After some extensive testing i come to the following analysis:

  • HBC still works in Firmware 4.2E as long as you update the HBC version first and then the Wii
  • USB forwarder will not start up. Need to unplug and reconnect power of the wii
  • WAD manager will not start up. Need to unplug and reconnect power of the wii
  • Other homebrew (like ScummVM 1.0) works perfectly.
  • Installing homebrew via homebrew broswer works perfectly.

So… i guess the firmware blocked some of the usb and wad channel thingies, but kinda leaves the rest alone…

system menu 4.2 has been reported to prevent out of region games from running when using a modchip

[B][U]new wii with 4.2 pre-installed[/U][/B]

pretty straight forward just follow the simplistic mod

most important: remove the stubbed cIOS above 200 and use homebrew channel with J0DI title id

bootmii/boot2 is 99.9999999999% not going to install. as boot1 will most likely have the bug fix preventing bootmii to install in boot2.

all previous system menu IOS are stubbed including IOS60, IOS50, IOS30, IOS20 and IOS11. be sure to install latest unstubbed versions for full compatibility and brick prevention.

wii drive chip is most likely going to be a D3-2. this drive has the controller chip removed and will never play dvd-r using softmods.

[B][U]older wii official updated to 4.2[/U][/B]

again follow the simplistic mod, not all steps are relevant however most of it is helpful.

bootmii/boot2 gets overwritten by newly installed boot2v4. however bootmii can be reinstalled using hackmii installer and function as normal. even a previous backup can be restored. so long as the wii had vulnerable boot1, bootmii will still install to boot2.

HBC title id HAXX is removed. however if HBC J0DI was previously installed its still there and completely functional.

need to updated DVDx to v2

as always with any install of a system menu preloader is removed.

all previous system menu IOS are stubbed including IOS60, IOS50, IOS30, IOS20 and IOS11. be sure to install latest unstubbed versions for full compatibility and brick prevention.

bootmii IOS is not removed.

[B][U]safely updated to 4.2[/U][/B]

[U]install[/U]
IOS70-v6687
HBC J0DI
DVDx v2
SM 4.2 wad for your region
preloader with correct hacks

[U]whats not affected[/U]
bootmii/boot2/IOS
cIOS above 200
stubbed system menu IOS [unless previously stubbed]
HBC J0DI
DVDx v2
any other apps or channels

[QUOTE=troy512;2482347]
[B][U]older wii official updated to 4.2[/U][/B]

again follow the simplistic mod, not all steps are relevant however most of it is helpful.

bootmii/boot2 gets overwritten by newly installed boot2v4. however bootmii can be reinstalled using hackmii installer and function as normal. even a previous backup can be restored. so long as the wii had vulnerable boot1, bootmii will still install to boot2.[/quote]

Soo, if i use the hackmii installer (again…) all should be well on my Wii to use the USBforwarder and the wad manager? I think i found the hackmii on the homebrew browser somewhere… gotta check tonight.

all previous system menu IOS are stubbed including IOS60, IOS50, IOS30, IOS20 and IOS11. be sure to install latest unstubbed versions for full compatibility and brick prevention.

By “stubbed” you mean Nintendo overwrote the old/previously hacked IOS schematics with crap? Do i still need to unstub them all if i just had used the hackmii?

usb loader needs IOS249 to run has nothing to do with hackmii installer

newer versions of wad manager such as v1.5 can also run using IOS249
http://www.mediafire.com/?0qbodmyvtzy

IOS249 is the IOS installed when running cIOS38 installer
http://www.mediafire.com/?yxdgygjanyq

by stubbed i mean they are purposely broken, have not other use except to overwrite the older working version.

see this thread

your wii will work just fine with the stubs under IOS200 installed. however if you were for any reason to install an older system menu your wii will become a full brick, unfixable except by using bootmii installed as boot2.

the hackmii installer is not on the homebrew browser, the latest version is Hackmii installer v0.6, available here
http://www.mediafire.com/?kjngz4m0nlq

.

I did some checks:

SignCheck 0.3b aka loveSexWii build report
Wii region, Europe
Wii unique device id, somethingsomething

IOS number, “Trucha bug”, “Flash access”, “Boot2 access”, “Usb2.0 IOS tree”

IOS70 (ver 6687), Disabled, Disabled, Disabled, Disabled
IOS61 (ver 5405), Disabled, Disabled, Disabled, Disabled
IOS57 (ver 5661), Disabled, Disabled, Disabled, Disabled
IOS56 (ver 5405), Disabled, Disabled, Disabled, Disabled
IOS55 (ver 5406), Disabled, Disabled, Disabled, Disabled
IOS53 (ver 5406), Disabled, Disabled, Disabled, Disabled
IOS38 (ver 3867), Disabled, Disabled, Disabled, Disabled
IOS37 (ver 3869), Disabled, Disabled, Disabled, Disabled
IOS36 (ver 3351), Disabled, Disabled, Disabled, Disabled
IOS35 (ver 3349), Disabled, Disabled, Disabled, Disabled
IOS34 (ver 3348), Disabled, Disabled, Disabled, Disabled
IOS33 (ver 3091), Disabled, Disabled, Disabled, Disabled
IOS31 (ver 3349), Disabled, Disabled, Disabled, Disabled
IOS28 (ver 1550), Disabled, Disabled, Disabled, Disabled
IOS22 (ver 1037), Disabled, Disabled, Disabled, Disabled
IOS17 (ver 775), Disabled, Disabled, Disabled, Disabled
IOS14 (ver 520), Disabled, Disabled, Disabled, Disabled
IOS13 (ver 273), Disabled, Disabled, Disabled, Disabled


So basically in order to run backups i need to

1 - Execute the cIOS38 installer at the HBC, which will install IOS249
2 - Execute the WAD manager at the HBC, which will install the USB Forwarder as a normal Wii channel
3 - Execute the USB Forwarder channel

right?

signcheck is a neat little app, however i have found it to be flawed.

  1. does not properly report trucha patches
  2. may not report stubbed IOS

if you official updated to 4.2 you will need to use anytitle delter to remove IOS249. then reinstall IOS249 using waninkokos cIOS38 installer or IOS249 wad from the simplistic mod guide.

the USB Loader GX forwarder channel requires the directory to be set on your sd card or fat32 partition on an external USB device.

sd:\apps\usbloader_gx\boot.dol

have you happened to read over the pimp my wii thread?

[QUOTE=troy512;2483794]signcheck is a neat little app, however i have found it to be flawed.[/quote] Bummer

if you official updated to 4.2
Which i did

you will need to use anytitle delter to remove IOS249. then reinstall IOS249 using waninkokos cIOS38 installer or IOS249 wad from the simplistic mod guide.
I tried waninkokos CIOS38 installer. It shows some very ugly creature holding a diamond or something and some text on the right. It told me it would use IOS249 to install IOS249. Fine with me i guess. I thouht it would automatically get the correct IOS, since it’s an offline installer. press A … and the wii freezes.

After reinserting the power to the Wii i tried IOS38 as a setting, also locks up at the same time.

Then i tried no reloading IOS… it tries to write IOS249 and it downloads some things (kinda strange for an offline installer), patches them, tries to write NAND and comes up with an error -tsomething… and i can reset the wii. Joy.

So currently my best bet is that my wii either already has a malfunctioning IOS249 or that ugly creature can’t write it. Since the signcheck can’t find a IOS249, but also is a flawed application, i can’t fathom to begin wether there was already a IOS249 or never has been a IOS249 and how to write a IOS249 correctly. There is no logic in the entire process. Then again, most 3rd party patch or write utilities seldom have logic in them.

the USB Loader GX forwarder channel requires the directory to be set on your sd card or fat32 partition on an external USB device.

sd:\apps\usbloader_gx\boot.dol
i thought once you could execute the forwarder channel it will automatically scan for a usb device, format it if necessary and that’s about it. It isn’t?

have you happened to read over the pimp my wii thread?
Yes, but it’s not entirely clear what IOS i need, how to get them all ok, how to correctly write them and i’ve seen several threads that the pimp my wii application also has a lot of errors.

What i find entirely strange in this matter is that the HBC is still quite alive. All other homebrew like ScummVM, HomeBrew browser, paint programs, etc work 100% perfectly, yet that USB forwarder thing and WAD can’t install because they need some weird hacked version installed as IOS249. Perhaps it’s better to wait when the internet gods found out how to run things just like ScummVM can run things, no more IOS things to worry about. :slight_smile:

[QUOTE=Mr. Belvedere;2484095] I tried waninkokos CIOS38 installer. It shows some very ugly creature holding a diamond or something and some text on the right. It told me it would use IOS249 to install IOS249. Fine with me i guess. I thouht it would automatically get the correct IOS, since it’s an offline installer. press A … and the wii freezes.

After reinserting the power to the Wii i tried IOS38 as a setting, also locks up at the same time.

Then i tried no reloading IOS… it tries to write IOS249 and it downloads some things (kinda strange for an offline installer), patches them, tries to write NAND and comes up with an error -tsomething… and i can reset the wii. Joy.[/quote]

I think i found out why it can’t write.

Question… Where do i place the wad on the sd card? It’s not mentioned anywhere where to place the wad file so it can read it. It should be on the root of the sd card eh? :slight_smile:

Update: relocating the wad file didn’t work either. Still freezes the wii

you need to remove the stubbed IOS249 before the properly working version will install.

please follow the guide i linked in post #10

It’s progressing.

BootMii works (i see the bootmii screen), but i can’t select any of the items on either of my 3 remotes so after 5 seconds it loads the Wii OS itself.

Pimp my Wii did the job the first time by first downgrading IOS15 it seems. Wad manager runs, on to the USB forwarder.

Thanks for all your help so far, much appreciated.

Latet update: Complete and total success!! :slight_smile:
Still can’t select anything in bootmii though, can only wait for the wii to load its normal os.