Hacking Do any Hekate payloads work for 3.0.0?

Im on 3.0.2 firmware any chance for hekate ?? Nobody care about 3.0.X users so best chance for hbl is update ??

Just wait a couple of weeks for atmosphere to be released and then you will have access to HBL aswell
 
hekate works on any FW and always will.
You're dancing about their question. They already stated that they've used pegaswitch, and the DNS method, and wish not to. Hekate itself works on any firmware, but this person wants to patch firmware to just load horizon and not need wifi to launch hbl. There's nothing wrong with this, and hekate currently doesn't support launching 3.0.0 patched firmware. Some people are getting update nags when using the DNS method, effectively killing hbl on 3.0.0
 
You're dancing about their question. They already stated that they've used pegaswitch, and the DNS method, and wish not to. Hekate itself works on any firmware, but this person wants to patch firmware to just load horizon and not need wifi to launch hbl. There's nothing wrong with this, and hekate currently doesn't support launching 3.0.0 patched firmware. Some people are getting update nags when using the DNS method, effectively killing hbl on 3.0.0
How am I dancing about it? I am always answering their question.
 
Last edited by Kubas_inko,
I have a Switch on 3.0.1, and although Hekate works for dumping the nand, it is unable to load custom FW. This prevents me from loading HBL.

The commit on 5/12 added 4xx support, but I think 3.0.0 and 3.0.1 still need to be patched.

From pkg1.c:

Code:
static const pkg1_id_t _pkg1_ids[] = {
    { "20161121183008", 0, 0x1900, 0x3FE0, { 2, 1, 0 }, 0x40014020, _secmon_1_patchset }, //1.0.0
    { "20170210155124", 0, 0x1900, 0x3FE0, { 0, 1, 2 }, 0x4002D000, _secmon_2_patchset }, //2.0.0
    { "20170519101410", 1, 0x1A00, 0x3FE0, { 0, 1, 2 }, 0x4002D000, NULL }, //3.0.0
    { "20170710161758", 2, 0x1A00, 0x3FE0, { 0, 1, 2 }, 0x4002D000, NULL }, //3.0.1
    { "20170921172629", 3, 0x1800, 0x3FE0, { 1, 2, 0 }, 0x4002B000, _secmon_5_patchset }, //4.0.0
    { "20180220163747", 4, 0x1900, 0x3FE0, { 1, 2, 0 }, 0x4002B000, _secmon_6_patchset }, //5.0.0
    { NULL, 0, 0, 0, 0 } //End.
};

Edit: Oops, I meant to write 3.0.1, not 3.0.3

Does that mean it's supposed to work on 1.0.0? Because I either get a pink or blue screen
 
Consider yourselves lucky that you can't run Hekate. It's not meant for regular users to load and mess around with. Its got a lot of issues such as not working in sleep mode. IMO, you're not missing out on much. And last but not least, summer is almost here:wink:
 
Of course, but when that code says it works on 1.0.0 it's hard not to try it
All hekate payloads work on all FWs. That doesn't mean that the patch will actually do something. If you are on 1.0.0, hekate is used for nand backup only. But you can do the same via pegaswitch + you can lunch hbl from pegaswitch.
Edit: didn't know that there is fork for 1.0.0.
 
Last edited by Kubas_inko,
Itd be really nice if we got hekate port for 3.0.1 so i wouldnt be tempted to update and lose potentional softmod in the future. Itd be really nice. (Never shouldve done the offline update for odyssey at christmas last year like an idiot X-x)
 
Last edited by ,
  • Like
Reactions: Azel
Well actually my version of hekate (1.5) supports firmware launching in all versions except 3.0.1, 3.0.2.
Not published here yet. Check github.
 
I dont know why people would update instead of just waiting

Im on 2.3.0 and I will just wait for atmosphere to start messing with my switch
 

Site & Scene News

Popular threads in this forum