Hekate.ipl.ini Help

[w3llus]

Hi all
Wondering if someone can help me. Its been a year since i have done anything with the Switch. Having just updated to the latest firmeware i went into smash the latest Atmosphere and Hekate update on my CFW

I am using Ultra NX as an all in one solution
Using their Hekate.ipl.ini I am running into failed boots

[config]
autoboot=1
autoboot_list=0
bootwait=4
backlight=90
noticker=0
autohosoff=2
autonogc=0
updater2p=0
bootprotect=0

[Atmosphere]
pkg3=atmosphere/package3
cal0blank=1
kip1=atmosphere/kips/*
logopath=bootloader/res/bootscreen.bmp
icon=bootloader/res/atmo_cfw.bmp

[Safe Mode]
pkg3=atmosphere/package3
cal0blank=1
logopath=bootloader/res/bootscreen.bmp
icon=bootloader/res/atmo_sm.bmp

The only way round this is to update the atmopshere boot to:

[Atmosphere]
payload=bootloader/payloads/fusee.bin 
emummcforce=1 
icon=bootloader/res/atmo_cfw.bmp

I removed the existing old bootloader, config and atmosphere folders, and have even tried the HAT package to see if someone was up but its the same issue.
I would be keen to understand and learn why i have had to update the boot ini and move away from the preset config

Thanks

 

[Badablek]

Hi,

this may be related to this ? with the fix here (this fix is not included with latest Hekate)

(I don't know if you have an Erista, and, by reading your hekate_ipl.ini, it seems you're not using emuMMC ? but you're using it with fusee config ? that's really strange)

 

[w3llus]

Hi and thanks for replying
I have the original V1 Switch (Erista)

I modded thew switch about 2 years ago now and have clearly missed a few of the updates as well as forgotten some knowledge.
Is my config an old way of loading Atmosphere and have things moved on?

 

[Badablek]

Erista is affected by the bug, but I don't know if it's only on emuMMC.

your hekate_ipl.ini seems OK :

• you're already using pkg3 instead of fss0, which shows you are not as outdated as you think.
• safe mode is not really helpful, as you only avoid to use sigpatches...and you're still hiding PRODINFO on sysMMC (which is NOT safe at all against ban)
• you should use sys-patch instead of sigpatches (by removing kip1 line)
• by using cal0, you're hiding PRODINFO on sysMMC and emuMMC...exosphere lets you hide it only on sys or emu...seems better to me

with fusee, you are forcing emuMMC (which is not needed as fusee will automatically load emuMMC if an emummc folder is at SD root)
but with your "old" config, you're not using emummc at all ? That's a little bit weird, isn't it ?

So...are you using emuMMC or not ?

if the answer is yes, then your main config should be :

config]
autoboot=1
autoboot_list=0
bootwait=4
backlight=90
noticker=0
autohosoff=2
autonogc=0
updater2p=0
bootprotect=0

[Atmosphere]
pkg3=atmosphere/package3
cal0blank=1
emummcforce=1
logopath=bootloader/res/bootscreen.bmp
icon=bootloader/res/atmo_cfw.bmp

 

[w3llus]

Erista is affected by the bug, but I don't know if it's only on emuMMC.

your hekate_ipl.ini seems OK :

• you're already using pkg3 instead of fss0, which shows you are not as outdated as you think.
• safe mode is not really helpful, as you only avoid to use sigpatches...and you're still hiding PRODINFO on sysMMC (which is NOT safe at all against ban)
• you should use sys-patch instead of sigpatches (by removing kip1 line)
• by using cal0, you're hiding PRODINFO on sysMMC and emuMMC...exosphere lets you hide it only on sys or emu...seems better to me

with fusee, you are forcing emuMMC (which is not needed as fusee will automatically load emuMMC if an emummc folder is at SD root)
but with your "old" config, you're not using emummc at all ? That's a little bit weird, isn't it ?

So...are you using emuMMC or not ?

if the answer is yes, then your main config should be :

config]
autoboot=1
autoboot_list=0
bootwait=4
backlight=90
noticker=0
autohosoff=2
autonogc=0
updater2p=0
bootprotect=0

[Atmosphere]
pkg3=atmosphere/package3
cal0blank=1
emummcforce=1
logopath=bootloader/res/bootscreen.bmp
icon=bootloader/res/atmo_cfw.bmp

I just want to say thank you for taking the time to reply. I will give this a go tomorrow morning. Thanks for explaining it all.

 

[Glomgold]

I was also affected by this bug, the fix is probably all you need.

 

[browntigerz]

Remove
kip1=atmosphere/kips/*
And try again