Homebrew When One Updates Luma, Should the New Version Be Copied to SYSNAND?

[starburst]

I am running Luma 6.6 (the latest stable release) and arm9LoaderHax on a New 3DS XL at version 11.0.0-33U.

When one updates Luma (say to a new stable release or to a nightly build), should this new version not be also copied to SYSNAND?

As I understood by following 3ds.guide, installing Luma meant copying it to SYSNAND (to make it permanent) and loading an identical copy of it from SD card. Is this correct, or am I confusing arm9LoaderHax with Luma?

Also related to this, when updating arm9LoaderHax, the guide states that one should copy the arm9loaderhax.bin file to SYSNAND. However, is that file not Luma itself? Why should one copy it to SYSNAND when it has not been changed (no new arm9loaderhax.bin file is created during the arm9LoaderHax updating process.)

 

[BL4Z3D247]

I am running Luma 6.6 (the latest stable release) and arm9LoaderHax on a New 3DS XL at version 11.0.0-33U.

When one updates Luma (say to a new stable release or to a nightly build), should this new version not be also copied to SYSNAND?

As I understood by following 3ds.guide, installing Luma meant copying it to SYSNAND (to make it permanent) and loading an identical copy of it from SD card. Is this correct, or am I confusing arm9LoaderHax with Luma?

Also related to this, when updating arm9LoaderHax, the guide states that one should copy the arm9loaderhax.bin file to SYSNAND. However, is that file not Luma itself? Why should one copy it to SYSNAND when it has not been changed (no new arm9loaderhax.bin file is created during the arm9LoaderHax updating process.)

The dev build doesn't change so unless you update Luma to the hourly build to fix things that updating to 11.x breaks you probably don't need to. However, if you update to the hourly build you should copy the new payload to the CRTNAND because if you boot without the SD card some things might now work because you have the normal dev build copied to your NAND. If you're on 11.0 and plan on staying there you don't need to change the payload on you NAND as everything should work with the normal dev build of Luma 6.6.

 

[Cuphat]

If you want that version to also be on CTRNAND for SDless use, then yes. Unless the older version that you have on CTRNAND doesn't work at all with your current firmware, though, it's not exactly super high priority.

Also related to this, when updating arm9LoaderHax, the guide states that one should copy the arm9loaderhax.bin file to SYSNAND. However, is that file not Luma itself? Why should one copy it to SYSNAND when it has not been changed (no new arm9loaderhax.bin file is created during the arm9LoaderHax updating process.)

That guide assumes you are upgrading from an older version of A9LH that doesn't have the CTRNAND loading, and thus you wouldn't already have arm9loaderhax.bin in CTRNAND.

 

[starburst]

Thank you both on your quick responses.

I am a new 3DS user; the first time I used a 3DS console was two weeks ago, the same device wherein I installed arm9LoaderHax and Luma.
From what I have read, online playing is the one feature that triggers system update prompts. If this is true, and my being only a casual gamer, I will stay on version 11.0.0-33U for as long as possible; for I do not play online.

Luma version 7 has just been released and I will update it and copy it to SYSNAND, to have it synchronised with its SD version.

squall14716, it now makes sense why the arm9LoaderHax updating guide tells us to copy Luma into SYSNAND.