My memory card is full. How can i make a nand backup on a second memory card? Which files does the new card need? Or can i just run decrypt9 take memory card out put new card in and do backup? Any help is appreciated
My memory card is full. How can i make a nand backup on a second memory card? Which files does the new card need? Or can i just run decrypt9 take memory card out put new card in and do backup? Any help is appreciated
My memory card is full. How can i make a nand backup on a second memory card? Which files does the new card need? Or can i just run decrypt9 take memory card out put new card in and do backup? Any help is appreciated
The new sd card can be empty?Go into Hourglass9/Decrypt9, switch sd card when pressing select, put new one in and proceed to backup babd.
Ok thanksJust place a files9 directory and place the Decrypt9.bin on the root of the sd card and name it "arm9loaderhax.bin". The second you turn on your 3ds, Decrypt9 will load automatically
yeah, you can use whatever method users told..The new sd card can be empty?
--------------------- MERGED ---------------------------
Ok thanks
I think you have no actual clue how arm9loaderhax works I guess? the payloads are written to the FIRM partition of your NAND, what allows us to let the arm9loader run any valid arm9 payload. in our case its the arm9loaderhax.bin on the root of your sd card. so he just renames the arm9 payload of Decrypt9 arm9loaderhax.bin and thats it. he doesn't need the luma payload since he does not want to boot into the FW. he can freely boot any arm9 payload like he wants to. can be Luma3DS, Decrypt9, ReiNand or whatever. just needs to be a valid arm9 payload.i am not sure if you need to also put the luma files in the sd card
either one is the same thing...
i forgot about that part that you can rename the decrypt\hourglass\whatever payload as arm9loaderhax.binI think you have no actual clue how arm9loaderhax works I guess? the payloads are written to the FIRM partition of your NAND, what allows us to let the arm9loader run any valid arm9 payload. in our case its the arm9loaderhax.bin on the root of your sd card. so he just renames the arm9 payload of Decrypt9 arm9loaderhax.bin and thats it. he doesn't need the luma payload since he does not want to boot into the FW. he can freely boot any arm9 payload like he wants to. can be Luma3DS, Decrypt9, ReiNand or whatever. just needs to be a valid arm9 payload.
full nand has ~300MB of blank space.What's the difference between nandmin and just regular nand?
full nand has ~300MB of blank space.
Nandmin doesn't backup this empty space
I believe it was just the initial option; i.e. dump all of nand - so code wise it's simpler I guess. Also the full is a 1:1 of the nand - which some might feel is 'better' to have.ok great. any reason why anybody would want to backup the empty space? why is it even an option?
thanks for taking your time to explain it.I believe ot was just the initial option; i.e. dump all of nand - so code wise it's simpler I guess. But the full is a 1:1 of the nand - which some might feel is 'better' to have.
Functionally they're the same and I think even for hardmods they act the same.
Similarly a ctrnand backup is a back of one of the nand partitions; still a viable backup for a9lh systems - just not fpr hardmods