Hacking Contenthax - a Vulnerability in Wii U File System Verification

  • Thread starter Thread starter VinsCool
  • Start date Start date
  • Views Views 186,511
  • Replies Replies 1,235
  • Likes Likes 43
It won't because some memory adresses are different.

I know because I had to give to FIX some debugging stuff from my wiiu running Kirby so he could port it to Brain age :D
thats more than likey region specific then, N probably didn't make their emu region free just like any of their other titles. BTW I'm just guessing lol
 
Last edited by KevinX8,
I get an error whenever I try to upload:

Code:
>>> w.up("rom.zip", "/vol/storage_usb01/usr/title/00050000/10179C00/content/0010/rom.zip")

up error : could not open /vol/storage_usb01/usr/title/00050000/10179C00/content/0010/rom.zip

-1

Any ideas? Cheers
 
I get an error whenever I try to upload:

Code:
>>> w.up("rom.zip", "/vol/storage_usb01/usr/title/00050000/10179C00/content/0010/rom.zip")

up error : could not open /vol/storage_usb01/usr/title/00050000/10179C00/content/0010/rom.zip

-1

Any ideas? Cheers
old version of brain age just like me, re download it from eshop should give you latest version
 
Anyone tinkering with files on mlc? I say that the wiiU comes with "Netflex" by default. I'd like to get my hands on this app.
 
Thanks, but no it's the newest version, freshly installed. I downloaded the original rom.zip as a backup, that worked fine, but I can't upload the new one.
oh wait just noticed you were installing to usb, it errored out for me too when I tried that, just gave up and put it on NAND instead
 
I get an error whenever I try to upload:

Code:
>>> w.up("rom.zip", "/vol/storage_usb01/usr/title/00050000/10179C00/content/0010/rom.zip")

up error : could not open /vol/storage_usb01/usr/title/00050000/10179C00/content/0010/rom.zip

-1

Any ideas? Cheers

try
vol/storage_usb
instead of
vol/storage_usb01
 
This is from a meta.xml file
Code:
<direct_boot type="unsignedInt" length="4">0</direct_boot>
Anyone have thoughts on what this could mean or be used for?
 
This is from a meta.xml file
Code:
<direct_boot type="unsignedInt" length="4">0</direct_boot>
Anyone have thoughts on what this could mean or be used for?
This should determine if an app can be set as AutoBoot or not (SystemConfigTool checks this. And if this one is set to 1, you can set this app as Autoboot)
 
This should determine if an app can be set as AutoBoot or not (SystemConfigTool checks this. And if this one is set to 1, you can set this app as Autoboot)
Sorry for being daft here, but what is the context of "AutoBoot"? Does this set this as a cold launch boot? Or has some other context?
 
Sorry for being daft here, but what is the context of "AutoBoot"? Does this set this as a cold launch boot? Or has some other context?
in the OP it talks about the system.xml file that automatically lauched whatever title you put in the default title place, you are pretty much guarranteed to brick thought as It's more than likely hash checked
 
Sorry for being daft here, but what is the context of "AutoBoot"? Does this set this as a cold launch boot? Or has some other context?
I guess you can set HomebrewLauncher as Autoboot if you set this Value to 1 AND edit the Autoboot Title in system.xml in /vol/system/config . This is just a speculation and I wouldn't try it on SysNAND.

--------------------- MERGED ---------------------------

I guess you can set HomebrewLauncher as Autoboot if you set this Value to 1 AND edit the Autoboot Title in system.xml in /vol/system/config . This is just a speculation and I wouldn't try it on SysNAND.

in the OP it talks about the system.xml file that automatically lauched whatever title you put in the default title place, you are pretty much guarranteed to brick thought as It's more than likely hash checked
Probably it bricked for the guy because in the meta.xml of the App he wanted to use as Autoboot had the value 0 instead of 1 in <direct_boottype="unsignedInt"length="4">0</direct_boot>
Probably it will work if the value is set to 1?

Would try it on RedNAND but not on SysNAND
 
  • Like
Reactions: Ryccardo
upload_2016-11-10_22-58-25.png

whatever nintendo changed @Afraidium they did a really good job hiding it, same file sizes and everything not even a byte of a difference extracted however the MD5 never lies:
WII U ROM: F30707665AF444433945328D9D1E5446
REAL EU ROM: 588B392DFD20E8C670AB3A2B2EE79CD8
 
Last edited by KevinX8,
The reason I am asking is because this is inside of "\vol\storage_mlc01\sys\title\00050010\10040100\meta\meta.xml"
Which I believe is the wiiU system menu title. It's set 0 on the directboot attrib.
 

Site & Scene News

Popular threads in this forum