This tool is for v5.5.1-v5.5.2 only (because of the HBL loader). OTP and SEEPROM are required, so it is only for previously hacked consoles with backup of those files. (If you installed redNAND before you should be able to dump those files from your SD)
(If you don't have OTP you can take the OTP from someone else because the USB key is the same).

This tool is very experimental, USE AT YOUR OWN RISK.
This tool is based on WFS File Injector.
Credit for @FIX94 for the Haxchi and for @dimok WFS Block Injector for the inspiration.

Instructions: (READ FIRST)

Preparing the USB

1. It is recommended to use a clean USB and format it for this process. The installer is expermintal and may corrupt the file system.
2. Buy and install one of the supported DS VC games, and move it to the usb.

Installing
Choose one of the following methods:

Method 1: Direct install to the USB (faster but more risky)

1. Connect the USB to your PC, and find out the drive index:
   Open PowerShell (WinKey + R, enter powershell)
   Run the command

   Get-WmiObject Win32_DiskDrive

   Find the DeviceID for your USB (Example: \.\PHYSICALDRIVE3)
2. Open command line with admin privileges (Start Menu -> Search for "Command Prompt" -> Right click wnd "Run as Administrator")
3. Go to the directory with the tool:
   

   cd <where you extracted the files from the zip>

4. Run the installer: (Don't forget to replace \.\PHYSICALDRIVE3 with the correct device)
   

   haxchi-pc-installer --image \\.\PHYSICALDRIVE3 --otp otp.bin --seeprom seeprom.bin

   And follow the instructions.

Method 2: Install on an image (safer)

1. Dump an image of the USB device with tool like Win32DiskImager.
2. It is recommended to backup the image.
3. Open ccommand line (WinKey + R, enter cmd)
4. Go to the directory with the tool:
   cd <where you extracted the files from the zip>
5. Run the installer:
   

   haxchi-pc-installer --image <dumped image file> --otp otp.bin --seeprom seeprom.bin

   And follow the instructions.
6. Flash the image back to the USB.

Finishing
Now just connect the USB back to the Wii U. If you run the game HBL should be opened instead.
Now with HBL access it is recommended to move the game back to the NAND and reinstall haxchi again with the regular Wii U installer.


Download (Source)

 

[EyeKey]

hello
Please help me
I have do all step but when a enter the code:
haxchi-pc-installer --image \\.\PHYSICALDRIVE4 --otp otp.bin --seeprom seeprom.bin
that done a error:Error: Unexpected WFS Version(bad key???)

Are you using the correct otp.bin seeprom.bin? How did you get them? have you ever did factory reset?

 

[tomcaliser]

Are you using the correct otp.bin seeprom.bin? How did you get them? have you ever did factory reset?

Yes from my sd card...before 5.5.2 i used Rednand,Mocha
And yes i have do a factory reset on my sysnand

--------------------- MERGED ---------------------------

i have used sdionander from dimok to dump a seeprom from my sd card that i have already used Rednand...
but it still do the same error WFS unexpected version

 

[EyeKey]

Yes from my sd card...before 5.5.2 i used Rednand,Mocha
And yes i have do a factory reset on my sysnand

--------------------- MERGED ---------------------------

i have used sdionander from dimok to dump a seeprom from my sd card that i have already used Rednand...
but it still do the same error WFS unexpected version

If you did factory reset after the dump, the seeprom has changed.
The rumors say that the usb seed is increased by one every factory reset, but I haven't verified it. The usb seed is in seeprom.bin at offset 0xB0-0xC0.
What does it mean increase by one? My guess would be the last byte. You can try to open seeprom.bin in hex editor and increase the byte at offset 0xBF by one.

Does anybody know how the usb seed exactly change at factory reset?

 

[piratesephiroth]

If you did factory reset after the dump, the seeprom has changed.
The rumors say that the usb seed is increased by one every factory reset, but I haven't verified it. The usb seed is in seeprom.bin at offset 0xB0-0xC0.
What does it mean increase by one? My guess would be the last byte. You can try to open seeprom.bin in hex editor and increase the byte at offset 0xBF by one.

Does anybody know how the usb seed exactly change at factory reset?

yeah

Well since the drive is completely encrypted with the seed you can't work around using that key to recover it. There is though a very simple trick to it I noticed. When you format your drive, your seed actually changes only on it's last number. The number seems to just be incremented.

Example:
If your seed was as following before you formatted:
12 34 56 78 90 12 34 56 78 90 12 34 56 78 90 12

After you format it the last number gets incremented. Meaning it will become something like this:
12 34 56 78 90 12 34 56 78 90 12 34 56 78 90 13

So since you have your current USB drive seed with the seeprom dumper, you can go ahead and decrement the number by one. Meaning if it is as following now:
12 34 56 78 90 12 34 56 78 90 12 34 56 78 90 13

You can change it back to and inject it:
12 34 56 78 90 12 34 56 78 90 12 34 56 78 90 12

There is a very good chance that you will hit the correct number by decrementing it and trying, maybe a few times. I think it depends on how often you formatted.

This was an observation on my end when I did format tests. I formatted 4 times and the number was increased by exactly 4. You could just go ahead and try it. Let me know if it worked for you.

 

[jde81]

would anyone be willing to make a video for this app? I tried to use the GUI that was made for it but its in a different language. I believe I have everything I need to get this working. If I could get back into my wiiu I even have a LEGIT DS game to use for Haxchi install

 

[tomcaliser]

THANK i will to test that so i tell you if that worked.

 

[tomcaliser]

*private seeprom info removed*

This was an observation on my end when I did format tests. I formatted 4 times and the number was increased by exactly 4. You could just go ahead and try it. Let me know if it worked for you.
But dont work for me

 

[EyeKey]

--------------------- MERGED ---------------------------

This was an observation on my end when I did format tests. I formatted 4 times and the number was increased by exactly 4. You could just go ahead and try it. Let me know if it worked for you.
But dont work for me

You need to increase it, not decrease.

 

[tomcaliser]

Nooooooo doesnt work...

 

[EyeKey]

Nooooooo doesnt work...

What was the original last byte and which bytes did you try? Did you increase it as decimal or as hexadecimal?

 

[tomcaliser]

95,i try 96,97,98,98,94,93,92,91,90.
But where i can see if I increase as decimal or hexadecimal?

 

[moops44]

DOESNT WORK FOR ME

FIRST STOP POST LIKE THIS and all the ascii art and cancer pictures!!!!
Thank you

The left side are Hex values
and you need to use HEX values
Hexadecimalsystem goes like this

Spoiler: HEXADECIMALSYSTEM

Hexadecimal/Decimal
0/ 0
1/ 1
2/ 2
3/ 3
4/ 4
5/ 5
6/ 6
7/ 7
8/ 8
9/ 9
A/ 10
B/ 11
C/ 12
D/ 13
E/ 14
F/ 15
10/ 16
11/ 17
12/ 18
13/ 19
14/ 20
15/21
16/22
17/23
18/24
19/25
1A/26
1B/27
1C/28
1D/29
1E/30
1F/31
20/32
and so on...

use a calculator like this http://www.binaryhexconverter.com/hex-to-decimal-converter

 

[tomcaliser]

OK OK thanks man,and sorry i ve got the picture cancer...

 

[moops44]

OK OK thanks man,and sorry i ve got the picture cancer...

look here how to calculate hex values
http://gbatemp.net/threads/wii-u-us...r-internal-memory.445514/page-63#post-6760674

 

[tomcaliser]

so i dosnt work

 

[EyeKey]

so i dosnt work

Try as a sanity check to dump the MLC from your redNAND, and run the exe on that file instead \\.\physicaldrive.. .
Just to check that you are using the correct otp and seeprom

 

[tomcaliser]

thanx but it's obligatory to have mlc?

 

[EyeKey]

No it is just a sanity check for the otp/seeprom, because you got them from rednand it should work with its mlc.
EDIT: oh nvm, the seeprom isn't used in mlc anyway

 

[tomcaliser]

But what i must to do to make a sanity checks?I don t know how to do that so explain please

 

[Corredor]

@tomcaliser has managed to install Haxchi. It was just an 'hexadecimal problem'. We can rely on @dimok 's observation: formatation just change the last byte (increase by 1).

Enviado de meu 6039J usando Tapatalk