Hacking WiiU game dump's list and nfo

  • Thread starter Thread starter markehmus
  • Start date Start date
  • Views Views 256,475
  • Replies Replies 496
  • Likes Likes 6
I can confirm that it is indeed legit, I decrypted it using the key and it does have data, we can't READ it for now, but yes, it is legit. For example I found a bunch of strings for the update section http://pastebin.com/3dni1xRF and the start of the junk data I found was "FST", like here http://pastebin.com/wktNfsAU so yes, you can start the hyping properly now. Haven't looked through all of it, but that should be proof enough for now.
 
  • Like
Reactions: Marionumber1
I can confirm that it is indeed legit, I decrypted it using the key and it does have data, we can't READ it for now, but yes, it is legit. For example I found a bunch of strings for the update section http://pastebin.com/3dni1xRF and the start of the junk data I found was "FST", like here http://pastebin.com/wktNfsAU so yes, you can start the hyping properly now. Haven't looked through all of it, but that should be proof enough for now.


1st you can not "confirm that it is indeed legit". You can believe it is or think it is.
You have at best partial decrypted what you could and most likely even that is NOT 100% accurate. The update partition (which you are seeing) is duplicated a lot of times(but again you probably do not have 100% of it decrypted).
You can not run the whole image through because there are at least 2 or 3 (maybe even 4 clear unencrypted sections).
The game partition of Super.Mario.3D.World.USA WUP-P-ARDE-00-310USA-0 (I believe) begins at
0xE000 0000 (unencrypted)with the FST at
0xE000 8000 (encrypted).
The game partition of Nintendo.Land.USA WUP-P-ALCE-00-101USA-2 (I believe) begins at
0xC000 0000 (unencrypted)with the FST at
0xC000 8000 (encrypted).



2nd do NOT believe a free solution is coming from the "scene",period. If the "scene" wanted you to have the 3ds commonkey or the wiiu commonkey you would. They do NOT want you to have it or you would already have it. The scene "power" and their "currency" is trading of information.
"Who has an sdk(s)?"
"Who knows how to dump dsi or 3ds or wiiu games?(you sure don't but you could if they wanted you to)"

No, you will get the "dongle" albeit a gateway 3ds, ode or ievo usually after a expolit window is closed (like dsiwarehax or gateway 3ds.)

The true heroes are the unsung devs who anonymously post a wii commonkey or a dsi commonkey. It's really not that hard for the scene or anyone else to post to pastie or pastebin. But no one has THAT should tell you ALL you need to know.

Note to moderators:
feel free to delete the 2nd part of this post or spin it off into a new thread to prevent a flame war in this thread.
 
Well of course, as I mentioned in my last post, it might be partially corrupted simply because of the size and time it'd take, not to mention this is brand new and hardware might be flawed, and it's called a TITLE key for a reason. I realize that there are unencrypted partitions, I've been doing this for quite a while, and I have more control and knowledge of the situation then you think. And I was referring to legit as in they didn't just BS and use a script to generate some random junk and just so happen to make it look convincing and be big enough to convince some people. Nothing more then that.
 
  • Like
Reactions: Marionumber1
:: Unknown :: New.Super.Mario.Bros.U.USA.WiiU-FAKE :: Pred 8h 31m 50s ago. : Fri 30 May 2014

2qkp8n5.png


i bought my retail MK8 at 9am but havent opened it yet ... wanna open it with the kids
 
time to see some videos running wii u backups
It's too early for end-users to show videos, but I agree in regards to the developers themselves. I called BS on Gateway until they showed proof and then I couldn't throw my money at them fast enough.
 
I did some compression testing on a couple of the releases and as previosly noted they are pretty compressible. Given that big parts of the data is encrypted they should be able to make even small using a strategy similar to the wia filetype.

25025314816 (24G) pwr-ninlnd.wud
3056920574 (2.9G) pwr-ninlnd.wud.nz (nanozip)
5109812208 (4.8G) pwr-ninlnd.wud.xz (lmza2)
3037560822 (2.9G) pwr-ninlnd.wud.zpaq (zpaq)

25025314816 (24G) pwr-sm3dw.wud
2794807759 (2.7G) pwr-sm3dw.wud.nz
2818699600 (2.7G) pwr-sm3dw.wud.xz
2778839835 (2.6G) pwr-sm3dw.wud.zpaq
 
  • Like
Reactions: osirisjem
I did some compression testing on a couple of the releases and as previosly noted they are pretty compressible. Given that big parts of the data is encrypted they should be able to make even small using a strategy similar to the wia filetype.

25025314816 (24G) pwr-ninlnd.wud
3056920574 (2.9G) pwr-ninlnd.wud.nz (nanozip)
5109812208 (4.8G) pwr-ninlnd.wud.xz (lmza2)
3037560822 (2.9G) pwr-ninlnd.wud.zpaq (zpaq)

25025314816 (24G) pwr-sm3dw.wud
2794807759 (2.7G) pwr-sm3dw.wud.nz
2818699600 (2.7G) pwr-sm3dw.wud.xz
2778839835 (2.6G) pwr-sm3dw.wud.zpaq
It would be nice if you would detail your options and settings for your commands so others can duplicate or test your results with greater accuracy.
Also if these wuds compress to about 12% of their original size then no one should waste their time or bandwidth with theses fake-y, powerup-and-off release groups that should have their releases repacked and originals nuked. Just about EVERY wiiu game released by nintendo(their full catalog) from ALL regions compressed would equal the bandwidth wasted by the current releases.
One final note, it would be consistent with the way the nintendo handles the update partition duplicating the files(repeatedly) if they did this within the game partition. Hence the insane compression numbers.
 
  • Like
Reactions: Kargaroc
Process of compressing: I used 7zip, of which the settings are here, it was working about 13-18MB/s the whole way through, and eating up my hard drive speed at that, took about 21 minutes, and went from 23.3 GB (25,025,314,816 bytes) to 4.04 GB (4,349,131,023 bytes).

I put up a torrent for the 7Z, along with the original NFO and JPG I got with the original download up.
Info Hash: 68ABAF15272FAD2894B43CF3C00C0F6B53686010
 
Process of compressing: I used 7zip, of which the settings are here, it was working about 13-18MB/s the whole way through, and eating up my hard drive speed at that, took about 21 minutes, and went from 23.3 GB (25,025,314,816 bytes) to 4.04 GB (4,349,131,023 bytes).

I put up a torrent for the 7Z, along with the original NFO and JPG I got with the original download up.
Info Hash: 68ABAF15272FAD2894B43CF3C00C0F6B53686010

That's a good call on the edit. It's now easier and better to read. Also, did you try nanozip or zpaq? They seem to be smaller after compression.
 

Site & Scene News

Popular threads in this forum