Homebrew Question Issues updating Atmosphere

[ticondrius99]

So, first of all, I'm on FW 10.0.1 and on Atmosphere 0.11.1
I wanted to update my Switch's firmware (in order to play newer games), but in order to do that I had to update Hekate and Atmosphere.
I simply dragged and dropped the newer releases of the two, and used Hekate's new .bin to inject the payload. The Switch booted onto Hekate - which asked me to set a date and time for Nyx - and then as usual I launched one of the two first option under Launch (I'm a real noob, sorry). It showed the usual splash screen (but not the Atmosphere logo after that) but the display stayed black. After a few tries, I had to keep the POWER button pressed for a few seconds, then press it again and the console entered RCM mode.
I tried to do it all again a few times (even choosing the other option under the 'Launch' in Hekate) but the result didn't change.
I restored the previous Atmosphere files and with the upgraded Hekate everything worked again.

What should I do to update Hekate? I found some patches online - but should that do the trick?
Should I update with Atmosphere Updater? I'm a bit scared to ruin something.
If it may be of help, I recently changed my SD card... Thanks to everyone in advance for any piece of advice!

 

[Gamerjin]

are you using a emunand?
if not, does your hekate_ipl.ini look similar to this:

[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100
[CFW - sysMMC]
payload=/bootloader/payloads/fusee-primary.bin
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

this is what i have been using to launch ams 0.16.2

 

[ticondrius99]

are you using a emunand?
if not, does your hekate_ipl.ini look similar to this:

First, thank you very much for your fast answer!
No - I'm not using an Emunand (at least, in Hekate's settings Emunand says 'disables').
And not, my hekate_ipl.ini is quite different:

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

I also don't have [CFW - sysMMC] configuration but just [CFW - SYSNAND] and [CFW - EMUMMC]
It has to be said that it's the first Hekate/Atmosphere update I've ever done since May 2020.
What should I do? Sorry to bother you...

 

[Gamerjin]

I also don't have [CFW - sysMMC] configuration but just [CFW - SYSNAND] and [CFW - EMUMMC]

can you post those section as well?

 

[ticondrius99]

can you post those section as well?

Of course, sorry!

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

{AtlasNX/Kosmos w/ nosigchk}
{}
{Discord: discord.teamatlasnx.com}
{Github: git.teamatlasnx.com}
{Patreon: patreon.teamatlasnx.com}
{Pegascape DNS: pegascape.sdsetup.com}
{}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
kip1=atmosphere/kips/*
{}

[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
kip1=atmosphere/kips/*
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}

This is everything in the file...
Thank you so much again!

 

[Gamerjin]

ok, it looks like your booting using fss0, which i dont know too much about....
try adding my section to the end of Custom firmware section:

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

to the end, and see if that boots, if it does, you may need to update the fss0 patches as well....

 

[ticondrius99]

try adding my section to the end of Custom firmware section:

I'm so, so sorry! I shared with you an old backup of the file!! Here's the one I'm using:

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

{AtlasNX/Kosmos w/ nosigchk}
{}
{Discord: discord.teamatlasnx.com}
{Github: git.teamatlasnx.com}
{Patreon: patreon.teamatlasnx.com}
{Pegascape DNS: pegascape.sdsetup.com}
{}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
kip1=atmosphere/kips/*
{}

[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
kip1=atmosphere/kips/*
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}

Still, it uses the fss0... Should I put your string of code nonetheless?
And I should do that before merging Atmosphere's new files, right?
I'm a real noob, sorry!

 

[Gamerjin]

just put my section at the end of the custom firmware section but before the stock option....

 

[ticondrius99]

just put my section at the end of the custom firmware section but before the stock option....

Alright, I did just as you said, and booting up Hekate and pressing Launch opens up a new option 'sysMMC'. I tried to use it and Atmosphere boots up just as fine (the only differences I could see where the splash screens). Should I now try to update Atmosphere files?

 

[Gamerjin]

it should work now, but it doesnt...........
well lets wait until we cross that bridge.

 

[ticondrius99]

Alright, I'll try! I'm also putting the patches I found of someone who had a similar problem.
Thank you very much for your kind help! I'll keep you updated!

 

[ticondrius99]

it should work now, but it doesnt...........
well lets wait until we cross that bridge.

Bad news: it went just as far as the Atmosphere logo, but then the screen turns black without showing the NSW logo...

 

[Gamerjin]

allright, welp, we crossed that bridge.
im only to ams 16, but i will see if i can update to latest AMS, and if so, i will see what i had to do....
i also have work soon, so the answer will be posted tomorrow....

 

[kidkat210]

Easiest way I would say is delete these folders, bootloader, atmosphere, and sept. Essentially start from scratch

 

[ticondrius99]

allright, welp, we crossed that bridge.
im only to ams 16, but i will see if i can update to latest AMS, and if so, i will see what i had to do....
i also have work soon, so the answer will be posted tomorrow....

Thank you very much! Take your time, I'm not in a hurry... In the meanwhile, I'll try other methods.

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

Easiest way I would say is delete these folders, bootloader, atmosphere, and sept. Essentially start from scratch

So I should delete those folders and put the upgraded ones into the root of the SD?
I'll try, thanks!

 

[ticondrius99]

Eureka! It worked! I put a clean atmosphere folder and worked like a charm! Thank you guys for your help!!
I hope to be able to update my firmware...
Thanks!

 

[kidkat210]

When updating cfw, I highly suggest doing a fresh "install" instead of overwriting