Homebrew RELEASE Atmosphere 0.14.0 released

[ShadowOne333]

UPDATE: Atmosphere has been updated to subversion 0.14.0. Check the Github releases for the updated version.

Another June 15th, another release!
This new Atmosphere update brings along a new feature, Daybreak, which is an updater for the firmware of the Switch without having to rely on other firmware updaters like ChoidujourNX.
This update also lays the groundwork (but not support) for both Mariko support and Mesosphere, the later being a complete rewrite and implementation of the Switch's kernel, but there's still an on-going development for both of them.

Happy June 15th! Atmosphere 0.14.0 has released: https://t.co/XAgjhx9Exg

This includes the new system update api/installation homebrew daybreak, as well as other fixes/improvements.

I hope you all enjoy! :)

— Michael (@SciresM) August 1, 2020

As always, head to the GitHub page to get the latest version!
Here's the updated changelog:

The following was changed since the last release:

• An issue was fixed in 0.14.0 that would cause a black screen on boot when the INI1's size was not aligned to 8 bytes.
• General system stability improvements to enhance the user's experience.

The changelog for the previous release, 0.14.0 is as follows:

• An API (ams:su) was added to allow homebrew to safely install system upgrades or downgrades.
  • This is a re-implementation of the logic that ns uses to install gamecard system updates.
  • Nintendo (and now atmosphère) uses an installation process that can recover no matter where a failure occurs, which should significantly improve the safety of custom system update installation.
• Support was added to exosphère for running on Mariko hardware.
  • Please note: Atmosphère still does not support Mariko, and should not be run on Mariko yet.
    • Certain stratosphere components do not handle mariko-specific logic fully correctly yet, and may initialize or interact with hardware incorrectly.
    • This will be fixed and support will be added over the remainder of the Summer.
• A homebrew application (daybreak) was added that uses the system updater API (with thanks to @Adubbz for both design and implementation).
  • daybreak is included with atmosphère, and functions as a safer/more accurate equivalent to e.g. ChoiDujourNX.
  • Upgrades/downgrades can be installed from a folder containing the update NCAs on the SD card.
  • Because the update logic functions identically to Nintendo's, daybreak will be safe to use on Mariko when the rest of atmosphère has support.
  • Please note: Daybreak requires that meta (.cnmt) NCAs have the correct extension .cnmt.nca.
    • This is because gamecard system update logic uses extension to determine whether to mount the content.
    • Several scripts have been made by community members to automatically rename folders with incorrect extensions.
• A bug was fixed that would cause file-based emummc to throw an error (showing a hexdump) on boot.
  • Major thanks to @hexkyz for tracking down and resolving this.
• A number of minor issues were resolved, including:
  • fusee now prints information to the screen when an error occurs, instead of getting stuck trying to initialize the display.
  • A race condition in Horizon was worked around that could prevent boot under certain circumstances.
  • A bug was fixed that would cause atmosphère modules to open ten copies of certain filesystems instead of one.
    • This could cause object exhaustion under certain circumstances.
• For those interested in atmosphère's future development plans, the project's roadmap was updated.
• General system stability improvements to enhance the user's experience.

For information on the featureset supported by 0.14, please see the official release notes.

Atmosphere's GitHub Repository Release Page

 

[SciresM]

Atmosphere 0.14.0 does not actually include Mesosphere -- mesosphere does not yet support firmwares lower than 10.0.0 (I need to do backwards compatibility), and it will need a lot of testing.

Once mesosphere is actually done, two atmosphere zips will be distributed in releases. A "stable" zip without mesosphere, and a "cool kids" zip with mesosphere. This will continue for some time until meso is stable, and then Atmosphere's version will be changed to 1.0.0.

 

[ShadowOne333]

Atmosphere 0.14.0 does not actually include Mesosphere -- mesosphere does not yet support firmwares lower than 10.0.0 (I need to do backwards compatibility), and it will need a lot of testing.

Once mesosphere is actually done, two atmosphere zips will be distributed in releases. A "stable" zip without mesosphere, and a "cool kids" zip with mesosphere. This will continue for some time until meso is stable, and then Atmosphere's version will be changed to 1.0.0.

Thanks for the headsup!
I did notice Mesosphere (kernel implementation) wasn't added in this release upon further reading.
I simply jumped the shark and made the assumption, but will make the correction right away.

Will be looking forward to its progress!

 

[iriez]

Im wondering if this fixes a bug I recently discovered on 0.13.0

I had just upgraded a system and noticed that when I long press power for a shutdown when attempting to do a cold boot (stock, no rcm) the system would just hang. Something about the shutdown process broke the next normal boot sequence. However if I used RCM to boot a payload it would not happen.

 

[mattyxarope]

Does SX have to take part in allowing other firmwares to run on SX Core/Lite? Or will it be possible directly after Atmosphere supports it?

 

[Nemix77]

I think it might be for me to pickup a Mariko Switch.

 

[enzobelmont]

now my zelda physical copy get stuck on initial switch logo rotating but not responding, home button not working, nothing, I have to poweroff with power button. Updated to CFW 10.1 ATMOS 0.14.0 and latest sigpatches.

any idea?

 

[jeremy27041980]

A little more patience for the support of the switch mariko....
I can't wait any longer.

 

[DaFixer]

Great!!

 

[HaloEffect17]

Can we have a Daybreak tutorial soon? Also, if people are already on fw 10.1.0, can they update to 0.14.0 and not have to update their sigpatches?

 

[ChaosEternal]

Does SX have to take part in allowing other firmwares to run on SX Core/Lite? Or will it be possible directly after Atmosphere supports it?

If SX doesn't actively block the launching of other firmwares, then it should be supported immediately. However, iirc their test kits did include code that would block any non-SX CFW from running, so we'll have to see.

 

[Rahkeesh]

From what I understand the final release version of SX lets you boot any payload. So you should be able to for example run atmosphere on a patched V1 right now with SX core. However payloads/atmosphere have yet to be fully updated to support Mariko chips, i.e V2/Lite.

 

[Lacius]

Can we have a Daybreak tutorial soon? Also, if people are already on fw 10.1.0, can they update to 0.14.0 and not have to update their sigpatches?

No.

Horizon 10.0.0 moved the ES signature functions from ExeFS to a new "loader" module.
Following that change, Atmosphère implemented a "loader" sysmodule to replicate the functionality. Since ES and ACID check functions for CFW are now in that Atmosphère sysmodule, CFW 10 requires some way to patch that new module if you ever need ES patches to install and play unsigned apps.

https://gbatemp.net/threads/guide-to-choose-which-atmosphere-patches-to-use-on-switch-fw-10.563886/ (thread includes some outdated information about NeutOS, where to find current patches, etc.)

In other words, new signature patches are required anytime Nintendo updates their loader module and/or other things, and new patches are required anytime Atmosphere updates its loader sysmodule (if using 10.0.0 or higher). If you're on 9.x or lower, then you don't need new signature patches when updating Atmosphere.

 

[ZachyCatGames]

Horizon 10.0.0 moved the ES signature functions from ExeFS to a new "loader" module.
Following that change, Atmosphère implemented a "loader" sysmodule to replicate the functionality. Since ES and ACID check functions for CFW are now in that Atmosphère sysmodule, CFW 10 requires some way to patch that new module if you ever need ES patches to install and play unsigned apps.]

That description is very inaccurate. kek

 

[Lacius]

That description is very inaccurate. kek

It would be infinitely more helpful if you explained how it was inaccurate.

 

[ZachyCatGames]

It would be infinitely more helpful if you explained how it was inaccurate.

Nothing was moved from es to Loader, and es didn't ever do acid sigchecks. Prior to 10.0.0, FS did acid checks

 

[Lacius]

Nothing was moved from es to Loader, and es didn't ever do acid sigchecks. Prior to 10.0.0, FS did acid checks

from ExeFS to a new "loader" module.

 

[ZachyCatGames]

from ExeFS to a new "loader" module.

Oh yeah, that also makes absolutely no sense. exefs is a partition in NCAs, not a sysmodule

 

[Lacius]

Oh yeah, that also makes absolutely no sense. exefs is a partition in NCAs, not a sysmodule

ACID is/was a small signature protected header inside of exefs partitions.

 

[ZachyCatGames]

ACID is/was a small signature protected header inside of exefs partitions.

It's a small signed area in an npdm, but yeah
"Horizon 10.0.0 moved the ES signature functions from ExeFS to a new "loader" module."
is inaccurate though, because as I've already said, es never checked acid (also Loader is faaaar from being "new")