Hacking Question SX OS EmuNand creation options

SpaceJump

Well-Known Member
OP
Member
Joined
Aug 18, 2005
Messages
3,866
Trophies
1
Location
Zebes
XP
3,280
Country
Germany
Can someone explain the different options in the EmuNand creation process?

These are the options:
  • Copy USER partition to EmuNand: What is this? Is it recommended that this is enabled?
  • EmuNand sizes: From 5GB up to 25GB: How come different sizes are available? What size is recommended? Any disadvatages to the 5GB size?
Haven't found any clear explanations for these options, even on the SX OS website.
 

lisko

Well-Known Member
Member
Joined
Oct 28, 2018
Messages
125
Trophies
0
Age
33
XP
637
Country
Italy
A disadvantage is the """EmuNAND""" it-self really. Just takes space IMHO.
Otherwise, there is "none". Max that it can brick your console if something happens during "installation"
Not true as stated billions of times, it doesn't touch the partitions only creates new files in USER partition (plus writes to unused space in boot). If the process is interrupted sx os will not boot due to damaged emunand files but all you need to do to restore your switch is to uninstall the broken emunand from sx os boot menu and restart the installation process if you want. Also emunand is useful even for non developers/enthusiasts as is a complete brick protection to your switch. Remember that also installing nsp to sdcard writes your ticketblob in nand and could brick your switch if it gets corrupted (remember early devmenu nsp which bricked switches), with emunand is all a lot safer.
 
  • Like
Reactions: thaikhoa

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Psionic Roshambo @ Psionic Roshambo: What are the odds lol