- Joined
- May 28, 2018
- Messages
- 645
- Trophies
- 0
- Location
- Barstow, on the edge of the desert
- XP
- 1,873
- Country
How did you get it to work? It seems impossible to me.The .nsp uploaded by @8BitWonder works fine with ams 0.19.3, just rename to exefs.nsp
You could ask over reswitched discordHow did you get it to work? It seems impossible to me.
I started fresh by following this the guide from nh-server on github from start to finish, then I did exactly what it said in your first post, but using @8BitWonder uploaded files instead and renamed them as they should be, but I'm still stuck with the same error:
"A fatal error ocurred when running Atmosphere.
Program ID: 0100000000000004
Error Desc: std::abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_000000000bc68b99.bin"
Should I post the .bin file here or is it not to any use for those other than Atmosphere developer?
Can you send us your "00FF747765616BFF" working folder? Upload the compacted file, just to see if it works? Followed tutorial three or four times, but doesn't works for me. Like user @hetop, I'm using Atmos 0.19.3 / Hekate 5.5.6 / FW 12.0.2.The .nsp uploaded by @8BitWonder works fine with ams 0.19.3, just rename to exefs.nsp
Can you send us your "00FF747765616BFF" working folder? Upload the compacted file, just to see if it works? Followed tutorial three or four times, but doesn't works for me. Like user @hetop, I'm using Atmos 0.19.3 / Hekate 5.5.6 / FW 12.0.2.
I'll appreciate you help.
I think I've somewhat solved it, although I'm completely new to the Switch-scene, so I'm not sure if what I'm doing now has any disadvantages or advantages over what I was doing before.
What I used to do, and what I suspect you did as well, was boot into RCM-mode and in TegraRCMGUI I selected fusee-primary.bin to try and boot into Atmosphere. That did not work and I got the abovementioned error.
What did work, however, was selecting hekate_ctaer_5.5.6.bin instead, click on Launch and then click on Atmosphere F550 EmuMMC. That way it booted into Atmosphere without issues and I could use sys-tweak however I wanted.
The reason I used fusee-primary.bin and not hekate_ctaer_5.5.6.bin is because with Hekate-payload I have to manually click two more times just to launch the OS, whilst with Fusee-payload it boots straight into Atmosphere without me having to click on anything else. But if you boot into Hekate and click on Options, then on Auto Boot OFF and click on Atmosphere F550 EmuMMC it should now say Auto Boot ON and the next time you send the Hekate.payload it should boot you straight into Atmosphere.
If you want to get back to Hekate at any time, instead of it autobooting into Atmosphere, after you've sent the Hekate-payload, and when it says Hekate IPL Custom NX Bootloader on the screen, click and hold VOL- and it should launch you back into Hekate.
Hope it was informative and understandable and might help anyone else who encounters this issue.
Oh, that's cool! Sadly, I don't use that "Atmosphere FSS0 EmuMMC" option. My hekate ini file only has options Atmosphere 0.19.3, Atmosphere 0.19.3 (Sysnand) and Oficial Firmware. Never used Emunand, too. Even tried to setup a fresh new Hekate from scratch, but nothing seems to work. Even so, thanks for the tips!
EDIT: It worked! I'm thinking has something to do with Incognito. Tried to boot the "Force Sysnand" Hekate option (without Incognito), and sys-tweak works. Thanks!
so to make it clear if one is on atmospher 0.19.3 and fw 12,0,2, one cannot boot directly into atmosphere via fusee.primary.bin? You need to boot via hekate? Is this because of sys-tweak?
The .nsp uploaded by @8BitWonder works fine with ams 0.19.3, just rename to exefs.nsp
It doesn't have to be named FSS0, that's just what mine is called. The one called Atmosphere, without the (Sysnand) is probably your Emunand. Glad you got it working either way.
What change(s) did you make?Compiled this so people won't have to keep using fss0 through Hekate. If you have issues, update AMS to the latest version.
This should fix the fatal error from 0100000000000004.
I updated my libs, libnx-master and atmosphere-libs. I'm learning how to compile on the fly coming from no experience. All I know for sure is that it runs on fusee-primary for me now and it didn't before. Haha.What change(s) did you make?
I updated libs for AMS 0.19.3 on my fork but was able to boot through both fusee/fss0 with the build from earlier and my forked build, so I figured no update would be necessary.
I'm having trouble building yours I'm getting this error. "fatal error: jpeglib.h: No such file or directory"What change(s) did you make?
I updated libs for AMS 0.19.3 on my fork but was able to boot through both fusee/fss0 with the build from earlier and my forked build, so I figured no update would be necessary.
Double-check that you have switch-libjpeg-turbo installed in DKP.I'm having trouble building yours I'm getting this error. "fatal error: jpeglib.h: No such file or directory"
Thanks, man! I'll try and come back to tell if worked for me.Compiled this so people won't have to keep using fss0 through Hekate. If you have issues, update AMS to the latest version.
This should fix the fatal error from 0100000000000004.