Hacking Having a weird problem with the hackMii installer on the vWii of a Wii U.

[KhX-3]

Well, this one certainly takes the cake in all of the messing around I've done with Homebrew Channel....

First thing I should mention is that this isn't my first dance with HBC and the HackMii installer on a Wii. I own a regular Wii and I've done a lot to it over the years. Everything I've ever wanted to do worked just fine on it, for a very long time.

However, I just got a Wii U, and so far, it's been a completely different story. Now I'm in a huge jam and am seriously worried there is no way to fix what's happened, here.

First thing I did was to use SmashStack to boot up the HackMii installer on the virtual Wii of the Wii U. Worked like a charm, at first....

Then I had trouble running some forwarders, so I decided it was time to fix that up with some IOS installing. Here's where the problem comes in. So I installed the IOS's all fine and dandy, then found that some forwarder Wads weren't properly installing. Curious. So I switched to IOS236, and that did it... or so I thought. They installed.

So, while on IOS236 I backed out of MMM, intending to go back to the System. Complete freeze. Let it sit there for about 20 minutes. Nothin'. Tried the Wiimote, tried the buttons on the system, nothing. Something about this did NOT like that IOS I was on, that installed the forwarders (it was for the NES and SNES emulators I use, if you want to know). But being on this IOS, gave me that crash that froze everything. Had no choice but to just turn the whole system off.

So, I figure I would head back to the Homebrew Channel, and... black screen. Wha? Tried it about 3 more times. Just a black screen and nothing.

I started panicking at this point. Seems Homebrew Channel has completely frozen and locked up. Tried re-installing HackMii from SmashStack, go into created stages, the whole 9 yards, everything is fine up until the "Scam Warning" message, where it sits there, not doing anything. "Press 1 to continue" dosn't come up, or anything. I let it sit there, giving it the opportunity, nothing.

So, now I find myself unable to use Homebrew Channel, at all, to fix anything, and I find myself unable to re-install it. Is there ANYTHING that can be done?? Can't load the channel, can't re-install the channel. Is this it for me? :/ Dunno what the heck happened. Try as I might, I can't figure it out, aside from something about IOS236 made everything go heywire, causing the installer to not be able to patch itself, and unable to change the IOS, if it is, in fact, IOS236 causing this calamity. Am I up a creek, or what? :/

----UPDATE----
So, after searching around for a bit, I find this tidbit of info: "Hackmii installer freezing at the scam screen is caused by ios30-v1040 - ios35-v1042 being installed on a wii that will not function with those ios. The hackmii installer tries to load ios30-ios36 and the ios crashes resulting in the freeze. Simple fix, install cios30-v6174 -ios36-updated and the issue is fixed"

Uhhh. Uh oh. Since my Homebrew Channel that loads these things like cios installers, now cannot load past a black screen, and I cannot re-install, I have this sinking feeling, that by one sheer, quickly remarkable mistake in under only 5 minutes, I have completely and utterly fucked myself, somehow. ...so basically, in trying to teach a dog to sit, i've deleted the dog's legs, so the dog can't sit OR get up to sit back down. :/

 

[KhX-3]

Sooo.... It's been about a day since I had this problem, (has this ever happened to anyone else like this?), and i've tried all sorts of things, since then.

Since I have no way to actually get into the vWii properly, since I keep getting a frozen screen on the scam warning of the HackMii installer, and the Homebrew Channel that did work for a while until I switched the IOS now just leads to a black screen.....

I have tried multiple methods of loading the installer, other exploits. Nothing.

I tried DOP-Mii WiiBrew Edition to fix the IOS instead of trying to run HackMii in it's place (since there are no vulnerable IOS's to patch... or so it's telling me), but all that manages to do is say that the boot.dol is failing to load. All kinds of different exploits, and all kinds of ways to get it repair any.all IOS's that just backing out of MMM seems to have done... In desperation, and being completely at my wits end, I even renamed the DOP-Mii file to boot.elf. I did this, because the error messages were telling me that "Boot.elf" was not found when I tried this, instead of bypassing boot.dol like it wasn't even there. (I know that REALLY wasn't going to change anything... I just thought it was briefly worth trying. It just THEN said that "boot.elf wasn't valid", anyway.)....

So None of the exploits work, the HackMii installer keeps freezing, and the HBC still keeps going to a broken black screen. Now the question i'm left with is.... why did my IOS's stop working, in the first place, anyway? In the span of the 4 minutes since it worked, and since it stopped working, I hadn't fiddled with the IOS's, or delete any of them, or really change anything since backing out of MMM froze everything, and all the problems began.

Honest to god for the life of me, I can't figure out what I did wrong, why it blew up so soon after it seemed like it worked, and why no method i've searched for, or read about has gotten me any further past the square one I quickly find myself at?

Is it really just that switching to IOS236, and then backing out of MMM, just destroy everything entirely? Any help or comments would be appreciated... even if someone could, from the evidence gathered, let me know if I truly fucked everything over beyond repair somehow, even that'd be appreciated. It's just driving me insane, now.

---UPDATE: I just tried HackMii installer's older versions wondering if THAT would do something, as someone elsewhere suggested when I googled it. ....nothin'. It REALLY seems as if switching over to IOS236 in MMM, and then backing out of MMM to the system, just fried everything. I don't know how. It wouldn't make any sense. But that's the only thing I did different. :/

(edit: Oh, by the way, I apologize if I posted this in the wrong place, talking about Wii hacking when I clearly meant vWii hacking. That one distinction I now know is a bit different, since apparently people are saying that the IOS's for the vWii are different than regular Wii. Even so, it's not like I did anything TO the IOS, aside from just backing out of MMM after setting to another one. So It just seems odd to me that this one thing can put a halt to everything I tried to do.)

 

[rooskie54]

Well "I decided it was time to fix that up with some IOS installing" is where your problem started. IOSes for Wii and IOSes for vWii aren't the same thing. Your only hope is to replace the ones you installed with the original versions. This has two problems:

1. You have to get the IOSes you over wrote. If you didn't make a NAND backup that you can extract them from then it's complicated to get them.
2. You have to get a wad manager to load and work properly without the homebrew channel.

I've seen similar stuff come up in the WiiU hacking section and the solutions weren't pretty. Hopefully someone from those sections that knows what to do sees this.

 

[KhX-3]

Ohhh, that may have done it. Yeah, I almost forgot I basically replaced one IOS with the regular version that the regular Wii uses, thinking they were more or less the same between systems.

Come to think of it, when it wouldn't load the ticket and install my forwarder until I switched it to the IOS236 (which then worked), the IOS I replaced, IOS58.

So, is it fair to assume that the exact problem here is that the vWii's "IOS58", and the regular Wii's "IOS58" are incompatible and caused the lock-up on both the installer AND the HBC that was there? the vWii's "IOS58" is absolutely necessary? I see, I am starting to understand what the problem is, and why I may not be able to fix it. Getting the vWii to load and work properly without the HBC, as you said, is just resulting in errors, so I may be screwed, unless someone knows a more complicated, roundabout way to get around it. Hmm.

Thanks for the reply, man. At least now I am starting to see where I went wrong and why. sigh.

 

[Heran Bago]

I got nothing to add but I hope you get that figured out.

 

[rooskie54]

Ohhh, that may have done it. Yeah, I almost forgot I basically replaced one IOS with the regular version that the regular Wii uses, thinking they were more or less the same between systems.

Come to think of it, when it wouldn't load the ticket and install my forwarder until I switched it to the IOS236 (which then worked), the IOS I replaced, IOS58.

So, is it fair to assume that the exact problem here is that the vWii's "IOS58", and the regular Wii's "IOS58" are incompatible and caused the lock-up on both the installer AND the HBC that was there? the vWii's "IOS58" is absolutely necessary? I see, I am starting to understand what the problem is, and why I may not be able to fix it. Getting the vWii to load and work properly without the HBC, as you said, is just resulting in errors, so I may be screwed, unless someone knows a more complicated, roundabout way to get around it. Hmm.

Thanks for the reply, man. At least now I am starting to see where I went wrong and why. sigh.

That will do it. The homebrew channel prefers to use IOS58, which is always present on vWii. The homebrew channel chooses which IOS it will use when it's installed, and it picked 58 at installation, so working 58 means...well you've seen first hand what it means. Running the hackmii installer to reinstall the homebrew channel won't be an option until you can get your IOS problem fixed. The hackmii installer scans all of your IOSes for vulnerabilities, and it basically shits itself if the right IOSes aren't there on a vWii.

 

[KhX-3]

...well shit.

sigh. Was planning to homebrew up my new Wii U, and thus sell my old Wii off. Not this time.

I suppose, unless anyone else has any ideas how to restore IOS58 without having the means to go in through HBC, in recognition of my lament, with seemingly no other recourse remaining to me, I may as well honor the fall of my Wii U-based vWii hacking adventures by way of composing a final haiku....

Love is now over
The cruelty of loss thus concludes.
Guess i'll keep that Wii.




.

 

[Cyan]

I'll close this thread, as it's not the correct section and there's an updated situation thread here :
http://gbatemp.net/threads/and-now-...-to-an-earlier-situation-and-a-warning.357956