[Doubt] Does it work for OLED switch model?

  • Thread starter Thread starter johw
  • Start date Start date
  • Views Views 13,127
  • Replies Replies 59
I find this whole thread confusing. Your chip loads /payload.bin. If /payload.bin happens to be hekate, then simply selecting reboot from the power menu, will reboot the console to nyx. I've done this since chipping my OLED. I seriously don't understand what the issue is/was. I've used the firmware here since the beginning. This hekate loader is useless for a chipped Switch. Unless you just *have to* be able to reboot, while docked, from across the room, with a pro controller...
 
Last edited by urherenow,
Can I suggest a power off option?

Now I'm using the OFF-switch from ITotalJustice with a forwarder:

https://github.com/ITotalJustice/Off-Switch

In my unpatched erista I had the power off payload and launched vía fastCFWswitch.

I'll try with an entry in the hekate_ipl.ini... Studious Pancake should list it.
interesting, so see if it works and post the result here.
 
Studious Pancake
Guys, which path do I add to hekate_ipl to add hetake or shutdown ?
 

Attachments

  • overlay.png
    overlay.png
    479.7 KB · Views: 71
Place this to your SD
Hey following up on this, are you saying this will work on OLED Switch models with a mod chip? Because I tried earlier from the official Github and it didn't work so curious how this is any different?
 
So here's a question, the reason why fastcfwswitch DOESNT FULLY WORK on Mariko is because Mariko doesn't support the payload that would contain the instruction on what to do after reboot.

So if that's the case, why not save the instructions to the SDcard (like the bootid, or UMS) with a flag, that would be reset after it's executed.

I'm aware it would require changes to fastcfwswitch as well as a PR to hekate but it seems possible.
 
  • Like
Reactions: johw
So here's a question, the reason why fastcfwswitch DOESNT FULLY WORK on Mariko is because Mariko doesn't support the payload that would contain the instruction on what to do after reboot.

So if that's the case, why not save the instructions to the SDcard (like the bootid, or UMS) with a flag, that would be reset after it's executed.

I'm aware it would require changes to fastcfwswitch as well as a PR to hekate but it seems possible.
https://github.com/HookedBehemoth/studious-pancake/releases

the best option is to use this one
 
Okay once i set this up on my OLED switch , how do i change it so one of the options boots to the Hekate menu without going into UMS mode in Hekate?
Hey everyone, following up on this as i'm still not sure how to do this. There is an option to reboot to UMS mode in Hekate but i want to add an option to boot into Hekate without UMS, how can I do this?
 
Hey everyone, following up on this as i'm still not sure how to do this. There is an option to reboot to UMS mode in Hekate but i want to add an option to boot into Hekate without UMS, how can I do this?

You can set up a boot option on your hekate_ipl for hekate payload so when you load it up with studious pancake it reboot into hekate.
 
You can set up a boot option on your hekate_ipl for hekate payload so when you load it up with studious pancake it reboot into hekate.
You can set up a boot option on your hekate_ipl for hekate payload so when you load it up with studious pancake it reboot into hekate.
Okay, so how exactly do I do this? My my hekate_ipl.ini file located in the bootloader folder has the following in it:

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

[SEMI-STOCK (SYSMMC)]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
{}

[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}
 
Okay, so how exactly do I do this? My my hekate_ipl.ini file located in the bootloader folder has the following in it:

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

[SEMI-STOCK (SYSMMC)]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
{}

[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}
Hey everyone just following up. If someone can please help me I would really appreciate it. This has been driving me crazy for months. I just want to be able to have another option in studios pancake to boot directly into hekate, not into hekate UMS mode.
 
Hey everyone just following up. If someone can please help me I would really appreciate it. This has been driving me crazy for months. I just want to be able to have another option in studios pancake to boot directly into hekate, not into hekate UMS mode.

{Hekate}
[Hekate]
payload=bootloader/payloads/Hekate.bin
{}
 
FastCFWswitch only reboots to hekate on modchip consoles.

Check my pack for hekate configs...
Can I suggest a power off option?

Now I'm using the OFF-switch from ITotalJustice with a forwarder:

https://github.com/ITotalJustice/Off-Switch

In my unpatched erista I had the power off payload and launched vía fastCFWswitch.

I'll try with an entry in the hekate_ipl.ini... Studious Pancake should list it.
One question: is this your package
PacOS?
config\BootSoundNX\sound
When does this one play? I thought it was really cool.
 

Site & Scene News

Popular threads in this forum