Hacking Updated to 9.0.0 with cfw, but now i cant play my carts

[samedifference]

Similar problem here, recently upgraded from 7.0.1 directly to 9.1.0 only to find that I can't actually play my carts anymore (error message). I'm running the latest Atmosphere release through hekate + fusee-primary, and I've attempted to disable the AutoNoGC setting in hekate's bootloader, along with manually editing BCT.ini on my SD card to have the nogc flag added, but even after rebooting, my game carts can't be read. I've also tried reinstalling the 9.1.0 update a few times to no avail, even when the flags are set correctly.

 

[bad361]

Similar problem here, recently upgraded from 7.0.1 directly to 9.1.0 only to find that I can't actually play my carts anymore (error message). I'm running the latest Atmosphere release through hekate + fusee-primary, and I've attempted to disable the AutoNoGC setting in hekate's bootloader, along with manually editing BCT.ini on my SD card to have the nogc flag added, but even after rebooting, my game carts can't be read. I've also tried reinstalling the 9.1.0 update a few times to no avail, even when the flags are set correctly.

If you use fusee, there's no reason to edit nogc option in hekate... Where's your BCT.ini located and show contents cause everything works after editing BCT config. Im on 9.1, latest atmos.

 

[kantaroo]

I just went thought this process myself so I thought I'd post about my experience even if all it does is reveal that I am a complete Noob. I used the Hekate menu to disable nogc and then booted onto eMMC. But the game card still didn't work the first time around. I did it again and it turned out to be a very simple mistake I was making: in the Hekate menu, where you disable nogc, you have to exit by clicking on the "save options" button. If you disable nogc but don't save your options and just go back to the home menu, then it will simply ignore your selection and keep nogc enabled.
I know it was obvious, but I thought I would share just in case the same step is stumping anyone else.

 

[grcd]

Can someone clarify if there is any way to make the game card reader work when going from 8.1.0 to 9.0.1 without having to stay on 9.0+ permanently afterwards for the game card reader to work?

 

[Lacius]

Can someone clarify if there is any way to make the game card reader work when going from 8.1.0 to 9.0.1 without having to stay on 9.0+ permanently afterwards for the game card reader to work?

No, you have to make a choice.

 

[grcd]

No, you have to make a choice.

So, effectively, if I plan to ever revert I must lose game card functionality?

Should fuses for the CPU be burnt also?

 

[Lacius]

So, effectively, if I plan to ever revert I must lose game card functionality?

That's right, unless you want to forego gamecard usage while on 9.x.

It should be noted that you're highly unlikely to have a need to downgrade in the future, and if you were to downgrade, you wouldn't be able to play newer games anyway. Also, downgrading your sysNAND to a lower version and then booting an up-to-date emuNAND will allow you to use the gamecard slot. In other words, if you have game cartridges you want to use, then there isn't too much of a reason not to burn your gamecart slot fuses.

The only reason I can think of why you might downgrade is for a future exploit, and you will be using that exploit to boot an up-to-date emuNAND with gamecart functionality anyway.

Should fuses for the CPU be burnt also?

No, you don't have to burn both sets of fuses. If you want gamecard functionality, you only have to burn the gamecard fuses.

 

[grcd]

Also, downgrading your sysNAND to a lower version and then booting an up-to-date emuNAND will allow you to use the gamecard slot.

I am one of those people who have been steadfast in not using EMUNAND. Not sure why, just afraid of the extra complexity layer, and also the difficulty of managing my already many games. I have my games spread over two 256GB SD cards, and it is already unyieldly and difficult. Is there yet any easy way to manage SD card content, or to transfer data from SYSNAND to EMUNAND and vice-versa?

Many thanks for your incredibly helpful answers!

 

[vree]

I am one of those people who have been steadfast in not using EMUNAND. Not sure why, just afraid of the extra complexity layer, and also the difficulty of managing my already many games. I have my games spread over two 256GB SD cards, and it is already unyieldly and difficult. Is there yet any easy way to manage SD card content, or to transfer data from SYSNAND to EMUNAND and vice-versa?

Many thanks for your incredibly helpful answers!

Emunand and systemnand will not help with that. I also don't use emunand because I got another switch to play online. Emunand isn't really needed unless you want to play online on your hacked system.

Also 256SD should be more then enough there is no point in installing 60 games at the same time. Just install what you want to play and deinstall what you are done with...

 

[Lacius]

I am one of those people who have been steadfast in not using EMUNAND. Not sure why, just afraid of the extra complexity layer, and also the difficulty of managing my already many games. I have my games spread over two 256GB SD cards, and it is already unyieldly and difficult. Is there yet any easy way to manage SD card content, or to transfer data from SYSNAND to EMUNAND and vice-versa?

Many thanks for your incredibly helpful answers!

Unless you plan on using online play with legitimately purchased games, emuNAND is not recommended. For your issues, I'd recommend purchasing a bigger SD card.

With the newest Switch update (10.0.0), you can easily send Switch games/update/DLC between the NAND and the SD card. This can somewhat help you in managing SD content. For example, if you want to move Game A from SD A to SD B, you can move Game A from SD A to the NAND, switch the SD card to SD B, and then move the game from the NAND to SD B. Other than that, there's no much you can do aside from reinstalling NSP files.

 

[Arras]

If anyone else can't get this to work like I couldn't - I had two BCT.ini files for some reason, one in /atmosphere and one in /atmosphere/config. Make sure to edit both of them (or at least the config one).

 

[Draxzelex]

If anyone else can't get this to work like I couldn't - I had two BCT.ini files for some reason, one in /atmosphere and one in /atmosphere/config. Make sure to edit both of them (or at least the config one).

You're not supposed to have a BCT.ini file in the atmosphere folder..

 

[MalayZN]

So I see i need to enable it in the BCT.ini
but not sure how to edit the line.
below is what i see with text editor
BCT0
[stage1]
stage2_path = sept/payload.bin
stage2_mtc_path = atmosphere/fusee-mtc.bin
stage2_addr = 0xF0000000
stage2_entrypoint = 0xF0000000

[stratosphere]
; To force-enable nogc, add nogc = 1
; To force-disable nogc, add nogc = 0

; To opt in to using Atmosphere's NCM reimplementation, add enable_ncm = 1

 

[bad361]

So I see i need to enable it in the BCT.ini
but not sure how to edit the line.
below is what i see with text editor
BCT0
[stage1]
stage2_path = sept/payload.bin
stage2_mtc_path = atmosphere/fusee-mtc.bin
stage2_addr = 0xF0000000
stage2_entrypoint = 0xF0000000

[stratosphere]
; To force-enable nogc, add nogc = 1
; To force-disable nogc, add nogc = 0

; To opt in to using Atmosphere's NCM reimplementation, add enable_ncm = 1

should look like this

[stratosphere]
; To force-enable nogc, add nogc = 1
; To force-disable nogc, add nogc = 0
nogc = 0

 

[MalayZN]

should look like this

Thanks!
there was another ini file it will pull the info from.
added to that ini and worked great!
thank you.

 

[Deleted member 514389]

==Not-completly-off-topic-necro==

As I (foolishly) decided to update my sysnand to 11.0
~ While EmuNand remains on 10.1.0|AMS 0.14.4E:

Atmo crashes (2002-2634) if I
a) Have a gamecard inserted upon boot
b) Insert it during operation

I tried (BCT.ini) both "nogc = 0" and "nogc = 1"
One crashes still. The other can't read the gamecard.

Sooo..
Is there a way around having to update the emunand to the (not yet supported by atmo) 11.0 fw ?

 

[Xjackio]

==Not-completly-off-topic-necro==

As I (foolishly) decided to update my sysnand to 11.0
~ While EmuNand remains on 10.1.0|AMS 0.14.4E:

Atmo crashes (2002-2634) if I
a) Have a gamecard inserted upon boot
b) Insert it during operation

I tried (BCT.ini) both "nogc = 0" and "nogc = 1"
One crashes still. The other can't read the gamecard.

Sooo..
Is there a way around having to update the emunand to the (not yet supported by atmo) 11.0 fw ?

I updated atmos, then start as stock, updated switch, restarted in rcm, load it with fusee and started playing as normal, while my pokemon sword was in the switch all the time

 

[Deleted member 514389]

What FW ?

 

[Xjackio]

What FW ?

11.0.0

 

[Fgamer]

==Not-completly-off-topic-necro==

As I (foolishly) decided to update my sysnand to 11.0
~ While EmuNand remains on 10.1.0|AMS 0.14.4E:

Atmo crashes (2002-2634) if I
a) Have a gamecard inserted upon boot
b) Insert it during operation

I tried (BCT.ini) both "nogc = 0" and "nogc = 1"
One crashes still. The other can't read the gamecard.

Sooo..
Is there a way around having to update the emunand to the (not yet supported by atmo) 11.0 fw ?

Atmosphere has supported 11.0.0 since yesterday https://github.com/Atmosphere-NX/Atmosphere/releases/tag/0.16.0

emuMMC is very slow at the moment though so you might want to wait for a fix for that.