Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

[NickyRay]

Atmos 14
System 15.0
So far so good. I have everything working and autoboot with this in hekate ipl
-nope- patches

[Atmosphere EmuMMC]
emummcforce=1
fss0=atmosphere/package3
kip1patch=nosigchk
fss0experimental=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp

This solution worked for me.. thanks a lot.. you are a life saver. atmosphere discord is full of jerks. i mentioned the issue there but no solution was provided. then i mentioned your solution there and i got banned.

 

[urherenow]

yep I was unable to compile Atmosphère too, SciresM says you need new LibNX version https://github.com/Atmosphere-NX/Atmosphere/issues/1954

git pull origin pull/596/head

(in your cloned libnx directory)

this will grab the pull request and merge it on your end, build and install it, then Atmosphere will build without issues.

EDIT: and I don't use the libnx fork (because I didn't notice he made other branches and the default one that shows for me is outdated). Clone the switchbrew/libnx and use the command above to grab the needed updates.

 

[mrdude]

git pull origin pull/596/head

(in your cloned libnx directory)

this will grab the pull request and merge it on your end, build and install it, then Atmosphere will build without issues.

I've just built it after updating libnx from the link impeeza mentioned.

 

[urherenow]

I've just built it after updating libnx from the link impeeza mentioned.

if you build your own hekate as well, remember to run the script in Atmosphere's emummc folder to build emummc.kipm for it.

 

[mrdude]

if you build your own hekate as well, remember to run the script in Atmosphere's emummc folder to build emummc.kipm for it.

I just use hekate via it's github release page. Also I'm building in windows, not Linux so that shell script it not needed to be run on windows. But If I was using linux I will remember that so thanks for the reminder. In windows you can use python 3.10 and make a batch file with this in it: (put correct path to hactool or put hactool in the emummc directory)

hactool.exe -t kip emummc.kip --uncompressed emummc_unpacked.kip
python tools/kip1converter.py emummc_unpacked.kip emummc.data
cat emummc.caps emummc.data > emummc.kipm

EDIT: also in the release zips on Atmosphere github, how is it that /atmosphere/emummc.kip is not included in the release zip file?

 

[whitezombie]

FW 14.1.2 -
boots from package3 - good
boots from fusee.bin - good

FW 15.0.0
boots from package3 - good, but sometimes fails to boot and sometimes takes a long time to boot and gets stuck on switch logo.
boots from fusee.bin - fail, shows Atmosphere boot screen, fails to get to switch logo - requires hard reset.

Almost identical behavior for me on EmuNand with Atmosphère 1.4.0 (pre-release), FW 15.0.0, using payload=bootloader/payloads/fusee.bin with hekate_ipl.ini, or chaining Hekate and choosing fusee.bin from payload, or loading fusee.bin with TegraRCMGui. Everything works fine on FW 14.1.2.

 

[CurlyFries27]

I am sorry for being a noob, but I accidentally updated my switch to 15.0.0 last night, I got the latest atmosphere and hekate and patches.ini and such, but everything is not really working. Someone told me that I need the sigpatches for 15.0.0. I honestly don't know what sigpatches are, or how to use them. I apologize if someone already asked but this is a long thread and I can't read the whole thing. Have the sigpatches for 15.0.0 been released? And if so, what exactly do I do with them?

 

[mrdude]

Almost identical behavior for me on EmuNand with Atmosphère 1.4.0 (pre-release), FW 15.0.0, using payload=bootloader/payloads/fusee.bin with hekate_ipl.ini, or chaining Hekate and choosing fusee.bin from payload, or loading fusee.bin with TegraRCMGui. Everything works fine on FW 14.1.2.

I reported it on Atmosphere github - this is the reply.

https://github.com/Atmosphere-NX/Atmosphere/issues/1963

I didn't use the correct template to report, I don't know the indepth workings of Atmosphere's boot process, and apparently fusee.bin works great for eveyone else.....so I must be stupid and I am going to sit in the corner for the rest of the night.

 

[binkinator]

I reported it on Atmosphere github - this is the reply.

https://github.com/Atmosphere-NX/Atmosphere/issues/1963

I didn't use the correct template to report, I don't know the indepth workings of Atmosphere's boot process, and apparently fusee.bin works great for eveyone else.....so I must be stupid and I am going to sit in the corner for the rest of the night.

Saw that. It’s a tough crowd. To be fair they deal with a ton of bullshit but sometimes they hit good guys trying to help with their oversized newbie bat!

 

[mrdude]

Saw that. It’s a tough crowd. To be fair they deal with a ton of bullshit but sometimes they hit good guys trying to help with their oversized newbie bat!

Yep I know, I've reported on that github page in the past and had a similar reply, so I was kind of expecting a reply like I got.

I got a brand new SD card today - installed only Atmosphere from the github release page. Used hekate to make an emunand. Then updated the emunand to 15.0.0 - then pushed the new fusee.bin payload - same result and no boot. Other firmwares work fine though.

 

[linuxares]

Why is it so hard for people NOT TO WRITE OUT piracy sites names?
Want them shutdown faster or something?

 

[ShadowOne333]

I reported it on Atmosphere github - this is the reply.

https://github.com/Atmosphere-NX/Atmosphere/issues/1963

I didn't use the correct template to report, I don't know the indepth workings of Atmosphere's boot process, and apparently fusee.bin works great for eveyone else.....so I must be stupid and I am going to sit in the corner for the rest of the night.

Kind of expected lol
I think best option here would be to try to contact Scires directly through Discord, that's the most reliable and fast way to do it.
Hopefully that can help to narrow down what the problem is with the fusee.bin on your end, I haven't tried even updating my Switch yet at all.

 

[mrdude]

Kind of expected lol
I think best option here would be to try to contact Scires directly through Discord, that's the most reliable and fast way to do it.
Hopefully that can help to narrow down what the problem is with the fusee.bin on your end, I haven't tried even updating my Switch yet at all.

If you're updating - make sure you are using emunand & that you have 14.1.2 so you can go back again if you have issues.

So far I have noticed this:
Issues booting into emunand cfw by pushing fusee.bin from any payload launcher.
Patches - not sure if there's issues with the patches or if it's something else - XCI's install fine, but have issues running. NRO fowarders that I tried give the corrupt error message (can't remember the exact phrase off the top of my head).

Good points: You can boot into emunand from hekate via hekate_ipl.ini. Installed NSP's run fine.

 

[binkinator]

I'm on discord right now...reading before I speak...Scires seems pretty convinced it's not an issue since he doesn't use hekate and only uses fusee.bin himself. I just got my switch running again so I'm going to gingerly dip my toe into this 15.0.0 swamp and see if I get the same ish.

 

[mrdude]

I'm on discord right now...reading before I speak...Scires seems pretty convinced it's not an issue since he doesn't use hekate and only uses fusee.bin himself. I just got my switch running again so I'm going to gingerly dip my toe into this 15.0.0 swamp and see if I get the same ish.

I tried without hekate installed and on a bare sd card with just emunand and atmosphere installed - I could boot into every firmware from 11.0 to 14.12 installed on the emunand by pushing fusee.bin with TegraRCMGui - but trying to boot into FW15.0.0 was always a failure.

 

[whitezombie]

Well I got shut down too on github.

https://github.com/Atmosphere-NX/Atmosphere/issues/1964

The only thing we can do is to get more people to submit this issue.

 

[hippy dave]

He keeps offering to help debug on discord, maybe try that. I've worked through a few actual atmosphere bugs with him on discord in the past, went well.

 

[ShadowOne333]

He keeps offering to help debug on discord, maybe try that. I've worked through a few actual atmosphere bugs with him on discord in the past, went well.

Yeah I agree. That's the best course of action.
It's better not to take the responses in GitHub personally and to try to contact him directly there, he might be able to pinpoint the exact issue that way, since he can't replicate it on his end.

 

[whitezombie]

Sweet! Looks like he fixed it! By the way is ReSwitched the Discord channel to join that is linked on the GitHub page?

 

[impeeza]

yes please, some of us do not use discord, copy the link or a image of the thread.

we need to understand a SciresM, just think about how many people is asking things and no on the best way, should be overwhelming.