Well, I thought I was doing this right.
Updated atmosphere and hekate, far as I understood it via the AIO updater. Updated the sys-patch and sigpatches. Waited this long to see if there were any issues propping up regarding the 17.0.0 firmware, but didn't see any.
Downloaded, and use Daybreak to update it (emucfw). At first, it was just atmosphere giving me an error screen and prompting me to reboot or reload to hekate. Noticed the error code it displayed on this screen and since it kept repeating, I followed This result to power cycle the thing. And... now it won't turn on. Even if I plug in the rcmloader, I get nothing.
... What the heck do I do?
Updated atmosphere and hekate, far as I understood it via the AIO updater. Updated the sys-patch and sigpatches. Waited this long to see if there were any issues propping up regarding the 17.0.0 firmware, but didn't see any.
Downloaded, and use Daybreak to update it (emucfw). At first, it was just atmosphere giving me an error screen and prompting me to reboot or reload to hekate. Noticed the error code it displayed on this screen and since it kept repeating, I followed This result to power cycle the thing. And... now it won't turn on. Even if I plug in the rcmloader, I get nothing.
... What the heck do I do?