Hacking [RCM Payload] Hekate - CTCaer mod

[VIERcntHOLZ]

Kind of noobish question:
If i select "Stock" in Hekate, will my fuses be burnt, or will it just launch the ofw without patches?
and
Can i include the Launch of ReiNX via [Launch], instead of using Payloads => ReiNX.bin? (by editing the hekate_ipl?)

 

[sj33]

Fuses will not be burnt.

 

[Nazosan]

I'm not sure why this is happening, and nobody I've asked has an explanation so I am posting this issue as I think it might be related to Hekate. fusee_primary boots into Atmosphere normally, but I am unable to with Hekate.

For what it's worth -- and you may already know this -- Hekate can chainload other payloads, so you can use Hekate and have it boot fusee_primary anyway. It's not a proper solution to the actual problem, but it would get you into the system using Hekate.

Can i include the Launch of ReiNX via [Launch], instead of using Payloads => ReiNX.bin? (by editing the hekate_ipl?)

Absolutely. You can load its kips or you can add an entry in the INI to chainload the payload so you don't have to start it manually in the menu.


Does ReiNX offer anything worthwhile anymore versus just going straight to the source (Atmosphere)?

 

[sj33]

At this point, ReiNX and Atmosphere are pretty similar. ReiNX is built upon an older version of Atmosphere but has its own bootloader, focused on modularity regarding loading kips etc. However, ReiNX has started to focus more on implementing features from SX so we may see greater divergence from now on.

 

[fodder]

For what it's worth -- and you may already know this -- Hekate can chainload other payloads, so you can use Hekate and have it boot fusee_primary anyway. It's not a proper solution to the actual problem, but it would get you into the system using Hekate.

Yeah, I was was doing that, and still am, CTCaer is helping me with this, seems to be related to 6.2 as I'm able to use Hekate to boot Atmosphere on any firmware below 6.2 normally. I don't think this has happened to anyone else, so idk, my Switch is cursed

 

[kristiansja]

@CTCaer your neweest update was confusing for me. I cant remember what payload is on my modchip, but it seems to load 4.6 just fine. Do i need to reflash my modchip? because i cant get it recognized on my pc

 

[Hayato213]

@CTCaer your neweest update was confusing for me. I cant remember what payload is on my modchip, but it seems to load 4.6 just fine. Do i need to reflash my modchip? because i cant get it recognized on my pc

If you are on 6.2 then you would need 4.5 or 4.6, as for lower firmware you can use 4.2. Also if you are on a mod chip you need UF2 not bin format payload.

 

[kristiansja]

If you are on 6.2 then you would need 4.5 or 4.6, as for lower firmware you can use 4.2. Also if you are on a mod chip you need UF2 not bin format payload.

you dont know what you are talking about. Hekate loads update.bin if its newer. i was wondering if 4.6 breaks this

 

[Hayato213]

you dont know what you are talking about. Hekate loads update.bin if its newer. i was wondering if 4.6 breaks this

Lol at least I got a working trinket m0 switch and you don't, firmware 6.2 require minimum of hekate 4.5. Getting it to recognize your pc has nothing to do what uf2 was already flashed.

 

[Nazosan]

You're actually going to fight about this? 4.6 has in its description that it makes some changes on how the update is handled, so it is a valid question.

you dont know what you are talking about. Hekate loads update.bin if its newer. i was wondering if 4.6 breaks this

It won't work in RCM mode. You need to get out of RCM first. Basically boot the system up and then double press the button to get it into flash mode then instead of during RCM. If the chip is working at all, assuming it uses the same mechanism as the Trinket M0/SwitchMe/etc then it should be able to connect to the PC when done right. And it doesn't use any drivers or anything -- it just shows up as a USB drive. (This flash method is actually pretty amazing and I hope more things do it this way in the future.)

 

[CTCaer]

@CTCaer your neweest update was confusing for me. I cant remember what payload is on my modchip, but it seems to load 4.6 just fine. Do i need to reflash my modchip? because i cant get it recognized on my pc

Basically the chainloader had a bug that was occurring only for the update.bin chainloading. It was trying to call at x100 bytes before the payload.
Strangely enough, this works because the data there is normally empty and the CPU is able to traverse to the real payload.
But there are certain circumstances that can break it. (If that ram area is filled with instruction data, it halts there. E.g. launching 6.2 compatible fusee can also break it)

This was fixed in v4.6. And I call it breaking change, because you have to flash your modchip once again.
Hopefully, after that, it wont be needed anymore, because I also made the new versions to redo the hwinit, in case there's a change on it.

In the end, update.bin with versions 4.0 - 4.5 mostly work. Just have in mind, that if you see any black screen after injecting, that the problem is this one.
So it's up to you if you want to reflash.

 

[OvOvOv]

Question: I made a backup with old hetake version. Now i want to restore it, but files path have changed. I do not have eMMC S/N (/Backup/<eMMC S/N>/Restore/Partitions/*), i only have backup folder. How can i get it?

 

[CTCaer]

Question: I made a backup with old hetake version. Now i want to restore it, but files path have changed. I do not have eMMC S/N (/Backup/<eMMC S/N>/Restore/Partitions/*), i only have backup folder. How can i get it?

Easiest way is to backup BOOT0/1 or dump fuses.

I would suggest to also make a new backup with your current state before restoring your old one.

 

[mspy]

Quick question: I have this backed up this files BOOT0 + BOOT1 + rawnand.bin with v3.2, I assume its best to use the same version to perform a restore so in what path exactly do I place those files on my SDCard ?

 

[CTCaer]

Quick question: I have this backed up this files BOOT0 + BOOT1 + rawnand.bin with v3.2, I assume its best to use the same version to perform a restore so in what path exactly do I place those files on my SDCard ?

Of course not.

Use v4.6.

Also backup your current before restoring, in case something goes wrong.

After your new backup you'll see the new folder structure. It's /backup/<your emmc s/n>/restore/ where you put them. And your new backup will be in /backup/<your emmc s/n>/

 

[mspy]

But I don't wanna do a new backup again just to know the 'new' path, there isn't another way? I already got a working backup so I guessed that using v3.2 would be fine as well ?

 

[CTCaer]

But I don't wanna do a new backup again just to know the 'new' path, there isn't another way? I already got a working backup so I guessed that using v3.2 would be fine as well ?

Yeah, do a backup of BOOT0/1 which is ultra fast.

EDIT:
Don't use v3.2.
There's a reason new versions exist.
This is also a disclaimer ^. It's not my problem if you want to tread dangerously.

 

[shchmue]

there's another way, just take note of the very tiny text error message when the restore fails, it prints the path it checks to screen

 

[jackirate]

Hi guys, i got my SXPRO Working, i wiped everything and it worked so i guess i missed something.

Next question, im currently performing a full nand back up using hekate via SXOS. Ive used 5% battery so far and not even hit 1%!

Am i missing something or is this not going to die before i hit 50% lol.

 

[GATWYAY3.2]

will a back up to the USB storage be possible