What was the point of even making that post?
to point out that the topic title makes it look like everyone's wii is going to have an issue for whatever reason
What was the point of even making that post?
to point out that the topic title makes it look like everyone's wii is going to have an issue for whatever reason
I've seen some stupid stuff on this website. I've seen some REALLY stupid stuff on this website. That just ranks in the top as one of the most stupid posts I've seen. I think one would have to be quite a few steps past mentally handicapped to make that assumption from the title.
[useful post]
OP, installing a new SM overwrites priiloader. priiloader is patched into the SM, and is not a standalone program; making an overwrite to the System Menu (such as upgrading/downgrading) overwrites the portion that contains priiloader, meaning it's gone until you reinstall it.
You have, someone correct me if I am wrong, no way to boot into BootMii@IOS without being able to boot into a way to access HBC or an app that can access it.
Why you would install a stub is beyond me, as that is NEVER a good idea, ESPECIALLY when that IOS is the SYSTEM MENU IOS. A stub is useless; imagine having a desk covered with cups, most of which have water in them, but some are empty, which would be the stubs. You'd be better off not having them there (in almost every single case), but best scenario would be having them replaced with a cup filled with beer instead (or, in the case of the Wii, a patched and non-stubbed IOS). Why you would also install SM 2.2 is beyond me, but I'm not going to go on about it, because I'm sure you regret it enough without having people point out how critical of a mistake you made.
Your only options are booting a game with SaveMiiFrii and installing an updated SM (which SHOULD work fine, if I am not mistaken, I've been out of the Wii scene way too long to guarantee anything though), installing a drive-chip capable of autobooting a disk that has a newer update on it, or buying an Infectus/Progskeet and building a new NAND and flashing it with your Wii keys (or, better yet, contact DeadlyFoez and pay him to have it shipped to him and fixed, provided you have the keys. He has the necessary hardware and is the biggest person on GBAtemp, arguable the entire world, to do this for people.)
If you never made a NAND backup, that last option is completely out, at which point SaveMiiFrii or a drivechip are going to be your only options at hopefully getting it to work.
Like I said, I've been out of this shit too long to promise anything, but for SMF you only need a GC controller (which you can put back together afterwards), and an autoboot capable drivechip shouldn't be too expensive; not as expensive as a new Wii at least.
[/useful post]
Also, OP, should you get this fixed, or buy a new Wii if it can't be, don't do something risky like this without asking people here and/or checking Google and WiiBrew first. Not only is a few hours of waiting and doing other things in the mean time cheaper than a new Wii or the time wasted by fixing it, but you'll learn from every single question you ask. You might be called a noob by some people by asking if something is a good idea or not, sure, but you'll get a lot more flak for doing something stupid and asking how to fix it after the fact. For what it's worth, future knowledge, it's almost never a good idea to touch an IOS below slot 200. You've got 54 slots to install cIOSes in, though one of them (254) will be filled with BootMii@IOS. Having every single SM IOS slot installed with a valid and patched IOS isn't a bad thing; it's rather good, in fact, as it does ad a slight level of brick safeguarding, should you have priiloader installed (and at that, there are always people that advist against priiloader, but had you had it installed, you could change your SM IOS to something like 249 so you could boot like normal and reinstall IOS20, or boot straight to the HBC. Just food for thought.
I guess you didn't read the entire post.wow you totally posted an entire essay to rebuttle one line of thread
I didn't know priiloader could run on sysmenu ios.Why the hell were you trying to install 2.2U and a STUB IOS? What was the point of this? And why didn't you use ModMii?
I didn't know priiloader could run on sysmenu ios.
*facepalm*to point out that the topic title makes it look like everyone's wii is going to have an issue for whatever reason
Why would you install 2.2?U shouldve used modmii and get 4.1.I installed 2.2U as the system menu and was reinstalling IOS20 with the stub version.
I have Priiloader installed and BootMii as IOS.
I turn on the wii with really nothing! No black screen, no message, no everything!
Even when powering on and holding reset to get to the priiloader menu, still nothing.
HEEEEEEEEELLLLLLLLLLP!
I installed a theme as a wad with modmii on 4.1J...My wii still works...ModMii isnt dangerous, definitly other things are though.you wouldn't have to do all of that if you used a csm file an not a wad. wad themes are dangerous.