Hi everyone!

I noticed lots of people are very confused how they should update their patches... Kosmos patches? Hekate Patches?! Atmos patches?!

As asked by some users, here you have my set up and this simplifies everything.

This is very simple tutorial on how to boot Vanilla Atmosphere via Hekate and use the Normal patches from the new thread from our friend @Raugo.
You just need to do this once. Everytime a new release is out, you just need to update Atmos files + your patches from Here

Note:
This new patches thread replaces the no-more-updated old thread well known as "Sweet Patches".

First, lets understand:

1. Hekate comes with this folder structure:

SD:\bootloader this folder have 4 sub-folders and no files.

2. The 4 sub-folders are:

SD:\bootloader\ini this folder is empty
SD:\bootloader\payloads this folder is empty
SD:\bootloader\res this folder have the default icons (resources)
SD:\bootloader\sys this folder have system files (don't mess with them!)

Then, lets configure Hekate to boot vanilla Atmosphere (+ Normal patches) and forget about those Hekate/Kosmos patches:

1. Let's create the main configuration file:

Create a new file hekate_ipl.ini inside bootloader folder:

SD:\bootloader\hekate_ipl.ini

Note:
If you are a Windows user, be careful with the extension of the file. Google "how to view extensions for know file types".

2. Inside this file you can copy/paste this text:

[config]
autoboot=1
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1

{------- Launch -------}
[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/icon_atmosphere.bmp

[Horizon]
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_horizon.bmp

3. Then, you just need to put fusee-primary.bin inside payloads folder like this:

SD:\bootloader\payloads\fusee-primary.bin

4. You can create your own customized icon for Atmosphere and Horizon and put them on the res folder like this (You will have to learn how to create this BMP files or use the default ones, renaiming their names):

SD:\bootloader\res\icon_atmosphere.bmp
SD:\bootloader\res\icon_horizon.bmp

5. You can also create your own bootloader screen and put it here (You will have to learn how to create this BMP file):

SD:\bootloader\bootlogo.bmp

And that's it! This simple configuration will let you:

inject Hekate ----> See your custom bootlogo ----> Boot Vanilla Atmos + Normal Patches

and forget about Kosmos/Hekate patches!

If you press Vol - button while injecting, you can go to Hekate menu and check you configurations.
You can boot Atmosphere and Horizon.

Feel free to ask your questions.

 

[Corgano]

Try using Awoo (noir fork) or something instead.

This is what I'm doing for now. Only reason i really keep tinfoil around is installing updates / DLC for games i installed to the nand from gamecart.

 

[Broduskii]

Using this setup I was able to get standard atmosphere running and run all my games - sweet
When i start tinfoil it complains about hekate being on my sd, even if it wasn't used to start atmosphere. Any idea how to get tinfoil to stop being a bitch about having hekate even when not used?

Does it just look for the boot folder or something? I'm not sure how its detecting it.

 

[Corgano]

I'm not sure either. What I heard was it looks for a patches.ini - which I don't have - and kip patches, which i have no idea where or what these are.

 

[Broduskii]

I'm a little confused as to which patches we should to be using ?

 

[Itsuki235]

I'm a little confused as to which patches we should to be using ?

Which patches depend on which OFW version you are using <10.0 (does not require loader_patches) or >= 10.0 (requires either loader_patches or SD:/atmosphere/kips/loader.kip) and how Hekate is loading Atmosphere, either directly through payload= as in the OP or indirectly via "fss0=" method that Kosmos is configured to use by default.

Here are some links to the patches: https://gbatemp.net/threads/fixed-cant-boot-anymore-after-updating-atmosphere.563549/#post-9032069

So which ones you need are sort of for you to figure out based upon your OFW version and Atmosphere loading style.

If you don't want to bother with patches anymore, there is this project call NeutOS which is an Atmosphere fork that has the patches baked into the boot process, along with some anti-Kosmos code.

Then the SD:/bootloader/hekate_ipl.ini file would have a line that looks just like the one in the OP but pointing to the fusee-primary from NeutOS.

Try using Awoo (noir fork) or something instead.

What is the point of the Noir fork? It does not list any improvements, only that they made the default theme worse.

Does it have any important features or bug fixes compared to the mainline Awoo?

 

[Broduskii]

I think i figured it out


I deleted my atmosphere , bootloader and sept folders.
I downloaded Atmosphere 0.12.0 And Hekate , as well as these patches

my hekate_ipl.ini looks like

[config]
[config]
autoboot=1
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=1
autonogc=1
updater2p=0
{------ Atmosphere ------}
[Atmosphere emuMMC]
payload=bootloader/payloads/fusee-primary.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emu_boot.bmp
{}
[Atmosphere SYS]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

I am able to use the Hekate payload to boot into my emuMMC and use tinfoil without issue.
I did also replace the reboot_payload.bin with Hekate's.
Its working for me but i'm not sure if im doing anything wrong.

 

[Itsuki235]

I think i figured it out

I am able to use the Hekate payload to boot into my emuMMC and use tinfoil without issue.
I did also replace the reboot_payload.bin with Hekate's.
Its working for me but i'm not sure if im doing anything wrong.

That looks good so far. Consider deleting the sysnand Atmosphere option if you do not plan to use it. So far that config will work for <=9.2.0. If you ever upgrade to >= 10.0.0, then be sure to install SD:/atmosphere/kips/loader.kip from here:
https://github.com/HarukoNX/Atmosphere/releases

 

[Broduskii]

That looks good so far. Consider deleting the sysnand Atmosphere option if you do not plan to use it. So far that config will work for <=9.2.0. If you ever upgrade to >= 10.0.0, then be sure to install SD:/atmosphere/kips/loader.kip from here:
https://github.com/HarukoNX/Atmosphere/releases

I'm guessing that Kip folder is the main issue with tinfoil on >= 10.0.0?

I kept my emuand on 9.20, and have updated my sysnand to 10.0.0.

I think my only issue here is that i do use sysnand Atmosphere to update my firmware, backup saves and use Emuiibo (I need Lucky in AC).

If I use the kip folder then tinfoil wont let me proceed unless it deletes said folder? Maybe ill just keep a copy on the sd and copy it with goldleaf after i use tinfoil.

 

[Itsuki235]

If I use the kip folder then tinfoil wont let me proceed unless it deletes said folder? Maybe ill just keep a copy on the sd and copy it with goldleaf after i use tinfoil.

Horizon 10.0.0 moved signature verification to a "loader" module that made Atmosphere implement a "loader" sysmodule to replicate the functionality. So OFW 10 requires some way to patch that module.

The most direct way (and least error prone) is to use that .kip in the SD:/atmosphere/kips folder, but you can instead use the loader_patches (extracted from neutOS) and apply them to vanilla atmosphere to make tinfoil work. Those loader_patches can be obtained from here: https://gbatemp.net/threads/atmosph...fusee_primary-only.562812/page-4#post-9028710

 

[Broduskii]

Horizon 10.0.0 moved signature verification to a "loader" module that made Atmosphere implement a "loader" sysmodule to replicate the functionality. So OFW 10 requires some way to patch that module.

The most direct way (and least error prone) is to use that .kip in the SD:/atmosphere/kips folder, but you can instead use the loader_patches (extracted from neutOS) and apply them to vanilla atmosphere to make tinfoil work. Those loader_patches can be obtained from here: https://gbatemp.net/threads/atmosph...fusee_primary-only.562812/page-4#post-9028710

Thank you so much i understand this a little more now !

 

[Corgano]

What is the point of the Noir fork? It does not list any improvements, only that they made the default theme worse.

Mostly just preference. Personally I'd prefer they add a cheat code for tits out, but that's just me.

 

[Itsuki235]

Mostly just preference. Personally I'd prefer they add a cheat code for tits out, but that's just me.

Same. But at least you can change the foreground image yourself using photoshop and placing images at SD:/switch/Awoo-Installer/awoo_inst.png and SD:/switch/Awoo-Installer/awoo_main.png

 

[KeoniAzugon]

I would like to ask for clarification on SysNand vanilla Atmosphere chainloading and EmuNand chainloading settings with Hekate.
My personal setup is through SysNand (Self-Banned cause the switch was bought prehacked with AutoRCM on. No clean nand backup so don`t want to risk an actual ban.)
Then there's my siblings Setup with EmuNand for cfw and SysNand with OFW for online play.

personally enjoyed ReiNX and switching to Atmosphere since 9.0 and worst still with 10.0, there is a lot of scattered information.

 

[DCMaxxx]

[...] My personal setup is through SysNand (Self-Banned cause the switch was bought prehacked with AutoRCM on. No clean nand backup so don`t want to risk an actual ban.) [...]

Just so you know, I bought a Switch with the same setup (CFW on SysNAND), no NAND backup, might have been online on CFW for what I know.

I made a NAND backup just to be safe (with the CFW on), then I factory reset it using Haku33, re-made a clean NAND backup, and re-installed a CFW on emuNAND.
Everything works like a charm, I'm using sysNAND online everyday without any issue.

I know I risked (and might still risk) a ban if Nintendo kept some logs or whatever, but since you can't use your Switch online no matter what, I'd try that if I were you :-).

Have a nice day !

 

[KeoniAzugon]

Just so you know, I bought a Switch with the same setup (CFW on SysNAND), no NAND backup, might have been online on CFW for what I know.

I made a NAND backup just to be safe (with the CFW on), then I factory reset it using Haku33, re-made a clean NAND backup, and re-installed a CFW on emuNAND.
Everything works like a charm, I'm using sysNAND online everyday without any issue.

I know I risked (and might still risk) a ban if Nintendo kept some logs or whatever, but since you can't use your Switch online no matter what, I'd try that if I were you :-).

Have a nice day !

I did think about it since a dirty reformate was done on this Switch the moment it was in my hands. Coming from the 3ds scene, i had fun messing with Emu and Sys nand to this day. Thanks for the tip and recommendation of Haku33.

 

[alvpf]

Just so you know, I bought a Switch with the same setup (CFW on SysNAND), no NAND backup, might have been online on CFW for what I know.

I made a NAND backup just to be safe (with the CFW on), then I factory reset it using Haku33, re-made a clean NAND backup, and re-installed a CFW on emuNAND.
Everything works like a charm, I'm using sysNAND online everyday without any issue.

I know I risked (and might still risk) a ban if Nintendo kept some logs or whatever, but since you can't use your Switch online no matter what, I'd try that if I were you :-).

Have a nice day !

Dear friend, as you helped another friend with your tip, I was hoping you (or anyone here!) could help me too!

I installed cfw (Atmosphere) on a new and clean Switch (after making a clean NAND backup with Hekate) last year, before Hekate made it possible to use EmuNAND. I have been using my Switch booting Atmosphere directly through tegraRCM since then. Now I'm thinking about joining the EmuNAND wagon party to be able to play original cartridges online on a clean SysNAND too.

Can you tell me how should I proceed? Should I restore my original NAND backup, simply create an EmuNAND with Hekate and install Atmosphere there? I fear that I can mess something up as I used incognito (and right now, my Switch has no serial number in the settings... should I restore that before everything?), kefir to make a fake Nintendo Account (that I know that I'll have to do once again after I make the EmuNAND) and other little things as lanplay... I mean, how should I "prepare" and how should I "proceed"?

I'll be really thankfull if you or anyone here can help me!

---

Also, Regarding this post, and now for anyone here,

I'm booting Neutos-Atmos 0.12.0 directly (without hekate and on SysNAND 10.0.1) at the moment, to be able to use tinfoil, and I don't think this tutorial in this post is considering that, right? Neutos uses another payload that comes in the package, not the fusee-primary that comes with vanilla Atmosphere... Is it possible to use Neutos in this tutorial from this post?

 

[Itsuki235]

[...]

What I would recommend is:

1. Backup your save data using Checkpoint
2. Restore your NAND backup
3. Update OFW using official servers (burning fuses) to 10.0.2
4. Create a second NAND backup on that vanilla 10.0.2 OFW
5. Create emuMMC and enable it in Hekate
6. Boot CFW emuMMC (fusee-primary.bin) and install Incognito

For Step #6, either vanilla atmosphere + sigpatches or NeutOS would work for CFW emuMMC.

 

[KeoniAzugon]

What I would recommend is:

1. Backup your save data using Checkpoint
2. Restore your NAND backup
3. Update OFW using official servers (burning fuses) to 10.0.2
4. Create a second NAND backup on that vanilla 10.0.2 OFW
5. Create emuMMC and enable it in Hekate
6. Boot CFW emuMMC (fusee-primary.bin) and install Incognito

For Step #6, either vanilla atmosphere + sigpatches or NeutOS would work for CFW emuMMC.

I second that. Another way in case you don't have an account, is make the EmuNand from the current SysNand, then follow most of the steps above.

 

[Itsuki235]

I second that. Another way in case you don't have an account, is make the EmuNand from the current SysNand, then follow most of the steps above.

The above steps do not require an online account. The console will update the system's firmware regardless of that.

 

[alvpf]

What I would recommend is:

1. Backup your save data using Checkpoint
2. Restore your NAND backup
3. Update OFW using official servers (burning fuses) to 10.0.2
4. Create a second NAND backup on that vanilla 10.0.2 OFW
5. Create emuMMC and enable it in Hekate
6. Boot CFW emuMMC (fusee-primary.bin) and install Incognito

For Step #6, either vanilla atmosphere + sigpatches or NeutOS would work for CFW emuMMC.

Nice! I'm really greatful for your attention!

Do I need to restore my prodinfo through incognito before everything?