Hacking [RCM Payload] Hekate - CTCaer mod

[BaamAlex]

Love you guys all!

Wanna ask you humble, does Hekate 5.6.0 supports the new Atmosphere 1.0.0-pre?

Obviously not...tf?

 

[Adran_Marit]

Love you guys all!

Wanna ask you humble, does Hekate 5.6.0 supports the new Atmosphere 1.0.0-pre?

not sure if hekate has been updated yet but I seem to recall Scires did testing with hekate pointing to the new stuff

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

not sure if hekate has been updated yet but I seem to recall Scires did testing with hekate pointing to the new stuff

From discord last night, I'm under the assumption it will with the following config, until hekate updates

 

[ZachyCatGames]

Love you guys all!

Wanna ask you humble, does Hekate 5.6.0 supports the new Atmosphere 1.0.0-pre?

It works fine if you update your config to use the new "secondary" archive ("atmosphere/package3").

 

[Adran_Marit]

It works fine if you update your config to use the new "secondary" archive ("atmosphere/package3").

Like in the screenshot I posted above

 

[ZachyCatGames]

Like in the screenshot I posted above

I saw and am stating that works

 

[Krude]

Now that TSEC keys are derived in hekate, can you now boot stock on >7.0 without atmosphère?

 

[BaamAlex]

Now that TSEC keys are derived in hekate, can you now boot stock on >7.0 without atmosphère?

You can always boot stock without atmosphère. Also in the past.

 

[Krude]

You can always boot stock without atmosphère. Also in the past.

Wrong. You needed atmosphere to boot stock on FWs 7+ because of TSEC boot, which is why the hekate .ini template for booting stock looked like this:

[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1

# This disables kernel patching and CFW kips.
# Includes exosphere and warmboot, ONLY when >= 7.0.0 and Erista.
# Includes exosphere on Mariko.
# Exosphere/warmboot are not identifiable as it is now.
# This is the closest to OFW, especially when AutoRCM is needed.

The question is, can we now just simply put "stock=1" for all firmwares and expect it to work flawlessly? Or do we still need atmo exosphere on higher ones?

 

[Tyvar1]

hekate v5.6.1 and Nyx 1.0.7 are now released!

- HOS 13.0.0 Support
- Nyx TSEC Keys info/dump replaced with Lockpick RCM
- Create/Change/Migrate emuMMC now uses a unique ID

Check release log for more!https://t.co/LX5oGSDUf2

— CTCaer (@CTCaer) September 19, 2021

 

[MassiveRican]

Hi everyone, I recently updated to AMS 1.1.1 and Hekate v.5.6.3/Nyx v.10.8 and updated my Sys/emuNAND to 13.0.0, did a clean install but not sure where I'm going wrong here. So far I can go into emuNAND no prob but reboot 2 payload just restarts atmosphere which loads up my emuNAND. Sorry if the question has been asked 1000x, is there something I'm missing here? I already tried rename the latest hekate.bin file to reboot_payload.bin and that I think just makes it boot to a blackscreen after I choose reboot to payload.

Here's my hekate_ipl.bin

Spoiler

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=98
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[EmuNAND]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

 

[drgnslayers]

Hi everyone, I recently updated to AMS 1.1.1 and Hekate v.5.6.3/Nyx v.10.8 and updated my Sys/emuNAND to 13.0.0, did a clean install but not sure where I'm going wrong here. So far I can go into emuNAND no prob but reboot 2 payload just restarts atmosphere which loads up my emuNAND. Sorry if the question has been asked 1000x, is there something I'm missing here? I already tried rename the latest hekate.bin file to reboot_payload.bin and that I think just makes it boot to a blackscreen after I choose reboot to payload.

Here's my hekate_ipl.bin

Spoiler

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=98
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[EmuNAND]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Look there: https://rentry.org/MigrateToAtmosphere1_0_0 It does work

 

[clasnas]

# Exosphere/warmboot are not identifiable as it is now.

Is there an explanation as to why this is the case? I'm considering using autoRCM and use hekate to boot into sysNAND with OFW, but Im worried of increasing my ban risk.

 

[BaamAlex]

# Exosphere/warmboot are not identifiable as it is now.

Is there an explanation as to why this is the case? I'm considering using autoRCM and use hekate to boot into sysNAND with OFW, but Im worried of increasing my ban risk.

Banned for using autorcm? I would say that's unlikely. I mean, they could detect that... technically. Because the boot partition is corrupted iirc. But i never heard from autorcm usage related bans. Using nsps, cheating online is very ban risky.

 

[clasnas]

Banned for using autorcm? I would say that's unlikely. I mean, they could detect that... technically. Because the boot partition is corrupted iirc. But i never heard from autorcm usage related bans. Using nsps, cheating online is very ban risky.

I'm not too worried about autoRCM, its about the use of Atmpspheres exosphere and warmboot to boot OFW. I've read its undetectable, but I'd like to see some documentation if available.

 

[ZachyCatGames]

I'm not too worried about autoRCM, its about the use of Atmpspheres exosphere and warmboot to boot OFW. I've read its undetectable, but I'd like to see some documentation if available.

There's 0 telemetry in that area and the only way they could really detect it from userspace is by calling ams smcs, which would cause a panic on stock firmware.

 

[ganons]

So switch was updated to 13.2.0 (ex fat)

have the latest atmos and hekate
On boot it says

Missing LP0 (sleep mode) lib!
Missing or Old Minerva lib!

Update bootloader folder!

Press any key...

edit:
formatted a saller sd card to fat32, I get into hekate but new error
Failed to identify kernel!
Failed to launch HOS!

 

[BaamAlex]

Update bootloader folder!

There is your problem. Update hekate.

 

[ganons]

There is your problem. Update hekate.

I have since then with latest hektate

formatted a saller sd card to fat32, I get into hekate but new error
Failed to identify kernel!
Failed to launch HOS!

 

[BaamAlex]

Atmosphère updated?

 

[Tyvar1]