Hacking Wii U Hacking & Homebrew Discussion

[the_randomizer]

Okay, I'll learn how to program, but don't expect miracles.

 

[Marionumber1]

So we're fucked then? Sure as hell sounds like it. -_- I think I'm going to just sit and think about what could've been.

You don't need to lapse into depressed moaning every time you think (incorrectly) that the scene is doomed.

 

[TheZander]

Dude, back off. No one asked you.



Well, the fact I have zero programming skills (that's not an exaggeration), doesn't exactly help me, so....

What is it with you? I don't understand. All this "woe is me" crap all the time

 

[BullyWiiPlaza]

The game id can be read at address 0x100136D0 (on 5.3.2)

Hmm, no. For Mario Kart 8 PAL and firmware 5.3.2 the value there is 00050000 and this doesn't look right.

 

[Marionumber1]

Hmm, no. For Mario Kart 8 PAL and firmware 5.3.2 the value there is 00050000 and this doesn't look right.

That is the first 32-bit word of the title ID, the next word should be the game ID.

 

[AHP_person]

Hmm, no. For Mario Kart 8 PAL and firmware 5.3.2 the value there is 00050000 and this doesn't look right.

Wouldn't that be the title id's high bytes?
EDIT: Ninja'd

 

[BullyWiiPlaza]

That is the first 32-bit word of the title ID, the next word should be the game ID.

They are not ASCII characters though. Here's some memory (address, value, value, value, value):

Spoiler

10013660 00000000 10000C74 0101D7BC 00000006
10013670 00000000 00000000 00000000 00000000
10013680 10011DA0 1000063C 0101E9C8 00000000
10013690 00000000 10000C7C 0101D8E4 00000006
100136A0 00000000 10000140 0101D8E4 00000006
100136B0 00000000 00000000 00000000 00000000
100136C0 10011DB0 1000063C 0101E9C8 00000000
100136D0 00050000 1010ED00 00050010 1000400A
100136E0 0000000F 00000000 00000001 00000200
100136F0 00000001 1005F680 00000000 00000000
10013700 00000000 10013700 00000000 00000001
10013710 106B57E0 10085E28 107752A0 10085E80
10013720 38613400 10085ED8 BAD5CAFF FAD5CAFF
10013730 3AD5CAFF 100012B4 100012D0 100012EC
10013740 10001308 10001324 10001340 00000000
10013750 00000000 00000000 00000000 00000000

 

[Skeet1983]

The scene is not doomed. We just got the Kexploit, others will come. Patience is the key and good things come in time
I don't know much about hacking and programming, and I would help if I could. But I do thank those who are putting time and effort into all of this, much appreciated

 

[LawnMeower]

They are not ASCII characters though. Here's the memory layout (address, value, value, value, value):

Spoiler

10013660 00000000 10000C74 0101D7BC 00000006
10013670 00000000 00000000 00000000 00000000
10013680 10011DA0 1000063C 0101E9C8 00000000
10013690 00000000 10000C7C 0101D8E4 00000006
100136A0 00000000 10000140 0101D8E4 00000006
100136B0 00000000 00000000 00000000 00000000
100136C0 10011DB0 1000063C 0101E9C8 00000000
100136D0 00050000 1010ED00 00050010 1000400A
100136E0 0000000F 00000000 00000001 00000200
100136F0 00000001 1005F680 00000000 00000000
10013700 00000000 10013700 00000000 00000001
10013710 106B57E0 10085E28 107752A0 10085E80
10013720 38613400 10085ED8 BAD5CAFF FAD5CAFF
10013730 3AD5CAFF 100012B4 100012D0 100012EC
10013740 10001308 10001324 10001340 00000000
10013750 00000000 00000000 00000000 00000000

this is the ID. but not the (producer's) serial^^

 

[AHP_person]

00050000 1010ED00

There's your game's title id, then. http://wiiubrew.org/wiki/Title_database

 

[BullyWiiPlaza]

Dumping in TCP Gecko.NET is slooooow. It needs about 15 minutes to do the range 10000000 to 3B000000. I thought that the USB Gecko was slow with its 2 minutes for memory range 90. -_-
Any tips to cut this time though? Maybe smaller dumping ranges, slower graphical interface updating in TCP Gecko.NET or more efficient data transmission? My Internet speed is 50.000 DSL so I can download much quicker than this and it's just transmission in the local network.

Downloading 1 GB from the Internet: 3 minutes
Dumping 688 MB with Gecko: 15 minutes (what?)

 

[LawnMeower]

Dumping in TCP Gecko.NET is slooooow. It needs about 15 minutes to do the range 10000000 to 3B000000. I thought that the USB Gecko was slow with its 2 minutes for memory range 90. -_-
Any tips to cut this time though? Maybe smaller dumping ranges, slower graphical interface updating in TCP Gecko.NET or more efficient data transmission? My Internet speed is 50.000 DSL so I can download much quicker than this and it's just transmission in the local network.

Downloading 1 GB from the Internet: 3 minutes
Dumping 688 MB with Gecko: 15 minutes (what?)

for me dumping 900MB + a bit more (until it froze) took 13 minutes. Maybe you could try reducing the distance between your wii u and the router.
My Wii U is is about 2.5m away from the router and the router is connected to my computer by a very short patch cable.
But as soon as you can expect in what range snipped to search for cheats you can reduce the duration a lot

 

[BullyWiiPlaza]

@CosmoCortney
Alright, I have everything wireless. Laptop about 2 meters away from the router and Wii U about 5. The benchmarks make sense, I didn't "optimize" my setup.

Also with TCP Gecko.NET I noticed that the game sometimes freezes for no reason. It's not really good right now.

 

[MrRean]

getting there :\

 

[loco365]

Well, I'm just admittedly feeling a bit off that I'm far behind, that people seem to be progressing with the scene, that's all.

I wouldn't be complaining that you're "far behind". People on 5.4.0 are "far behind" because work is still being done to finish the exploit for public use still (Granted - there are people here that have access to it because they're in the loop with this, but that's beyond the point) because of the reliability issues that MrRean mentioned. However, these issues are being addressed by people that are probably working on other projects that are equally as important (Such as, perhaps, firmware spoofing) right now.

 

[kardus]

If FW spoofing became a reality, would it be possible to do the Wii U "system transfer" from a higher FW (let's say 5.5) to 5.3.2 whilst retaining all saves and other data without screwing anything up?

I am on 5.4 right now, I sort of regret updating. I'm going to do the nand dump mod soon before updating again so at least I will have a 5.4 dump.

 

[TobiasAmaranth]

For me, the scene has only until Mario Maker launches to create firmware spoofing. Mario Maker for me is a higher priority than the hacks, due to the online requirements of it. Likewise being able to access the game updates cleanly. I think you guys are doing a lot of needed stuff, but if firmware spoofing doesn't make it in two weeks, I'll be 'forced' to update. I hope that by then, you at least have a solution for us.

 

[MrRean]

Firmware spoofing is a no.



for a bit

Anyways, new video is done. I just have to convert it to an MP4 and we'll be good for uploading.

 

[Marionumber1]

For me, the scene has only until Mario Maker launches to create firmware spoofing. Mario Maker for me is a higher priority than the hacks, due to the online requirements of it. Likewise being able to access the game updates cleanly. I think you guys are doing a lot of needed stuff, but if firmware spoofing doesn't make it in two weeks, I'll be 'forced' to update. I hope that by then, you at least have a solution for us.

To clarify, it is fairly likely that the update process is fully controlled by IOSU. I did an experiment where I patched connect() to fail before trying to start Smash, and it prompted me for an update, which it would not do if internet connectivity worked. This indicates that the update process is internal to IOSU, and nothing we do on the PPC can stop that.

 

[BullyWiiPlaza]

Anyways, new video is done. I just have to convert it to an MP4 and we'll be good for uploading.

In case people haven't realized, I'm also making tutorial videos like crazy so check out my YouTube too.