Homebrew Question What's the significance of the hekate_ipl.ini file? Can you just download any?

[x3malx]

Sorry for the noob question, I'm new to the homebrew scene and I'm trying to get a basic working understanding of everything.

What does this file do? I'm not sure if I got mine from the SD website or elsewhere.

Should I ensure its contents are correct? Should I change it?

Thanks

 

[fvig2001]

It usually is used to determine:

1. Available launch profiles (cfw nand, cfw emunand, stock)
2. Auto boot settings
3. When to use emunand
4. When to use sigpatches (if Hekate sigpatches)
5. Which payload to use (fusee-primary, Android)

It's only safe to use downloaded ones probably from sdsetup and for Linux/Android. The others may have references to missing files or may cause you to boot into stock and burn a fuse.

 

[x3malx]

Thanks for the reply.

1) Do ever need to change it then?

2) why do I have to inject a payload (eg. Fusee_primary.bin) or manually select a boot option from hekate if the ini file does this already? For example, I've got 4 options on boot: CFW (sysMMC), CFW (emuMMC), Stock and Fusee.

I find this stuff interesting so I'm curious haha

 

[fvig2001]

1. Casually, probably not unless sigpatch method changes like recently
2. People usually use fusee-primary as a payload because there was a time when Hekate sigpatches were not updated due to drama caused by Tinfoil's author. The only way hekate users could use sigpatches was to use Atmosphere sigpatches. This was done by loading Hekate first then Hekate loading Atmosphere directly to apply sigpatches. I personally just set auto boot via toolbox so that I don't have to deal with the Hekate menu.