Hacking Wii U Hacking & Homebrew Discussion

[endoverend]

Anything "serious" will be in a private message and likely IRC. 100% on IRC. Nwplayer1234 and marionumber1 stop by, are very patient, and give useful posts and replies. Never too late to hit the "reset" button in a lot of ways. You can hit "ignore" and then remove the "fluff." I like to glance over it all for a laugh. I have more fun messing with sports forums than video game ones. I buy all of my games and have anything I could want on other devices so aside from a Game Genie type of function and/or a backup loader (others will use it for piracy, lmfao) I really have no use for much of this.

99% want piracy and everyone knows it. The odds are if people cannot find a kernel exploit after the browser bug then they won't find an IOSU exploit. Chadderz and Bean thinking "obfusgation" will protect their exploit are kidding themselves. Whatever NWplayer1234 and MN1 have seems to be a different exploit. As it is, you'll have a choice; stay on an exploitable firmware without using the internet for homebrew you can already get elsewhere (or buy a full system for $5 to $15, lmfao) or update when the great game you've been wanting comes out. From what I've read, the kernel exploit won't allow the region free or "firmware spoofing" people say they want. So really endoverend, not sure if you are like me, but aside from a way to revert (like a 360 with a hardware flasher) or with the Wii and "bootmii" or "priiloader" and an IOSU exploit where I can do what I want (a lot more than with a kernel or "userspace" exploit that is not persistent) it is really not worth it. No disrespect to MN1 or NWplayer who seem to be very nice. Some will stay on 5.2.0 or lower and not get Zelda or other games when Nintendo makes those games require 5.4 or higher, lol. I have a big stack, for me, of about 10 Wii U games that have all been played extensively by me and my family.

I literally just asked for this type of post not to be made. If you want to talk about if it's "worth" staying on another firmware there's no sense in doing it here. I was merely trying to clean the discussion up.

 

[NWPlayer123]

Anything "serious" will be in a private message and likely IRC. 100% on IRC. Nwplayer1234 and marionumber1 stop by, are very patient, and give useful posts and replies. Never too late to hit the "reset" button in a lot of ways. You can hit "ignore" and then remove the "fluff." I like to glance over it all for a laugh. I have more fun messing with sports forums than video game ones. I buy all of my games and have anything I could want on other devices so aside from a Game Genie type of function and/or a backup loader (others will use it for piracy, lmfao) I really have no use for much of this.

99% want piracy and everyone knows it. The odds are if people cannot find a kernel exploit after the browser bug then they won't find an IOSU exploit. Chadderz and Bean thinking "obfusgation" will protect their exploit are kidding themselves. Whatever NWplayer1234 and MN1 have seems to be a different exploit. As it is, you'll have a choice; stay on an exploitable firmware without using the internet for homebrew you can already get elsewhere (or buy a full system for $5 to $15, lmfao) or update when the great game you've been wanting comes out. From what I've read, the kernel exploit won't allow the region free or "firmware spoofing" people say they want. So really endoverend, not sure if you are like me, but aside from a way to revert (like a 360 with a hardware flasher) or with the Wii and "bootmii" or "priiloader" and an IOSU exploit where I can do what I want (a lot more than with a kernel or "userspace" exploit that is not persistent) it is really not worth it. No disrespect to MN1 or NWplayer who seem to be very nice. Some will stay on 5.2.0 or lower and not get Zelda or other games when Nintendo makes those games require 5.4 or higher, lol. I have a big stack, for me, of about 10 Wii U games that have all been played extensively by me and my family.

I'll just leave this quote here:
[11:08:32] <Marionumber1> Homebrew is a goal, but we're really game modders
[11:08:42] <Marionumber1> And that's something we really want to do
That's why we're working on a kernel exploit, because you don't need anything more then that to mod games. We've been working on modding Super Mario Galaxy 2 for over 4 years now, it's time to step up our game (pun intended).

 

[Vappy]

So not too far removed from what chadderz/mrbean were aiming for? With the difference that you will hopefully, in time, have a more flexible release, whereas chadderz said if they ever did release their work to the public it'd be locked to Mario Kart.

 

[NWPlayer123]

So not too far removed from what chadderz/mrbean were aiming for? With the difference that you will hopefully, in time, have a more flexible release, whereas chadderz said if they ever did release their work to the public it'd be locked to Mario Kart.

Correct

 

[Skeet1983]

Darn, was hoping for game cheats

 

[pedrobarca]

Darn, was hoping for game cheats

I think should stop whining about your stupid cheats. You spammed enough in this thread.

 

[dragonmaster]

i prefer a method with no soldering skills required to get the common keys but if it is needed i can improvise

 

[pedrobarca]

I just want to throw in that I am a huge fan of cheats, so I'm looking forward to them too.

I have no problems with cheats I was just annoyed by the fact, that Skeet was begging for cheats over and over again.

 

[endoverend]

So I finally sat myself down and watched the 31c3 f0f talk and I mostly understand it. But does fail0verflow have the common key? I saw a hash for it in the video.

 

[NWPlayer123]

So I finally sat myself down and watched the 31c3 f0f talk and I mostly understand it. But does fail0verflow have the common key? I saw a hash for it in the video.

Yes, they have every key, except for the boot1 key, as detailed here: https://fail0verflow.com/blog/2014/console-hacking-2013-omake.html

 

[endoverend]

Yes, they have every key, except for the boot1 key, as detailed here: https://fail0verflow.com/blog/2014/console-hacking-2013-omake.html

Thanks, I was a little surprised at the fact that the keys have been decrypted since 2013. Was there any Wii U talk at CCC this year?

 

[NWPlayer123]

Thanks, I was a little surprised at the fact that the keys have been decrypted since 2013. Was there any Wii U talk at CCC this year?

Nope, they were there but they just had a stand.

 

[Vappy]

And seems like they didn't do much related to games consoles this year, more of a focus on other hw that interested them and CTFs.

 

[noobiez]

Would it be useful to get second bank of nand (2x512) read in vwii mode? if i have understood that the other half is wii and another is wiiu. i think the route is same at motherboard but nand is switched to other when using. that wouldnt be problem to activate wiiu nand in vwii by hardware but i think it needs to be combaned to soft reset hack at the same time.

 

[Bug_Checker_]

on the subject of the common key, i'd like to make two questions:

Spoiler

question number 1:

snip

what is the functionality of this?

question number 2:

snip

what is the functionality of this?

Don't bother going through sha1sum, i already went and neither matches.

These ARE keys, i just don't know what for.

If somebody could explain me what these bytes do i'd appreciate it.

I totally missed this original post(before numbers were edited out).
Did anyone make any progress on it?
Were they 16 byte numbers?
Any clue as to their origin/purpose?
What files or disc they may have worked with?

 

[shinkodachi]

And seems like they didn't do much related to games consoles this year, more of a focus on other hw that interested them and CTFs.

I think fail0verflow said it best in his opening paragraphs of his blog post in 2013:

It’s been almost 7 years since the Wii was released. Back in 2006, not many owned a living room PC. PCs were still relatively bulky, and the Chinese offerings were limited to horrible media players. At the time, the prospect of having a game console double as a HTPC and being able to browse the web, play games for older platforms with emulation, and run homebrew games on a device which you already had in the living room was rather appealing.

Fast forward to today. Mobile SoCs have made huge advances - you can get a quad-core chip in a phone these days - and have made the jump to the living room. Spend $25 and you can get a Raspberry Pi, which is about on par with the Wii at 1/10 of the launch price and 1/7th of the power consumption (with HD video). Spend $100 and you can get an Ouya, which beats the Wii U’s CPU and doesn’t have too shabby graphics at one third the cost. These mobile-derived devices aren’t quite a replacement for game consoles yet, but they’re catching up fast. They’re cheap enough that they’re almost disposable. The software ecosystem is much larger and wider than any console has ever had. More importantly, they’re open, and the development tools and environments are way better for open development than any game console ever was.

 

[Vappy]

Yup. Still good fun to get as far as finding an exploit in a closed system, but building up a workable knowledgebase and toolset from reverse engineering and documenting, not as much.

 

[Marionumber1]

Awesome! I hate people who are against piracy but who have developed great exploits that can lead to it.

The exploit could possibly lead to it (not quite sure whether piracy could be done with just a kernel exploit), but we've made it clear that we intend to obfuscate before release. If someone ends up reversing the obfuscation, good for them.

 

[Marionumber1]

So you're going against piracy and so you're obfuscating?

Yes, and complaints aren't going to change my mind.

 

[shinkodachi]

So you're going against piracy and so you're obfuscating?

He doesn't want all the hard work put into the exploit that could lead us to a nourishing homebrew community go in vain.