Tutorial  Updated

How to: Hekate chainload vanilla Atmos

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.
 
Last edited by toxic9,

alvpf

Active Member
Newcomer
Joined
Mar 21, 2020
Messages
25
Trophies
0
Age
36
XP
110
Country
Brazil
Restoring from the MMC backup will also restore the prodinfo which is why it is necessary to wipe it again in emuMMC.

Also, after updating through official servers and burning fuses, is it possible to downgrade the EmuMMC firmware to a lower fuse stage one?
 

Itsuki235

Well-Known Member
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
368
Country
United States
Also, after updating through official servers and burning fuses, is it possible to downgrade the EmuMMC firmware to a lower fuse stage one?
The fuses are a one-way physical hardware component of booting the switch. This means that both sysMMC and emuMMC "share them". AutoRCM mode bypasses fuse checks completely.

Technically, it is possible to downgrade emuMMC to a lower system firmware but doing so is nearly always unnecessary. CFW and every important Homebrew works on OFW 10.0.2 right now.
 

alvpf

Active Member
Newcomer
Joined
Mar 21, 2020
Messages
25
Trophies
0
Age
36
XP
110
Country
Brazil
The fuses are a one-way physical hardware component of booting the switch. This means that both sysMMC and emuMMC "share them". AutoRCM mode bypasses fuse checks completely.

Technically, it is possible to downgrade emuMMC to a lower system firmware but doing so is nearly always unnecessary. CFW and every important Homebrew works on OFW 10.0.2 right now.

Once again, thank you very much for taking your time to help me!
 
  • Like
Reactions: Itsuki235

Itsuki235

Well-Known Member
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
368
Country
United States
the idea is to maintain current CFW setup while having a fresh clean OFW setup. An idea from the 3DS to save time.
It does not really save time though because then you are in a situation where you are updating both OFW and CFW separately.

Just updating them at the same time, so creating a new emuMMC setup from vanilla should not take more time.
 

KeoniAzugon

Well-Known Member
Member
Joined
Mar 21, 2016
Messages
181
Trophies
0
Age
29
Website
Nblog.org
XP
697
Country
United States
The Idea is as follows:
* create EmuNand from SysNand
* verify EmuNand
* Restore Nand backup to SysNand
* Update SysNand
* Profit. the OFW and CFW are ready to go.

Edit: The update for EmuNand to latest firmware was a missed detail cause he has current SysNand CFW on 10.0.1
Minor updates, unless necessary, are missed.
 
Last edited by KeoniAzugon, , Reason: edit note

Itsuki235

Well-Known Member
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
368
Country
United States
The Idea is as follows:
* create EmuNand from SysNand
* verify EmuNand
* Restore Nand backup to SysNand
* Update SysNand
* Profit. the OFW and CFW are ready to go.
Okay I see what you mean now. It does skip the step of installing incognito since that is already done, and more importantly backups do not need to be reinstalled/save data restored.

However that only applies to alvpf. Typically, people do not have their system's firmware updated to the latest version. In that situation, needing to stay offline on emuMMC would necessitate using ChoijudourNX and locating the firmware update files, but that does not apply here.
 

LapCheong

Well-Known Member
Member
Joined
Mar 6, 2019
Messages
219
Trophies
0
XP
519
Country
Australia
What is difference between booting with

fusee primary
kips _patches
payload=fusee_primary.bin

AND

fss0 fusee secondary
nogc
patches.ini
 
Last edited by LapCheong,

Kohmei

Well-Known Member
Member
Joined
Feb 17, 2013
Messages
824
Trophies
0
XP
1,039
Country
United States
My emuNAND boot section looks like this:
Code:
[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
kip1=atmosphere/kips/*
atmosphere=1
How do I implement this, so that I can use the standard patches. Or can I?
 

Stellar

Well-Known Member
Member
Joined
Jul 20, 2014
Messages
194
Trophies
0
XP
1,776
Country
Portugal
Thanks for the guide, it worked wonderfully.

You can also replace "/atmosphere/reboot_payload.bin" with hekate's payload, and now when you restart your console it will boot to hekate instead of fusee-primary.
 

Senbou

Well-Known Member
Member
Joined
Jan 7, 2020
Messages
114
Trophies
0
XP
348
Country
Philippines
hey guys..I cant seem to make this .ini to work..whenever I try to inject fusee-primary.bin, it stays on black screen..but when I put my old .ini file it works but its not vanilla atmos Im sure of that..forgot what i did a few updates back..need help for making this work thanks..


and btw here's my current .ini that's working for me

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=100
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0


[CFW - sysMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/fusee-secondary.bin
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: 10 tabs open on chrome and no slow downs suck it low ram ple bs lol