Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

[Blythe93]

I'll ask the question differently.
What's the interest of having an "unofficial" version when the pre-release works very well?

A bit more convenience for the end users. It's far from AIO pack and it's more like what Atmosphere should have in a first place. Fortunately for us, SciresM decided to omit those thingies that existed mainly for piracy reasons, which allowed Atmosphere to remain on the safe side from big N. Thankfully, supplementing Atmosphere with all these missing features is pretty easy, thanks to all those talented homebrew makers.

 

[bth]

It looks like another aio pack

it's my fork intended for myself, bundled with minimal amount of extra things, since i use it myself, with exefs ips patches generated on compile time, and sys-patch bundled, despite neither are necessary. (but included in the event that someone not me boots with hekate fss0 method, sys-patch would cover FS), since the FS patches are embedded into fusee.

i also considered building sys-patch into package3 as a meme, but i've been too lazy to do that.

 

[Thee_Almighty]

Try redownloading these two:
...Tesla-Menu
...nx-ovlloader

Just downloaded these files, I'm seeing a bunch of folders and files.
Which of these do I move to the switch? Do I drag and drop all?

Apologies. I'm new to this, just need some guidance.
Been staring at YouTube videos all day but you guys are way more helpful!

 

[Blythe93]

Just downloaded these files, I'm seeing a bunch of folders and files.
Which of these do I move to the switch? Do I drag and drop all?

Apologies. I'm new to this, just need some guidance.
Been staring at YouTube videos all day but you guys are way more helpful!

Extract them both to the root of your SD card, overwriting the existing files if prompted.

Whenever in doubt, compare the folder structure in the archive from e.g. Tesla Menu and nx-ovlloader with the folder structure on your SD card.

Tesla Menu's archive contains switch folder and should go wherever switch folder is on your SD card i.e. root.
Same for he nx-ovlloader, its archive contains atmosphere folder and should go wherever atmosphere folder is on your SD card i.e. once again, root.

 

[Thee_Almighty]

Extract them both to the root of your SD card, overwriting the existing files if prompted.

Whenever in doubt, compare the folder structure in the archive from e.g. Tesla Menu and nx-ovlloader with the folder structure on your SD card.

Tesla Menu's archive contains switch folder and should go wherever switch folder is on your SD card i.e. root.
Same for he nx-ovlloader, its archive contains atmosphere folder and should go wherever atmosphere folder is on your SD card i.e. once again, root.

You are the man, it all works now!

Question, in my hbmenu, I have something called Reboot to Hekate Version 1.0, when I click on it, it gives me an error saying "Failed to open hekate.bin"

I read somewhere I might have to rename and move a file somewhere?
Can someone shed some light on this, thanks!

 

[Blythe93]

I read somewhere I might have to rename and move a file somewhere?

Grab the latest Hekate's payload, rename it to payload.bin and put it onto the root of your SD card.

I personally use Atmosphere's Reboot to Payload app (i.e reboot_to_payload.nro located in the switch folder) but I've replaced the Atmosphere's reboot_payload.bin with the Hekate's renamed hekate_ctcaer_x.x.x.bin. No need for anything else, really.

 

[josete2k]

Atmosphere/libraries/libstratosphere/include/stratosphere/ncm/ncm_system_content_meta_id.hpp # line 342

    struct TinfoilId {
        u64 value;

        constexpr operator ProgramId() const {
            return { this->value };
        }

        constexpr inline bool operator==(const TinfoilId &) const = default;
        constexpr inline bool operator!=(const TinfoilId &) const = default;

        static const TinfoilId Start;

        static const TinfoilId Tinfoil;
        static const TinfoilId TinfoilForwarder;

        static const TinfoilId End;
    };

    inline constexpr const TinfoilId TinfoilId::Start                         = { 0x0500000000000000ul };
  
    inline constexpr const TinfoilId TinfoilId::TinfoilForwarder              = { 0x0500000000010000ul };
    inline constexpr const TinfoilId TinfoilId::Tinfoil                       = { 0x050000BADDAD0000ul };

    inline constexpr const TinfoilId TinfoilId::End                           = { 0x050000C000000000ul };

    inline constexpr bool IsTinfoilId(const ProgramId &program_id) {
        return (TinfoilId::Start <= program_id && program_id <= TinfoilId::End) || IsTinfoilId(program_id);
    }

    inline constexpr bool IsTinfoilId(const TinfoilId &) {
        return true;
    }

Atmosphere/stratosphere/loader/source/ldr_meta.cpp # line 210

        if (loc.program_id == ncm::TinfoilId::Tinfoil) {
            if (hos::GetVersion() >= hos::Version_19_0_0) {
                FixDebugCapabilityForHbl(static_cast<util::BitPack32 *>(meta->acid_kac), meta->acid->kac_size / sizeof(util::BitPack32));
                FixDebugCapabilityForHbl(static_cast<util::BitPack32 *>(meta->aci_kac),  meta->aci->kac_size  / sizeof(util::BitPack32));
            }
        }

        if (loc.program_id == ncm::TinfoilId::TinfoilForwarder) {
            if (hos::GetVersion() >= hos::Version_19_0_0) {
                FixDebugCapabilityForHbl(static_cast<util::BitPack32 *>(meta->acid_kac), meta->acid->kac_size / sizeof(util::BitPack32));
                FixDebugCapabilityForHbl(static_cast<util::BitPack32 *>(meta->aci_kac),  meta->aci->kac_size  / sizeof(util::BitPack32));
            }
        }

This does make both tinfoil and it's internal retroarch forwarder run (it spawns a plain hbmenu application forwarder)

Working here!!! Thanks.

 

[Rubicant8]

Working here!!! Thanks.

Is this attachment something which folks on 19.0.1 can extract to root for a likely tinfoil forwarder fix?

 

[josete2k]

Is this attachment something which folks on 19.0.1 can extract to root for a likely tinfoil forwarder fix?

It's my own compilation of atmosphere... And Yes, tinfoil 18 is working even using the self installer.

Note: You need sys-patch in order to get it working because loader patches are not the same.

 

[Rubicant8]

It's my own compilation of atmosphere... And Yes, tinfoil 18 is working even using the self installer.

Note: You need sys-patch in order to get it working because loader patches are not the same.

Installed both and tinfoil works again, thank you!

 

[tsukimaru]

Hi, I need help on a switch that I can't figure out.
PicoFly with RP2040 tiny has just been installed (no previous installation was made prior to this) and the switch is constantly checking if the software can be played. I've already verified that all my packages are up to date, sigpatches also up to date (got them from this thread and also from sigmapatches, none worked). This switch hasn't had a downgrade as far as I'm aware since it was untouched prior, and it's currently on HOS 19.0.1.

I've triple checked my packages, sigpatches, but nothing seems to work and I'm very confused as to why. Has anyone experienced this and found a solution?

 

[impeeza]

Hi, I need help on a switch that I can't figure out.
PicoFly with RP2040 tiny has just been installed (no previous installation was made prior to this) and the switch is constantly checking if the software can be played. I've already verified that all my packages are up to date, sigpatches also up to date (got them from this thread and also from sigmapatches, none worked). This switch hasn't had a downgrade as far as I'm aware since it was untouched prior, and it's currently on HOS 19.0.1.

I've triple checked my packages, sigpatches, but nothing seems to work and I'm very confused as to why. Has anyone experienced this and found a solution?

install SYS-Patch Sysmodule and restart your console

 

[HenryBaby]

I have a mariko unit that I just updated to 19.0.1 in stock. Rebooted and getting a blue screen. Same with sysmmc. I updated hekate and atmosphere to their respective latest versions, and stock/sysmmc is still giving me a blue screen. Emummc works fine tho, and also if I use Hekate -> Reboot -> OFW option then it boots fine into stock. What am I missing?

 

[impeeza]

I have a mariko unit that I just updated to 19.0.1 in stock. Rebooted and getting a blue screen. Same with sysmmc. I updated hekate and atmosphere to their respective latest versions, and stock/sysmmc is still giving me a blue screen. Emummc works fine tho, and also if I use Hekate -> Reboot -> OFW option then it boots fine into stock. What am I missing?

same of above install SYS-Patch Sysmodule and restart your console OR KEEP IT OFFLINE.

 

[HenryBaby]

same of above install SYS-Patch Sysmodule and restart your console OR KEEP IT OFFLINE.

I did, but still getting the blue screen. Hmm. Not sure what I'm doing wrong.

 

[impeeza]

I did, but still getting the blue screen. Hmm. Not sure what I'm doing wrong.

CAN YOU PLEASE SHARE A SCREEN SHOT OF YOUR BOSD.

 

[HenryBaby]

CAN YOU PLEASE SHARE A SCREEN SHOT OF YOUR BOSD.

EDIT: I tried putting a random CFW pack on another SD card and it boots fine, so I guess something is not updated properly on my normal SD card. I'll figure it out tho. Thank you @impeeza!

 

[Hayato213]

EDIT: I tried putting a random CFW pack on another SD card and it boots fine, so I guess something is not updated properly on my normal SD card. I'll figure it out tho. Thank you @impeeza!

That is different compare to Atmosphere crash screen. Blue color is kernel

 

[Blythe93]

EDIT: I tried putting a random CFW pack on another SD card and it boots fine, so I guess something is not updated properly on my normal SD card. I'll figure it out tho. Thank you @impeeza!

You could try backing up atmosphere and bootloader folders on your original SD card before deleting them and replacing with the fresh Atmosphere, Hekate and sys-patch files. If everything goes well, it should work.

Last time I got blue screen was when something was wrong with the latest Hekate version at that time on the Erista units and only while I was trying to load Atmosphere's package3 via Hekate's FSS0.

 

[HenryBaby]

That is different compare to Atmosphere crash screen. Blue color is kernel

Yeah I thought so too, which is very strange that it booted fine into emummc.

You could try backing up atmosphere and bootloader folders on your original SD card before deleting them and replacing with the fresh Atmosphere, Hekate and sys-patch files. If everything goes well, it should work.

Last time I got blue screen was when something was wrong with the latest Hekate version at that time on the Erista units and only while I was trying to load Atmosphere's package3 via Hekate's FSS0.

This seems to have worked. Going to replace my modules and homebrew one by one and see if everything is back to normal.