Hacking SXOS "Emunand" setup time

[Ashura66]

The measurement is correct, however there aren't 32GB free like here with this fake emuNand there aren't 16GB free; some space is always reserved by OS.
BTW yes, if you read the same tweets I read, this is a screenshot taken from the emuNand, not the sysNand.

No wonder people were saying that the fake emuNAND shrunk the original SysNAND. big case of misinterpretation it seems

 

[Matt7402]

I canceled and mine is working just fine. Mine ran for 2 hours before i canceled it. It told then it was "complete" I the went back in and deleted the emunand and everything was just fine. Everyone just need to quit freaking out.

I also didn't lose any space. did a 10 GB emunand w/ 12.8 GB free before and have 12.8 gb free after canceling and then deleting the emunand.

 

[Ashura66]

I canceled and mine is working just fine. Mine ran for 2 hours before i canceled it. It told then it was "complete" I the went back in and deleted the emunand and everything was just fine. Everyone just need to quit freaking out.

I also didn't lose any space. did a 10 GB emunand w/ 12.8 GB free before and have 12.8 gb free after canceling and then deleting the emunand.

Yes yes that little misunderstanding has been resolved already

 

[WiiUAre]

it took me more 3 hours+ . but it works fine. still don't understand the space. I had 19gb free now I have around 5gb . so It seems to me its just the same size in total to bad it cant use space from the sd I probably go back to normal nand since I don't see the benefit of the emunand at this time

 

[Ashura66]

it took me more 3 hours+ . but it works fine. still don't understand the space. I had 19gb free now I have around 5gb . so It seems to me its just the same size in total to bad it cant use space from the sd I probably go back to normal nand since I don't see the benefit of the emunand at this time

When the emunand is active, what you see in the sys settings is the size of the "emunand", not the size of your sysnand.So yeah, it's going to be smaller, usually by half

 

[pka4916]

so do you still need the Dongle and Jig for it to boot up? or is it all without.. otherwise I don't see the point of it.

 

[iMythD]

I'm having the same issue. First time around took an hour and then said it failed. That was at 10Gb. I'm now trying 15Gb NAND size, but it's taken over an hour, still going.. no end in sight. What's going on?

 

[jslay]

1. Delete all software from main menu/launcher (this does not delete saves, make a list of what you are deleting if you need to)
2. Reboot into CFW/OFW, as this will clear some caches
3. Check Data Management to see how much free space you have on System Memory
   1. You want to leave some room for the OFW to grow and shrink as needed, I had 24GB free at this stage, and decided to create a 15GB EmuNAND. This leaves 9GB left for the OFW
   2. If you don't have enough free space to create a 15GB EmuNAND, there is a good chance you will need to NOT copy over the USER partition when creating the EmuNAND
4. Reboot with RCM and hold Vol + when the payload is injected to get to the SX OS Bootloader menu.
5. Select Options -> NAND -> Dump NAND -> Continue. This creates a backup of your NAND in case anything goes wrong. This will take about 1.5 hours or so, depending on the speed of your SD card. You will also need at least 32GB available on your SD card. You should really not be messing with any NAND writes without a proper NAND dump!
6. When NAND dump is complete select EmuNAND -> Create EmuNAND.
7. Go into Advanced and select your EmuNAND size.
8. If you are being forced to select a smaller EmuNAND size than 15GB because of current free space restrictions, change "Copy USER partition to EmuNAND" to NO
   1. If you want to get specific NAND user saves and the like over to the EmuNAND, you can boot into the SX OS Bootloader, disable EmuNAND, boot CFW, and back them up to SD card. Then Restore them on EmuNAND with a reboot into CFW again
9. Click Done, and then Continue. Wait roughly 40 minutes, not sure where the 20m estimate comes from on their part.
10. Once this finishes, select Poweroff at the top left.
11. Boot into RCM and inject SX as usual, this time, no need to hold Vol +. It will automatically select the EmuNAND if present by default.
12. Enjoy the best of both worlds.

 

[Ericthegreat]

The way TX installs EmuNAND is by directly changing the NAND inside your console. Interrupting such a delicate and fragile process shouldn't lead to anything less than a brick.

I've already seen one report, people were trying to help him in switch hacks.

 

[Antoniofurtadodias]

Do you recommend using emunand? what are the advantages?

 

[The Real Jdbye]

Do you recommend using emunand? what are the advantages?

Not really the right thread for this, but if you want to use online for legit stuff, you have no choice but to use emuNAND. It's the only way to keep your CFW stuff hidden from Nintendo while also being able to play online legit. If you don't care about that, then I suppose it doesn't matter, but it's still a good idea to make a NAND backup before you use any CFW or homebrew, so if you decide in the future you want to play online you have a clean NAND backup to go back to.

 

[Ashura66]

Not really the right thread for this, but if you want to use online for legit stuff, you have no choice but to use emuNAND. It's the only way to keep your CFW stuff hidden from Nintendo while also being able to play online legit. If you don't care about that, then I suppose it doesn't matter, but it's still a good idea to make a NAND backup before you use any CFW or homebrew, so if you decide in the future you want to play online you have a clean NAND backup to go back to.

Pretty sure emunand isn't going to protect you and allow you to go online legit but this has yet to be proven

 

[The Real Jdbye]

Pretty sure emunand isn't going to protect you and allow you to go online legit but this has yet to be proven

There are ways Nintendo could detect emuNAND (but at the moment, they aren't), but they at least won't be able to detect all your CFW activities. Right now it's safe, with the next update that might not be the case anymore.

 

[Ashura66]

There are ways Nintendo could detect emuNAND (but at the moment, they aren't), but they at least won't be able to detect all your CFW activities. Right now it's safe, with the next update that might not be the case anymore.

I only say this because it's proven that Ninty gathers data on your nand size and it's also been proven that emunand is significantly smaller than your sysnand and basically exists WITHIN the sysnand so it's not all THAT farfetched to think that they might see it

 

[jslay]

Pretty sure emunand isn't going to protect you and allow you to go online legit but this has yet to be proven

I have been going online with my OFW and my legitimately purchased titles, while keeping all the other stuff in EmuNAND, have not received a ban.



Also, there is nothing that keeps Nintendo from detecting an EmuNAND on sysNAND vs a microSD card. So where the EmuNAND is makes no real difference beyond the fact that you have to basically 'shrink' the OFW sysNAND for SX EmuNAND setup. I guess the only 'difference' it would make, is that they would be aware you have intentionally modified the sysNAND of THAT particular console, vs if it were on SD card, they couldn't really say for sure that specific console is a modified console.