Switch gets stuck when trying to reboot console

[masagrator]

Can't find this issue, so I guess I will ask here.

Recently moved to another Switch, migrated data from one sdcard to another that was already used by different Switch.

Everything works fine except for one thing - when I try to reboot console in HOS with Atmosphere, after display gets turned off but before it completely shuts down it gets stuck and I need to press long time power button to actually shut it down. I don't want to redo atmosphere folder, so maybe someone else had this issue and figured out how to fix it?

Previous Switch is using SX Modchip, current Switch is using picofly.

 

[thesjaakspoiler]

Did that feature ever work or is this the first time you try and you notice that it doesn't?

There should be a file called payload.bin or reboot_payload.bin in your Atmosphere folder.
This is the primary payload file that just has been renamed.
This should be the same primary payload for the Atmosphere version that you are currently using.
A newer or older version will give all kinds of funky issues.
It can also be some related settings.
Maybe read through this thread :

Post in thread 'Reboot to payload bin file'

Feb 6, 2022

I responded to you in this thread recommending you try this with hekate.

Rename hekate_ctcaer_x.x.x.bin to reboot_payload.bin and put it into atmosphere folder.

Set updater2p=1 and autoboot=1 (assuming Atmosphere on Emunand is your first entry) in /bootloader/hekate_ipl.ini

Reboot and you are done!

Config option	Description
autoboot=0	0: Disable, #: Boot entry number to auto boot.

updater2p=0

0: Disable, 1: Force updates (if needed) the reboot2payload binary to be hekate.

• binkinator

 

[masagrator]

It worked properly on my initial sdcard, after migration it started behaving weirdly.
I have reboot_payload.bin in atmosphere folder that is used to boot Hekate, it's not fusee.

That thread you linked is discussing rebooting to wrong payload, in my case it seems to not reboot at all (no visual signal from modchip that it happened).

 

[cucholix]

Do you have the folder warmboot_mariko for your picofly console?

 

[masagrator]

Do you have the folder warmboot_mariko for your picofly console?

I had, but I deleted it and it's now fixed. Thanks for pointing in correct direction.