Hacking Question NCA Error with Goldleaf, corrupt install with Tinfoil, I have latest sig patches?

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
Hi guys

I am sorry if this has been asked a million times, I have been trying to get my switch to work for hours.
If someone can please help me figure out what is wrong I would really appreciate it.

I am on 9.1.0 and running hekate payload.
Some games install OK using tinfoil and Goldleaf, some come up as either corrupt install (tinfoil) or refuse to start installing and give NCA error (goldleaf).

I have also extracted the latest version of Joonies sig patches.

Does anyone have an idea what I am doing wrong here?

Thank you
 

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
get rid of hekate, use atmosphere primary and reinstall non-working stuff.. do they work now?


Could you be a little more specific pls, I am new to all this?

Do I download the Kosmos complete package and just extract it to my sd card?

Thanks for your help!
 
Last edited by gandalf,

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand

Thank you

So do I just delete everything from my SD, and then just unpack atmosphere-0.10.2-master-d5458960+hbl-2.3+hbmenu-3.2.0.zip
from the link you suggested on the root of my SD card?

when I reboot into hekate, and select payloads, I can load fusee-primary.bin.
Is this what you were initially saying I should run?

In any case result is the same, even with this payload, I get a corrupt install, same errors as before.
 
Last edited by gandalf,

Mthodmn101

Well-Known Member
Member
Joined
Jan 31, 2008
Messages
650
Trophies
1
XP
1,711
Country
United States
Thank you

So do I just delete everything from my SD, and then just unpack atmosphere-0.10.2-master-d5458960+hbl-2.3+hbmenu-3.2.0.zip
from the link you suggested on the root of my SD card?

extract to sd card along with https://gbatemp.net/threads/i-heard-that-you-guys-need-some-sweet-patches-for-atmosphere.521164/

then use the payload fusee-primary.bin to boot cfw on your switch

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

Thank you

So do I just delete everything from my SD, and then just unpack atmosphere-0.10.2-master-d5458960+hbl-2.3+hbmenu-3.2.0.zip
from the link you suggested on the root of my SD card?

when I reboot into hekate, and select payloads, I can load fusee-primary.bin.
Is this what you were initially saying I should run?

In any case result is the same, even with this payload, I get a corrupt install, same errors as before.

Is that booting fusee-primary.bin directly? (not through hekate payload menu)
 

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
extract to sd card along with https://gbatemp.net/threads/i-heard-that-you-guys-need-some-sweet-patches-for-atmosphere.521164/

then use the payload fusee-primary.bin to boot cfw on your switch

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



Is that booting fusee-primary.bin directly? (not through hekate payload menu)

Yes, it was trough hekate. But now it doesn't boot at all.

I just did all this, when I inject the payload, it says its successful, but the switch screen just remains black and nothing happens.

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

Weird.

Now whenever I try to inject the payload it says its injected successfully, then it goes to red and says RCM device disconnected.

I just press and hold the volume up button and plug in the usb cable into my pc. This was working fine last night when tried, not it doesnt.

Hekate injecting still works, I am really confused.
 
Last edited by gandalf,

Mthodmn101

Well-Known Member
Member
Joined
Jan 31, 2008
Messages
650
Trophies
1
XP
1,711
Country
United States
Yes, it was trough hekate. But now it doesn't boot at all.

I just did all this, when I inject the payload, it says its successful, but the switch screen just remains black and nothing happens.

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

Weird.

Now whenever I try to inject the payload it says its injected successfully, then it goes to red and says RCM device disconnected.

I just press and hold the volume up button and plug in the usb cable into my pc. This was working fine last night when tried, not it doesnt.

delete the folders atmosphere and sept on your sd card, and recopy over from the zip file, and inject payload fusee-primary.bin

if not, you can go back to hekate/kosmos.. if i had to guess what the issue is, i would assume missing some specific sigpatches, in which case, booting just vanilla atmosphere would fix it
 

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
delete the folders atmosphere and sept on your sd card, and recopy over from the zip file, and inject payload fusee-primary.bin

if not, you can go back to hekate/kosmos.. if i had to guess what the issue is, i would assume missing some specific sigpatches, in which case, booting just vanilla atmosphere would fix it

I am really confused now, last night I was able to inject fusee-primary.bin, now I am unable to.

I have just reformatted the SD card with a FAT32 formatter GUI and recopied all the files from the sources you linked.
Still the same, black screen, then tegrarcmgui reports RCM device disconnected after injecting the payload.
 

Mthodmn101

Well-Known Member
Member
Joined
Jan 31, 2008
Messages
650
Trophies
1
XP
1,711
Country
United States
I am really confused now, last night I was able to inject fusee-primary.bin, now I am unable to.

I have just reformatted the SD card with a FAT32 formatter GUI and recopied all the files from the sources you linked.
Still the same, black screen, then tegrarcmgui reports RCM device disconnected after injecting the payload.

and you are using the most up-to-date fusee-primary.bin?

thats the only thing i could thing of why it would not load atmosphere.. that is all you need
 

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
and you are using the most up-to-date fusee-primary.bin?

thats the only thing i could thing of why it would not load atmosphere.. that is all you need


Yes from the link you posted above. That is the latest ver.

I am just curious as to why some games work, some dont.

So, hekate still loads up fine.
Followed this guide when jailbreaking

 

The Real Jdbye

*is birb*
Member
Joined
Mar 17, 2010
Messages
23,290
Trophies
4
Location
Space
XP
13,846
Country
Norway
Hi guys

I am sorry if this has been asked a million times, I have been trying to get my switch to work for hours.
If someone can please help me figure out what is wrong I would really appreciate it.

I am on 9.1.0 and running hekate payload.
Some games install OK using tinfoil and Goldleaf, some come up as either corrupt install (tinfoil) or refuse to start installing and give NCA error (goldleaf).

I have also extracted the latest version of Joonies sig patches.

Does anyone have an idea what I am doing wrong here?

Thank you
Check your games with NX Game Info. If any of them fail signature checks they will not install without enabling installing of unsigned code in the Tinfoil settings.
However, that's not recommended unless you trust every NSP you install because it makes you vulnerable to malicious NSPs.
Games that are converted from XCI (NX Game Info tells you if they are) will always fail signature checks, and can not be verified good and not corrupted/malicious. I installed a converted XCI of Ni No Kuni that turned out to be corrupted, as there were some corrupted textures ingame, and I had random crashes. In the case where you can't find a CDN dump of a game and only converts are available, it's better to download an XCI and install it with Tinfoil, it will be auto converted and since it has the original XCI, signature checks will still pass during install so it will install fine.
CDN dumps (NX Game Info will tell you if they are in CDN format) should never fail signature checks, it's a sign that the NSP has been tampered with. Many scene release DLCs will fail signature checks though, because they are forged from data mined from the game, and not properly dumped from CDN. These should still be safe to install as long as you know they are the original scene releases.

That's why they won't install in Tinfoil.
However to run any installed games that are from XCI converts or "fake" DLCs, homebrew NSPs and such, you also need the correct sig patches. That's why they still won't run even when installed with Goldleaf. In my opinion Goldleaf should not allow you to install such titles without any warning but I digress.

Have a look at the launch entry in your bootloader\hekate_ipl.ini
Does it say payload=atmosphere\fusee-primary.bin or fss0=atmosphere\fusee-secondary.bin?
You need different sig patches depending on which method you are using.

https://github.com/Joonie86/hekate/releases
If you are using fusee-primary use Atmosphere_patches_.for.fusee.primary.only.7z and extract it to SD.
If you are using fusee-secondary use Kosmos_patches_12_08_2019.zip, extract it to SD and add kip1patch=nosigchk on a new line in the launch entry, if it's not already there. Ignore that it says Kosmos, it has nothing to do with Kosmos. It's just the sig patches. I don't use Kosmos myself and I don't recommend it because it doesn't teach you what you're doing so you have no idea to fix it when something doesn't work.

Always a good idea to make sure your Hekate is updated as well. https://github.com/CTCaer/hekate/releases/

And you will want to replace atmosphere\reboot_payload.bin after every time you update Atmosphere (as Atmosphere will overwrite it), replacing it with the latest Hekate payload instead. And keeping it up to date when you update Hekate as well of course. Having an out of date reboot_payload.bin, or letting Atmosphere overwrite it, will lead to rebooting into a black screen or an error message.

Then you can continue launching CFW just as you have been doing. No point in fixing what aint broken, Hekate is just fine and myself and many others are using it. Not sure what that guy's beef with Hekate is. It's incredibly useful to have as a bootloader, for easily dual booting with Android/Lakka, making NAND backups, or booting other payloads easily without having to put every payload you want to use on your dongle (if you use one), smartphone, or PC. Just keep them all on the Switch so they're always easily accessible. And my favorite feature is that you can't accidentally boot sysNAND CFW if you forget to insert your MicroSD card and inject Fusee. Hekate will not boot CFW if it can't find the boot config.
I tried Fusee once, accidentally booted into sysNAND several times while trying to set it up because it was silently ignoring my misconfigured emummc.ini instead of throwing an error, and booted into it accidentally when I forgot to put the MicroSD back in, luckily I had made a NAND backup beforehand so I restored that (just to make 100% sure there is no chance I would get banned for it) and went back to SX OS for a few more months, until I decided to take the time to set up Hekate to launch CFW, which has worked much better for me.
 
Last edited by The Real Jdbye,
  • Like
Reactions: datnodude

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
Check your games with NX Game Info. If any of them fail signature checks they will not install without enabling installing of unsigned code in the Tinfoil settings.
However, that's not recommended unless you trust every NSP you install because it makes you vulnerable to malicious NSPs.
Games that are converted from XCI (NX Game Info tells you if they are) will always fail signature checks, and can not be verified good and not corrupted/malicious. I installed a converted XCI of Ni No Kuni that turned out to be corrupted, as there were some corrupted textures ingame, and I had random crashes. In the case where you can't find a CDN dump of a game and only converts are available, it's better to download an XCI and install it with Tinfoil, it will be auto converted and since it has the original XCI, signature checks will still pass during install so it will install fine.
CDN dumps (NX Game Info will tell you if they are in CDN format) should never fail signature checks, it's a sign that the NSP has been tampered with. Many scene release DLCs will fail signature checks though, because they are forged from data mined from the game, and not properly dumped from CDN. These should still be safe to install as long as you know they are the original scene releases.

That's why they won't install in Tinfoil.
However to run any installed games that are from XCI converts or "fake" DLCs, homebrew NSPs and such, you also need the correct sig patches. That's why they still won't run even when installed with Goldleaf. In my opinion Goldleaf should not allow you to install such titles without any warning but I digress.

Have a look at the launch entry in your bootloader\hekate_ipl.ini
Does it say payload=atmosphere\fusee-primary.bin or fss0=atmosphere\fusee-secondary.bin?
You need different sig patches depending on which method you are using.

https://github.com/Joonie86/hekate/releases
If you are using fusee-primary use Atmosphere_patches_.for.fusee.primary.only.7z and extract it to SD.
If you are using fusee-secondary use Kosmos_patches_12_08_2019.zip, extract it to SD and add kip1patch=nosigchk on a new line in the launch entry, if it's not already there. Ignore that it says Kosmos, it has nothing to do with Kosmos. It's just the sig patches. I don't use Kosmos myself and I don't recommend it because it doesn't teach you what you're doing so you have no idea to fix it when something doesn't work.

Always a good idea to make sure your Hekate is updated as well. https://github.com/CTCaer/hekate/releases/

And you will want to replace atmosphere\reboot_payload.bin after every time you update Atmosphere (as Atmosphere will overwrite it), replacing it with the latest Hekate payload instead. And keeping it up to date when you update Hekate as well of course. Having an out of date reboot_payload.bin, or letting Atmosphere overwrite it, will lead to rebooting into a black screen or an error message.

Then you can continue launching CFW just as you have been doing. No point in fixing what aint broken, Hekate is just fine and myself and many others are using it. Not sure what that guy's beef with Hekate is. It's incredibly useful to have as a bootloader, for easily dual booting with Android/Lakka, making NAND backups, or booting other payloads easily without having to put every payload you want to use on your dongle (if you use one), smartphone, or PC. Just keep them all on the Switch so they're always easily accessible. And my favorite feature is that you can't accidentally boot sysNAND CFW if you forget to insert your MicroSD card and inject Fusee. Hekate will not boot CFW if it can't find the boot config.
I tried Fusee once, accidentally booted into sysNAND several times while trying to set it up because it was silently ignoring my misconfigured emummc.ini instead of throwing an error, and booted into it accidentally when I forgot to put the MicroSD back in, luckily I had made a NAND backup beforehand so I restored that (just to make 100% sure there is no chance I would get banned for it) and went back to SX OS for a few more months, until I decided to take the time to set up Hekate to launch CFW, which has worked much better for me.

Thank you for such an extensive explanation.

I will stick with hekate then, since that is the only one that works for me without any issues, apart from corrupt game install, but you made it clear that this is to do with modded NSP's.

You are correct, the games that FAIL the NCA signature check in tinfoil always end up as corrupted on the main menu, and cannot be played. This is after I enable the unsigned code installation in tinfoil options.
So I should just stay away from these and get an XCI version instead?
Which signature patches do I need to able to run these?

I am still a bit confused as to which sig patches I need to run. Here is my hekate_ipl.ini file

[config]
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=1

{AtlasNX/Kosmos v15.1}
{}
{Discord: discord.teamatlasnx.com}
{Github: git.teamatlasnx.com}
{Patreon: patreon.teamatlasnx.com}
{Pegascape DNS: pegascape.sdsetup.com}
{}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}
 

The Real Jdbye

*is birb*
Member
Joined
Mar 17, 2010
Messages
23,290
Trophies
4
Location
Space
XP
13,846
Country
Norway
Thank you for such an extensive explanation.

I will stick with hekate then, since that is the only one that works for me without any issues, apart from corrupt game install, but you made it clear that this is to do with modded NSP's.

You are correct, the games that FAIL the NCA signature check in tinfoil always end up as corrupted on the main menu, and cannot be played. This is after I enable the unsigned code installation in tinfoil options.
So I should just stay away from these and get an XCI version instead?
Which signature patches do I need to able to run these?

I am still a bit confused as to which sig patches I need to run. Here is my hekate_ipl.ini file

[config]
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=1

{AtlasNX/Kosmos v15.1}
{}
{Discord: discord.teamatlasnx.com}
{Github: git.teamatlasnx.com}
{Patreon: patreon.teamatlasnx.com}
{Pegascape DNS: pegascape.sdsetup.com}
{}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}
Assuming you have an emuNAND, you should remove the CFW (SYSNAND) and Stock (SYSNAND) options, you don't need them and they only serve to put you at risk (even if it's a small risk) of a ban if you launch them by accident. Stock is not 100% stock either, the only way to boot 100% stock sysNAND is by booting normally.
If you don't have an emuNAND you should probably look into getting one but I won't explain all that here.

You appear to be using Kosmos. Had you set it up from scratch rather than relying on a premade pack you would have a better understanding of how it works and you wouldn't have needed to make this thread.

Installing XCI directly with Tinfoil is better than installing a converted XCI because the signatures are verified against the original XCI so that you know it's a good dump and you won't have any issues with it. And that it's not malicious. Malicious NSPs are rare but they do exist, but that mostly matters when you are one of the first to download something off a forum or something, before a lot of people have tested it and verified it's working.

Anyway, you're using fusee-secondary. I told you what you need to do.
 
Last edited by The Real Jdbye,

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
Assuming you have an emuNAND, you should remove the CFW (SYSNAND) and Stock (SYSNAND) options, you don't need them and they only serve to put you at risk (even if it's a small risk) of a ban if you launch them by accident. Stock is not 100% stock either, the only way to boot 100% stock sysNAND is by booting normally.
If you don't have an emuNAND you should probably look into getting one but I won't explain all that here.

You appear to be using Kosmos. Had you set it up from scratch rather than relying on a premade pack you would have a better understanding of how it works and you wouldn't have needed to make this thread.

Installing XCI directly with Tinfoil is better than installing a converted XCI because the signatures are verified against the original XCI so that you know it's a good dump and you won't have any issues with it. And that it's not malicious. Malicious NSPs are rare but they do exist, but that mostly matters when you are one of the first to download something off a forum or something, before a lot of people have tested it and verified it's working.

Anyway, you're using fusee-secondary. I told you what you need to do.

Thank you

Is this how my edited ini file should be looking?
Should it be under config section right at the top, or under custom firmware?

[config]
kip1patch=nosigchk
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=1

{AtlasNX/Kosmos v15.1}
{}
{Discord: discord.teamatlasnx.com}
{Github: git.teamatlasnx.com}
{Patreon: patreon.teamatlasnx.com}
{Pegascape DNS: pegascape.sdsetup.com}
{}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}
 

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
So I added the entry kip1patch=nosigchk under, as below and copied Kosmos_patches_12_08_2019.zip to the root of my micro sd, but am still getting NCA signature verification failed in tinfoil?

[config]
kip1patch=nosigchk
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=1
 

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
Just tried a few XCI's this time.
Same problem, game corrupt after install or nca sig fail.
It seems none of the recent release games will run on my system.
 

kylum

Well-Known Member
Member
Joined
Dec 8, 2008
Messages
394
Trophies
1
XP
1,481
Country
United States
And you did apply the latest Kosmos patches like @The Real Jdbye told you to do?
Here
kip1patch=nosigchk is in the wrong place!
Put it directly under this line for CFW:
fss0=atmosphere/fusee-secondary.bin
 

gandalf

Well-Known Member
OP
Newcomer
Joined
Jan 30, 2017
Messages
68
Trophies
0
Age
40
XP
226
Country
New Zealand
Hi Guys

I have managed to run fusee as a primary and then installed the atmosphere patches.
Now most of the games work, and the one that don't usually do when sig checker is disabled in tinfoil.

Thank you very much for all your support.
 
  • Like
Reactions: kylum

kylum

Well-Known Member
Member
Joined
Dec 8, 2008
Messages
394
Trophies
1
XP
1,481
Country
United States
Hi Guys

I have managed to run fusee as a primary and then installed the atmosphere patches.
Now most of the games work, and the one that don't usually do when sig checker is disabled in tinfoil.

Thank you very much for all your support.

Glad to hear. Even better that you learned something while you were at it!
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    OctoAori20 @ OctoAori20: Nice nice-