Hacking Atmosphere and Hekate update: failed?

[v1nce]

Hello,

The stock firmware of my Switch is 3.0.0, and I'm playing with emuNAND firmware 9.1.0 .
Because I want to update from 9.1.0 to 11.0.1, I followed these inscructions:
https://nh-server.github.io/switch-guide/extras/updating/
So I updated Atmosphere to 0.18.0 and Hekate to CTCaer mod v5.5.3 & Nyx v0.9.9.

Note: before to copy the various directories, I saved the old ones.

If now I launch Fusee_Atmosphere.bin at boot as I usually did to launch automatically my emuNAND, here is what is displayed:
- "Welcome to atmosphere fusee!" (in text mode),
- sept message,
- atmosphere logo,
- black screen endless...

If now I launch hekate-5.5.3.bin at boot, it runs, but when I try to click on LAUNCH and EMUMMC, here is what is displayed:
- atlasNX Losmos logo,
- black screen endless...

I tried to copy the backup directories of the previously installed Atmosphere and Hekate, but it doesn't work anymore :-(

What should I do to get back a working emuMMC?
Anything related to sigpatches may be?...

I thank you in advance...

V1nce

 

[thesjaakspoiler]

Just my personal experience : start off with a clean install of hekate/atmosphere as old files/folders might cause such problems.
The only thing of value is the Nintendo folder. That can be copied as-is.

Sigpatched should not prevent your CFW from booting afaik.

Other things could be the archive bit flags on the Nintendo folder.
Hekate has an option to fix that.

 

[v1nce]

> Just my personal experience : start off with a clean install of hekate/atmosphere
> as old files/folders might cause such problems.
> The only thing of value is the Nintendo folder. That can be copied as-is.

Backup of my previous version of Atmosphere is 146MB, with only 15.9MB for the last release.
Backup of my previous version of Hekate is 5.84MB, with only 1.65MB for the last release.
... I guess some files would miss, or not?

> Sigpatched should not prevent your CFW from booting afaik.

Yes, I guess it would just prevent to launch games.

> Other things could be the archive bit flags on the Nintendo folder.
> Hekate has an option to fix that.

Ok, I'll check and will let you know.

Thanks for your answers!

Any idea why it doesn't boot when I restore my backup of Atmosphere and Hekate?

 

[Draxzelex]

> Just my personal experience : start off with a clean install of hekate/atmosphere
> as old files/folders might cause such problems.
> The only thing of value is the Nintendo folder. That can be copied as-is.

Backup of my previous version of Atmosphere is 146MB, with only 15.9MB for the last release.
Backup of my previous version of Hekate is 5.84MB, with only 1.65MB for the last release.
... I guess some files would miss, or not?

> Sigpatched should not prevent your CFW from booting afaik.

Yes, I guess it would just prevent to launch games.

> Other things could be the archive bit flags on the Nintendo folder.
> Hekate has an option to fix that.

Ok, I'll check and will let you know.

Thanks for your answers!

Any idea why it doesn't boot when I restore my backup of Atmosphere and Hekate?

How is your SD card formatted?

 

[v1nce]

How is your SD card formatted?

FAT32. The sdcard ran all right before, the partition is ok, just the software needs to be updated.

 

[v1nce]

Just my personal experience : start off with a clean install of hekate/atmosphere as old files/folders might cause such problems.
The only thing of value is the Nintendo folder. That can be copied as-is.

Sigpatched should not prevent your CFW from booting afaik.

Other things could be the archive bit flags on the Nintendo folder.
Hekate has an option to fix that.

Yes! it works! I just backuped the original files and copied the ones from a fresh install of atmosphere and hekate, and my CFW boots now like a charm!
Unfortunatelly, I cannot run again my installed games.
I guess I need to install again sigpatches to do so.
I'll search online, but do not hesitate to point me toward the right URL ;-)

 

[BigOnYa]

1 - Format SD card to FAT32
2 - Fresh install of Atmosphere files on SD card. - https://github.com/Atmosphere-NX/Atmosphere/releases
3 - Get and put Correct Sigpatches in "atmosphere" folder - https://github.com/ITotalJustice/patches/releases
4 - (optional) Get Tinwoo or Goldleaf and place inside "switch" folder - https://github.com/XorTroll/Goldleaf/releases
5 - Boot into Hekate menu, select "Payloads", then select "Fusee-Primary"
Good Luck and Have fun!

 

[v1nce]

1 - Format SD card to FAT32
2 - Fresh install of Atmosphere files on SD card. - https://github.com/Atmosphere-NX/Atmosphere/releases
3 - Get and put Correct Sigpatches in Atmosphere folder - https://github.com/ITotalJustice/patches/releases
4 - (optional) Get Tinwoo or Goldleaf and place inside "switch" folder - https://github.com/XorTroll/Goldleaf/releases
5 - Boot into Hekate menu, select "Payloads", then select "Fusee-Primary"
Good Luck and Have fun!

I just did it and it works perfectly!
Thank you very much :-)

 

[Draxzelex]

1 - Format SD card to FAT32
2 - Fresh install of Atmosphere files on SD card. - https://github.com/Atmosphere-NX/Atmosphere/releases
3 - Get and put Correct Sigpatches in "atmosphere" folder - https://github.com/ITotalJustice/patches/releases
4 - (optional) Get Tinwoo or Goldleaf and place inside "switch" folder - https://github.com/XorTroll/Goldleaf/releases
5 - Boot into Hekate menu, select "Payloads", then select "Fusee-Primary"
Good Luck and Have fun!

Any particular reason you are recommending fusee_primary? Not everyone chainloads and fss0 works just as fine if not better.

 

[BigOnYa]

Any particular reason you are recommending fusee_primary? Not everyone chainloads and fss0 works just as fine if not better.

No real reason, no, just what I have used and done, and figured I'd put it out there to help some, but thank you for the comments because I don't know which is better frankly.

 

[urherenow]

Any idea why it doesn't boot when I restore my backup of Atmosphere and Hekate?

Did you have any kind of theme installed? If so, that's why. You'd need to delete /atmosphere/contents/0100000000001000/ to get it booting. Other culprits would be anything in atmosphere/contents/ that has a boot2.flag in it (not including what's in the Atmoshphere.zip, of course), that also needed an update.

 

[Taorn]

Any particular reason you are recommending fusee_primary? Not everyone chainloads and fss0 works just as fine if not better.

You made me curious: What benefits does one gain by loading through fss0 instead?

 

[Draxzelex]

You made me curious: What benefits does one gain, by loading through fss0 instead?

Fss0 loads Atmosphere faster than fusee overall and has the benefit of allowing you to launch sysMMC and emuMMC simultaneously while fusee can only launch one at a time. Fss0 also defaults the toggling of the nogc patch to Hekate which is easier to use than manually editing the bct.ini file used by fusee. The only advantage to fusee is that it is updated in tandem with Atmosphere so if you like bleeding edge updates, then fusee is your choice otherwise fss0 is objectively superior.