Hacking why you dont like emu nand ?

  • Thread starter Thread starter aerios169
  • Start date Start date
  • Views Views 8,753
  • Replies Replies 91
I would say both are fine, it just depend of what you are used to.

Personally, I have a Gateway and doesn't have any reason to change as it works fine, so I'm keeping it. But if I was a more recent 3DS owner, I would have probably installed A9LH+Luma directly, as it's free.

About the boot rate, it's not a big problem if you, like me, often keep the 3DS in sleep mode when you know you'll play it again soon.

(But even if I have a Gateway, I only use .cia files)
 
Last edited by davhuit,
  • Like
Reactions: CreAtor135
No emuNAND because it saves 1GB and you can always start homebrew on boot if something is wrong.
On another SD Card I have a regionchanged emuNAND though.
 
For the common person, it's really not necessary. For devs it can be useful and for people wanting to change their region, but not change their sysNAND's region. Otherwise if you are just using it for your everyday gaming, it's a waste of 1GB to 2GB.
 
For the common person, it's really not necessary. For devs it can be useful and for people wanting to change their region, but not change their sysNAND's region. Otherwise if you are just using it for your everyday gaming, it's a waste of 1GB to 2GB.
That's how I am, personally. I use my nands for gaming mostly, but also for testing things out for developers, or testing an update to the system that could potentially brick it for whatever reason. If something goes wrong, a nand backup before the update saves my day. :)
 
IMO Emunand is good for a few things like keeping dev apps separated, maybe as a "second user" on the same DS if you have a kid or a sibling, brick testing, Gateway use, just extra protection(?) for paranoid people etc. It has it's uses but like others said, for the average user with CFW that has firm protection it's not necessary especially with smaller SD cards. Before A9LH was widespread an Emunand was the only way to have CFW and an updated system at the same time so it was required if you wanted hacks and to use the system as stock more or less. It still had drawbacks like having to unlink the NANDs to use eShop, installing certain CIAs on both NANDs for them to work, fear of updating sysnand on accident while using Pasta to install some games or something. So when we could most of us gave it up for ease of access, others that kept it did so for their own reasons.
 
16GB SD Card = 14.8 GB Total Capacity
emuNAND = 1.3GB Total Capacity Required
14.8 - 1.3 = 13.5GB
A GB I could use towards, games, music or pictures.
 
I have an emunand (and a9lh), I converted to dev firmware for fun :P

Yeah I really don't know what to do with it.
 
I've always had an emunand on my 64gb card so when I switched to A9LH I just restored it, it's always worked fine for me so why not keep using it
 
First of all, EmuNAND is not emulated NAND. Just like RedNAND, EmuNAND is a redirected NAND.

As for your question. It's a bit redundant for A9LH users who have a CFW with FIRM protection. It's also less convenient. I use it, for experiments and to test tools that may brick my EmuNAND, or because I'm not certain changes can be easily reversed (or I can't be bothered to change it back). After I'm done with experimented, I get my main SD card and just keep using my 3DS as normal, from SysNAND.
 
For simple people looking to use CFW for pirating, homebrew, free games ect. a9lh is perfect, plus it's fairly noob proof with guides like Plailect's, updated and really simple to follow.
 
Plot twist, I still like emunand for my purposes. Those purposes are for having two nand regions (sysnand with a working eshop, emunand with my english titles and other shit) on my n3ds, and for doing stupid stuff like sysdowngrading to 2.1 on my o3ds. None of these things should apply to the majority of people.
 
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.

Why does a console have 2 firmware partitions? Even a kids leapfrog has it. So if one gets corrupted during install, there is a fall back.

Whats stats do you have on the percentage of consoles in any generation that have ever actually relied on that fall back?

Once the loss out weighs the gain, any console company will write both partitions and reimburse those few who lost a console with no visible violation of tos in tampering.

How would a console hack brick then be viewable over a 'legitimate' hack? Do you know or are you one of those who parrot in a bullying fashion what they have heard without knowing any ins and outs of the situation?

Whats your favorite color shoe? Do you tell everyone theirs are shit cause' their not the same as your favorite?

This scene is so full of 'know all fuck all fanboys' who keep the scene stained. Theres only one guide, only one cfw, only one way, etc.. or your a fucking idiot - projection mentality. I say projection cause' maybe the fucking idiot is really the one holding that limited hierarchy attitude, but if you get everyone to support it, YOU FEEL RIGHT AND BIG ABOUT BEING A OPINIONATED KNOW ALL FUCK ALL.
 
Last edited by tivanh,
Why does a console have 2 firmware partitions? Even a kids leapfrog has it. So if one gets corrupted during install, there is a fall back.

Whats stats do you have on the percentage of consoles in any generation that have ever actually relied on that fall back?

Once the loss out weighs the gain, any console company will write both partitions and reimburse those few who lost a console with no visible violation of tos in tampering.

How would a console hack brick then be viewable over a 'legitimate' hack? Do you know or are you one of those who parrot in a bullying fashion what they have heard without knowing any ins and outs of the situation?

Whats your favorite color shoe? Do you tell everyone theirs are shit cause' their not the same as your favorite?

This scene is so full of 'know all fuck all fanboys' who keep the scene stained. Theres only one guide, only one cfw, only one way, etc.. or your a fucking idiot - projection mentality. I say projection cause' maybe the fucking idiot is really the one holding that limited hierarchy attitude, but if you get everyone to support it, YOU FEEL RIGHT AND BIG ABOUT BEING A OPINIONATED KNOW ALL FUCK ALL.
bad day?
 
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.

Didn't Nintendo just do this? Isn't this why booting GW kills A9LH on 11.3 SysNAND?
 
Last edited by el_gonz87,
  • Like
Reactions: Quantumcat
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.
A9LH is far from being risk free, there are plenty of threads made by people who permanently bricked their consoles with it. With CFW, however, you can't brick your system, the worse that could happen is that you might corrupt your emunand and have to format your SD card and start over. (You could also update sysnand by mistake, but there are ways to prevent that from ever happening)
 
Didn't Nintendo just do this? Isn't this why booting GW kills A9LH on 11.3 SysNAND?
Updating with gw as your cfw kills a9lh because gw doesn't have firm protection.

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

Emunand is slower than sysnand.
No, not really. After initial boot times (2 second difference right now for me), it is essentially the same.
 
  • Like
Reactions: gnmmarechal
Updating with gw as your cfw kills a9lh because gw doesn't have firm protection.

But I've recently seen 2 posts of people simply booting GW on 11.3 SysNAND that ended up with a brick. I think Nintendo added code that caused this in the latest update.
 
  • Like
Reactions: Quantumcat

Site & Scene News

Popular threads in this forum