Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,195,164
  • Replies Replies 3,331
  • Likes Likes 128
I did the Dump Package 1-2 by mistake. Is there any way to restore the things changed by doing this? I was exploring for raw nand dump fuction and clicked on that. Also i sadly did this before backing up my nand and boot 0 and boot 1 files. Are these files altered permanently? If not how do i revert these files back to factory so i can properly backup my switch before using any altered firmware.
 
Last edited by RobbieDanger,
I did the Dump Package 1-2 by mistake. Is there any way to restore the things changed by doing this? I was exploring for raw nand dump fuction and clicked on that. Also i sadly did this before backing up my nand and boot 0 and boot 1 files. Are these files altered permanently? If not how do i revert these files back to factory so i can properly backup my switch before using any altered firmware.
Nothing was changed in eMMC. Dump means get the data from something and copy them somewhere. Here eMMC -> Sd card.
 
I did the Dump Package 1-2 by mistake. Is there any way to restore the things changed by doing this? I was exploring for raw nand dump fuction and clicked on that.
Nothing was changed in eMMC. Dump means get the data from something and copy them somewhere. Here eMMC -> Sd card.
Awesome, thanks for the reply. Currently backing up rawnand.bin with no issues. My intentions are to have a clean backup available, glad to hear I did not screw that up!
 
  • Like
Reactions: Azel
I think i soft bricked my device. I first nand backed everything up through hekate. Afterwards I activated SX OS and put it on auto rcm. Later learned that my switch needs update to 'see'' exfat sdcards. So I tried the get the exfat support by doing the biskeydump & memeloader method. The switch now wont boot normally, I can only send payloads through pc but I cant get into normal boot in any way unfortunately.
I tried restoring BCPKG2-1-Normal-Main etc through Hackdismount but the problem persists. What should I do? Btw my nintendo still wont ''work'' with exfat but only fat32.
 
Restore your BOOT0/1 and RAWNAND backup.
Wont the exfat thing pose a problem for the rawnand restoring?(because in the topic it states only exfat works with rawnand restoring) My switch asked me to update to make it work with exfat (back when switch was booting fine)
 
Last edited by ts61fa,
Wont the exfat thing pose a problem for the rawnand restoring?(because in the topic it states only exfat works with rawnand restoring) My switch asked me to update to make it work with exfat (back when switch was booting fine)
Hekate does not care if you have the exfat update. That's for horizon only. Hekate supports exFAT out of the box.

And that support is only inside hekate. When you are outside of it, it falls on the loaded firmware.
 
  • Like
Reactions: ts61fa
Hekate does not care if you have the exfat update. That's for horizon only. Hekate supports exFAT out of the box.

And that support is only inside hekate. When you are outside of it, it falls on the loaded firmware.
My nandbackuo was in parts because my sdcard was fat32 back then i guess. Can i just copy the parts to root of sd (exfat format) and restore or do I havr to merge the files first?(if so any tutorial for that?)
Thx in advance!
 
Wont the exfat thing pose a problem for the rawnand restoring?(because in the topic it states only exfat works with rawnand restoring) My switch asked me to update to make it work with exfat (back when switch was booting fine)
So you already updated FW on your console? And what FW was when you made nand backup?
 
My nandbackuo was in parts because my sdcard was fat32 back then i guess. Can i just copy the parts to root of sd (exfat format) and restore or do I havr to merge the files first?(if so any tutorial for that?)
Thx in advance!
Currently you have to merge them. Otherwise, the restore option wouldn't say exfat only. The restore works only on exfat cards because it's bigger than 4GB.

There are file joiner scripts provided where you downloaded the payload.
 
So you already updated FW on your console? And what FW was when you made nand backup?
No i didnt update any firmware, the switch came with 4.0.1 fw. Immediately i nandbacked it up with hekate on my fat32 sdcard and after that i activated SX OS pro and enabled auto rcm mode. But later I learned that my Switch had problems with exfat(need to update) and while trying to update sdcard method it got softbricked. So now im tryng to restore it
 
No i didnt update any firmware, the switch came with 4.0.1 fw. Immediately i nandbacked it up with hekate on my fat32 sdcard and after that i activated SX OS pro and enabled auto rcm mode. But later I learned that my Switch had problems with exfat(need to update) and while trying to update sdcard method it got softbricked. So now im tryng to restore it
AutoRCM? You tried to load the payload and launch horizon with either of the options (e.g. Stock)?
 
AutoRCM? You tried to load the payload and launch horizon with either of the options (e.g. Stock)?
Im srry im not really following, i enabled the auto rcm mode of SX Os pro. Later when i tried to fix the exfat thing with biskeydumping and hackdismount this softbrick thing started.
 
Im srry im not really following, i enabled the auto rcm mode of SX Os pro. Later when i tried to fix the exfat thing with biskeydumping and hackdismount this softbrick thing started.
A console with AutoRCM is actually bricked. And you need to always launch Horizon (switch OS) through hekate or other payloads.
Try it before restoring anything.
Download the sd files or the template I have on the repo and save the hekate_ipl.ini to the root of your sd card.
Launch hekate and choose Launch firmware. Select Stock.
 
  • Like
Reactions: ts61fa
A console with AutoRCM is actually bricked. And you need to always launch Horizon (switch OS) through hekate or other payloads.
Try it before restoring anything.
Download the sd files or the template I have on the repo and save the hekate_ipl.ini to the root of your sd card.
Launch hekate and choose Launch firmware. Select Stock.
Ok thx im omw home gonna try asap
 
A console with AutoRCM is actually bricked. And you need to always launch Horizon (switch OS) through hekate or other payloads.
Try it before restoring anything.
Download the sd files or the template I have on the repo and save the hekate_ipl.ini to the root of your sd card.
Launch hekate and choose Launch firmware. Select Stock.
A console with AutoRCM is actually bricked. And you need to always launch Horizon (switch OS) through hekate or other payloads.
Try it before restoring anything.
Download the sd files or the template I have on the repo and save the hekate_ipl.ini to the root of your sd card.
Launch hekate and choose Launch firmware. Select Stock.
THX! I finally got to boot normally into switch. Just to be sure: I allways need the dongle(or payload through pc/phone) otherwise I cant even boot normally into switch because of auto rcm? I thought the dongle was only necessary if you want sx os functions, but u can allways stock boot I thought, Because when I attached the dongle it booted through SX OS, but without the dongle it didnt do anything, is this normal?

and another question: Why didnt it boot earlier when I attached the dongle? I HAVE to first payload hekate >> stock after doing stuf with emmc?
 
Last edited by ts61fa,
THX! I finally got to boot normally into switch. Just to be sure: I allways need the dongle(or payload through pc/phone) otherwise I cant even boot normally into switch because of auto rcm? Because when I attached the dongle it booted through SX OS, but without the dongle it didnt do anything, is this normal?

and another question: Why didnt it boot earlier when I attached the dongle? I HAVE to first payload hekate >> stock after doing stuf with emmc?
With AutoRCM you need to start OFW or SX OS via dongle or android/PC + payload. You do not need jig with AutoRCM.
 
With AutoRCM you need to start OFW or SX OS via dongle or android/PC + payload. You do not need jig with AutoRCM.
Oh so with Auto RCM you MUST have dongle or payload with pc/phone even to boot to stock? Thats what I didnt know.
 
Oh so with Auto RCM you MUST have dongle or payload with pc/phone even to boot to stock? Thats what I didnt know.
AutoRCM bricks your console by corrupting boot sector, so yeah you will always need to start console via RCM in any firmware.
 
  • Like
Reactions: ts61fa

Site & Scene News

Popular threads in this forum