Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,195,292
  • Replies Replies 3,331
  • Likes Likes 128
Documentation on Atmosphere is extremely sparse, apparently, so i'll ask here since hekate is my go-to bootloader.

How do i go about using Hekate + Atmosphere? Do i start it via secondary payload, or do i chainload the primary or what? Do i need the BCT.ini if i load via Hekate? Can i use any of the Hekate patches together with Atmo?

Would a proper boot entry look like this?

[Atmosphere]
payload=fusee-primary.bin
BCT.ini is needed if you launch fusee-primary.

If you launch atmosphere from kips/exo you need to create an .ini boot entry for hekate to launch

Any idea why custom bootlogo Not work with my setup?

A use the Atmosphere "bootlogo.bmp" and put it on the root of my sd card...

In /bootloader/hekate.ipl ini i add/change under Config:

customlogo=1
logopath=/bootlogo.bmp

... But on every start/Restart the hekate boot Logo pops up?
logopath key is only for boot entries. If you want to change bootlogo for all boot entries, you put it at bootloader/bootlogo.bmp
If you want only for a specific entry, you put it the logopath key at its entry. Also the first slash is not needed (logopath=bootlogo.bmp)
(Also the customlogo=1 is needed at the config entry)
 
Thanks for replying.
Nothing is actually in that folder. I have no idea where to get the payload file. If it helps I followed the instructions on this video: .

Which cfw? REINX? You need to put the payload you want boot into bootloader/payloads Folder...the Payload.bin is normaly at the cfw zip inside(or Manually in github release Tab)

Also for ReiNX its inside the zip called "REINX.bin"
 
Last edited by Pyro1992,
  • Like
Reactions: RahRah
Which cfw? REINX? You need to put the payload you want boot into bootloader/payloads Folder...the Payload.bin is normaly at the cfw zip inside(or Manually in github release Tab)

Also for ReiNX its inside the zip called "REINX.bin"
Woo! Thanks! Ok so that actually worked lol, but I got an error at first so I googled it and tried a nightly build. It loaded the anime girl, but it looks just like a regular boot and I can't see the firmware because it's saying "system update is ready". I'm scared to hit System Update lol.
 
Last edited by RahRah,
Woo! Thanks! Ok so that actually worked lol, but I got an error at first so I googled it and tried a nightly build. It loaded the anime girl, but it looks just like a regular boot and I can't see the firmware because it's saying "system update is ready". I'm scared to hit System Update lol.
you see no visual firmware change^^ You can try now put HBmenu to REINX or something
 
Hi,

This all started from when my switch got bricked to the Switch Logo after install the bugged Pokemon Lets Go Pikachu.nsp that was released today.
My nand dump was created on 5.1 firmware before I did any CFW stuff, using Hekake 3.2. Attached is the list of list it created:
Today I updated my firmware to 6.1 firmware suing ChoidujourNX and it was working fine until I install that NSP.

Booted in Hekate 4.2 with the files copied onto the SD card and tried to restore which didn't work.
Created the create folder structure after some reading and put rawnand.bin file into the restore folder and tried restore boot0/1 which didn't work.
Tried restore emmc RAW GPP exfat only and the restore process started and completed in over an hour.
Rebooted and got black screen only but could still inject hekate.
Tried disabling AutoRCM in Hekate, no luck.
In Hekate I did went to Launch, Stock (noob mistake) and it did some process to the kernel, not good I know. It finished to a white screen.
Now rebooting takes me to a blue screen but I can at least inject hekate.
Tried restoring GPP partitions and it errored on user but the others were fine.
Rebooted, Blue screen.
I am currently restoring the rawnand.bin hoping that fixes the issue but if not I'm not sure what else to do or what I'm doing wrong.

Any help would be greatly appreciated. I'd be happy with a switch that boots in OFW and CFW, don't care about the games or saves, updates etc.
Thanks

Update - Restoring the Rawnand.bin again didn't help. Still boots to a blue screen :-(
 

Attachments

  • Capture.JPG
    Capture.JPG
    24.5 KB · Views: 217
Last edited by morpheus9394,
Hi,

This all started from when my switch got bricked to the Switch Logo after install the bugged Pokemon Lets Go Pikachu.nsp that was released today.
My nand dump was created on 5.1 firmware before I did any CFW stuff, using Hekake 3.2. Attached is the list of list it created:
Today I updated my firmware to 6.1 firmware suing ChoidujourNX and it was working fine until I install that NSP.

Booted in Hekate 4.2 with the files copied onto the SD card and tried to restore which didn't work.
Created the create folder structure after some reading and put rawnand.bin file into the restore folder and tried restore boot0/1 which didn't work.
Tried restore emmc RAW GPP exfat only and the restore process started and completed in over an hour.
Rebooted and got black screen only but could still inject hekate.
Tried disabling AutoRCM in Hekate, no luck.
In Hekate I did went to Launch, Stock (noob mistake) and it did some process to the kernel, not good I know. It finished to a white screen.
Now rebooting takes me to a blue screen but I can at least inject hekate.
Tried restoring GPP partitions and it errored on user but the others were fine.
Rebooted, Blue screen.
I am currently restoring the rawnand.bin hoping that fixes the issue but if not I'm not sure what else to do or what I'm doing wrong.

Any help would be greatly appreciated. I'd be happy with a switch that boots in OFW and CFW, don't care about the games or saves, updates etc.
Thanks

Update - Restoring the Rawnand.bin again didn't help. Still boots to a blue screen :-(
rawnand is paired with BOOT0/1. If you didn't restore these you can't boot.

These 2 must be exactly named BOOT0 and BOOT1
 
Im trying to restore my Boot0/boot1 partitions and well... it says ERROR 4 while opening back up!
You need to adhere to the folder structure.

if you have BOOT0/1 and rawnand.bin, you've put them in /backup/<eMMC S/N>/restore/
If you have only partitions and BOOT0/1 you've put them in /backup/<eMMC S/N>/restore/partitions/ and the BOOT0/1 to /backup/<eMMC S/N>/restore/

Where <eMMC S/N> is your eMMC serial number, as shows in the photos you took.

Error 4 is no file found and 5 is folder not found.
https://github.com/CTCaer/hekate/blob/master/bootloader/libs/fatfs/ff.h#L226
 
  • Like
Reactions: Ty_ and huma_dawii
I want to restore my NAND but I only have the files. I dont have the folder
/Backup/Restore/BOOT0 and /Backup/<eMMC S/N>/Restore/

How to I get those folder. Should I do a backup now to get the folder and replace the file with my nand backup
 
I want to restore my NAND but I only have the files. I dont have the folder
/Backup/Restore/BOOT0 and /Backup/<eMMC S/N>/Restore/

How to I get those folder. Should I do a backup now to get the folder and replace the file with my nand backup
yes
 
I want to restore my NAND but I only have the files. I dont have the folder
/Backup/Restore/BOOT0 and /Backup/<eMMC S/N>/Restore/

How to I get those folder. Should I do a backup now to get the folder and replace the file with my nand backup

^
Easiest and fastest way to recreate the folder stracture is to run Backup BOOT0/1.
 
[QUOTE = "wil32, post: 8160252, member: 457912"] Não consigo restaurar um backup. Erro (4) ao abrir backup [/ QUOTE]
me too
 
@CTCaer I got a odd question, but is it possible to get Hekate to log while the Switch is booting? To see how and what it reads?
 

Site & Scene News

Popular threads in this forum