Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[Dave_Chad]

The latest atmosphere just hangs on the Switch logo on my friends Switch Lite. I'm trying to downgrade to 11.0.0 for him and understand i need to boot atmosphere for him. I have an unpatched Switch so i'm reasonably good with Atmosphere stuff not with the SX crap.

 

[Adran_Marit]

The latest atmosphere just hangs on the Switch logo on my friends Switch Lite. I'm trying to downgrade to 11.0.0 for him and understand i need to boot atmosphere for him. I have an unpatched Switch so i'm reasonably good with Atmosphere stuff not with the SX crap.

Did you flash spacecraft-nx or chainbooting through the sx bootloader?

 

[SciresM]

The latest atmosphere just hangs on the Switch logo on my friends Switch Lite. I'm trying to downgrade to 11.0.0 for him and understand i need to boot atmosphere for him. I have an unpatched Switch so i'm reasonably good with Atmosphere stuff not with the SX crap.

Turn off prodinfo blanking in exosphere.ini, or build atmosphere-master, which has a fix for prodinfo-blanking-on-mariko-units.

 

[Dave_Chad]

Will try when I get home I actually had suspicions about the prodinfo blanking. Thanks very much mate

 

[urherenow]

-master often does not boot because I make no attempt to keep it stable), you can do so without making public docker tooling.

FWIW, other than occasionally having to do a manual update of libnx (to complete a build), I don't recall having issues.

Also, atmosphere only officially supports building on Windows, Linux isn't broken at the moment but I can't guarantee that will always be true, since I use windows exclusively.

In what environment though? with either linux subsystem or msys2, it's pretty much the same environment. Any tool not provided by devkitpro (thus far) has included source, so they're built in the environment that's being used to build Atmosphere.

 

[SciresM]

In what environment though? with either linux subsystem or msys2, it's pretty much the same environment. Any tool not provided by devkitpro (thus far) has included source, so they're built in the environment that's being used to build Atmosphere.

I build from windows cmd, I think I actually technically use MinGW make, since it's higher in my path than dkP stuff.

 

[urherenow]

No, those patches are for hekate + secondary, im using hekate with primary.

lol, if you're using primary, then you aren't using hekate at all (except as a bootloader).

Calling primary == fusee-primary does the initial setup then boots fusee secondary using Atmosphere's config files such as BCT.ini, and requires the Atmosphere patches.

fss0=atmosphere/fusee-secondary.bin uses hekate for the initial setup and uses hekate_ipl.ini and hekate patches to load fusee secondary.

In short, there are no separate patches for hekate +primary and hekate + secondary. There are only hekate patches and Atmosphere patches. Anything else requires a custom kip or layeredfs.

 

[Dave_Chad]

Turn off prodinfo blanking in exosphere.ini, or build atmosphere-master, which has a fix for prodinfo-blanking-on-mariko-units.

Worked absolutely perfectly thanks for the help. Now downgraded to 11.0.0 and back on his dirty pirate os :haha

I'll stick to Atmosphere myself.

 

[SciresM]

Happy June 15th!

 

[mattyxarope]

Happy June 15th!

SciresM's calendar:

 

[Asia81]

Hello, what do I need to do to update Atmosphere?
Just replace the fusee-primary.bin payload?

 

[BaamAlex]

Hello, what do I need to do to update Atmosphere?
Just replace the fusee-primary.bin payload?

And the zip package from github. The fusee-primary.bin doesn't need to be updated after every new release.

 

[toxic9]

The new v17.1 doesn't have an "EXPERIMENTAL" release as the others.
Instead it has an "WITHOUT MESOSPHERE" release.

Is Mesosphere standard from now on?

 

[linuxares]

The new v17.1 doesn't have an "EXPERIMENTAL" release as the others.
Instead it has an "WITHOUT MESOSPHERE" release.

Is Mesosphere standard from now on?

Yes

 

[Dothackjhe]

The new v17.1 doesn't have an "EXPERIMENTAL" release as the others.
Instead it has an "WITHOUT MESOSPHERE" release.

Is Mesosphere standard from now on?

Only optional at this point.

--------------------- MERGED ---------------------------

Hello, what do I need to do to update Atmosphere?
Just replace the fusee-primary.bin payload?

Technically, you just need to copy over the contents of Atmosphere into the root of the micro-SD Card, in addition to overwriting the fusee-primary.bin within the bootloader/payload folder.

However, I personally find deleting the files held in the micro-SD card, which are only either going to be overwritten or added with, and copying over the new files on a clean slate to be a better way about it. Based on experience, merely overwriting old files with new ones can, at times, cause a conflict (due to some leftover files that do not get overwritten) that prevent the system from booting properly.

Just do not forget to copy over the latest sigpatches as well if you've use for it, because it, too, gets deleted if you choose to remove the "atmosphere" folder from the root of the micro-SD Card.

 

[SciresM]

Happy June 15th!

 

[hippy dave]

Happy June 15th!

The DNS substitution sounds like a fun feature!

 

[mitcha]

Happy June 15th!

i wonder what you will say , when june 15 2021 comes

 

[ZachyCatGames]

i wonder what you will say , when june 15 2021 comes

Today is June 15th 2021 though.

 

[BaamAlex]

i wonder what you will say , when june 15 2021 comes

SciresM's calendar xD
As already stated above