Tutorial  Updated

Swap sysnand and emunand (arm9loaderhax only)

Arm9loaderhax coupled with AuReiNand gives us lucky 3DS users the amazing option of running Custom Firmware on sysnand. The advantages of this are as follows:
  • Much faster and more reliable CFW cold booting compared to menuhax + emunand
  • Slightly faster CFW cold booting compared to arm9loaderhax + emunand
  • Using 2GB of SD card space for emunand is no longer needed (but still recommended to keep a 9.2 emunand around)
  • GBA ROMs only need to be installed once, since they run from sysnand now!

Most CFW users will already have a 9.2 sysnand which is usually kept as vanilla as possible, and then an emunand running a higher FW version (i.e. 10.5) booted through CFW. With arm9loaderhax and AuReiNand, we can now swap the firmware versions over so 10.5 runs directly on SysNand, and EmuNand is used only when 9.2 is really needed (e.g. for running decrypt9). This tutorial will walk you through the process of swapping your sysnand and emunand, and changing your arm9loaderhax to use AuReiNand in order to cold boot directly to a patched 10.5 sysnand.

This tutorial assumes the following:
  • You have a 9.2 or below sysnand and CFW running an emunand of a higher firmware version
  • You know how to verify a SysNAND backup using md5
  • You know how to back up your sysnand, emunand and SD card
  • You know how to access hax to get to the Homebrew Launcher
  • You know how to install homebrew apps on your 3DS
  • You know how to install CIAs
  • You have already captured your OTP and built an arm9loaderhax installer
  • You have FBI installed on your sysnand
I won’t explain how to do all of these as this guide is intended to be an overview of the process I used to swap my sysnand and emunand.


If you follow this guide and do not have a valid sysnand backup, you risk bricking your console and this may not be recoverable without a hardmod.

This guide involves updating your sysnand to 10.5. If you don’t have a reliable way of downgrading to 9.2 if you need to, don’t follow this guide. This means you need to be able to use arm9loaderhax to boot CFW, or have a hardmod and a NAND backup, if you want to undo this.

Do not attempt this procedure without a working arm9loaderhax installer. A hardmod is not required but is recommended.


You will need:
  • Homebrew hax already set up and running on your sysnand
  • CFW already installed with a working emunand
  • Decrypt9
  • EmuNAND9
  • MiniPasta
  • AuReiNand mod (do not install this yet)
If you already have arm9loaderhax set up to boot your emunand, you will need to remove it. This is because one of the needed tools, decrypt9, can only run from sysnand. Arm9loaderhax will prevent you from entering sysnand at all, so will need to be removed. I did this by restoring a vanilla 9.2 sysnand backup which I took from the console prior to installing arm9loaderhax.


Stage 0: Make a backup of your SysNand, EmuNand and 3DS SD card

Seriously, you’ll be glad you did if something goes wrong. This process involves a lot of messing around with both sysnand and emunand.


Stage 1: Dump EmuNAND partitions
  1. Boot your 3DS to sysnand
  2. Launch hax and run MiniPasta
  3. When back at sysnand, launch hax and run Decrypt9
  4. Go to “EmuNAND Options” and then “Partition Dump”
  5. Dump each of the partitions with the exception of FIRM0 and FIRM1, pressing B after each one to return to the menu and dump the next partition
  6. Press START to quit Decrypt9, and reboot back to sysnand

Stage 2: Downgrade EmuNand to 9.2
  1. From sysnand, launch hax and run MiniPasta
  2. When back at sysnand, launch hax and run EmuNAND9
  3. Choose “EmuNAND Manager Options” and then choose “Clone SysNAND to EmuNAND”
  4. Once this is complete, press START to reboot
  5. From sysnand, launch hax and run TinyFormat to format SysNand and unlink NANDs
  6. Once the system reboots, complete the initial setup without linking NNID
  7. Once you are at the home menu, set your sysnand theme to red
  8. Launch hax and run CFW to get into emunand
  9. Once in emunand, set the theme to blue
  10. Power off the 3DS

At this point, your sysnand and emunand should both be on 9.2, and you should have dumps of your original emunand. The purpose of setting the NAND colours to red and blue is to ensure you can tell which NAND you are in, since they are both at this stage running the same FW version and will look identical.


Stage 3: Update SysNand to AuReiNand CFW 10.5
  1. Take out your 3DS SD card and put it in your computer
  2. Replace the rei folder, arm9loaderhax.bin and ReiNand.dat in the root of your SD card with the ones from AuReiNand.
  3. In the new rei folder on your SD card, place the firmware.bin and firmware90.bin from the FIRMs archive linked from the AuReiNand GitHib page
  4. Create an empty file on the SD card in the /rei folder called updatedsysnand
  5. Put your SD card back in your 3DS and boot it up to sysnand
  6. Launch hax and run arm9loaderhax.3dsx to install the loader
  7. If you get stuck on a message saying “Exploiting arm9…”, you can safely reboot your 3DS
  8. The 3DS will reboot once this process is complete
  9. You should now be in sysnand but running ReiNand. Verify that arm9loaderhax has been installed by powering off your 3DS, removing the SD card and powering on again. Your system should hang on a black screen because the arm9payload is not available. If your 3DS boots to sysnand without the SD card inserted, this means that arm9loaderhax has not been installed properly and you MUST NOT proceed
  10. Once you have verified that arm9loaderhax is working, replace the SD card and power on your 3DS to boot to sysnand
  11. Open System Settings set up your Internet connection
  12. Update to 10.5 (seriously, don’t do it unless you’re certain the CFW is running by doing the SD card removal test in step 9. If you update to 10.5 without CFW up and running, you risk not being able to run any unsigned code, meaning you could end up stuck on 10.5 with no CFW)
  13. Once the update is complete and the system has rebooted, enter System Settings to verify that you are now on 10.5


Step 4: Reinject emunand partitions to sysnand

This stage will make your new 10.5 sysnand how your emunand used to be
  1. Power off the 3DS
  2. While holding L, power the 3DS back on. This will boot into the 9.2 emunand
  3. Launch hax, and run Decrypt9
  4. Choose “SysNAND Options” and then “Partition Inject”
  5. Inject each of the partitions in turn, with the exception of FIRM0 and FIRM1, pressing B after each one to return to the menu and inject the next partition
  6. Press START to quit Decrypt9 and reboot back to SysNand.

If everything went according to plan, you should be looking at your sysnand but with all your CIAs showing. In my case, they were all back in presents and out of their folders which was a mild inconvenience. I also lost my custom theme, so that had to be reinstalled.


Final checks
  1. Launch a CIA from sysnand to verify that it works. Successful launching of a CIA will indicate that the sysnand CFW is working
  2. Enter System Settings from sysnand to confirm that you are on 10.5
  3. Power off your 3DS, and power it back on while holding L. You should then be booted to your emunand, which will resemble your sysnand before the swap over
  4. Enter System Settings from emunand to confirm that it is on 9.2
  5. Now, do another sysnand, emunand and SD backup!
 
Last edited by mashers,

AkGBA

Nope
Member
Joined
Feb 14, 2007
Messages
345
Trophies
1
XP
1,437
Country
France
I can confirm swapping them works, but I followed a slightly simpler set of steps.

Start: AiReiNAND latest is running thorough A9LH, 9.2 SysNAND and 10.X EmuNAND. Backups exist of both for safety but are not directly used should it work.
  • Use SysUpdater on EmuNAND to downgrade it to 9.2
  • Run SysNand with 9.0 FIRM (hold L on boot, needs latest AuRei)
  • Open Decrypt9, backup all partitions of both NANDs that aren't FIRM
  • Inject SysNand partitions into EmuNAND
  • (Optional) Reboot now to make sure it worked, since all you changed so far is EmuNAND
  • Inject EmuNAND partitions into SysNand
  • Eject SD or shut down and add updatedsysnand flag to rei folder on SD
  • (Re)Boot, update SysNand, and you're done
Of course, there's only one safety check in these steps, but so long as you're sure of what you're doing it's pretty easy.

What if I already have a 9.2 sysnand backup from before a9lh installation ?


0. sysnand 9.2 full backup, then a9lh install
1. backup emunand 10.6 without firm0/firm1, with decrypt9, on sysnand 9.2 with 9.0 FIRM loaded
2. inject it on sysnand
3. inject previous 9.2 sysnand backup in emunand, using emunandtool on computer

Could it work ? I'm no expert, so please tell me where this could go wrong.

@dkabot : could you explain me why you did start by downgrading your 10.x emunand ?
 

dkabot

Better With Others' Systems Than Their Own
Member
Joined
Sep 9, 2014
Messages
1,042
Trophies
0
XP
626
Country
United States
What if I already have a 9.2 sysnand backup from before a9lh installation ?


0. sysnand 9.2 full backup, then a9lh install
1. backup emunand 10.6 without firm0/firm1, with decrypt9, on sysnand 9.2 with 9.0 FIRM loaded
2. inject it on sysnand
3. inject previous 9.2 sysnand backup in emunand, using emunandtool on computer

Could it work ? I'm no expert, so please tell me where this could go wrong.

@dkabot : could you explain me why you did start by downgrading your 10.x emunand ?
Starting by downgrading EmuNAND because safety, prolly not needed but doing it anyway.
Personally, I'd rather not reinstall A9LH if I don't need to, as that brings in another chance for it to fail (however slim that is) and it bothers me.
Other than that, your strategy is valid.
 

AkGBA

Nope
Member
Joined
Feb 14, 2007
Messages
345
Trophies
1
XP
1,437
Country
France
Starting by downgrading EmuNAND because safety, prolly not needed but doing it anyway.
Personally, I'd rather not reinstall A9LH if I don't need to, as that brings in another chance for it to fail (however slim that is) and it bothers me.
Other than that, your strategy is valid.

Yeah, I see. Thanx for your answer. Only wrote step 0 because I still haven't compiled/installed a9lh.
 

dkabot

Better With Others' Systems Than Their Own
Member
Joined
Sep 9, 2014
Messages
1,042
Trophies
0
XP
626
Country
United States
Yeah, I see. Thanx for your answer. Only wrote step 0 because I still haven't compiled/installed a9lh.
Ah, I see. In that case, nothing wrong there.
Worst case, should downgrading EmuNAND be required somehow (really doubt it) you'd still have A9LH and could recover.
 

HighMans

Well-Known Member
Member
Joined
Aug 9, 2012
Messages
140
Trophies
0
XP
228
Country
United States
I can confirm swapping them works, but I followed a slightly simpler set of steps.

Start: AiReiNAND latest is running thorough A9LH, 9.2 SysNAND and 10.X EmuNAND. Backups exist of both for safety but are not directly used should it work.
  • Use SysUpdater on EmuNAND to downgrade it to 9.2
  • Run SysNand with 9.0 FIRM (hold L on boot, needs latest AuRei)
  • Open Decrypt9, backup all partitions of both NANDs that aren't FIRM
  • Inject SysNand partitions into EmuNAND
  • (Optional) Reboot now to make sure it worked, since all you changed so far is EmuNAND
  • Inject EmuNAND partitions into SysNand
  • Eject SD or shut down and add updatedsysnand flag to rei folder on SD
  • (Re)Boot, update SysNand, and you're done
Of course, there's only one safety check in these steps, but so long as you're sure of what you're doing it's pretty easy.


I can't seem to launch decrypt 9 from sysnand using CN. When I launch it, it flashes and goes back to Homebrew.
 

dkabot

Better With Others' Systems Than Their Own
Member
Joined
Sep 9, 2014
Messages
1,042
Trophies
0
XP
626
Country
United States
I can't seem to launch decrypt 9 from sysnand using CN. When I launch it, it flashes and goes back to Homebrew.
Make sure the SysNAND is 9.2, and that you're running it with the 9.0 FIRM.
In the case of AuReiNAND A9LH, make sure it's not set to updatedsysnand and hold L to accomplish this.
 

HighMans

Well-Known Member
Member
Joined
Aug 9, 2012
Messages
140
Trophies
0
XP
228
Country
United States
Make sure the SysNAND is 9.2, and that you're running it with the 9.0 FIRM.
In the case of AuReiNAND A9LH, make sure it's not set to updatedsysnand and hold L to accomplish this.

Crap. It's on 9.0 and the only way I can get in to Sysnand is using R instead of L.
I can upgrade to 9.2 using SafeSysUpdater if I injected FBI in to my sysnand though, right?
 

dkabot

Better With Others' Systems Than Their Own
Member
Joined
Sep 9, 2014
Messages
1,042
Trophies
0
XP
626
Country
United States
Crap. It's on 9.0 and the only way I can get in to Sysnand is using R instead of L.
I can upgrade to 9.2 using SafeSysUpdater if I injected FBI in to my sysnand though, right?
R and L both boot the opposite NAND in AuRei.
Check that you have firmware90.bin in your "rei" folder, and try again
 

HighMans

Well-Known Member
Member
Joined
Aug 9, 2012
Messages
140
Trophies
0
XP
228
Country
United States
R and L both boot the opposite NAND in AuRei.
Check that you have firmware90.bin in your "rei" folder, and try again

I moved firmware90.bin from root to my rei folder, with the included N3DS firmware.bin file from firms.7z and I get "An error has occurred. Hold down the power ..." when holding down L.
 

dkabot

Better With Others' Systems Than Their Own
Member
Joined
Sep 9, 2014
Messages
1,042
Trophies
0
XP
626
Country
United States
I moved firmware90.bin from root to my rei folder, with the included N3DS firmware.bin file from firms.7z and I get "An error has occurred. Hold down the power ..." when holding down L.
Okay, so that sounds like your firmware90.bin is either incorrect or incompatible, if it went from nothing to "error"
 

HighMans

Well-Known Member
Member
Joined
Aug 9, 2012
Messages
140
Trophies
0
XP
228
Country
United States
Okay, so that sounds like your firmware90.bin is either incorrect or incompatible, if it went from nothing to "error"

Copied it again from the firms.7z archive. Same issue. If I hold down L, it crashes. If I hold down R it goes to sysnand (9.0). If I don't hold anything, it goes to emunand (10.5).

Should I update Sysnand to 9.2?
 

HighMans

Well-Known Member
Member
Joined
Aug 9, 2012
Messages
140
Trophies
0
XP
228
Country
United States
@dkabot Updated to 9.2, and something interesting happened. If I hold down L or R during boot (no flag) and remove and reinsert the micro sd card after it boots for 10-15 seconds, Sysnand is loaded in...
 
Last edited by HighMans,

piratesephiroth

I wish I could read
Member
Joined
Sep 5, 2013
Messages
3,453
Trophies
2
Age
103
XP
3,233
Country
Brazil
@mashers
So I did everything and it's working but if our emuNAND was originally 10.5, there's absolutely no reason for "Stage 3: Update SysNand to AuReiNand CFW 10.5".

I just skipped that and injected my extracted emuNAND partitions into the sysNAND after I got AuReiNand to boot via arm9loaderax.
 

vexhash

Well-Known Member
Member
Joined
Nov 27, 2015
Messages
114
Trophies
0
Age
28
Location
Moscow
XP
106
Country
Serbia, Republic of
Didn't understand a little thing.
Do i actually need emunand at the end if i can just have backup of 9.2 sysnand? I mean, 9.2 emunand is practically useless at this point, is it not?
 

piratesephiroth

I wish I could read
Member
Joined
Sep 5, 2013
Messages
3,453
Trophies
2
Age
103
XP
3,233
Country
Brazil
Didn't understand a little thing.
Do i actually need emunand at the end if i can just have backup of 9.2 sysnand? I mean, 9.2 emunand is practically useless at this point, is it not?
Well I think you need the emunand if you want to run other apps like Decrypt9 or Emunand9.
 

mashers

Stubborn ape
OP
Member
Joined
Jun 10, 2015
Messages
3,837
Trophies
0
Age
40
Location
Kongo Jungle
XP
5,074
Country
@mashers
So I did everything and it's working but if our emuNAND was originally 10.5, there's absolutely no reason for "Stage 3: Update SysNand to AuReiNand CFW 10.5".

I just skipped that and injected my extracted emuNAND partitions into the sysNAND after I got AuReiNand to boot via arm9loaderax.
The reason I included that is because I didn't know whether 10.5 emunand partitions would function correctly on a 9.2 NAND. I thought it safer to update it to 10.x first and then inject the partitions.
 

piratesephiroth

I wish I could read
Member
Joined
Sep 5, 2013
Messages
3,453
Trophies
2
Age
103
XP
3,233
Country
Brazil
The reason I included that is because I didn't know whether 10.5 emunand partitions would function correctly on a 9.2 NAND. I thought it safer to update it to 10.x first and then inject the partitions.
Well, AuReiNand already locks the sysNAND firm partitions so A9LH isn't overwritten, doesn't it?
So in the end you're gonna update only the remaining partitions, and they're gonna become the same as the ones extracted from the emuNAND.

Then I just injected them into the 9.2 sysNAND and everything worked fine.
 
Last edited by piratesephiroth,

mashers

Stubborn ape
OP
Member
Joined
Jun 10, 2015
Messages
3,837
Trophies
0
Age
40
Location
Kongo Jungle
XP
5,074
Country
Well, AuReiNAnd already locks the sysNAND firm partitions so A9LH isn't overwritten, doesn't it?
So in the end you're gonna update only the remaining partitions, and they're gonna become the same as the ones extracted from the emunand.

Then I just injected them into the 9.2 sysNAND and everything worked fine.
Good point. I'll update the guide at some point :)
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Lol rappers still promoting crypto