Hacking Contenthax - a Vulnerability in Wii U File System Verification

  • Thread starter Thread starter VinsCool
  • Start date Start date
  • Views Views 188,670
  • Replies Replies 1,235
  • Likes Likes 43
So I just found one weird behavior with my current redNAND modifications. It seems doing anything that causes the system to reload fw.bin (entering and exiting settings) from within redNAND will cause it to load back into sysNAND. I have no clue if it still has all the sig patches but is just reading sysNAND, and I am not going to test that. So for now be VERY careful with my currently released redNAND items until I can figure out what is causing this problem

Edit:
The issue is exactly what I was thinking it was. It seems reloading firmware causes it to read from the SD root again instead of /wiiu/boot, leading me to believe it is an issue with the fw.img this time. I'll have a look into the code to see if I can figure out what to change to fix this, but if someone wants to point me in the right direction I would sure appreciate that.
You need to change the path in the fw.img too!
https://github.com/dimok789/iosuhax/blob/master/patches/0x5000000.s#L121
 
That's what I was assuming was the issue. I was just taking a look at that patch and saw that line of code right before you posted that :)
Looks like I'll be creating a fork for iosuhax as well.

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

Okay I also modified dimok's iosuhax fw.img to properly load fw.img from /wiiu/boot when reloading firmware from redNAND.
https://github.com/TheCyberQuake/iosuhax
You will have to recompile fw.img using that in order for it to properly support the other modifications I've made, mainly moving fw.img from sd root to /wiiu/boot
 
  • Like
Reactions: Quantumcat
i really appreciate you for the work but i will wait for something from any group
and in that time lets play some pokemon sun / moon :yay3ds:

aSoJFbl.jpg
 
To anyone still having trouble creating your own .tga's

bootDrcTex and bootTvTex have to be saved as 24bit uncompressed, while iconTex has to be saved as 32 bit uncompressed.

(Wasn't sure if this was said, I just know some of us had trouble)
 
To anyone still having trouble creating your own .tga's

bootDrcTex and bootTvTex have to be saved as 24bit uncompressed, while iconTex has to be saved as 32 bit uncompressed.

(Wasn't sure if this was said, I just know some of us had trouble)
Thanks for that info. That should make it easier for me to do custom icons in the future, I just kinda guessed my way through until I got it last time.
 

Site & Scene News

Popular threads in this forum