Online emuMMC with CFW

jerrokun

Active Member
OP
Newcomer
Joined
Jan 14, 2015
Messages
41
Trophies
0
Age
32
XP
169
Country
United States
I have 2 switches. One patched model for online play, one offline unpatched model running homebrew on emuMMC.

I want to merge the two setups together onto my hacked Switch, and get rid of the patched one. 2 emuMMCs on the sd card, one for online, one for offline, both using CFW. Based on this guide.

Here's an outline of what I plan to do:

1) Take unpatched Switch, use Hekate to format microsd card with 2 emuMMC partitions
2) Create a new emuMMC by cloning sysnand ("online")
3) Load the online emuMMC through Atmosphere. Connect to the internet and update through the system settings
4) Confirm that there's no ban
5) Perform system transfer from patched Switch

Then setup the offline emuMMC:

6) Use Hekate's "Migrate emuMMC" option to restore the old emuMMC ("offline") to the 2nd partition
7) Load the offline emuMMC, confirm it works
8) Switch between the two emuMMCs from Hekate
9) Confirm that there's no ban for the online emuMMC

I have several questions about this process.

1) Will going online on a clean emuMMC with Atmosphere result in a ban?

This is assuming it's unmodified and has no homebrew usage. I only want to use emuMMC to preserve my sysnand's low firmware and to switch between the two emuMMCs easily.

I previously assumed using CFW online in any form was unsafe, but apparently it's fine as long as you don't modify anything.

2) Are the internet settings across sysnand and different emuMMC partitions separate?

I only want the clean emuMMC going online. I want to confirm that adding my wifi on that emuMMC won't add it to sysnand or the offline emuMMC.

3) How do I safely update an online emuMMC?

I can't use homebrew to update it, because I assume that will flag a ban. If I update via system settings, and the system reboots, will that only modify the clean emuMMC? I don't want it modifying sysnand, the system's burnt fuse count, or anything else.

4) Does anything I do on the offline emuMMC affect the online emuMMC?

I want to keep the two completely isolated.

5) Can I use any homebrew online without getting banned?

I assume the answer is no, but it can't hurt to ask.
 

JackTheFroster

Well-Known Member
Member
Joined
Feb 13, 2017
Messages
166
Trophies
0
Age
22
XP
269
Country
Germany
I sometimes used Atmosphere with sysNAND just for savegame (checkpoint) related stuff and nothing happened yet, i still won't recommend it though, you never know... but messing with more stuff like installing unsigned code, go online with cheats etc. is probably too much. just keep that for offline emuMMC :) for me its still very unlikely to get banned on a clean emuMMC, but i cant be for sure since i only used sysNAND. if theres anything that nintendo sees, its more likely on an emuMMC.

Every emuMMC and sysNAND has their own setups. i am pretty sure there wont be any problems with internet configs unless you use a LAN adapter.

Keeping a "lower firmware" isnt making much sense for me. I'd rather just say how i understood it but research more about it to be safe! As long as you wont burn efuses, you should probably be fine with downgrading in the future. As far as i know this will be achieved by updating sysNAND while on CFW. I dont know if only updating on emuMMC works or is safe... it will most likely update your gamecart reader making lower firmwares fail to read your gamecarts until being on the same firmware again... I dont know if your gamecart reader might not update when installing a newer firmware with CFW, havent seen such things yet. i dont mind about burning efuses, others do. i only think a future exploit where we dont need RCM anymore might be the only thing that i would not burn my fuses, but rcm is good enough for me... still, maybe someone else can explain it better.

As already said, every emuMMC and sysNAND has their own setups. no matter what you do, it wont effect any other.

There is a way to block nintendo's servers with DNS setups. that way you should be okay to use homebrew that might need internet connection safely. still, i used homebrew on sysNAND online and nothing happened to my switch yet. but a risk is always there...

EDIT: I see now why not updating is profitable here assuming you are on 4.1.0 or below. As stated on the tutorials forum you can see:
I didn't quite understand your question.

For online use, one of your emuMMC must be created from a clean NAND.

The goal here is to have a dirty and a clean emuMMC (both can be updated, using ChoirdujourNX and Nintendo servers respectively), and keep your real sysnand with the lowest possible firmware, in order to benefit from DejaVu.
So updating might not be a problem on a clean emuMMC and you can always update your "dirty" one with daybreak
 
Last edited by JackTheFroster,
  • Like
Reactions: binkinator

Nagaa

Well-Known Member
Newcomer
Joined
Nov 8, 2020
Messages
54
Trophies
0
XP
321
Country
France
I don't understand why you want to create a emunand for playing online, i'm not even sure you can connect online with emunand.

Create a Emunand for all your pirated game / emulator, and use sysnand online with atmosphere if you need it

For the question you ask :
1)Playing online with cfw won’t get you banned
However having piracy, dumped games, and homebrew on the home screen now is an instant ban
2)Separate settings
3) Daybreak
4)Never use a dual emunand setup but it should not
5)Homebrew in title override is fine
 

HalfScoper

Well-Known Member
Member
Joined
Apr 16, 2021
Messages
293
Trophies
0
Age
82
XP
704
Country
Germany
I have 2 switches. One patched model for online play, one offline unpatched model running homebrew on emuMMC.

I want to merge the two setups together onto my hacked Switch, and get rid of the patched one. 2 emuMMCs on the sd card, one for online, one for offline, both using CFW. Based on this guide.

1) Will going online on a clean emuMMC with Atmosphere result in a ban?

This is assuming it's unmodified and has no homebrew usage. I only want to use emuMMC to preserve my sysnand's low firmware and to switch between the two emuMMCs easily.

I previously assumed using CFW online in any form was unsafe, but apparently it's fine as long as you don't modify anything.

2) Are the internet settings across sysnand and different emuMMC partitions separate?

I only want the clean emuMMC going online. I want to confirm that adding my wifi on that emuMMC won't add it to sysnand or the offline emuMMC.

3) How do I safely update an online emuMMC?

I can't use homebrew to update it, because I assume that will flag a ban. If I update via system settings, and the system reboots, will that only modify the clean emuMMC? I don't want it modifying sysnand, the system's burnt fuse count, or anything else.

4) Does anything I do on the offline emuMMC affect the online emuMMC?

I want to keep the two completely isolated.

5) Can I use any homebrew online without getting banned?

I assume the answer is no, but it can't hurt to ask.

Throw away that thought and listen to the others, it's not necessary to have 2 emuMMCs/NANDs, just setup one emuNAND to play/use homebrew/whatever you want offline, and configure it appropriately to not connect to Nintendo's servers.
Then, on your stock firmware, you can continue to use the online services, the eShop and anything else you "normally" would without having to worry to get banned.
Again, as long as you configure everything correctly, you are safe that way, I am aswell since almost 2 years now, visiting stock firmware regularly to access the eShop and backup my games offline.

To answer the questions (and providing proper links):

1) Answering it in a different way (which should interest you more concerning what I said above), you can even use CFW on your sysNAND (internal storage) without having to worry for a ban, as long as you configure everything for your other "offline plans" correctly. Some things should be avoided, like having "non-official backups" installed or applications like Tinfoil, also cheating in online games with leaderboards (MH: Rise for example is (pretty) safe) or using custom profile icons. Generally speaking anything that taints your system in a way directly. Casual homebrew NROs from within the hbmenu are safe.

2) The emuNAND is a 1:1 copy of your sysNAND, so any configuration you had before creation of the emuNAND will be present on it aswell. However, since sys and emuNAND are independent from each other, changing anything on your emuNAND won't affect the sysNAND (and also vice-versa for an already created emuNAND).

3) Safely updating your firmware depends on where: for sysNAND you can just use the system settings, it's really as easy as that, either you are careful enough to not get banned or don't care about it, just use it.
Given that you intend to use your emuNAND for "other means" you should use Daybreak. Getting firmware files is on you, but googling ain't hard just saying, guide is here: https://rentry.org/UpgradeDowngrade . Please note that you always should update your CFW files beforehand to avoid issues.

4) Look at 2), no, everything is independent from each other once created.

5) Also to 1), take a look at this: https://rentry.org/AvoidSwitchBan . Read everything and then decide what method suites you best, means either Incognito or exosphere (recommended) + dns_mitm configuration for your emuNAND (the NAND you intend to do "other things" on.


Hope that clears it up for you.
 

VeniaSilente

Well-Known Member
Newcomer
Joined
Sep 6, 2014
Messages
88
Trophies
0
XP
447
Country
Cote d'Ivoire
Others have already replied with most of what you need, just thought I'd add a few minor details in particular if for some weird reason you decide to go with two emuNANDs. Since I am more familiar with how dual emuNAND methods operate as my Switch requires Caffeine (and so do I).

1) Take unpatched Switch, use Hekate to format microsd card with 2 emuMMC partitions
2) Create a new emuMMC by cloning sysnand ("online")
3) Load the online emuMMC through Atmosphere. Connect to the internet and update through the system settings
4) Confirm that there's no ban
5) Perform system transfer from patched Switch

Then setup the offline emuMMC:

6) Use Hekate's "Migrate emuMMC" option to restore the old emuMMC ("offline") to the 2nd partition
7) Load the offline emuMMC, confirm it works
8) Switch between the two emuMMCs from Hekate
9) Confirm that there's no ban for the online emuMMC
The plan is sound, just unneeded. You can do with one emuNAND. If for some reason you want to still go with two, consider that this means twice the lost space on your SD Card.

A means to palliate this is, if you have the latest versions of Hekate, to pre-partition your SD Card so that the offline emuNAND has less than 28 GB reserved. You can do with somewhere around 16 GB and 24 GB for the offline one without issues, you'll just have less room to store game saves (so balance this against eg.: if you are going to play Save-heavy games like New Pokémon Snap on the offline one).

But as others have said, why go through all that trouble.

3) How do I safely update an online emuMMC?
So long as you don't connect online your sysNAND, do via the System Settings. It works ("always has been" meme) without issues.

Otherwise, you have to update sysNAND normally and update both emuNANDs ONLY EVER via Daybreak,

Just make sure to make a NAND Backup right after you're done with the first boot on the new firmware version.

4) Does anything I do on the offline emuMMC affect the online emuMMC?
They are about as independent from each other as you can get, except for one thing: Home Menu modifications. If you install themes, they'll be active on both the emuNANDs and the sysNAND, since they are actually applies to Atmosphere's "contents/" folder and not to the firmware paritition and Atmosphere has not implemented multiseat/multiconfig yet as far as I know, so avoid it (even on the offline one) if you can.

I want to keep the two completely isolated.

5) Can I use any homebrew online without getting banned?
On online emuNAND: No [*1]

On offline emuNAND: Depends [*2]

[*1] You can in theory use any homebrew that you launch via applet mode without issues. I was running stuff like JKSV, ftpd, etc for a few years before my Switch died and back then was the 12.x firmware versions and nothing had happened yet that I recall. That said, you'll be safer if you enable Atmosphere's DNS MITM full protection mode in the meantime, I guess? Since that blocks connections to *all* known Nintendo servers.

However note that in this case you'll have to use different MITM setups for offline and online emuNANDs (this is supported by choosing different filenames for their host files), and I'm not sure how that dual setup can be properly tested on the online emuNAND side since a resolution test while you are doind sysmodule stuff might perhaps risk a ban?

[*2] So long as your offline emuNAND is properly configured with DNS MITM to avoid any connection to Nintendo *ever*, you should be able to use most of everything. Just always make sure to use MITM full protection mode (the hosts file that blocks all Nintendo, portal and Switch domains).
 
  • Like
Reactions: jerrokun

The Real Jdbye

*is birb*
Member
Joined
Mar 17, 2010
Messages
22,062
Trophies
3
Location
Space
XP
11,332
Country
Norway
I have 2 switches. One patched model for online play, one offline unpatched model running homebrew on emuMMC.

I want to merge the two setups together onto my hacked Switch, and get rid of the patched one. 2 emuMMCs on the sd card, one for online, one for offline, both using CFW. Based on this guide.

Here's an outline of what I plan to do:

1) Take unpatched Switch, use Hekate to format microsd card with 2 emuMMC partitions
2) Create a new emuMMC by cloning sysnand ("online")
3) Load the online emuMMC through Atmosphere. Connect to the internet and update through the system settings
4) Confirm that there's no ban
5) Perform system transfer from patched Switch

Then setup the offline emuMMC:

6) Use Hekate's "Migrate emuMMC" option to restore the old emuMMC ("offline") to the 2nd partition
7) Load the offline emuMMC, confirm it works
8) Switch between the two emuMMCs from Hekate
9) Confirm that there's no ban for the online emuMMC

I have several questions about this process.

1) Will going online on a clean emuMMC with Atmosphere result in a ban?

This is assuming it's unmodified and has no homebrew usage. I only want to use emuMMC to preserve my sysnand's low firmware and to switch between the two emuMMCs easily.

I previously assumed using CFW online in any form was unsafe, but apparently it's fine as long as you don't modify anything.

2) Are the internet settings across sysnand and different emuMMC partitions separate?

I only want the clean emuMMC going online. I want to confirm that adding my wifi on that emuMMC won't add it to sysnand or the offline emuMMC.

3) How do I safely update an online emuMMC?

I can't use homebrew to update it, because I assume that will flag a ban. If I update via system settings, and the system reboots, will that only modify the clean emuMMC? I don't want it modifying sysnand, the system's burnt fuse count, or anything else.

4) Does anything I do on the offline emuMMC affect the online emuMMC?

I want to keep the two completely isolated.

5) Can I use any homebrew online without getting banned?

I assume the answer is no, but it can't hurt to ask.
I would use two different SD cards, as it's not possible to have a different set of Atmosphere files per emuNAND, that means sysmodules, sigpatches etc. will be loaded even on the "legit" emuNAND, which could increase the risk of a ban, also if you use PRODINFO blanking and/or DNS blacklisting, it will apply to both emuNANDs and prevent you from going online, so you have to revert to the old school method of Incognito and/or 90DNS, which is more trouble.
The question is, why do this? On a patched 4.1.0 console it makes sense, as you can't update the sysNAND. On an unpatched console there is no issue updating the sysNAND at all, so using an emuNAND for online is a waste of space and a needless (albeit small) ban risk. The safest way is loading OFW from a normal boot.
 

RandomUser

Rosalina in Plush Form
Member
Joined
May 9, 2010
Messages
938
Trophies
0
XP
956
Country
United States
Are the NAND encrypted to a specific console? I have not been in the loop for switch hacking, but I think what you're proposing won't work.
Someone please correct me if I'm wrong.
 

fvig2001

Well-Known Member
Member
Joined
Aug 21, 2006
Messages
726
Trophies
0
XP
2,155
Country
Philippines
1. In theory no. I didn't get banned on mine since I had to use emummc since I had a 256GB nand
2. Well if you change them each, yes
3. Legitly, just use the normal system settings update as long as Atmosphere supports the new firmware
4. Yes
5. If it doesn't touch the OS obviously then yes. I've used it to dump firmware before. Editing saves could get your switch banned.

I personally would not recommend using an emunand for legit online. My experience is that some games don't run at all like games downloaded from eShop.
 

jerrokun

Active Member
OP
Newcomer
Joined
Jan 14, 2015
Messages
41
Trophies
0
Age
32
XP
169
Country
United States
Thanks for the replies.

I should clarify: I know how to update an offline emuMMC using homebrew. I asked question 3) specifically regarding an online emuMMC without homebrew, because I wasn't sure if a regular update through Nintendo's servers would cause issues for the setup.

I don't plan on connecting the offline emuMMC to the internet at all, so DNS settings shouldn't even be necessary. I can look into that later if I want to use online homebrew.

EDIT: I see now why not updating is profitable here assuming you are on 4.1.0 or below. As stated on the tutorials forum you can see:

So updating might not be a problem on a clean emuMMC and you can always update your "dirty" one with daybreak

That's it, yeah. More trouble to setup but it means preserving a low sysnand firmware so I can use Deja Vu instead of a payload.

I don't understand why you want to create a emunand for playing online, i'm not even sure you can connect online with emunand.

Create a Emunand for all your pirated game / emulator, and use sysnand online with atmosphere if you need it
just setup one emuNAND to play/use homebrew/whatever you want offline, and configure it appropriately to not connect to Nintendo's servers.

To answer the questions (and providing proper links):

1) Answering it in a different way (which should interest you more concerning what I said above), you can even use CFW on your sysNAND (internal storage) without having to worry for a ban, as long as you configure everything for your other "offline plans" correctly. Some things should be avoided, like having "non-official backups" installed or applications like Tinfoil, also cheating in online games with leaderboards (MH: Rise for example is (pretty) safe) or using custom profile icons. Generally speaking anything that taints your system in a way directly. Casual homebrew NROs from within the hbmenu are safe.

Is Atmosphere safe to use online for sysnand, then? It means burning fuses and no Deja Vu, but it would be easier to setup.

Otherwise, you have to update sysNAND normally and update both emuNANDs ONLY EVER via Daybreak,

Just make sure to make a NAND Backup right after you're done with the first boot on the new firmware version.
3. Legitly, just use the normal system settings update as long as Atmosphere supports the new firmware

So updating through the system menu won't change anything? Except disable autoRCM?

The question is, why do this? On a patched 4.1.0 console it makes sense, as you can't update the sysNAND. On an unpatched console there is no issue updating the sysNAND at all, so using an emuNAND for online is a waste of space and a needless (albeit small) ban risk. The safest way is loading OFW from a normal boot.

Preserving fuses and being able to use Deja Vu to launch Hekate. After all these replies, it sounds like it might not be worth the trouble.

Are the NAND encrypted to a specific console?

They might be, but that doesn't stop me from doing anything I described here.

New questions:

6) Will going online with Atmosphere on sysnand cause a ban?

This would basically be the same as having a clean "online" emuMMC, just with much less setup.

7) Is it worth preserving fuses in 2022?

I like the idea of being able to keep sysnand low and fuses unburnt, in case any new developments happen. But if I can safely use Atmosphere on sysnand, it seems more trouble than it's worth...
 

fvig2001

Well-Known Member
Member
Joined
Aug 21, 2006
Messages
726
Trophies
0
XP
2,155
Country
Philippines
updating legitly has no effect on autorcm if the firmware being updated is in emunand.

For legit nand, I usually boot info CFW with no sigpatches and update normally. This one prevents autorcm from being removed.
 

RednaxelaNnamtra

Well-Known Member
Member
Joined
Dec 8, 2011
Messages
1,133
Trophies
0
XP
2,656
Country
Germany
Thanks for the replies.

I should clarify: I know how to update an offline emuMMC using homebrew. I asked question 3) specifically regarding an online emuMMC without homebrew, because I wasn't sure if a regular update through Nintendo's servers would cause issues for the setup.

I don't plan on connecting the offline emuMMC to the internet at all, so DNS settings shouldn't even be necessary. I can look into that later if I want to use online homebrew.



That's it, yeah. More trouble to setup but it means preserving a low sysnand firmware so I can use Deja Vu instead of a payload.




Is Atmosphere safe to use online for sysnand, then? It means burning fuses and no Deja Vu, but it would be easier to setup.




So updating through the system menu won't change anything? Except disable autoRCM?



Preserving fuses and being able to use Deja Vu to launch Hekate. After all these replies, it sounds like it might not be worth the trouble.



They might be, but that doesn't stop me from doing anything I described here.

New questions:

6) Will going online with Atmosphere on sysnand cause a ban?

This would basically be the same as having a clean "online" emuMMC, just with much less setup.

7) Is it worth preserving fuses in 2022?

I like the idea of being able to keep sysnand low and fuses unburnt, in case any new developments happen. But if I can safely use Atmosphere on sysnand, it seems more trouble than it's worth...
If you make a backup of your sysnand and use autorcm you will preserve the fuses and always be able to go back to the current state if needed for an exploit.

Another thing to keep in mind:
always just have one nand that connects to nintendos servers. There are logs shared, that the system keeps even after factory resets, and if they don't match, because you restored a backup from before the last connection to nintendos serves or because you connected with a different setup, you will most likely get flagged for a ban.

About the emunand, it would make your setup just needlessly complicated when you use two emunands, because your goal can be archived in a better way, that's less probable to create issues by accident (like accidentally connecting online on the low firmware sysnand).
Another thing to keep in mind is the gamecard firmware, atmosphere comes with gc patches enabled by default, which will prevent your gamecard reader firmware from updating and burning fuses, but it also prevents you from using gamecard at all. So if you want or use gamecards on the online nand, you will need to disable them, leading to no way to use gamecards on a lower firmware version.

Also keep your atmosphere for going online as stock as possible. System modules and homebrew started from applet mode via album or app mode via app overwrite (hold r while booting a game) aren't a problem and can be used relatively safely while going online. But patches to things like the signature checks can be problematic, so be careful with them. You might be able to load them seperatelly for the offline emunand via manual kip or package 3 definition, but since i don't use them, I'm would need to check what they contain excatly to give some more specific instructions.
Custom builds of atmosphere with custom paths would also work to seperated them, but no idea of someone releases some build for that.
 

The Real Jdbye

*is birb*
Member
Joined
Mar 17, 2010
Messages
22,062
Trophies
3
Location
Space
XP
11,332
Country
Norway
Thanks for the replies.

I should clarify: I know how to update an offline emuMMC using homebrew. I asked question 3) specifically regarding an online emuMMC without homebrew, because I wasn't sure if a regular update through Nintendo's servers would cause issues for the setup.

I don't plan on connecting the offline emuMMC to the internet at all, so DNS settings shouldn't even be necessary. I can look into that later if I want to use online homebrew.



That's it, yeah. More trouble to setup but it means preserving a low sysnand firmware so I can use Deja Vu instead of a payload.




Is Atmosphere safe to use online for sysnand, then? It means burning fuses and no Deja Vu, but it would be easier to setup.




So updating through the system menu won't change anything? Except disable autoRCM?



Preserving fuses and being able to use Deja Vu to launch Hekate. After all these replies, it sounds like it might not be worth the trouble.



They might be, but that doesn't stop me from doing anything I described here.

New questions:

6) Will going online with Atmosphere on sysnand cause a ban?

This would basically be the same as having a clean "online" emuMMC, just with much less setup.

7) Is it worth preserving fuses in 2022?

I like the idea of being able to keep sysnand low and fuses unburnt, in case any new developments happen. But if I can safely use Atmosphere on sysnand, it seems more trouble than it's worth...
Deja Vu is the browser exploit, right? If so, it's a bigger hassle than just using RCM. You need wifi and internet, you need to boot the console into OFW first before you can launch it, sometimes it fails and you need to reboot, etc.
It takes only a few seconds to launch a payload with RCM from powered off state, compared to the 45 seconds it takes to launch a payload with the browser exploit from powered off state.
 
Last edited by The Real Jdbye,

JackTheFroster

Well-Known Member
Member
Joined
Feb 13, 2017
Messages
166
Trophies
0
Age
22
XP
269
Country
Germany
Deja Vu is the browser exploit, right? If so, it's a bigger hassle than just using RCM. You need wifi and internet, you need to boot the console into OFW first before you can launch it, sometimes it fails and you need to reboot, etc.
Yes, its the warmboot exploit. pros for that is you dont need to inject a payload, having a dongle or whatever, but i would rather use rcm or a coldboot exploit.

I also havent seen anyone really showcasing the exploit on youtube, which might be because there are barely consoles anymore on 4.1.0 or lower. Many people are probably updating and use the latest firmware since SciresM keeps Atmosphere and many other things updated and its way easier to update and manage things with just one emuMMC imo. Could be more likely to see a new exploit on newer firmwares anyway...
 

jerrokun

Active Member
OP
Newcomer
Joined
Jan 14, 2015
Messages
41
Trophies
0
Age
32
XP
169
Country
United States
For legit nand, I usually boot info CFW with no sigpatches and update normally. This one prevents autorcm from being removed.
But patches to things like the signature checks can be problematic, so be careful with them. You might be able to load them seperatelly for the offline emunand via manual kip or package 3 definition, but since i don't use them, I'm would need to check what they contain excatly to give some more specific instructions.

I'm not familiar with sigpatches. If I use those for Atmosphere on my offline emuMMC, will they affect Atmosphere on sysnand? If so, will that result in a ban?

Deja Vu is the browser exploit, right? If so, it's a bigger hassle than just using RCM.
Yes, its the warmboot exploit. pros for that is you dont need to inject a payload, having a dongle or whatever, but i would rather use rcm or a coldboot exploit.

I also havent seen anyone really showcasing the exploit on youtube, which might be because there are barely consoles anymore on 4.1.0 or lower.

That seems to be the general consensus. In that case, I'm not too fussed about burning fuses. One emuMMC would be a lot easier to manage.
 

HalfScoper

Well-Known Member
Member
Joined
Apr 16, 2021
Messages
293
Trophies
0
Age
82
XP
704
Country
Germany
If you install sigpatches onto a SD card, which you use for both sys and emuNAND, they will also be loaded if you'd start sysNAND with CFW, there's no way avoiding that other than having two seperate SD cards. Still, just having them shouldn't cause a ban, "utilizing" them as in having them for game backups is, but then you'd get banned for the backups, not the patches.
I personally use and recommend two SD cards, one for sysNAND means and one for emuNAND.

At least it seems you got rid off the thought having two emuNANDs.
 
  • Like
Reactions: jerrokun

josete2k

Well-Known Member
Member
Joined
Apr 24, 2009
Messages
392
Trophies
0
Age
42
Location
Spain
XP
782
Country
Spain
I'd install perma incognito (launching incognito rcm) to the offline emunand. And launch online emunand without the kip1 active in hekate_ipl.ini.
 

josete2k

Well-Known Member
Member
Joined
Apr 24, 2009
Messages
392
Trophies
0
Age
42
Location
Spain
XP
782
Country
Spain
If you install sigpatches onto a SD card, which you use for both sys and emuNAND, they will also be loaded if you'd start sysNAND with CFW, there's no way avoiding that other than having two seperate SD cards. Still, just having them shouldn't cause a ban, "utilizing" them as in having them for game backups is, but then you'd get banned for the backups, not the patches.
I personally use and recommend two SD cards, one for sysNAND means and one for emuNAND.

At least it seems you got rid off the thought having two emuNANDs.
No, you can load one emummc with patches and another emummc without patches.
 

HalfScoper

Well-Known Member
Member
Joined
Apr 16, 2021
Messages
293
Trophies
0
Age
82
XP
704
Country
Germany
I'd install perma incognito (launching incognito rcm) to the offline emunand. And launch online emunand without the kip1 active in hekate_ipl.ini.
Honestly don't know what you are on about because I don't even have a kip entry in my hekate_ipl.ini and it's not needed, fusee.bin loads them automatically (if patches.ini is also present on a hekate setup).
No, you can load one emummc with patches and another emummc without patches.
Ok, aside from it being pretty useless still, you could also spare one more minute of your time and explain how, because OP obviously would've been interested in it.
 

jerrokun

Active Member
OP
Newcomer
Joined
Jan 14, 2015
Messages
41
Trophies
0
Age
32
XP
169
Country
United States
If you install sigpatches onto a SD card, which you use for both sys and emuNAND, they will also be loaded if you'd start sysNAND with CFW, there's no way avoiding that other than having two seperate SD cards. Still, just having them shouldn't cause a ban, "utilizing" them as in having them for game backups is, but then you'd get banned for the backups, not the patches.
I personally use and recommend two SD cards, one for sysNAND means and one for emuNAND.

At least it seems you got rid off the thought having two emuNANDs.

Thanks for the info. I suppose 2 sd cards is an option, even if it's not ideal.

No, you can load one emummc with patches and another emummc without patches.

Can you explain how? I don't need 2 emuMMCs. But can you load emuMMC with patches and sysNAND without, with one sd card?
 

josete2k

Well-Known Member
Member
Joined
Apr 24, 2009
Messages
392
Trophies
0
Age
42
Location
Spain
XP
782
Country
Spain
Stock (sysmmc without any patches):

[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
id=stock



Sysmmc CFW With patches:

[sysmmc CFW]
fss0=atmosphere/package3
emummc_force_disable=1
kip1patch=nosigchk
id=sysnand


Sysmmc CFW without patches (useless better use stock):

[sysmmc unpatched]
fss0=atmosphere/package3
emummc_force_disable=1
id=sysnand0


Emummc #1 with patches (remember to apply RCM incognito before)

[emuMMC incognito]
emupath=emuMMC/SD00
fss0=atmosphere/package3
emummcforce=1
kip1patch=nosigchk
id=emunand1


Emummc #2 without patches (go online)


[emuMMC online]
emupath=emuMMC/SD01
fss0=atmosphere/package3
emummcforce=1
id=emunand2



The emupath folder must be created by hekate when creating the emummc files/raw
 
Last edited by josete2k,
General chit-chat
Help Users
  • No one is chatting at the moment.
    Sonic Angel Knight @ Sonic Angel Knight: https://twitter.com/Rubberduckcooly/status/1559319321850941440