Hacking [RCM Payload] Hekate - CTCaer mod

[BaamAlex]

I updated my firmware through the official updater to 7.0.1. But my burnt fuses are 8 instead of 9. Is that good or not? AutoRCM is enabled.

 

[CTCaer]

I updated my firmware through the official updater to 7.0.1. But my burnt fuses are 8 instead of 9. Is that good or not? AutoRCM is enabled.

You probably updated while in CFW. Atmo has protection for that and your autorcm was not lost. And that's why you still have 8 fuses.
Or you had the jig plugged in and you were holding VOL UP while the install finished. Entered rcm and re enabled autorcm

 

[crow132]

You probably updated while in CFW. Atmo has protection for that and your autorcm was not lost. And that's why you still have 8 fuses.
Or you had the jig plugged in and you were holding VOL UP while the install finished. Entered rcm and re enabled autorcm

wait, didnt know about that.. so choidujour is not needed anymore?

 

[BaamAlex]

Or you had the jig plugged in and you were holding VOL UP while the install finished. Entered rcm and re enabled autorcm

Ehm. No. The console restarted normally after updating. After this i shutted down the console and put the jig in to start Hekate. I mean the console works fine.

 

[BaamAlex]

Does that mean i can downgrade to 6.2 if i want that?

 

[M7L7NK7]

wait, didnt know about that.. so choidujour is not needed anymore?

If you want to update to something other than the very latest it is

 

[Draxzelex]

Ehm. No. The console restarted normally after updating. After this i shutted down the console and put the jig in to start Hekate. I mean the console works fine.

No what he meant was you were most likely running Atmosphere before you installed the update which prevented AutoRCM from being removed.

Does that mean i can downgrade to 6.2 if i want that?

Technically you can downgrade to any firmware with the current exploit even if you burnt fuses. The only stipulation is that if you downgrade to a firmware that expects a lower fuse count than your current fuse count, you can only boot the console through RCM. A fuse count of 8 indicates that you can downgrade to a firmware of 6.2 or higher without RCM. For future reference, you can find a list of fuse counts and their respective firmware versions here.

 

[BaamAlex]

No what he meant was you were most likely running Atmosphere before you installed the update which prevented AutoRCM from being removed.

Yes. Atmosphere was already running while i updated the console.

 

[hippy dave]

Suggestion, maybe put a really explicit message on the NAND restore screen, spelling out that you have to restore matching boot0/1 with rawnand if changing fw version, or shit will break? See so many posts about that issue. (I'm not calling it an issue with hekate, to be clear, it's a common user error that a warning might help avoid.)

 

[BaamAlex]

spelling out that you have to restore matching boot0/1

That is interesting. I want to know that too. Should i restore boot0/1 and my rawnand in case of a brick? Or is that not important?

 

[hippy dave]

That is interesting. I want to know that too. Should i restore boot0/1 and my rawnand in case of a brick? Or is that not important?

I guess what you would need to restore would depend on the kind of brick, you'd just need to restore the part which got broken, assuming your backup is the same firmware version your Switch is currently on. I'm talking about changing firmware versions, people commonly restore a rawnand.bin of an older firmware version but don't restore the matching boot0/1 (so they leave their existing boot0/1 of a newer fw version), then their system won't boot.

 

[BaamAlex]

The system boots. But only with rcm if i understand that correctly. Because the fuses don't match the firmware. Or how does the system work behind it? Do I have a mistake of my own?

 

[Draxzelex]

The system boots. But only with rcm if i understand that correctly. Because the fuses don't match the firmware. Or how does the system work behind it? Do I have a mistake of my own?

Your system will not boot if boot0/boot1 don't match the firmware of the system. Meaning boot0/boot1 are also firmware-specific but people often forget this when they restore a NAND backup that is a different firmware than the one they are currently running. Having a mismatched boot0/boot1 usually leads to a blue screen when you try to turn on the console.

There are two different things that can happen when the fuses don't match the firmware when you boot normally. If your fuses are lower than the firmware, your console burns them to compensate so that the fuse count matches the firmware. If your fuses are higher than your firmware, your console doesn't boot up and the screen stays black. It doesn't even enter RCM in this state. This would be classified as a soft brick since you can just boot into RCM and use a bootloader that bypasses the fuse check which all of them do nowadays.

 

[BaamAlex]

I have backed up my boot0 and 1. So it is okay when i restore it in case of a brick?

 

[Hayato213]

I have backed up my boot0 and 1. So it is okay when i restore it in case of a brick?

Yea that is the whole point of having a NAND backup and having a way to restore it.

 

[BaamAlex]

A nand backup is a must have for me

 

[Hayato213]

A nand backup is a must have for me

But becareful to not burn your fuse.

 

[TunisDream]

I was on 7.0.1 with ReinNX and my 8 year old son updated to 8.0 ReinNX is not starting but I can load hekate with RCM. Is there a way to restore last known working situation? I have a backup, but i need my Zelda savefiles

 

[shchmue]

I was on 7.0.1 with ReinNX and my 8 year old son updated to 8.0 ReinNX is not starting but I can load hekate with RCM. Is there a way to restore last known working situation? I have a backup, but i need my Zelda savefiles

sure if you replace everything in all the partitions including boot0 and boot1 it NOT USER with the ones from the backup you have. or back up your saves manually and restore them after restoring the backup.

 

[CTCaer]

hekate v4.10 is released!

Full 8.0.0 support
And more

Check OP or HERE for changelog or more..[/SIZE]