Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

Hi All,

I have a question which I am hoping I can get some help with.

I am running latest AMS and HOS with latest version of Hekate. All is good but I sometimes tend to use Tinfoil to see if new game updates and DLC's are released then I manually download anyway so I never install using tinfoil. How do I avoid the red screen when launching Tinfoil. my hekate config is below.....for info if I do not launch into Hekate I usually always boot via Fuse-Primary. I only ever boot Hekate for USB access if needed etc.

[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere FSS0 EmuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/emu_boot.bmp
{}
[Atmosphere FSS0 SYS]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

Based on your config above, it seem you are using Hekate fss0, to use Fusee-Primary you need to set it as the following

[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/icon_atmosphere.bmp

Problem is Blawar and Hekate/ Kosmos developers didn't get along when Kosmos was still around, that why it wouldn't run on Fss0 build.

 

[burhansalih]

Thank you both....I will give this a go when i get my switch back

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

Based on your config above, it seem you are using Hekate fss0, to use Fusee-Primary you need to set it as the following

[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/icon_atmosphere.bmp

Problem is Blawar and Hekate/ Kosmos developers didn't get along when Kosmos was still around, that why it wouldn't run on Fss0 build.

So I am guessing it just replaces the Atmosphere section so it looks like the below...is that correct? See red Text

[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/icon_atmosphere.bmp
{}
[Atmosphere FSS0 SYS]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

 

[Hayato213]

Thank you both....I will give this a go when i get my switch back

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



So I am guessing it just replaces the Atmosphere section so it looks like the below...is that correct? See red Text

[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/icon_atmosphere.bmp
{}
[Atmosphere FSS0 SYS]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

If you use Fusee-Primary you need Fusee patches it would conflict with Fss0/Hekate patches that you are currently using.

 

[burhansalih]

If you use Fusee-Primary you need Fusee patches it would conflict with Fss0/Hekate patches that you are currently using.

I have the patches so no problem

Is the config changes in red look correct.

 

[Hayato213]

I have the patches so no problem

Is the config changes in red look correct.

Most of it is correct, the icon part is based on what the icon in the bootloader folder is named, also there isn't a kip line under Fusee-Primary build.

 

[petspeed]

I have the patches so no problem

Is the config changes in red look correct.

KIP and EmuMMC lines is not needed when booting fusee-primary

 

[burhansalih]

KIP and EmuMMC lines is not needed when booting fusee-primary

Thank you.

ill play around when ive got my switch back much appreciated for all your help

 

[Deleted member 514822]

If you use Fusee-Primary you need Fusee patches it would conflict with Fss0/Hekate patches that you are currently using.

The patches dont actually conflict. The only ones that overwrite are ES patches which are identical between them since ES patches arent handled by the bootloader. FS patches for fusee go in the atmosphere folder and for hekate go in bootloader/patches.ini. That being said, since hes using tinfoil he will need to clear fss0 FS patches for it to properly launch.

Thank you.

ill play around when ive got my switch back much appreciated for all your help

Download fusee sigpatches, set it to

[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/icon_atmosphere.bmp

Then when you still get the red screen, hit Y to clear hekate fss0 patches.

 

[burhansalih]

The patches dont actually conflict. The only ones that overwrite are ES patches which are identical between them since ES patches arent handled by the bootloader. FS patches for fusee go in the atmosphere folder and for hekate go in bootloader/patches.ini. That being said, since hes using tinfoil he will need to clear fss0 FS patches for it to properly launch.

Download fusee sigpatches, set it to

[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/icon_atmosphere.bmp

Then when you still get the red screen, hit Y to clear hekate fss0 patches.

Thank you much appreciated

 

[blazingwolf]

Are sigpatches cumulative? I am having trouble installing .nsps after upgrading to Atmosphere 19.1 and Switch FW 11.0.1. Never had issues before but now I can't install certain DLC and .NSPs without getting an NCA error. If I go to the github and get the latest sigpatches for my version of Atmosphere, that means I can sign .nsps for all firmwares 11.0.1 or lower right? Not sure what I'm doing wrong.

 

[Deleted member 514822]

Are sigpatches cumulative? I am having trouble installing .nsps after upgrading to Atmosphere 19.1 and Switch FW 11.0.1. Never had issues before but now I can't install certain DLC and .NSPs without getting an NCA error. If I go to the github and get the latest sigpatches for my version of Atmosphere, that means I can sign .nsps for all firmwares 11.0.1 or lower right? Not sure what I'm doing wrong.

Which github, which download on that github if theres multiple, and how are you booting atmosphere (fusee primary or hekate, if you chainload fusee primary from hekate then that counts as fusee primary)

 

[blazingwolf]

Which github, which download on that github if theres multiple, and how are you booting atmosphere (fusee primary or hekate, if you chainload fusee primary from hekate then that counts as fusee primary)

Thanks for your reply.

I'm not that well versed in Switch hacking so forgive my ignorance.

I am using the patches found here: https://github.com/ITotalJustice/patches/releases

I am booting Atmosphere through Hekate, its all I've ever known. I tried booting Fusee Primrary through the "Payloads" option in the bootloader, but it just booted to a black screen. My setup is basically a drap and drop the SDCardSetup folder onto the root and launch the payload. If I have to do anything to get fusee primary to load through hekate, I would have to look into it.

Do you need to use fusee primary to install certain .nca/.nsps now, has something changed? Thanks for your help!

 

[Deleted member 514822]

Thanks for your reply.

I'm not that well versed in Switch hacking so forgive my ignorance.

I am using the patches found here: https://github.com/ITotalJustice/patches/releases

I am booting Atmosphere through Hekate, its all I've ever known. I tried booting Fusee Primrary through the "Payloads" option in the bootloader, but it just booted to a black screen. My setup is basically a drap and drop the SDCardSetup folder onto the root and launch the payload. If I have to do anything to get fusee primary to load through hekate, I would have to look into it.

Do you need to use fusee primary to install certain .nca/.nsps now, has something changed? Thanks for your help!

That link has multiple patches, which did you use? If you used the hekate ones and it didnt work then the issue might be because of your hekate config, it requires you specify loading fs patches in the hekate_ipl (es patches do not require this) which would explain the issue.

Youd need to either add kip1patch=nosigchk to your boot config or switch to fusee primary. Id be willing to bet that fusee primary not working is because you downloaded your stuff from some random site and not from atmospheres repo. If youre looking to make fusee primary work, my recommendation would be to clear out atmosphere files and redownload atmosphere and fusee primary from atmospheres github.

 

[blazingwolf]

That link has multiple patches, which did you use? If you used the hekate ones and it didnt work then the issue might be because of your hekate config, it requires you specify loading fs patches in the hekate_ipl (es patches do not require this) which would explain the issue.

Youd need to either add kip1patch=nosigchk to your boot config or switch to fusee primary. Id be willing to bet that fusee primary not working is because you downloaded your stuff from some random site and not from atmospheres repo. If youre looking to make fusee primary work, my recommendation would be to clear out atmosphere files and redownload atmosphere and fusee primary from atmospheres github.

I reinstalled Atmosphere 19.1 from Github and put kip1patch=nosigchk in my hekate_ipl boot config and its working now. Thank you so much! I guess why I'm confused is that I've never needed to do that before. When I updated my switch to 9.2.0 and 10.2.0 , I didn't have any issues signing old and new .nsps. Now that I'm on Atmosphere 19.2 and CFW 11.01, it appears that's changed. Is this something new that I have to do each time I update my firmware?

What also throws me off is I was able to install Monster Hunter Rise just fine, but this SSB DLC gave me issues.

Anyway, thank you again, I was starting to get quite frustrated.

 

[Deleted member 514822]

I reinstalled Atmosphere 19.1 from Github and put kip1patch=nosigchk in my hekate_ipl boot config and its working now. Thank you so much! I guess why I'm confused is that I've never needed to do that before. When I updated my switch to 9.2.0 and 10.2.0 , I didn't have any issues signing old and new .nsps. Now that I'm on Atmosphere 19.2 and CFW 11.01, it appears that's changed. Is this something new that I have to do each time I update my firmware?

What also throws me off is I was able to install Monster Hunter Rise just fine, but this SSB DLC gave me issues.

Anyway, thank you again, I was starting to get quite frustrated.

Most likely the reason is that your MHR nsp was a clean signed copy, which means it uses es patches and those arent handled by the bootloader so they installed without issue. Your smash dlcs were probably scene unlockers from venom, which are unofficial reverse engineered nsps that are not signed and need fs patches, which are handled by the bootloader. Because of this, you needed to instruct hekate to load patches.

 

[neontiger]

Try fully deleting the atmosphere, bootloader and sept folders. Download atmosphere and fusee primary from atmospheres github. Push fusee and see if it has the same issue.

I've tried following another guide (nh-server.github.io) which suggests partitioning using TegraExplorer and collecting files from the official repositories like you mentioned, but still I get the same result; Atmosphere won't boot but I get to see the Hekate logo for a few seconds after the Launch option. I will try to push fusee-primary and let you know if anything changes, although I believe I have to modify my hekate_ipl first.

 

[Deleted member 514822]

I've tried following another guide (nh-server.github.io) which suggests partitioning using TegraExplorer and collecting files from the official repositories like you mentioned, but still I get the same result; Atmosphere won't boot but I get to see the Hekate logo for a few seconds after the Launch option. I will try to push fusee-primary and let you know if anything changes, although I believe I have to modify my hekate_ipl first.

You dont need to modify your hekate ini, you can just push fusee instead of ever going into hekate. Although modifying the hekate ini is an option if you wanted to.

 

[neontiger]

You dont need to modify your hekate ini, you can just push fusee instead of ever going into hekate. Although modifying the hekate ini is an option if you wanted to.

Tried both approaches mentioned in the "Alternate boot setups" section of the NH Switch Guide (nh-server)
1. Adding fusee-primary.bin in bootloader, modifying hekate_ipl.ini, pushing the Hekate payload and selecting Launch -> Atmosphere. Result is black screen after both the Hekate and Atmosphere logo.
2. Pushing the fusee-primary.bin payload. Result is black screen after the Atmosphere logo.

 

[Deleted member 514822]

Tried both approaches mentioned in the "Alternate boot setups" section of the NH Switch Guide (nh-server)
1. Adding fusee-primary.bin in bootloader, modifying hekate_ipl.ini, pushing the Hekate payload and selecting Launch -> Atmosphere. Result is black screen after both the Hekate and Atmosphere logo.
2. Pushing the fusee-primary.bin payload. Result is black screen after the Atmosphere logo.

Sounds like the nand youre booting is messed up to me, although i cant be 100% certain.

 

[neontiger]

Sounds like the nand youre booting is messed up to me, although i cant be 100% certain.

A user on another message board suggested that upgrading solved the problem.
Is there any method to upgrade the emuNAND of CFW without burning fuses or altering the OFW version (4.1.0) in any way?