NAND Backup question related to system transfer

[Deleted member 598242]

I have two systems and I performed a system transfer between them. Before that, I made a NAND backup for each console which means I now have two backups.
Just wondering... I'm not sure about this, but the correct NAND for my current system would be the one that came from the console when the backup was created, even before the transfer. Is this correct or not and is there anything else to be aware of?

 

[KleinesSinchen]

The only thing that gets moved between systems is movable.sed
Each console has unique encryption keys for the NAND in OTP. Never try to restore an image from console A on console B regardless of a transfer. GodMode9 will refuse to do it (good!) and if you manually inject it, you'll get greeted with 8046 BOOTROM Error after a reboot.

Backup each console once again now. Restoring to a state before the transfer is potentially problematic and could be noticed when using the systems online. Keeping additional images is always a good idea.

Good luck and have fun!

 

[Deleted member 598242]

The only thing that gets moved between systems is movable.sed
Each console has unique encryption keys for the NAND in OTP. Never try to restore an image from console A on console B regardless of a transfer. GodMode9 will refuse to do it (good!) and if you manually inject it, you'll get greeted with 8046 BOOTROM Error after a reboot.

Backup each console once again now. Restoring to a state before the transfer is potentially problematic and could be noticed when using the systems online. Keeping additional images is always a good idea.

Good luck and have fun!

Very good to know, thank you!
I backed up the NAND again and I noticed that some (.exefs and .bin) files are missing that were there when I first backed it up for the first time. Now, there are only 3 files. What exactly does this mean?

 

[KleinesSinchen]

Very good to know, thank you!
I backed up the NAND again and I noticed that some (.exefs and .bin) files are missing that were there when I first backed it up for the first time. Now, there are only 3 files. What exactly does this mean?

Two files:
[date]_[Serial number]_sysnand_00.bin → The NAND image (about 1GB)
[date]_[Serial number]_sysnand_00.bin.sha → sha256 checksum of the image (just a checksum)

essentials.exefs is embedded into the NAND image as well, but if you need it separately, copy it within GodMode9 from [S:] SYSNAND VIRTUAL
If you are using latest Luma3DS, it will copy important files (bootroms, OTP,…) to SD:/luma/backups as well.

3DS homebrew and CFW is very safe and well-tested and well thought out.

 

[Deleted member 598242]

Two files:
[date]_[Serial number]_sysnand_00.bin → The NAND image (about 1GB)
[date]_[Serial number]_sysnand_00.bin.sha → sha256 checksum of the image (just a checksum)

essentials.exefs is embedded into the NAND image as well, but if you need it separately, copy it within GodMode9 from [S:] SYSNAND VIRTUAL
If you are using latest Luma3DS, it will copy important files (bootroms, OTP,…) to SD:/luma/backups as well.

3DS homebrew and CFW is very safe and well-tested and well thought out.

Alright, thanks.
I also got a .3ds file, it ends with v01.trim.3ds, what is this about?