Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[impeeza]

https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10291762

 

[rave420]

https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10291762

Brilliant, that explains it.

I made the mistake of popping my head into the first ~150 pages of this thread, to see how the project started and how it grew, and whew oh boy did the existence of Atmosphere bring out the trolls and salt miners. I am surprised to see how much negativity there was going around.

Anyways, if the team behind Atmosphere had a way for me to buy everyone a six-pack after the fact, I probably would . Thanks for this outstanding CFW, thanks for persisting through the misery that was the first year or so, you people are awesome.

 

[SkullHex2]

Also can you go to the ultrahand ovl thread and report your problem, may be a bug on int.

Should I do so even if using the 'official' release of nx-ovlloader fixes it?

 

[impeeza]

Should I do so even if using the 'official' release of nx-ovlloader fixes it?

May be not, if the official resolve it , then there all ok.

Post automatically merged: Dec 5, 2023

Well Firmware 17.0.1 is out, but no "my dog accidentally updated my console" because the patches didn't change.

 

[DominoBright]

Any changes that can break homebrew and such?

 

[impeeza]

Any changes that can break homebrew and such?

no so far

 

[Hayato213]

Any changes that can break homebrew and such?

CFW work fine for 17.0.0, if you are going from 17.0.0 to 17.0.1 you should have no issue, as SciresM said Atmosphere 1.6.2 should work fine

 

[SkullHex2]

May be not, if the official resolve it , then there all ok.

So, in the end it wasn't any of your custom-compiled stuff, but Fizeau. I've already reported it in the thread.

 

[impeeza]

So, in the end it wasn't any of your custom-compiled stuff, but Fizeau. I've already reported it in the thread.

Cool, I don't use Fizeau to change screen colors, but will give a try. Thanks for let us to know.

 

[SciresM]

Brilliant, that explains it.

I made the mistake of popping my head into the first ~150 pages of this thread, to see how the project started and how it grew, and whew oh boy did the existence of Atmosphere bring out the trolls and salt miners. I am surprised to see how much negativity there was going around.

Anyways, if the team behind Atmosphere had a way for me to buy everyone a six-pack after the fact, I probably would . Thanks for this outstanding CFW, thanks for persisting through the misery that was the first year or so, you people are awesome.

There isn't really a team, it's pretty much just me. No way to buy me a six-pack (I don't accept donations of any kind), but I appreciate the sentiment.

The first year was fine, to be honest. I don't really give a shit what anyone else has to say, and didn't back then, either.

 

[impeeza]

There isn't really a team, it's pretty much just me. No way to buy me a six-pack (I don't accept donations of any kind), but I appreciate the sentiment.

The first year was fine, to be honest. I don't really give a shit what anyone else has to say, and didn't back then, either.

Hope you receive the best wishes of the everyone on the community, the scene is big and most of us appreciate a lot your work.

Regards buddy.

 

[Noizetank]

I don't know if this is the best place to ask but I get the below error when trying to use emummc. I'm using the latest atmosphere and sig patches etc. Using an unpatched switch. Can anyone give me some pointers please.

 

[Blythe93]

I don't know if this is the best place to ask but I get the below error when trying to use emummc. I'm using the latest atmosphere and sig patches etc. Using an unpatched switch. Can anyone give me some pointers please.

Did you update your fusee.bin payload as well? Also make sure that you're using latest Hekate as well.

 

[Noizetank]

Did you update your fusee.bin payload as well? Also make sure that you're using latest Hekate as well.

Hi
Thanks for the info, I know this is a really dum question but where do I put the fusee.bin? On the SD card Or do I use that as the payload on tegra?

 

[Blythe93]

Hi
Thanks for the info, I know this is a really dum question but where do I put the fusee.bin? On the SD card Or do I use that as the payload on tegra?

As payload on Tegra for sure.

 

[impeeza]

Did you update your fusee.bin payload as well? Also make sure that you're using latest Hekate as well.

Also you need to upgrade the payload you use to inject on your console.

 

[linuxares]

Also you need to upgrade the payload you use to inject on your console.

Not with Hekate, but yes.

 

[impeeza]

Not with Hekate, but yes.

You are right since some time Hekate autoload the most recent payload if you inject an old one. but if your injection method have a very old Hekate, you need to update it.

Also after Hekate start it can load the fusee.bin file or package3 file and if they are old you get the reported error.

Post automatically merged: Dec 11, 2023

The auto reload of new Hekate was introduced on Hekate 5.5.8

 

[Noizetank]

Thank you so much, all working now.
Cheers!!

 

[impeeza]

That's why for all my V1 consoles I have RCM Loaders with Argon-NX SE payload, and Argon-NX Se is set on my SD Card to autoboot "SDMC:/argon/payload.bin" which is a copy of Hekate's update.bin so I only have to updgrade my SD Card and never the injector.

For my ModChipe'd consoles the SDMC:/Payload.bin is Argon-nx SE payload.