Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,121,198
  • Replies Replies 21,104
  • Likes Likes 29
Kernel exploit for 5.4.0 is already public, all you need is the browser exploit to use it.
Yeah, I know. The question is rather when the browser exploit for 5.4/5.5 will go public and when the new kernel exploit for 5.5. If we get the browser exploit first, than it would be better to stay on 5.4. Otherwise it wouldn't do any difference so that we (I) could update to 5.5. That's what I wonder atm. ;)
 
Yeah, I know. The question is rather when the browser exploit for 5.4/5.5 will go public and when the new kernel exploit for 5.5. If we get the browser exploit first, than it would be better to stay on 5.4. Otherwise it wouldn't do any difference so that we (I) could update to 5.5. That's what I wonder atm. ;)

The last public exploits were mainly released because nintendo patched them in new updates, the bug for the browser exploit in 5.4.0 is already public, so it's very likely that nintendo will patch it in a later update, however nothing guarantees a release of the kernel exploit for 5.5.0 any soon.

But if you're waiting for what Hykem is planning to release, he said he's IOSU exploitation will work up to 5.5.0, so that should give you more than what 5.3.2 uszers already have, but when is it coming out ? we don't know ^^, we only know Hykem is working on it and he doesn't plan to keep it private once he's done.
 
When IOSU was 100% finished and released surely that kernel exploit will be released too, just be patient.
Has no reason to hold Kernel Exploit 5.5 and release IOSU 5.5, i think everything will release at same time.
If Nintendo release a new firmware wait until devs (especially hykem) say it's safe to update.
 
Last edited by Antonio Ricardo,
I'm just getting into the Wii U hacking scene, and I'd to verify some information.

> 5.1.2U is vulnerable to the IOSU exploit supposedly being built for <5.2.0FW, and I should stay on it.
> NANDWay can backup the Wii U NAND chip, and there's no e-fuses to get in the way of a NAND restore for downgrading purposes
> You have to backup both the NAND (Wii U side) and eMMC to have a complete, restorable backup to earlier firmware
> Hardware downgrading has been tested and it works as expected.
> The Webkit entrypoint needed to install the IOSU exploit (I assume) will be released for 5.1.2 as well when the IOSU exploit is released, or is this firmware unsupported?

Thanks for any answers in advance!
 
I'm preparing to buy Super Mario Maker, just got to have it at this point. Can I buy Super Mario Maker on eShop and play it fine with spoofed 5.3.2? Is the spoof really safe? It's scary since it's permanent.
 
I'm preparing to buy Super Mario Maker, just got to have it at this point. Can I buy Super Mario Maker on eShop and play it fine with spoofed 5.3.2? Is the spoof really safe? It's scary since it's permanent.
Spoofing is relatively safe (no bricks I know of), not sure about the rest. Should work though, using nnu-patcher.

You can stil update the wii u after spoofing, so be sure to read everything if you decide to try if you don't want updated.
 
I'm just getting into the Wii U hacking scene, and I'd to verify some information.

> 5.1.2U is vulnerable to the IOSU exploit supposedly being built for <5.2.0FW, and I should stay on it.
> NANDWay can backup the Wii U NAND chip, and there's no e-fuses to get in the way of a NAND restore for downgrading purposes
> You have to backup both the NAND (Wii U side) and eMMC to have a complete, restorable backup to earlier firmware
> Hardware downgrading has been tested and it works as expected.
> The Webkit entrypoint needed to install the IOSU exploit (I assume) will be released for 5.1.2 as well when the IOSU exploit is released, or is this firmware unsupported?

Thanks for any answers in advance!

The IOSU exploit for 5.2.0 should work on 5.1.2, but there isn't really an impetus for us to backport the browser exploit to that version. Don't worry, we are working on various other IOSU attacks for more recent versions. ;) I don't know much about the progress on hardware NAND dumping, nor do I believe it's been tested, but you would likely need both the Wii U NAND and eMMC for a true downgrade. It may be possible to just downgrade OSv10 (on NAND) and keep other apps (on eMMC) at their latest versions, but this is less likely to be successful.
 
  • Like
Reactions: Apostrophe
The IOSU exploit for 5.2.0 should work on 5.1.2, but there isn't really an impetus for us to backport the browser exploit to that version. Don't worry, we are working on various other IOSU attacks for more recent versions. ;) I don't know much about the progress on hardware NAND dumping, nor do I believe it's been tested, but you would likely need both the Wii U NAND and eMMC for a true downgrade. It may be possible to just downgrade OSv10 (on NAND) and keep other apps (on eMMC) at their latest versions, but this is less likely to be successful.
Alright, then you're confirming that the IOSU exploit being worked on also runs on 5.2.0FW, not just below? From what I've seen, only SSBU V1 has 5.2.0 FW, and is difficult to find. If needed, I'd be willing to contribute in any way I can to back porting the exploit to 5.1.2, as it's reasonably easy to find a B version MarioKart 8, which is what I used to update from my original 2.1.0FW. I'm actually in electronics engineering though, so code might not be my best contribution, but I can set up any debug tools needed on my Wii U to help out, including any hardware debug, like serial terminal output or otherwise. Else, I'll just backup everything on a hardware level and update to 5.3.2FW in hopes of a future release.
 
Could someone, in some easy to understand explainitlikeimfive sentences, describe what actually is expected from this hack that everybody is waiting for? Like, give me an example on how the process might look like when it comes to getting the hack onto the wiiu and how loading backups might work. Give us something so we can visualize it! (I'm sure I'm not alone)
 
Last edited by Cyanopsis,
Could someone, in some easy to understand explainitlikeimfive sentences, describe what actually is expected from this hack that everybody is waiting for? Like, give me an example on how the process might look like when it comes to getting the hack onto the wiiu and how loading backups might work. Give us something so we can visualize it! (I'm sure I'm not alone)
well once we have iosu acess we can make a real homebrew channel wich would stop all the bowser stuff and we would have easy usb acess too.
 
Could someone, in some easy to understand explainitlikeimfive sentences, describe what actually is expected from this hack that everybody is waiting for? Like, give me an example on how the process might look like when it comes to getting the hack onto the wiiu and how loading backups might work. Give us something so we can visualize it! (I'm sure I'm not alone)
Check the wii hacking scene, that's a close visualization of what it would be like to exploit the IOSU ;).
 
Implementing fw 5.1.1 to 5.3.1 into libwiiu would be nice for many people I'm sure!
That could be a starting point for you! :) Testing could be difficult though! ^^'
According wiiubrew the browser is the same from 5.1.1 up to 5.3.0 (NX/3.0.3.12.14) so the same exploit should work (the webkit exploit for 5.3.2 should be adapted), while for 5.3.1 and 5.3.2 is NX/3.0.3.12.15. Maybe this explains the video showing loadiine running on 5.3.1 :)
 
According wiiubrew the browser is the same from 5.1.1 up to 5.3.0 (NX/3.0.3.12.14) so the same exploit should work (the webkit exploit for 5.3.2 should be adapted), while for 5.3.1 and 5.3.2 is NX/3.0.3.12.15. Maybe this explains the video showing loadiine running on 5.3.1 :)
So wait, if the IOSU exploit is being adapted for 5.2.0 and below firmwares, and 5.2.0 shares the same browser as 5.1.2, then why would I need to develop a stand-alone Webkit adaption? The only thing I might need to do is help find any differing kernel addresses, or at least that's how I'm interpreting it.
 
So wait, if the IOSU exploit is being adapted for 5.2.0 and below firmwares, and 5.2.0 shares the same browser as 5.1.2, then why would I need to develop a stand-alone Webkit adaption? The only thing I might need to do is help find any differing kernel addresses, or at least that's how I'm interpreting it.
That's the point!
Most people didn't bother finding out all the addresses and if you ported it over to the OS version you have, it would benefit you and all the people who are on the same fw!
I suggested the implementation because it is something that is missing in the whole package and something that came to my mind! :P
 

Site & Scene News

Popular threads in this forum