Hacking Downgrading bricked wii

newer wii's cannot run a 3.2 system menu UNLESS you first install IOS60v6174 to slot30... chances are good that you bricked yourself.

Do you have a nand backup? If so, you can send your Wii to DeadlyFoez and he can repair it using his infectus nand programmer to restorer your nand backup.

edit: this is a perfect example of how ModMii's extra brick protection comes in handy. If this wii had ModMii's extra brick protection installed (which includes IOS60v6174 installed to slot30), then making the mistake of installing a 3.2U system menu would not have resulted in a brick.
 
Well...this seems pretty obvious: the system menu's use different IOS'es. That makes upgrading and downgrading a bit more obnoxious: you need not only to switch the system menu, but make sure to have the correct IOS installed as well (according to wiibrew, system menu 3.2 uses IOS 30).

The solution? I sure hope he has bootmii or priiloader installed. If not, he can use his wii as a nice paper weight. What the hell was he thinking downgrading it to begin with? Did he grew tired of having access to SDHC cards or something?
 
Same thing happened to me and there where nothing i could do. The wii was still under warranty so i sended to nintendo telling them i had an upgrade problem that damaged mi wii(wich is kind of what hapend) and they repaired for me.
 
Well, to find out for sure if he can have bootmii installed to boot2, have him compare his serial number to the ones in this thread http://gbatemp.net/index.php?showtopic=205180

If his serial number falls in the "Compatible" range then there is a chance to unbrick it by manually installing bootmii into boot2. But if his wii is incompatible then the only way to save that wii is with a nand backup.
 

Site & Scene News

Popular threads in this forum