What the hell are you all arguing about? My post was clearly misunderstood somehow, so let me try again...
No one was lied to, I never stated anything contrary to what NWPlayer123 had stated before.
The 5.3.2 bug is real, causes a controllable crash and gives us a nice heap overflow. That's enough to be confident that it can be turned into an exploit on the Wii U. Plus, I've personally confirmed that the heap overflow is consistent and reproducible (via crash logs).
That's more information that I should even share, since it's still a work in progress. Either way, it's safe to update to 5.3.2 because it's vulnerable and it's pointless to remain on an older firmware version when you can update and keep using your Wii U normally until you wait for the exploit.
The work being done on firmware 3.0.1 has nothing to do with this. I'm exploiting this firmware because it's closer to the firmware version that was exploited by comex some years ago.
Essentially, firmware versions from 2.0.0 (first installment of the Internet Browser) to 3.1.0 (last version before the WebKit's source was updated) are great entry points for an IOSU exploit, mainly because very little changed across them. After firmware 4.0.0, major changes were applied and my ultimate goal is to find if the original IOSU exploit still exists and, if not, to find a new one so the Wii U can be fully exploited up to it's latest firmware version.
I'm merely re-tracing fail0verflow's steps at this point. The goal is to fully hack the Wii U again on the latest firmware version.