Well I mean, there's no reason to not have one, if you're that worried about space then just delete it and get it over with, but some people have found several different ways to make emuNANDs extremely useful. And you can't forget people that still use Gateway in 2017 and have issues just from trying to run a sysNAND only setup.Because with A9LH you cannot lose your system even if it's sysNAND only? A9LH and it's payloads load before anything else when the console is booted, so even if sysNAND is bricked it still can be restored.
So with A9LH you can install everything without fear as well. Your reasoning for emuNAND being better as such is invalid.
Well I mean, there's no reason to not have one, if you're that worried about space then
Not really. A9LH is installed on the CTRNAND chip, which is the same location as your sysnand. If your sysnand gets bricked, there's a slim chance your A9LH installation gets corrupted. Slim, but still possible. And if Nintendo released an update that bypasses your CFW's Firm0/1 protection, you lose A9LH on your sysnand. Again, a slim thing, but not impossible.Because with A9LH you cannot lose your system even if it's sysNAND only? A9LH and it's payloads load before anything else when the console is booted, so even if sysNAND is bricked it still can be restored.
So with A9LH you can install everything without fear as well. Your reasoning for emuNAND being better as such is invalid.
Posted by accident, my reply is finished now.There is no reason to have one either if you're an average user. If you have GW then it's another story.
And the only reason for Gateway are the cheats, which I've been hearing people ask for other CFW to support out of the box, so that's one thing that should make Gateway completely obsolete.Most reasons against emuNAND are as "invalid" as the ones given by "emuNAND fans". I mean "save space"? Like I care about space on my 128GB SD card. Except for people with 4GB card, it's not possible to really care about 2GB, and in that case the solution isn't to get rid of emuNAND but to upgrade the card. Though same kind of invalid arguments on the other side with stuff like "fool-proof setup". Well technically you could restore your NAND from decrypt9 on a9lh even if you screw up badly. And you'd be really unlucky to get NAND wearing soon so there is nothing to be afraid of. So yeah, with these kind of bad arguments, everyone could argue for days without convincing anyone.
The one real reason why emuNAND is inferior to sysNAND is because of GBA VC and stuff like that that really depend on sysNAND but that are really straightforward when you are using your sysNAND as your main NAND.
And the one reason why someone would "need" an emuNAND is because of Gateway (though a better idea would be for them to support sysNAND for real...).
Not really. A9LH is installed on the CTRNAND chip, which is the same location as your sysnand. If your sysnand gets bricked, there's a slim chance your A9LH installation gets corrupted. Slim, but still possible. And if Nintendo released an update that bypasses your CFW's Firm0/1 protection, you lose A9LH on your sysnand. Again, a slim thing, but not impossible.
how A9LH is protected?If Nintendo released an update that bypassed the protection everyone's console would brick. Pretty obvious why they haven't done it. Nintendo isn't stupid, they surely know about A9LH and it's "weakness", but the problem is that they can't do anything about it without bricking everyone's consoles. Also if you install something to your sysNAND that doesn't mesh well and it gets bricked, there's no chance to brick A9LH because of what we just talked about .. it's protected.
Their recent update was a pretty nice attempt at silently bricking us, but it fell flat because Luma was prepared, doesn't stop other CFWs from getting affected though. In the event that a sysNAND gets bricked in the future, people will be glad they kept emuNAND.If Nintendo released an update that bypassed the protection everyone's console would brick. Pretty obvious why they haven't done it. Nintendo isn't stupid, they surely know about A9LH and it's "weakness", but the problem is that they can't do anything about it without bricking everyone's consoles. Also if you install something to your sysNAND that doesn't mesh well and it gets bricked, there's no chance to brick A9LH because of what we just talked about .. it's protected.
Yeah, unless said app that doesn't mesh well was (un)intentionally coded to corrupted/erase A9LH. That's another topic all together, and would rather not go into an argument about. Nintendo isn't stupid, they wouldn't risk bricking their consoles, but doesn't mean users wouldn't do something to cause it.If Nintendo released an update that bypassed the protection everyone's console would brick. Pretty obvious why they haven't done it. Nintendo isn't stupid, they surely know about A9LH and it's "weakness", but the problem is that they can't do anything about it without bricking everyone's consoles. Also if you install something to your sysNAND that doesn't mesh well and it gets bricked, there's no chance to brick A9LH because of what we just talked about .. it's protected.
Luma, for example, is created to protect A9LH by preventing it from being overwritten by Nintendo. It detects A9LH and stops writes to it.how A9LH is protected?
I'm pretty sure that's only for linked emuNANDs.waste of sd card space, obsolete, current hacks ONCE INSTALLED are relatively safe, can't have my tiny brothers in law screw their every cia and save by opening data mgmt.
I'm pretty sure that's only for linked emuNANDs.
And the only reason for Gateway are the cheats, which I've been hearing people ask for other CFW to support out of the box, so that's one thing that should make Gateway completely obsolete.
If Nintendo released an update that bypassed the protection everyone's console would brick. Pretty obvious why they haven't done it. Nintendo isn't stupid, they surely know about A9LH and it's "weakness", but the problem is that they can't do anything about it without bricking everyone's consoles. Also if you install something to your sysNAND that doesn't mesh well and it gets bricked, there's no chance to brick A9LH because of what we just talked about .. it's protected.
how A9LH is protected?