Grav said:Still having issues. At 3.2U (recently downgraded) and have NO CIOS installed and IOS36 installed from what I can tell, but wiigators cios installer still gives me -1017 when i try to install it.
mariomaniac33 said:Good job a_running_pir8! I was wondering if the IOS16 trick would work... hopefully Nintendo won't find out too soon...
I just made a channel out of this for those who are interested. I recommend installing it after you follow the fix. Here's the links
Patchanka said:they already said that they were saving IOS16 as a last resort if Nintendo closes all the other doors. Now the last resort is lost, because you couldn't be more patient.
noobwarrior7 said:never update, 3.1 or 3.2 for the win, 3.2 is best.
You do not seem to understand the phrase "last resort".noobwarrior7 said:you think IOS16 was the big bug/last resort they mentioned? I kinda doubt it, because it relies on distributing copyright nintendo code, which they never do...and also, it won't be a viable option for a lot of people.
knowitall599 said:Yeah, you are good to go. Just install cIOS that came with the launcher and you are set. This is in response to whostorm05.
marcan said:You do not seem to understand the phrase "last resort".noobwarrior7 said:you think IOS16 was the big bug/last resort they mentioned? I kinda doubt it, because it relies on distributing copyright nintendo code, which they never do...and also, it won't be a viable option for a lot of people.
If (say, in 9 months) get to the point where Nintendo fixed all the known holes and we couldn't find new ones over some time, then maybe we'd consider IOS16 as an option.
Now, if that happens, I guess we'll just take a nice long vacation from looking for holes.
Sure, we have more exploits, but they won't last forever. We have big bugs. The last resort (IOS16) wasn't one of them. It was a (shitty) last resort. Which you've just killed.
This crap makes me want to release BootMii in such a way that somehow, someway, it's useless for the WAD crap (don't think for a second that I wouldn't if it were obvious, it's just that it isn't). Then you guys can have fun finding the real exploits once this one's closed.
Calm down, Marcan. Sure, he's killed a small exploit and opened the gate again for wads again, but it's not all that bad that you should threaten to stop development later on.marcan said:You do not seem to understand the phrase "last resort".noobwarrior7 said:you think IOS16 was the big bug/last resort they mentioned? I kinda doubt it, because it relies on distributing copyright nintendo code, which they never do...and also, it won't be a viable option for a lot of people.
If (say, in 9 months) get to the point where Nintendo fixed all the known holes and we couldn't find new ones over some time, then maybe we'd consider IOS16 as an option.
Now, if that happens, I guess we'll just take a nice long vacation from looking for holes.
Sure, we have more exploits, but they won't last forever. We have big bugs. The last resort (IOS16) wasn't one of them. It was a (shitty) last resort. Which you've just killed.
This crap makes me want to release BootMii in such a way that somehow, someway, it's useless for the WAD crap (don't think for a second that I wouldn't if it were obvious, it's just that it isn't). Then you guys can have fun finding the real exploits once this one's closed.