Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

[petspeed]

I apologise for the stupid questions!

So I have updated my Switch to 17.0.0 on the EmuMMC, updated Hekate, Atmosphere 1.6.2, fusee.bin etc. The Switch crashes with the error code for a blanked prodkey. I have backups of my prodkeys for both SysMMC and EmuMMC. If I boot my Switch into SysMMC, it's on an old firmware and the serial number shown in the settings is correct for the console, ie: I never blanked the SysMMC one.

However, booting my Switch into EmuMMC crashes. I have the backups of absolutely everything, including the prodkey bin files from Incognito_RCM. I understand to get my EmuMMC working again, I'll need to restore the prodkey to EmuMMC via Incognito_RCM. The problem I think is that there isn't a version (yet) that supports 17.0.0.

This repository supports 16.0 - https://github.com/mistervampi/Incognito_RCM - using this, I get 'unknown pkg1 version' when it's attempting to retrieve biskeys.

Are my options to wait for an Incognito_RCM to support 17.0, or to simply delete my EmuMMC and start over, with no blanked serial number? I have a lot of data inside the EmuMMC so it would be a pain to lose it all.

Thanks!

If you want to restore your prodkey.bin you can downgrade EmuMMC to 16.0.0 with Daybreak, then use Incognito_RCM to restore prodkey and then use Daybreak to upgrade EmuMMC back to 17.0.0

But you can also just use DNSmitm to block Nintendo servers. Then your switch will not crash even with a blanked serial.
https://rentry.org/ExosphereDNSMITM

 

[SkullHex2]

If you've ever turned your machine on in OFW, before ever using CFW, while on a firmware higher than 4.1, then the nogc option is pointless, and in fact causes some people problems when booting with game cart inserted. Only people who are still convinced that a cold-boot CFW will come for 4.1 or lower, are worried about it. With that said, kip1patch=nogc is intended to be used when booting with stock=1 (for those concerned about this). Otherwise, it should be up in your global config in the form of

[config]
autonogc=1

There is a pretty detailed explanation of every one of these things on the front page of the repo. Not knowing this, is why I despise AIO packs.

Good to know. I suspected nogc was only useful when booting with stock=1, but I wasn't completely sure as that would mean you're either on the last firmware and can download games from eShop, or you can't use your Switch at all.. I think.
When you say “repo,” do you mean Hekate's?

 

[urherenow]

When you say “repo,” do you mean Hekate's?

Yes. But autonogc is the same thing as kip1patch=nogc. But it applies to all of your entries (unless you specifically use kip1patch on a boot entry, in which case it will use that, I think).

But again, if you've ever run your switch above fw 4.0 (I thought 4.1 before... dunno why that was stuck in my head), then there is no use for either. Personally, I always have it =0. I always have a cart in the slot, and don't want any surprise black screens.

 

[cmdwedge]

If you want to restore your prodkey.bin you can downgrade EmuMMC to 16.0.0 with Daybreak, then use Incognito_RCM to restore prodkey and then use Daybreak to upgrade EmuMMC back to 17.0.0

But you can also just use DNSmitm to block Nintendo servers. Then your switch will not crash even with a blanked serial.
https://rentry.org/ExosphereDNSMITM

That did the trick! Now boots and works in EmuMMC on 17.0.0, thanks so much for your help. Probably no reason to unblank the prodkey now anyway. My SysMMC remains clean and I still haven't revealed the key to Nintendo.

Cannot thank you enough for this!

 

[impeeza]

That did the trick! Now boots and works in EmuMMC on 17.0.0, thanks so much for your help. Probably no reason to unblank the prodkey now anyway. My SysMMC remains clean and I still haven't revealed the key to Nintendo.

Cannot thank you enough for this!

exaclty, you don need so far, has been explained a couple of times on the last posts.

 

[piek50]

I have updated to the latest Atmosphère, Hekate and sigpatches and everything worked fine like two weeks ago.
Now today i try to connect to the internet and im getting this. can someone give me some advice how to fix this? I'm using GFW on sysnan.

Edit :
after i delete the exosphere ini file the crash stops.
I have try the options on this website but i got crash again.
https://rentry.org/ExosphereDNSMITM

 

[petspeed]

I have updated to the latest Atmosphère, Hekate and sigpatches and everything worked fine like two weeks ago.
Now today i try to connect to the internet and im getting this. can someone give me some advice how to fix this? I'm using GFW on sysnan.

Edit :
after i delete the exosphere ini file the crash stops.
I have try the options on this website but i got crash again.
https://rentry.org/ExosphereDNSMITM

It's been explained so many times before
You need to use DNSmitm to block nintendo servers. Then the crash won't happen even with a blanked serial. Instructions are on the site you link to yourself

 

[piek50]

It's been explained so many times before
You need to use DNSmitm to block nintendo servers. Then the crash won't happen even with a blanked serial. Instructions are on the site you link to yourself

i had already done it a wile ago and i was gonna edit my post.
Thanks to reply.

 

[duckbill007]

You just need one more patch for nim module, that prevents this crash.

 

[eskirol]

Are new patches needed for 17.0.1?

 

[mathew77]

Are new patches needed for 17.0.1?

Nope, old one for 17.0.0 works well enough.

 

[impeeza]

Are new patches needed for 17.0.1?

Please READ the answer is exactly 4 post above yours

 

[eskirol]

Well sorry but 4 answers above I only see someone talking who updated hekate, ams and sigpatches but I don't see anything about 17.0.1

 

[gusklein]

Some updates not installing with 17.0.0 sigpatches. !7.0.1 needed,

 

[PagaN]

Some updates not installing with 17.0.0 sigpatches. !7.0.1 needed,

even on 16.1 all patches installing and working with last DBI

 

[linuxares]

Some updates not installing with 17.0.0 sigpatches. !7.0.1 needed,

Incorrect. They work fine since nothing changed with Atmosphere.
Plus it's a minor update, not a massive one that changed a lot of things in the system.

 

[gusklein]

Incorrect. They work fine since nothing changed with Atmosphere.
Plus it's a minor update, not a massive one that changed a lot of things in the system.

Splatoon 3 latest update not installing because sigpaptches. Rocket League latest update not installing because sigpaptches. Trying install on latest Tinfoil. "Convert to standard cripto" not working.

 

[linuxares]

Splatoon 3 latest update not installing because sigpaptches. Rocket League latest update not installing because sigpaptches. Trying install on latest Tinfoil.

Try using a better installer like DBI

 

[impeeza]

Splatoon 3 latest update not installing because sigpaptches. Rocket League latest update not installing because sigpaptches. Trying install on latest Tinfoil.

read last post, and use DBI to install legally acquired NSP or XCI files.

 

[gusklein]

I did the tests. The installation only works if done with DBI and doing a forced downgrade in encryption. Conclusion: It works by doing workarounds, but the existence and possible need for 17.0.1 sigpatches is real.