Hacking Question Two emuNANDs in a single SD for Atmosphere?

[el_refugio]

I'm looking for a way to create two emu NANDs in a single SD for Hekate+Atmosphere.

My SysNAND is in 6.2 IIRC, my current SD card has already a 8.1 emunand.
I want a 9.x emunand to play future game updates, since some games already refuse to work in 8.0. However, I want to keep my Lotus fuses intact, since I use a lot of original game cards in both sys and emu NANDs. Updating my emu NAND would disable the game card slot, so I wouldn't be able to play some original games.

So my idea is to have two emu NANDs: the current 8.1 and a new one that I'd use just for newer (digital only) games.



Is it really possible? What tools I need to get it done?

 

[BaamAlex]

Updating my emu NAND would disable the game card slot

The gamecard controller will only be updated when you disable the "Auto NoGC" option in hekate. Or when you boot the console normally. Then you burn fuses.

 

[el_refugio]

The gamecard controller will only be updated when you disable the "Auto NoGC" option in hekate. Or when you boot the console normally. Then you burn fuses.

I know. But if I leave it enabled, then I cannot use gamecards in 9.x. Am I wrong?

 

[BaamAlex]

I know. But if I leave it enabled, then I cannot use gamecards in 9.x. Am I wrong?

If it is enabled, then your gc controller will NOT, i repeat, NOT be updated.

 

[The Real Jdbye]

I know. But if I leave it enabled, then I cannot use gamecards in 9.x. Am I wrong?

If you disable it and boot 9.x, the game cart firmware gets updated anyway. You won't be able to use cartridges on sysNAND anymore without updating.

 

[el_refugio]

I'm not considering disabling the Auto NoGC. Since if I enable it, then it will burn the Lotus fuses and I won't be able to use gamecards in any <9.0 firmware. And I do not want that.

What I want is to have two emu NANDs, a 8.x to load my gamecards and a 9.x to load any other content (with Auto NoGC enabled, of course).

 

[The Real Jdbye]

I'm not considering disabling the Auto NoGC. Since if I enable it, then it will burn the Lotus fuses and I won't be able to use gamecards in any <9.0 firmware. And I do not want that.

What I want is to have two emu NANDs, a 8.x to load my gamecards and a 9.x to load any other content (with Auto NoGC enabled, of course).

What's the big deal about being able to use carts on <9.0? When are you ever going to need to do that? And why <9.0 specifically? Every major update (x.0) as well as some minor updates (?.x) update the game cart firmware and prevent game cart usage on lower FW. It's not only 9.0 that does that.

Also, why don't you update your sysNAND to 8.x and use that? Inserting any game cart with 8.x on it should prompt to update to that firmware.

Do keep in mind, new games that come out will probably not work on 8.x, and same thing with new updates/DLC. Basically you will only be able to play what you have right now and if you buy new cart games down the line, or want to use newer updates/DLC with your cart games, you would have to update anyway.

As for your question, you set up a second emuNAND in exactly the same way as the first. Create another partition of 29856 size, and create emuNAND in Hekate (but make sure to select the correct partition, don't wipe your existing emuNAND!) and to switch between the two, change the active emuNAND in Hekate and remember to press save settings.

 

[el_refugio]

What's the big deal about being able to use carts on <9.0? When are you ever going to need to do that?

Because I've got them and I want to use them.

And why <9.0 specifically? Every major update (x.0) as well as some minor updates (?.x) update the game cart firmware and prevent game cart usage on lower FW. It's not only 9.0 that does that.

AFAIK, nto every major udpate does that. I've been able to use gamecards in my 8.x emu NAND, and they still work in my 6.x sys NAND.

Also, why don't you update your sysNAND to 8.x and use that? Inserting any game cart with 8.x on it should prompt to update to that firmware.

Because I want to keep my sys NAND as low as possible, just in case another exploit appears in a future.

As for your question, you set up a second emuNAND in exactly the same way as the first. Create another partition of 29856 size, and create emuNAND in Hekate (but make sure to select the correct partition, don't wipe your existing emuNAND!)

Oh, was it that easy?
I'll try in the following days, thank you.
I will backup all my FAT files and repartition from there, I do not trust repartitioning an existing partition.

 

[The Real Jdbye]

Because I've got them and I want to use them.



AFAIK, nto every major udpate does that. I've been able to use gamecards in my 8.x emu NAND, and they still work in my 6.x sys NAND.


Because I want to keep my sys NAND as low as possible, just in case another exploit appears in a future.


Oh, was it that easy?
I'll try in the following days, thank you.
I will backup all my FAT files and repartition from there, I do not trust repartitioning an existing partition.

There is a warmboot exploit confirmed to be possible on up to 7.0.1, but it requires wifi and a working web browser every time. If you accidentally forget to use the custom DNS when connecting to a wifi to run the exploit, you get a supernag and it locks you out of the browser. Also, to boot CFW, you need to first boot sysNAND, go through the steps to set up a wifi with the DNS if needed, launch the captive portal browser, and hope that the exploit works. If it fails (which it does maybe 1/3 of the time on 4.1 0) you have to reboot and try again. I hacked my brother's iPatched Switch on 4.1.0 this way (same exploit) and it's a much bigger hassle than a RCM dongle and jig. It's not worth waiting for on an unpatched Switch. There are no better exploits that have been discovered, and who knows if there ever will be. If you still want to wait knowing all that, feel free. Meanwhile, I'm going to be enjoying my Switch with online on my updated sysNAND and CFW on my offline emuNAND.

 

[BaamAlex]

just in case another exploit appears in a future

But you already have a almost perfect futureproof exploit called fusée gelée. I don't get it why the people keeps their firmware as low as possible. There may be exploits in the future. But what does it do for you? Except that you can run a custom firmware without a jig and dongle through a coldboot? For me it is an argument which is very weak. Just update the console and dump the games. You don't have to change your gamecard all the time. Which is really annoying after a long time.