Hacking Question help updating to 6.2 sx os 2.4

[Phoenixrite]

Hi so i dont wanna mess anything up. My switch is on 5.1.0, Sx Os V1.4. What do i do next?

1) I need a stable version of SX OS. ( Recommendations)
2) Using that Version of SX OS to make Nand Dump or just update to 6.2 then make Nand Dump? Update Via Big N or choirdu watever? i dont care about downgrading!
3) Dont want my saves to get erased, how should i babk it up or wen making emunand it gets saved?
4) there are now 3 types of emunand i want the most undetectible one!
5) Play Games!

Any tutorial video links welcome!

 

[Kubas_inko]

1. The latest beta.
2. You can backup/restore your NAND whenever you want. FW does not matter as you can always boot through RCM. Do you care about being banned? If so, update via choidujournx.
3. When you create EmuNAND, it mirrors your NAND to it, so saves will get transferred as well. If you want you can use something like checkpoint to save your saves.
4. Separate partition. That's the one everybody wanted and loves.
5. Don't know what to say to that...

For the tutorial, just follow their website.

 

[Deleted User]

Backup your Nintendo folder.
Setup your sxos licence as needed.
Use sxos to setup emunand.
Boot into emunand.
Run choidujournx and use it to update to 6.2.
Make sure you have the newest 2.4 boot.dat on your sd card.
Delete the Emutendo folder, copy your Nintendo folder to the sd card.
Rename Nintendo folder to Emutendo.
????
Profit!

 

[Alucardus]

Where can I find firmware 6.2? Google isn't returning anything useful. Edit: found one on consolehax.

Also not sure if this is firmware related, but after I update SX OS firmware to latest 2.04 beta, all the installed NSP cannot launch and has that cloud icon on top right of the game. Every time I try to launch the game, it says I need to redownload it.

When I replace the boot.dol of SX OS to previous version I had, the game launch fine.

This tells me every time you update SX OS, you need to reinstall all your NSP again?

This is why I think I need to update to 6.2 using choidujournx.

Thanks for the assist.

 

[Phoenixrite]

much appreciated thanks!

 

[miasma]

On a similar note, I want to use multiple micro as cards so am tempted to put emunand on internal memory so that I don't have to do it on every memory card. What are the drawbacks of this?, is it dangerous or just a bad idea cos everyone seems to want to save it to micro sd

 

[Deleted User]

On a similar note, I want to use multiple micro as cards so am tempted to put emunand on internal memory so that I don't have to do it on every memory card. What are the drawbacks of this?, is it dangerous or just a bad idea cos everyone seems to want to save it to micro sd

Easily detected and banable by Nintendo. If some malicious homebrew is executed, could fuck up your switch. Emunand on sd is safer, and you barely lose any space due to it also counting as "system" storage aswell.

 

[RitchieRitchie]

Easily detected and banable by Nintendo. If some malicious homebrew is executed, could fuck up your switch. Emunand on sd is safer, and 'you barely lose any space due to it also counting as "system" storage aswell.

Sorry for butting in but when you say 'you barely lose any space due to it also counting as "system" storage aswell.' what do you mean exactly? I assumed that it would take up 15gb on the micro sd card, is this not the case? Appreciate any advice as I'm going to make an emunand soon!

 

[Deleted User]

Sorry for butting in but when you say 'you barely lose any space due to it also counting as "system" storage aswell.' what do you mean exactly? I assumed that it would take up 15gb on the micro sd card, is this not the case? Appreciate any advice as I'm going to make an emunand soon!

Basically, when you make emunand, it makes a full copy of your system nand on your sd card, empty space included. What's cool is that you can install to "system memory" which is all that empty space that was copied, or to the sd card as "external" memory source.. But really, because it's emunand, they're both actually on the sd card. So you really only lose about 5 gigabytes max.

--------------------- MERGED ---------------------------

Basically, when you make emunand, it makes a full copy of your system nand on your sd card, empty space included. What's cool is that you can install to "system memory" which is all that empty space that was copied, or to the sd card as "external" memory source.. But really, because it's emunand, they're both actually on the sd card. So you really only lose about 5 gigabytes max.


Edit: If you were installing to a normal nand, it would be on the nand chip in the switch, or to the sd card. But because we boot emunand, the system memory is on the sd card, as is all install to sd card options. The real, internal memory of the switch system is completely untouched.

 

[RitchieRitchie]

Thanks for taking the time to reply - and apologies but i'm a total noob and don't really understand it (my fault - not yours!) I'm planning to make the emunand on the sd card (not partition as I don't want to format my sd card). So if I choose that option it should just take up 5gb, is that correct? Thanks again!

 

[Deleted User]

Thanks for taking the time to reply - and apologies but i'm a total noob and don't really understand it (my fault - not yours!) I'm planning to make the emunand on the sd card (not partition as I don't want to format my sd card). So if I choose that option it should just take up 5gb, is that correct? Thanks again!

It'll take up the full 32 gigabytes of space because you're backing up the full nand, but you can install to system memory, and it'll all be redirected to the emunand system memory. I'm not really sure how to explain it, just trust me, it works, because I'm doing this myself.

On emunand, I installed lots of games to the emunand system memory, and none show up in the regular system memory.

Just give it a try once you have emunand up and running and you'll see what I mean

--------------------- MERGED ---------------------------

I might try and make a small illustration real quick, because it's hard to explain in text but visually easy to show.

 

[RitchieRitchie]

It'll take up the full 32 gigabytes of space because you're backing up the full nand, but you can install to system memory, and it'll all be redirected to the emunand system memory. I'm not really sure how to explain it, just trust me, it works, because I'm doing this myself.

On emunand, I installed lots of games to the emunand system memory, and none show up in the regular system memory.

Just give it a try once you have emunand up and running and you'll see what I mean

--------------------- MERGED ---------------------------

I might try and make a small illustration real quick, because it's hard to explain in text but visually easy to show.

Ah, d'uh! I get it now! So I need to have 32gb free on my sd card but i'll be able to install games to the 'internal' memory - is that correct?

 

[Deleted User]

Ah, d'uh! I get it now! So I need to have 32gb free on my sd card but i'll be able to install games to the 'internal' memory - is that correct?

Yes! That's exactly correct!

Hopefully this explains what I'm trying to say better.Split it into 2 images just to make each bit of the explanation clear.

Anyone, feel free to reference this if needed

 

[RitchieRitchie]

Yes! That's exactly correct!

Hopefully this explains what I'm trying to say better.Split it into 2 images just to make each bit of the explanation clear.

Anyone, feel free to reference this if needed

Awesome! Totally understand it now! I'm using a 128gb sd card, it's pretty full so will have to delete quite a bit to free up 32gb - how much extra free space do you think I need to make over and above the 32gb for the emunand?

 

[Deleted User]

Awesome! Totally understand it now! I'm using a 128gb sd card, it's pretty full so will have to delete quite a bit to free up 32gb - how much extra free space do you think I need to make over and above the 32gb for the emunand?

Well, just a heads up, there's multiple kinds of emunand now. You chose to create a partitioned emunand, it'll format your card entirely. I'm using the "files" emunand which runs emunand from a bunch of files. without formatting. Whatever you do, do not use the "Internal EmuNand" option because that's easily detectable by Nintendo.

Either way, all the different kinds of emunand work exactly the same as I illustrated above.

You'll need to completely free up 33 gigs of space to create a files emunand. (I say 33 just to give that extra leeway just incase). Otherwise, back up everything from your card and create a partitioned emunand and it'll do its thing.

 

[RitchieRitchie]

Cool, I'm going to use the files emunand system. Thanks for all your help, have a good one!

 

[arcsy]

Hope I'm not hijacking this thread but I'd like to ask some questions related to this concern.

1. What exactly is the point of Emunand? From my understanding is that it allows you to boot to official firmware so you could play online, correct? Has this been proven to be working and no cause for bans even if you already have nsps or homebrews installed prior to making an Emunand?

2. I am on FW6.1 using SXOS v2.2 Beta. I have installed lots of NSPs and acquired lots of errors from the Retroarch homebrew. How do I go on updating and can I still use Emunand while being protected on Nintendo onwards or should I make a complete format and restoring my official 6.1 nand backup before updating to 6.2 and SXOS v2.4.1 Beta?

Thank you so much!