Hacking Homebrew Homebrew app Help a father with his son’s Switch!

[Invenromuto]

Hello, I have a problem with my Switch v1. I used to have Hekate, which was launched via TegraRCM and then Atmosphere, with the DNS configured to avoid bricks, and I was able to successfully run homebrew.

After a reboot, it started giving error messages when loading both emuMMC and sysMMC. Since I couldn’t fix it in any way, I started from scratch by formatting the SD card and following step by step this guide that was recommended in several posts on this forum: switch.hacks.guide

I followed the whole procedure successfully, but when I try to launch any of the three options, I get the same message. Hekate – IPL starts loading and after a few seconds a red text appears on the right side of the console, vertically, that says:
pkg2 decryption failed!
pkg1/pkg2 mismatch or old hekate!
failed to launch HOS!
press any key…

When I press a button I am taken back to the Hekate home screen.
I have already tried restoring a BOOT1 and BOOT2 backup I had from 2020, and redoing the whole procedure from the beginning, but nothing changed. I also tried with a different SD card, but again nothing changed.

The payload version used is hekate_ctcaer_6.5.1
The Atmosphere version is 1.10.2

Help a father make his son happy!

I am attaching below the photos with the information about the console.

 

[Deleted member 681324]

Get the latest atmosphere and hekate versions, and don't forget to update your tegraRCM with the matching latest boot.bin payload

 

[thesjaakspoiler]

I have already tried restoring a BOOT1 and BOOT2 backup I had from 2020, and redoing the whole procedure from the beginning, but nothing changed.

someone correct me if I'm wrong but afaik BOOT0 and BOOT1 have a version that must match the GPP partition.
So you could try restoring all 3 of them so that the versions match if you are sure you do have the latest version of Hekate (+ primary payload).

 

[The Real Jdbye]

someone correct me if I'm wrong but afaik BOOT0 and BOOT1 have a version that must match the GPP partition.
So you could try restoring all 3 of them so that the versions match if you are sure you do have the latest version of Hekate (+ primary payload).

Correct, they should never be restored by themselves.

 

[Invenromuto]

someone correct me if I'm wrong but afaik BOOT0 and BOOT1 have a version that must match the GPP partition.
So you could try restoring all 3 of them so that the versions match if you are sure you do have the latest version of Hekate (+ primary payload).

I didn't find the backup of the GPP part, but I did a full backup of everything, boot1, boot2 and GPP before restoring the 2020 backup of just boot1 and boot2, so I can restore those in case it could be a further source of problems.

Post automatically merged: Feb 20, 2026

Get the latest atmosphere and hekate versions, and don't forget to update your tegraRCM with the matching latest boot.bin payload

The payload version used is hekate_ctcaer_6.5.1
The Atmosphere version is 1.10.2
These are the latest available versions I found.
How can i check matching between boot.bin payload and tegraCRM?

 

[Deleted member 681324]

I didn't find the backup of the GPP part, but I did a full backup of everything, boot1, boot2 and GPP before restoring the 2020 backup of just boot1 and boot2, so I can restore those in case it could be a further source of problems.

Post automatically merged: Feb 20, 2026

The payload version used is hekate_ctcaer_6.5.1
The Atmosphere version is 1.10.2
These are the latest available versions I found.
How can i check matching between boot.bin payload and tegraCRM?

Take the boot.bin from the hekate 6.5.1 payload(s) and copy it over to your tegraRCM payload.

 

[Invenromuto]

Take the boot.bin from the hekate 6.5.1 payload(s) and copy it over to your tegraRCM payload.

I've injected hekate .bin with tegraRCM, but the same error occurr T_T