- Status
Do these patches work with Stock Atmosphere 12.0 FW 10.0.0/1 booted from Hekate? The other patches say fusee primary I guess I boot from fusee secondary and don't know how else to boot Atmosphere
Sigpatch Installer has now been released! Sigpatch Installer is an easy to use application to automatically download the correct FS and ACID signature patches for the atmosphere/firmware version installed on your Switch. It will also setup the Hekate configuration file for you, and reboot into Hekate after setup.
is it ONLY for kosmos, and doesn't support the fusee-primary sigpatches if you want to actually use atmosphere without that bs?
It's currently only for Atmosphere + Hekate, which is the same as Kosmos.
I just installed Kosmos 15.6, ran Sigpatch Installer, and it worked just fine on my Switch with firmware 10.0.1.
Right, I understand what you mean. But I use Atmosphere + Hekate with a direct fusee-primary payload option instead of fss0, and you're saying that setup won't be supported. Got it
Yea not currently, I am able to port my Hekate patches over to Atmosphere IPS patches, and I will probably support fusee-primary at some point. However Just for the time being I wanted to get the Sigpatch Installer out.
This worked, also some games I had trouble installing with Goldleaf due to patches are now working. Thanks man!
Please do, especially with the new requirements for loader patch (whether Kosmos or fusee-primary) requiring an update for each Atmosphere update, the hbmenu can still launch and you could provide an updated patch set for both sets of users. Would be much appreciated!
I'm sure you know, but fusee-primary patches are located at https://gbatemp.net/threads/atmosphere-patches-es-fs-and-loader-fusee_primary-only.562812/
Hi sir, tq for sharing the same problem, when you not using that Line, and your switch can boot up..how about thr sigpatches? Any problem for install new games like trials of mana and animal crossing?
I never tried only 1 Line actually, if i let kips folder and everything else at my SD, and not using two Line, i still got problem with "sigpatches is too low" >.<
--------------------- MERGED ---------------------------
Hi sir, thank you for the sharing
Sorry i don't know which patches i must download..
What i must to do?
0. Firmware 10.0.1
1. Kosmos 15.6
2. Upgrade atmosphere 0.12.0
3. Put Sigpatches HarukoNX
4. It works
Or
0. FW 10.0.1
1. Kosmos 15.6
2. Stay at atmosphere right now
3. Download (which patch sorry?)
4. Put Sigpatches HarukoNX
5. Works?
Thank you
Is there a reason why Kosmos uses fusee_secondary?
Wouldn't it be easier to provide the same patches as the ones for fusee_primary and a hekate_ipl.ini to launch atmosphere with fusee_primary? Or to convince Kosmos devs to do that change in the hekate_ipl.ini they provide.
That way there would only be one set of patches for every configuration.
To All & @HarukoNX
Thank you for the explanation! I tried download atmosphere 0.12.0 and put into my SD with fusee also, and it works like charm!
1. Use kosmos 15.6
2. Use patches from first page
3. Use atmosphere 0.12.0
4. Fusee primary ( i don't know it is necessary or no, please help)
5. Sigpatch installer from first page
Works..i can install Animal Cros and working all of the games!
Update : But after installed Animal Cross, suddenly my Goldleaf broken..it transform into grey button, and if i press..BSOD atmosphere >.<
Thank you for the explanation! I tried download atmosphere 0.12.0 and put into my SD with fusee also, and it works like charm!
1. Use kosmos 15.6
2. Use patches from first page
3. Use atmosphere 0.12.0
4. Fusee primary ( i don't know it is necessary or no, please help)
5. Sigpatch installer from first page
Works..i can install Animal Cros and working all of the games!
Update : But after installed Animal Cross, suddenly my Goldleaf broken..it transform into grey button, and if i press..BSOD atmosphere >.<
i completely agree
fusee-secondary is unnecessary, but apparently kosmos will keep doing it ad infinitum
The reason why they do it, is because it is the only way to have sysnand and emummc entries on boot. Chainloading fusee primary will always boot emummc, unless the emummc.ini is changed. Via fusee secondary, they can choose whether sysnand or emummc should be booted, and then give you some nice booting options when running Hekate. But still, not much a need for that: they could just provide a emummc entry (via fusee primary) and a "stock" entry (via fusee secondary, which does not require any patches for stock) and let people boot emummc and stock sysnand.
The only catch is that there would be no way to boot sysnand with CFW and use fusee patches, as disabling emummc on boot requires fusee secondary, as I explained. This can be solved by using some homebrew that let's you flip the config in emummc.ini, reboot to hekate and choose the emummc entry (which chainloads fusee primary, and then will load sysnand CFW this time).
That is why I still believe booting directly with fusee primary, bypassing Hekate completely, and using a emummc swapper homebrew is the simplest solution. No burned fuses, no messing up with fusee secondary, and boot whatever you want. The catch here is that with fusee primary you can only either boot in cfw sysnand or cfw emummc. Booting stock sysnand requires shutting down the Switch and booting it normally (with Nintendo's official bootloader), which burns fuses which (i still need to understand why) seems to be a concern for many. Even CTCaer, the author of Hekate, just burns fuses without worrying.
However, booting sysnand with cfw (at least on my side) does not lead to any ban, as long as you don't do anything illegal, and just use your switch normally. Been doing it for two years now, and still buying games from the eshop. So, one can use sysnand with CFW as their "stock" sysnand for non homebrew related stuff.
Of course, if you go online (even with emummc) and download games illegally with hbg shop, your emummc (and thus your sysnand since one is a copy of the other) will likely be banned. You might use incognito or Dns, but it is not clear whether they really help.
So, my suggestion is just use the fusee primary payload with your RCM payload sender, boot whatever the emummc.ini dictates and just flip the config with homebrew if you want to move from emummc to (CFW) sysnand, and vice versa.
However, if booting stock sysnand without burning fuses is important for you, then use Hekate, and just change the hekate_ipl.ini as I suggested above (this is also explained in this tutorial). In both cases, you can then use the fusee primary patches, when on emummc.
Last edited by ::Phoenix::,
I realy dont understand the fuss about the .ips patches we "need" for fusee-primary.
Atmosphere without hekate (fusee-primary) is supporting loading .kip files to.
Just put the "loader.kip" @HarukoNX is providing into "\atmosphere\kips\" and get rid ot the "\atmosphere\kip_patches\loader_patches" folder (if you use the loader.kip you can delete the "loader_patches" folder because we dont need the .ips patches then).
But remember to also use the ES and FS patches. We just dont need the .IPS Patches for loader if we use the .kip file!
I think a problem in using kips (regardless of Atmosphere support for that) is that Atmosphere might not boot properly if there are changes to the loader module in a new release, and loader.kip is not updated accordingly. With ips patches, we can decide to which "revision" of loader to apply them, by using the hash of the loader module in the name of the ips (this is also why we can safely copy paste patches for FW 2.0.0 through 10.0.1, without having issues). Don't think something like this is possible with a .kip (as it fully replaces the loader module with HerokuNX's fork). Then, with ips the system would at least boot, when a new release of Atmo comes out, but the loader patches are not yet up to date, which is again, another good reason to not use Hekate with fusee_secondary.bin to boot CFW with patches, and rather use ips patches with fusee_primary.
Last edited by ::Phoenix::,
First off I would like to thank the hard work of Joonie, and I'm sad to see them leave the Switch scene. This is simply just a continuation of their work. I have taken their FS patches and got them working without a custom version of Hekate. I've also forked Atmosphere to remove the acid signature check from the loader service. My repository does not include ES patches, as I personally don't have any use for them. These patches work perfectly for installing backups of game cards, and homebrew NSPs. If you want ES patches you can find them on SDSetup along with my patches.
Download Sigpatch Installer: https://github.com/HarukoNX/Sigpatch-Installer/releases/latest
Download: https://github.com/HarukoNX/Atmosphere/releases/latest
SDSetup: https://sdsetup.com/console?switch
(Just to help SDSetup I've attached a zip file that contains all the patches for the time being.)
Hi guys, I have install the Slgpatch installer
conect Switch on internet
Launch Slgpatch
Selct Emummc
From hakate launch Emummc
But no way I have the "!" on some game like Zelda breath of the wild or Puzzle quest.
I have firmware 10.0.0 FW e AMS 0.12.0 E can y help me pls
- Status
Similar threads
-
BigOnYa
-
Xdqwerty
what are you looking at? -
K3Nv2
-
OctoAori20
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
OctoAori20:
I've been fighting with Windows 10's laughably awful Bluetooth bs trying to connect my Switch Pro Controller to the computer lol
-
-
-
