Hacking Atmosphere-NX - Custom Firmware in development by SciresM

Solo761

Active Member
Newcomer
Joined
Jul 11, 2009
Messages
29
Trophies
1
XP
314
Country
Croatia
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.

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.



@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...

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...
 

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,897
Trophies
1
XP
20,849
Country
United States
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.
 

Solo761

Active Member
Newcomer
Joined
Jul 11, 2009
Messages
29
Trophies
1
XP
314
Country
Croatia
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.

Not just slower, I could live with that, but it was unreliable. In the end I wanted to go back to SX OS, but figured I'd try with older Hekate just to see what will happen and... it happened. So far everything I tried worked fine so I'm staying with Atmosphere it seems.


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.

This one has OK speed. Around 90 MB/s read and when I install something over USB it writes it at 35-45 MB/s, it actually depends on cable, I had one that I use for my cell phones, braided, thick, supposedly of quality and I get 35 MB/s with it. Today my cell phone was charging so I grabbed one from my drawer and now I get 42-45 MB/s... Same USB port on my PC... Crazy.

As for spotty drives I have few 64 GB AData USB 3.0 flash drives. Read speed is about 20 MB/s, write is around 2 MB/s. If it was any slower it would go backwards :ha:
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,323
Trophies
3
Age
46
Location
At my chair.
XP
18,585
Country
Colombia
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

you should read the thread about sigpatches:

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.

on that thread several people having similar issues have found answer.
 

Vultix93

Well-Known Member
Newcomer
Joined
Dec 9, 2014
Messages
96
Trophies
0
Age
31
XP
479
Country
Italy
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
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,323
Trophies
3
Age
46
Location
At my chair.
XP
18,585
Country
Colombia
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.
 
Last edited by impeeza,

Vultix93

Well-Known Member
Newcomer
Joined
Dec 9, 2014
Messages
96
Trophies
0
Age
31
XP
479
Country
Italy

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,323
Trophies
3
Age
46
Location
At my chair.
XP
18,585
Country
Colombia
Thanks, updating the sigpatches worked, I was sure I already did that but apparently, I forgot. Some homebrews still don't work though
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.

Today almost all homebrew I use are updated to newest libraries. Or have several people working on it.

So please read the release page of the homebrew you want to use and update them properly. If you found a non updated homebrew, you can:
  • Read if there is not a currently open issue for it and politely ask for update.
  • Make changes to the code, recompile and propose the corresponding comits to code.
  • Look for updated forks.
 
Last edited by impeeza,

CaptainHIT

Well-Known Member
Member
Joined
Mar 2, 2011
Messages
384
Trophies
1
Age
47
Location
Frankfurt
XP
1,453
Country
Germany
Ok, tried it again, this time I remembered something about the hekate_ipl.ini. I compared both my old ini file and the one from the fresh install.
There is an entry in the emuMMC section: "kip1=atmosphere/kips/*"
In my older install it is: "kip1=nosigchk"

After changing this, the problems are gone!
 
Last edited by CaptainHIT,

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,323
Trophies
3
Age
46
Location
At my chair.
XP
18,585
Country
Colombia

mondul

Well-Known Member
Member
Joined
Aug 8, 2018
Messages
126
Trophies
0
Age
40
Location
Barranquilla
XP
895
Country
Colombia
New Atmosphere is out.

0.19.3 is Atmosphère's forty-ninth official release.

fusee-primary was last updated in: 0.19.3.

With thanks to the @switchbrew team, Atmosphère 0.19.3 is bundled with hbl 2.4.1, and hbmenu 3.4.0.

The following was changed since the last release:

  • Support was added for 12.0.2.
  • A number of minor issues were fixed, including:
    • An issue was fixed in dns.mitm that caused a crash when games attempted to resolve the IP address of nullptr.
    • An issue was fixed in erpt that would cause an abort when booting without having ever booted stock previously.
    • An issue was fixed in (file-based) emummc that caused an error on system format/downloading certain games.
  • General system stability improvements to enhance the user's experience.
Download from here:
https://github.com/Atmosphere-NX/Atmosphere/releases/tag/0.19.3
 
Last edited by mondul, , Reason: Add release info
  • Like
Reactions: Tyvar1 and Mata84

Baoulettes

The lonely man
Member
Joined
May 25, 2011
Messages
836
Trophies
1
Age
33
Location
C:\Users\Baoulettes\Desktop\GBATemp
Website
www.baoulettes.fr
XP
2,287
Country
France
No idea if that the right place but I guess it is,
Since latest update of Atmo I have quite some issues :
First the most annoying :
Unable to read game card.
So before explaining more I will tell step by step what I did :

I was on 12.0.1 FW with Atmo 0.19.1
It worked fine without error just since it was updated to support latest FW I said "why not"

I have first updated Atmo to 0.19.3 here without issues
(every time I empty my content folder so it force me to update my homebrew)

Since it was working fine there I proceed to update FW with official method (Settings-console-update)
It boot fine but now I am unable to make it read any games from card slot (so definitely a legit game)

I tried rebooting etc no change.
I tried to shutdown and start again after some seconds
I tried several different game from Mario kart 8 to Zelda with Mario Maker.
I tried booting original FW ( I do not care about burnt fuse)

What could cause the reader to actually not read games?

PS: I have absolutely zero nsp installed and do not plan to do any sort of workaround or things, I use Atmo only for tesla menu.
Also I never downgrade or anything so in theory the FW should be pretty clean from games card reader issue ?
 

petspeed

Well-Known Member
Member
Joined
Nov 13, 2009
Messages
1,128
Trophies
1
Age
49
XP
1,735
Country
Denmark
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)
Copy BCT.INI from E:\atmosphere\config_templates\ to E:\atmosphere\config\
Edit the file and add this under the [stratosphere] section:
nogc = 0

If you use Hekate to boot CFW you might also need to make sure that you have this in your hekate_ipl.ini:
autonogc = 0
 

mattyxarope

Well-Known Member
Member
Joined
Jan 15, 2019
Messages
544
Trophies
0
XP
1,995
Country
United States
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...
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    SylverReZ @ SylverReZ: @salazarcosplay, I'm here.