Remove these linesDo you guys have any idea why i can boot Atmosphere on emunand via fusee.bin but not via hekate?
Since I updated firmware to 17.0.1 and atmosphere to 1.6.2 (hekate 6.0.7), I get the infamous Error 2162-0002 (0x4a2) on either program 0100000000001000 or 010000000000100C (seems to be random) . I already knew these kind of programs referred to custom themes being installed and incompatible with the new release, although i've never been interested in themes and i don't have those folders in atmosphere/contents.
So far I've tried to clean up my atmosphere/contents folder and updating all tesla overlays but to no avail. I also removed tesla menu and the .overlays contents completely, but still getting a crash when loading Atmosphere.
I can boot into atmosphere only by loading fusee.bin from the hekate menu, and everything works as expected (even tesla and all overlays).
The moment I try to reboot and launch the emummc via hekate, I get the same error again and I have to reboot and load fusee.bin to boot into atmosphere.
The hekate_ipl.ini settings I'm trying to load (which worked on earlier atmosphere versions) is this:
Code:[Atmosphere (emuMMC)] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 cal0blank=1 atmosphere=1 logopath=bootloader/res/bootlogo-emunand-f.bmp icon=bootloader/res/icon_payload.bmp
Do you have any idea what might be wrong with the way I'm loading atmosphere via hekate?
emummcforce=1
cal0blank=1
atmosphere=1