Hacking Will a Custom Firmware eventually be possible?

[JoostinOnline]

Sorry, wrong thread
http://gbatemp.net/threads/coding-vwii-3-core-support-everything-you-need-to-know.347626/

If you just get on IRC in the afternoon (GMT-6) then Maxternal usually has something to test.

 

[the_randomizer]

Sorry, wrong thread
http://gbatemp.net/threads/coding-vwii-3-core-support-everything-you-need-to-know.347626/

If you just get on IRC in the afternoon (GMT-6) then Maxternal usually has something to test.

The channel on EFNet, correct?

 

[JoostinOnline]

Yep. Use
/join #vWii

 

[Maxternal]

You might not be able to install a CFW onto the Wii U itself but I don't think it would be impossible all together. There's always the possibility of a CFW the way it's done on the 3DS, using an exploit every time to load a hacked firmware from somewhere else. (kinda like using ModMii's abstinence wizard on a normal Wii)

You also might not be able to install a HomebrU channel on the console itself as easily as it was done on Wii ... but there MIGHT be other ways to install a permanent exploit onto the console. For example, if all executable code on Wii U was signed but other files were not and there was (just an example) an exploitable bug in how it loaded image files for banners, you could replace some banner on NAND with a hacked one (using the web browser exploit as a start) so it would run unsigned code every time it loads up and tries to load that banner and then that exploit could be made to run a Wii U mode version of something like SNEEK to load a CFW from SD or USB.

(I have no idea if any exploit like could exist for sure ... but there's always the possibility that some workaround could be found)

 

[Ray Lewis]

That or a kexec type solution. I was in on those conversations but not a contributor.

 

[jammybudga777]

im not gonna pretend i no anything about coding exc. but i do believe it would be possible after an exploit is found/released in the future and for the keys too be found within the console im sure a cfw would be approachable....... but things do take time

 

[JoostinOnline]

im not gonna pretend i no anything about coding exc. but i do believe it would be possible after an exploit is found/released in the future and for the keys too be found within the console im sure a cfw would be approachable....... but things do take time

We are approaching it without the exploit. Nobody who understands it WANTS the exploit to be public.

 

[the_randomizer]

We are approaching it without the exploit. Nobody who understands it WANTS the exploit to be public.

Exactly. To release the exploit now would spell disaster, as Nintendo would patch it, to reflect what you said earlier. The other approach (what Max and those guys are doing now), is the safer route IMHO

 

[jammybudga777]

okay my bad. sorry for the retarded postlol

 

[the_randomizer]

okay my bad. sorry for the retarded postlol

No, you're fine, no worries

 

[NostalgicMillennial]

Custom firmware is already possible, but certain hacking groups won't set their pride and egos aside for the greater good.

We need backup loaders, we need Wii U homebrew, and we need it NOW!!! I don't see Nintendo reviving the system any time soon, even with a shitty Zelda-meets-Destiny-Warriors mashup, Super Smash Brothers Universe, and Mario Kart 8 in the near future.

can you describe *slaps on eye patch* the "greater good?"

 

[Marionumber1]

You might not be able to install a CFW onto the Wii U itself but I don't think it would be impossible all together. There's always the possibility of a CFW the way it's done on the 3DS, using an exploit every time to load a hacked firmware from somewhere else. (kinda like using ModMii's abstinence wizard on a normal Wii)

You also might not be able to install a HomebrU channel on the console itself as easily as it was done on Wii ... but there MIGHT be other ways to install a permanent exploit onto the console. For example, if all executable code on Wii U was signed but other files were not and there was (just an example) an exploitable bug in how it loaded image files for banners, you could replace some banner on NAND with a hacked one (using the web browser exploit as a start) so it would run unsigned code every time it loads up and tries to load that banner and then that exploit could be made to run a Wii U mode version of something like SNEEK to load a CFW from SD or USB.

(I have no idea if any exploit like could exist for sure ... but there's always the possibility that some workaround could be found)

Of course there's a possibility such a vulnerability exists, but it still seems unlikely to me. Either way, components like boot1, IOSU, and Cafe OS probably can't be modified.

 

[Jayro]

What about those who can't program worth crap, but still want to help anyway? The problem is, I don't even know how to code, much less understand the rudiments of PPC ASM.

I'm quite skilled in Photoshop, and could make artwork for Wii U channels (or whatever the Wii uses to launch titles, I don't have a Wii U because, well... it's not hacked yet). Photoshop is like my second home. :3

 

[daicon]

Because homebrew will totally save the system. Seriously, so few people care about it (especially without backup loaders) that it won't help at all. Even if it would boost sales, the people who would buy it would mostly buy it for backup loaders and not buy any games, which doesn't help.

The people who buy the Wii U to pirate never would have bought the system in the first place and never would have bought the games in the first place either. See the problem there?

I never cared about the PSP until it was hacked, and then I picked one up.. and here I am over half a decade later with a shelf full of over 30 legally owned UMD games that I wouldn't have bought if homebrew never happened on PSP. ( also no I don't own a WiiU)

Just my 2cents, but I personally think piracy is overstated around here.. it's almost as if it's turned into a bandwagon (probably because people know f0f glances at these forums and some members are desperate to s their d..)

 

[wiired24]

I think that Custom Firmware for the WII U is definitley possible in the future, only time will tell. Since the Bootrom has been dumped if there isnt already an exploit in the works for the Wii U more than likley there will be one very soon.

 

[Marionumber1]

I think that Custom Firmware for the WII U is definitley possible in the future, only time will tell. Since the Bootrom has been dumped if there isnt already an exploit in the works for the Wii U more than likley there will be one very soon.

As many other people and I have tried to explain, dumping the Boot ROM does not bring us that much closer to Wii U homebrew. Dumping the Boot ROM is in fact completely useless by itself. The only thing it does is pave the way for implementing the HRESET attack to get the PowerPC binary decryption keys, which is also useless by itself. Getting the keys is only helpful once a Wii U mode exploit has been implemented (through the web browser). There is effort underway to develop that Wii U mode exploit, but don't expect anything to come out of it for a while.

 

[daicon]

As many other people and I have tried to explain, dumping the Boot ROM does not bring us that much closer to Wii U homebrew. Dumping the Boot ROM is in fact completely useless by itself. The only thing it does is pave the way for implementing the HRESET attack to get the PowerPC binary decryption keys, which is also useless by itself. Getting the keys is only helpful once a Wii U mode exploit has been implemented (through the web browser). There is effort underway to develop that Wii U mode exploit, but don't expect anything to come out of it for a while.

When was the last time the Wii U browser was updated by Nintendo?

 

[Marionumber1]

When was the last time the Wii U browser was updated by Nintendo?

It was last updated sometime in 2013, to WebKit 536.28 from late 2012.

 

[daicon]

It was last updated sometime in 2013, to WebKit 536.28 from late 2012.

Thanks. I wonder how many bugs were patched in that period, and if that'll affect things enough to warrant working on an older Webkit over the 536.28

 

[Marionumber1]

Thanks. I wonder how many bugs were patched in that period, and if that'll affect things enough to warrant working on an older Webkit over the 536.28

WebKit 536.28 probably doesn't have as many exploitable bugs as the version fail0verflow exploited back in 2012. However, I've found at least 6 possible exploitable bugs, which I'll be looking at further next week.