Status
Not open for further replies.

Atmosphere CFW updated to 1.4.0

banner.png


The frequent dose of stability is here yet again with a new firmware update released just a couple days ago.
As with each new firmware release, SciresM has debugged and release an update to the Atmosphere NX custom firmware for the Nintendo Switch with pre-release version 1.4.0.
While the amount of features listed in the new official firmware 15.0.0 aren't nothing to write home about, there's a lot of under-the-hood changes that were done to the Switch with this recent update.

This new version itself is currently on a pre-release status, meaning an early version of the firmware so users can help debug and beta test the current pre-release, so that any bugs encountered can be addressed and fixed for the proper and final stable version of Atmosphere 1.4.0.
The changes done to the new Atmosphere v1.4.0 are as follows:

Atmosphere 1.4.0 Changelog said:

Atmosphère 1.4.0 (pre-release)​


1.4.0 is Atmosphère's sixty-seventh official release.
Please be sure to update fusee when upgrading to 1.4.0. fusee-primary no longer exists, and will not work any more.
Please note: Atmosphère 1.4.0 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.4.0 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.4.0 is bundled with hbl 2.4.1, and hbmenu 3.5.1.
The following was changed since the last release:
  • Support was added for 15.0.0.
    • mesosphère was updated to reflect the latest official kernel behavior.
    • ncm was updated to reflect the latest official kernel behavior.
  • A number of minor issues were fixed and improvements were made, including:
    • The capacity limit on registered add-on contents was fixed in NCM to reflect the increase that occurred in 12.0.0.
    • An off-by-one was fixed in mesosphere when computing the new value for an address arbiter signaled with ModifyByWaitingCountIfEqual.
    • dmnt.gen2's gdbstub now sanitizes thread names to prevent invalid characters from breaking gdb.
    • dmnt.gen2's gdbstub now reports the architecture tag correctly when attached to 32-bit processes.
    • Support for program-specific html manual content overrides was added for non-hbl takeover context.
    • A bug was fixed in how emummc constructed the alternate Nintendo directory path.
      • Previously, this was using /*/Nintendo/Nintendo instead of /*/Nintendo.
      • Code was added to automatically move the old folders to the new ones when booting into emummc.
    • A bug was fixed in boot that caused an incorrectly low input voltage limit to be set.
  • General system stability improvements to enhance the user's experience.
For information on the featureset supported by 1.4, please see the official release notes.

As usual, if you have your console hacked, avoid updating your Switch to the latest firmware, both to wait until Atmosphere hits a stable "release" build, and for the signature patches to be updated for the latest 15.0 Firmware and for Atmosphere 1.4.0 as well.

:arrow: Source
:discuss: Discussion thread
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • K3Nv2 @ K3Nv2:
    Switch the switch to resolve your issue
  • Xdqwerty @ Xdqwerty:
    @BigArnold, sorry but i cant, i dont have a switch. also what k3nv2 says is a joke
  • B @ BigArnold:
    That's what I figured. I put a post up in a forum but no one seems to replying to posts there. I also don't what this chat is attached to.
  • K3Nv2 @ K3Nv2:
    General chat as it implies
  • Xdqwerty @ Xdqwerty:
    @BigArnold, try posting in the "switch noob paradise" thread
  • B @ BigArnold:
    That's where I put it. But like I said other people's posts from a day or two ago have no responses. I'm not sure if the chat is part of the Nintendo forum that I'm on or a part of the website as a whole.
  • Xdqwerty @ Xdqwerty:
    @BigArnold, part of the website as a whole
  • Xdqwerty @ Xdqwerty:
    then try making a thread
  • Xdqwerty @ Xdqwerty:
    wait you are too new to be able to do that
  • B @ BigArnold:
    That's fine. I'll find my way.
    +1
  • BigOnYa @ BigOnYa:
    @BigArnold you put the fusee or hekate.bin in the hekate/ payloads folder, or use app to push the payload to switch while its in rcm mode
    +1
  • B @ BigArnold:
    The problem is is that TegraGUI isn't detecting my Switch despite it being plugged in and in RCM or maintenance mode.
    +1
  • BigOnYa @ BigOnYa:
    Did you click install driver inside the tegra app.
  • B @ BigArnold:
    I did all of that stuff and it seemed successful but still nothing. The only thing different from the guide I used was that my device wasn't showing up as APX but rather Nintendo Switch.
  • B @ BigArnold:
    I did it inside the Tegra app and Zadig.
  • BigOnYa @ BigOnYa:
    Try a different USB c cable, or different USB port on your pc.
  • B @ BigArnold:
    I tried a different port and don't have another cable. I'm fairly certain there's no issue with the equipment I'm using.
  • BigOnYa @ BigOnYa:
    Some cheap USB c cables don't send data, they only charge
  • B @ BigArnold:
    The cable is usually used to connect my controller to my switch's dock.
  • BigOnYa @ BigOnYa:
    Only other thing Id suggest is using a phone/tablet and use the Rekato app, or different pc
  • B @ BigArnold:
    Okay then.
    Thanks for your help.
    +2
  • S @ salazarcosplay:
    @Xdqwerty how are you doing!?
  • Xdqwerty @ Xdqwerty:
    @salazarcosplay,
    I keep thinking about killing myself and i believe i dont deserve to be happy... i also feel a bit dizzy
  • S @ salazarcosplay:
    @Xdqwerty I believe
    you deserve to be happy
    Xdqwerty @ Xdqwerty: @salazarcosplay, aw thx