Ok guys, I need a little help. I'm not new to updating and wii hacking, but I've run in to some strange happenings. My problems all started when for whatever reason my system menu updated to 4.2U when I know I've been on 4.1U since it came out. Anway, was going to update to 4.2 using the sticky guide and got as far as banner bomb when it said I couldn't load hackmii because of unsupported IOS. Previous versoins of Boot Mii and preloader were both working fine, and I checked them to make sure. I tried going into system settings to check my version to make sure I was on 4.1...after getting many blank screens (could still hear music) it finally decided to let me navigate and my system menu was 4.2U?!?! I didn't load any system update WAD files or anything...basically all I ran was the files off the SD card (banner bomb) and tried to load the hackmii installer (which failed on start due to no usable IOS) How this happened I have no idea. I checked bootmii again and checked to see the NAND version...it said I have boot2v4?? How did this happen?? Mind you all my homebrew stuff works still, backups load, and I can run USB loaders, etc... no problem. After doing some more reading I decided to go ahead and try to finish the update in the sticky, but use the part AFTER a 4.2 update to modify. I could still load WAD files with Wadmanger, and loaded the files listed in the sticky guide. Still the homebrew stuff works... I just wanted to make sure I have all the correct IOS files installed. I don't know if bootmii still worked at this point because I didn't test it. I'm thinking it didn't because I had it skip the health screen and at reboot I had to push "a" to get to the wii menu.
After this I still wasn't sure if my system files were all up to date, so I said F' it.... I've read that it's best to just to do a Nintendo update, and then go from there. At this point I thought I'll just try the nintendo updater and see what happens. Not sure if it made any difference since I did the sticky update...but Nintendo's update lasted for like a minute and it was done. I'm guessing it's because the files were already updated?? Anyway, I don't see any difference now from the Nintendo update that I did before doing it. I still have homebrew channel, everything works in it, I can still run backups, my USB loaders still work...however I don't have the Bootmii installed and it wont let me saying something about unsupported IOS. I've read something about deleting IOS 30, then using another IOS (IOS 36?) and reinstall a patched IOS 30 to be able to install bootmii.
Right now I'm just concerned about what IOS and cIOS files are on my wii, and if it will become unstable. I really want bootmii back just for the added protection. My wii is definitely not bricked, not too concerened about bricking it since I have a fairly decent idea of what NOT to delete. I just want to make sure all my homebrew is compatable with the proper IOS files if that makes sense.
In the past I would just reformat my wii and start fresh. I've done that many times in the past when I first got into wii hacking and homebrew. I've leaned a lot from trial and error, and saved my wii from what I thought was a brick. Anyway, my original system is pre 3.2U. I've read if I'm at 4.2U downgrading will brick it since it has boot2v4, I would think reformatting would just put my system back to what it was from factory...but would boot2v4 cause a problem? If so this is a major oversight by Nintendo. I've also read formatting is a bad idea and shouldn't be done, since I doesn't remove all IOS files or cIOS files. I've also read about "re-virginizing" my 4.2U wii...of course keeping all the homebrew IOS files and channels...
What should I do guys?? Just keep it as is since my homebrew is working? I need to get bootmii installed though. I guess I'm just too anal about having the latest updates (though I initially didn't even update to 4.2) and knowing if I have the proper IOS files and cIOS files.
After this I still wasn't sure if my system files were all up to date, so I said F' it.... I've read that it's best to just to do a Nintendo update, and then go from there. At this point I thought I'll just try the nintendo updater and see what happens. Not sure if it made any difference since I did the sticky update...but Nintendo's update lasted for like a minute and it was done. I'm guessing it's because the files were already updated?? Anyway, I don't see any difference now from the Nintendo update that I did before doing it. I still have homebrew channel, everything works in it, I can still run backups, my USB loaders still work...however I don't have the Bootmii installed and it wont let me saying something about unsupported IOS. I've read something about deleting IOS 30, then using another IOS (IOS 36?) and reinstall a patched IOS 30 to be able to install bootmii.
Right now I'm just concerned about what IOS and cIOS files are on my wii, and if it will become unstable. I really want bootmii back just for the added protection. My wii is definitely not bricked, not too concerened about bricking it since I have a fairly decent idea of what NOT to delete. I just want to make sure all my homebrew is compatable with the proper IOS files if that makes sense.
In the past I would just reformat my wii and start fresh. I've done that many times in the past when I first got into wii hacking and homebrew. I've leaned a lot from trial and error, and saved my wii from what I thought was a brick. Anyway, my original system is pre 3.2U. I've read if I'm at 4.2U downgrading will brick it since it has boot2v4, I would think reformatting would just put my system back to what it was from factory...but would boot2v4 cause a problem? If so this is a major oversight by Nintendo. I've also read formatting is a bad idea and shouldn't be done, since I doesn't remove all IOS files or cIOS files. I've also read about "re-virginizing" my 4.2U wii...of course keeping all the homebrew IOS files and channels...
What should I do guys?? Just keep it as is since my homebrew is working? I need to get bootmii installed though. I guess I'm just too anal about having the latest updates (though I initially didn't even update to 4.2) and knowing if I have the proper IOS files and cIOS files.
