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

nabelo · 2024-10-18T15:49:26+0100

impeeza said:
working on them

Post automatically merged: Wednesday at 4:48 PM

Happy June 15th for everyone!!

with this great day also comes the new set of patches.

Any idea why syspatch is saying "es7_FW18-19" is "unpatched" with those files?

impeeza · 2024-10-18T15:53:05+0100

Fellow tempers The most recent version of IPS Patch Creator is out, IPS Patch Creator 1.5.9, with support for ANY FIRMWARE and Atmosphère is here:

https://gbatemp.net/download/ips-patch-creator-1-5-9.38850/

Please do not bitching about blah blah blah or bleh bleh bleh, if you like use it, if you don't like, do not use it.

nabelo · 2024-10-18T15:56:16+0100

w350922439 said:
first test-pre is:
#Loader Atmosphere-1.8.0
[Loader3FD950603AECC4D]
.nosigchk=0:0x602A:0x1:01,00

this new released pre is:
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00

and also your must add new loader file to atmosphere\kip_patches\loader_patches

If i use the files from this post syspatch says "es7_FW18-19" is "patched".
So i'll guess there is something wrong or missing in the lates files from @impeeza

josete2k · 2024-10-18T16:32:36+0100

nabelo said:
If i use the files from this post syspatch says "es7_FW18-19" is "patched".
So i'll guess there is something wrong or missing in the lates files from @impeeza

Another build

nabelo · 2024-10-18T17:15:50+0100

josete2k said:
Another build

something has definitely changed

“es7_FW18-19” is now displayed as "patched", but now suddenly "es7" is set to "unpatched" which was not the case before...

josete2k · 2024-10-18T17:21:10+0100

nabelo said:
something has definitely changed

“es7_FW18-19” is now displayed as "patched", but now suddenly "es7" is set to "unpatched" which was not the case before...

es7 and es7_FW18-19 are the same.

But es7_FW18-19 shouldn't be there...

How are you updating your sys-patch? MTP?

Do you update both, sysmodule and ovl?

nabelo · 2024-10-18T17:42:02+0100

josete2k said:
es7 and es7_FW18-19 are the same.

But es7_FW18-19 shouldn't be there...

How are you updating your sys-patch? MTP?

Do you update both, sysmodule and ovl?

I'll always use the USB mode in Hekate to access my SD.
This is how it looks like if i boot atmo via fusee:

And this is how it looks like if i boot via hekate with patches.ini:

Post automatically merged: 32 minutes ago

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.

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

Active Member

¡Kabito!

Active Member

Well-Known Member

Attachments

Active Member

Well-Known Member

Attachments

Active Member

Similar threads

Popular threads in this forum