Nearly 2 years iirc. I bought it together with Links Awakening when it was released.How old is it?
Last edited by CaptainHIT,
Nearly 2 years iirc. I bought it together with Links Awakening when it was released.How old is it?
I would recommend going the FAT32 route, I mean everything can be done in FAT32, you have no need of exFAT, exFAT is probably the reason you are getting the black screen, Also you should go with highest available Atmosphere build if you have a sysnand version on 2.0.0 to 4.1.0, as the 0.19.1 build had a problem with it.
@Solo761 we're kind of hijacking the thread here. Please start a new thread to continue, or point me to it, if you already have. Your SD isn't stuck in 1bit either, so it's not a hardware problem (at least not with the sd or sd slot... could be a RAM problem). It's probably either file corruption (switching from fat32 to exfat and back won't do you any favors if you're copying the same corrupted file back and forth), or something silly like a theme, sys module, or game cart slot firmware...
As I mentioned, I tried exFAT AND FAT32 multiple times with same result. And I also used latest hekate and Atmosphere release.
With this Kingston card only emuMMC in file worked. But I've run into new problems with that. It turns out with Atmosphere using file based emuMMC is highely unreliable. Tried to copy stuff from memory card and Atmosphere crashed, again, multiple times.
I didn't exactly "switch" from FAT32 to exFAT, every time I did that that mean complete format of SD card and CFW setup from zero. It wasn't just copy everything from SD to HDD, format and copy back to SD.
Today I tried few more times but again the same. Doesn't work with Kingston SD, but works with Samsung SD...
But I got an idea thought to try just once more...
This time I used Hekate 5.5.4, instead of latest 5.5.5, to reformat my SD card, prepare emuMMC partition and create. After that I repeated the usual procedure and this time it worked WITHOUT PROBLEMS. CFW booted fine from emuMMC on Kingston card. After that I updated emuMMC firmware to 12.0.1 using Daybreak. I had few demos in my sysNAND that were passed to emuNAND and since fw 10.0 implemented option to transfer games from SD to internal and vice-versa I tried that and it also worked without problems. In multiple "directions". I also managed to update to 12.0.1 with file based emuNAND, but this transfer of games would crash Atmosphere after few hundreds of megabytes.
So all in all, if someone else stumbles on black screen on emuMMC setup (on clean SD), try older Hekate version. It seems something changed in SD routines in 5.5.5 that corrupted firmware while it was copied to emuMMC with this flavour of SD card. In my case 5.5.4, one version "older" was enough to avoid the issue.
After I created partition and copied fw with Hekate 5.5.4 I updated it to 5.5.5, copied Atmosphere files to main parition and it still worked fine. So it seems there was some issue with how Hekate 5.5.5 does this process...
It probably have something to do with the SD, I never used any Kingston one, only Samsung and Sandisk so far for me. File based is slower compared to partition based.
At work we had some sandisk cards that had absolutely terrible performance, which I always figured were fake but they came through the normal distributor and so we could never prove anything. The only visible difference was they had a different country, so it might be that sandisk themselves ended up getting done over when they contracted that factory.
Write speed was incredibly lumpy and we were barely writing anything.
I've tried and searched alot to find a solution by myeself but I think I need help:
After I've updated my (RCM-able) Switch to 12.0.1 I've formatted my 400GB Sandisk Ultra microSD and wanted to start a fresh new emuMMC. This card already had emuMMC, but was done by hand (created after the switch hacking guide) prior Hekate's emuMMC creation tools were even built in.
Well, I've cleaned the partitions, formatted it as FAT32 (32k clustersize) and then started everything from scratch again with the switch hacking guide.
Everything went out right of course, I also put in the latest sigpatches, but when I want to install something, doesn't matter if old or new software, doesn't matter if Goldleaf or Awoo-Installer, doesn't matter if trying to install to SD or internal memory, I always get the same error.
It's the latest Atmosphere, Hekate, sigpatches on emuMMC.
View attachment 261798 View attachment 261795 View attachment 261797
I got some errors too but on SoS Pioneers, Pkmn Sw and Zelda BoW. Tried different google sources nsp and xci.
Found the problem with DBI, some updates messes with file (or tickets I do not know, just got them with checking and as result got hash errors). So messing with upd uninstalling it on xci, or applying dlc after install base on nsp got errors.
My solution was get xci bundle from google sources and play it until the game breaks not the best solution but so far Im still playing them.
Maybe, as Impeeza mentioned, some games have rushed dump and sites (or shops) are not interested to review or redump so you need to find a good one to make it work.
So haven't updated in a while, my system is on EMUMMC 10.2.0, and decided to update Atmosphere first and then pass it to the firmware. After installing Atmosphere 19.2 most of my homebrew don't work. I can't open Checkpoint, ChoiDujourNX( so I can't update), HB App store, and some others. What I'm supposed to do?
Games works fine though
You must to update the sigpatches. Search the web or go to https://gbatemp.net/threads/sigpatc...ate-fss0-fusee-primary-fusee-secondary.571543
By the way, until ChoiDujourNX get updated you must use Daydream to upgrade the firmware.
Most of the hombrew should be updated to the new libraries. Is stated on the atmosphère release page and and almost every post related to atmosphère and 12.x firmware.Thanks, updating the sigpatches worked, I was sure I already did that but apparently, I forgot. Some homebrews still don't work though
you should read the thread about sigpatches:
on that thread several people having similar issues have found answer.
I have it only in E:\atmosphere\config_templates\ (E being my SD Card for Switch)Do you have a bct.ini?
https://github.com/Atmosphere-NX/Atmosphere/issues/794
Copy BCT.INI from E:\atmosphere\config_templates\ to E:\atmosphere\config\I have it only in E:\atmosphere\config_templates\ (E being my SD Card for Switch)
And never edited anything there (also downloaded game work fine)
What happens when you get the error? Does the switch reboot?Does anyone have a problem upon first booting? The first title I try always errors out, but from then on I can choose any title successfully...