Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,134,852
  • Replies Replies 21,104
  • Likes Likes 29
Yeah, there's two different things, it's the little chunk at the top of Fail0verflow's fancy graph https://fail0verflow.com/blog/2014/console-hacking-2013-omake.html
32GB eMMC/MLC + 2x512MB NAND/SLC, for the 32GB of game storage that came with the console and the two-bank NAND for vWii+Wii U, which comes up to 33GB (or 9GB if you have the cheapo 8GB Wii U) and since most testing right now is with raw dumps cause there's no shrinker rn, you need 64GB or more cause the 33GB just barely exceeds a 32GB card, not promising anything cause I know nothing about the SALT team but there'll hopefully be some way to shrink it down later on cause releasing with that big of a requirement is gonna be eh
 
Yeah, there's two different things, it's the little chunk at the top of Fail0verflow's fancy graph https://fail0verflow.com/blog/2014/console-hacking-2013-omake.html
32GB eMMC/MLC + 2x512MB NAND/SLC, for the 32GB of game storage that came with the console and the two-bank NAND for vWii+Wii U, which comes up to 33GB (or 9GB if you have the cheapo 8GB Wii U) and since most testing right now is with raw dumps cause there's no shrinker rn, you need 64GB or more cause the 33GB just barely exceeds a 32GB card, not promising anything cause I know nothing about the SALT team but there'll hopefully be some way to shrink it down later on cause releasing with that big of a requirement is gonna be eh
Ah many MANY thanks for the explanation!
Surely cleared up all my questions. :)
 
Yeah, there's two different things, it's the little chunk at the top of Fail0verflow's fancy graph https://fail0verflow.com/blog/2014/console-hacking-2013-omake.html
32GB eMMC/MLC + 2x512MB NAND/SLC, for the 32GB of game storage that came with the console and the two-bank NAND for vWii+Wii U, which comes up to 33GB (or 9GB if you have the cheapo 8GB Wii U) and since most testing right now is with raw dumps cause there's no shrinker rn, you need 64GB or more cause the 33GB just barely exceeds a 32GB card, not promising anything cause I know nothing about the SALT team but there'll hopefully be some way to shrink it down later on cause releasing with that big of a requirement is gonna be eh
We weren't really going to comment on this yet as this stuff's still under development but we'll support creating shrunken mlc images. The minimum SD requirement will ultimately be around 16GB for all consoles, I think. If you're a 32gb owner and you want to keep your entire mlc (onboard storage) usable, you'll need 33GB of space on a 64+GB card. The rest of the SD card is all fat32-formatted, and usable for other cool stuff we have planned.
Additionally, our backup format for system storage (2xslc + mlc + otp and seeprom) dumps has some really smart compression to keep the backup filesizes waaay down.
 
We weren't really going to comment on this yet as this stuff's still under development but we'll support creating shrunken mlc images. The minimum SD requirement will ultimately be around 16GB for all consoles, I think. If you're a 32gb owner and you want to keep your entire mlc (onboard storage) usable, you'll need 33GB of space on a 64+GB card. The rest of the SD card is all fat32-formatted, and usable for other cool stuff we have planned.
Additionally, our backup format for system storage (2xslc + mlc + otp and seeprom) dumps has some really smart compression to keep the backup filesizes waaay down.

Wew that sounds swell
 
https://github.com/shinyquagsire23/gx2test


In case anyone wants a decent GX2 example for WUT with actual multitasking. GX2 init and deinit can be a bit of a pain with multitasking, might be able to make it a bit cleaner but idk. Based on dimok's mildly sketchy colored cube example.
 
  • Like
Reactions: I pwned U!
https://github.com/shinyquagsire23/gx2test


In case anyone wants a decent GX2 example for WUT with actual multitasking. GX2 init and deinit can be a bit of a pain with multitasking, might be able to make it a bit cleaner but idk. Based on dimok's mildly sketchy colored cube example.


Now you just need a microfibre cloth, and just apply it to the right hand side. :3

We need benchmark tools. :D
 
There hasn't really been any proof of an exploit, has there? I mean, there are trusted devs, but HE was one too, and how'd that go?

Sent from my SM-G900V using Tapatalk
 
There hasn't really been any proof of an exploit, has there? I mean, there are trusted devs, but HE was one too, and how'd that go?

Sent from my SM-G900V using Tapatalk
I think the common key existing publicly is enough of at least one, and HE sent me the SSL key forever ago which I verified when I "theoretically" got my hands on an exploit too
 
Heh, thank god I have a 128GB SD card. But a 32GB NAND? Fuck..

I would assume it would be fast to dump though because..most of it would be empty data..or is that not the case?
 
Heh, thank god I have a 128GB SD card. But a 32GB NAND? Fuck..

I would assume it would be fast to dump though because..most of it would be empty data..or is that not the case?
Well it's encrypted by default so no it's not "empty" (all zeroes) but it should be decently fast since it's flash memory to flash memory, depending on the algorithm used to dump it all
 
  • Like
Reactions: DKB
I think the common key existing publicly is enough of at least one, and HE sent me the SSL key forever ago which I verified when I "theoretically" got my hands on an exploit too
Woah you can feel the IOSU with your hands? I knew it was elusive, but I would of never figured it had tangible properties as well.
 

Site & Scene News

Popular threads in this forum