Yes, I'd be wary of things possibly breaking in the future though. Something to keep in mind.
"Failed to run tsec_keygen firmware" on SXOS Pro USB dongle when using fusee payload to launch AMS 1.2.3
- Thread starter efgamer
- Start date
- Views 11,243
- Replies 34
You need to boot using package3 instead of fusee.. just delete the payload line from your hekate...
This have no effect on the issue
It's something in atmosphere from back with 1.0 and i think that only SciresM can fix it
Just read the link...I've had that issue back when I've updated to 13.0.0.. I'm on atmospheres 1.2.6 and it works..My sysnand is on 10.2 I boot using SX OS - hekate - atmosphere emunand...
I’m getting confused. I see dongle, then I see chip. Why do people in different situations insist on hijacking a thread?
If you’re chipped, modify it with Spacecraft-nx firmware.
If you’re using a dongle, try the gear boot.dat (can’t really hurt at this point) or try creating your own as suggested here. At the very least, use the jig and inject hekate with your PC or Android phone. Forget about the dongle. I haven’t touched mine since the RCM loader came out.
If you’re chipped, modify it with Spacecraft-nx firmware.
If you’re using a dongle, try the gear boot.dat (can’t really hurt at this point) or try creating your own as suggested here. At the very least, use the jig and inject hekate with your PC or Android phone. Forget about the dongle. I haven’t touched mine since the RCM loader came out.
Originally, it was just this:
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
After some reading, I added the following:
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
fss0=atmosphere/package3
kip1=atmosphere/kip_patches/*
id=atmo
Seeing as how that didn't work, I removed a few lines after reading those threads:
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
[Atmosphere CFW]
fss0=atmosphere/package3
kip1=atmosphere/kip_patches/*
id=atmo
FWIW, there is indeed a 'fusee.bin' in the payloads folder (latest version).
Maybe this isn't anything I need to worry about? Everything works at the moment.
This is the one that should work and not get the tsec_keygen error. This is how mine is set up and I don’t get the error anymore. The fusee.bin route is the official way to boot up and SciresM has been very clear that SX is not supported. As I understand it fss0 is the old fusee-secondary style of booting. In my experience it does not trip up on the tsec error.
from Hekate:
That’s fine, unless you make a hekate_ipl.ini stanza that incorporates it, it will sit there and do nothing.
it’s not anything to worry about :-)
So everything is good? No more tsec keygen errors?
Last edited by binkinator,
Edit: just looked at your previous messages in this thread. You are on a chipped Erista. This should work for you: https://rentry.org/mys8q
Yah…I don’t know then. Thats what worked for me.
Maybe try this guy: https://sx-boot-dat-creator.herokuapp.com/
You can upload a payload.bin (such as hekat.x.x.x.bin or fusee.bin) and it will give you a boot.dat. Make sure it doesn’t have any other suffix like boot.dat.html or anything crazy. “Backup“ your original boot.dat by moving it to boot.bak and replace it with your new boot.dat you just downloaded and try again.
Last edited by binkinator,
I guess I mis-typed that. No matter what I do, I keep getting that tsec error. If getting the error doesn't mean anything bad will happen, I guess I'll just let it be and live with it.
The reason I keep using the SX OS dongle is because it's convenient vs. having to hook the Switch up to a PC whenever I need to do a full shutdown/reboot.
Got my hopes up, man. To be honest the RCM Loaders aren't horribly expensive if you want to get out of the SX world altogether. Prolbably not a bad idea to be honest.
Dude it works it freaking works finally
thanks for the guide skipped the migrate emummc part and the step that prevent from banning now that im not on the net.
Used this guide https://rentry.org/mys8q
And the boot time is like 80% faster LOL
Last edited by spoggi,
Similar threads
