If I added you then no, it's not necessary right now. I'd advise against it until something is ready for testing.I want to be a tester,but I'm on 5.4.
Do I have to update?Do it is necessary?
If I added you then no, it's not necessary right now. I'd advise against it until something is ready for testing.I want to be a tester,but I'm on 5.4.
Do I have to update?Do it is necessary?
In reality though, the more people working on an exploit (or exploits) the better - it allows for more entrypoints down the road and makes it easier for users to work with, as there's options.Hykem said to everyone that his IOSU exploit will work up to 5.5 (include 5.3.2), people still think that will work only on 5.3.2. LOL
@Hykem It would be cool to speak on this topic as is the progress because neither @Mathew_Wi know.
Hykem said to everyone that his IOSU exploit will work up to 5.5 (include 5.3.2), people still think that will work only on 5.3.2. LOL
@Hykem It would be cool to speak on that topic as is the progress because neither @Mathew_Wi know.
Most of the IOSU has been reverse-engineered and I'm still updating the wiki almost daily: http://wiiubrew.org/wiki/Special:RecentChanges
I already have an exploitable bug that should work up to firmware 5.5.0 and naehrwert is working on something too (currently for lower than 5.2.0 firmwares). When everything is ready it will be publicly released (at least on my end).
No clue what @Mathew_Wi is up to, but he did work with @Marionumber1 to get the 5.3.2 firmware exploit working (debugging via DevKit) and he found the MP4 bug test case that's being used to exploit 5.4.0/5.5.0 (which turned out to be a libstagefright bug, way before the controversial presentation).
My Wii U is on 5.4.0 and is gathering dust because I can't do anything with it.It surprises me that most people seem to consider this opportunity as a chance to get hacks/backup loading before an official release.
Testing can be tedious, and you may risk your Wii U 's life over it.
I was unaware of your progress with IOSU. Congrats.
Most of the IOSU has been reverse-engineered and I'm still updating the wiki almost daily: http://wiiubrew.org/wiki/Special:RecentChanges
I already have an exploitable bug that should work up to firmware 5.5.0 and naehrwert is working on something too (currently for lower than 5.2.0 firmwares). When everything is ready it will be publicly released (at least on my end).
No clue what @Mathew_Wi is up to, but he did work with @Marionumber1 to get the 5.3.2 firmware exploit working (debugging via DevKit) and he found the MP4 bug test case that's being used to exploit 5.4.0/5.5.0 (which turned out to be a libstagefright bug, way before the controversial presentation).
There are more than one just one that functions best.Last question just to finish and dont bother you.
You have a Kernel Exploit 5.5.0 working too different from MN1 & team?
How many Kernel Exploit have working on 5.5.0? Still only 1?
Huh, that is interesting.he found the MP4 bug test case that's being used to exploit 5.4.0/5.5.0 (which turned out to be a libstagefright bug, way before the controversial presentation).
Well, considering Hykem is pretty much finished with IOSU, I don't think I'll need anything for a good while. I've edited the main post.What kind of hardware do you require for the development or attack you have in mind?
Yea I saw, very nice. Along with the StageFright history.Well, considering Hykem is pretty much finished with IOSU, I don't think I'll need anything for a good while. I've edited the main post.