-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to Argon-NX #12
Comments
Hekate has had chainloading since around ver. 3.0... No reason to change off the most popular payload when it does everything perfectly... I haven't updated my trinket in over a year and it runs flawlessly |
I guess my main concern with using Hekate to chain load would be then you're really just running two instances of Hekate - with one being older than the other. Argon boots and promptly hands to Hekate, and is actually designed for things like the Trinket. You can load Hekate without chain loading to Hekate, sure, but then you get no updates. |
AFAIK once hekate sees the update.bin in the bootloader folder it ceases further action and restarts using that bin. I'm fairly sure you're not running two instances (simultaneously) during a chainload. It's just hekate handing off to hekate. As far as updates atmosphere updater in the hbappstore will download/unzip/rename the hekate.bin and place it in the bootloader folder for you as well as copying over the new folder all from within HOS. I don't think it can get much easier than a one button untethered update... None of this matters though cause all this is is a method of pushing a payload, you can easily adapt this to argon if you really wanted to. There's no need to change the guide though since it works perfectly fine as is. |
It's mentioned in your readme that an open-source chainloader would mean the trinket wouldn't need reflashing. Argon-NX seems to fit this bill. Is there any consideration in including this by default?
The text was updated successfully, but these errors were encountered: