I don't know. However, if this was the problem, I suspect that Gecko would work with the play it once idea.Mejilan said:For those of us that safe-updated to 4.2 and are still getting prompted to update via the disc, can't we just use DOP-IOS to manually install IOS53 and call it a day?
I haven't actually tried playing the game yet, so I haven't tested it myself.
Yes. It likely won't bother updating your boot2 again, and even if it does, your Wii is already known to be safe.Dimmuxx said:Is it safe to play nsmb pal on a 4.2 officially updated wii? It will just update ios53 and don't remove any nice stuff(hbc, IOS236 & cIOS249) right?
You have to watch the updater, it can often crash before completion. It will tell you if it completed. As for NSMB, even if you do the 4.2 Safe Update, NSMB will ask you to update. It is likely detecting the lack of boot2v4 on your system.Bizzyb said:Just did the 4.2 safe updater via HBC BUT the Wii still reads as Ver 4.1 and the Mario Disc Channel still reads System Update. I'm not sure if I should run it again or what went wrong I just don't want to fuck up my Wii.
Any suggestions?
Or he can install it to a HDD and play it from there without having to worry about the disc update.Clipper said:Play NSMB with Gecko OS for another day or two. If Mejilan finds that IOS53 is enough to bypass the update, I'll add that method to the tutorial. If it isn't enough, I'll add StartPatch to the tutorial.
Yes, install BootMii as boot2 if you can and make a backup. There is no reason not to.Seagoon said:Is there any software I can run on the Wii to display a summary of all the IOS versions that are installed etc?
Should I bother installing bootmii? - I understand it can make a backup of my machine in case something in the future bricks it. (I have already followed the excellent guide and have Configurable USB Loader running).
Thank you for the awesome tutorial website.
See below.Mama Robotnik said:Hi Clipper (or anyone else that can help), a quick question, had look at the thread and wiki but didin't spot the answer. (My apologies if its been prominently answered)
My Wii is still on firmware 3.2, it hasn't been updated since and I'd prefer not to go through the hassle. Will NSMB work using GeckOS to bypass the disk-update? Is there anything in the updates I've missed that could cause the game not to function properly?
My thanks.
Thanks for that Mejilan. I'll add that to the update tutorial.Mejilan said:Just use DOP-IOS v8 to install the newest version of IOS53.
I did that, and also updated to a newer version of IOS55.
Disabled the Preloader hack that blocks on-disc updates, then rebooted the Wii.
Game runs off the disc without an update prompt. So as far as I can tell, it's not checking the boot2 sector. It just requires 4.1 and a new IOS53 (and/or possibly IOS55), as far as I can see.
Clipper said:You could also install Preloader or StartPatch to avoid the updates. I may add a page for StartPatch to the tutorial soon because of the NSMB issue.
Whether you have the HBC installed or not, the chances of bricking are equal. Thus, there is no real need for him to delete it.
Clipper said:Edit: New info on the What's New Page says: Added Avoid Disc Updates page.![]()
Have you also previously updated to 4.2 via the safe installer?wackojackosnose said:Hey Clipper, I've tried this with twice now (old and revised instructions) but it still isn't working for me. I get to (5) of the latest instructions but the program doesn't offer to install IOS36. Instead, after loading IOS249, I'm given the option of entering IOS, Channels and System Menu. I go into IOS and install both IOS53 and IOS55 without applying Sig Hash Check Patch. Upon restarting the system, the NSMB disc is still telling me to update my system. I checked with the IOS Mod program and it says I have IOS53 (rev 5406) and IOS55 (rev 5406). Where am I going wrong?
Thanks for any help.
Clipper said:Thanks for that Mejilan. I'll add that to the update tutorial.
Clipper said:Have you also previously updated to 4.2 via the safe installer?
It's also just possible that this whole plan is wrong :S.
Hmm, I guess I'm updated from the 4.1 update on the NSMB disc, so if you can tell me what IOS versions you have (using DOP-IOS or Title Lister), maybe we can work out what else you need!
Mejilan said:Just use DOP-IOS v8 to install the newest version of IOS53.
I did that, and also updated to a newer version of IOS55.
Disabled the Preloader hack that blocks on-disc updates, then rebooted the Wii.
Game runs off the disc without an update prompt. So as far as I can tell, it's not checking the boot2 sector. It just requires 4.1 and a new IOS53 (and/or possibly IOS55), as far as I can see.
Dragona Akehi said:OK this is slightly confusing. I installed my copy of NSMBWii (NTSC/US version) and it has run just fine and I have a completely uninteresting 4.1 Wii. Do I actually need IOS53 for anything?
Mejilan said:I was merely testing/devising a way to get rid of the on-disc update prompts when running the game off the actual disc, without actually running the on-disc update.
If you're running it off HDD (as I am), then the steps I posted aren't really necessary.
According to DOP-IOS, I actually already had (an older version of) IOS53 installed, before I even bought NSMB Wii. I imagine it hit via the 4.2 safe updater. *shrugs*
Is there a bootmii directory on your SD card? If not, run the installer again and choose the "Initialise SD card" option. If so, try copying it to another SD card if you have one. BootMii is particularly picky about SD cards that you use.Quixzlizx said:I have a question about BootMii. I currently have 4.0u, and I followed the instructions on this page. I installed BootMii, and installed it as boot2, and used the sdhc card that was in there as the bootmii card. According to the installer, this was all successful. The HBC apparently installed fine, but my system is automatically going to the regular Wii menu when I start it up, so I'm not sure what I need to do to get BootMii to initialize. Thanks.
Clipper said:Is there a bootmii directory on your SD card? If not, run the installer again and choose the "Initialise SD card" option. If so, try copying it to another SD card if you have one. BootMii is particularly picky about SD cards that you use.
wackojackosnose said:Here you go:
IOS57 v5661
IOS56 v5405
IOS70 v6687
IOS250 v65535
IOS249 v15
IOS254 v3
IOS61 v5405
IOS50 v5120
IOS16 v512
I just updated IOS15 (which is now v523) but the disc channel is still telling me to update. Hmm... :/ Thanks for your help though!
Just update IOS249.autobzooty said:Also, when I boot up Twilight Princess, Configurable USB Loader says something about a warning for CIOS 249 before rev14 and that error #001 might not be addressed. I forget the exact error message, usually it goes away too fast before the game starts up. Is this going to cause a problem for me later on? Aside from the sound issue, the game is playing fine.
Answered in this thread already if you look up. And it's on the Gaf Homebrew FAQ now I think. To answer simply, NSMBWii will still ask for an update most probably. Won't remove homebrew but will remove Bootmii and also therefore has the very minimal chance of being bricked.Vinterbird said:Stupid question time:
- If I use the safe upgrade to 4.2, can I play New Super Mario Bros. Wii straight from the disc, or does the game have an newer update on it? (and can I update via the normal official way without loosing homebrew and the likes, and only risk the minimal chance of a brick?)
A folder called bootmii will be on your SD. Move it to your PC as it should contain a nand backup you'll want to keep hold of. Copy that back on to the SD if you ever need to use Bootmii- Every time I boot my Wii with the SD card inserted, it boots straight into the BootMii menu. Is there a way so I can have the SD card in the Wii, and have it boot to the normal Wii menu?
Maybe with a drive cleaning disc, maybe.- Some Wii games like Metroid Prime Trilogy and Brawl doesn't load via the disc due to their dual-layer nature. According to Nintendo, I need to send them my Wii so they can clean the reader-head. Is there a way (non USB harddrive way) to fix it myself?
You can update internally. There's an update option in global options IIRC.- Whats the easiest way to update the Configurable USB Loader?
Or he can just rename it on the card and then change it back when he wants to use bootmii. Another option is to set it to autoboot to the Wii system menu or HBC after any time he chooses.samratty said:A folder called bootmii will be on your SD. Move it to your PC as it should contain a nand backup you'll want to keep hold of. Copy that back on to the SD if you ever need to use Bootmii
Yeh, these ways are better and easier.Fuzzy said:Or he can just rename it on the card and then change it back when he wants to use bootmii. Another option is to set it to autoboot to the Wii system menu or HBC after any time he chooses.
Thanks, I'll try it out!CO_Andy said:Just reinstall HBC to flip the channel screen to normal position.
You get it upside down if you install something that modifies the contents of the HBC.
I wanted to add a few more points to the answers you already got.Vinterbird said:Stupid question time:
As stated, you will still be asked to update and risk bricking. A procedure has been added to allow you to avoid the disc update.- If I use the safe upgrade to 4.2, can I play New Super Mario Bros. Wii straight from the disc, or does the game have an newer update on it? (and can I update via the normal official way without loosing homebrew and the likes, and only risk the minimal chance of a brick?)
You can rename the directory as suggested, but you can also turn on the autoboot option to make BootMii autoboot to either the System Menu or HBC (I personally set a 1 second timeout to HBC as it gives easy access to my Homebrew, and the system menu is easy to get back to with the home button). Instructions to do this are on the BootMii page.- Every time I boot my Wii with the SD card inserted, it boots straight into the BootMii menu. Is there a way so I can have the SD card in the Wii, and have it boot to the normal Wii menu?
Cleaning seems to be the only thing you can try.- Some Wii games like Metroid Prime Trilogy and Brawl doesn't load via the disc due to their dual-layer nature. According to Nintendo, I need to send them my Wii so they can clean the reader-head. Is there a way (non USB harddrive way) to fix it myself?
Instructions to do this by both online and offline methods are on the page for it.- Whats the easiest way to update the Configurable USB Loader?
There is something fishy in your story. This is either not a new Wii, you have installed additional stuff to what you were told to install, or you didn't follow the Wiki properly. The HBC turns upside-down if the IOS it runs off is not original. There is no step in the Wiki that ever changes any of your original IOSes.Ormberg said:I need to ask the wizards in here about this one...
So I got a new Wii with fw 3.3 installed. Followed the gaf wiki but after IOS15 restore I got a "DUMP" screen. Wii seemed to work fine though, so I decided to redo it from step 1.
Well, after I reinstalled the homebrew channel and installed cios 38 rev 14, the HBC was upside down :lol
I still got USB Loader working and I could install my games on it and the play fine, but HBC, and only HBC, is still upside down :lol
Any reason to be worried?
That's rubbish.CO_Andy said:Just reinstall HBC to flip the channel screen to normal position.
You get it upside down if you install something that modifies the contents of the HBC.
The bricking fw is 4.2 iirc. 4.1 only fixed that Wii Sports Resort bug.Mama Robotnik said:On my Wii Firmware 3.2, I decided to take the risk and use the software-update that comes with New Super Mario Bros (PAL). It did two updates (and two restarts), and now my menu says I am running VER 4.1E. Game runs as its meant to, my homebrew channel is still present and working fully.
I can provide photos if needed. Could it be that, unexpectedly, the game actually doesn't contain the bricking firmware?
wrowa said:The bricking fw is 4.2 iirc. 4.1 only fixed that Wii Sports Resort bug.
I did exactly the same process as you with the two updates and everything. It was then that I noticed that BootMii wasn't autobooting me to the HBC any more and I realised my boot2 had been updated.Mama Robotnik said:On my Wii Firmware 3.2, I decided to take the risk and use the software-update that comes with New Super Mario Bros (PAL). It did two updates (and two restarts), and now my menu says I am running VER 4.1E. Game runs as its meant to, my homebrew channel is still present and working fully.
I can provide photos if needed. Could it be that, unexpectedly, the game actually doesn't contain the bricking firmware?
Clipper said:I did exactly the same process as you with the two updates and everything. It was then that I noticed that BootMii wasn't autobooting me to the HBC any more and I realised my boot2 had been updated.
The 4.1E update on PAL NSMB is a hybrid update. It's 4.1, plus a few new IOSes, plus the infamous boot2 update.
You are actually safe from the 4.2 update. It will not update boot2 again. Basically, your Wii would either have been susceptible to this update or not. By not bricking, you have proved it isn't susceptible and it would be safe even if they did try to overwrite it again (although a boot2v5 or later could cause problems).Mama Robotnik said:Then I take it all back!
So I have the dangerous update safely installed, but my homebrew channel is secure, at least at present...
The Wii Shop Channel is asking for a system update - I presume doing this will install 4.2 over 4.15 (?) and mess with boot2 again? Not to mention wipe the Homebrew Channel?
They like to make it complicated, don't they? A shame, as I have Wii Points to spend.
I wonder why Nintendo went with the hybrid firmware over 4.2 then?
Thanks for the prompt answer, by the way.
Clipper said:You are actually safe from the 4.2 update. It will not update boot2 again. Basically, your Wii would either have been susceptible to this update or not. By not bricking, you have proved it isn't susceptible and it would be safe even if they did try to overwrite it again (although a boot2v5 or later could cause problems).
It could wipe the HBC, but if you installed the latest version of the HBC, it won't. You would need to install IOS249 and IOS222/223 again, though.
As for spending your points, I've had a method to access the Wii Shop without updating the Wii since the update came out in the first place. I think it might have even been within 24 hours of the release of 4.2.