Atmosphere NX CFW has been updated to 1.6.1 fixing a critical bricking problem

banner.png

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:

Atmopshere NX's 1.6.1 Release Notes said:
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.

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

Goku1992A

Well-Known Member
Member
Joined
Nov 20, 2019
Messages
1,831
Trophies
1
Age
33
XP
2,747
Country
United States
idk about you guys but I mainly use YUZU... updating has always been a cat and mouse game. My CFW switch is still on 15.0.0. I like to sit back and watch the stability before I jump the gun but respectfully.

Yuzu > CFW Switch. I hardly touch my switch unless I'm playing Pokémon 60FPS smooth I love it.
 

AkiraKurusu

Stratospheric Thunder!
Member
Joined
Dec 29, 2019
Messages
1,396
Trophies
2
Age
26
Location
Northwood, Sydney
XP
4,301
Country
Australia
idk about you guys but I mainly use YUZU... updating has always been a cat and mouse game. My CFW switch is still on 15.0.0. I like to sit back and watch the stability before I jump the gun but respectfully.

Yuzu > CFW Switch. I hardly touch my switch unless I'm playing Pokémon 60FPS smooth I love it.
I've used Ryujinx before, but...eh, I prefer playing on console myself. It just runs better with large, open-world-esc games like Xenoblade Chronicles 2 and 3, and probably others too.
 

Nameless_Mofo

Member
Newcomer
Joined
Aug 15, 2022
Messages
15
Trophies
0
Location
Somewhere
XP
417
Country
United States
the same two awesome teams will be doing the sigpatches this time?

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
 

halfashark

Well-Known Member
Newcomer
Joined
Nov 10, 2022
Messages
88
Trophies
0
XP
298
Country
Canada
This is why its important to wait a tiny little bit and just do something else in the first 2-3 days of a major update. Play a PC game, knit a scarf, draw, binge-watch/listen to some show or novel...

That way if something breaks, you're still good.

:')

(This post is brought to you by the pain I felt when I bricked my PSP in Ye Ol' Days™️)
 

fvig2001

Well-Known Member
Member
Joined
Aug 21, 2006
Messages
964
Trophies
1
XP
3,162
Country
Philippines
So the people that got bricked are those that rebuilt their nand due to corruption or loss of original backup and used donor backups?

Edit:

Looks like it's caused by 3rd party tools (Haku33 or TegraExplorer or EmmcHaccGen or ChoiDujour), which I have used on some of the Switches. Looks like for safety, I will have to update OFW with atmosphere loaded on affected consoles.
 
Last edited by fvig2001,

Slluxx

GBATemp Mayor
Developer
Joined
Jul 17, 2019
Messages
612
Trophies
1
XP
2,203
Country
Germany

NinStar

Ny'hrarr ♂
Member
Joined
Apr 3, 2017
Messages
692
Trophies
2
Age
24
Location
Rio de Janeiro
Website
ninstar.carrd.co
XP
2,488
Country
Brazil

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Sicklyboy @ Sicklyboy: jonkler gonna jonkler