There is a small possibility of the 5.5 webkit exploit used for this being very unstable, and -possibly- even not working at all
Is this just your thoughts on the matter or do you have inside-ish info that confirms 5.5 may "-possibly- even not work[ing] at all"?
A phrase like that is going to scare lots of folks round these here parts.
That's fair. I mean he said "firmware versions 5.4.0 and 5.5.0 still need to have a proper exploit done. This is being worked on as well"Well... I know there exists a 5.5 kexploit which uses webkit entrypoint and Hykem says he uses a different webkit exploit than the kexploit on 5.5 soooo... I'm more inclined to believe Hykem will support 5.4/5.5 but he may run into trouble getting it to work *shrug*.


You guys are overthinking this. Hykem's IOSU uses existing webkit userland exploits. There does not yet exist a webkit exploit for 5.4+ that could be considered ready for public consumption. I assume stagefright has been scrapped, and Matt and Mn1 have moved onto working on another. It's also possible Hykem joined them to try and complete it. There would be no point in porting IOSU to a firmware with no webkit entry point.
Hykem says he uses a different webkit exploit than the kexploit on 5.5 soooo...
"But won't emuNAND be blocked like the N3DS?" you say. No, the Wii-U doesn't have the extra hardware that the N3DS has to create the required on-boot key verification, so the chances of emuNAND being blocked are basically zero.
Just hopping in briefly to point out that so long as we don't have the boot1 "common" key, access to future system versions through emunand isn't 100% guaranteed. Basically, N can ship a boot1 update that makes some arbitrary change to IOSU ancast image decryption. This would make it impossible to have newer IOSU versions, and, and newer PPC-side stuff would likely have dependencies that older IOSU versions wouldn't support.
As it stands, IOSU maintains access to its ancast key since it's used to decrypt cafe2wii and (though i'm not sure when/if this is used on retail yet) to decrypt and reboot into another normal IOSU ancast image. If they shipped every update with IOSU and boot1 as a pair, they could have a new IOSU key for every system version. boot1 is already being updated with nearly every system update as it stands, so this wouldn't be unreasonable. If this was done, even if one version's key was leaked it wouldn't help future versions get emunand support.
Of course even if they did this, someone could sit on a private IOSU exploit/the boot1 "common" key and just release IOSU keys every update. You should hope to god this is some cool community member and not a piracy company trying to turn a profit.
tl;dr you probably won't be able to update emunand forever and whoever still has their own hax will be the only one(s) to really be able to help out with that.

5.3.2You think Hykem is using a 5.4+ system? Heh. Also mentioning PPC kernel here is irrelevant because this is apparently a straight jump to IOSU from the initial attack.


Actually depending on how Fix94 and Co. go about it, we could potentially have GameCube games rendered in full 1080p as long as the textures are high enough resolution1080p upscaled*
And since when does an exploit remove online? Just spoof to 5.5.0.
Isn't that what dolphin does?Actually depending on how Fix94 and Co. go about it, we could potentially have GameCube games rendered in full 1080p as long as the textures are high enough resolution

Less than ideal considering HD texture packs take effort, and we can't have that now can we?Actually depending on how Fix94 and Co. go about it, we could potentially have GameCube games rendered in full 1080p as long as the textures are high enough resolution

Precisely, except this would be running on native hardware so theoretically there shouldn't be as big of a performance hitIsn't that what dolphin does?

That feels GREAT to hear.5.5 is the new 9.2.

I would say 5.3.2 is the new 9.2 if it weren't for us 5.5.0 users getting a second chance so fastThat feels GREAT to hear.



