Studious-pancake is a Tesla overlay, similar to fastCFWSwitch in that it will reboot your Switch into the various boot methods you have in your hekate_ipl.ini and a few other handy options.I saw this new plugin what does it do?
But this one doesn't work for mariko? Btw i recently saw an fastcfwmod posted https://github.com/TTghostsemir/fastCFWswitch/releases/tag/1.3.1_modIt’s similar to fastCFWSwitch in that it will reboot your Switch into the various boot methods you have in your hekate_ipl.ini and a few other handy options.
Wow! That’s an awesome find! Yes, Mariko doesn’t use reboot-to-payload so they must have figured out another method. Thanks for this. I’m going to try it out!But this one doesn't work for mariko? Btw i recently saw an fastcfwmod posted https://github.com/TTghostsemir/fastCFWswitch/releases/tag/1.3.1_mod
Which supossidly works for mariko?
Please let me know if it worksWow! That’s an awesome find! Yes, Mariko doesn’t use reboot-to-payload so they must have figured out another method. Thanks for this. I’m going to try it out!
Check this fork from Studious-Pancake it has Mariko Support.
You Need to merge it whit master from HookedBehemoth/studious-pancake for fw 16 Support.
Maybe someone create a pull request to HookedBehemoth.
https://github.com/btc08gh/studious-pancake
What is the difference for fastcfwswitch between sysnand.emunand, atmosphere in the ovl? atmosphere is CFW emunand right? so why have 2 entries. I tried sysnand and it booted me into hekate.. so the mod doesn't work i guess?Studious-pancake is a Tesla overlay, similar to fastCFWSwitch in that it will reboot your Switch into the various boot methods you have in your hekate_ipl.ini and a few other handy options.
You mean the example config.ini located here?What is the difference for fastcfwswitch between sysnand.emunand, atmosphere in the ovl? atmosphere is CFW emunand right? so why have 2 entries. I tried sysnand and it booted me into hekate.. so the mod doesn't work i guess?
I tried but whatever I do it seems to reboot to hekate, and not boot atmosphere or sysnand. I try to make them link id.You mean the example config.ini located here?
https://github.com/Hartie95/fastCFWswitch/blob/master/out/config/fastCFWSwitch/config.ini
[CFW]
type=section
name=CFW
[SYSMMC]
name=sysMMC
path=/bootloader/update.bin
bootId=sysnand
[EMUMMC]
name=emuMMC
path=/bootloader/update.bin
bootId=emunand
[ATMOSPHERE]
name=Atmosphere
path=/atmosphere/reboot_payload.bin
[SXOS]
name=SX OS
path=/sxos/reboot_payload.bin
[ANDROID]
name=Android
path=/bootloader/update.bin
bootId=SWANDR
[Ubuntu]
name=Ubuntu
path=/bootloader/update.bin
bootId=SWR-UBU
[TOOLS]
name=Tools
[HEKATE]
name=hekate
path=/bootloader/update.bin
[LOCKPICKRCM]
name=Lockpick RCM
path=/bootloader/payloads/Lockpick_RCM.bin
[UMS]
name=hekate UMS options
[SD_CARD]
name=microSD
path=/bootloader/update.bin
ums=sd
[EMMC_GPT]
name=EMMC GPT
path=/bootloader/update.bin
ums=emmc_gpt
Those are just examples.
You need to ensure you have an id that matches each bootId in your hekate_ipl.ini file.
the config.ini passes that value to hekate.
I posted an example of mine over here so you can see how the two files work together
https://gbatemp.net/threads/how-to-...s-on-the-same-sd-tutorial.601607/post-9705442
I’ve found that when it stops on Hekate that usually means it doesn’t like something (can‘t find something or a mismatched Id, stuff like that.) Double check that everything you are referencing is actually there and in place.I tried but whatever I do it seems to reboot to hekate, and not boot atmosphere or sysnand. I try to make them link id.
This is my hekate config:
[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100
[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_Atmosphere.bmp
id=atmo
[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_stock.bmp
id=sysnand
[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
This is the fastCFW config:
[CFW]
type=section
name=CFW
[SYSMMC]
name=sysMMC
path=/bootloader/update.bin
bootId=sysnand
[EMUMMC]
name=emuMMC
path=/bootloader/update.bin
bootId=emunand
[ATMOSPHERE]
name=Atmosphere
path=/atmosphere/reboot_payload.bin
bootId=atmo
[SXOS]
name=SX OS
path=/sxos/reboot_payload.bin
[ANDROID]
name=Android
path=/bootloader/update.bin
bootId=SWANDR
[Ubuntu]
name=Ubuntu
path=/bootloader/update.bin
bootId=SWR-UBU
[TOOLS]
name=Tools
[HEKATE]
name=hekate
path=/bootloader/update.bin
[LOCKPICKRCM]
name=Lockpick RCM
path=/bootloader/payloads/Lockpick_RCM.bin
[UMS]
name=hekate UMS options
[SD_CARD]
name=microSD
path=/bootloader/update.bin
ums=sd
[EMMC_GPT]
name=EMMC GPT
path=/bootloader/update.bin
ums=emmc_gpt
I get what you are saying and I had the same idea. but the files there are original and there. I think i matched the ID's from what i can see but o well. guess it was too good to be ttrueI’ve found that when it stops on Hekate that usually means it doesn’t like something (can‘t find something or a mismatched Id, stuff like that.) Double check that everything you are referencing is actually there and in place.
/bootloader/update.bin
/atmosphere/reboot_payload.bin
…you get the idea.
No, this doesn't help at all.Maybe this tool could be help.
It's a reboot/shutdown tool.
I believe it shuts down the switch hard without hos resetting the rtc clock.
https://github.com/dezem/Safe_Reboot
Naw…I have it on my switch and it works perfectly. I’m going to give 16.0.0 a try and see if it broke the functionality.I get what you are saying and I had the same idea. but the files there are original and there. I think i matched the ID's from what i can see but o well. guess it was too good to be ttrue
I’m on a V1. Only just heard that it was “working” on Mariko in this thread. Haven’t tried it. Looks like it might be a dead end…but... do you have a mariko console?