@damysteryman FIX94 is right, the new IgnoreKKey patch still fails on a real Wii.
How about adding the FixTicket function from WAD Manager to IOSPatcher.c? That way, the installer will be able to replace the common key index byte to "00" in the memory array right before installing the IOS236.
I have tested it and it works fine, I just wanted to point this out.
Code:
/* Avoid -1029 error on vWii installation */
u8 *data = (u8 *)ios->ticket;
u8 *ckey = data + 0x1F1;
if (*ckey != 0)
{
printf("Setting common key index to 0 (fixes error -1029)...\n");
*ckey = 0;
tik_dirty = true;
}
_____________________________
@ damysteryman: I STILL get "Could not identify ES module" error followed by "IOS236 installation failed" when trying to install your latest (v7) patched IOS36 into slot 236.
You didn't even respond to one of my previous posts related to file size differences of dumped IOS36 WAD files.
Some other people also mentioned that they had the same or similar issues.
There has to be more investigation on this case IMO.
That's probably a bug in ShowMiiWads. Have you tried using BlueDump?
The installation has *worked* for me, but I didn't use any of those tools to generate the IOS36 WAD.
Instead, I just used a hex editor to lookup the shared contents in the content.map file, based of the TMD information. Then, I proceeded to manually encrypt them with OpenSSL and generate the WAD by adding the data
in the correct order. I also changed the byte 0xC31 to "00", in order to avoid possible -1029 errors (that byte shouldn't be "02", in any case, since the WAD is now encrypted using the "normal" common key instead of the Wii U specific one).
My WAD is also 1.871.040 bytes in size.
CRC32: D8EFD4A0
MD5: 0F14BED8BC13B8C8DD4CC7BCB44DC93D
SHA-1: 2FFA52BD9430337DAE4269CF825C915F5BF7CBA4
Hope that helps.