Hacking How often do you backup you nand?

mrdude

Developer
Developer
Joined
Dec 11, 2015
Messages
3,071
Trophies
1
Age
56
XP
8,227
Every update when a fuse gets blown - you should make a back so you can restore.

Basically every time you add a game/install an nsp - data gets written to the nand and changes bytes 00 to something else. You can look at a clean nand dump in a hex editor and see what bytes are changed. Then compare it to an updated nand image where you installed some stuff.

In a dumped sx os nand - you can make a clean nand using a hex editor - then test your clean nand by putting it in the emunand folder and testing it works.

I do it like this:
Dump an updated nand (6.1.0 for now).

Don't touch boot1/boot2

Edit:
full.00.bin - jump to address 53362000 - edit everything under this address - make bytes 00
full.01.bin - full.06.bin - change all bytes to 00
full.07.bin - from - address 00 to 47cdfdff - change all bytes to 00 (don't touch anything under 47cdfdff).

Now copy all modded files to sxos - emunand folder and boot into emunand.
Open ChoiDujourNX and update emunand to 6.1.0 (ex-fat) - and in the options uncheck prevent fuse burning (auto rcm), check System initialize (full factory reset). Then start installation.

Now shutdown the switch and remove the sd card - make a backup of emunand folder - this is now your clean nand you can restore from.

Now test the modded nand files in by booting into emunand - it the switch boots properly and functions properly - this would work as a new clean nand backup.
 
  • Like
Reactions: Vic_Vinegar

Vic_Vinegar

Well-Known Member
OP
Member
Joined
Jun 21, 2018
Messages
112
Trophies
0
Age
38
XP
229
Country
Canada
Every update when a fuse gets blown - you should make a back so you can restore.

Basically every time you add a game/install an nsp - data gets written to the nand and changes bytes 00 to something else. You can look at a clean nand dump in a hex editor and see what bytes are changed. Then compare it to an updated nand image where you installed some stuff.

In a dumped sx os nand - you can make a clean nand using a hex editor - then test your clean nand by putting it in the emunand folder and testing it works.

I do it like this:
Dump an updated nand (6.1.0 for now).

Don't touch boot1/boot2

Edit:
full.00.bin - jump to address 53362000 - edit everything under this address - make bytes 00
full.01.bin - full.06.bin - change all bytes to 00
full.07.bin - from - address 00 to 47cdfdff - change all bytes to 00 (don't touch anything under 47cdfdff).

Now copy all modded files to sxos - emunand folder and boot into emunand.
Open ChoiDujourNX and update emunand to 6.1.0 (ex-fat) - and in the options uncheck prevent fuse burning (auto rcm), check System initialize (full factory reset). Then start installation.

Now shutdown the switch and remove the sd card - make a backup of emunand folder - this is now your clean nand you can restore from.

Now test the modded nand files in by booting into emunand - it the switch boots properly and functions properly - this would work as a new clean nand backup.
Thank you for this!
 

Mythical

Well-Known Member
Member
Joined
May 11, 2017
Messages
2,153
Trophies
1
Age
25
XP
3,003
Country
United States
Data loss can be incredibly frustrating.

Having a server at home where I dump complete backups of all me consoles on really helps. (think Xbox's HDD, 360 HDD/MU/NAND, PS2 HDD + image of the Memory units, PS3 HDD + NOR dump, 3DS NAND + SD backup etc)
Even if I haven't used a console in a year, doing a yearly backup of everything all at once is another great way to fight data loss.

If you ever plan on doing such a thing on a external harddrive or w/e, make sure you compare the dumps.
If everything matches then you can delete the old obsolete backup.
Never just dump and store, always dump, compare and then store.

I honestly don't think doing periodic backups is overkill, it's something everybody should do if they cared about their data.
I have two extra 4tb drives that have all of my consoles install able files and hdds. It's a boon to have especially if you're inexperienced
 
  • Like
Reactions: DinohScene

jaysea

Well-Known Member
Member
Joined
Aug 17, 2009
Messages
279
Trophies
1
Age
46
XP
1,189
Country
Netherlands
Every time you go online you should make a backup afterwards or expect to be banned if you do not put that latest backup back before going online again.
 

EmulateLife

Well-Known Member
Member
Joined
May 30, 2016
Messages
3,979
Trophies
0
Age
42
XP
1,889
Country
United States
Be aware of another thing: Your Nand has your saves. So if you restore a Nand from along time ago all of your saves made since that time are gone. Of course, you could just backup your saves seperately.
 

Vic_Vinegar

Well-Known Member
OP
Member
Joined
Jun 21, 2018
Messages
112
Trophies
0
Age
38
XP
229
Country
Canada
All good information, thanks guys.

For backing up my nand, should I stick with hekate ctcaer or use sx os? Or does it not matter?
 

Ian095

Well-Known Member
Member
Joined
Jun 25, 2018
Messages
381
Trophies
0
XP
839
Country
United Kingdom
I done it the first time Homebrew came out when I was on 4.1.0, I burned a fuse updating to 5.1.0 but still keep that backup as it may potentionally be useful one day (though unlikely) as from what I've heard if you're using RCM and skipping fuse checks it's still works (unless I've been misinformed) it just doesn't work on stock.

So on 5.1.0 I done the exact same again, incase I ever needed to wipe everything dodgy done on the console and go 99.999% clean.

I managed to dodge the fake NSPs making the round over the months but before Smash comes out... I'm making another backup as there is sure to be plenty of fake ones making the rounds. I've gotten lucky far too much so far, you should make a backup before/after updating without burning fuses and also if you have a lot of changes, do it before installing a newly released well desired game NSP as well, you don't want to lose everything and worst case scenario, end up with a brick.
 

annson24

The Patient One
Member
Joined
May 5, 2016
Messages
1,191
Trophies
0
Age
32
XP
1,843
Country
Philippines
Twice, one after unboxing, and one after (fuseless) updating to v5.1.0. I will make another backup before trying some of the dangerous stuff (i.e downgrading)

Sent from my SM-G950F using Tapatalk
 

roden

Well-Known Member
Member
Joined
Oct 14, 2007
Messages
169
Trophies
0
XP
534
Country
I am actually just about to do my first, as i have not been bothered yet and figured it would be a good time to do so.
Im on 6.01, do i just need RAW NAND Dump and Boot 1 and 2?
 

subcon959

@!#?@!
Member
Joined
Dec 24, 2008
Messages
5,845
Trophies
4
XP
10,109
Country
United Kingdom
Backup frequency should be based on a simple question: How much fuckery are you happy doing to get back to a usable state if you lost everything today?
 

marveldragon

Active Member
Newcomer
Joined
Sep 23, 2018
Messages
42
Trophies
0
Age
33
XP
304
Country
United States
You should only need to have two back ups.

One of a clean out of the box nand. This one you keep however long you have your console.

Second is a copy of the nand you have your current official firmware on. This one you will throw away after you update you console and create a new nand backup if you choose to update your firmware.

Aside from that you do not need to make daily or weekly unless you are severely tinkering with you switch.
But you might want to use checkpoint to backup you save data daily?
 

RedHunter

Well-Known Member
Member
Joined
Dec 12, 2014
Messages
441
Trophies
0
XP
1,573
Country
Italy
I was wondering, I still have my old 2.3 backup but since I have updated to 6.1 and so burned the fuses it's useless right? I should only have the latest backup everytime I update the console?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: Like for micro