Hacking Wii U Hacking & Homebrew Discussion

[MRJPGames]

You completely forgot that IOSU can do everything PPC kernel can do.
A 5.4.0 webkit exploit will be out with IOSU as @Hykem stated, so it is safe to update.

But thers already stuff for ppc kernel not much for IOSU (assuming hyken releases something you can do with iosu along with the exploit, otherwise there is nothing you can do with IOSU when the exploit is released.)

 

[VinsCool]

has it crossed any ones mind that this is just a wind up and that its fake ????? i mean a week later and still nothing

Nice b8 m8

 

[JaceCearK1]

@troll The username fits so well!

 

[OctopusRift]

has it crossed any ones mind that this is just a wind up and that its fake ????? i mean a week later and still nothing

Dude. Do uyou know what "Dev Hell" means?

He could rush it and just shit out Sonic Boom. Or a polished sploit.

 

[FusionGamer]

Dude. Do uyou know what "Dev Hell" means?

Don't feed @troll. (Seriously, that's his username.)

 

[canariobr]

any news from hykem?

 

[Fjar]

any news from hykem?

Not yet let's wait, maybe, next week we will have some news about IOSU exploit

 

[codychaosx]

EDIT: Don't take it personally, just having some bad days :< A fox ran out in front of my car some days ago, so I have been having some real shitty guilt since ._. Shouldn't project it unto others. My point still stands, though.

 

[Pioneer2k7]

Guys, just let him finish his work, it will be done when it's done. Even if he releases it right now, u wouldn't be able to do something unless you are a developer.

This is just annoying.
Just my 2 cents

 

[Deleted User]

Be patient guys. He's taking time out of his daily life to give us all IOSU for free. He followed it up with an update and it hasn't been a week since. If I were him the more and more I read the ungrateful people it would steer me away from release. Nothing new though this same shit happens with all the pre hacked consoles.

 

[CaptainLoozer]

Used to keep up with wii hacking on the original system. Bought a wii u last year in hopes that it would be hacked soon and was disappointed that it hadn't been. I just happened to do a little googling yesterday and was surprised to see this announcement. I'm very excited about this exploit and can't wait to play backups. Hope it is released soon.

I still have my mini usb hdd and sd card. Would anything else be needed to come back to the wii hacking scene?

 

[codychaosx]

Guys, just let him finish his work, it will be done when it's done. Even if he releases it right now, u wouldn't be able to do something unless you are a developer.

This is just annoying.
Just my 2 cents

i thought this as well although i heard that since there are private exploits that some people have been using on 5.5 and 5.4 and 5.5 even has a version of loadiine working on it via these private hacks. i would think it would be ported rather quickly to hykems exploit. but im no dev or expert so im just making "educated" (lol) guesses

 

[Deleted User]

Used to keep up with wii hacking on the original system. Bought a wii u last year in hopes that it would be hacked soon and was disappointed that it hadn't been. I just happened to do a little googling yesterday and was surprised to see this announcement. I'm very excited about this exploit and can't wait to play backups. Hope it is released soon.

I still have my mini usb hdd and sd card. Would anything else be needed to come back to the wii hacking scene?

With the exception of the needed files I would say your good to go.

 

[Hykem]

So, I've got good news and bad news.
The bad news is that I'm going to postpone the release again. I said this week would be a more realistic release date, but I never confirmed it would happen then. Still, it's not a huge delay and it's definitely not to wait for a new firmware update.
Like I stated before, I have the entire month of January free just to work on this and the exploit will be released and maintained before February (yes, I'm sure of that).
Now the good news, which should explain the additional delay. I need some time to pursue something I found in the MCP module. If I'm correct about this, we should be able to get a boot-time exploit. The reason for that is that the MCP module is responsible for launching "master" titles (like the PPC kernel, for example) and I found a bug that, if it turns out to be exploitable, should allow to hijack execution while MCP is still preparing to launch stuff. This means, early IOSU access and a direct boot into an exploitable environment. Not to mention that MCP is the IOSU user module with most privileges (next to BSP that is) and having access to it alone is more than enough to own the IOSU kernel at any given time.
I believe it's important to look into this because if it works, no one will have to worry about possibly bricking consoles by installing custom titles (homebrew channel, for example) and then attempting to launch them before triggering the exploit again after a fresh boot.

With that said, if this turns out to be nothing, I'll release the exploit right away.

 

[paulloeduardo]

So, I've got good news and bad news.
The bad news is that I'm going to postpone the release again. I said this week would be a more realistic release date, but I never confirmed it would happen then. Still, it's not a huge delay and it's definitely not to wait for a new firmware update.
Like I stated before, I have the entire month of January free just to work on this and the exploit will be released and maintained before February (yes, I'm sure of that).
Now the good news, which should explain the additional delay. I need some time to pursue something I found in the MCP module. If I'm correct about this, we should be able to get a boot-time exploit. The reason for that is that the MCP module is responsible for launching "master" titles (like the PPC kernel, for example) and I found a bug that, if it turns out to be exploitable, should allow to hijack execution while MCP is still preparing to launch stuff. This means, early IOSU access and a direct boot into an exploitable environment. Not to mention that MCP is the IOSU user module with most privileges (next to BSP that is) and having access to it alone is more than enough to own the IOSU kernel at any given time.
I believe it's important to look into this because if it works, no one will have to worry about possibly bricking consoles by installing custom titles (homebrew channel, for example) and then attempting to launch them before triggering the exploit again after a fresh boot.

With that said, if this turns out to be nothing, I'll release the exploit right away.

Tanks

 

[gameboy]

do your thing, i believe most people wanted to know if it was real and not too worried about the release date

 

[OctopusRift]

So, I've got good news and bad news.
The bad news is that I'm going to postpone the release again. I said this week would be a more realistic release date, but I never confirmed it would happen then. Still, it's not a huge delay and it's definitely not to wait for a new firmware update.
Like I stated before, I have the entire month of January free just to work on this and the exploit will be released and maintained before February (yes, I'm sure of that).
Now the good news, which should explain the additional delay. I need some time to pursue something I found in the MCP module. If I'm correct about this, we should be able to get a boot-time exploit. The reason for that is that the MCP module is responsible for launching "master" titles (like the PPC kernel, for example) and I found a bug that, if it turns out to be exploitable, should allow to hijack execution while MCP is still preparing to launch stuff. This means, early IOSU access and a direct boot into an exploitable environment. Not to mention that MCP is the IOSU user module with most privileges (next to BSP that is) and having access to it alone is more than enough to own the IOSU kernel at any given time.
I believe it's important to look into this because if it works, no one will have to worry about possibly bricking consoles by installing custom titles (homebrew channel, for example) and then attempting to launch them before triggering the exploit again after a fresh boot.

With that said, if this turns out to be nothing, I'll release the exploit right away.

CoLD BOOT WOOT.

 

[CaptainLoozer]

So lets say the latter happens:

Using this exploit could likely brick our systems?

 

[aracom]

Using this exploit could likely brick our systems?

No, if you only do what you're supposed to do, follow tutorials and use code you got from here.

 

[Vappy]

Delays suck, but plenty understandable when it's for a good reason, and potential coldboot exploitation is a damn good reason.