Okay this is fairly simple tutorial, but there have been people asking in discord what to do to get this running so I figured I would type this up.

This process assumes you have run hekate previously and have used an older version of atmosphere
Patches are required to add full functionality. Get them here

SD FILES UPDATED. GET THEM FROM HERE

Process:

1) Download Atmosphere from here. Make sure you download both the .zip files and the .bin file, this is very important.
2) Override your previous atmosphere folder, bct.ini and fusee-secondary.bin on your sd card
3) Copy fusee-primary.bin to sd:/bootloader/payloads and override the previous file
4) Edit your hekate_ipl.ini to look like the following. (you can add a new entry or just modify the existing cfw one)

[Atmosphere 6.2 CFW]
payload=bootloader/payloads/fusee-primary.bin

5) Save and close the ini.
6) Put your Micro SD back into your switch
7) Launch hekate with hekate_ctcaer_4.2.bin and choose your newly edited cfw option and enjoy [/INFORMATION]

 

[smf]

I am wondering if there's anything different in that fork versus vanilla atmosphere.

looks a bit weird

https://github.com/Atmosphere-NX/At...asNX:6b31b1cb5e578b6ac79d0d56d48541258adb6b54

https://github.com/AtlasNX/Kosmos-A...e-NX:bd76e73b253fa14327425e3952815e720dbf8343

 

[JeepX87]

The only ips files I have are the fs/es patch folder inside the atmosphere folder

I was booting fine without them

I have a problem - I got key derivation failed on every first boot but works on every 2nd boot after power off the Switch, so my solution by put biskey in it won't work.

Any idea to fix key derivation failed error?

 

[OrGoN3]

looks a bit weird

https://github.com/Atmosphere-NX/At...asNX:6b31b1cb5e578b6ac79d0d56d48541258adb6b54

https://github.com/AtlasNX/Kosmos-A...e-NX:bd76e73b253fa14327425e3952815e720dbf8343

Thank you very much. I didn't know that was possible on the site. Very much appreciated.

 

[Adran_Marit]

Thank you very much. I didn't know that was possible on the site. Very much appreciated.

It's just pre bundled stuff vs set up yourself

--------------------- MERGED ---------------------------

I have a problem - I got key derivation failed on every first boot but works on every 2nd boot after power off the Switch, so my solution by put biskey in it won't work.

Any idea to fix key derivation failed error?

What version are you using 0.8.0 or 0.8.1 I know they fixed some stuff with the latter

 

[JeepX87]

It's just pre bundled stuff vs set up yourself

--------------------- MERGED ---------------------------

What version are you using 0.8.0 or 0.8.1 I know they fixed some stuff with the latter

0.8.1

 

[noahc3]

@noahc3 is there any chance to include this on switch guide? so people can play in 6.2.0 while waiting for official hakate compatibility for 6.2.0? thanks.

I'll get around to this sometime this week, yes. Will just use the Kosmos 11.1 pre-release.

 

[JeepX87]

0.8.1

Just switched to Kosmos so it is fully resolved now.

 

[OrGoN3]

It's just pre bundled stuff vs set up yourself

--------------------- MERGED ---------------------------


What version are you using 0.8.0 or 0.8.1 I know they fixed some stuff with the latter

Is there anything special kosmos does for the sleep mode fix?

 

[Adran_Marit]

Is there anything special kosmos does for the sleep mode fix?

sleep mode fix? didnt know there was an issue with sleep mode

 

[smf]

Is there anything special kosmos does for the sleep mode fix?

sleep mode is fixed by updating to a firmware version that matches the fuses you have burnt.

If you have 8 fuses burnt then upgrade to 6.2 and you'll be fine.

 

[OrGoN3]

sleep mode is fixed by updating to a firmware version that matches the fuses you have burnt.

If you have 8 fuses burnt then upgrade to 6.2 and you'll be fine.

And if I upgrade to a firmware beyond the amount of fuses I have burnt?

 

[Adran_Marit]

And if I upgrade to a firmware beyond the amount of fuses I have burnt?

if you boot without a cfw you will burn fuses = to the fuse requirements

 

[OrGoN3]

if you boot without a cfw you will burn fuses = to the fuse requirements

I meant in terms of sleep mode. If I upgrade my firmware past the amount of burnt fuses (with autorcm on), will that affect sleep mode? When it returns from sleep mode?

 

[Freloque]

I meant in terms of sleep mode. If I upgrade my firmware past the amount of burnt fuses (with autorcm on), will that affect sleep mode? When it returns from sleep mode?

Can someone explain to me what's the point of avoiding burning fuses ? (honest question). I updated to 6.2.0 with OFW (so I burned fuses) and then I installed a CFW and it works so why should we avoid that ?

 

[Adran_Marit]

Can someone explain to me what's the point of avoiding burning fuses ? (honest question). I updated to 6.2.0 with OFW (so I burned fuses) and then I installed a CFW and it works so why should we avoid that ?

the avoiding of burning fuses is for downgrading (if you want to) otherwise if you downgrade you won't have any sleep mode

 

[loopz]

That’s perfect, many thanks and huge thanks to @SciresM

 

[gianm93]

I have to inject Hekate 4.5 twice in order to start my switch (I am on 6.2.0). Is that a bug or did I something wrong?

 

[Zumoly]

Is there a way to set bootlogo for atmosphere (not hekate) after the payload injection (same way as ReiNX)?

 

[Adran_Marit]

Is there a way to set bootlogo for atmosphere (not hekate) after the payload injection (same way as ReiNX)?

put bootlogo in atmosphere folder?

 

[Zumoly]

put bootlogo in atmosphere folder?

I did but it's still not showing.
I'm launching AMS via payload from Hekate (autoboot)