How to get themes on emunand "WITHOUT" unlinking your emunand from your sysnand

The Catboy · Feb 8, 2016

Ominous66521 said:
I have the eshop working just fine on rx-e 10.5 linked and I've downloaded game updates so that's not true....well atleast for me.

Then my information is either out of date or incorrect. If someone else can confirm this for me, that would be awesome!
Edit: Although, I still see no reason to keep them linked. I have my 3DS to coldboot straight into my CFW's, well my sysNAND just chills untouched.

kingaz · Feb 10, 2016

Crystal the Glaceon said:
I don't see why anyone would want to keep their NANDs linked. Hell, I was able to use emunand tool and Gateway to make make a back of my NAND, unlink, then use the backup to completely restore my sysNAND to my emuNAND. I lost nothing, my NNID was able to work.
Honestly, keeping them linked, just seems like a silly thing to do when it's easy to unlink and keep your sysNAND untouched and safe.

Woah woah, hold on. This works?!? I have so many questions!

1) Can you still access all of your stuff in both emuNAND and sysNAND? Or rather, say you downloaded Super Mario 3D Land legitimately from the eshop years ago, before Gateway or CFW or whatever. Would that game be accessible from both NANDs? (Obviously something like Fire Emblem Fates would not be accessible from Sysnand in either case).

2) How did you get your NNID transferred over to emuNAND?

3) Are you sure that your emuNAND didn't go right back to saving out of the first 3DS folder when you restored it?

wormdood said:
the main point is safety . . . setting up a theme is secondary at best

Alright, so I know that with linked NANDs, accessing the sysNAND System Settings deletes all of your CIAs. You also have to unwrap every game that isn't in both NANDs every time. It's also tricky (but not impossible) to set up coldbooting to CFW with Linked NANDs, and similarly tricky to set up separate custom themes. I also guess that it's easier to accidentally update sysnand when they're linked? Idk...

So aside from this handful of hassles, what are the actual risks to Linked NANDs? I've read stuff about patches and updates, but what's the deal?

Deleted User · Feb 10, 2016

kingaz said:
Alright, so I know that with linked NANDs, accessing the sysNAND System Settings deletes all of your CIAs

Just tried that and all my CIA's are just fine on rxtools.What cfw are you on?

kingaz · Feb 11, 2016

Ominous66521 said:
Just tried that and all my CIA's are just fine on rxtools.What cfw are you on?

Oh, I haven't had this problem. I'm actually pretty slow to the party (just installed Cakes the other day!). I just know that this is a common problem, and that people have had their systems delete their CIAs with invalid signatures when they went into system settings on sysNAND (emuNAND is fine).

This is of course avoided by not going into system settings on sysNAND, but since the NANDs are linked, getting two different themes to clearly differentiate them can be tricky. It can be done (my linked emuNAND currently has a lovely Okami theme with music) but it requires some trickery.

Minasodrom · Feb 11, 2016

this is really stupid, you people obviously dont understand what unlinking is and what it is for. there is no reason not to unlink, since you always have a nand backup in case something happens. you do not want to have your 2 NANDs using the same folder on the sd, that can lead to problems and in some cases even updating emunand updated sysnand. since your not using sysnand why have it linked in the first place?

kingaz · Feb 11, 2016

Minasodrom said:
you do not want to have your 2 NANDs using the same folder on the sd, that can lead to problems and in some cases even updating emunand updated sysnand.

Do you have a source? People keep throwing this assertion out there, that updating a linked emuNAND risks updating the sysNAND, and yet the more I read, the more I find people who most likely only thought that they were updating emuNAND.

This is what has been bothering me when researching this topic. On the one hand, I'm very concerned and curious as to when and how this phenomenon has occurred. On the other hand, I see example after example where people simply made a mistake, because it's hard to visually distinguish linked NANDs from one another thanks to the whole sharing theme data thing. It's like this tendency to get linked NANDs confused morphed into this urban legend about update data tunneling through a freaking wormhole to the linked sysNAND and magically updating it past all of the delicious hacks.

Do you, or anyone else, have anything substantial regarding this? The EmuNAND/Save Data Mega Guide GBATemp Doesn't Deserve doesn't mention a damn thing about emuNAND update risks.

Yes, there's the gift wrapping bug. Yes, there's the difficulties with the NANDs sharing themes, which screws with menuhax, cold booting CFW, and makes it easy to confuse linked NANDs. And yes, there's the risk of deleting all of your CIAs when entering data management. But these are either annoyances or risks that can be mitigated with some knowhow.

Minasodrom said:
this is really stupid, you people obviously dont understand what unlinking is and what it is for.

Bite me. I know plenty about what it is and what it is for.

Minasodrom said:
there is no reason not to unlink

What, besides not having to mess around to play my legitimate ambassador games, DSiware, and VC games? Or trust my NAND to hobbyist code in the event that something goes wrong?

Look, I concede that my attachment to my original NAND is not entirely rational. It is me being paranoid, and selectively so. Unlinking NANDs seems like good practice, and is undeniably the best choice for new systems or systems that have very little invested in terms of eShop software. But I'm stubborn, and I'm not really inclined to go ahead and format my system (even though I do have the backups) because of crap that people made up.

So, once again, can you point me to someone, anyone, who managed to update their sysNAND while clearly in emuNAND? Do you have some understanding of 3DS hardware that would make such an event seem plausible? Do you have anything of substance to offer?

If not, go patronize someone else.

Deleted User · Feb 11, 2016

Minasodrom said:
you do not want to have your 2 NANDs using the same folder on the sd, that can lead to problems and in some cases even updating emunand updated sysnand.

Not true for the rxtools video tut I used.I've updated my emunand linked multiple times with my secondary sd card and I can confirm that it only updates the emunand even if its linked so it will always kick you back to sysnand on 9.2 no matter what after the update.aslong as you update in emunand you won't have a problem no matter if they are linked or not.

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

Minasodrom said:
since your not using sysnand why have it linked in the first place?

Who sead you had to use it even if it is linked? But to answer the question some people use different entrey points then others using cold boots.I use menuhax plain and simple so I never have to touch my sysnand unless I'm updating my emunand since after updating the emunand it bounces back to 9.2 sysnand everytime no matter if you are linked or unlinked

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

kingaz said:
(just installed Cakes the other day!)

Ah thanks for answering my question,I use rxtools so there might be some differences with our linked nands and possibly different bugs when unlinking aswell .Hopefully this tut will come in handy if you ever want to theme you're emunand before unlinking.I would wait untill a proper video tut comes out showing you everything that happens after the unlink so you know what you could possibly lose rather then take random people's words for granted.Anyways good luck

Minasodrom · Feb 14, 2016

kingaz said:
What, besides not having to mess around to play my legitimate ambassador games, DSiware, and VC games? Or trust my NAND to hobbyist code in the event that something goes wrong?

Look, I concede that my attachment to my original NAND is not entirely rational. It is me being paranoid, and selectively so. Unlinking NANDs seems like good practice, and is undeniably the best choice for new systems or systems that have very little invested in terms of eShop software. But I'm stubborn, and I'm not really inclined to go ahead and format my system (even though I do have the backups) because of crap that people made up.
If not, go patronize someone else.

the updating issue may be made up, it does seem very unlikely. but is it worth the risk and is it smart to put this under GUIDES AND TUTORIALS, while people that dont figure this out by themselves, clearly dont know enough to have their nands linked?
the eshop and save loss is always brought up and its bogus, you know that. you cant lose your ambassador games and they are still legitimate (NNID is a thing), they just dont work on emunand (without workaround).
Dsiware and vc need a workaround (installed on emunand and sysnand), but still less of a hassle than switching sd cards (and since installed on nand storage no extra space used), problems with acessing data management in sysnand or having your wireless settings saved in sysnand etc.
Your NAND is not being tampered with, its just being loaded by cfw. and if something happens by installing corrupted cia (practically never) you have your backup handy.
what if nintendo brings out an update that reencryps the nands sd files and acessing them in sysnand wipes them? while unlikely, it could happen. in unlinked emunand not even theoretically.

i respect that you want to keep your system unformated, and i actually dont want to convince you spesifically otherwise.
just dont convince noobs to do it.

GBAtemp Official Catboy™: Boywife

Well-Known Member

Deleted User

Guest

Well-Known Member

Well-Known Member

Well-Known Member

Deleted User

Guest

Well-Known Member

Similar threads

Popular threads in this forum