Hacking [Video] First Wii U Homebrew Game [Pong]

  • Thread starter Thread starter Relys
  • Start date Start date
  • Views Views 37,887
  • Replies Replies 116
  • Likes Likes 50
I hope the current firmware version will be supported again one day because that would be useful to many people including me.

I might stop updating now since it's getting worth it. :)
 
beforeload-iframe? I sure hope that's the one, it works on latest which is very nice.

It's a different one, but we're currently trying to use the kernel exploit to install exception handlers so we can get a crash log of the exploit we're using which also works on the latest version.
 
beforeload-iframe? I sure hope that's the one, it works on latest which is very nice.


We have a few that work on the latest version which are being tested. It's not beforeload-iframe, though I believe it behaves similarly. As NWPlayer123 said, we plan to use our kernel exploit to create a nice debugging environment for the browser and see exactly how it behaves. That should make it much easier to turn the bug into an exploit.
 
We have a few that work on the latest version which are being tested. It's not beforeload-iframe, though I believe it behaves similarly. As NWPlayer123 said, we plan to use our kernel exploit to create a nice debugging environment for the browser and see exactly how it behaves. That should make it much easier to turn the bug into an exploit.

Well kudos to you for prioritizing porting to latest FW. So the IOSU exploit in question still needs a way to be loaded right now? Or am I still not quite up to speed? :P
 
  • Like
Reactions: Fpsrussia117
Well kudos to you for prioritizing porting to latest FW. So the IOSU exploit in question still needs a way to be loaded right now? Or am I still not quite up to speed? :P

No, as has been stated many times in the past, the only requirement for an IOSU exploit is the ability to run code. A kernel exploit is not a prerequisite.
 
No, as has been stated many times in the past, the only requirement for an IOSU exploit is the ability to run code. A kernel exploit is not a prerequisite.

Ah, makes sense. Sorry, it's very very hard to keep up with things when the progress thread is so full of... not progress. :P
 
  • Like
Reactions: NWPlayer123
So is Hykems plan to use fof's iosu exploit (since his console is on very low firmware)? Then from there work his magic on dumping the rest of the keys? Or does plan on finding & making his own iosu exploit?

I hope he manages to defeat the bootloader :blink:
 
Dude... Please tell me you're kidding...
I decided that he MUST be trolling! That or ignorant. If someone were to make a rom/backup loader it would be because of their own desire, not because of requests by users who can't do it themselves. People are hilarious sometimes.. SMH!
 
So is Hykems plan to use fof's iosu exploit (since his console is on very low firmware)? Then from there work his magic on dumping the rest of the keys? Or does plan on finding & making his own iosu exploit?

I hope he manages to defeat the bootloader :blink:


The plan is using the IOSU exploit on a low firmware unit to dump the rest of the keys first. The reason for this is the fact that one of the missing keys allows you to decrypt the IOSU code (fw.img) on your computer, similar to what can now be done with the kernel code (kernel.img).
From that point on, it will be possible to just get the IOSU code from every single firmware version and analyze internal patches from Nintendo. I already have an exploit plan that should, in theory, work. If it happens to actually work across all firmware versions, then it's done, the Wii U is "fully" hacked up to the latest firmware.
Of course, there's still the bootloader missing, which not even Fail0verflow managed to defeat.
 
The plan is using the IOSU exploit on a low firmware unit to dump the rest of the keys first. The reason for this is the fact that one of the missing keys allows you to decrypt the IOSU code (fw.img) on your computer, similar to what can now be done with the kernel code (kernel.img).
From that point on, it will be possible to just get the IOSU code from every single firmware version and analyze internal patches from Nintendo. I already have an exploit plan that should, in theory, work. If it happens to actually work across all firmware versions, then it's done, the Wii U is "fully" hacked up to the latest firmware.
Of course, there's still the bootloader missing, which not even Fail0verflow managed to defeat.
And then what? Do you guys have any plans for the time after that (Custom firmware, SNEEK-like emuNAND, removing region lock, homebrew channel, etc)?
 
And then what? Do you guys have any plans for the time after that (Custom firmware, SNEEK-like emuNAND, removing region lock, homebrew channel, etc)?
I think these guys will need a well deserved break after all of this. What we need is a team of homebrew developers to come out of the shadows and get things going with. homebrew. I have a feeling there are plenty of them out there. Probably waiting for a proper method of running code(outside of userspace). Once the dev 'team' releases their work, shit will blow up. Hykem will eventually be the key to a permanent exploit or at least be the one to defeat all of Nintendo's future patches. Well, maybe not always him specifically, but his work.
 
  • Like
Reactions: TeamScriptKiddies

Site & Scene News

Popular threads in this forum