Will the emuNAND in this cfw require 25GB partitioned on your sd card? The same size as the switch's flash memory? Can't remember how emunand works storage wise.
My guess is users of an emuNAND will require a microSD card that's at least 64GB.
Hmm that doesn't seem very practical. You would need a very large sd card if you plan to go all digital. But that really shouldn't bother me. I buy all my games physical anyway. This is the first console I actually feel like supporting. I hacked most of my consoles for free gamez in the past. Im not doing that this time around.
Edit: aaand qouted the wrong person and read it wrong facepalm
Last edited by DualBladedKirito,
It's the same thing with emuNAND on the Wii U. On the 32GB models of the Wii U, you needed an SD card bigger than 32GB, and 64GB is the next available option.
No, the emuNAND had to be loaded from the SD card.
Emunand was unnecessary with the wiiu. You could just install straight to the hdd albeit no homebrew tho.
Your right tho to use emunand on wiiu you needed an sd card. I just didn't feel the need to install emunand on my wiiu
Your right tho to use emunand on wiiu you needed an sd card. I just didn't feel the need to install emunand on my wiiu
Last edited by DualBladedKirito,
Too bad Team Salt never release their implementation of emuNAND that shrunk the 32gb model emuNAND to the smaller size.
Since no CFW-blocking or true exploit-blocking updates were ever released, there was never any reason to use an emuNAND on the Wii U. This already isn't the case with the Switch.
I remember the 5.5.2 panic
Edit: I completely botched the update number I was talking about. It's been so long since I've touched my wii u lol
Last edited by TheCyberQuake,
I'm well aware. Like I stated before: I've been a pirate on my systems. All of them. But this time around I'm all for actually buying them this time around while still having a CFW.
wrong. Just 5.5.0 and the ones after that didn't fix exploits. But previous versions did that.
We didn't have a functional emuNAND option until 5.5.0, not to mention CFW.
5.5.2 fixed the main browser exploit. But then another was discovered so it had almost no impact
But there were still exploit-blocking updates.
Haxchi worked anyways.
It still blocked out those who didn't have haxchi installed because that was a secondary entry point. Without a primary entry point you can't install the secondary entry point. Luckily we got another browser exploit.
You have a fundamental misunderstanding of how emunand in general works
Edit: Just so we're clear what I'm talking about and it doesn't just sound like I'm being an asshole (because I'm not trying to be), emunand (or any drive that's being cloned, for that matter) needs exactly as many bits OR MORE as is on the partition being copied for the new drive to not be reduced to a corrupted mess. Since Nintendo consoles have historically kept both the system and data on the same chip, but keys on a separate, very small one on the SoC for security, that means we need exactly as much as is advertised on the console box... Plus a little bit extra, which unfortunately means you need to go one size up since flash memory is only sold in powers of 8.
The reason that hasn't been an issue until now is that up until the Wii U, Nintendo never had a console with any significant amount of storage. The Wii only had 512mb, which doubled means a 1GB SD card requirement. 3DS had 2(?)GB onboard, which meant a 4GB SD card. The Wii U had an 8GB version that could skate by with a 16GB emunand, but unfortunately the "Deluxe" version required a 64GB card; as will the Switch, most likely
Also, due to some techno-bullshit I don't understand, emunand almost always has to be on an SD card, rather than a hard drive. It probably has to do with the SD bus being the same as onboard storage (since they're both flash memory) or something like that
Last edited by TotalInsanity4,
Similar threads
-
- Portal
-
- Portal
-
- Portal
-
- Portal
