Hacking [RCM Payload] Hekate - CTCaer mod

[CTCaer]

That's awesome.....my hope is we start to see some ready to go kits that have the new Nand chip already mounted on a board with the quick connector, and then we will start to see it gain traction as it will be easy as pie to upgrade.

This is up to china.
I did mine to a local smd repair shop be fore months. But if I can get a 256GB samsung already mounted on the custom pcb, it would be the best.

 

[fatterdude2000]

Great tool. thanks. Any chance this will have gamecard slot firmware backup/restore in future?

 

[CTCaer]

Great tool. thanks. Any chance this will have gamecard slot firmware backup/restore in future?

This is an ASIC chip. The fw is loaded on boot.
What's needed is to patch the older fs versions.

 

[annson24]

So for hekate v4.1, having a portable payload injector (i.e trinket, gemma, modchips, ns-atmosphere, etc.), when a new hekate is released, we can just place it as update.bin inside the bootloader folder and that will be the one to be booted up, is that right? So we won't have to inject hekate to the modchips/dongle every time there is an update?

 

[CTCaer]

So for hekate v4.1, having a portable payload injector (i.e trinket, gemma, modchips, ns-atmosphere, etc.), when a new hekate is released, we can just place it as update.bin inside the bootloader folder and that will be the one to be booted up, is that right? So we won't have to inject hekate to the modchips/dongle every time there is an update?

That's correct. And it's since hekate v4.0.
When I added the chainloading to everything, I also added the self update chainloading.

In v4.1 I just fixed the version check. (In v4.0, the check was always succeeded and it was always using the update.bin.)

Also I wanted to have hekate in appstore, but I forgot to put it.
Probably v4.2 will be there though.

 

[kazehaya]

Hi, is there any risk of gettin banned if i use hekate just to make a nand backup?

 

[sj33]

Hi, is there any risk of gettin banned if i use hekate just to make a nand backup?

There's never a 0% risk, but you should be safe.

 

[Deleted User]

Hekate 4.1 that he literally just released today has full 6.0 support. Couldn't you have at least have checked the first post...

(No, I’m just blind (sarcastic answer) ...

Hekate - CTCaer mod v4.1

* CFW Launching for ALL current updates (1.0.0, 2.X, 3.X, 4.X, 5.X)

———————-
Next time before answering. )



@CTCaer thanks for the job mate

 

[XaneTenshi]

(No, I’m just blind (sarcastic answer) ...

Hekate - CTCaer mod v4.1

* CFW Launching for ALL current updates (1.0.0, 2.X, 3.X, 4.X, 5.X)

———————-
Next time before answering. )



@CTCaer thanks for the job mate

Blind/Ignorant, your choice really...

_______________________________

Changelog:
v4.1:

• Full 6.0.0 support
  Secmon/ kernel patches, FS patches, sleep mode, hw config, etc.
• Improved .ini/payload handling
  hekate_ipl.ini is no longer required and hekate does not hang on empty folders.
• PWM backlight
  You can now change the backlight brightness.
• Auto full power off when the device woke up from HOS' power off
  Usefull with modchips/dongles when using AutoRCM. (You can see it as a breathing backlight with hekate's logo).
• Backup can be now cancelled when in the writing process (white bar), by pressing VOL UP + DOWN.
• Self update chainloading properly checks for version number now to avoid uneeded loads.
• Support payloads with broken/bad hw init...
• Added ipatches info and dumping of patched/unpatched bootrom and ipatches
• Corrected some hw config changes found in 5.x-6.0.0
• More boot reasons and bootrom registers restores to normal
• It now properly restores BCT on dev units from where it's supposed to.
• Added warning message when the bootloader library for sleep mode is missing.
• And many many bugfixes

______________________________

This is from the exact same post ás the text you copied btw

 

[Deleted User]

Blind/Ignorant, your choice really...

_______________________________

Changelog:
v4.1:

• Full 6.0.0 support
  Secmon/ kernel patches, FS patches, sleep mode, hw config, etc.
• Improved .ini/payload handling
  hekate_ipl.ini is no longer required and hekate does not hang on empty folders.
• PWM backlight
  You can now change the backlight brightness.
• Auto full power off when the device woke up from HOS' power off
  Usefull with modchips/dongles when using AutoRCM. (You can see it as a breathing backlight with hekate's logo).
• Backup can be now cancelled when in the writing process (white bar), by pressing VOL UP + DOWN.
• Self update chainloading properly checks for version number now to avoid uneeded loads.
• Support payloads with broken/bad hw init...
• Added ipatches info and dumping of patched/unpatched bootrom and ipatches
• Corrected some hw config changes found in 5.x-6.0.0
• More boot reasons and bootrom registers restores to normal
• It now properly restores BCT on dev units from where it's supposed to.
• Added warning message when the bootloader library for sleep mode is missing.
• And many many bugfixes

______________________________

This is from the exact same post ás the text you copied btw

Nobody offended you so don’t try to offend ... I saw that in the same day (since nobody had posted that worked) I was skeptic

Have a nice weekend

 

[XaneTenshi]

Nobody offended you so don’t try to offend ... I saw that in the same day (since nobody had posted that worked) I was skeptic

Have a nice weekend

You are right and I do apologize. I regret writing that like 5 minutes after I had posted it:S

Your 2nd post just triggered me because if you had bothered to scroll a little and checking the whole OP you would have known and I just see this way too often.

 

[CTCaer]

Hi, is there any risk of gettin banned if i use hekate just to make a nand backup?

You are 100% ok.
As long as you select Power off or Reboot (Normal) after that.

 

[Zap Rowsdower]

You are 100% ok.
As long as you select Power off or Reboot (Normal) after that.

So in terms of legitimate online usage, is Reboot (Normal) any 'safer' with hypothetical detection than booting stock?
https://gbatemp.net/threads/about-restoring-a-clean-rawnand-before-going-online.518729/#post-8293444

 

[sj33]

The point is that you don't want to be booting from a custom bootloader if going online, you want to be using the official bootloader.

Nobody actually knows what causes a ban, but logic dictates that Nintendo cannot know if you've used hekate to backup as long as don't boot into Horizon.

 

[ishidad5]

Hi I'm using hekate v4.1 to dump the keys, got the done msg but I can not see any files created on my SD card and when try to use kezplez-nx it says that there is no files on the sd card, I'm on fw 5.1.0 and sd card is exfat, am i doing something wrong?

 

[CTCaer]

Hi I'm using hekate v4.1 to dump the keys, got the done msg but I can not see any files created on my SD card and when try to use kezplez-nx it says that there is no files on the sd card, I'm on fw 5.1.0 and sd card is exfat, am i doing something wrong?

The files are in /backup/<emmc S/N>/dumps/

And you need to use an existing fork of keplez that can find the backups and the dumps in the new structure. Otherwise move the backups and the dump folder in /backup/

 

[Maupiti]

The files are in /backup/<emmc S/N>/dumps/

And you need to use an existing fork of keplez that can find the backups and the dumps in the new structure. Otherwise move the backups and the dump folder in /backup/

The one (Keplez) in this thread https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/
works with latest release of Hekate

 

[metaljay]

The files are in /backup/<emmc S/N>/dumps/

And you need to use an existing fork of keplez that can find the backups and the dumps in the new structure. Otherwise move the backups and the dump folder in /backup/

i keep getting Error (4) when restoring? what am i doing wrong now?

 

[AlexTCGPro]

So I updated from 4 to 4.1 and now I need to inject the payload twice to be able to use it, first time it shows the logo and then nothing happens, then I have to reconnect the cable and inject it again and now it works, running 5.1

 

[CTCaer]

i keep getting Error (4) when restoring? what am i doing wrong now?

You just quoted a post of mine.
Check it better. /backup/<eMMC S/N>/restore

So I updated from 4 to 4.1 and now I need to inject the payload twice to be able to use it, first time it shows the logo and then nothing happens, then I have to reconnect the cable and inject it again and now it works, running 5.1

That's the auto power off, if the console was awaken because you powered off from HOS.
Useful to protect your battery from uneeded autorcm.
v4.2 will have an option to disable it.