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

[dogtygr]

Very dirty hack. Man, you have PreProcessCapability function just for that purpose!

Yes indeed, you're correct!

 

[TomSwitch]

I'm using the latest version of Atmosphere and the latest sigpatches from this thread, unless you mean something entirely different in which case I don't know how to update those.

Using the word latest is shooting your own foot cause then nobody can help you when you actually were using the wrong one

Post automatically merged: Oct 19, 2024

I don't know if someone has already posted a solution for the nsp forwarders issues but since I haven't seen anyone mentioning the
FixDebugCapabilityForHbl() function I'll join in. I've also modified sys-patch and the IPS patch from MrDude but it seems like people have already made fixes so I don't think I need to address that.

Atmosphere has done something to bypass the debug_force_prod flag to its tool Hbl in order to avoid to recompile the tool via
FixDebugCapabilityForHbl (commit 7aa0bed869c7ed642d5503c6c80e3dc337bc56bd) where it basically forces the debug_force_prod to false. By adding this function everytime we run loadMeta this allows to add by default the debug_force_prod and it allows old nsp forwarders to work.

Here is the changes I've made (I've also removed the acidsigchk). The code could be improved though, we could for example check if the debug_force_prod exists and if not add this function but I think this can suffice for now. I also think that a ips can be made if people aren't already working on it I can do it.

check if your dmnt is still working. Currently the official one debug flags not set, you need to build one with it set or you can't cheat

 

[impeeza]

So this is tough. Do we keep the newest version, or do we revert to previous branch to have support for those old forwarders and the port of SM64? I do not like to loose the new added features and fixes AMS might have.

I think I will keep the latest version. And let's hope this small issues can be fixed in the near future.

You was advised to NOT UPGRADE your firmware until everything is stable. Now what is apre release Atmosphère you can downgrade to Firmware 18.1.0 and stop having issues

Very dirty hack. Man, you have PreProcessCapability function just for that purpose!

Excellent. Please do it and share with us, thanks

 

[TomSwitch]

So this is tough. Do we keep the newest version, or do we revert to previous branch to have support for those old forwarders and the port of SM64? I do not like to loose the new added features and fixes AMS might have.

I think I will keep the latest version. And let's hope this small issues can be fixed in the near future.

What new added features you think you are getting? Nintendo have maybe two total improvements since day 0. Folder for games and BT headset support. Otherwise you get stability downgrade all the time

 

[dogtygr]

You was advised to NOT UPGRADE your firmware until everything is stable. Now what is apre release Atmosphère you can downgrade to Firmware 18.1.0 and stop having issues



Excellent. Please do it and share with us, thanks

It is actually straight forward. Instead of using the function
FixDebugCapabilityForHbl like the idiot I was you can just update
PreProcessCapability to be like FixDebugCapabitlity.

I've made an IPS patch that calls Fixdebugcapability instead of preprocesscapability and it seems to work. I don't know the repercussions of doing that though

 

[TomSwitch]

It is actually straight forward. Instead of using the function
FixDebugCapabilityForHbl like the idiot I was you can just update
PreProcessCapability to be like FixDebugCapabitlity.

I've made an IPS patch that calls Fixdebugcapability instead of preprocesscapability and it seems to work. I don't know the repercussions of doing that though

I think functionally there is no difference as preprocesscapability seems to be a place holder that do nothing. Have you try to cheat yet. Working for you? I expect it to not work as dmnt currently don't have the debug flag set and this hack elevate games above dmnt. A solution is to fork dmnt ( a silly thing for just the debug flag ). Maybe dmnt's flag setting can also be patched?

void PreProcessCapability(util::BitPack32 *kac, size_t count) {
for (size_t i = 0; i < count; ++i) {
const auto cap = kac;
switch (GetCapabilityId(cap)) {
/* NOTE: Currently, there is no pre-processing necessary. */
default:
break;
}
}
}

 

[dogtygr]

I think functionally there is no difference as preprocesscapability seems to be a place holder that do nothing. Have you try to cheat yet. Working for you? I expect it to not work as dmnt currently don't have the debug flag set and this hack elevate games above dmnt. A solution is to fork dmnt ( a silly thing for just the debug flag ). Maybe dmnt's flag setting can also be patched?

I don't use any kind of cheat it will take time for me to set it up and test it but you can try it yourself if you already have something set up.

You can use this ips if you have kip loader activated in Atmosphere or you can use the patches.ini file by adding the values below (haven't tested it with hekate, beware!).

[Loader:A73B75768096EA90] .nosigchk=0:0x602A:0x1:01,00 .forcedebugprod=0:0x5f84:0x1:87,77 .forcedebugprod=0:0x5f98:0x1:82,72

 

[TomSwitch]

I don't use any kind of cheat it will take time for me to set it up and test it but you can try it yourself if you already have something set up.

You can use this ips if you have kip loader activated in Atmosphere or you can use the patches.ini file by adding the values below (haven't tested it with hekate, beware!).

[Loader:A73B75768096EA90] .nosigchk=0:0x602A:0x1:01,00 .forcedebugprod=0:0x5f84:0x1:87,77 .forcedebugprod=0:0x5f98:0x1:82,72

I am actually telling you the side effect. People who use you patch can't cheat anymore. The fix is easy just not elegant. (compile dmnt with flag set)

 

[dogtygr]

I am actually telling you the side effect. People who use you patch can't cheat anymore. The fix is easy just not elegant. (compile dmnt with flag set)

Makes sense, thank you for sharing!

Edit the patch actually forces the debug flag to true I don't know if this is what you were talking about

 

[batouttahell24]

Using the word latest is shooting your own foot cause then nobody can help you when you actually were using the wrong one

Post automatically merged: Oct 19, 2024

check if your dmnt is still working. Currently the official one debug flags not set, you need to build one with it set or you can't cheat

Okay, let me specify. Atmosphere 1.8.0 pre-release and the current beta sigpatches from the first post of this thread. I'm also on 19.0.0, so do I have the wrong version of anything? And if so, what versions should I get?

Post automatically merged: Oct 19, 2024

Also hekate 6.2.2 if you need to know my loader version.

 

[swampyballs]

Okay, let me specify. Atmosphere 1.8.0 pre-release and the current beta sigpatches from the first post of this thread. I'm also on 19.0.0, so do I have the wrong version of anything? And if so, what versions should I get?

Post automatically merged: Oct 19, 2024

Also hekate 6.2.2 if you need to know my loader version.

Atmosphere has had a silent release since the patches were posted, use the IPS tool which is posted on this forum by impeeza to make a new loader patch.

 

[batouttahell24]

Atmosphere has had a silent release since the patches were posted, use the IPS tool which is posted on this forum by impeeza to make a new loader patch.

Okay sweet, can you link to the post by them so I can grab the patch? And is it just as simple as putting the patch on the root of the SD card?

 

[lsp199308]

The repository only has the binaries, no source code.

https://github.com/borntohonk/Atmosphere

 

[AMANO9527]

But exefs patches are applied too.

If i use the latest files "impeeza" postet i get the "es7" "Unpatched.
If i use the files "w350922439" postet here --> https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-205#post-10517695" everything is fine.

I am using Firmware 18.1.0 | AMS 1.8.0-pre-c6014b533

I compared them and found the problem lies in
exefs_patches\es_patches\897C2CF2777B3A8845640C096933ACE61DD12272.ips.

When using the version from impeeza or Sigpatch-IPS-Creator V1.5.9, it shows Unpatched.
But when switching to the w350922439 version, it shows green as Patched.
Could you check this IPS patch? It should be the patch for Firmware 18.x.

 

[impeeza]

Okay sweet, can you link to the post by them so I can grab the patch? And is it just as simple as putting the patch on the root of the SD card?

The most recent version of Atmosphère 1.8.0 is "1.8.0 Prerelease-c6014b533" the one before that is "1.8.0 Prerelease-5717ea6c0"

Both set of patches are included since V3 sigpatches (current is V5) on https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10511757 you can check you SDMC:/bootloader/patches.ini file and at end you can see:

Post automatically merged: Oct 19, 2024

I am using Firmware 18.1.0 | AMS 1.8.0-pre-c6014b533

I compared them and found the problem lies in
exefs_patches\es_patches\897C2CF2777B3A8845640C096933ACE61DD12272.ips.

When using the version from impeeza or Sigpatch-IPS-Creator V1.5.9, it shows Unpatched.
But when switching to the w350922439 version, it shows green as Patched.
Could you check this IPS patch? It should be the patch for Firmware 18.x.

There is a version of ESFW19 patches what WILL NEVER be patched, the gurus find that patch at very start of FW 19 analysis, and later founded what that string is in code but never is executed so never get memory, hence never is patched. on the next release of SYS-Patch will be removed.

if you see ESFW19_2 patched you are ok.

 

[josete2k]

I compared them and found the problem lies in
exefs_patches\es_patches\897C2CF2777B3A8845640C096933ACE61DD12272.ips.

When using the version from impeeza or Sigpatch-IPS-Creator V1.5.9, it shows Unpatched.
But when switching to the w350922439 version, it shows green as Patched.
Could you check this IPS patch? It should be the patch for Firmware 18.x.

Well, I'm not a programmer or developer but as impeeza said, it seems that there is a function that calls another function.

The ips patches the first one and for that reason the second one did not run.

Sys-patch patches the second function, which obviously does not exist if you have used ips.

 

[batouttahell24]

The most recent version of Atmosphère 1.8.0 is "1.8.0 Prerelease-c6014b533" the one before that is "1.8.0 Prerelease-5717ea6c0"

Both set of patches are included since V3 sigpatches (current is V5) on https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10511757 you can check you SDMC:/bootloader/patches.ini file and at end you can see:
View attachment 465966

Post automatically merged: Oct 19, 2024

There is a version of ESFW19 patches what WILL NEVER be patched, the gurus find that patch at very start of FW 19 analysis, and later founded what that string is in code but never is executed so never get memory, hence never is patched. on the next release of SYS-Patch will be removed.

if you see ESFW19_2 patched you are ok.

I'm using c6014 for Atmosphere and I just ran your IPS patcher for "Loader" and "ES". Still didn't work and my patches.ini file just has "
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00"
in it.

Did I do something wrong or do I have to add those lines to make it work?

 

[impeeza]

I'm using c6014 for Atmosphere and I just ran your IPS patcher for "Loader" and "ES". Still didn't work and my patches.ini file just has "
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00"
in it.

Did I do something wrong or do I have to add those lines to make it work?

download and extract to the root of your SD Card

https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10511757

OVERWRITE ALL FILES.


also download and extract to the root of your sd card
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10519569

ORVERWITE ALL FILES.


THEN RESTART YOUR CONSOLE

 

[batouttahell24]

download and extract to the root of your SD Card

https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10511757

OVERWRITE ALL FILES.


also download and extract to the root of your sd card
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10519569

ORVERWITE ALL FILES.


THEN RESTART YOUR CONSOLE

Tried putting those onto my SD card with DBI and also tried it with putting the SD card into my computer, homebrew NSPs/forwarders still fail to launch but all of my games work just fine. sys-patch logs all show either an orange "Patched" or red "Unpatched". i have no idea

Post automatically merged: Oct 19, 2024

Note that DBI probably overwrites automatically, but I DID choose to overwrite files when I plugged my SD card into my PC.

 

[impeeza]

NSP FORWARDERS WILL NOT WORK UNTIL YOU CREATE AND INSTALL NEW ONES, PLEASE READ THE PREVIOUS POSTS

CREATE NEW ONES ON https://nsp-forwarder-git-fork-masagrator-main-tootallteam.vercel.app/
THOSE WILL WORK ONLY ON FW19 AND ATMOSPHÈRE 1.8.0