Hekate unmounts and disables power to sd card when in hekate's main menus.
This ensures no corruption.
Nope customlogo entry was removed because it served no actual purpose.
It is now enforced if a bootlogo.bmp or a logopath= is found.
If you have newly found problems, please reply with your setup and I'll try to find the new bug when I have time.
This implies that sx os has actually 7.0.X support.
So, hekate:
[Stock] option is not removed. It works as before on 6.2.0 and under.
On 7.0.X you must use:
[Stock (7.0+)]
secmon=modules/required/exosphere.bin
warmboot=modules/required/lp0fw.bin
atmosphere=1
Exosphere supports maintenance mode. Just press the combo and keep holding it the moment you select Stock.
As for real stock or OFW, that works as before.
Without autorcm, you select reboot (Normal), in order to preserve fuses. (That ofc if you power off and go into rcm after HOS Power Off immediately.)
Or power off and press PWR to boot completely normally if you don't care about fuses.
Last edited by CTCaer,
kHekate unmounts and disables power to sd card when in hekate's main menus.
This ensures no corruption.
Nope customlogo entry was removed because it served no actual purpose.
It is now enforced if a bootlogo.bmp or a logopath= is found.
If you have newly found problems, please reply with your setup and I'll try to find the new bug when I have time.
This implies that sx os has actually 7.0.X support.
So, hekate:
[Stock] option is not removed. It works as before on 6.2.0 and under.
On 7.0.X you must use:
[Stock (7.0+)]
secmon=modules/required/exosphere.bin
warmboot=modules/required/lp0fw.bin
atmosphere=1
Exosphere supports maintenance mode. Just press the combo and keep holding it the moment you select Stock.
As for real stock or OFW, that works as before.
Without autorcm, you select reboot (Normal), in order to preserve fuses. (That ofc if you power off and go into rcm after HOS Power Off immediately.)
Or power off and press PWR to boot completely normally if you don't care about fuses.
some guy said he used newest hekate alone on fw 6.2 and stock option was not available, and payloads were blank
my guess is that you have to have atmos fully setup to use hekate payload for running ofw (he was using autorcm)
hmm or maybe he was missing the ini file?
idk guy was a complete noob
Last edited by Don Jon,
In 6.2.0 and lower, you just need an empty boot entry after the [config] entry.
[Stock]
without any kip or other option defined.
For example:
[Stock]
[CFW]
kip1=mplahmplah
...
This is the case with previous versions also. Only 7.0.x changed that, because there's no access to pkg1 that holds secmon and warmboot.
So I've confirmed I have the appropriate files that the commands point to in their respective directory and made changes to the .ini as perscribed above. When i select launch>stock under misc I get both splashes (sept and atmo) and horizon boots up as per normal. In System settings fw version is 7 0.1(ams 0.8.4)...I am also able to run hbl via title replacment and launch a .nro so it seems that Im not in OFW at all...all of the above also occured after making no changes to the .ini (boots into cfw instead of ofw) which is how I was pointed in this direction. Has anyone successfully booted stock fw with the instructions laid out a bit earlier in tthe thread?...
Edit I think I see it.....well I tried adding two parentheses the end...same thing
Edit I think I see it.....well I tried adding two parentheses the end...same thing
Attachments
Last edited by atypicalchaos,
If you see that, then your /sept/payload.bin is fusee instead of hekate.
New version will mitigate that without intruding (if sept/payload is foreign, then rename it and copy hekate there. When sept runs, it will run hekate and it will rename the payload back for the next time).
Actually I thought it was because I left those parentheses out in the .ini...all the other sections have them and I took them out
..but when I tried it still didn't work- Omg thank you Ill try that in a bit...
Edit...so I tried this and after the sept splash it goes to hekate and goes through a few lines as it loads things and then goes to a bright red screen (and no further)...that definitely made a difference but now I think something else is missing...Ill have to rebuild all of the folders ......when I wake up that is....thank you @CTCaer...Im pretty sure you fixed one thing but I must've borked another
Last edited by atypicalchaos,
Hit enter to change line after the atmosphere=1. The ini parser, looks for \n to save an entry.
EDIT:
https://github.com/CTCaer/hekate/blob/master/bootloader/config/ini.c#L38
lbuf != '\n'
Last edited by CTCaer,
I recently updated to Hekate 4.8/AMS 0.8.4 and "Launch - Atmosphere" no longer works. I see the payload doing its work and then the Nintendo logo, but after that it's just a black screen. I'm on Horizon v5.1. Is there something I need to change in hekate.ipl? Or maybe I'm missing some files?
I just tried to print fuse info and tsec info. Fuse info worked without any problem but tsec not so much. The only thing happening when I go there is I get the text "found pkg1 (201811xxxxx)" and the console locks up.
Got 6.2 updated from 3.1 via choidujour
Anyone knows what's going on?
Skickat från min ONEPLUS A6003 via Tapatalk
Got 6.2 updated from 3.1 via choidujour
Anyone knows what's going on?
Skickat från min ONEPLUS A6003 via Tapatalk
I have the same problem, IIRC when I was on 5.1 I was able to get them by using this method.
The problem is not 4.6 or 4.8.
The problem is that you chainload hekate from another bootloader that has a broken hwinit that enables CCPLEX (normal CPU).
TSEC keys in 6.2.0 need a specific exploit that uses that said CPU.
So just ask them to fix this or just inject hekate directly.
Anyway, you just getting this now, because you just updated to 6.2.0.
Cheers for the answer!
I do have another question though.
I was able to load hekate 4.8 through SX OS menu, but when I tried it using tegrarcmgui the software would freeze and the payload wouldn't get through.
I tried this 3 times with same results.
As soon as I chose the 4.6 payload it would work without a hitch.
Got any idea why this would happen?
Skickat från min ONEPLUS A6003 via Tapatalk
I do have another question though.
I was able to load hekate 4.8 through SX OS menu, but when I tried it using tegrarcmgui the software would freeze and the payload wouldn't get through.
I tried this 3 times with same results.
As soon as I chose the 4.6 payload it would work without a hitch.
Got any idea why this would happen?
Skickat från min ONEPLUS A6003 via Tapatalk
CTCaer- thank you for the suggestion but I get the same result (bright red screen). As per a comment made earlier I am using the SX bootloader to launch hekate..which workes fine for launching atmo from hekate or simply just launching atmo by launching fusee_primary.bin....maybe this is causing the issue? I'm on 7.0.1 using latest stable for SX which lately has only been a launchpad into other cfw. Ive attached a picture of my .ini as well. Thanks for your help. I have tomrrow off so if the issue is not being able to chainload Hekate from SX bootloader I can try it from my pc instead...though in my case this defeats the purpose as launching ofw and cfw from just my dongle for convenience was my aim (using the dongle and jig on the bus is perilous 
)
Edit...
Woah...just went to boot atmosphere using fusee_primary which worked fine before and get red screen...
Whew....made it work again by restoring payload.bin to root/sept.....fusee_primary.bin created an endless loop when I used it...I used the payload.bin from the sept folder from atmo 0.8.4 release instead(which is 4X bigger than fusee) and I booted into atmo without issue again....
)Edit...
Woah...just went to boot atmosphere using fusee_primary which worked fine before and get red screen...
Whew....made it work again by restoring payload.bin to root/sept.....fusee_primary.bin created an endless loop when I used it...I used the payload.bin from the sept folder from atmo 0.8.4 release instead(which is 4X bigger than fusee) and I booted into atmo without issue again....
Attachments
Last edited by atypicalchaos,
hi all. If i set kip1=modules/required/* line and put in /modules/required/sys-ftpd.kip does load sys-ftpd module at every boot?
i didn't meant to put literally a \n.CTCaer- thank you for the suggestion but I get the same result (bright red screen). As per a comment made earlier I am using the SX bootloader to launch hekate..which workes fine for launching atmo from hekate or simply just launching atmo by launching fusee_primary.bin....maybe this is causing the issue? I'm on 7.0.1 using latest stable for SX which lately has only been a launchpad into other cfw. Ive attached a picture of my .ini as well. Thanks for your help. I have tomrrow off so if the issue is not being able to chainload Hekate from SX bootloader I can try it from my pc instead...though in my case this defeats the purpose as launching ofw and cfw from just my dongle for convenience was my aim (using the dongle and jig on the bus is perilous
Edit...
Woah...just went to boot atmosphere using fusee_primary which worked fine before and get red screen...
Whew....made it work again by restoring payload.bin to root/sept.....fusee_primary.bin created an endless loop when I used it...I used the payload.bin from the sept folder from atmo 0.8.4 release instead(which is 4X bigger than fusee) and I booted into atmo without issue again....
But to press enter there and save.
Also currently the sept/payload.bin must be hekate to be able to boot via hekate into HOS. Next version will be smarter and allow you to have sth else there and still be able to boot via hekate.
Yeah, it will also load sys-ftpd.kip at every boot.
If you don't want that, you can have 2 profiles, both with /* lines and on the 2nd profile to also have an additional line with kip1=modules/required/extra/sys-ftpd.kip or sth.
Similar threads
-
-
-
-
-
-
-
-
-
-
-
-
@
Julie_Pilgrim:
@Psionic Roshambo i have 16 gb in my pc and i run into issues with ram more than i'd like to admit -
-
-
-
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
