Last edited by BigOnYa,
And new Atmosphere also that go with obv....
https://github.com/Atmosphere-NX/Atmosphere/releases
With mesosphere means that it has a custom kernal made by Sciresm while without mesosphere means that it uses the defualt Nintendo kernal. For the end user, both versions feel pretty much the same. Eventually the non-mesosphere version will be removed.what's the difference between "without mesosphere" and with?
How are you booting exactly?Hi all,
I have a major issue with these sigpatches, it is the first time I have any issue in the Switch custom firmware world, and I've started 2 years ago in March 2019!
My working status was with FW 10.x with AMS 0.14.x or 0.15 and their Hekate Sigpatches.
I prepared the SD card with package taken from SDSetup (AMS 18.1 + hekate 5.5.4v2). I prepared the firmware folder with 11.0.1. I downloaded these sigpatches and replaced the files on the SD card as usual. Note: i basically delete everything but the Nintendo and the switch folders, put the newest SDSetup files, replace the Sigpatches files, make the flags folder/file for firmware update, check/replace the homebrews one by one in the switch folder.
First weird thing: as soon as I pushed the Hekated 5.5.4 included in the SDSetup download I immediately had a message about "old nyx gui. there will be dragons", which is the first time ever I saw this message.
I booted CFW (sysnand) as usual, everything worked, also games played, so I upgraded the firmware using Choi.
Once the process completed, it asked to reboot and I'm back to Hekate (still with the dragons message). I launched again CFW (sysnand) but this time nothing starts, just black screen.
After some failed attempts, I restored the SDSetup AMS, thus basically reverting all the sigpatches files (atmosphere+bootloader). No more "dragons" message as soon as I pushed Hekate. And now the CFW boots, but of course I don't have sigpatches!
EDIT:
I've tried the Sigpatches for 0.18.1, hekate version, from here:
https://github.com/ITotalJustice/patches/releases
No "dragons" error and the CFW boots correctly, but the only game I attempted to start did not launch and is now corrupted
EDIT 2:
I noticed ITotalJustice patches do not inlcude a customized hekate_ipl.ini. By adding the two properties kip1patch=nosigchk and atmosphere=1 to the default hekate config now the games boots correctly!
So summarizing:
With sigpatches on this thread:
- Hekate 5.5.4v2 shows dragons error
- 0.14.x+10.x boots from Sysnand and nsp installed games plays correctly
- 0.18.1+11.0.1 won't boot
With ITotalJustice hekate sigpatches:
- 0.18.1+11.0.1 boots and, applying the correct hekate_ipl.ini config the nsp installed games boot correctly.
How are you booting exactly?
Through fusee-primary or fusee-secondary?
This is important.
The issue that I think could be the culprit, will most likely be the IPS patches directly, and not the patches.ini from Hekate itself.
Also, I don't think the hekate_ipl.ini file that is provided in the pack has anything wrong with it, since it's just settings.
What differences are there between the hekate_ipl.ini that worked and the one that didn't?In both cases I'm using fusee secondary.
With ITotalJustice it was just a metter of fixing the default hekate_ipl.ini config, adding the parameters for sigpatches, but CFW (sysNAND) boots and installed NSP works.
With the sigpatches on this thread instead, as soon as I push Hekate "5.5.4v2" (name found on SDSetup) I have the "dragons" warning and, with the config already included in this sigpatches package here, the CFW (sysNAND) do not boot, just black screen.
What differences are there between the hekate_ipl.ini that worked and the one that didn't?
It could be related to a mismatch of Nyx, but I am not sure.Nothing in the CFW(sysNAND) boot part as I copied the config from the package here to the default hekate one, as ITotalJustice package do not include hekate_ipl.ini.
The differences are in the initial part:
autohosoff=1
bootwait=3
updater2p=0
But as I said, with the sigpatches here I immediately have the "dragons" warning before Hekate starts.
Could be related to the hekate payload used? SDSetup calls it "5.5.4v2", I image is "hekate v5.5.4 & Nyx v1.0.1" as there was a previous "hekate v5.5.4 & Nyx v1.0.0".
It could be related to a mismatch of Nyx, but I am not sure.
Do you have an image of the error?
Ah yes, it's an error with Nyx not being the correct version.The message showing up is the one in the original post on this thead:
https://gbatemp.net/threads/bootloader-dragons-error.561914/
Later, starting CFW(sysNAND), just a black screen.
I get my sigpatches from AIO Updater. Is there any advantage in getting them from these threads other than getting them sooner?
Gotcha! Thanks a lot. I'm still learning and you were very helpful.AIO Updater get the patches from ITotalJustice repo and that repo is always first with the updates actually before the tools to make patches ourselves the OP was getting the patches for this thread from that same repo so better stick with the AIO Updater
Then, I can launch already installed backups perfectly with no problems but any game (even older ones like Link's A.) that I try to install with goldleaf and quark says NCA invalid, sigpatches missing or too old version.