switch stuck at switch logo after booting into sysnand

[Otakuboy45]

i just did the same thing of replacing everything whenever something new comes and now when I boot into sysnand it hangs on the switch logo. I tried replacing both the atmosphere and bootlader files but nothing worrks please help me out.

 

[binkinator]

i just did the same thing of replacing everything whenever something new comes and now when I boot into sysnand it hangs on the switch logo. I tried replacing both the atmosphere and bootlader files but nothing worrks please help me out.

Did you replace fusee.bin?

move /atmosphere/contents to /atmosphere/contents.bk to get your sysmodules out of the way and try rebooting.

try entering and exiting maintenance mode:

1. Ensure the console is powered off.
   • If the console does not respond, hold down the POWER Button for twelve seconds to force it to shut down.
2. With the console powered off, hold down the volume up (+) and volume down (-) buttons, then press the POWER Button to turn the system on.
   • Be sure to maintain the volume buttons pressed down until the Maintenance Mode menu is displayed.
3. don’t select anything….just reboot.

 

[Otakuboy45]

this is what happens whenever i try to start sysnand

 

[binkinator]

this is what happens whenever i try to start sysnand

Sorry…I don’t follow. Are you saying this happens with OFW/Sysnand or CFW/Sysnand?

 

[Otakuboy45]

Did you replace fusee.bin?

move /atmosphere/contents to /atmosphere/contents.bk to get your sysmodules out of the way and try rebooting.

try entering and exiting maintenance mode:

1. Ensure the console is powered off.
   • If the console does not respond, hold down the POWER Button for twelve seconds to force it to shut down.
2. With the console powered off, hold down the volume up (+) and volume down (-) buttons, then press the POWER Button to turn the system on.
   • Be sure to maintain the volume buttons pressed down until the Maintenance Mode menu is displayed.
3. don’t select anything….just reboot.

ok so I replaced the fusee.bins and I got into maintenance mode just fine. I also renamed contents to contents.bk and it works! thanks so much dude, I appreciate you

Post automatically merged: Mar 1, 2023

Sorry…I don’t follow. Are you saying this happens with OFW/Sysnand or CFW/Sysnand?

cfw/sysnand. It boots up now but now none of the cheats I have shows up

 

[binkinator]

ok so I replaced the fusee.bins and I got into maintenance mode just fine. I also renamed contents to contents.bk and it works! thanks so much dude, I appreciate you

Glad you’re sorted. Enjoy!

If you want, you can go through your contents directory and move the numbered directories one at a time to a new /atmosphere/contents directory to see which sys-module or mods were blocking you (and upgrade them if an upgrade i available.)

 

[jeffyTheHomebrewer]

Sorry to bump this, but WHERE do I get fusee?

 

[binkinator]

Sorry to bump this, but WHERE do I get fusee?

It’s right next to the atmosphere.x.x.x.zip on GitHub.

 

[jeffyTheHomebrewer]

It’s right next to the atmosphere.x.x.x.zip on GitHub.

View attachment 356364

Ah. But why doesn't it just come inside of the atmosphere{version}.zip if it's so critical?

Post automatically merged: Mar 1, 2023

It’s right next to the atmosphere.x.x.x.zip on GitHub.

View attachment 356364

Somehow I forgot I had Mission Control installed, turns out THAT was the issue.

 

[binkinator]

Ah. But why doesn't it just come inside of the atmosphere{version}.zip if it's so critical?

Post automatically merged: Mar 1, 2023

Somehow I forgot I had Mission Control installed, turns out THAT was the issue.

I think I’m going to put together a “top 5 things to do after updating” list.

 

[gdavies]

Ah. But why doesn't it just come inside of the atmosphere{version}.zip if it's so critical?

Post automatically merged: Mar 1, 2023

Think it is because you can use other payloads too although not sure why you would given that one works so well, I have it on my RCM Loader in its own folder and just switch to that folder when i boot from the off

 

[jeffyTheHomebrewer]

Think it is because you can use other payloads too although not sure why you would given that one works so well, I have it on my RCM Loader in its own folder and just switch to that folder when i boot from the off

I just have to wonder what fusee does exactly. Do I truly need it?
Like, I realise I SHOULD probably know more about switch homebrew, but isn't the rcm-to-home menu pipeline like the 3DS?
Since on the 3DS, it's boot9strap -> boot.firm on sd card, or on nand if sd card is missing/has no firm -> luma3ds/home menu (or other cfw/firm/etc)
and on the switch, rcm -> hekate -> atmosphere -> HOS

Post automatically merged: Mar 2, 2023

I think I’m going to put together a “top 5 things to do after updating” list.

Number three: find sigpatches

 

[binkinator]

I just have to wonder what fusee does exactly. Do I truly need it?
Like, I realise I SHOULD probably know more about switch homebrew, but isn't the rcm-to-home menu pipeline like the 3DS?
Since on the 3DS, it's boot9strap -> boot.firm on sd card, or on nand if sd card is missing/has no firm -> luma3ds/home menu (or other cfw/firm/etc)
and on the switch, rcm -> hekate -> atmosphere -> HOS

Post automatically merged: Mar 2, 2023

Number three: find sigpatches

Fusee.bin is the payload that loads Atmosphere.

You don’t have to use it, alternatively you can do it with Hekate and package3.

Fusee method is straight and to the point to get Atmosphere running. You can inject it directly or chainload it in hekate_ipl.ini
payload=/bootloader/payloads/fusee.bin

Hekate method allows you to use bootloader tools and the options in hekate_ipl.ini to tweak things.
fss0=atmosphere/package3

 

[jeffyTheHomebrewer]

Fusee.bin is the payload that loads Atmosphere.

You don’t have to use it, alternatively you can do it with Hekate and package3.

Fusee method is straight and to the point to get Atmosphere running. You can inject it directly or chainload it in hekate_ipl.ini
payload=/bootloader/payloads/fusee.bin

Hekate method allows you to use bootloader tools and the options in hekate_ipl.ini to tweak things.
fss0=atmosphere/package3

Ah. Bootloader tools eh? Not to derail too much, but what can those do?

 

[binkinator]

Ah. Bootloader tools eh? Not to derail too much, but what can those do?

Payload launcher, Format sd card partitions, display hardware information, backup/restore Nand images, and a whole lot more!

Check out the full list of features here:
https://github.com/CTCaer/hekate#features

 

[jeffyTheHomebrewer]

Payload launcher, Format sd card partitions, display hardware information, backup/restore Nand images, and a whole lot more!

Check out the full list of features here:
https://github.com/CTCaer/hekate#features

Oh, somehow I thought "bootloader features" meant something other than hekate. I guess since I've used those (especially the USB stuff a lot) I must be using package3 then..

 

[gdavies]

Oh, somehow I thought "bootloader features" meant something other than hekate. I guess since I've used those (especially the USB stuff a lot) I must be using package3 then..

I use an RCM Loader rather than inject via usb, I found the lockpick bootloader really useful, atmosphere or possibly deep sea provided a common faults bootloader which I always keep on my RCM Loader

 

[jeffyTheHomebrewer]

I use an RCM Loader rather than inject via usb, I found the lockpick bootloader really useful, atmosphere or possibly deep sea provided a common faults bootloader which I always keep on my RCM Loader

I see. I just put the jig in, hold both volume buttons, then plug my switch into my PC, which then also powers it back on. Once it's on tegrarcmgui (typically minimized) will recognize it and smash in hekate, which then should autoboot to atmosphere (with my 3 second bootlogo)

 

[binkinator]

I see. I just put the jig in, hold both volume buttons, then plug my switch into my PC, which then also powers it back on. Once it's on tegrarcmgui (typically minimized) will recognize it and smash in hekate, which then should autoboot to atmosphere (with my 3 second bootlogo)

And at that point you could technically inject fusee and boot straight in to AMS and bypass Hekate altogether OR you could inject Hekate and chainload fusee.bin inside your hekate_ipl.ini via a payload= in your chosen stanza and just boot straight in to AMS (no splash screens or other bells and whistles) OR use fss0= and add any other tweaks you would like in the hekate_ipl.ini stanza. Lots of options! Play around with the various options and see which you prefer…or don’t and just use what works until you run into a use case that you need.

 

[gdavies]

Personally I let mine boot into hekate an that way choose a payload that is best suited, I only keep it so it boots into heKate as an almost safety net given it is just a boot loader