Cannot read any game cart when in Atmosphere, fatal error when using nogc=0

[simsimsim]

I just switch to atmosphere but none of the game carts I have could be read. Doesn't matter if I re-insert 10 times or reboot. I searched online and found that I need to put [stratosphere] nogc = 0 in the stratosphere.ini which I copied from ConfigTemplates to the config folder under "atmosphere".

However when I did that, upon booting I got a "fata error occurred when running Fusee. Failed to parse stratosphere.ini". Only way I could reboot without this screen is removing the ini file from config. But now I still can't play any of the carts.

Also, I noticed that Checkpoint no longer works despite using the latest version. Is that normal? What's another good save manager beside it? JKSV?

Thanks for your help!

 

[impeeza]

you did edit the stratosphere on a unsupported text editor, use a good one like Notepad++, in order to be sure what you have a good stratosphere.ini file, copy the one inside of a FRESH DOWNLOADED ZIP FROM GITHUB on the path ZIP:/atmosphere\config_templates\stratosphere.ini and copy it to your SD:/atmosphere/config folder, then edit it using Notepad++

if you use MAC remember to fix archive bit on you SD card.


Also, remember to edit Hekate_ipl.ini too if you boot using hekate.

put:

[config] autonogc=0

on it.

 

[Draxzelex]

I just switch to atmosphere but none of the game carts I have could be read. Doesn't matter if I re-insert 10 times or reboot. I searched online and found that I need to put [stratosphere] nogc = 0 in the stratosphere.ini which I copied from ConfigTemplates to the config folder under "atmosphere".

However when I did that, upon booting I got a "fata error occurred when running Fusee. Failed to parse stratosphere.ini". Only way I could reboot without this screen is removing the ini file from config. But now I still can't play any of the carts.

Also, I noticed that Checkpoint no longer works despite using the latest version. Is that normal? What's another good save manager beside it? JKSV?

Thanks for your help!

I recommend asking in the Switch Noobs Paradise instead.

 

[impeeza]

Also, I noticed that Checkpoint no longer works despite using the latest version. Is that normal? What's another good save manager beside it? JKSV?

Nop, the only full functional Save manager now is JKSV. also has been the best for some time ago.

you can use DBI for save management, it's a little bit complex but is a great option. you connect the console to computer and run DBI on MTP responder mode then your PC "See" a device with a Saves folder inside, that folder have a folder for each game and you can copy from/to you computer the save for each profile and BCAT y SYSTEM slots.

also on the console you can use DBI to export individual saves of each game to files on SD.

 

[impeeza]

I recommend asking in the Switch Noobs Paradise instead.

It's true, this question has been answered several times on the noob paradire, the problem is the answers are buried on 3300 posts. ;(

 

[binkinator]

We need a FAQ. I requested and received access to edit the wiki. Thinking about throwing together some common gotchas.

E: would also be helpful to state…this is a problem #37. Please see the wiki.

 

[impeeza]

definitely!!

 

[simsimsim]

you did edit the stratosphere on a unsupported text editor, use a good one like Notepad++ for ensure your have a good stratosphere.ini file. open the one inside of a FRESH DOWNLOADED ZIP FROM GITHUB on the path ZIP:/atmosphere\config_templates\stratosphere.ini and copy it to your SD:/atmosphere/config folder, then edit it using Notepad++

if you use MAC remember to fix bit archive on you SD card.


Also, remember to edit Hekate_ipl.ini too if you boot using hekate.

put:

[config] autonogc=0

on it.

Thanks a lot! Can you please tell me what's the difference between using fusee_primary.bin to boot vs using hekate?

 

[HalfScoper]

Thanks a lot! Can you please tell me what's the difference between using fusee_primary.bin to boot vs using hekate?

If you say "fusee_primary" you should redo your setup with latest files, fusee_primary/secondary isn't used anymore, it's just fusee (and package3) now. Read this for how to: https://rentry.org/MigrateToAtmosphere1_0_0 (ignore the "1_0_0" link part, it's always for latest version available)

To answer the question, hekate is just a step in front of Atmosphere for emuNAND/SD management etc, also needed to chainload fusee on v2 Switches.

 

[impeeza]

ok, again answered a lot of times on Noob Paradise.

fuse_primary.bin WAS the name of fuse.bin file, that file is the bootloader of atmosphere.

Hekate is another bootloader, hekate can load a lot of firmwares, like LAKKA, Android, and of course Atmosphere. Hekate can chainload fuse.bin or package3 files, if your chainload fuse.bin all the process is passed to Atmosphére, if you chainload package3 hekate boot some part of the CFW and the rest is handled by Atmosphere.

so in summary the difference is how to handle the first part of the boot.


is a personal taste. for me I do use:

Hekate -> Package3 boot secuence.

 

[impeeza]

if you are reading/talking about FUSE_PRIMARY.BIN Is likely you are reading a outdated guide or looking a video, STAY AWAY of YouTube videos they always are outdated. use the official guides

https://rentry.org/SwitchHackingIsEasy

our my favorite https://nh-server.github.io/switch-guide/

 

[simsimsim]

if you are reading/talking about FUSE_PRIMARY.BIN Is likely you are reading a outdated guide or looking a video, STAY AWAY of YouTube videos the always are outdated. use the official guides

https://rentry.org/SwitchHackingIsEasy

our my favorite https://nh-server.github.io/switch-guide/

thanks so much!

 

[Stormflora]

Hi. Necrobump, but thread is relevant to my question.

I'd like to boot up some of my old retail game cards again, but that would involve disabling Auto NoGC in Hekate.
Is it safe to do so? What are the possible consequences of burning fuses now, by disabling that?

Or should I seek out and download some copies of the games to run instead?

FWIW, my current official firmware (OFW) version on the stock sysNAND is 8.1.0. That's what came with the console.
The latest firmware of the game cards I have would require OFW 9.0.0.

Thanks!

 

[Hayato213]

Hi. Necrobump, but thread is relevant to my question.

I'd like to boot up some of my old retail game cards again, but that would involve disabling Auto NoGC in Hekate.
Is it safe to do so? What are the possible consequences of burning fuses now, by disabling that?

Or should I seek out and download some copies of the games to run instead?

FWIW, my current official firmware (OFW) version on the stock sysNAND is 8.1.0. That's what came with the console.
The latest firmware of the game cards I have would require OFW 9.0.0.

Thanks!

9.0.0 updated the game cart controller (Lotus) firmware), so you need to burn the gamecard fuse if you want to use the cartridge slot, you can either disable nogc, or boot into stock NAND and insert the cartridge if you are on firmware 9.0.0.

From Atmosphere 9.4 release notes:

• Please note: 9.0.0 updated the switch's gamecart controller ("lotus") firmware.
  • To prevent the burning of lotus fuses, Atmosphere now applies nogc patches when booting into 9.0.0 with fuses below 9.0.0.
  • If you wish to play gamecarts on 9.0.0 (but forever prevent yourself from playing them on < 9.0.0), set nogc = 0 in BCT.ini.

 

[Stormflora]

9.0.0 updated the game cart controller (Lotus) firmware), so you need to burn the gamecard fuse if you want to use the cartridge slot, you can either disable nogc, or boot into stock NAND and insert the cartridge if you are on firmware 9.0.0.

From Atmosphere 9.4 release notes:

• Please note: 9.0.0 updated the switch's gamecart controller ("lotus") firmware.
  • To prevent the burning of lotus fuses, Atmosphere now applies nogc patches when booting into 9.0.0 with fuses below 9.0.0.
  • If you wish to play gamecarts on 9.0.0 (but forever prevent yourself from playing them on < 9.0.0), set nogc = 0 in BCT.ini.

Hi there, thank you for the quick response! I did a bit more research, reading through some of the pages here, and I have a better understanding of what Auto NoGC does now.

Considering how old the Switch is and how it seems like nothing's really going to change from here, I don't really mind burning some fuses to upgrade the GC slot to 9.0.0 to boot up my cards again.

However, with my OFW on 8.1.0, is there any way to manually update the OFW to 9.0.0 to prevent OS FW and GC FW confusion? Or is that impossible? (For reference, my emuNAND CFW is currently updated to the newest OFW available.)

If there isn't, then I assume it means the GC slot would be permanently disabled for the sysNAND, effectively making the OFW useless to go back to except for digitally installed games (unless I were to update the OFW online to the latest version).

Post automatically merged: Aug 7, 2024

Update: Did some more research. Apparently, you can boot up the sysMMC through Hekate with Atmosphere's CFW, and then use Daybreak to install whatever OFW it is you desire? Would that work in updating the OFW to my own desired firmware level?

 

[Hayato213]

Hi there, thank you for the quick response! I did a bit more research, reading through some of the pages here, and I have a better understanding of what Auto NoGC does now.

Considering how old the Switch is and how it seems like nothing's really going to change from here, I don't really mind burning some fuses to upgrade the GC slot to 9.0.0 to boot up my cards again.

However, with my OFW on 8.1.0, is there any way to manually update the OFW to 9.0.0 to prevent OS FW and GC FW confusion? Or is that impossible? (For reference, my emuNAND CFW is currently updated to the newest OFW available.)

If there isn't, then I assume it means the GC slot would be permanently disabled for the sysNAND, effectively making the OFW useless to go back to except for digitally installed games (unless I were to update the OFW online to the latest version).

The game cart slot firmware is separate from the NAND firmware, so for example if you if your OFW/Sysnand firmware is 9.0.0 and your cartridge slot firmware is at a lower lotus firmware, if you disable nogc or boot into stock and load the cart then you would burn the lotus firmware, I know 9.0.0 update had a lotus firmware update.

 

[Stormflora]

The game cart slot firmware is separate from the NAND firmware, so for example if you if your OFW/Sysnand firmware is 9.0.0 and your cartridge slot firmware is at a lower lotus firmware, if you disable nogc or boot into stock and load the cart then you would burn the lotus firmware, I know 9.0.0 update had a lotus firmware update.

I made a minor edit to my previous post, which I think you may have missed.

That being said, it seems OFW 9.0.0 came out five years ago, so unless the GC FW has been updated again at any point since then, it's probably a non-issue to disable Auto NoGC now since Nintendo probably doesn't care about the GC slot anymore.

I don't think anyone would ever need to downgrade or keep their OS or GC FW below 9.0.0 at this point in time xD

 

[Hayato213]

I made a minor edit to my previous post, which I think you may have missed.

That being said, it seems OFW 9.0.0 came out five years ago, so unless the GC FW has been updated again at any point since then, it's probably a non-issue to disable Auto NoGC now since Nintendo probably doesn't care about the GC slot anymore.

I don't think anyone would ever need to downgrade or keep their OS or GC FW below 9.0.0 at this point in time xD

Some people like to have NAND backup of older firmware, but the point is if you update your cart slot firmware then you won't be able to use cart slot if you go back from a higher firmware to a lower firmware. Below are the system firmware that had a cart slot firmware update.

ReadFw​

Code for reading retail Gamecards. Only the normal and secure Gamecard modes are supported.

Found inside FS.

[4.0.0+] This firmware blob was updated to provide support for new Gamecards.
[9.0.0+] This firmware blob was updated.
[11.0.0+] This firmware blob was updated.
[12.0.0+] This firmware blob was updated.
[14.0.0+] This firmware blob was updated.

 

[Stormflora]

Some people like to have NAND backup of older firmware, but the point is if you update your cart slot firmware then you won't be able to use cart slot if you go back from a higher firmware to a lower firmware. Below are the system firmware that had a cart slot firmware update.

ReadFw​

Code for reading retail Gamecards. Only the normal and secure Gamecard modes are supported.

Found inside FS.

[4.0.0+] This firmware blob was updated to provide support for new Gamecards.
[9.0.0+] This firmware blob was updated.
[11.0.0+] This firmware blob was updated.
[12.0.0+] This firmware blob was updated.
[14.0.0+] This firmware blob was updated.

I see. So basically, if a game is more recent and I want to use the physical game card, I would need to install newer firmware on both the OS as well as the GC slot. That's useful to keep in mind.

For the time being, it seems I only need to update the OFW to 9.0.0, so I'll start with that for now. Thanks a bunch!

 

[Hayato213]

I see. So basically, if a game is more recent and I want to use the physical game card, I would need to install newer firmware on both the OS as well as the GC slot. That's useful to keep in mind.

For the time being, it seems I only need to update the OFW to 9.0.0, so I'll start with that for now. Thanks a bunch!

Yeah you would have to update the system firmware and the lotus firmware, the cartridge slot also have it own anti downgrade purpose like the OS firmware have it fuses, for anti downgrade, if you burnt the system firmware fuses and you downgrade to a much lower firmware the system won't boot.