Stock MMC still works also

If your SysNAND works fine but your EmuNAND doesn't work anymore, try backing up your current EmuNAND to somewhere safe and recreate your EmuNAND to make sure it isn't just a corruption issue or anything like that with the EmuNAND

same issue, was working right before updating to 1.5.4

Do a factory reset and a new emunand

Do a factory reset and a new emunand

ended up having to do this unfortunately

Do a factory reset and a new emunand

ended up having to do this unfortunately

Have you sorted out what the problem is?
I just followed re-entry guide for a clean emunand install. I have same issue. Started as hekate IPL loading bar --> atmosphere logo maybe like 1 sec blimp --> everything goes black --> had to power off switch and inject payload via Tegra again

All latest releases

Also having this issue. If someone finds out a solution that isn't nuclear (factory reset), would appreciate it lots.

Solutions I have tried (None of which have worked)

1. Manually downloading the newest fusee from the github and using that instead
2. Deleting the contents folder of atmosphere
3. Deleting ONLY the Atmosphere, bootloader, Config, Switch folders from the SD card, then dragging them back on from the zip I downloaded from SD Setup
4. Scanning and repairing the drive on Windows (Windows said there was no issues)
5. Injecting fusee directly and not using the hektate bootscreen
6. Using emuMMC (this causes an entirely different error: (Failed to identify FS version)
7. Formatting SD card, fresh install of all files.
8. Getting a new download of Hekate, even though the payload I was using was the same version (6.0.3)
9. Waiting for atmos to boot by leaving my switch alone after launching the fusee payload (someone told me to wait 5 minutes, I waited 30 minutes and nothing)

I fixed the issue by just getting a brand new SD card, and starting over the installs from zero. It seems that my old one had corrupt files that Windows could not delete properly, and that were not caught in the scan and repair.

Fresh SD card worked perfectly.

same issue tried everything mentions above, everything up to date idk whats the problem tbh . tried to boot trough hekate with the fusee.bin(taking the same updated fusee.nin everywhere).My root folder looks like this. At this point might be my sd card. Nobody got an idea or a suggestions before wiping ?

same issue tried everything mentions above, everything up to date idk whats the problem tbh . tried to boot trough hekate with the fusee.bin(taking the same updated fusee.nin everywhere).My root folder looks like this. At this point might be my sd card. Nobody got an idea or a suggestions before wiping ?

Your atmosphere folder (among others) hasn't been updated since 2020. Have you downloaded the newest version?

Yes I did it just keep de modified date to 2020 idk why tho but I did it its weird

Move your existing SD card contents to a different place, set the card up again like you would if you were just setting up atmosphere, and see if it happens again.

Ok will try it

No new install. Just fixed it by using another fusee.bin as payload to inject: #2192

Same issue on 1.6.2. with RCM. How to resolve? I already reformat my SD and download new fusee.bin

I'm the same.
I was on FW16.0.3/1.5.5 on EmuMMC partition (on FAT32 SD card) on unpatched HAC-001.
I tried updating to 16.1.0 as I would normally:

• dl'd 16.1.0 and extracted to fw folder on sd
• update Hekate to 6.0.7 and that seemed good
• updated Atmosphere to 1.6.2 with latest sigpatches, put the card into the switch and booted into CFW all ok.
• R+game to launch non-applet mode -> Daybreak and installed 16.1.0 (accidently chose FAT32+exFAT - but I don't think that should matter).
• it said it installed fine, rebooted and it flashes Atmosphere logo for 1/2 second and only blank screen.

much swearing, tried 1.6.2's fusee and lots of different hekate_ipl.ini mentioned online, and always black screen. Tried removing/renaming the Atmosphere/contents folder (as some have suggested), but still black screen.

• Tried OFW and that works, so it's not bricked the Switch.
• Went back to Hakate and restored EmuMMC back to FW16.0.3 and working fine.
• re-installed Atmosphere 1.6.2, this time from a AIO package - booted and worked fine.
• re-dl'd FW16.1.0 from a new location.
• non-applet Daybreak again and installed with FAT32 only option
• still the same - flash of Atmosphere logo and black screen.

I feel like I've tried everything apart from a clean format of the SD card. But, I'd be restoring from the same FW16.0.3 backup, so I think the partition would still be in the same state?

I'm 1/2 wanting to try FW17.0.0 but with the comments about bricking loops/issues then I'm wondering if what's causing 16.1.0 to be issue will still occur on 17.0.0?

Is something dodgy? or what more can I try? Is 16.1.0 checking for fuses that aren't burnt via Daybreak, or something silly like that?

Deleted commend containing warez stuff. Also, please do not coopt other people's issues.

Same behaviour after updating atmosphere, hekate and sigpatches but NOT firmware to all latest versions; solution in my csae was rolling back the files in the atmosphere folder to the previous 1.5.5 ones I had, now emucc working again.

UPDATE: Took the chance and updated to 17.0 while on atm 1.5.5 and then update to 1.6.2 and the black screen no longer shows.

so what did you do to fix it bc im having this problem

what worked for me its updating atmoshphere to another version and it worked, maybe the atmsh version i had wasnt compatible.

Same behaviour after updating atmosphere, hekate and sigpatches but NOT firmware to all latest versions; solution in my csae was rolling back the files in the atmosphere folder to the previous 1.5.5 ones I had, now emucc working again.

UPDATE: Took the chance and updated to 17.0 while on atm 1.5.5 and then update to 1.6.2 and the black screen no longer shows.

Thanks for including this reply. I was having similar issues going from 1.5.4/16.0.3 -> 1.6.2 (before upgrading to 17.0.1) and just getting a black screen after the atmosphere logo. On a prayer, rolled back to 1.5.4 and booted right up so came looking for answers. Found your post, upgraded to 17.0.1 (didn't boot of course) and then manually upgraded atmosphere to 1.6.2 and boom, all good!

(I had already upgraded sigpatches to the version that supported 1.6.2 when I downgraded to 1.5.4. Research told me they were backwards compatible so I did not search out what I was using for 1.5.4 and did not touch them again during this process)

Same behaviour after updating atmosphere, hekate and sigpatches but NOT firmware to all latest versions; solution in my csae was rolling back the files in the atmosphere folder to the previous 1.5.5 ones I had, now emucc working again.
UPDATE: Took the chance and updated to 17.0 while on atm 1.5.5 and then update to 1.6.2 and the black screen no longer shows.

Thanks for including this reply. I was having similar issues going from 1.5.4/16.0.3 -> 1.6.2 (before upgrading to 17.0.1) and just getting a black screen after the atmosphere logo. On a prayer, rolled back to 1.5.4 and booted right up so came looking for answers. Found your post, upgraded to 17.0.1 (didn't boot of course) and then manually upgraded atmosphere to 1.6.2 and boom, all good!

(I had already upgraded sigpatches to the version that supported 1.6.2 when I downgraded to 1.5.4. Research told me they were backwards compatible so I did not search out what I was using for 1.5.4 and did not touch them again during this process)

i had a panic error show up when i booted to atmosphere, and after looking online i applied a fix by pressing "Fix Archive Bit" button in hekate. now i have a the same problem you had where after launching sysmmc cfw, the atmosphere would show for a few seconds and a black screen would appear. (weirdly, my PC said "setting up 'Nintendo Switch'/ 'Nintendo Switch' is ready to go" after the switch went to a black screen). I'll try downgrading Atmosphere to 1.5.4 never had a previous version of atmosphere as I was following a video guide on how to restore HOS using a donor nand.

Had the same problem on switch lite.
To avoid black screen follow this:

Update Atmosphere through AIOupdater and after that update the firmware through Daybreak.This way there is no problem with black screen.

After that i got the Error 2123-0011 that is triggering when the wifi is on.
(Nintendo did some NEXT LEVEL PIRATE PREVENTION TACTICS)
You can simply fix it by doing the Exosphere and DNS MITM settings from the Rentry guide.

After these fixes the switch is again top notch.

[ADDITIONAL INFO]
On update 17.0.1,the black screen on boot appears when you update atmosphere manually.Thus you need to update through AIOupdater.

To avoid being in bad situation after atmosphere update,first backup atmosphere,bootloader and switch folder on your pc in case you get black screen.This way you can pop out your sd card and overwrite the files and have your system working again with the previous atmosphere version.

"Im here to kick errors and chew ass.And im all OUTTA ERRORS"

Had the same problem on switch lite. To avoid black screen follow this:

Update Atmosphere through AIOupdater and after that update the firmware through Daybreak.This way there is no problem with black screen.

After that i got the Error 2123-0011 that is triggering when the wifi is on. (Nintendo did some NEXT LEVEL PIRATE PREVENTION TACTICS) You can simply fix it by doing the Exosphere and DNS MITM settings from the Rentry guide.

After these fixes the switch is again top notch.

[ADDITIONAL INFO] On update 17.0.1,the black screen on boot appears when you update atmosphere manually.Thus you need to update through AIOupdater.

To avoid being in bad situation after atmosphere update,first backup atmosphere,bootloader and switch folder on your pc in case you get black screen.This way you can pop out your sd card and overwrite the files and have your system working again with the previous atmosphere version.

"Im here to kick errors and chew ass.And im all OUTTA ERRORS"
I have actually fixed the issue by just redoing the YouTube guide but instead using firmware 16.1.0 that the YouTuber suggested to me. Thanks for the info, never knew there was such a thing as an AIO updater, interesting. Now my problem is that my switch is practically banned as i found-out/should've-realized it can't connect to the eshop or anything online as I used a donor prodinfo and nand as I was too incompetent to realize I should've backed up the nand before wiping it for lineage os android (long story). I don't really know what to use my practically forever banned switch for, maybe Linux, dunno really.

Had the same problem on switch lite. To avoid black screen follow this:

Update Atmosphere through AIOupdater and after that update the firmware through Daybreak.This way there is no problem with black screen.

After that i got the Error 2123-0011 that is triggering when the wifi is on. (Nintendo did some NEXT LEVEL PIRATE PREVENTION TACTICS) You can simply fix it by doing the Exosphere and DNS MITM settings from the Rentry guide.

After these fixes the switch is again top notch.

[ADDITIONAL INFO] On update 17.0.1,the black screen on boot appears when you update atmosphere manually.Thus you need to update through AIOupdater.

To avoid being in bad situation after atmosphere update,first backup atmosphere,bootloader and switch folder on your pc in case you get black screen.This way you can pop out your sd card and overwrite the files and have your system working again with the previous atmosphere version.

"Im here to kick errors and chew ass.And im all OUTTA ERRORS"

I don't really agree with this methodology because it did not echo my experience. Just FYI for others reading.

I initially upgraded atmosphere from 1.5.4 -> 1.6.2 using AIOUpdater and updated sigpatches manually. Rebooted, expecting v1.6.2 atmopshere to still work with v16.0.3 of firmware. This did not work. This resulted in the black screen.

What fixed it was manually downgrading back to 1.5.4. Upgrading firmware to v17.0.1 with Daybreak and then manually upgrading to 1.6.2. Manual upgrade to 1.6.2 at this point is required because CFW won't boot of course with new firmware and old atmosphere.

At no point was AIO Updater an actual solution for this issue. It wasn't the problem. But it wasn't the solution either. If you update to v1.6.2 in AIO Updater (updating sigpatches however you want) and then reboot, in my experience, you will be dead in the water. If AIO Updater allowed you to update to 1.6.2 and then you hopped over and upgraded firmware to 17.0.1 without rebooting until firmware was updated, that'd probably work, but AIO Updater forces a reboot after upgrading atmosphere in this scenario.

Usually updating atmosphere + sigpatches ahead of firmware and rebooting is fine. Something was different this time. I did want to point out that in my experience, on my particular version path, there is no way to upgrade atmosphere with AIO Updater and then use Daybreak successfully. It was not possible.

Had the same problem on switch lite. To avoid black screen follow this:
Update Atmosphere through AIOupdater and after that update the firmware through Daybreak.This way there is no problem with black screen.
After that i got the Error 2123-0011 that is triggering when the wifi is on. (Nintendo did some NEXT LEVEL PIRATE PREVENTION TACTICS) You can simply fix it by doing the Exosphere and DNS MITM settings from the Rentry guide.
After these fixes the switch is again top notch.
[ADDITIONAL INFO] On update 17.0.1,the black screen on boot appears when you update atmosphere manually.Thus you need to update through AIOupdater.
To avoid being in bad situation after atmosphere update,first backup atmosphere,bootloader and switch folder on your pc in case you get black screen.This way you can pop out your sd card and overwrite the files and have your system working again with the previous atmosphere version.
"Im here to kick errors and chew ass.And im all OUTTA ERRORS"

I don't really agree with this methodology because it did not echo my experience. Just FYI for others reading.

I initially upgraded atmosphere from 1.5.4 -> 1.6.2 using AIOUpdater and updated sigpatches manually. Rebooted, expecting v1.6.2 atmopshere to still work with v16.0.3 of firmware. This did not work. This resulted in the black screen.

What fixed it was manually downgrading back to 1.5.4. Upgrading firmware to v17.0.1 with Daybreak and then manually upgrading to 1.6.2. Manual upgrade to 1.6.2 at this point is required because CFW won't boot of course with new firmware and old atmosphere.

At no point was AIO Updater an actual solution for this issue. It wasn't the problem. But it wasn't the solution either. If you update to v1.6.2 in AIO Updater (updating sigpatches however you want) and then reboot, in my experience, you will be dead in the water. If AIO Updater allowed you to update to 1.6.2 and then you hopped over and upgraded firmware to 17.0.1 without rebooting until firmware was updated, that'd probably work, but AIO Updater forces a reboot after upgrading atmosphere in this scenario.

Usually updating atmosphere + sigpatches ahead of firmware and rebooting is fine. Something was different this time. I did want to point out that in my experience, on my particular version path, there is no way to upgrade atmosphere with AIO Updater and then use Daybreak successfully. It was not possible.

Man i wish github has some kind of flowchart feature. that could realy make it easier to comprehend the workaround that's needed to fix the black screen

I am getting the same issue after updating to 1.6.2. On firmware 16.0.1. Happens with both sysMMC and emuMMC. Only thing that works is downgrading back to AMS 1.5.5.

Is AMS 1.6.2 broken on firmware 16.0.1?
I would rather not risk updating my firmware to 17.0.1 and be stuck without working CFW.

I am getting the same issue after updating to 1.6.2. On firmware 16.0.1. Happens with both sysMMC and emuMMC. Only thing that works is downgrading back to AMS 1.5.5.

Is AMS 1.6.2 broken on firmware 16.0.1? I would rather not risk updating my firmware to 17.0.1 and be stuck without working CFW.

No idea but all I can say is my process worked. I know it's a risk but it's not like you are risking bricking it or something.

Figured my issue out. I forgot to update fusee haha. Nevermind me!