This is a New 3DS running firmware 11.0.0-33U, originally hacked using arm9LoaderHax and Luma 6.6, and about two weeks ago the hack was upgraded to boot9strap and Luma 7.1.
Everything is running great but I have a doubt about the new NAND backup files.
Following 3DS.guide during the hacking process using A9LH, a NAND backup was created, and two files were to be safely stored: serial-numer.bin and opt.bin. This original backup was already used for a successful NAND restoration (to remedy some system crashes) long before moving to B9S.
According to the new version of the 3DS.guide, now the NAND backup during the hacking process using B9S creates two files: nand.bin and the hash nand.bin.sha. Do I need to generate a corresponding nand.bin.sha hash of my original backup? Is this hash necessary for eventual NAND restorations in the future?
Everything is running great but I have a doubt about the new NAND backup files.
Following 3DS.guide during the hacking process using A9LH, a NAND backup was created, and two files were to be safely stored: serial-numer.bin and opt.bin. This original backup was already used for a successful NAND restoration (to remedy some system crashes) long before moving to B9S.
According to the new version of the 3DS.guide, now the NAND backup during the hacking process using B9S creates two files: nand.bin and the hash nand.bin.sha. Do I need to generate a corresponding nand.bin.sha hash of my original backup? Is this hash necessary for eventual NAND restorations in the future?