They are identical, kip1 just means that the file is pretty old in 99% of the cases (since we switched from kip1 to kip)Can someone clarify the differences between .kip and .kip1?
I've seen hekate_ipl.ini's with identical .kip(1) filenames, but both as .kip and .kip1. It confuses me.
Thanks buddyThey are identical, kip1 just means that the file is pretty old in 99% of the cases (since we switched from kip1 to kip)
ReiNX need to download via ReiNX.bin. There's no other way.Is it possible to load a .kip(1) from a CFW such as ReiNX?
did you try renaming to FS.kipIs it possible to load a .kip(1) from a CFW such as ReiNX?
I'm trying to auto-load an exFAT driver (FS.kip1) and tried putting it in ReiNX's sysmodules folder, but there were only .kip files there (loader.kip and sm.kip) and my .kip1 wasn't loaded.
I'm assuming that i need to load it manually via hekate_ipl.ini, but i don't know if it can load it by default, regardless of what i choose to launch from the bootloader.
I thought so too..ReiNX need to download via ReiNX.bin. There's no other way.
Driver exfat can be set via ChoiDujourNX.
Apparently this workeddid you try renaming to FS.kip
uhhh here https://github.com/rajkosto/hekate/releases/tag/rajkosto-fskip_patching but you should really just use current hekate, which includes a ton of new useful features and includes this functionality already if specified in the iniwhere can I download hekate_fspatches_v1.bin