As the title says, why can't we have those payloads zip files directly on their github page? People don't trust zip files found online as those could potentially brick the switch (this happened in the past)
Thank you, but i suggested to put those zips directly on the official github pageThere is old hekate.
Anyway, here you go. Few hekate(s) and SX payload.
Also, here is my "amazing" fork with those payloads.
What do you mean by the official page? I put the .h on the fork. I can't put them anywhere else.Thank you, but i suggested to put those zips directly on the official github page
What do you mean by the official page? I put the .h on the fork. I can't put them anywhere else.
Then make a pull request for that. I really can't do anything about that.i mean, for i.e., in the hekate/releases page (https://github.com/CTCaer/hekate/releases) should be the trinket m0 zip file
Then make a pull request for that. I really can't do anything about that.
Or SX payload which has it from the start.Because the devs aren't interested in supporting every single device that could potentially deliver their payload. Think about it. It doesn't make any sense.
Get your payloads from trustworthy sources here or build them yourself.
If you already have Hekate 4 running, it supports chain loading so you don't ever have to update the Trinket after the first time. Just update your configuration ini.
If you already have Hekate 4 running, it supports chain loading so you don't ever have to update the Trinket after the first time. Just update your configuration ini.
Can you please explain what should i do? Or at least link me a guide? Thanks!