Thanks. Just wrote a question about 'what now?' after region change back to 3.2e. Lack of planning maybe but now so happy my jap wii is pal, and i will no longer accidentally update, delete my mii with mario kart and galaxy saves again.... but worried about updates etc. Good warning and will update to 4.0 just now!
I dont believe you have to downgrade your Wii to 3.2 to fix that bug. I just used this guide NEW AND IMPROVED WII SOFTMOD GUIDE ! which I think is the easiest well put guide ive seen so far in learning how to mod my Wii, even with all the help ive gotten from everyone nothing compares to how easy this guide is. I litteraly softmodded my Wii in the amount of time it took to update to 4.1 +5-10 minutes to follow the guide for the first time.
1 of the steps said it was going to downgrade some IOS and patch them with the bug fix so I guess if thats what your looking for theres no need to go down to 3.2
Well... I'm fairly sure this is the problem I have now, I'm posting here to double check and ask some questions.
My brother said he was downgrading to 3.2 from 4.0 on the wii, and now the wii does not work.
Symptoms: Plug in the wii, the light is red, press power, the light turns green, disc drive boots up, no video, no audio, nothing happens and the controllers will not connect. Can't turn off the wii, unless I pull out the power cord.
Kicker: He did not know what bootmii was. (Yet I discovered it after 5-10 minutes of googling this problem. I am not amused.)
Do the two options in the first post still stand? (No other alternatives?) And can anyone give me a fairly technical explanation (or at least some more info) as to why SaveMii or that free alternative using a GCN controllerin the 4th port will not work?
Sounds like a full brick. Not much you can do other than Savemii/savemiifrii. If that doesn't work, you gotta send it to Nintendo for repair. I bricked my wii about a month ago soft modding. Unfortunately it was out of warranty, and I had to pay 75 usd for repair.
Originally Posted by zzzman
@zzzman Savemii and Savemiifrii both attempt to do the same thing, to load the recovery menu. The recovery menu is a built in component of the System Menu (in this case IOS50) and as it is a stub (empty) can no longer be used.
At the moment we are unable to re-program the NAND directly without prior modification to the console. Currently the best method to do this is bootmii as boot2 as that launches before anything else.
In future who knows what will happen.
The downgrade itself will not often brick the Wii, it's what you do after causes the problems. Unless of course he chose the wrong region to downgrade to.
Have a buddy how downgraded to 3.2 - Now install IOS50 v4889 - Then free to update to 4.1?
Well actually this brick only accurs when updating to 3.4 from 3.2 without prior installation of the IOS50. I'm guessing (really guessing) that an update to 4.1 will be fine even without the IOS50 being installed as it is not used at 4.1. Still - to be safe, no harm will come to anyone installing good old friendly IOS50.
Bootmii as boot2? Can you write down where to put the files on the SD card? I have this downgrading then updating problem.
You can't just go putting the files on your SD card and expect it to work, you needed to have installed it to your Wii beforehand. If you did then you need armboot.bin, ppcboot.elf and bootmii.ini in the bootmii folder on the SD card, which it would have created at time of installation.
2 weeks i softmodded my wii using this download
Wii 4.0 softmod hack (NO ZELDA NEEDED) (download torrent) - TPB)
2 days ago i downgraded my wii to ver 3.2 then re upgraded to ver 4.1 and i redowngraded to 3.2 in hopes of upgrading to ver4.0 is there a way to do so and if i updated 4.1 should i install it in the same way but forget the ios