Of course, the toolkit doesn't restore the NAND so the dumps have to be restored by something else.Nand backups made from Toolkit can be used in Hekate to restore the switch?
Of course, the toolkit doesn't restore the NAND so the dumps have to be restored by something else.Nand backups made from Toolkit can be used in Hekate to restore the switch?
Of course, the toolkit doesn't restore the NAND so the dumps have to be restored by something else.
Sorry Im asking more about the compability of this ttool. CTCaer say to me on one of his post "But if you do it (restore from a ReiNX Toolkit nand backup), you'll risk of corrupting your eMMC".
I want to know if anyone has succeded doing that operation?
Sorry Im asking more about the compability of this ttool. CTCaer say to me on one of his post "But if you do it (restore from a ReiNX Toolkit nand backup), you'll risk of corrupting your eMMC".
I want to know if anyone has succeded doing that operation?
I think the toolkit does have a way to verify the NAND dump but not sure right now. The real reason CTCaer believe it will corrupt the eMMC is because restoring the NAND involves writing to the eMMC and he considers anything that writes to it dangerous, regardless if the dump is verified or not. Its also the reason why AutoRCM is labeled as dangerous; not because of its history but because it writes directly to part of the eMMC.What he probably meant by that, is that the Toolkit doesn't verify the nand dump it makes. For more peace of mind, you should at least make one verified dump with Hetake.