Hacking Question what is the best scenario for brand new unpatched switch with firmware 4.1.0?

[Goldenman66]

i'm confused in regards the best way i should go through, i bought a brand new unpatched switch and it comes with 4.1.0 firmware and SD card 128GB, it's brand new and never connected to internet, first thing i did before even power on the switch i take a NAND backup. now i don't know which is better update SYSNAND to latest firmware and after that use atmosphere for emuMMc? or install a CFW with autoRCM then offline update to 8.1.0? also i don't know is it worthy to have firmware 4.1.0 or NAND backup from it?

Please advise for the best option?
Thanks in advance

 

[Hayato213]

Depends on what you want to do, if you are 100% sure the NAND is clean then create an emunand and use the sysnand for online gaming and emunand for all your homebrew/cfw stuffs. Unless you care about the software base exploit feel free to update.

 

[Goldenman66]

Depends on what you want to do, if you are 100% sure the NAND is clean then create an emunand and use the sysnand for online gaming and emunand for all your homebrew/cfw stuffs. Unless you care about the software base exploit feel free to update.

yes i'm sure NAND is clean but when i tried to create emunand it didn't work i guess due to it's on firmware 4.1.0 which is not support exfat and large SD cards. if there is a tutorial for this please send it

 

[Lacius]

Do you care about playing online? If not, then there's probably no real reason to use an emuNAND.

 

[tabzer]

If you want to use it online, you are going to want to update it to the latest ofw anyway, so preserving fuses for downgrades in the future is a moot point at this stage. You should create a NAND backup after updating. Or create a NAND backup immediately if you plan on retaining fuses and not playing online. You can use hekate/atmosphere to create an emummc partition so that you can have a CFW side for the homebrew side of things and an OFW side for the more "legitimate" side of things.

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

Do you care about playing online? If not, then there's probably no real reason to use an emuNAND.

But... Tetris!

 

[shano]

Make a NAND backup then update to latest firmware via ChoiDujourNX without burning fuses. Make sure to use autorcm and if you wanna go back to 4.1.0 later you can since you didnt burn any fuses updating firmware.

 

[Reecey]

Don’t touch your 4.1.0 ofw at all! I just hope you haven’t already. Get sxos, make a backup first in the options menu, then setup emunand with hidden partition on the sd card, update your emunand to the latest firmware exfat using ChoiDujournx and away you go setup your switch settings as normal just make sure from now on you always boot into emunand which it should by default. That’s your best option without a doubt.

 

[Goldenman66]

Don’t touch your 4.1.0 ofw at all! I just hope you haven’t already. Get sxos, make a backup first in the options menu, then setup emunand with hidden partition on the sd card, update your emunand to the latest firmware exfat using ChoiDujournx and away you go setup your switch settings as normal just make sure from now on you always boot into emunand which it should by default. That’s your best option without a doubt.

I didn’t and i do prefer your scenario but when I tried to emunand using atmosphere it didn’t work, do you think it will work with sxos?

 

[BaamAlex]

I didn’t and i do prefer your scenario but when I tried to emunand using atmosphere it didn’t work, do you think it will work with sxos?

Emunand on ams cfw is experimental atm.

 

[Goldenman66]

Emunand on ams cfw is experimental atm.

Sorry I didn’t got your point?

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

Make a NAND backup then update to latest firmware via ChoiDujourNX without burning fuses. Make sure to use autorcm and if you wanna go back to 4.1.0 later you can since you didnt burn any fuses updating firmware.

Can i use ChoiDujourNX on the ofw? I think it’s usable with cfw only

 

[Lacius]

Don’t touch your 4.1.0 ofw at all! I just hope you haven’t already. Get sxos, make a backup first in the options menu, then setup emunand with hidden partition on the sd card, update your emunand to the latest firmware exfat using ChoiDujournx and away you go setup your switch settings as normal just make sure from now on you always boot into emunand which it should by default. That’s your best option without a doubt.

There is no reason to purchase SX OS when Atmosphere can do just about everything for free.

I didn’t and i do prefer your scenario but when I tried to emunand using atmosphere it didn’t work, do you think it will work with sxos?

Follow this guide if you want to use an emuNAND:
https://nh-server.github.io/switch-guide/user_guide/emummc/partitioning_sd/

Emunand on ams cfw is experimental atm.

It's technically experimental, but it's fully functional.

Can i use ChoiDujourNX on the ofw? I think it’s usable with cfw only

You can use ChoiDujourNX with your sysNAND or your emuNAND. However, it should only be used with a NAND you don't intend to keep clean for online play.

 

[tabzer]

Why does that guide say to leave the first 16MB unallocated?

 

[Reecey]

I didn’t and i do prefer your scenario but when I tried to emunand using atmosphere it didn’t work, do you think it will work with sxos?

Yes I would personally use sxos emunand because it’s been more refined and in development a lot longer, Atmosphere emunand is in its very early stages that’s why I didn’t suggest atmosphere emunand. sxos is your best bet and is very straightforward to set up this is another reason why I suggested it for you.

Get sxos put the general build first on your sd card 2.5.3 boot up settings on power, back up your nand save that, then setup emunand hidden partition. When you have done those go back to the sxos menu make sure it says emunand, update your sxos to 2.8 beta build, grab your 8.1.0 firmware files put them on your sd card start up ChoiDujournx and run firmware 8.1.0 exfat in emunand reboot, job done! Then go ahead and setup your switch as you would normally.

Edit: make sure you have all your required files in your switch folder on your sd card and as well of course your sxos files on the route. In fact put all your files you need to begin with on your sd card including your firmware files after setting up emunand. When you first setup emunand hidden partition it will erase your sd card just leaving the hidden nand and your emutendo folder then put all your files back on.

Make sure you use a high quality genuine micro sd card don’t go cheap you will only have issues in the long term.

 

[tabzer]

Yes I would personally use sxos emunand because it’s been more refined and in development a lot longer

Lol. That's a load of bull on both accounts.

 

[Reecey]

Lol. That's a load of bull on both accounts.

You do realise Team Xecuter developed emunand for the switch before Michael/Atmosphere? and yes it’s been developed and perfected way longer! and No they didn’t steal any code in the process..

I personally would never touch atmosphere emunand and tbh I wouldn’t even use Atmosphere cfw, full stop unless I had no other choice and I had to. No offence to Michael of course, it’s my opinion.

 

[OperationNT]

My Switch is in the same case, here is my configuration:
- Keep SysNAND on 4.1.0 without AutoRCM and configure it for PegaScape (with DNS "51.15.245.41"), see https://pegascape.sdsetup.com/
- Create an EmuMMC from this SysMMC (you can use SX OS free part to generate the EmuMMC partition, it's far more easy than doing it yourself; however, take care, it will wipe your SD card)
- Use Atmosphere with EmuMMC configuration: emummc_enabled = 1, emummc_sector = 0x2 (except for playing XCIs and thinking it keeps you safe online, now there is zero advantage in SX OS usage)
- Update the EmuMMC using ChoiduJourNX to latest FW

With this configuration, you can:
- Avoid AutoRCM restart issues when there is no more battery
- Start Atmosphere from your 4.1.0 SysMMC using PegaScape
- And, as your unit is unpatched, you can still use classic RCM with a paperclip (in case, for example, you get the SuperNAG on you SysMMC and you wish to remove it using GagOrder)

 

[Goldenman66]

There is no reason to purchase SX OS when Atmosphere can do just about everything for free.


Follow this guide if you want to use an emuNAND:


It's technically experimental, but it's fully functional.


You can use ChoiDujourNX with your sysNAND or your emuNAND. However, it should only be used with a NAND you don't intend to keep clean for online play.

I tried it with same results when I press to launch atmosphere EmuMMC it reboot again to hekate

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

My Switch is in the same case, here is my configuration:
- Keep SysNAND on 4.1.0 without AutoRCM and configure it for PegaScape (with DNS "51.15.245.41"), see https://pegascape.sdsetup.com/
- Create an EmuMMC from this SysMMC (you can use SX OS free part to generate the EmuMMC partition, it's far more easy than doing it yourself; however, take care, it will wipe your SD card)
- Use Atmosphere with EmuMMC configuration: emummc_enabled = 1, emummc_sector = 0x2 (except for playing XCIs and thinking it keeps you safe online, now there is zero advantage in SX OS usage)
- Update the EmuMMC using ChoiduJourNX to latest FW

With this configuration, you can:
- Avoid AutoRCM restart issues when there is no more battery
- Start Atmosphere from your 4.1.0 SysMMC using PegaScape
- And, as your unit is unpatched, you can still use classic RCM with a paperclip (in case, for example, you get the SuperNAG on you SysMMC and you wish to remove it using GagOrder)

Will give it a try

 

[Goldenman66]

I tried it with same results when I press to launch atmosphere EmuMMC it reboot again to hekate

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


Will give it a try

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

My Switch is in the same case, here is my configuration:
- Keep SysNAND on 4.1.0 without AutoRCM and configure it for PegaScape (with DNS "51.15.245.41"), see https://pegascape.sdsetup.com/
- Create an EmuMMC from this SysMMC (you can use SX OS free part to generate the EmuMMC partition, it's far more easy than doing it yourself; however, take care, it will wipe your SD card)
- Use Atmosphere with EmuMMC configuration: emummc_enabled = 1, emummc_sector = 0x2 (except for playing XCIs and thinking it keeps you safe online, now there is zero advantage in SX OS usage)
- Update the EmuMMC using ChoiduJourNX to latest FW

With this configuration, you can:
- Avoid AutoRCM restart issues when there is no more battery
- Start Atmosphere from your 4.1.0 SysMMC using PegaScape
- And, as your unit is unpatched, you can still use classic RCM with a paperclip (in case, for example, you get the SuperNAG on you SysMMC and you wish to remove it using GagOrder)

Do I really need pegascape or i can use autorcm or payload injectors to run SX OS?

 

[tabzer]

You do realise Team Xecuter developed emunand for the switch before Michael/Atmosphere? and yes it’s been developed and perfected way longer! and No they didn’t steal any code in the process..

It's been around longer, but continuous development for it is far cry. The idea of it being "perfected" is very debatable. The very reason that m4w and SciresM took so long to develop emummc is because they saw the method of emunand to be shoddy and rushed.

While their methods are open source, you can't really say SX OS steals from Atmosphere, but you can at least say they were "inspired" enough by it to copy/paste from it. https://gbatemp.net/threads/proof-tx-used-code-stolen-from-reswitched.509329/

SX OS is great for people who want to do little, except pay money, to use their switch to play pirated games. But when it comes to other projects like L4T Ubuntu and LineageOS Android, it's a real annoyance to try to incorporate emunand, if possible. https://gbatemp.net/threads/setup-g...id-with-emummc-bigger-fat32-partition.544981/ I wouldn't be able to pentaboot OFW (for online), CFW-Atmo, Lakka, Android, and L4T if I was using SXOS emunand. As SXOS does like to draw inspiration from projects like Atmosphere, you can count on them lagging behind the "competition" in updating compatibility with new firmware. The only feature it does have is running xcis from an external drive, which is a massive perk to the general hoarder. Compared to emunand, though, emummc is superior although requires more literacy to set up. Don't be surprised if SXOS decides to change how they do emunand.

The question is how interested someone like @Goldenman66 is going to be in further development on the homebrew front of things. Does he just want minimal setup and not really learn about technicalities, or is he invested in learning and trying new things with it as development happens?

I tried it with same results when I press to launch atmosphere EmuMMC it reboot again to hekate

All you need to do is create a second (FAT32) partition of 29856 MiB or 31307 MB, then use NYX to create the emummc AND set the configuration for it. Make sure your hekate_ipl.ini says:

[emuMMC All FW <-this can be changed, what's below is important]
fss0=atmosphere/fusee-secondary.bin

If it doesn't work, and you do have latest atmosphere on the sd, then it could be that your SD card is to blame: https://www.heise.de/download/product/h2testw-50539

 

[OperationNT]

Do I really need pegascape or i can use autorcm or payload injectors to run SX OS?

You can use AutoRCM but you will lose interest of this part: "Avoid AutoRCM restart issues when there is no more battery".