Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,073,040
  • Replies Replies 21,104
  • Likes Likes 29
No, first you have to pack the folder into an archive using SARCPack (you'll need to use command prompt because for whatever reason it doesn't like drag/drop, just "sarcpack.exe/py folder"), and then compress that archive using yaz0enc to get the SZS file. I'll fix that stuff some time when it finally matters.

Shot044.png
I can't get the program to work.....
 
sorry to ask again. was it the end of this month we are hopeing to see some releases? i did try looking for the answer but there is so many pages to this thread
 
sorry to ask again. was it the end of this month we are hopeing to see some releases? i did try looking for the answer but there is so many pages to this thread

The target is E3 which I think is in June. Most likely the main goal of exploits and porting to 5.3.2 maybe 5.4 if compatible should be done by E3. If not before then... But if I was a betting man I would say E3 is the time you likely to see a public release
 
  • Like
Reactions: jammybudga777
Forget it... now I know how. ;)

It seems like you're just starting out with this stuff, at least the type of programs and the command line.. Though, you should probably learn somewhere else, and not the hacking discussion thread. It's nice to see someone messing with NSMBU though. Hope you can make some custom levels some day. Anyway, here's a basics to command line website. Should probably read it if you plan on continuing in the scene. A lot of programs start as cmd tools and get GUIs later.
 
  • Like
Reactions: AboodXD and yahoo
My mario kart is version 3. So i'm guessing thats the latest? I've erased all my internet settings now until I get some time to block all the IP's through my router.

Have I missed something? Was there something that one could do with MK8 that they can't if they aren't on the latest version??
 
Hey,

Does anyone here have access to the Mario Kart 8 BFRES files? I'd like to mess around with some of the course models, but I don't know how to rip the game, etc.
 
Hey,

Does anyone here have access to the Mario Kart 8 BFRES files? I'd like to mess around with some of the course models, but I don't know how to rip the game, etc.

Google for the .WUD (the public cant currently rip Wii U disks) and use DiscU to decrypt and look through the filesystem
 
Can dumps be scrubbed yet? The only reason I haven't started looking into character modding is because I can't sneak a 24GB .WUD past my ISP lol.
 
It seems like you're just starting out with this stuff, at least the type of programs and the command line.. Though, you should probably learn somewhere else, and not the hacking discussion thread.

OK, but I know a little programming and I know how to use the command prompt, this is the command line I needed: SARCPack-0.2.exe 1-1\
It's nice to see someone messing with NSMBU though. Hope you can make some custom levels........
I'm working on a one, also I'm doing some texture editing, then I would ask NWPlayer123 if he can test thing for me.
Uhm, ObjectData/Mario.szs maybe?

lol, I'm sooo stupid, I carelessly checked that folder earlier, but now searched it again and I found the file, thanks Kinnay.
 
Ok, I have a small nuisance to report. As I mentioned a few pages ago, the current bug we're looking at doesn't work in firmwares lower than 3.0.0, because Nintendo implemented the Internet Browser on firmware 2.0.0 using a really old WebKit version as basis (534.52). It was later updated on firmware 3.0.0 (536.28) and has stayed the same up to firmware 5.3.2.
Considering that the IOSU exploit was designed with firmware 3.x in mind and it would be easier for me to test the new WebKit bug on firmware 3.x, I'm going to update my Wii U to firmware 3.0.1. This means I won't waste any more time looking for a way to exploit the browser for firmware 2.1.1.
I hope this is not a problem (I really doubt anyone would be interested in seeing an exploit for such an old firmware version anyway) since I began by stating that I would try to port an exploit for each firmware I could find.
 
Ok, I have a small nuisance to report. As I mentioned a few pages ago, the current bug we're looking at doesn't work in firmwares lower than 3.0.0, because Nintendo implemented the Internet Browser on firmware 2.0.0 using a really old WebKit version as basis (534.52). It was later updated on firmware 3.0.0 (536.28) and has stayed the same up to firmware 5.3.2.
Considering that the IOSU exploit was designed with firmware 3.x in mind and it would be easier for me to test the new WebKit bug on firmware 3.x, I'm going to update my Wii U to firmware 3.0.1. This means I won't waste any more time looking for a way to exploit the browser for firmware 2.1.1.
I hope this is not a problem (I really doubt anyone would be interested in seeing an exploit for such an old firmware version anyway) since I began by stating that I would try to port an exploit for each firmware I could find.

Great work! Man I can't wait until the release!!!!!! :D
 
Ok, I have a small nuisance to report. As I mentioned a few pages ago, the current bug we're looking at doesn't work in firmwares lower than 3.0.0, because Nintendo implemented the Internet Browser on firmware 2.0.0 using a really old WebKit version as basis (534.52). It was later updated on firmware 3.0.0 (536.28) and has stayed the same up to firmware 5.3.2.
Considering that the IOSU exploit was designed with firmware 3.x in mind and it would be easier for me to test the new WebKit bug on firmware 3.x, I'm going to update my Wii U to firmware 3.0.1. This means I won't waste any more time looking for a way to exploit the browser for firmware 2.1.1.
I hope this is not a problem (I really doubt anyone would be interested in seeing an exploit for such an old firmware version anyway) since I began by stating that I would try to port an exploit for each firmware I could find.

I'm sure only a very very small handful people are on that firmware anyway. Makes sense to focus on higher firmware. Are you already working on the IOSU exploit?

I'm looking forward to your release :)
 
Sigh... I'll have to correct myself again. Apparently, firmware 3.0.1 still has WebKit 534.52!
After updating and noticing this, I decided to dig a bit through logs and code to come up with a reliable layout for the WebKit updates:
Code:
2.0.0 -> Version: 0x08 (534.52)
2.1.0 -> Version: 0x14 (534.52)
3.0.0 -> Version: 0x31 (534.52)
4.0.0 -> Version: 0x59 (536.28)
4.1.0 -> Version: 0x66 (536.28)
5.0.0 -> Version: 0x71 (536.28)
5.1.1 -> Version: 0x82 (536.28)
5.3.0 -> Version: 0xB1 (536.28)
5.3.1 -> Version: 0xC1 (536.28)

As you can see, Nintendo only updated the WebKit base version on firmware 4.0.0. Fail0verflow's presentation confirms this when you take into account that it took place December 2013 and comex mentions Nintendo having updated WebKit a few months ago (that update was 4.0.0 on October 2013).
Anyway, as expected, the bug still doesn't work on firmware 3.0.1 and it only works on firmware 4.0.0 and higher. To the end user, this is yet another reason to update to 5.3.2 as soon as possible.
To me, this means I won't be able to test the bug on my own unit without updating to 4.0.0, so I will leave it at 3.0.1 and port the use-after-free bug instead. This way I can still use it for the IOSU exploit and to dump the keys.
 

Site & Scene News

Popular threads in this forum