Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[laz305]

has been out for moths on the github repo https://github.com/Atmosphere-NX/Atmosphere/releases.

Check https://rentry.org/UpdateCFWAndFW

and DO NOT FORGET to upgrade your sigpatches BEFORE the restart https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/

And don’t forget to uninstall themes lol

 

[impeeza]

And don’t forget to uninstall themes lol

Oh, yeah, I almost forgot those.

 

[petspeed]

I’m on ams 1.6.2 can I upgrade to 17.0 or I need to update ams also?

You ALWAYS need to upgrade CFW BEFORE upgrade FW.

AMS 1.6.2 is the latest version so you are already up to date

 

[Purple_Heart]

@laz305 you are on latest ams. just update your FW. but you have to uninstall custom themes for sure.

Post automatically merged: Feb 16, 2024

and sigpatches i would update too.

 

[impeeza]

Firmware 17.0.1(r) has been released, so far no need for new Atmosphère nor other updates.

 

[Amidaraxar]

Hello guys, good evening,

just to avoid committing anything wrong, is it correct that the latest Atmosphère (1.6.2) support the FW 17.0.0 and not 17.0.1?
One last question: which is the difference between the FW rebootless or not?

Thank you in advance

 

[Hayato213]

Hello guys, good evening,

just to avoid committing anything wrong, is it correct that the latest Atmosphère (1.6.2) support the FW 17.0.0 and not 17.0.1?
One last question: which is the difference between the FW rebootless or not?

Thank you in advance

1.6.2 support firmware 17.0.x, rebootless doesn't require a reboot, but you should use the regular firmware, that is what most people would use.

 

[Blythe93]

Hello guys, good evening,

just to avoid committing anything wrong, is it correct that the latest Atmosphère (1.6.2) support the FW 17.0.0 and not 17.0.1?
One last question: which is the difference between the FW rebootless or not?

Thank you in advance

Atmosphere 1.6.2 works with 17.0.1 as it doesn't have any significant change to the main code. Rebootless firmware updates usually contain only bad words filter, so it doesn't matter whether you've updated to the latest rebootless or not.

 

[duckbill007]

Rebootless is minor update above normal firmware. If you want to have most recent fw you should use latest rebootless update. It does not require reboot only if update from previous the same version fw.

 

[petspeed]

I am on 17.0.1 rebootless update and it works fine with Atmosphere 1.6.2.
I updated SysMMC the official way and dumped that with Tegraexplorer and then used the dump to update EmuMMC with Daybreak.

 

[qaz015393]

I haven't updated my switch in a while, what else would I need besides the atmosphere 1.6.2 (master and fuse) and the 17.0.1? I forgot

 

[BigOnYa]

I haven't updated my switch in a while, what else would I need besides the atmosphere 1.6.2 and the 17.0.1? I forgot

https://github.com/Atmosphere-NX/Atmosphere/releases
https://github.com/CTCaer/hekate/releases
https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
https://rentry.org/UpdateCFWAndFW

 

[qaz015393]

https://github.com/Atmosphere-NX/Atmosphere/releases
https://github.com/CTCaer/hekate/releases
https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
https://rentry.org/UpdateCFWAndFW

Ok so it seems to be different than before - I believe last time I onky had to use a app like daybreak or something and then select the few to update. I'll follow that update tutorial but how would I do it for 17.0.1? Because the sigpatch from that page 1 is for 17.0.0

 

[Blythe93]

I haven't updated my switch in a while, what else would I need besides the atmosphere 1.6.2 and the 17.0.1? I forgot

Latest Hekate, sigpatches and/or sys-patch module (grab Tesla + nx-ovlloader as well, for convenience) because these are required for games to work.
Additionally, make sure that you have DNS MITM as well, in order to block Nintendo servers if you ever plan to connect to the Internet (e.g. to use homebrew appstore).
Make sure to uninstall any custom theme before updating.

If you've used either Haku33. TegraExplorer. EmmcHaccGen or ChoiDujour to clean or reset your console in the past, it probably won't be able to boot once you update to the lastest firmware. To fix it, make sure to boot into Atmosphere v1.6.1 or higher (v1.6.2 is currentčy the latest version) on sysMMC. Check here for more info.

Because the sigpatch from that page 1 is for 17.0.0

17.0.1 didn't have any changes done to the actual code so the sigpatches for 17.0.0 work for 17.0.1 as well.

Post automatically merged: Mar 6, 2024

It's also worth mentioning that starting from the next Atmosphere's release, if you're loading Atmosphere's package3 via fusee.bin. kip patches will no longer work.
You'll need to load package3 via Hekate instead.
More info can be found from this post onward. A detailed explanation can be found here as well, courtesy of @impeeza.

 

[qaz015393]

Latest Hekate, sigpatches and/or sys-patch module (grab Tesla + nx-ovlloader as well, for convenience) because these are required for games to work.
Additionally, make sure that you have DNS MITM as well, in order to block Nintendo servers if you ever plan to connect to the Internet (e.g. to use homebrew appstore).
Make sure to uninstall any custom theme before updating.

If you've used either Haku33. TegraExplorer. EmmcHaccGen or ChoiDujour to clean or reset your console in the past, it probably won't be able to boot once you update to the lastest firmware. To fix it, make sure to boot into Atmosphere v1.6.1 or higher (v1.6.2 is currentčy the latest version) on sysMMC. Check here for more info.


17.0.1 didn't have any changes done to the actual code so the sigpatches for 17.0.0 work for 17.0.1 as well.

Post automatically merged: Mar 6, 2024

It's also worth mentioning that starting from the next Atmosphere's release, if you're loading Atmosphere's package3 via fusee.bin. kip patches will no longer work.
You'll need to load package3 via Hekate instead.
More info can be found from this post onward. A detailed explanation can be found here as well, courtesy of @impeeza.

Oh ok. Well I believe I last updated my switch back when I was playing megaman battle network and the Crisis core games. I don't really remember if I used any of those apps in the past to fix any issues like soft brick/ reinstall to update cfw but not 100% sure. I only have wifi on for local play like using my switch pro controller (or maybe Bluetooth controller when I get it since my joycons have drift) and when I was/am trading Pokemon between my games/switchs so I have madterballs and rare candys in my other game while working on dexs). I usually have/keep my device on airplane mode and I don't 100% remember if I did the blocking or not.

 

[worm28]

I have an issue with atmosphere v1.6.2 when i boot into cfw right after the nintendo logo it goes into sleep mode i have to press the home button like three times to get it to turn on after that it works normally it does not happen every time but most of the time i dont know if its an atmosphere issue or if the problem is on my end does anyone else have this issue or know of a fix?

 

[Starwarsfan2099]

I have an issue with atmosphere v1.6.2 when i boot into cfw right after the nintendo logo it goes into sleep mode i have to press the home button like three times to get it to turn on after that it works normally it does not happen every time but most of the time i dont know if its an atmosphere issue or if the problem is on my end does anyone else have this issue or know of a fix?

I've noticed this too.

 

[impeeza]

I've noticed this too.

That's because a slow SD Card, I updated to a new SD and the issue ended.

 

[Starwarsfan2099]

That's because a slow SD Card, I updated to a new SD and the issue ended.

That checks out. Last time I updated Atmosphere and FW I also switched to a larger SD card, which is when this began.

 

[impeeza]

Also look if you have a lot of sysmodules by example NXBootSound with length sounds can cause the issue too.