Hacking Easiest way to make NAND dump?

blackwhitexy

Well-Known Member
Newcomer
Joined
Apr 20, 2014
Messages
93
Reaction score
63
Trophies
0
Age
38
XP
568
Country
Croatia
With all the talk of brick code potentially being hidden in releases, I want to make a NAND backup.

I use SX OS. Is there an easy tool to do this or is it a really complicated process?
 
With all the talk of brick code potentially being hidden in releases, I want to make a NAND backup.

I use SX OS. Is there an easy tool to do this or is it a really complicated process?
SX OS has it's own NAND Dumper. Boot the loader by holding VolUp while pressing power, go to Options and there you'll find it, do a Raw Nand dump.
 
SX OS has it's own NAND Dumper. Boot the loader by holding VolUp while pressing power, go to Options and there you'll find it, do a Raw Nand dump.

yesss. this is the answer i was hoping for. thank you.

do you perhaps know if i need to do a NAND dump every time i update my console?
 
yesss. this is the answer i was hoping for. thank you.

do you perhaps know if i need to do a NAND dump every time i update my console?
No, you don't. If you, say, are on a hypothetical 7.0.0 that burns more fuses than 6.1.0, and you were to restore the 6.1.0 dump to said 7.0.0 console, you would only be able to boot via Hekate, ignoring fuse checks. But then you could update to 7.0.0 again from there and go on.
I'd say just to a backup every now and then, it is no effort besides waiting for a bit, rest is done itself. I personally do backups after system updates, or like once in a month, whichever comes first.
 
Cant' really understand why pretty much everyone is recommending hekate when SX Pro does have its own NAND backup/restore function. Are there confirmed problems I'm not aware of or is it just the usual "Team Xecuter sucks" stuff?
 
Cant' really understand why pretty much everyone is recommending hekate when SX Pro does have its own NAND backup/restore function. Are there confirmed problems I'm not aware of or is it just the usual "Team Xecuter sucks" stuff?
Because hekate is the original and checks the backup to make sure it is not corrupted.
 
Console specific keys, but you can also dump them after your switch is bricked. Doesn't hurt to have them
Are they what you dump with kezplez-nx? If not, which option is it in hekate?
I'm asking because I made NAND backup yesterdey, BOOT0/1 and rawnand.bin, and I'd rather have everything, just in case.
 
Are they what you dump with kezplez-nx? If not, which option is it in hekate?
I'm asking because I made NAND backup yesterdey, BOOT0/1 and rawnand.bin, and I'd rather have everything, just in case.
With TegraRcmSmash and biskeydump from https://switchtools.sshnuke.net/ open a windows cmd (windows+x -> cmd, or in explorer with nothing selected shift+right click -> open powershell here), send the biskeydump payload to your Switch:
Code:
P:\ath\to\TegraRcmSmash.exe P:\ath\to\biskeydump.bin -r
And copy the output somewhere safe. (you may need to input ctrl+M to be able to copy)
 
Last edited by BDS,
Cant' really understand why pretty much everyone is recommending hekate when SX Pro does have its own NAND backup/restore function. Are there confirmed problems I'm not aware of or is it just the usual "Team Xecuter sucks" stuff?
Verification so you know your dump is ok. Also I watched ctcaer's dumper develop and get perfected, so I trust it.
 

Site & Scene News

Popular threads in this forum