​

The general stability is here once again with a new custom firmware update released just a few minutes ago for Atmosphere NX.
SciresM has debugged the original release of 1.6.0 further and released an update to Atmosphere NX for the Nintendo Switch with a new pre-release version 1.6.1, in which a critical problem causing certain consoles that had a rebuilt SYSTEM partition to brick once updated to 17.0.0 has been fixed.

As with any other pre-release for the custom firmware, this is an early version of the custom firmware so users can help debug and beta test the current version, so that any bugs encountered can be addressed and fixed for the proper and final stable version of Atmosphere 1.6.1. The changes done to the new Atmosphere v1.6.1 are as follows:

1.6.1 is Atmosphère's seventy-sixth official release.
Please be sure to update fusee when upgrading to 1.6.1. fusee-primary no longer exists, and will not work any more.
Please note: Atmosphère 1.6.1 is currently in pre-release, and issues may be found that need to be fixed before full release.

• If any bugs are reported while Atmosphère is in pre-release, they will be fixed and the build will be updated.
• 1.6.1 will transition to release after a short amount of time has passed without pressing bug reports.

With thanks to the @switchbrew team, Atmosphère 1.6.1 is bundled with hbl 2.4.3, and hbmenu 3.5.1.
The following was changed since the last release:

• An improved solution to the problem that would cause consoles which had previously re-built their SYSTEM partition to brick on update-to-17.0.0 was added.
  • In particular, booting atmosphère will now automatically detect the problem and unbrick any consoles which have fallen into this state.
• Some improvements were made to haze, including:
  • Performance was greatly improved:
    • Support was added for GetObjectPropList, which decreases the amount of requests made by ~8x.
    • Haze now performs rendering on the GPU, freeing up the CPU to respond to requests in a more timely manner.
  • An issue was fixed with how haze configures bMaxPacketSize0 which improves support for USB3.
• General system stability improvements to enhance the user's experience.

And the following was changed in 1.6.0:

• Basic support was added for 17.0.0.
  • The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
    • There shouldn't be anything user visible resulting from this, but it will be addressed in a soon-to-come atmosphère update.
  • exosphère was updated to reflect the latest official secure monitor behavior.
  • mesosphère was updated to reflect the latest official kernel behavior.
  • ncm was updated to reflect the latest official behavior.
  • erpt was partially updated to support the latest official behavior.
• Atmosphere's gdbstub now supports waiting to attach to a specific program id on launch (as opposed to any application).
  • The monitor command for this is monitor wait <hex program id>, where program id can optionally have an 0x prefix.
• Support was added to haze for editing files in-place and performing 64-bit transfers (files larger than 4 GB).
• bpc.mitm was enabled on Mariko units, and now triggers pmic-based shutdowns/reboots (thanks @CTCaer).
  • This should cause the console to no longer wake ~15 seconds after shutdown on Mariko.
• A number of minor issues were fixed and improvements were made, including:
  • A workaround was added for a change in 17.0.0 that would cause consoles which had previously re-built their SYSTEM partition to brick on update-to-17.0.0.
• General system stability improvements to enhance the user's experience.

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

Atmosphere NX's Release at GitHub
Atmopshere's Discussion Thread

 

[Ryab]

How much hassle for a word filter update

A lot more changed this update then it seems. A bunch of under the hood changes. Most notably the kernel's memory usage has dropped massively.

 

[Morricorne]

This has me thinking that the entire homebrew community depends on 1 guy

Nothing new. I see this on PSP and PS VITA previosly. Its always depends on one guy

 

[codezer0]

Nothing new. I see this on PSP and PS VITA previosly. Its always depends on one guy

If thats the case, said guy on the scene deserves to never have to pay for his own booze again.

 

[raging_chaos]

How much hassle for a word filter update

Try actually reading the firmware notes for what really changed in this update, updating a word filter isn't what has caused these issues.

 

[The-Ran-Dom-One]

This update unbricked my Switch. So thank you one guy. Now can anywhere share the Sigpatches ?

 

[KirovAir]

SciresM carrying the switch scene as usual. Interesting writeup and nice solution.

 

[Lather]

still doesnt know how high of version can nintendo make XDD

 

[TomSwitch]

​

The general stability is here once again with a new custom firmware update released just a few minutes ago for Atmosphere NX.
SciresM has debugged the original release of 1.6.0 further and released an update to Atmosphere NX for the Nintendo Switch with a new pre-release version 1.6.1, in which a critical problem causing certain consoles that had a rebuilt SYSTEM partition to brick once updated to 17.0.0 has been fixed.

As with any other pre-release for the custom firmware, this is an early version of the custom firmware so users can help debug and beta test the current version, so that any bugs encountered can be addressed and fixed for the proper and final stable version of Atmosphere 1.6.1. The changes done to the new Atmosphere v1.6.1 are as follows:



Atmosphere NX's Release at GitHub
Atmopshere's Discussion Thread

Your statement is not correct. If you click on the link in the release note there is an explanation of the problem which has nothing to do with Atmosphere. Atmosphere is trying to help. Some user's Switch may brick when they update to HOS17 and if they had 1.6 when they first boot they would be saved and now with 1.6.1 they can recover from brick if they brick their Switch cause they didn't have 1.6 when it first boot.

 

[proconsule54]

We are lucky to have SciresM that deeply know the internal process of HOS!
And also thanks to all who help him for test and so on!

 

[lordelan]

Noob question: Is there a way of updating this straight from the Switch?

There is (All in One Updater) but from someone who did that very often in the past: Don't do it. It sucks and can cause issues. If you don't wanna pull out the SD card, transfer files over from within hekate's USB mode but definitely put the files (or at least one of those packages like DeepSea) manually on your SD.

 

[Lather]

There is (All in One Updater) but from someone who did that very often in the past: Don't do it. It sucks and can cause issues. If you don't wanna pull out the SD card, transfer files over from within hekate's USB mode but definitely put the files (or at least one of those packages like DeepSea) manually on your SD.

me corrected: very horrible
just put the files into SDcrad by yourself

 

[Slluxx]

me corrected: very horrible
just put the files into SDcrad by yourself

disagreed

 

[linuxares]

ITotalJustice created a cool tool called sys-patch that basically does the patching function at run time, no pre-generation of patches required.

It doesn't work for ancient f/w like 9.0.0 but any modern f/w since ~13.0.0 is supported.

github/ITotalJustice/sys-patch

Yet he still recommend sigpatches over his tool and it doesn't work on 17 at this moment

 

[[Truth]]

Yet he still recommend sigpatches over his tool and it doesn't work on 17 at this moment

He doesn't actually.

 

[linuxares]

He doesn't actually.

https://github.com/ITotalJustice/sy...t-i-should-stop-downloading--using-sigpatches

 

[[Truth]]

https://github.com/ITotalJustice/sy...t-i-should-stop-downloading--using-sigpatches

Where is he recommending sigpatches over his tool?
He said you should use both in case his patches break.
But the point is moot now, because with FW 17 both broke.

 

[linuxares]

I won't answer for him, but it really seem he do recommend signature patches first.
Anyway, as you say FS is broken at the moment but ES patching still works.

 

[[Truth]]

As long as you always check compatibility before updating ams/hos there really is no reason to use both simultaneously or one over the other.

 

[LeyendaV]

Noob question: Is there a way of updating this straight from the Switch?

There are, but you should never do that.

 

[Ampersound]

In particular, booting atmosphère will now automatically detect the problem and unbrick any consoles which have fallen into this state.

Now THAT is cool! Hats off to the devs