UPDATE: Everything is working now.
tl;dr I updated sysnand to 12.0.0 (emunand is on 11.0.0). Everything worked initially, but now sysnand won't sleep or dock and emunand gives error when trying to boot.
At the beginning of yesterday, my SX OS emunand was on 11.0.0 and my sysnand was on 11.0.1 . Once the new Hekate/Atmosphere version released, I wanted to update sysnand to 12.0.0 so that I could play online.
This part may or may not be irrelevant, but I want to include it in case it could possible effect anything. I did an oopsie and accidentally updated emunand instead of sysnand. This is a problem, because I'm using SX OS. I'm using file based emunand and I changed to the file names/folder structure that Atmosphere is expecting. I booted into Atmosphere on emunand and downgraded it to 11.0.0 via Daybreak. I changed my emunand back to the file names/folder structure that SX OS is expecting. SX OS emunand boots fine and games are working. At this point, my system is in the same condition that it was at the beginning of the day.
I boot into Atmosphere on sysnand and updated it to 12.0.0 using Daybreak. After restart, everything is working great. I play Splatoon 2 online for bit and everthing is good. A few hours later, I go to play some more Splatoon, but for some reason the system is completely off (it was in the dock the whole time). I inject the payload using the SX Pro dongle, chainload from SX bootloader to Hekate (latest version), and boot into stock sysnand from Hekate. Every appears to boot fine, but whenever I put the system back in the dock, nothing comes up on the TV. The tablet screen stays on after placing it in the dock. It's definitely not an issue of not being fully seated or cables not being hooked up. The system isn't charging in the dock either; it will charge with the cable plugged in directly, though. To add to the weirdness, the system will not sleep. If I hit power button on the console, it will appear to go to sleep, but it won't wake back up later. I have to inject a payload and everything to get the system back up. I figured I would try booting emunand to see if docking/sleep work when using emunand. However, attempting to boot into emunand gives me the SX OS error screen saying that something went wrong and to press power to restart (something to that effect). This is despite the fact that emunand was just working fine (after downgrading with Atmosphere). Does anyone have insight on what could possibly be going wrong here?
- SX OS error was from having a game card inserted on a lower firmware (12.0.0 contained a game card slot update).
- The system not being able to wake from sleep was an 'Atmosphere bug'. I'm assuming something with fusee-secondary because I don't know how else it would affect stock sysnand. Fixed by updating to the latest Atmosphere build files
- The issue with the system not docking appears to have been a physical connection issue that coincidentally happened at the same time as the other issues. It just started working again for no reason.
tl;dr I updated sysnand to 12.0.0 (emunand is on 11.0.0). Everything worked initially, but now sysnand won't sleep or dock and emunand gives error when trying to boot.
At the beginning of yesterday, my SX OS emunand was on 11.0.0 and my sysnand was on 11.0.1 . Once the new Hekate/Atmosphere version released, I wanted to update sysnand to 12.0.0 so that I could play online.
This part may or may not be irrelevant, but I want to include it in case it could possible effect anything. I did an oopsie and accidentally updated emunand instead of sysnand. This is a problem, because I'm using SX OS. I'm using file based emunand and I changed to the file names/folder structure that Atmosphere is expecting. I booted into Atmosphere on emunand and downgraded it to 11.0.0 via Daybreak. I changed my emunand back to the file names/folder structure that SX OS is expecting. SX OS emunand boots fine and games are working. At this point, my system is in the same condition that it was at the beginning of the day.
I boot into Atmosphere on sysnand and updated it to 12.0.0 using Daybreak. After restart, everything is working great. I play Splatoon 2 online for bit and everthing is good. A few hours later, I go to play some more Splatoon, but for some reason the system is completely off (it was in the dock the whole time). I inject the payload using the SX Pro dongle, chainload from SX bootloader to Hekate (latest version), and boot into stock sysnand from Hekate. Every appears to boot fine, but whenever I put the system back in the dock, nothing comes up on the TV. The tablet screen stays on after placing it in the dock. It's definitely not an issue of not being fully seated or cables not being hooked up. The system isn't charging in the dock either; it will charge with the cable plugged in directly, though. To add to the weirdness, the system will not sleep. If I hit power button on the console, it will appear to go to sleep, but it won't wake back up later. I have to inject a payload and everything to get the system back up. I figured I would try booting emunand to see if docking/sleep work when using emunand. However, attempting to boot into emunand gives me the SX OS error screen saying that something went wrong and to press power to restart (something to that effect). This is despite the fact that emunand was just working fine (after downgrading with Atmosphere). Does anyone have insight on what could possibly be going wrong here?
Last edited by CanIHazWarez,
