So, we all know that kexploit 5.5.X has been leaked by an unknown source, so after working a little bit around it, I decided to compile a little tutorial how to make it work.
IMPORTANT NOTE: The Real Jdbye came up with a solution for EU consoles. This fixed version HaxServer may also work with US versions. Both links will be posted below.
For people who don't want to selfhost, have difficulty with this tutorial or simply want a quick access, go to the end of the tutorial.
Step 1: Downloading HaxServer
For this tutorial, you will need Java 8, HaxServer, and your port 80 opened on your router/firewalls and make sure nothing uses it (usually it's web servers).
1. Download the kexploit + haxserver (AtLongLast.zip) there:
http://www.mediafire.com/download/6jqfane80fqkavy/AtLongLast.zip
Note: If you have a EU console also get this link: https://dl.dropboxusercontent.com/u/8225581/HaxServer.jar
2. Make sure you have Java 8:
http://java.com/en/ (Skip this step if you do)
3. Open a command line window (in windows) or a terminal (linux/macosx).
4. Extract AtLongLast.zip to C:\kexploit (or wherever, but keep it short)
Note: For EU consoles, overwrite the HaxServer.jar with the one mentionned above in step 1.
5. Rename the folders as they are inverted. Example: atad = data; sdaolyap = payloads
6. From your command line, go to the folder where HaxServer.jar is and type: java -jar HaxServer.jar (For linux and MacOSX you will need elevated priviledges. Use sudo java -jar HaxServer.jar)
7. Type "ipconfig" and check your ipv4 (looks like: 192.168.xxx.xxx)
NOTE: You will see Exploits: 0; Data: 0; Errors: 0. Totally normal, those numbers will change as you initiate a payload (kexploit or apps). MAKE SURE to use the command line so you can see if there is an error. If not, the command line will report the payload you are loading.
Now we got it running and we got our IP address !
Step 2: Preparing your SD Card
1. Put your SD card in your computer.
2. Download loadiine or homebrew browser and extract the contect on your SD card making sure the elf file is in wiiu/apps/(application name). IT NEEDS TO BE THE EXACT FOLDER NAME !
3. Put whatever games you want if you go for loadiine or whatever apps you want. There are several tutorials for this.
4. Take your SD card out, and put it in your WiiU
Step 3: Running the exploit
1. Start up your WiiU and go to the internet browser.
2. So we'll load up the Kernel10 payload first. Clear your cookies, and input the URL:
http://192.168.XXX.XXX/hax?kexploit10 (Note that XXX is whatever you got from ipconfig). You will see the hack load.
3. It will return you to your the home menu, go back in the web browser and type:
http://192.168.XXX.XXX/hax?loadiine or
http://192.168.XXX.XXX/hax?launcher (or any other payloads you'd like to launch).
Et voila ! Exploit running.
IF IT CRASHES DON'T PANIC, you may get stuck at a video loading screen or getting a RaceAttack error, just shut down your console and redo the "Running the exploit" it may take a few tries.
You can also follow NWPlayer123 video tutorials here:
In case your get a "file not found" error, please refer to Mr.Rean tutorial here on how to selfhost without HaxServer over here http://rhcafe.us.to/?page=t&id=108
Remote Host:
If you have problems loading the exploit, or the payloads, or that you want a remote solution, prepare your SD card with the Loadiine and Homebrew Launcher. Then, simply put your SD card in and point your webbrowser to:
http://loadiine.ovh/
It will detect your firmware and give you the exploit choices you want to run and even have a automation system. I have yet to encounter a crash using this website.
FAQ
Q: I get "unable to access" error.
A: Instead of running HaxServer through command line (which is preferable), go to the icon, right-click and run as administrator. You should see a window with Exploits/Data/Errors.
Q: My WiiU freeze or I get a "Race attack" error...
A: This happens, the exploit is not stable. Reboot your wiiu and try again. May take several tries.
Q: I get "file not found" when trying to run HaxServer...
A: You are probably on a EU console. Check for the EU link for the hotfix.
re}
