- Joined
- Aug 23, 2009
- Messages
- 3,010
- Trophies
- 1
- Age
- 29
- Location
- Ontario, Canada
- Website
- Visit site
- XP
- 1,711
- Country
Do what?Pumpkin King said:Ok. I did the updater again and it worked.
Now my only problem is with the preloader. It says something like it can't find the hacks.ini file...
The hacks.ini must be at the root of the SD card (not in any folder)
Be sure it has the hacks for your system menu version
QUOTE(Scott-105 @ Sep 2 2009, 05:00 PM) I'm a noob at this and need some help. Do you need a modded wii or anything to do this?
I think leaving it at 10 and letting people update themselves if they choose is fine. Ive had problems installing higher than rev10 on virgin Wiis before.nabster92 said:Also if you do update to have it use rev14, you should say to run the cIOS rev14 installer and have it use IOS36 because it prompts for what IOS to use and that's the whole point of using the Trucha Bug Restorer to restore the trucha bug to IOS36.
And regarding the doing step 12 before step 11, the 4.1 updater gives you an error if you do not have IOS60 installed on your system as I believe it is really meant to be an updater to 4.1 from 4.0. So if you are updating from 4.0 you can do it fine otherwise you would need to install IOS60 first (which is why doing step 12 first works). What you could also do is have them run the 4.0 updater first and then the 4.1 updater then still run dop IOS on IOS60 afterwards. Doing dop-IOS first and then running the updater should also work as well though.
And as a last note, I do suggest that you remove the IOS and cIOS downgrader steps. They really aren't necessary and are actually the only things holding this guide back from working on any Wii right now.
assassda said:I think leaving it at 10 and letting people update themselves if they choose is fine. Ive had problems installing higher than rev10 on virgin Wiis before.nabster92 said:Also if you do update to have it use rev14, you should say to run the cIOS rev14 installer and have it use IOS36 because it prompts for what IOS to use and that's the whole point of using the Trucha Bug Restorer to restore the trucha bug to IOS36.
And regarding the doing step 12 before step 11, the 4.1 updater gives you an error if you do not have IOS60 installed on your system as I believe it is really meant to be an updater to 4.1 from 4.0. So if you are updating from 4.0 you can do it fine otherwise you would need to install IOS60 first (which is why doing step 12 first works). What you could also do is have them run the 4.0 updater first and then the 4.1 updater then still run dop IOS on IOS60 afterwards. Doing dop-IOS first and then running the updater should also work as well though.
And as a last note, I do suggest that you remove the IOS and cIOS downgrader steps. They really aren't necessary and are actually the only things holding this guide back from working on any Wii right now.
If you run Dop-IOS and then 4.1 Updater will it overwrite the patched IOS60 that you just installed?
IOS-Downgrader is to remove the trucha bug, a lot of these steps are overly cautious so that no one will have problems. I havent seen anyone reply here saying IOS-Downgrader didnt work.
assassda said:I think leaving it at 10 and letting people update themselves if they choose is fine. Ive had problems installing higher than rev10 on virgin Wiis before.nabster92 said:Also if you do update to have it use rev14, you should say to run the cIOS rev14 installer and have it use IOS36 because it prompts for what IOS to use and that's the whole point of using the Trucha Bug Restorer to restore the trucha bug to IOS36.
And regarding the doing step 12 before step 11, the 4.1 updater gives you an error if you do not have IOS60 installed on your system as I believe it is really meant to be an updater to 4.1 from 4.0. So if you are updating from 4.0 you can do it fine otherwise you would need to install IOS60 first (which is why doing step 12 first works). What you could also do is have them run the 4.0 updater first and then the 4.1 updater then still run dop IOS on IOS60 afterwards. Doing dop-IOS first and then running the updater should also work as well though.
And as a last note, I do suggest that you remove the IOS and cIOS downgrader steps. They really aren't necessary and are actually the only things holding this guide back from working on any Wii right now.
If you run Dop-IOS and then 4.1 Updater will it overwrite the patched IOS60 that you just installed?
IOS-Downgrader is to remove the trucha bug, a lot of these steps are overly cautious so that no one will have problems. I havent seen anyone reply here saying IOS-Downgrader didnt work.
rich333 said:Hi,
I followed this guide last night, offline version, to upgrage from 3.2 to 4.0.
I had previously installed softmii 2.1 and wanted to get rid of CIOScorp.
My question is about step 11, installing wads 1-18. Are they installed to IOS249 (as thats what is selected in wad manager 1.4)? So do they then overwrite the old IOS or become part of 249. Why don't you select IOS15 to install the IOS15.wad?
I also noticed some of my old CIOScorp IOS werent in the 1-18 wads (IOS9, 14, etc) so i downloaded the with NUS, when i installed them i replaced the actual IOS (ie. installed IOS9.wad with IOS9 selected in wad manager 1.4) - should i have selected 249 as i did with the 1-18?
Any clarification on this would help, i'm trying to get my wii as stable as possible - CIOScorp free.
Also, after all this i installed the cios rev14 wad to 249. Is this ok or should i have done this first (ie, instead of step 10)
Thanks,
Rich
Don't use this guideSimpleSimon08 said:Followed the guide got error -1036 using Waninkoko 4.1 updater so used Waninkoko 4.0 with intention of running 4.1 update, 4.0 installed okay but now can't run Homebrew and no backups working. Bootmi installed at boot2 but doesn't run just black screen and can't get to run 4.1 updater. NAND backup done as per guide. What should I do next? Help
Kirb94 said:How do i get BootMii compatible with the Wii remote and how do I get the wii to turn on and go straight to the systemmenu instead of going to BootMii?
You don't Bootmii can't support Wiimote's and never will. You need to use the power button to move right and the reset button to select or you need to use a gamecube controller.
Use the bootmii configuration editor app to set it to autoboot the HBC or the system menu after however many seconds of bootdelay that you want it to stay on the bootmii menu. Look for the link in my guide in the boot2 bootmii section.
QUOTE(SimpleSimon08 @ Sep 12 2009, 11:32 AM) Followed the guide got error -1036 using Waninkoko 4.1 updater so used Waninkoko 4.0 with intention of running 4.1 update, 4.0 installed okay but now can't run Homebrew and no backups working. Bootmi installed at boot2 but doesn't run just black screen and can't get to run 4.1 updater. NAND backup done as per guide. What should I do next? Help
SimpleSimon08 said:Didn't make myself clear in previous post so wil try again but system updated to 4.1E as per guide.
Bootmi was loading just couldn't get to HBC so repeated step 2 and 3 only reinstalling HBC. Then continued with guide from point 8 and then straight to point 11 and worked this time not sure if it was cIOS36 not installed properly.
Now have patched system but loaded NeoGamma loader which warns I am using version 10 not v14, can I just run the latest cIOS36 v14 installer without additional steps?