InsaneNutter
Resident Nutter
Yes it's FAT32 formatted. I already had the "SD mount failed" error.
Here are the contents
View attachment 14801
Providing the homebrew_launcher.elf is in the homebrew_launcher folder that all looks correct. Like others are seeing the exploit is unreliable to essentially keep trying. After the first successful exploit launch it should be a lot more reliable. In previous posts I have listed a few tips you can try, as have other people.
I am starting to see there are multiple ways to exploit the console.
It looks like the majority of homebrew tutorials do require some kind of exploitable game.
I don't know how the exploit here differs or why no game is required with this exploit but I am wondering why it has to fail so many times before it succeeds.
Is there some kind of algorithm involved where it keeps trying to cycle through to identify a correct value and until it does the console will freeze?
Perhaps it remember that value thereafter which might explain why the exploit is more reliable once the initial exploit is applied?
Again any tutorial that requires a game is for the Wii not the Wii U, however some do work on the Wii U's "Virtual Wii" which is what i'm thinking is confusing you. Think of the "Virtual Wii" as like a Virtual PC, if you hack that you are not hacking the Wii U, just an emulated Wii.
The only currently released hack for the Wii U requires the web browser as an entry point.
As to why it's so unreliable, its a race attack, it's racing to exploit the Wii U before the Wii U blocks it from doing so, for a lack of a better way of explaining it. Once it's successful i presumed this is logged how the attack succeeded which is why is becomes a lot more reliable. I can't really explain any better as i don't know the technical details of how the exploit works, beyond that.

