- Joined
- Aug 6, 2017
- Messages
- 19,244
- Solutions
- 7
- Reaction score
- 10,211
- Trophies
- 2
- Age
- 32
- Location
- New York City
- XP
- 14,111
- Country

You used the very buggy and problematic AIO Updater, that's what. I don't know who or what told you to use that bad tool but it is most likely the root cause of your issues. I would first recommend deleting it. Then I would recommend deleting everything from your SD card except the Nintendo folder just to remove any traces of what the AIO Updater may have installed. Then download a fresh set of files from the official Atmosphere GitHub. Now to turn the console back on, when you say you power cycled it, did you perform a normal shutdown or a manual shutdown? If its the former, then you will have to perform a manual shutdown by holding the power button for 15 seconds. If you already performed one, try performing another one then turning the console back on.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?








