Kernel exploit for 5.4.0 is already public, all you need is the browser exploit to use it.Hm, if there's already a hack for 5.5, so is there still any reason to stay on 5.4!?
Kernel exploit for 5.4.0 is already public, all you need is the browser exploit to use it.Hm, if there's already a hack for 5.5, so is there still any reason to stay on 5.4!?
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.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.![]()

Possibly it works also on 5.1.1-5.3.1?Kernel exploit for 5.4.0 is already public, all you need is the browser exploit to use it.
Possibly it works also on 5.1.1-5.3.1?

Spoofing is relatively safe (no bricks I know of), not sure about the rest. Should work though, using nnu-patcher.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 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!
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.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.
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 IOSUCould 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)
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.1Implementing 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! ^^'
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.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![]()
That's the point!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.
Ok thanks! So the work with the softmod for the wii was similar to that of the IOSU, in terms of work process?Check the wii hacking scene, that's a close visualization of what it would be like to exploit the IOSU.