Online emuMMC with CFW
- Thread starter jerrokun
- Start date
- Views 13,777
- Replies 33
Morbidly curious on how this is going to turn out.
This is going to be hard to test.
initially thought you could just urn off your wifi/disconnect cable from dock or whatever you need to do to disable network and boot into CFW/Sysnand and see if you could start a game, but if you couldn’t it would crash and write a nice entry in your logs to tell Ninty next time it was able to check in.
Maybe the log redirection in Atmosphere takes care of that though?
To be safe you should probably make a backup of your Sysnand so you can restore it to how it was before the test. That way you can try a game and see if Sigpatches are put in place automatically even though you aren’t specifying them.
Anyone have better ideas on how to test whether or not Sigpatches are in play?
Well, an unpatched cfw should not have any backups installed... So legit games should work.
Same as stock.
The unpatched emunand is for caffeine/pegaswitch users, so they can upgrade their emummc in order to play online safety. That's why I think that is a good idea to apply rcm incognito te gustaría the patched emummc.
Same as stock.
The unpatched emunand is for caffeine/pegaswitch users, so they can upgrade their emummc in order to play online safety. That's why I think that is a good idea to apply rcm incognito te gustaría the patched emummc.
Right, but how to definitively test that Sigpatches aren’t in play when you go online with Sysnand/CFW?
Probably easiest to test the "offline" emuMMC by trying with and without the "kip1patch=nosigchk" line and seeing if that toggles them on and off.
I just intend to use 2 sd cards for now, and keep sysnand on stock. But I'll look into that later on.
Don't boot sysNAND through CFW, just boot OFW by booting the system normally.
There's no such thing as CFW with no patches. Fuse check patches are always applied, Atmosphere has its own custom sysmodules/patches that are needed for it to work, and there are patches applied to bypass the AutoRCM brick.
Also, removing nosigchk won't fully disable sig patches, that's only half of it. The other half is the files that are placed in the atmosphere folder, which are always applied.
I would say its best to boot OFW always without Atmosphere unless updating your firmware since that would at least not burn any fuses i think. thats what i am doing for years now and my CFW is always offline
The only time you burn fuses during an update is when the console restarts to ofw. The only way to bypass burning efuses is by booting hekate, fusee.bin, etc.
Fuse check is in bootloader, not in HOS... And Ninty can't know if you have booted by genuine bootloader or by hekate/fusee.
There are many people that aren't banned and boot their emummc cfw by pegaswitch exploit (without sigpatches of course).
And how can you be sure that they can't know?
Yes, my little brother is among them. All the Switches for sale at the time were patched so the only option was an iPatched 4.1.0 unit. Still, it's not ideal, and not worth taking any risks (however small) unless it's the only option, like it is for those people with patched 4.1.0 units.
Since Hekate can bypass burnt fuse checks on Emunand and you can upgrade/downgrade to your heart’s content, just upgrade Sysnand and boot normaly w/o CFW. Be squeaky clean Online w/ Sysnand.
The fuse game is overrated and buys you nothing really.
The fuse game is overrated and buys you nothing really.
easy. just dont install package3 sigpatches. they use to be separated before. package3 sigpatches are that txt file that comes with sigpatches(+ that nosigchk line in hekate ini), just only copy n paste the ones that drop into the atmosphere folder. then you dont have package3 (aka sysnand) sigpatches.
i only ever install fusee sigpatches for my incognito'd emunand, while i go online and play online in syscfw. been fine for 3+yrs now no ban.
Similar threads
