Hacking Can emunand created on one 3ds be used on another?

[Sketchy1]

Idk why I bothered asking in the title cause I know the answer is no, but before you bombard me with "no you dumb ass" and "nobody uses emunand anymore switch to a9lh", just know that I created this thread cause I want to know the TECHNICAL details as to why it isn't.

Thanks

 

[xtheman]

No it cannot. It is console specific and therefor won't boot on a different console

(Also you can use emunand with a9lh)

 

[Hayleia]

If your goal is to share the same Nintendo 3DS subfolder(s), you can achieve that result by playing around with your movable.sed files.

 

[Deleted member 370671]

No, it can't. Each nand (or emunand) is encrypted using console unique keys, which are... unique. If you try to use an emunand from a 3DS on another 3DS, the other 3DS won't be able to boot because it won't have the necessary keys to decrypt it.

However, what you can do to get (almost) the same result, is to dump the first console's specific files with Decrypt9 (ticket.db, title.db, SecureInfo_a, etc...) and inject them into the target console's *emunand* (DON'T inject them into sysnand, or brixx). If you do that, don't forget to back up the emunand of the second 3DS before attempting anything.

 

[Sketchy1]

OK thanks. And I'm not trying to attempt or achieve any specific goal, I was just wondering why it could not be done.

Also, could you not just edit a nand dump from the console the emunand was created from and inject the target consoles files into it? That would invalidate existing content, no?

 

[Deleted member 370671]

OK thanks. And I'm not trying to attempt or achieve any specific goal, I was just wondering why it could not be done.

Also, could you not just edit a nand dump from the console the emunand was created from and inject the target consoles files into it? That would invalidate existing content, no?

Well, you can't edit a nand dump: the only way to inject those files is to do it from the 3DS itself, since only the console can decrypt the nand/emunand. But yes, you can inject those files into the first 3DS.
I'm not sure what you mean by "invalidate existing content", but if you mean that you won't be able to launch the games you installed on the 1st 3DS anymore, then yes. Only the games installed from the 2nd 3DS (or the 1st 3DS after injecting the files) will be usable.

 

[Sketchy1]

Well, you can't edit a nand dump: the only way to inject those files is to do it from the 3DS itself, since only the console can decrypt the nand/emunand. But yes, you can inject those files into the first 3DS.
I'm not sure what you mean by "invalidate existing content", but if you mean that you won't be able to launch the games you installed on the 1st 3DS anymore, then yes. Only the games installed from the 2nd 3DS (or the 1st 3DS after injecting the files) will be usable.

If you have the xorpads or the dump was created with decrypt9, osfmount can edit/extract/inject

 

[HyperT]

As no one's mentioned it. The ctrNAND is transferrable. Extract ctrnand from emunand of system #1; transfer and reinject into system #2

 

[Sketchy1]

As no one's mentioned it. The ctrNAND is transferrable. Extract ctrnand from emuband of system #1; transfer and reinject into system #2

Savage