Yo guys. So I have a Switch that is fusee gelee exploitable. Updated to 10.0.4 on the sysNAND, made a 29.2 GB partition for emuMMC, and the rest in FAT32. Created emuMMC, boot into emuMMC, and was able to get in. I was able to launch homebrew. The keyword is "was".
Now I can't boot into emuMMC. I send the hekate payload (v5.3.0), choose "Launch", select "CFW - emuMMC" to launch Atmosphere (0.13.0), Atmosphere logo pops up, Nintendo Switch logo pops up, then a blank screen with backlight.
I went back into hekate, made a new emuMMC, tried again, and no difference. Any suggestions? I have a sysNAND backup of when it was 4.1.0, before updating the sysNAND to 10.0.4, and another sysNAND backup after I updated the sysNAND to 10.0.4.
I don't think the sysNAND backup of 4.1.0 is any good, as I've burnt fuses updating the sysNAND through the official servers.
Now I can't boot into emuMMC. I send the hekate payload (v5.3.0), choose "Launch", select "CFW - emuMMC" to launch Atmosphere (0.13.0), Atmosphere logo pops up, Nintendo Switch logo pops up, then a blank screen with backlight.
I went back into hekate, made a new emuMMC, tried again, and no difference. Any suggestions? I have a sysNAND backup of when it was 4.1.0, before updating the sysNAND to 10.0.4, and another sysNAND backup after I updated the sysNAND to 10.0.4.
I don't think the sysNAND backup of 4.1.0 is any good, as I've burnt fuses updating the sysNAND through the official servers.