Hacking O3DS to N3DS Questions

[Ohana_Honokusu]

Hi, I want to transfer my whole emuNand from my O3DS to N3DS, but I have a few questions first:
1. Do you lose the installed CIAs upon transfer and need to install the CIAs again? If you do lose them, do you have the save data?

2. Since EmuNand works as 9.5 on N3DS, does that mean that some games can't be played?

Thanks in advance ^w^

 

[Ohana_Honokusu]

I'm using the same SD card for the transfer, I forgot to ask how can that be done too.

 

[BloodRose]

I'm using the same SD card for the transfer, I forgot to ask how can that be done too.

I don't think what you're trying to do is entirely possible. Someone more experienced and knowledgeable than me should be able to confirm either way though.

 

[Ohana_Honokusu]

Anyone? ?

 

[CrispyYoshi]

Your 3DSes read all its channels/saves/themes/etc from the /Nintendo 3DS/ folder. (Homebrew apps are typically stored at /3ds/)

Within the /Nintendo 3DS/ folder, your particular NAND reads from a specific folder based off ID information unique to the NAND. This is also why when you format a system, you change your NAND's ID, thereby "unlinking" the NANDs.

If you want your proper Nintendo 3DS folder to read from the O3DS to the N3DS, you need to transfer your NAND (including its ID) over to the N3DS, then just use that SD card on the new 3DS.

Assuming you primarily use EmuNAND for everything, do an official system settings system transfer from emunand to emunand (they must both be on the latest version, and I recommend using the same cfw, e.g. reinand for both too)

This transfer your NAND ID over to the N3DS, and allow it to read from the correct folder within SD:/Nintendo 3DS/

If you want to keep the ID on the O3DS too, back up your emunand on the o3ds, then do the system transfer and restore the backup. However, doing this would probably set some red flags to Nintendo if you used both online simultaneously. (Two different consoles sharing the same exact NAND ID)

---

If you have stuff on your SysNAND, consider using SaveDataFiler to back up your stuff. However, I'm not sure how possible this is with GBA VC (AGBSAVE9 can only do so much at the moment...) so you might lose those in the process, or just keep them on your O3DS until AGBSAVE9 can support more GBA game save formats.

---
To give you a more straight answer:

1. Installed .cias are stored within the /Nintendo 3DS/ folder (if you installed them to SD, and not NAND). Otherwise, they exist in the NAND.bin you dump. You don't have to re-install the ones on your SD card, but the ones patched to your NAND must be re-installed on the new system
2. EmuNAND only going up to 9.5 on N3DS is actually outdated information: The keys to unlock 9.5+ CFW on N3DS have been found, and nearly all modern CFWs like ReiNAND/CakesFW/AuReiNand support the latest firmware

 

[Quantumcat]

Hi, I want to transfer my whole emuNand from my O3DS to N3DS, but I have a few questions first:
1. Do you lose the installed CIAs upon transfer and need to install the CIAs again? If you do lose them, do you have the save data?

2. Since EmuNand works as 9.5 on N3DS, does that mean that some games can't be played?

Thanks in advance ^w^

The above poster went into a lot of detail, but here's a less detailed guide.

0. Delete any games on the O3DS you don't plan to play in the next month. Too much data makes the transfer get stuck.

1. You need an SD card in both 3DS consoles. If you want to eventually use the one in your O3DS in your N3DS, you need to get a new SD card, format emuNAND on it, backup the emuNAND on the old SD card, restore the backup to the new card, and copy all the files from the old card to the new card. Then put the new SD in the o3DS and put the old SD in the new 3DS. Format emuNAND on the new 3DS.

2. Update emuNAND on both consoles

3. Initiate system transfer on both consoles (in emuNAND)

5. Choose wireless data transfer when it asks

6. When the new 3DS finishes and restarts, disable wireless in sysNAND before booting to emuNAND. Cancel the transfer. Then in emuNAND, visit the eShop, log in, and exit. All your games appear.

To answer your questions, everything will be transferred, and emuNAND can be updated to the latest nowadays, as long as you use an up to date CFW.

 

[CrispyYoshi]

If you want to eventually use the one in your O3DS in your N3DS, you need to get a new SD card, format emuNAND on it, backup the emuNAND on the old SD card, restore the backup to the new card, and copy all the files from the old card to the new card. Then put the old SD in the new 3DS. Format emuNAND on it.

Wait, will this really work from O3DS to N3DS? NAND.bin dumps are different in size and also unique to the console.

Also, this person might also have some data on SysNAND, like GBA VC injections.

 

[Quantumcat]

Wait, will this really work from O3DS to N3DS? NAND.bin dumps are different in size and also unique to the console.

Also, this person might also have some data on SysNAND, like GBA VC injections.

Not sure what the size of the NAND.bin has to do with it, we aren't dumping or restoring sysNAND? The bit about restoring emuNAND is just to move it to a new card so that the card that the OP wants will eventually be used with the N3DS. I'm not sure about DSi or GBA because I didn't use any when I did my system transfer from o3DS to n3DS, but, all my non-legit CIAs came over. However when I did a system transfer from n3ds to n3ds I was not able to use wireless data transfer and my non-legit cias did not come over. So it's the wireless data transfer that's the crucial part to keeping all your data.

Edit: fixed my first reply to make it a little clearer

 

[CrispyYoshi]

Not sure what the size of the NAND.bin has to do with it, we aren't dumping or restoring sysNAND? The bit about restoring emuNAND is just to move it to a new card so that the card that the OP wants will eventually be used with the N3DS. I'm not sure about DSi or GBA because I didn't use any when I did my system transfer from o3DS to n3DS, but, all my non-legit CIAs came over. However when I did a system transfer from n3ds to n3ds I was not able to use wireless data transfer and my non-legit cias did not come over. So it's the wireless data transfer that's the crucial part to keeping all your data.

Ahh I see! Thanks for the clarification.

 

[Ohana_Honokusu]

Thanks for the help, Guys

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

The above poster went into a lot of detail, but here's a less detailed guide.

0. Delete any games on the O3DS you don't plan to play in the next month. Too much data makes the transfer get stuck.

1. You need an SD card in both 3DS consoles. If you want to eventually use the one in your O3DS in your N3DS, you need to get a new SD card, format emuNAND on it, backup the emuNAND on the old SD card, restore the backup to the new card, and copy all the files from the old card to the new card. Then put the new SD in the o3DS and put the old SD in the new 3DS. Format emuNAND on the new 3DS.

2. Update emuNAND on both consoles

3. Initiate system transfer on both consoles (in emuNAND)

5. Choose wireless data transfer when it asks

6. When the new 3DS finishes and restarts, disable wireless in sysNAND before booting to emuNAND. Cancel the transfer. Then in emuNAND, visit the eShop, log in, and exit. All your games appear.

To answer your questions, everything will be transferred, and emuNAND can be updated to the latest nowadays, as long as you use an up to date CFW.

Also, you mentioned to format emuNand, you mean to format it with the tool after copying everything?

 

[Quantumcat]

Thanks for the help, Guys

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


Also, you mentioned to format emuNand, you mean to format it with the tool after copying everything?

I mean create emuNAND (e.g. with emunand9 or the Gateway menu).

 

[Ohana_Honokusu]

I mean create emuNAND (e.g. with emunand9 or the Gateway menu).

Oh right. Thanks for clearing it up

 

[Ohana_Honokusu]

I'm using RXTools on O3DS, does that mean I will need to use RXTools during the transfer and RXTools can be updated with latest firmware on N3DS, right?

EDIT: I'm asking if it RXTools needs to be used on N3DS during the transfer too

 

[Quantumcat]

I'm using RXTools on O3DS, does that mean I will need to use RXTools during the transfer and RXTools can be updated with latest firmware on N3DS, right?

EDIT: I'm asking if it RXTools needs to be used on N3DS during the transfer too

No, you can use any CFW you want on the N3DS. I would recommend something other than rxTools.

 

[Ohana_Honokusu]

No, you can use any CFW you want on the N3DS. I would recommend something other than rxTools.

So I can switch to a different one after transfer? Good. Which one would you recommend?

 

[Quantumcat]

So I can switch to a different one after transfer? Good. Which one would you recommend?

I'm not actually sure because I moved directly from Gateway to Cakes (A9LH). I have heard very good things about AuReinand. (By the way, if you ever plan to use A9LH, now is a good time to do it because with a stock new 3ds with nothing done to it yet, you can follow the guide exactly as written and not have to work out what steps to skip).

 

[Ohana_Honokusu]

I'm not actually sure because I moved directly from Gateway to Cakes (A9LH). I have heard very good things about AuReinand. (By the way, if you ever plan to use A9LH, now is a good time to do it because with a stock new 3ds with nothing done to it yet, you can follow the guide exactly as written and not have to work out what steps to skip).

Is there a guide to this A9LH Process?

 

[Quantumcat]

Is there a guide to this A9LH Process?

Yep, https://github.com/Plailect/Guide/wiki

 

[Ohana_Honokusu]

Yep, https://github.com/Plailect/Guide/wiki

Thanks

 

[Ohana_Honokusu]

Sorry for the late response. After looking over some of the process it mentioned some of things you would do to start off homebrew and you mentioned a stock new 3DS (it's new and wasn't even turned on yet) should I do this process after setting up emunand and the transfer or do I do it right from starting it up and then transferring?