Hacking Wii U Hacking & Homebrew Discussion

[NWPlayer123]

If anything I'd suggest staying on 5.4 since we may release the latest Webkit exploit later down the line, but it's probably very unlikely the new kernel exploit (needed for 5.5) will see the light of day any time soon.

 

[VinsCool]

If anything I'd suggest staying on 5.4 since we may release the latest Webkit exploit later down the line, but it's probably very unlikely the new kernel exploit (needed for 5.5) will see the light of day any time soon.

Good for 5.4 people though

 

[Marionumber1]

If anything I'd suggest staying on 5.4 since we may release the latest Webkit exploit later down the line, but it's probably very unlikely the new kernel exploit (needed for 5.5) will see the light of day any time soon.

Unless we find another one, but the current focus of most of our exploit developers (me, Hykem, Matt) is IOSU.

 

[the_randomizer]

Here is a question I am curious about however. Given the fact that the Nintendo will always update the Wii U, and break any exploits, isn't updating to the latest discouraged anyway? And if we're warned to not upgrade, why would releasing it now or later make any difference? Not to be rude, but I don't think there will be a time Nintendo's going to stop updating the Wii U anytime soon. As long as Nintendo keeps updating the Wii U, this further delays the exploit from being released, so why should it be delayed every time Nintendo updates?

Releasing it now, or releasing it later doesn't make any difference, hypothetically speaking, because Nintendo is just keep on going to release new firmware versions anyway. Damned if you do, damned if you don't, no reason to let Nintendo win. Surely, you guys don't expect to hold off till Nintendo moves on to the NX? That won't be till 2016 or 2017 at the very least, doesn't sound very conducive.

They're very aggressive about not letting the Wii U be hacked as they're not as lax as they were with the Wii and just stopped updating.

 

[PhyChris]

Here is a question I am curious about however. Given the fact that the Nintendo will always update the Wii U, and break any exploits, isn't updating to the latest discouraged anyway? And if we're warned to not upgrade, why would releasing it now or later make any difference? Not to be rude, but I don't think there will be a time Nintendo's going to stop updating the Wii U anytime soon. As long as Nintendo keeps updating the Wii U, this further delays the exploit from being released, so why should it be delayed every time Nintendo updates?

Releasing it now, or releasing it later doesn't make any difference, hypothetically speaking, because Nintendo is just keep on going to release new firmware versions anyway. Damned if you do, damned if you don't, no reason to let Nintendo win. Surely, you guys don't expect to hold off till Nintendo moves on to the NX? That won't be till 2016 or 2017 at the very least, doesn't sound very conducive.

I see what you mean. if its already patched in latest FW then why hold it.

 

[nonamejohn]

I made a joke a while ago about them holding out for the machine to be EOL. Maybe that's going to happen ! LOL!

 

[the_randomizer]

I see what you mean. if its already patched in latest FW then why hold it.

It's no wonder the scene's at a stalemate; almost as if they don't expect Nintendo to not be active in upping the ante with their security patches. Here's a little newsflash for the developers, Nintendo isn't stupid this time like they were on their last console the Wii, or the DS. They're fighting fire with fire, and if things keep getting delayed, by the time they give up updating the Wii U and move on its successor, there won't be a viable ecosystem on which to develop homebrew with.

If I'm wrong, so be it, I'm wrong.

 

[Marionumber1]

Here is a question I am curious about however. Given the fact that the Nintendo will always update the Wii U, and break any exploits, isn't updating to the latest discouraged anyway? And if we're warned to not upgrade, why would releasing it now or later make any difference? Not to be rude, but I don't think there will be a time Nintendo's going to stop updating the Wii U anytime soon. As long as Nintendo keeps updating the Wii U, this further delays the exploit from being released, so why should it be delayed every time Nintendo updates?

Releasing it now, or releasing it later doesn't make any difference, hypothetically speaking, because Nintendo is just going to release a new firmware version anyway. Damned if you do, damned if you don't, no reason to let Nintendo win. Surely, you guys don't expect to hold off till Nintendo moves on? That won't be till 2016 or 2017 at the very least, doesn't sound very conducive.

As I have said, numerous times, before, there are a few conditions on which exploits will be released:
1. Nintendo patches a bug we're using.
2. We develop another stockpiled exploit, allowing us to release one (this is tricky, though; Nintendo may fix unreleased bugs too, so we have to play a psychological game to determine which exploit is the most advantageous to release).
3. We come up with a method to prevent updates and prevent bugs from being patched. crediar's firmware spoofer or even a boot time exploit that patches out IOSU's update ability would be examples of this. Even then, we still have to keep in mind that we could release an exploit, it will get patched, and then someone just joining the scene may be locked out. So we don't necessarily want to do this if other exploits don't exist first.

Right now, we have a browser exploit that Nintendo hasn't patched and a kernel exploit that Nintendo hasn't patched. We're currently ahead of them, and don't want to lose the advantage. Currently, developing more permanent attacks or more exploits is worth it, and that's what we're working on.

 

[TheZander]

does anyone have an idea of how nintendo catches wind of something once it's released? I know they must have a piracy control group or copyright group that hassles youtube jerks, do you think they track it down? Do they really have hands on deck that go through the exploit find something that they need to patch, then package it all up in an update that's released to millions of WiiU owners? That has to feel pretty cool being responsible for forcing a company as big of nintendo to pour so much time and effort fixing something you worked hard on, thus transiently effecting millions of people. Smealum got over on the guys behind Cubic Ninja though I suppose by kicking em off eShop. He also greatly increased their used cartridge sales, so if they had any inventory they hadn't berried in a land fill at that point they could finally cash in.

 

[the_randomizer]

As I have said, numerous times, before, there are a few conditions on which exploits will be released:
1. Nintendo patches a bug we're using.
2. We develop another stockpiled exploit, allowing us to release one (this is tricky, though; Nintendo may fix unreleased bugs too, so we have to play a psychological game to determine which exploit is the most advantageous to release).
3. We come up with a method to prevent updates and prevent bugs from being patched. crediar's firmware spoofer or even a boot time exploit that patches out IOSU's update ability would be examples of this. Even then, we still have to keep in mind that we could release an exploit, it will get patched, and then someone just joining the scene may be locked out. So we don't necessarily want to do this if other exploits don't exist first.

Right now, we have a browser exploit that Nintendo hasn't patched and a kernel exploit that Nintendo hasn't patched. We're currently ahead of them, and don't want to lose the advantage. Currently, developing more permanent attacks or more exploits is worth it, and that's what we're working on.

My deepest apologies, I didn't know that that was the plan you guys intended to take, to find a more permanent solution to making the Wii U in an exploitable state; I admit that I was wrong in assuming otherwise. Sorry...

 

[NWPlayer123]

does anyone have an idea of how nintendo catches wind of something once it's released? I know they must have a piracy control group or copyright group that hassles youtube jerks, do you think they track it down? Do they really have hands on deck that go through the exploit find something that they need to patch, then package it all up in an update that's released to millions of WiiU owners? That has to feel pretty cool being responsible for forcing a company as big of nintendo to pour so much time and effort fixing something you worked hard on, thus transiently effecting millions of people. Smealum got over on the guys behind Cubic Ninja though I suppose by kicking em off eShop. He also greatly increased their used cartridge sales, so if they had any inventory they hadn't berried in a land fill at that point they could finally cash in.

I don't know how exactly they're doing it, but "We're listening, too." is definitely true (https://twitter.com/NintendoAmerica). I'm on their hitlist ever since I made a video about playable Octolings, all of them adding up to almost a million views (500+K on the first video on my old channel, like 300K on the second, and 201K on my new one that got copyrighted and shut down). Supposedly even the higher ups know about me since Sploon is their big new IP.

 

[PhyChris]

As I have said, numerous times, before, there are a few conditions on which exploits will be released:
1. Nintendo patches a bug we're using.
2. We develop another stockpiled exploit, allowing us to release one (this is tricky, though; Nintendo may fix unreleased bugs too, so we have to play a psychological game to determine which exploit is the most advantageous to release).
3. We come up with a method to prevent updates and prevent bugs from being patched. crediar's firmware spoofer or even a boot time exploit that patches out IOSU's update ability would be examples of this. Even then, we still have to keep in mind that we could release an exploit, it will get patched, and then someone just joining the scene may be locked out. So we don't necessarily want to do this if other exploits don't exist first.

Right now, we have a browser exploit that Nintendo hasn't patched and a kernel exploit that Nintendo hasn't patched. We're currently ahead of them, and don't want to lose the advantage. Currently, developing more permanent attacks or more exploits is worth it, and that's what we're working on.

now i see what u mean haha

 

[TheZander]

I don't know how exactly they're doing it, but "We're listening, too." is definitely true (https://twitter.com/NintendoAmerica). I'm on their hitlist ever since I made a video about playable Octolings, all of them adding up to almost a million views (500+K on the first video on my old channel, like 300K on the second, and 201K on my new one that got copyrighted and shut down). Supposedly even the higher ups know about me since Sploon is their big new IP.

That's awesome, did you at least get to cash in with some ads? Are you saying that official twitter follows you? They were nintendo's views you're saying?

Do you think you guys are at the point where you can 'release' something with just claims and nintendo will scurry trying to rectify it? NSMBU Exploit for instance then they just release an update? Like Nintendo just pulled Cubic Ninja and said screw it, didn't bother patching.

 

[Zap Rowsdower]

If anything I'd suggest staying on 5.4 since we may release the latest Webkit exploit later down the line

So by down the line, it's going back to the original plan (Mathew_Wi?)
of waiting until after it's patched to go public? Is it still currently 'broken'?
I happen to know that IOSU got about 3MB larger, and the version increased by over 4000 revisions with 5.5, so I gather staying on 5.4 would be wise.
-scratch- -scratch-

 

[NWPlayer123]

So by down the line, it's going back to the original plan (Mathew_Wi?)
of waiting until after it's patched to go public? Is it still currently 'broken'?
I happen to know that IOSU got about 3MB larger, and the version increased by over 4000 revisions with 5.5, so I gather staying on 5.4 would be wise.
-scratch- -scratch-

It's not "broken", it's just that the buffer that the bug jumps to for running the ROP to set up our code varies between WiiU's, I have it figured out for mine and it works basically 100%, as long as the browser doesn't do something stupid. If/when it's released I'll probably detail all my little tricks.

 

[Marionumber1]

That's awesome, did you at least get to cash in with some ads? Are you saying that official twitter follows you? They were nintendo's views you're saying?

Do you think you guys are at the point where you can 'release' something with just claims and nintendo will scurry trying to rectify it? NSMBU Exploit for instance then they just release an update? Like Nintendo just pulled Cubic Ninja and said screw it, didn't bother patching.

We do have a few potentially exploitable apps in mind that go beyond the browser. There were actually some crashes that we generated in a few apps, but we didn't spend too much time investigating. I may come back to those sometime.

 

[TheZander]

We do have a few potentially exploitable apps in mind that go beyond the browser. There were actually some crashes that we generated in a few apps, but we didn't spend too much time investigating. I may come back to those sometime.

Would they compatible with anything you have now? The browser exploit has internet connectivity that loads stuff off a computer with a game wouldn't you need some screwed around game save? Or just the internet function of the game and it will do the same stuff? But then it would only work if on the latest FW because nintendo is mandating that now.

 

[Marionumber1]

Would they compatible with anything you have now? The browser exploit has internet connectivity that loads stuff off a computer with a game wouldn't you need some screwed around game save? Or just the internet function of the game and it will do the same stuff? But then it would only work if on the latest FW because nintendo is mandating that now.

There are various ways of getting data into a game. It could read data from the FS or network, or we could use the browser exploit to install hacked savefiles and later have that as "insurance" against a patched browser.

 

[TheZander]

There are various ways of getting data into a game. It could read data from the FS or network, or we could use the browser exploit to install hacked savefiles and later have that as "insurance" against a patched browser.

The hacked savefile that loads the exploit in the game once it's selected? Instead of poking with TCPGecko it just has all that stuff cooked into it?

 

[Marionumber1]

The hacked savefile that loads the exploit in the game once it's selected? Instead of poking with TCPGecko it just has all that stuff cooked into it?

Yes, a hacked savefile would be stored on the eMMC and launching it would exploit the system.