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

[Hayato213]

They were necessary to install it, otherwise the game was stuck on a black logo with infinite loading.

Your video show no game installation, just loading a game, that is what ES patches are for.

 

[goma341]

I introduced it last week, before today's new fs patch we could already (via fss0 config only) install games, the old installed games didn't work before today.

thanks i'll check it out

 

[impeeza]

I just updated hekate and atmosphere but now my digital games don't work, only physical games. Not sure what I did wrong.

you need latest set of patches.

 

[Zoria]

Sigpatch ES, FS, Loader compatible with fusee and fss0 for firmware 17.0.0)
I specify that even the forwarder (it depends on the forwarder of course) works.

As for the rec, yes I didn't rec the installation, only the end because I didn't think it would work when I did my tests.

 

[mrdude]

you need latest set of patches.

IPS patcher updated on github now. I expect sys-patch will be updated in a little while if it's not already.

 

[impeeza]

IPS patcher updated on github now. I expect sys-patch will be updated in a little while if it's not already.

@mrdude, so the scene now get all the needed patches? I just see the update on the github about https://github.com/ITotalJustice/sys-patch/issues/5#issuecomment-1777128671 I didn't understand all of it but was exciting.

 

[Deleted member 413168]

IPS patcher updated on github now. I expect sys-patch will be updated in a little while if it's not already.

its ready

 

[mrdude]

its ready

Good stuff, well that was a pain in the arse. I hope you don't delete that comment on your github as it has lots of valuable info in it, now we know this new fs patch location we can try to figure out how it was found, probably for the next few updates the pattern will change a little by a few bytes but at least we rougly know where to look.

 

[Deleted member 413168]

Good stuff, well that was a pain in the arse. I hope you don't delete that comment on your github as it has lots of valuable info in it, how we know this new fs patch location we can try to figure out how it was found, probably for the next few updates the pattern will change a little by a few bytes but at least we rougly know where to look.

I'd archive some important stuff if i were you, just in case they decide to dmca me again. But yes, i will keep the thread, it's very valuable.

 

[impeeza]

Using the great tool from @mrdude here are the most recent set of patches all on one package, Firmware from 1.0.0 to 17.0.0 and Atmosphère from 0.11.0 to 1.6.1 prerelease

@ShadowOne333 please update the OP.

Post automatically merged: Oct 24, 2023

What a journey!!! thanks you the geniuses of the scene!!

 

[ShadowOne333]

Using the great tool from @mrdude here are the most recent set of patches all on one package, Firmware from 1.0.0 to 17.0.0 and Atmosphère from 0.11.0 to 1.6.1 prerelease

@ShadowOne333 please update the OP.

Post automatically merged: Oct 24, 2023

What a journey!!! thanks you the geniuses of the scene!!

OP updated with the latest patches!
Thank you for all your work @mrdude , @TotalJustice and @impeeza

 

[mrdude]

OP updated with the latest patches!
Thank you for all your work @mrdude , @TotalJustice and @impeeza

No need to thank me, I didn't do anything - the people that found the patch locations did all the hard work.

 

[EchoStorm]

working great, thanks

 

[Windsall]

Wonder requires 16.0.0

I played multiple hours of it on lower firmware, before updating hekate and atmosphere.

I think the problem is patch loader, generate new loader patch with latest atmosphere

I don't think I know how to do that.

you need latest set of patches.

Weird that I'd need the sigpatches 'after' playing it on older ones. I guess I could do that too if I wanna play it, but I might just wait til for the v17 sigpatches now.

 

[impeeza]

I played multiple hours of it on lower firmware, before updating hekate and atmosphere.



I don't think I know how to do that.



Weird that I'd need the sigpatches 'after' playing it on older ones. I guess I could do that too if I wanna play it, but I might just wait til for the v17 sigpatches now.

they are already released.

 

[Windsall]

they are already released.

I just saw xD. I guess I don't need workarounds now... Though still good to try to understand things for if this happens again in the future.

 

[vctvinchester77]

After connecting to Wi-Fi, I saw this error

 

[impeeza]

After connecting to Wi-Fi, I saw this errorView attachment 400940

https://github.com/Atmosphere-NX/Atmosphere/issues/2215



https://github.com/Atmosphere-NX/Atmosphere/issues/2208

 

[ShadowOne333]

https://github.com/Atmosphere-NX/Atmosphere/issues/2215



https://github.com/Atmosphere-NX/Atmosphere/issues/2208

Is that crash related to people that have blanked out their serial number with Atmos alongside the Switch trying to connect to a WiFi network on 17.0.0?

 

[impeeza]

Is that crash related to people that have blanked out their serial number with Atmos alongside the Switch trying to connect to a WiFi network on 17.0.0?

yeah if you clean your product info and go online your console crash. even crash before start HOS. no matter is you did use stratosphere.ini or that Payload. you need to restore your prodinfo to the original state.

With this big N give a big slap to anybody who recover from a damaged NAND and the ones trying to stay anonymous.