Hacking [RCM Payload] Hekate - CTCaer mod

[CTCaer]

So, Ive tried searching through the thread and cant find anyone who had my same issue. I have my boot0.bin and boot1.bin the the correct restore folder. I was able to restore my rawnand.bin just fine but when I try to do the BOOT1 & 2 I get error (4) even though the files are in the correct location.

Am I missing something simple? any help is much appreciated.

Edit1: I've tried 2 different cards. both 200GB sandisk cards onee FAT32 and the other exFAT(which i restored the nand with)

Edit2: Just tried a 32GB samsung card and same thing. What am I doing wrong?

As always error 4 is file not found.

the answer is all over that thread and in OP.
2 boot files and your main physical partition.

Named: BOOT0, BOOT1, rawnand.bin

Move them to /backup/<emmc s/n>/restore/

 

[Resaec]

-too slow-

 

[cbloveday]

that's /bootloader/sys/libsys_lp0.bso on your SD card with a hekate install, but regardless sleep mode is not gonna work if your firmware is below your fuse count

New question based off my previous issue. Until 6.2 is supported how can I totally power off the system when not in use so I don't have to push the payload twice. Currently when I choose Power Off or Reboot both options auto Reboot into my AutoRCM.

Edit: My previous was updated to 6.2 then used ChoidujourNX to get myself back into 6.1 but somehow in the whole process still managed to burn the 8th fuse (thought I'd followed the guide correctly to not burn it but I guess not). Now that my Sleep doesn't work I have to push payloads twice if the system sleeps. I'm just wanting a way to fully power off when the system isn't being used and then when I do power it back on it comes back into my AutoRCM and only have to push the payload once (and so the system isn't still draining the battery when I thought it was powered off.

 

[shchmue]

New question based off my previous issue. Until 6.2 is supported how can I totally power off the system when not in use so I don't have to push the payload twice. Currently when I choose Power Off or Reboot both options auto Reboot into my AutoRCM.

Edit: My previous was updated to 6.2 then used ChoidujourNX to get myself back into 6.1 but somehow in the whole process still managed to burn the 8th fuse (thought I'd followed the guide correctly to not burn it but I guess not). Now that my Sleep doesn't work I have to push payloads twice if the system sleeps. I'm just wanting a way to fully power off when the system isn't being used and then when I do power it back on it comes back into my AutoRCM and only have to push the payload once (and so the system isn't still draining the battery when I thought it was powered off.

hold power for 12+ seconds to power completely off without payload. you burned the fuse upgrading not downgrading.

 

[CTCaer]

New question based off my previous issue. Until 6.2 is supported how can I totally power off the system when not in use so I don't have to push the payload twice. Currently when I choose Power Off or Reboot both options auto Reboot into my AutoRCM.

Edit: My previous was updated to 6.2 then used ChoidujourNX to get myself back into 6.1 but somehow in the whole process still managed to burn the 8th fuse (thought I'd followed the guide correctly to not burn it but I guess not). Now that my Sleep doesn't work I have to push payloads twice if the system sleeps. I'm just wanting a way to fully power off when the system isn't being used and then when I do power it back on it comes back into my AutoRCM and only have to push the payload once (and so the system isn't still draining the battery when I thought it was powered off.

hold power for 12+ seconds to power completely off without payload. you burned the fuse upgrading not downgrading.

If you use autoRCM, press PWR once (to go into that mode) and then do this ^.

 

[cbloveday]

hold power for 12+ seconds to power completely off without payload. you burned the fuse upgrading not downgrading.

I do the 12+ seconds to Power Off but it still boots into AutoRCM even when doing that. I've tested that by doing the 12+ second hold to power down left it over night tried to push hekate once I plugged it into my PC and once hekate loaded it showed 0% battery at the bottom. Once I recharged the system I did the hold to power down again but this time left it plugged into my PC and after about 2 seconds of being powered off my TegraRCM picked it up as being in AutoRCM mode again without even toughing any buttons on the Switch what so ever. I have also tried using the Power Off in the system itself with the same results. I don't have this issue with my second Switch that is still on 6.0.1 running AMS7.5 only having this issue with the one that went through the update. Wondering if it could possibly have something to do with the update or maybe I have a bad file on my SD Card but the SD card is brand new 256 Samsung I took it straight out of the package loaded up the SD files from GitHub then re installed my games that were on the old SD card.

 

[gundamu]

I do the 12+ seconds to Power Off but it still boots into AutoRCM even when doing that. I've tested that by doing the 12+ second hold to power down left it over night tried to push hekate once I plugged it into my PC and once hekate loaded it showed 0% battery at the bottom. Once I recharged the system I did the hold to power down again but this time left it plugged into my PC and after about 2 seconds of being powered off my TegraRCM picked it up as being in AutoRCM mode again without even toughing any buttons on the Switch what so ever. I have also tried using the Power Off in the system itself with the same results. I don't have this issue with my second Switch that is still on 6.0.1 running AMS7.5 only having this issue with the one that went through the update. Wondering if it could possibly have something to do with the update or maybe I have a bad file on my SD Card but the SD card is brand new 256 Samsung I took it straight out of the package loaded up the SD files from GitHub then re installed my games that were on the old SD card.

go in rcm, send hekate, power off from it.
there you go

 

[CTCaer]

I do the 12+ seconds to Power Off but it still boots into AutoRCM even when doing that. I've tested that by doing the 12+ second hold to power down left it over night tried to push hekate once I plugged it into my PC and once hekate loaded it showed 0% battery at the bottom. Once I recharged the system I did the hold to power down again but this time left it plugged into my PC and after about 2 seconds of being powered off my TegraRCM picked it up as being in AutoRCM mode again without even toughing any buttons on the Switch what so ever. I have also tried using the Power Off in the system itself with the same results. I don't have this issue with my second Switch that is still on 6.0.1 running AMS7.5 only having this issue with the one that went through the update. Wondering if it could possibly have something to do with the update or maybe I have a bad file on my SD Card but the SD card is brand new 256 Samsung I took it straight out of the package loaded up the SD files from GitHub then re installed my games that were on the old SD card.

I assumed that you didn't do this so fast.

The trigger happens in 15s. So if you do the PWR and then PWR+12s then it will power on.

So better wait 15s and then do the 12s thing

 

[cbloveday]

I assumed that you didn't do this so fast.

The trigger happens in 15s. So if you do the PWR and then PWR+12s then it will power on.

So better wait 15s and then do the 12s thing

I'll try it again. Didn't actually use a timer or anything but guessed it was about the right times.

Edit: Didn’t wanna double post warning since mine was the last post. Will the release of the new Atmosphere fix my Sleep mode issue now that you know of?

 

[noctis90210]

just want to ask question, im originaylly 4.1.0... then updated to 6.1.0 using choidujour without burning fuses (autorcm enabled)...

it is safe to reset/restore to factory on 6.1.0? will it burn fuses or not? thanks...

 

[CTCaer]

I'll try it again. Didn't actually use a timer or anything but guessed it was about the right times.

Edit: Didn’t wanna double post warning since mine was the last post. Will the release of the new Atmosphere fix my Sleep mode issue now that you know of?

It's not an issue actually. It's because autorcm. It can be patched though.

just want to ask question, im originaylly 4.1.0... then updated to 6.1.0 using choidujour without burning fuses (autorcm enabled)...

it is safe to reset/restore to factory on 6.1.0? will it burn fuses or not? thanks...

It's possible yeah. I never checked the specifics, but I suppose that it may update BOOT0 and remove autorcm and thus burn your fuses on reboot.

 

[noctis90210]

It's possible yeah. I never checked the specifics, but I suppose that it may update BOOT0 and remove autorcm and thus burn your fuses on reboot.

thanks... how about updating thru normal means (pop up update during launching game) while in autorcm? will it burn fuses?

 

[smf]

thanks... how about updating thru normal means (pop up update during launching game) while in autorcm? will it burn fuses?

Yes it will burn fuses.

 

[noctis90210]

@CTCaer is there a away to remove update nag (during launching the game) while in autorcm enabled cfw?

 

[Fishguy6564]

Any plans on adding 6.2.0 support? There's some stuff I use Hekate for that the payload atmosphere cfw uses can't do at the moment.

 

[tiliarou]

@CTCaer is there a away to remove update nag (during launching the game) while in autorcm enabled cfw?

This has nothing to do with Hekate.

just want to ask question, im originaylly 4.1.0... then updated to 6.1.0 using choidujour without burning fuses (autorcm enabled)...

it is safe to reset/restore to factory on 6.1.0? will it burn fuses or not? thanks...

Any downgrade you do should happen through choidujourNX: that way, it will re-enable autorcm right after installation.

 

[Sayora]

How exactly is Linux chainloaded from Hekate? What files need to be copied to SD?

 

[CTCaer]

hekate v4.5 is now released!

Support to 6.2.0 is here!

Check HERE for more..


Happy smash-ing tomorrow ^^

 

[huma_dawii]

hekate v4.5 is now released!

Support to 6.2.0 is here!

Check HERE for more..


Happy smash-ing tomorrow ^^

@tomGER

 

[Draxzelex]

@tomGER

Fooled you all so hard that it's already June 16th

https://github.com/AtlasNX/Kosmos/releases/tag/v11.5 Have fun with 100% boot success rates and more!