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

[Hayato213]

It is not a forwarder. It is a full NSP port. Other ports like Another Metroid 2 Remake (AM2R) or Sonic 1 and Sonic 2 SMS Remakes work flawlessly. Only port giving problems is Super Mario 64 HD v8 hotfix 2.

Then the problem might be Super Mario 64 HD v8

 

[Cer0_skydown]

Then the problem might be Super Mario 64 HD v8

Thank you people, you are the best!

 

[alcab]

Then the problem might be Super Mario 64 HD v8

Maybe. But I don't think so. In previous firmware and AMS it worked without problems using previous sigpatches. I tested it after applying the new sigpatches under firmware 18.1.0 and it stopped working.

 

[Hayato213]

Maybe. But I don't think so. In previous firmware and AMS it worked without problems using previous sigpatches. I tested it after applying the new sigpatches under firmware 18.1.0 and it stopped working.

the thing is each newer atmosphere build require new set of patches.

 

[alcab]

I know that. This port has been working properly for years under many firmware and AMS versions when the corresponding sigpatches were applied. Now it is giving exactly the same error as when no sigpatches are applied, or when sigpatches are a work in progress and are not working properly.
First thing I do after applying a new firmware and a new AMS version to my EmuMMC is testing these ports, because I know there might be issues with them. This is not the first time something like this happens.


In my opinion there could be a problem with the new sigpatches, but obviously I may be wrong and this might be an issue with the port.

Best regards.

 

[Hayato213]

I know that. This port has been working properly for years under many firmware and AMS versions when the corresponding sigpatches were applied. Now it is giving exactly the same error as when no sigpatches are applied, or when sigpatches are a work in progress and are not working properly.
First thing I do after applying a new firmware and a new AMS version to my EmuMMC is testing these ports, because I now there might be issues with them. This is not the first time something like this happens.


In my opinion there could be a problem with the new sigpatches, but obviously I may be wrong and this might be an issue with the port.

Best regards.

Probably the problem it is the forwarder, if other forwarder work fine, beside I wouldn't be in a rush to update when a new firmware come out.

 

[alcab]

As I said, this is not a forwarder. And I would like to add that I have not been in a rush to update. I updated an hour ago my EmuMMC and I can go back to previous firmware and AMS if I need to.
I'm just testing the new sigpatches under firmware 19.0.0 and AMS 1.8.0 and reporting the issues I have encountered.

In fact, I can say that this is the only problem I have encountered so far. Everything else is working flawlessly so I think I can report that it is safe to update right now.

Of course, some system modules for Tesla need to be updated, too (sys-tweak, mission control, sys-clk, saltynx or sys-patch...)

 

[Hayato213]

No, I have not been in a rush to update. I updated an hour ago my EmuMMC and I can go back to previous firmware and AMS if I need to.
I'm just testing the new sigpatches under firmware 19.0.0 and AMS 1.8.0 and reporting the issues I have encountered.

In fact, I can say that this is the only problem I have encountered so far. Everything else is working flawlessly so I think I can report that it is safe to update right now.

Of course, some system modules need to be updated, too.

The thing is to not rush to update when a new firmware come out. It seem like tinfoil doesn't work on firmware 19.0.0 as it use forwarder also.

 

[alcab]

Again, I didn't rush to update. I simply like to test things.
Tinfoil applet version works flawlessly. You just need to load it using the .nro file in the homebrew menu. I never use forwarders because sooner or later they always give problems and you have to rebuild them.

 

[Hayato213]

Tinfoil applet version works flawlessly. You just need to load it using the .nro file in the homebrew menu.

I'm talking about it forwarder, another one that is broken.

 

[Johnny Dunlop]

I think forwarders are just not working yet. I am also using latest firmware, latest atmosphere, latest patches and retroarch forwarders are no longer working for me. Retroarch and associated roms load fine via homebrew menu. I even generated new prod keys from sysnan and re-created the forwarders but same issue.

I guess we need to wait for forwarders to work.

 

[w350922439]

I updated atmosphere and hekate, and put impeeza's latest sign patches, but when I load emummc, it gives me the following error after 5 seconds:

In HOS 17.0.0 and after, blanking your PRODINFO using any method (exosphere/blanking PRODINFO on NAND) will cause a User Abort in the nim service. This repository has patch files that disable this abort, allowing you to use PRODINFO blanking on firmwares 17.0.0 and afterwards.

If you want to connect to wifi,you will enable DNSMiTm or use this exefs_patches to fix this error
https://github.com/fruityloops1/nim-prodinfo-blank-fix/releases

 

[alcab]

I'm talking about it forwarder, another one that is broken.

No, forwarders do not work and they need to be rebuilt for firmware 19.0.0.
But regarding Super Mario 64 v8 hotfix 2, as I said, I think this is not related to the forwarders issue. Super Mario 64 v8 hotfix 2 is a full port in NSP format.

Best regards, and have you all a good night.

 

[Johnny Dunlop]

No, forwarders do not work and they need to be rebuilt for firmware 19.0.0.
But regarding Super Mario 64 v8 hotfix 2, as I said, this is not related to the forwarders issue. Super Mario 64 v8 hotfix 2 is a full port in NSP format.

Best regards, and have you all a good night.

Is there any method yet to rebuild forwarders for 19.0.0? Thanks

 

[impeeza]

Is there any method yet to rebuild forwarders for 19.0.0? Thanks

yes access to the source code and build them using the latest devkitpro packages.

Try creating a new one using https://nsp-forwarder.n8.io/

 

[OLineGuy]

No, forwarders do not work and they need to be rebuilt for firmware 19.0.0.
But regarding Super Mario 64 v8 hotfix 2, as I said, I think this is not related to the forwarders issue. Super Mario 64 v8 hotfix 2 is a full port in NSP format.

Best regards, and have you all a good night.

if other homebrew nsps are working fine, gotta wait for a new build

 

[Johnny Dunlop]

yes access to the source code and build them using the latest devkitpro packages.

Try creating a new one using https://nsp-forwarder.n8.io/

I tried re creating the retroarch forwarder from that site actually and it didn't work. Is it supposed to work with fw 19 now?

I'll try looking into the devkitpro method although I have never done this before.

 

[impeeza]

I tried re creating the retroarch forwarder from that site actually and it didn't work. Is it supposed to work with fw 19 now?

I'll try looking into the devkitpro method although I have never done this before.

you can:

* downgrade to 18.1.0, because NO SOFTWARE NEEDS FW 19.
* Wait until the new set of forwarders will be created, that can take a lot.

 

[josete2k]

you can:

* downgrade to 18.1.0, because NO SOFTWARE NEEDS FW 19.
* Wait until the new set of forwarders will be created, that can take a lot.

Ahem...

https://gbatemp.net/threads/gui-for-nsp-forwarder-tool-for-12.588018/page-17#post-10516248


And Yes, the Sm64 nsp issue is the same that forwarder's...

 

[impeeza]

Ahem...

https://gbatemp.net/threads/gui-for-nsp-forwarder-tool-for-12.588018/page-17#post-10516248


And Yes, the Sm64 nsp issue is the same that forwarder's...

yeah, is the same problem for any Homebrew distributed as a NSP.

that's why most of the open source Homebrew is distributed as a NRO.