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

[impeeza]

So, updated to the latest firmware. Installed it. Updated to latest Atmosphere. Have latest fusee. However, when I boot into it using the jig, when I get to the home screen it has an error screen pop up after 3 seconds in purple/blue atmosphere screen saying error code: 2123-0011 (0x167b)

Followed by "an error occured" then a load of code.

Any idea what's causing this?

which atmosphere did you have before?

Post automatically merged: Apr 1, 2024

All sorted Thanks everyone

How did you sorted? leave to everyone wonder is no polite, and if anybody have the same issue will help them.

 

[dogtygr]

The IPS Patch Creator (not created by me) allows you to edit the database of patterns and offsets for search>


View attachment 429244
View attachment 429245

so you can upgrade or add the config manually.

Yes I know that's what Im saying if you made a software without the automatic stuff would nintendo be able to dmca it?

 

[jacobkoller]

Is DBI working with no issues on this new atmo/firmware?

 

[impeeza]

Is DBI working with no issues on this new atmo/firmware?

yes, why should no work?

 

[jacobkoller]

yes, why should no work?

I remember goldleaf has problems with every new update of the firmware/atmo. Nice to hear that DBI isn't effected.

 

[Blythe93]

Is DBI working with no issues on this new atmo/firmware?

Unless you run into an April Fools' Day joke, it should be working properly on the latest Atmosphere (1.7.0) and firmware (18.0.0).

 

[Supreme23]

Atmosphere still works with sig-patches if loaded via package3 and hekate. Or you can just use a modded fusee.bin such as this one that I compiled for the latest atmosphere which has ips kip patches support.

Thanks!

 

[Larsenv]

@impeeza how can you load sysnand with atmosphere with the latest version of hekate

 

[impeeza]

As far I know you can use a entry like this on your HEKATE_IPL.INI

{--- Custom Firmware ---}
{--- SYSNAND START---}
[CFW (SYSNAND)]
id=SYSNAND
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/atmosphere_hue_nobox.bmp
kip1patch=nosigchk

note the emummc_force_disable entry, that indicate to use the SYSNAND even if you have a configurated EmuNAND.

 

[TomSwitch]

Should I try dropping that file in the host folder then? Looks like this

# Block Nintendo Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendo-europe.com
127.0.0.1 *nintendoswitch.*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net

Post automatically merged: Apr 1, 2024

Or should I just wait for the next update?

If turning off wifi fix your problem you have four options

Host file
Don't turn on Wifi
Undo incognito
80DNS

 

[impeeza]

If turning off wifi fix your problem you have four options

Host file
Don't turn on Wifi
Undo incognito
80DNS

90DNS and/or Atmosphère's DNSMiTm

 

[Windsall]

Since the updates before this last one, has anyone gotten more 'USB connection lost' message when trying to install nsp files and such?

I dunno if another program would do better, been using Awoo still. I didn't like how dbi did things, sometimes it ended up with partly corrupted games.

 

[impeeza]

Since the updates before this last one, has anyone gotten more 'USB connection lost' message when trying to install nsp files and such?

I dunno if another program would do better, been using Awoo still. I didn't like how dbi did things, sometimes it ended up with partly corrupted games.

no me.

 

[ChaiusTheDark]

Help, i have Erista. how do i switch to Mariko?

 

[Hayato213]

Help, i have Erista. how do i switch to Mariko?

You need to get a new switch if you want Mariko.

 

[impeeza]

Help, i have Erista. how do i switch to Mariko?

Why do you mean about swith to Mariko?, Erista and Mariko are two revisions of hardware, are completely different consoles.

 

[RedColoredStars]

To start off with some context I am using both sys-patch and sigpatches.

Using either the sigpatches in this thread or ones that I made myself with Sigpatch IPS Creator, the log in the sys-patch overlay displays the 'ctest' section in green. Which means it is being patched by sys-patch and that the ctest sigpatch is being ignored or is not working. If using both sigpatches and sys-patch, it is supposed to be orange. Meaning that it is already patched by sigpatches.

Now, if I use the sigpatches from the three cats site, the 'ctest' section in the sys-patch log turns orange as it is supposed to. So what is going on here? Just swapping out one single file in atmosphere\exefs_patches\nfim_ctest with the one from the three cats sites works. So what is being done differently with their ctest patch as opposed to the one here and the one I create? Why does theirs work properly but not the others?

Also, when I create my own patches the following are present in atmosphere\kip_patches\fs_patches:
1E2C64B1CCE27824999B9DC2276701696C9569CBC607501D65CC1386CE485B65.ips
795F5A5EB0C6779EF2D5763E0052B3FB605C796869FE268F0C58714861EFCAEC.ips

Those two are also included in the sigpatches from here, but neither are in the sigpatches from three cats. I wonder why. It's weird that ONLY the three cats ctest sigpatch works properly, but that they're missing those two files the others have.

So.... ?????????

@impeeza @Blythe93

 

[josete2k]

Same question.

 

[linuxares]

Well maybe he use a proper method making the ctest patches and these from Mr Dude's software isn't good?

 

[SylverReZ]

Well maybe he use a proper method making the ctest patches and these from Mr Dude's software isn't good?

Too bad that MrDude was banned, so he cannot give us an update.