Hacking The Definitive Guide to Wii U Hacking

[the_randomizer]

Idk, what's the guide say? The only extra steps are exclusions for virus scanners and allowing the programs through your firewall.

Right, I understand that, but only on the Windows side of things, doesn't the Wii U still need to connect to my PC via Mongoose though?

I don't think I'm thinking straight...

Edit: Yup, saw it, sorry, long day ><

Also, @Summersett

Do you think we could add Fix94's VPad to GC driver to this at some point?

 

[fiveighteen]

Also, @Summersett

Do you think we could add Fix94's VPad to GC driver to this at some point?

It's hard to support something I don't have first hand experience in installing. That being said, I'll try to add it into the guide soon if I can find some good instructions/video, since it's super cool and a very useful hack. My wavebird wants a GC adapter for Christmas

 

[TotalInsanity4]

My wavebird wants a GC adapter for Christmas

Same, except mine's a Pelican (the amazingly comfortable white ones)

 

[the_randomizer]

It's hard to support something I don't have first hand experience in installing. That being said, I'll try to add it into the guide soon if I can find some good instructions/video, since it's super cool and a very useful hack. My wavebird wants a GC adapter for Christmas

Fix94 did add info on how to set it up, I think https://gbatemp.net/threads/gc-to-vpad-replace-the-gamepad-input-with-the-gamecube-adapter.398074/ and https://github.com/FIX94/gc-to-vpad I dunno, just an idea really

 

[fiveighteen]

+Compiled and added GC-to-Vpad (no guide yet).
+Actually added WUP Installer to the DefinitivePackage this time (missed it last night)
+Fixed my index.html (WUP Installer was pointing to frame.html instead of payload532.html. Crediar's uses PHP but PHP won't load with Mongoose free)
+Fixed NUSGrabberv1.7 since it needed a certain folder structure that I messed up in the previous upload

@FIX94, what is OS Report supposed to do? I get a bunch of junk on my screen when I try to run it.

 

[FIX94]

@FIX94, what is OS Report supposed to do? I get a bunch of junk on my screen when I try to run it.

where the hell do you see OS Report?

 

[fiveighteen]

where the hell do you see OS Report?

http://fix94.no-ip.org/wiiu/kernel/ -> OS Report

 

[mariogamer]

I think this guide have to be declared as sticky (its s really good).

 

[FIX94]

http://fix94.no-ip.org/wiiu/kernel/ -> OS Report

Well since that is my private testing site you cant expect everything to work for everyone That will patch my (3.1.0) OSReport function so I can basically see all the debug prints the wiiu does via TCPGecko which can be pretty useful.

 

[fiveighteen]

I think this guide have to be declared as sticky (its s really good).

Thanks! I wouldn't argue with a sticky since I constantly see the same questions being asked that are always answered here lol

Well since that is my private testing site you cant expect everything to work for everyone That will patch my (3.1.0) OSReport function so I can basically see all the debug prints the wiiu does via TCPGecko which can be pretty useful.

I know; I didn't expect it to work, just was curious what it was supposed to be for when I came across it. Sounds pretty handy.

 

[vehe]

Really great guide.
would like to see it in the sticky with all the new Loadiine explosem thats going to happen now.

 

[fiveighteen]

Really great guide.
would like to see it in the sticky with all the new Loadiine explosem thats going to happen now.

Thank you! I'll have Loadiine support and downloads in the guide soon™ (most likely tonight, otherwise Sunday or Monday night).

I also want to dump some memory while running a SNES VC game and try to find the rpx or config files to get some progress going for that.

 

[ViolentRockstar]

Just read that MN1 had a 5.5.0 exploit held privately. Hope it will be released soon

 

[Deleted member 342493]

Well, I tried 3 times to run the kernel exploit but I didn't have luck, always says "Race attack failed " , I heard FIX94 have a better exploit, should I use the that exploit, or keep trying with the official WiiULib one?
Thank you in advance !

 

[Maximilious]

Well, I tried 3 times to run the kernel exploit but I didn't have luck, always says "Race attack failed " , I heard FIX94 have a better exploit, should I use the that exploit, or keep trying with the official WiiULib one?
Thank you in advance !

The newest one will kick you out after you get a Race Attack message, and allow you to try again without restarting the system. You only need to enter and exit system settings and retry again.

 

[Deleted member 342493]

The newest one will kick you out after you get a Race Attack message, and allow you to try again without restarting the system. You only need to enter and exit system settings and retry again.

Enter to the system settings? I didn't know that :facepalm: all right, I will try it now, thanks .

EDIT: It worked, thanks again!

 

[fiveighteen]

Just read that MN1 had a 5.5.0 exploit held privately. Hope it will be released soon

Don't count on it too soon. This sums it up nicely; parenthesis mine:

The hacking team has an exploit for 5.5.0 now, they will release it in one of these conditions :
- The exploit gets patched on a newer version
- They find another exploit
- There is a very high demand in the homebrew community, meaning there are more people who are willing to contribute and make/port homebrew. (WUP Spoofer, Loadiine, and GC-to-Vpad are good steps)
- They find some kind of an emunand based solution or a better way to solve firmware updating problem. (WUP Spoofer is a good step)

If you are in 5.5.0 and want to use homebrew soon on your wii U, I would suggest you to block auto-updating asap, at least you still got a hope, but there is no guarantee a later version would be exploitable.

Well, I tried 3 times to run the kernel exploit but I didn't have luck, always says "Race attack failed " , I heard FIX94 have a better exploit, should I use the that exploit, or keep trying with the official WiiULib one?
Thank you in advance !

Just for the record, the "official WiiULib one" CONTAINS Fix94's updates. He updated the libwiiu-master branch.

 

[the_randomizer]

Don't count on it too soon. This sums it up nicely; parenthesis mine:



Just for the record, the "official WiiULib one" CONTAINS Fix94's updates. He updated the libwiiu-master branch.

In other words, they won't release it because of the lack of interest in Wii U homebrew, so why should we bother getting hopes up at all? That's sure as hell the vibes I'm getting.

"We have the exploit but we're not gonna release it because bullshit." Gotcha.

If they're gonna keep waiting for firmware updates, they're gonna just keep delaying the release more and more, and frankly, Nintendo's not gonna stop releasing firmware for the Wii U anytime soon, so....

 

[fiveighteen]

In other words, they won't release it because of the lack of interest in Wii U homebrew, so why should we bother getting hopes up at all? That's sure as hell the vibes I'm getting.

"We have the exploit but we're not gonna release it because bullshit." Gotcha.

If they're gonna keep waiting for firmware updates, they're gonna just keep delaying the release more and more, and frankly, Nintendo's not gonna stop releasing firmware for the Wii U anytime soon, so....

Incorrect. Let me break this down. Keep in mind that the main reason it's not released is because Nintendo is all but guaranteed to have it patched in the very next update. If there's only ONE exploit we don't want Nintendo to find out about it because then when it's patched in the next FW, we won't have any exploit to port to that version and we'd have to start all over. (by "we" I mean MN1 and team )

They will release it in one of these conditions :
- The exploit gets patched on a newer version (if it's already patched in the next FW, it can be released since that's the reason it's not being released anyways)
- They find another exploit (if there's a #2 exploit, then #1 can be released for the homebrew community to enjoy. We know it would be patched in the next FW, but hopefully exploit #2 could be ported)
- There is a very high demand in the homebrew community, meaning there are more people who are willing to contribute and make/port homebrew. (if there are so many people contributing that it's really hurting the scene to hold it back, that defeats the purpose of having the exploit in the first place. We would need more devs then just the ~5 that we currently have though)
- They find some kind of an emunand based solution or a better way to solve firmware updating problem. (with emuNAND, it doesn't matter what Nintendo does because all they could do is update the real NAND. Spoofer is good for now, but it's likely to get patched in the next update)

 

[oumoumad]

In other words, they won't release it because of the lack of interest in Wii U homebrew, so why should we bother getting hopes up at all? That's sure as hell the vibes I'm getting.

"We have the exploit but we're not gonna release it because bullshit." Gotcha.

If they're gonna keep waiting for firmware updates, they're gonna just keep delaying the release more and more, and frankly, Nintendo's not gonna stop releasing firmware for the Wii U anytime soon, so....

Sometimes I think you're not the same person using this account, I mean you've been present in the scene for longer than me, you'll definitely be able to understand the decisions of the developers for releasing the exploits. So far it's been successful. Look at the hacking scene, the moment IOSU exploit comes out, all people would have the possibility to use it since so far the team is ahead of nintendo. And everyone will be able to enjoy all this awesome stuff that came out, and more to come !