Hacking Question Updated switch to 8.1.0. Now I cant boot

[The Real Jdbye]

Nyx theme loads fine. No SD corruption. I am mostly a layman. Is there a guide somewhere on what I would do with these patches exactly?

Put them on the SD
You'll also have to add kip1patch=nosigchk to the hekate boot entry.

 

[Starkgod]

Put them on the SD
You'll also have to add kip1patch=nosigchk to the hekate boot entry.

I see. I've replaced the files on my sd with the premade patches on the github link. Now there are finally boot options in the launch menu. However launching them puts me back at the hekate menu. I suspect I have to do that last bit you mentioned. I don't see a file referencing that in the folders. Any ideas? Thanks for your help and patience, by the way. I'm as layman as they come.

 

[The Real Jdbye]

I see. I've replaced the files on my sd with the premade patches on the github link. Now there are finally boot options in the launch menu. However launching them puts me back at the hekate menu. I suspect I have to do that last bit you mentioned. I don't see a file referencing that in the folders. Any ideas? Thanks for your help and patience, by the way. I'm as layman as they come.

If you used the boot config from the link, it will already have nosigchk added. And the patches for it are in patches.ini, not in a separate file. You should probably remove both SYSNAND entries though if you are using emuNAND, to avoid accidentally booting sysNAND and tainting your clean NAND.

If you are using that config you will need Atmosphere as well or it obviously won't work. As well as that you should replace the atmosphere\reboot_payload.bin file with the Hekate payload (rename it) so that rebooting will boot into Hekate rather than fusee-primary. And you could set one of the boot entries to autoboot, so you don't have to select it every time.

 

[Starkgod]

If you used the boot config from the link, it will already have nosigchk added. And the patches for it are in patches.ini, not in a separate file. You should probably remove both SYSNAND entries though if you are using emuNAND, to avoid accidentally booting sysNAND and tainting your clean NAND.

If you are using that config you will need Atmosphere as well or it obviously won't work. As well as that you should replace the atmosphere\reboot_payload.bin file with the Hekate payload (rename it) so that rebooting will boot into Hekate rather than fusee-primary. And you could set one of the boot entries to autoboot, so you don't have to select it every time.

I see. So I should be fine then. I don't use EmuNAND. However when I choose to launch, it simply takes me back to hekate's menu.

 

[The Real Jdbye]

I see. So I should be fine then. I don't use EmuNAND. However when I choose to launch, it simply takes me back to hekate's menu.

You have Atmosphere on the SD?

 

[Starkgod]

You have Atmosphere on the SD?

I did not add the atmosphere folder assuming it would conflict with the Reinx cfw on the SD.

 

[The Real Jdbye]

I did not add the atmosphere folder assuming it would conflict with the Reinx cfw on the SD.

It won't conflict.
The config is for Atmosphere so without Atmosphere it obviously won't work. The atmosphere folder in the archive is just the sig patches, you still need to grab Atmosphere from https://github.com/Atmosphere-NX/Atmosphere/releases
As well as that you should replace the atmosphere\reboot_payload.bin file with the Hekate payload (rename it) so that rebooting (from the menu or after a crash) will boot into Hekate rather than fusee-primary. And you could set one of the boot entries to autoboot, so you don't have to select it every time.

 

[Starkgod]

It won't conflict.
The config is for Atmosphere so without Atmosphere it obviously won't work. The atmosphere folder in the archive is just the sig patches, you still need to grab Atmosphere from https://github.com/Atmosphere-NX/Atmosphere/releases
As well as that you should replace the atmosphere\reboot_payload.bin file with the Hekate payload (rename it) so that rebooting (from the menu or after a crash) will boot into Hekate rather than fusee-primary. And you could set one of the boot entries to autoboot, so you don't have to select it every time.

I am a bit confused at this. Could you break down step by step exactly where I should put the files?

 

[The Real Jdbye]

I am a bit confused at this. Could you break down step by step exactly where I should put the files?

They are already in the right folders, just put them on the SD.

 

[Starkgod]

They are already in the right folders, just put them on the SD.

So all the folders from kosmos. As well as the atmosphere 9.4 folder from the github go onto the sd? I am lost on the renaming part.

 

[The Real Jdbye]

So all the folders from kosmos. As well as the atmosphere 9.4 folder from the github go onto the sd? I am lost on the renaming part.

There shouldn't be an atmosphere 9.4 folder, just the folders "atmosphere" "sept" "switch" and hbmenu.nro
The hekate payload you use to inject, rename it to reboot_payload.bin and replace the existing file in the atmosphere folder.

 

[Starkgod]

There shouldn't be an atmosphere 9.4 folder, just the folders "atmosphere" "sept" "switch" and hbmenu.nro
The hekate payload you use to inject, rename it to reboot_payload.bin and replace the existing file in the atmosphere folder.

This seems to have worked. You have my eternal gratitude.