Hacking Autoboot Emunand- Cant access Hekate -vol on Atm 0.10.1

onibaku · Dec 13, 2019

So I just updated my atmosphere to 0.10.1, my emunand is on autoboot and before I would just have to hit restart and hold down vol- button to boot into hekate but it doesnt seem to work. My emunand is on 9.0.1 (sysnand 4.1.0 - caffeine). I checked the changelog for the atmosphere update and couldnt find any info on this change?

My hekate is also on 5.0.2, not sure if that matters

EDIT: So i moved all the new files from hekate 5.1.0 but still i cant seem to boot into the hekate menu. Is there any way i can disable the autoboot through editing an .ini file? Also I have an ipatched switch so i dont think i can send payloads via rcm.

gnze796 · Dec 13, 2019

Boot while holding Volume - should fix it. But do it all the way. After payload injection

The Real Jdbye · Dec 13, 2019

onibaku said:
So I just updated my atmosphere to 0.10.1, my emunand is on autoboot and before I would just have to hit restart and hold down vol- button to boot into hekate but it doesnt seem to work. My emunand is on 9.0.1 (sysnand 4.1.0 - caffeine). I checked the changelog for the atmosphere update and couldnt find any info on this change?

My hekate is also on 5.0.2, not sure if that matters

EDIT: So i moved all the new files from hekate 5.1.0 but still i cant seem to boot into the hekate menu. Is there any way i can disable the autoboot through editing an .ini file? Also I have an ipatched switch so i dont think i can send payloads via rcm.

Keep holding Vol- for a few seconds after you see the Hekate logo or your custom boot logo. It hasn't been changed, so if it doesn't work for you, you may have a dodgy Vol- button (might just need cleaning with some IPA)

onibaku · Dec 13, 2019

The Real Jdbye said:
Keep holding Vol- for a few seconds after you see the Hekate logo or your custom boot logo. It hasn't been changed, so if it doesn't work for you, you may have a dodgy Vol- button (might just need cleaning with some IPA)

Hmm the volume button seems to work fine, its a pretty new Switch (bought it less than two months ago). It just happened after i updated my atmosphere.. I read that someone else had the same issue on the Switch Noob Paradise thread. I tried it again and it didnt work but I did notice that once i was booted into atmosphere my volume was all the way down xD so im pretty sure the volume button works but maybe there's something wrong with my hekate set up

When booting into atmosphere I used to get the Kosmos logo and then the Atmosphere logo, but now its just the atmosphere logo. Not sure if that means something or if it was just a part of the atmosphere update..

The Real Jdbye · Dec 13, 2019

onibaku said:
Hmm the volume button seems to work fine, its a pretty new Switch (bought it less than two months ago). It just happened after i updated my atmosphere.. I read that someone else had the same issue on the Switch Noob Paradise thread. I tried it again and it didnt work but I did notice that once i was booted into atmosphere my volume was all the way down xD so im pretty sure the volume button works but maybe there's something wrong with my hekate set up

When booting into atmosphere I used to get the Kosmos logo and then the Atmosphere logo, but now its just the atmosphere logo. Not sure if that means something or if it was just a part of the atmosphere update..

Are you sure you're loading the Hekate payload and not fusee-primary?
Edit: atmosphere\reboot_payload.bin is replaced with fusee-primary by the Atmosphere update. You need to put the newest Hekate payload there instead.

onibaku · Dec 13, 2019

The Real Jdbye said:
Are you sure you're loading the Hekate payload and not fusee-primary?
Edit: atmosphere\reboot_payload.bin is replaced with fusee-primary by the Atmosphere update. You need to put the newest Hekate payload there instead.

Ahh okay, I didnt know that.. yeah so Ive probably been automatically booting fusee-primary then! Thank you so much, I'll try it out, so I just rename the hekate payload to reboot_payload.bin and paste it there?

The Real Jdbye · Dec 13, 2019

onibaku said:
Ahh okay, I didnt know that.. yeah so Ive probably been automatically booting fusee-primary then! Thank you so much, I'll try it out, so I just rename the hekate payload to reboot_payload.bin and paste it there?

Yeah, you'll have to do it every time you update Atmosphere.

onibaku · Dec 13, 2019

The Real Jdbye said:
Yeah, you'll have to do it every time you update Atmosphere.

Okay thats no problem

thank you so much, really appreciate it.

Deleted member 534671 · Sep 18, 2020

I’m having the same problem. I’ve enabled auto boot in Hekate, I’ve tried pressing the - volume button on boot to get into Hekate but no dice.

I’m on a patched switch on 4.1.0 running the pegascape exploit to run CFW.

I’ve read through this thread but I’m a noob so I don’t understand what the OP did to rectify the problem of not getting back into Hekate.

Any help would be greatly appreciated.

The Real Jdbye · Sep 18, 2020

ImFire said:
I’m having the same problem. I’ve enabled auto boot in Hekate, I’ve tried pressing the - volume button on boot to get into Hekate but no dice.

I’m on a patched switch on 4.1.0 running the pegascape exploit to run CFW.

I’ve read through this thread but I’m a noob so I don’t understand what the OP did to rectify the problem of not getting back into Hekate.

Any help would be greatly appreciated.

You need to replace reboot_payload.bin with the Hekate one if you're trying to get into Hekate after a reboot. If you're trying to get into Hekate after launching the exploit, are you sure you're launching the Hekate payload and not fusee-primary? There should be a Hekate logo that appears.

Deleted member 534671 · Sep 18, 2020

The Real Jdbye said:
You need to replace reboot_payload.bin with the Hekate one if you're trying to get into Hekate after a reboot. If you're trying to get into Hekate after launching the exploit, are you sure you're launching the Hekate payload and not fusee-primary? There should be a Hekate logo that appears.

Thank you for the reply. I just did this and booted into Hekate. Problem solved using the solution above.

Deleted member 534671 · Sep 18, 2020

Here’s what I did on my patched system on firmware 4.1.0 using pegascape to boot into CFW to get back into Hekate when Auto Boit was enabled in Hekate;

Remove your micro sd card from your switch and insert it into your PC

In the Atmosphere folder on your micro sd card remove the reboot_payload.bin to your desktop (you will need this putting back later so don’t delete it from your desktop)

After dragging and dropping the reboot_payload.bin file to your desktop for later you can delete reboot_payload.bin from your Atmosphere folder

Add the latest hekate_ctcaer_x.x.x.bin (x.x.x refers to the version number mine was 5.3.3 at the time of this post) payload file to the same folder from where you removed the reboot_payload.bin file earlier (the Atmosphere folder)

Rename the latest hekate_ctcaer_x.x.x.bin (x.x.x refers to the version number mine was 5.3.3 at the time of this post) payload file file to reboot_payload.bin

Reinsert your micro sd card into your switch

Boot into CFW as you normally would using pegascape

When you receive the onscreen notice to tap the screen and wait 3 seconds to tap the power button you must tap the screen and then power button as you normally would but immediately press and hold the volume - (down) button after you tap the power button (do not hold the power button, just hold the volume - (down) button)

Hold the volume - (down) button until you see the Hekate logo then release the volume - (down) button

You are now in Hekate again, it will ask you to set the time and date

Do what you need to do in Hekate and then press switch off (you can enable Auto Boot in Hekate again if you want to boot back into CFW and bypass the Hekate screen the next time you boot into CFW)

Wait for your switch to power down, remove your micro sd card and insert it back in to your PC

Go to the Atmosphere folder and delete the reboot_payload.bin file (this is the Hekate file we renamed earlier) from this folder

Drag and drop the original reboot_payload.bin (the one we removed earlier) from your desktop back to the Atmosphere folder

We are now back to how things were when we started

Hope this helps :-)

Hacking Autoboot Emunand- Cant access Hekate -vol on Atm 0.10.1

Lurker

Well-Known Member

*is birb*

Lurker

*is birb*

Lurker

*is birb*

Lurker

Well-Known Member

*is birb*

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum

is birb

is birb

is birb

is birb