Hacking [RCM Payload] Hekate - CTCaer mod

[x65943]

Let's try to stay on topic guys

Philosophical discussions of time are not on topic and will be deleted

 

[OvOvOv]

Is it possible to load OFW with autoRCM through hekate?

 

[Krude]

Yes. Hekate has an option to boot "stock" which disables all kernel patches but keeps your fuses intact.

 

[OvOvOv]

Yes. Hekate has an option to boot "stock" which disables all kernel patches but keeps your fuses intact.

How can I use it? I cant find this options un Hekate menu. Do I need to use Atmos ?

Edit: Do i have to remive AutoRCM doesn't it?

 

[Krude]

Check the hekate config template, it has boot entries for booting stock:
https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini

Note that to boot stock on Firmware 7.0.X, you'll need to download atmosphere 0.8.5 and put it on your SD card. It will still boot stock, but the atmosphere files are needed to get around the FW7+ security measures.
If you're on lower firmware you don't need it.

 

[OvOvOv]

Check the hekate config template, it has boot entries for booting stock:
https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini

Note that to boot stock on Firmware 7.0.X, you'll need to download atmosphere 0.8.5 and put it on your SD card. It will still boot stock, but the atmosphere files are needed to get around the FW7+ security measures.
If you're on lower firmware you don't need it.

Thanks, then I just need to copy that configuration to the hekate_ipl file and download the atmos folder so I can use OFW 7.0.1 without burning efuses?

 

[Krude]

Yeah, make sure "/atmosphere/fusee-secondary.bin" (latest one) exists on your SD card and use the "Stock All FW" boot entry from the template.

 

[OvOvOv]

Yeah, make sure "/atmosphere/fusee-secondary.bin" (latest one) exists on your SD card and use the "Stock All FW" boot entry from the template.

I copied:
stock=1
fss0=atmosphere/fusee-secondary.bin
to hekate_ipl.ini but does not show any options about launch stock fw.

Edit: Sorry i put the file in the wrong location. I get it work! Thanks!!!

 

[Inb404]

Hello guys, firts of all. Sorry for my bad english. Hope you can help me..

My switch is on 7.0.1, atmosphere 8.5 and payload is hekate 4.8.

I turn on autorcm and autoboot to cfw.

Now my switch when is complete off wont turn on to stock fw if i press power button, also i cant enter in recovery mode +- volume and power.

The only whay for turn it on is plugin my Phone and inject payload with nx loader. Switch turn on and enter into atmosphere.


If i remove my sd card switch dont turn on with power button, only with nx loader and payloader to hekate,so i cant access to stock firmware anymore. I Lunch hekate payload without sd, turn off rcm and autoboot. But is not working.


Also in both case with or without the sd, the switch dont charge the battery if i plug the wall adapte.


On hekate screen a red sing show an error message, sleep Mode files missing.


How can i fix this??

 

[pLaYeR^^]

Hello guys, firts of all. Sorry for my bad english. Hope you can help me..

My switch is on 7.0.1, atmosphere 8.5 and payload is hekate 4.8.

I turn on autorcm and autoboot to cfw.

Now my switch when is complete off wont turn on to stock fw if i press power button, also i cant enter in recovery mode +- volume and power.

The only whay for turn it on is plugin my Phone and inject payload with nx loader. Switch turn on and enter into atmosphere.


If i remove my sd card switch dont turn on with power button, only with nx loader and payloader to hekate,so i cant access to stock firmware anymore. I Lunch hekate payload without sd, turn off rcm and autoboot. But is not working.


Also in both case with or without the sd, the switch dont charge the battery if i plug the wall adapte.


On hekate screen a red sing show an error message, sleep Mode files missing.


How can i fix this??

If you have turned on AutoRCM, than you can't simply boot in OFW with just pressing the power button. That's how AutoRCM works: If you boot the switch, your console enter RCM right away. So how and why do you want to boot in OFW? If you update with ChoiDujourNX and boot in OFW without custom payload, your switch will burn fuses to 7.0.1. That's not what you want. So I suggest you to read what you are installing and how it works before you actually do it.

 

[Inb404]

If you have turned on AutoRCM, than you can't simply boot in OFW with just pressing the power button. That's how AutoRCM works: If you boot the switch, your console enter RCM right away. So how and why do you want to boot in OFW? If you update with ChoiDujourNX and boot in OFW without custom payload, your switch will burn fuses to 7.0.1. That's not what you want. So I suggest you to read what you are installing and how it works before you actually do it.

I got it second hand, never hacked with oficial 7.0.1 update vía WiFi. Make a 32gb backup and hack de switch Now autorcm is off, i can enter to OFW. When i plug the jig entre rcm and luch the payload atmosphere auto Lunch. The only way to see the hetake menú is injecting the payload in rcm without the sd card. I turn off autoboot but nothing happend

 

[natkoden]

I got it second hand, never hacked with oficial 7.0.1 update vía WiFi. Make a 32gb backup and hack de switch Now autorcm is off, i can enter to OFW. When i plug the jig entre rcm and luch the payload atmosphere auto Lunch. The only way to see the hetake menú is injecting the payload in rcm without the sd card. I turn off autoboot but nothing happend

but what are you trying to achieve, exactly?

 

[whobroughtben]

I'm looking to clean up my system in preparation for switching to SXOS specifically for emuNAND. While looking at my backup folder from before I did any modding, i noticed that i have a bunch of files, but no rawnand.bin. Does this effect my ability to do a full system restore to clean NAND? Here are the files I have:

BOOT0
BOOT1
dumps:
  fuses.bin
  kfuses.bin
  tsec_keys.bin
partitions:
  BCPKG2-1-Normal-Main
  BCPKG2-2-Normal-Sub
  BCPKG2-3-SafeMode-Main
  BCPKG2-4-SafeMode-Sub
  BCPKG2-5-Repair-Main
  BCPKG2-6-Repair-Sub
  PRODINFO
  PRODINFOF
  SAFE
  SYSTEM
pkg1:
  nxloader.bin
  pkg1_decr.bin
  secmon.bin
  warmboot.bin
pkg2:
  ini1.bin
  kernel.bin
  pkg2_decr.bin
dumps:
  fuses.bin
  kfuses.bin

Really hoping i can still do a clean NAND restore with these files. Any input or guidelines appreciated!

 

[XaneTenshi]

I'm looking to clean up my system in preparation for switching to SXOS specifically for emuNAND. While looking at my backup folder from before I did any modding, i noticed that i have a bunch of files, but no rawnand.bin. Does this effect my ability to do a full system restore to clean NAND? Here are the files I have:

BOOT0
BOOT1
dumps:
  fuses.bin
  kfuses.bin
  tsec_keys.bin
partitions:
  BCPKG2-1-Normal-Main
  BCPKG2-2-Normal-Sub
  BCPKG2-3-SafeMode-Main
  BCPKG2-4-SafeMode-Sub
  BCPKG2-5-Repair-Main
  BCPKG2-6-Repair-Sub
  PRODINFO
  PRODINFOF
  SAFE
  SYSTEM
pkg1:
  nxloader.bin
  pkg1_decr.bin
  secmon.bin
  warmboot.bin
pkg2:
  ini1.bin
  kernel.bin
  pkg2_decr.bin
dumps:
  fuses.bin
  kfuses.bin

Really hoping i can still do a clean NAND restore with these files. Any input or guidelines appreciated!

Well the good news is that you have the files needed to do a system restore. The "bad" news, (saying "bad" because I am not 100% certain), is that you only have the bare minimum for a nand restore. The files you have only rebuild the system partitions (so you have enough to recover from a brick), but you don't have a full rawnand.bin, so I'm not sure what happens to the content on your Switch, as the user partition is excluded and will not be replaced by your backup. But you can try the restore ether way:

The files you'll need are the boot0/1 files, and all the partitions, from BCPKG2-1-Normal-Main, to SYSTEM. You must restore the partition files by placing them inside /backup/<serial number>/restore/partition. The boot files go in /restore. Refer to the OP for more info. Don't know if you'll need the pkg files for example. Never did this type of restore.

But like I said, I'm not 100& certain you can go back to a clean system.

 

[nutsack]

Is there any reason why hekate_ctcaer_4.8.bin won't launch my AMS 0.8.1 CFW over 6.2.0 when the hekate_ctcaer_4.5.bin payload works great on it? Does 4.8 only work with 7.0.0 and above? When I try to launch CFW from the 4.8 payload it just goes right back into RCM mode while it launches fine from the 4.5 payload. I'm injecting the payloads through TegraRcmGui on PC.

 

[stick267]

Is there any reason why hekate_ctcaer_4.8.bin won't launch my AMS 0.8.1 CFW over 6.2.0 when the hekate_ctcaer_4.5.bin payload works great on it? Does 4.8 only work with 7.0.0 and above? When I try to launch CFW from the 4.8 payload it just goes right back into RCM mode while it launches fine from the 4.5 payload. I'm injecting the payloads through TegraRcmGui on PC.

Maybe the formatting of your hekate_ipl.ini doesn't match what Hekate 4.8 is looking for?

Why not update to Atmosphere 0.8.6 and Hekate 4.9.1?

 

[brollikk]

so all sigpatch problems with hekate are fixed now?

 

[Draxzelex]

so all sigpatch problems with hekate are fixed now?

Wrong thread. Sig patches have nothing to do with Hekate. Those are either due to the patches themselves or the CFW you are launching with Hekate which is usually Atmosphere.

 

[blindpet]

I have been trying to use Hekate 4.9.1 deliverd by TegraRCMGui 2.5 to my Switch (OFW 4.1) but when I click launch the bootloader folder is somehow emptied from the SD card so I get the error 'could not open bootloader/hekate_ipl.ini'. Is it some safety mechanism that it is deleting everything in the bootloader folder? I have verified this about 5 times, I copy over the files from AtlasNX Kosmos latest release and everything is there but upon Launch that error shows up immediately, I stick the SD card back in the laptop and the bootloader folder is empty.

I am using a 4 GB SD card so it is formatted as FAT32, my current goal is to update to 6.2 so I can use exFAT with a 400 GB SD card.

Any help would be greatly appreciated.

 

[blindpet]

Turned out to be a bad SD card!