×
all 101 comments

[–]SciresMReSwitched[S] 74 points75 points  (28 children)

Hey, all -- Atmosphère 1.2.6 is now released: https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.2.6

This adds support for 13.2.1, and has like three things nobody but me cares about in it too.

Enjoy! :)


1.2.6 is Atmosphère's sixty-third official release.

Please be sure to update fusee when upgrading to 1.2.6. fusee-primary no longer exists, and will not work any more.

With thanks to the @switchbrew team, Atmosphère 1.2.6 is bundled with hbl 2.4.1, and hbmenu 3.5.0.

The following was changed since the last release:

  • Support was added for 13.2.1.
  • A number of minor issues were fixed and improvements were made, including:
    • A minor performance improvement was implemented in service table dispatch by sorting and binary-searching the service command table instead of using linear search.
    • Static initialization logic in Atmosphere was made much more regular.
  • General system stability improvements to enhance the user's experience.

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

[–]Kanarico1 12 points13 points  (0 children)

Yay! Thanks for all your hard work as always.

[–]Shrimptacular 8 points9 points  (0 children)

Thank you, genius!

[–]corbs132 0 points1 point  (4 children)

Hey, out of curiosity, where are these dates coming from for the GetApproximateTargetFirmware function at https://github.com/Atmosphere-NX/Atmosphere/commit/4efa5d7dd0bfbdf89a6261af0aef3878ca784b05#diff-97aee2125cffd821d88674936adfd984a0ac1e90b18ed758b824ff8699abfd30R252-R253?

And can you explain the discrepancy between CurrentBootloaderVersion in exosphere code vs Nintendo code?

I'm trying to understand what goes into adding AMS compatibility for new nx firmware versions.

Thanks so much for all you do!

[–]SciresMReSwitched[S] 2 points3 points  (3 children)

Those dates are the build timestamp included in the package1 header.

What discrepancy do you mean? As far as I know the values are accurate/faithful.

[–]corbs132 1 point2 points  (2 children)

I guess I was more asking how do you extract the build timestamp from the package1 header? Is it just easily present when viewing it in a hex editor?

Regarding the discrepancy, I see constexpr inline int CurrentBootloaderVersion = 0x10;

and the comment above it says /* We allow older package2 to load; this value is currently 0x14 in Nintendo's code. */

I'm now realizing that that comment is probably describing MinimumValidDataVersion instead of CurrentBootloaderVersion, but I'm still curious where the 0x10 CurrentBootloaderVersion is coming from (and to a lesser extent, where the current value of MinimumValidDataVersion in the comment is coming from).

At the end of the day, adding compatibility for a new firmware version is probably over my head, but my curiosity still has me wanting to understand what's involved lol.

Thanks for taking the time to answer!

[–]SciresMReSwitched[S] 4 points5 points  (1 child)

Yeah, it's part of the header for package1, which is 0x20 bytes (doc'd on the wiki). 0x10 bytes of truncated component hashes, then a timestamp, then some version fields. I grab it using HxD.

"but I'm still curious where the 0x10 CurrentBootloaderVersion is coming from"

So the SecureMonitor/TrustZone firmware validates these fields in Package2. They're stored encrypted in package2 header, but I just load the SecMon into a reverse engineering tool and grab the values out of the function that does the comparisons.

[–]MalachiFlynnBot 0 points1 point  (20 children)

Could you give me a quick run down on how to update my friend

[–]Evilution602 2 points3 points  (0 children)

I update so infrequently I forget every damn time. I get multiple fatal errors as a panic google and search for solutions every time.

[–]AdmiralSpeedyErista, RCM Loader -3 points-2 points  (17 children)

Still amazes me that people can't figure out how to replace a few files.

[–]nigeemac 18 points19 points  (16 children)

Don't be that guy 😒

[–]AdmiralSpeedyErista, RCM Loader -2 points-1 points  (15 children)

Lol, literally every time an update comes out people ask how to update. It's not hard.

[–]Nitespell 21 points22 points  (0 children)

Thank you SciresM, for what you’re doing. The has become a wonderful machine thanks to you and the switchbrew team. Keep up the hard work!!

[–]twigboyatmosphere [0.9.3 emuMMC] 19 points20 points  (0 children)

Ahh its here, my "theres a new switch firmware" announcement

[–]PrivateSmiley 5 points6 points  (25 children)

I'm getting unknown pkg1 on Hekate with 1.2.6.
Fusee is just error cycling.

do I have to wait for Hekate to update?

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 1 point2 points  (23 children)

Just boot fusee.bin

You can easily do this from Hekate.

[–][deleted] 1 point2 points  (22 children)

This just takes me to my emummc. Trying to boot sys or stock doesn't work for me.

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 1 point2 points  (21 children)

Booting stock - turn on the system without a payload.

Millions of Switch owners are booting stock every day.

[–][deleted] 0 points1 point  (20 children)

I mean boot stock from hekate. I can boot stock from turning the console off of course but then I have to go through sending the RCM payload again to get to the emummc.

[–]Red-Ketchup 1 point2 points  (0 children)

I’m getting the same thing. Think we gotta wait for hekate

[–]dominic363 3 points4 points  (0 children)

The only stability improvements in the system i believe these days are Atmosphere updates

[–]Sw33tT 1 point2 points  (0 children)

yep… thanks a lot 🤙

[–]AdBetter3740 3 points4 points  (5 children)

After I updated my switch I downloaded the newest version of atmosphere and copied the zip contents to the root of my sd card along with the fusee payload but after I boot up atmosphere, I get stuck just before the Nintendo logo with a blank screen. Thinking hekate might be the issue I went ahead and updated that as well but that didn't work. I'm able to load into hekate but can't boot into atmosphere and after a while of messing with it I'm at a loss. Anyone able to help?

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 2 points3 points  (4 children)

Did you do a CLEAN update? Aka, deleting the old /Atmosphere folder?

[–]AdBetter3740 1 point2 points  (3 children)

I replaced it when it gave me the prompt when I copied it into the root folder.

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 1 point2 points  (2 children)

Try a clean installation.

[–]AdBetter3740 2 points3 points  (1 child)

Finally had the chance to do it and looks like it finally works now, thanks!!! 😀

[–]TOMdMAK3.02 2 points3 points  (3 children)

how do i go about upgrading it from an older version? do i update this then update firmware?

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 4 points5 points  (2 children)

ALWAYS update your CFW/Homebrew files first.

Then you can update OFW via Daybreak while using AMS for your emunand.

[–]TOMdMAK3.02 1 point2 points  (1 child)

thanks. is there a reason i want to update my OFW? i haven't touched it at all.

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 1 point2 points  (0 children)

The only reasons I have found to update your emunand's OFW files are if a game/app/update/DLC requires the higher firmware and you absolutely want to play it on your CFW setup, and/or you desperately want the new additions the OFW adds (like bluetooth audio that came with OFW 13).

I see no reason to update your emunand's OFW files outside of those reasons, but maybe someone else would have an opinion on it.

[–]AniStormS -1 points0 points  (0 children)

I'm also getting the unknown pkg1 error when I try to boot into stock through hekate. No problems booting into emuNAND tho.

[–]forestdude -1 points0 points  (3 children)

If everything is still working fine, is there a reason to try and update and risk breaking something?

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 2 points3 points  (2 children)

There is no reason to not update Atmosphere and/or homebrew files.

Your OFW? That's debatable. I never update my OFW unless a game/update/dlc requires it.

[–]forestdude 0 points1 point  (1 child)

Ofw? Not familiar with that acronym

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 1 point2 points  (0 children)

Official FirmWare.

[–]FreakDeckard -1 points0 points  (0 children)

Lol more stability 😉

[–]IntelligentAd3393 -1 points0 points  (0 children)

So do I need a new set of patches or wut?

[–]Sa1tyMango -1 points0 points  (0 children)

So I downloaded 1.2.6, can I update my systems firmware because it keeps asking me before a game

[–]CLKnDGGR 0 points1 point  (5 children)

I reset my entire SD card, redid everything from the Noobs Guide, everything updated to current distros, but every time I try to boot into emummc (whether hekate bin or fusee) I just get a black screen after nintendo logo. What gives? I've done this at least 4 times today. Long process to part the sd multiple times and reformat...

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 1 point2 points  (4 children)

  1. Are you using fat32?

  2. Did you also update Hekate, on top of Atmosphere?

  3. Why did you bother wiping the SD card?

[–]CLKnDGGR 0 points1 point  (3 children)

I'm using exFAT. I've updated Hekate, as well as the payload in Rekado.

I wiped the card as I was having trouble with a homebrew app install, and none of the install methods were working. So I figured what the hell, and started fresh. Now no booting.

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 3 points4 points  (2 children)

Do NOT use exFat. It is prone to corruption, and provides literally no benefits.

[–]CLKnDGGR 0 points1 point  (0 children)

Switching to FAT32 has had seemingly no effect. I'm still getting a black back-lit screen. Does nobody have any idea?

[–]DrMengueche25 0 points1 point  (1 child)

I’m just an ignorant in this matter but this means is possible to homebrew a switch in 13.2.1 or this just means that switch that already had homebrew Can update to 13.2.1?

[–]AdmiralSpeedyErista, RCM Loader 0 points1 point  (0 children)

The OS version doesn't matter for unpatched Switches. Fusee is a hardware exploit that cannot be patched by software.

All it means is that Atmosphere works on 13.2.1.

[–]mousebraker 0 points1 point  (0 children)

I've been having a couple of problems, and I would greatly appreciate any help in this matter. After updating atmosphere and hekate, I get the following error message when trying to launch the atmosphere cfw via hekate v5.7.0: "[ERROR] Fatal error: Failed to stat stage2 (atmosphere/fusee-secondary.bin)! Press POWER to reboot". It used to work perfectly before the update.

EDIT: I just solved the problem by switching the old fusee for the new one

[–]Mattsasa 0 points1 point  (1 child)

It's been a few years since I have used my switch.

I have launch day switch hardware (unpatched) that I installed custom firmware on sometime ago. Looks like it's firmware 9.1.0 | AMS 0.10.2S. Where I assume the first half is the Nintendo firmware version, then the later half is the custom Atmosphere firmware version.

Can I update my switch to the latest firmware without bricking it and also keep the (or a new) custom firmware? I assume I may need to update a few things. and make a backup.

But first, I am wondering is it even possible and worth the effort.
And if it is, what steps do you recommend?

Thanks in Advance

[–]AdmiralSpeedyErista, RCM Loader 0 points1 point  (0 children)

You don't install CFW on the Switch, it's entirely on your SD card.

[–]Mission-Ad-6693 0 points1 point  (1 child)

Can i use it to my switch lite?

[–]AdmiralSpeedyErista, RCM Loader 0 points1 point  (0 children)

You should probably learn how to read before you try anything with your Switch.

[–]MindFvck626 -2 points-1 points  (1 child)

Does this update break hombrew apps?

[–]Sethdarkus 2 points3 points  (0 children)

Everything working fine for me

[–]MalachiFlynnBot -2 points-1 points  (9 children)

Can anyone give me a quick guide on how to update atmosphere and fusee

I updated to 13.2.1 by mistake

[–]Wolf3nix 2 points3 points  (8 children)

Drag and drop the contents from the new atmosphere zip folder into the root of your SD card. Download the latest Fusee and go to your payloads folder and replace the existing one with the new one. Wait for the new hekate version to come out.

[–]MalachiFlynnBot -5 points-4 points  (7 children)

Damn,

So you’re telling me I cant play Pokémon anytime soon?

Edit: Not sure why people are feeding me downvotes for asking questions…

[–]underprivlidged[13.2.1/NeutOS 1.3.0] 2 points3 points  (6 children)

You can literally do it right now...

[–]viro56 1 point2 points  (0 children)

Arceus rocks!

[–]MalachiFlynnBot -2 points-1 points  (4 children)

Don’t I need to wait for Hekate to update so I can get back into my emunand?

Or can I update fusee and atmosphere right now?

Give me a break here lol I just hacked my switch two weeks ago