Hacking SWITCH NOOB PARADISE - Ask questions here

Lacius · Aug 1, 2019

apocalipsis_ending said:
So, the steps worked and now I can play games that require higher firmware. That's great! Thank you!
Just a little detail... Now my game cards are not recognized... It keeps asking to remove and reinsert them, and I do that, but it does not work.

Also, with the firmware upgrade now it tells me that a controller update is available.

Any Ideas on how to solve this?

You need to allow your GC slot to be updated. You can do this by disabling the block in BCT.ini on your SD card. Add "nogc = 0" where appropriate (it tells you where in the file).

If you downgrade to anything below 4.0.0, however, your game cartridge slot will not work unless you update back to 4.0.0 or higher.

It is safe to update your controllers if they're not physically modified.

namad · Aug 1, 2019

As far as I know 4.1.0 doesn't support sdmicro cards greater than 64gb in size. Because when I was on 4.1.0 and I put an exfat 128gb card in, it said I needed to update to use it. So now I've got a 128gb exfat sdmicro card I'm not using for anything, and a 32gb fat32 card i'm using for everything. Which is fine I guess. Although this discrepancy if I'm right, might answer a few people's question?

https://en-americas-support.nintendo.com/app/answers/detail/a_id/22481

he following types of microSD cards are supported on Nintendo Switch:

microSD (up to 2 GB)
microSDHC (4 GB - 32 GB)
microSDXC (64 GB and above)

Important:
In order to use a microSDXC card on the Nintendo Switch console, a system update is required.
and as far as I know all 128gb microsd cards are of the sdxc standard. So unless I'm wrong, this answers the question of why sometimes exfat doesn't work. yes?

apocalipsis_ending · Aug 1, 2019

Lacius said:
You need to allow your GC slot to be updated. You can do this by disabling the block in BCT.ini on your SD card. Add "nogc = 0" where appropriate (it tells you where in the file).

If you downgrade to anything below 4.0.0, however, your game cartridge slot will not work unless you update back to 4.0.0 or higher.

It is safe to update your controllers if they're not physically modified.

Thanks again for your reply.
I seem to be doing something wrong.

This is how I edited the file:

BCT0
[stage1]
stage2_path = atmosphere/fusee-secondary.bin
stage2_addr = 0xF0000000
stage2_entrypoint = 0xF0000000

[exosphere]
; Note: Disabling debugmode will cause parts of ams.tma to not work, in the future.
debugmode = 1
debugmode_user = 0
; Note: Disabling usermode exception handlers will cause atmosphere to not fail gracefully under error conditions.
; Support will not be provided to users who disable these. If you do not know what you are doing, leave them on.
disable_user_exception_handlers = 0

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

Could you tell me what is the correct way to do it?

Lacius · Aug 1, 2019

apocalipsis_ending said:
Thanks again for your reply.
I seem to be doing something wrong.

This is how I edited the file:

BCT0
[stage1]
stage2_path = atmosphere/fusee-secondary.bin
stage2_addr = 0xF0000000
stage2_entrypoint = 0xF0000000

[exosphere]
; Note: Disabling debugmode will cause parts of ams.tma to not work, in the future.
debugmode = 1
debugmode_user = 0
; Note: Disabling usermode exception handlers will cause atmosphere to not fail gracefully under error conditions.
; Support will not be provided to users who disable these. If you do not know what you are doing, leave them on.
disable_user_exception_handlers = 0

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

Could you tell me what is the correct way to do it?

You did it properly.

DrDoctor · Aug 1, 2019

Do I run the risk of burning fuses when booting into OFW SYSNAND from the normal RCM "cmd prompt"-looking screen (that appears when no SD card is inserted)?
Or do I need to do it through Hekate?

Lacius · Aug 1, 2019

DrDoctor said:
Do I run the risk of burning fuses when booting into OFW SYSNAND from the normal RCM "cmd prompt"-looking screen (that appears when no SD card is inserted)?
Or do I need to do it through Hekate?

It sounds like you're describing Hekate. Is that what you're pushing?

Draxzelex · Aug 1, 2019

namad said:
As far as I know 4.1.0 doesn't support sdmicro cards greater than 64gb in size. Because when I was on 4.1.0 and I put an exfat 128gb card in, it said I needed to update to use it. So now I've got a 128gb exfat sdmicro card I'm not using for anything, and a 32gb fat32 card i'm using for everything. Which is fine I guess. Although this discrepancy if I'm right, might answer a few people's question?

https://en-americas-support.nintendo.com/app/answers/detail/a_id/22481

he following types of microSD cards are supported on Nintendo Switch:

microSD (up to 2 GB)

microSDHC (4 GB - 32 GB)

microSDXC (64 GB and above)

Important:
In order to use a microSDXC card on the Nintendo Switch console, a system update is required.
and as far as I know all 128gb microsd cards are of the sdxc standard. So unless I'm wrong, this answers the question of why sometimes exfat doesn't work. yes?

Except for 1.0, all Nintendo Switch firmware versions support exFAT and require an additional driver. However you cannot download this driver without being on the latest firmware. There are homebrew applications that can install the driver unofficially such as ChoiDujourNX. However FAT32 is still recommended over exFAT as the Switch's exFAT driver is not stable and can corrupt your SD card. Plus, there is no incentive for Nintendo to address this issue.

apocalipsis_ending · Aug 1, 2019

Lacius said:
You did it properly.

Really?
But the problem persist.
Any ideas of another possible solution?

Lacius · Aug 1, 2019

apocalipsis_ending said:
Really?
But the problem persist.
Any ideas of another possible solution?

Take the game cartridge out and reboot the system. If that doesn't work, check to make sure you made the change to the BCT.ini file.

namad · Aug 1, 2019

Draxzelex said:
Except for 1.0, all Nintendo Switch firmware versions support exFAT and require an additional driver. However you cannot download this driver without being on the latest firmware. There are homebrew applications that can install the driver unofficially such as ChoiDujourNX. However FAT32 is still recommended over exFAT as the Switch's exFAT driver is not stable and can corrupt your SD card. Plus, there is no incentive for Nintendo to address this issue.

If I did manage to find this driver and install it, would it be possible to simply copy/paste all my data from my 32gb fat32 sdmicrocard to my 128gb fat32 sdmicrocard (which i guess i'd need a 3rd party formatting tool to create because windows defaults to formatting 128gb as exfat?) or are you saying that even without the driver the 128gb sdmicrocard would've worked if i'd simply reformatted it from exfat into fat32?

Hayato213 · Aug 1, 2019

namad said:
If I did manage to find this driver and install it, would it be possible to simply copy/paste all my data from my 32gb fat32 sdmicrocard to my 128gb fat32 sdmicrocard (which i guess i'd need a 3rd party formatting tool to create because windows defaults to formatting 128gb as exfat?) or are you saying that even without the driver the 128gb sdmicrocard would've worked if i'd simply reformatted it from exfat into fat32?

You can use third party software like minitool partition wizard or guiformat to format the sd card to FAT32, as @Draxzelex has stated you should use FAT32 over exFAT.

apocalipsis_ending · Aug 1, 2019

Lacius said:
Take the game cartridge out and reboot the system. If that doesn't work, check to make sure you made the change to the BCT.ini file.

Done, and done. But still does not solve the problem.
Worst case scenario I will have to reinstall Breath of the wild from a nsp file.
For now it does not worry me to much. I will come back another time with this issue.
Thank you very much for your help, Lacius. See ya!

namad · Aug 1, 2019

Hayato213 said:
You can use third party software like minitool partition wizard or guiformat to format the sd card to FAT32, as @Draxzelex has stated you should use FAT32 over exFAT.

Yeah I managed to google that part, the part of my question that was more uncertain, how do I switch sdcards? is removing the 32gb, then copying all it's data to the 128gb then putting the 128gb in.... enough? or is there some hidden secret reason that can't work?

Omar2325 · Aug 1, 2019

If I format my NAND can I still use all my previous backups?

Lacius · Aug 1, 2019

Omar2325 said:
If I format my NAND can I still use all my previous backups?

If you mean NAND backups, yes.

Omar2325 · Aug 1, 2019

Lacius said:
If you mean NAND backups, yes.

ok, thanks

--------------------- MERGED ---------------------------

how does partition between NAND and emuNAND work? let's say I create emuNAND with all the hack stuff on 8.1.0. Then I want to downgrade sysNAND to a clean state, initialize sysNAND and then update it to 8.1.0 for online. will emuNAND be affected because of that downgrade and/or initialization?

Zaybokk · Aug 1, 2019

I'm trying to update firmware from 6.2.0 custom to whatever Latest Firmware is-(not sure what latest hackable firmware is)-while keeping custom firmware.
also , wayy to much confusion around this new**-(well new to me)-
emuMMC thing or whatever it called?..-(and also don't know much about it other than what i seen about it-which is
it being some kind of emuNAND-(i feel this is going to be a major headache for me

,
also side note: don't know if it is required , but one post and or thread by a Well-Known Member*-
said this is required for newer*-games-titles-(which i'm guessing is for the one i'm trying to play
and install at the moment-(Fire Emblem Three Houses*) but keeps failing for some odd reason?).. hmm , i wonder..
is it possible just because it's not named with a shorter name* and Capitalized , like example:
Fire emblem three houses .XXX instead of something like : feth.xxx?? could be messing it up?..
i had issues with this same problem in the past and finally got one working long ago..??

side note!: just in-case anyone wondering about this , i wouldn't mind at all to be on Firmware Version latest that i know of-(8.1.0)- ONLY EXCEPTION THOUGH!**-(has to be hackable while keeping Custom Firmware)-if not then ,
what is latest firmware that supports everything-while Keeping Custom Firmware? , like Atmosphere Glaeee' or what it called..
and also i believe i possibly clicked right thing-(it gave me a few options to choose from at on menu*-from Atlas Kosmos and or Atmos-NX main Menu the latest one-
it said CFW-sysNAND and then another option said CFW-emuNAND.. i know difference between the two , but my problem is when i click the emuNAND option
it doesn't really show and or do anything that even shows that its working correctly and or even on emuNAND like the 3ds ones did long ago..-(plus i didnt even create an emuNAND that i know of??)

DrDoctor · Aug 1, 2019

Lacius said:
It sounds like you're describing Hekate. Is that what you're pushing?

Hmm, yes, that might be it, but without the slick interface due to the SD not being inserted.

HE1NZ · Aug 1, 2019

Zaybokk said:
I'm trying to update firmware from 6.2.0 custom to whatever Latest Firmware is-(not sure what latest hackable firmware is)-while keeping custom firmware.
also , wayy to much confusion around this new**-(well new to me)-
emuMMC thing or whatever it called?..-(and also don't know much about it other than what i seen about it-which is
it being some kind of emuNAND-(i feel this is going to be a major headache for me ,
also side note: don't know if it is required , but one post and or thread by a Well-Known Member*-
said this is required for newer*-games-titles-(which i'm guessing is for the one i'm trying to play
and install at the moment-(Fire Emblem Three Houses*) but keeps failing for some odd reason?).. hmm , i wonder..
is it possible just because it's not named with a shorter name* and Capitalized , like example:
Fire emblem three houses .XXX instead of something like : feth.xxx?? could be messing it up?..
i had issues with this same problem in the past and finally got one working long ago..??

side note!: just in-case anyone wondering about this , i wouldn't mind at all to be on Firmware Version latest that i know of-(8.1.0)- ONLY EXCEPTION THOUGH!**-(has to be hackable while keeping Custom Firmware)-if not then ,
what is latest firmware that supports everything-while Keeping Custom Firmware? , like Atmosphere Glaeee' or what it called..
and also i believe i possibly clicked right thing-(it gave me a few options to choose from at on menu*-from Atlas Kosmos and or Atmos-NX main Menu the latest one-
it said CFW-sysNAND and then another option said CFW-emuNAND.. i know difference between the two , but my problem is when i click the emuNAND option
it doesn't really show and or do anything that even shows that its working correctly and or even on emuNAND like the 3ds ones did long ago..-(plus i didnt even create an emuNAND that i know of??)

I think confusion here is because starting with 3DS scene these CFWs don't have anything to do with FW like in the old PS3 days. Current CFWs work more like patches. They are separate from system firmware. Once you install emuNAND and load into CFW like Atmosphere, you can update your FW inside emuNAND safely using ChoiDujourNX app. Just update to latest 8.1.0.
I'm not sure if it's safe and if there's any reason to update sysNAND if you have emuNAND on SD card.

Lacius · Aug 1, 2019

DrDoctor said:
Hmm, yes, that might be it, but without the slick interface due to the SD not being inserted.

You can't burn fuses when booting through Hekate, with or without the Nyx user interface.

I'm assuming you have AutoRCM installed. Without it, you will burn fuses at some point by booting normally.

Hacking SWITCH NOOB PARADISE - Ask questions here

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Newcomer

Member

Well-Known Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum