Hacking [RCM Payload] Hekate - CTCaer mod

[hippy dave]

Sysnand has nothing to do with the cfw stuff. This can always be updated without any hesitation.

This isn't completely true advice. 12.0 updated the gamecard slot firmware, which made the gamecard slot inaccessible in 11.0.1 emummc - this happens once in a while.

 

[Serah]

Hi! May i ask does the newest version 5.5.5 supports atmosphere 19.2??
Thanks in advance!

 

[petspeed]

Hi! May i ask does the newest version 5.5.5 supports atmosphere 19.2??
Thanks in advance!

You can use Hekate 5.5.5 together with Atmosphere 0.19.2 to boot CFW yes.

 

[Serah]

You can use Hekate 5.5.5 together with Atmosphere 0.19.2 to boot CFW yes.

So that means it supports switch HOS 12.0.1 right?? Sorry for asking these questions hehe

 

[petspeed]

So that means it supports switch HOS 12.0.1 right?? Sorry for asking these questions hehe

That's correct

 

[loopout]

with the new fw on the wilds, does anyone knows if Hekate needs to update in order to boot OFW clean sysnand through fusee secondary?

Just wanting to update my clean sysnand to keep playing online games.

 

[BaamAlex]

with the new fw on the wilds, does anyone knows if Hekate needs to update in order to boot OFW clean sysnand through fusee secondary?

Just wanting to update my clean sysnand to keep playing online games.

You can boot the console without the hekate payload?!

 

[loopout]

You can boot the console without the hekate payload?!

yes, but I manage a couple of my friends' switches and they are not that hacking savvy, so I usually just prepare everything with autoRCM and then they just have to choose to boot stock sysnand or cfw emunand on each reboot.

 

[Tyvar1]

Failed to fetch tweet https://twitter.com/CTCaer/status/1392441014036533253

 

[Tyvar1]

Failed to fetch tweet https://twitter.com/CTCaer/status/1402109358864056322

 

[WayOfTheRoad]

Odd question about eMMC RAW GPP backup.

I get this error at 5% after using multiple different SD Cards (all legitimate) and formatting them in both Fat32 and ExFat, both 16k and 32k splits:

error reading 8192 blocks @ LBA 00308000

It tries 3x real quick and then aborts. My question is whether this is a sign of a bad NAND chip in general? For instance, if the NAND booted to an error code or was generally bricked, could the issue be that it cannot PHYSICALLY read the NAND chip or will a NAND backup happen even on an error or bricked Switch *as long as you can boot to RCM and Hekate*?

Thanks.

Edit: Also, if it is possible that it cannot physically read the NAND chip that would remove all possibility of writing to it to try to restore it, I assume. Right?

 

[Adamos_22]

I`ve starting to experience issue with starting up atmosphere after back to bootloader hekate from android 10 - KO rate is 100% starting fromhekate ver 5.5.7 on 5.5.6 problem do not exist

 

[BaamAlex]

I`ve starting to experience issue with starting up atmosphere after back to bootloader hekate from android 10 - KO rate is 100% starting fromhekate ver 5.5.7 on 5.5.6 problem do not exist

KO Rate? What's that?

 

[Adamos_22]

KO Rate? What's that?

failed attempts - done on 7 attempts all failed to start atmosphere

 

[BaamAlex]

Atmosphère boots always on my console without any problems.

 

[Adamos_22]

have you tried after back to hekate from android 10 ?

 

[spiderpie]

Recover EmuNAND after hekate update

Hello,
I made a mistake and when I wanted to update the boot loader folder by overwriting it, it somehow deleted the whole folder and copied the new hekate one.
Now when I launch hekate I can’t get anything in launch. No ofw or cfw
Is there a way to recover from this?
Thanks

 

[aldo3]

@CTCaer, any thoughts how I can get rawnand.bin.05 to dump and complete my nand backup?
I am trying to make nand backup, but when I dump eMMC raw using hekate 5.5.3 I get an error. I have partial nand dump with all rawnand.bin.xx files except rawnand.bin.05. When I set partial.idx file to 0x05 to resume the dump, only rawnand.bin.05 fails with this error every time:
error reading 8192 blocks @ LBA 01478000, from eMMC (try 1). Retrying...
error reading 8192 blocks @ LBA 01478000, from eMMC (try 2). Retrying...
error reading 8192 blocks @ LBA 01478000, from eMMC (try 3). Aborting...
please try again...
Failed!

Did you fix this? Having the same problem (when restoring the backup).

--------------------- MERGED ---------------------------

Odd question about eMMC RAW GPP backup.

I get this error at 5% after using multiple different SD Cards (all legitimate) and formatting them in both Fat32 and ExFat, both 16k and 32k splits:

error reading 8192 blocks @ LBA 00308000

It tries 3x real quick and then aborts. My question is whether this is a sign of a bad NAND chip in general? For instance, if the NAND booted to an error code or was generally bricked, could the issue be that it cannot PHYSICALLY read the NAND chip or will a NAND backup happen even on an error or bricked Switch *as long as you can boot to RCM and Hekate*?

Thanks.

Edit: Also, if it is possible that it cannot physically read the NAND chip that would remove all possibility of writing to it to try to restore it, I assume. Right?

Same here. Did you solve this?

 

[Tyvar1]

Failed to fetch tweet https://twitter.com/CTCaer/status/1431670707340066816

 

[mathew77]

Love you guys all!

Wanna ask you humble, does Hekate 5.6.0 supports the new Atmosphere 1.0.0-pre?