Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[tomaladisto]

The battery drain bug somehow fixed itself after updating from v20.1.0 to v20.1.1, I have no idea how since I haven't really done anything differently. Hopefully I won't trigger it again unintentionally in the future.

 

[impeeza]

It's laters Hekate so are renamed.

for prepacked packages ask support on their site. or UPGRADE everyting manually, remove all atmosphère and homebrew from your card and isntall manually all you need.

 

[ChalkLines]

The only difference so far on the Atmosphère repo is the USB 3.0 patch for FW 20.0.1 (its the same for 20.1.1) that patch is even missing on the latest 1.9.1 release.

Anybody can build latest commit following https://gbatemp.net/threads/building-atmosphere-on-windows-using-msys2.613446/

Lol. Well, yes. That's why I specifically mentioned it. And it's a very good fix. I already tried setting all that up on a number of occasions and have never been successful. I've successfully compiled other things, but have never had any luck with Atmosphere. That's why I politely asked if some kind person who already has everything set up could make a version with the USB 3.0 fix instead of waiting who knows how long for an "official" updated build. I'm sure enough people on newer fw would like the USB 3.0 speeds working.

 

[impeeza]

Lol. Well, yes. That's why I specifically mentioned it. And it's a very good fix. I already tried setting all that up on a number of occasions and have never been successful. I've successfully compiled other things, but have never had any luck with Atmosphere. That's why I politely asked if some kind person who already has everything set up could make a version with the USB 3.0 fix instead of waiting who knows how long for an "official" updated build. I'm sure enough people on newer fw would like the USB 3.0 speeds working.

Try the instructions today, today will work without any «trick» sometimes when SciresM is actively developing you need to joggling with libraries and LibNX manual builds, but today installing packages, a clone and a make will build the code.

 

[ChalkLines]

Try the instructions today, today will work without any «trick» sometimes when SciresM is actively developing you need to joggling with libraries and LibNX manual builds, but today installing packages, a clone and a make will build the code.

I had already tried today. To a T. Over and over to make sure nothing was missed. If you're unable or unwilling to help, there's no point in you replying about it any further. "Follow the guide" doesn't help. Already followed it, and I can tell you that it's missing steps. Some of the commands didn't even work without researching what the errors meant. Had to install things not even listen in the guide. But still ... I'm not dealing with deciphering more error messages. If you don't want to help if it's so simple, so be it.

 

[impeeza]

I can tell you that it's missing steps.

Can you please give the feedback as stated on the guide, the guide is open to comments and improvement. and if somebody finds something need to change or add, it's helpful to add it on the tutorial, so others will benefit from it.

Some of the commands didn't even work without researching what the errors meant. Had to install things not even listen in the guide.

That is exactly What I mean, if you had to research, leaving a feedback will help others to avoid having to research the same again.


So far the feedback received in the past helped to make a better guide.

 

[ChalkLines]

Can you please give the feedback as stated on the guide, the guide is open to comments and improvement. and if somebody finds something need to change or add, it's helpful to add it on the tutorial, so others will benefit from it.


That is exactly What I mean, if you had to research, leaving a feedback will help others to avoid having to research the same again.


So far the feedback received in the past helped to make a better guide.

Anyway. I think I got it. But what does "dirty" mean in the resulting zip files:

atmosphere-1.9.1-master- d8a37b4b7-dirty.zip
&
atmosphere-1.9.1-master- d8a37b4b7-dirty-debug.zip

 

[josete2k]

That means that some file(s) are not matching hash with git repo

 

[impeeza]

Anyway. I think I got it. But what does "dirty" mean in the resulting zip files:

atmosphere-1.9.1-master- d8a37b4b7-dirty.zip
&
atmosphere-1.9.1-master- d8a37b4b7-dirty-debug.zip

Means you edited or changed any file and then started the build.

 

[ChalkLines]

That means that some file(s) are not matching hash with git repo

Means you edited or changed any file and then started the build.

Ah. Yes. I had to edit the 2 files for having Python 3 instead of Python 2 installed. Thanks.

 

[impeeza]

Ah. Yes. I had to edit the 2 files for having Python 3 instead of Python 2 installed. Thanks.

If you like the zip do not have the -dirty you can commit locally your files changed running the command:

git add .

this create a new local commit and when you build it the resultant file have that number of commit.

 

[_badger67]

I'm currently not experiencing the battery discharge issue. So i'm very hesistant on changing anything on my system but actually will need to have to in order to migrate my save states and what not to switch 2. I'm on 20.1.0 on sysnand. My emunand is somewhere below that. Now I would need to upgrade sys to 20.1.1 to go further.

My emunand has originally be created on some 2.x.x firmware with an original linked NNID in it and patched via daybreak over the years.

Should I be worried about upgrading sysnand? Would it help to unlink the nnid in emunand via linkalho? Or would you for sure have to recreate emunand?

Much appreciated.

 

[Blythe93]

I'm currently not experiencing the battery discharge issue. So i'm very hesistant on changing anything on my system but actually will need to have to in order to migrate my save states and what not to switch 2. I'm on 20.1.0 on sysnand. My emunand is somewhere below that. Now I would need to upgrade sys to 20.1.1 to go further.

My emunand has originally be created on some 2.x.x firmware with an original linked NNID in it and patched via daybreak over the years.

Should I be worried about upgrading sysnand? Would it help to unlink the nnid in emunand via linkalho? Or would you for sure have to recreate emunand?

Much appreciated.

While Atmosphere 1.9.1 apparently works (i.e. boots) on latest 20.1.1 firmware, there are probably some issues that need to be addressed by the dev who is apparently on a vacation right now. However, you should be able to update your sysNAND without many issues.

Why would you be worried, because you used Daybreak to update your sysNAND? Last time I checked, Daybreak updates the Switch pretty much the same way Nintendo does (someone tell me if I'm wrong, but I'm pretty sure I've read it somewhere in the official Atmosphere repo or issues).

If you're unsure about whether the battery draining issue will happen on your emuNAND, you could make a backup of your emuNAND and, if things go south, restore it and update only up to 19.0.1. Otherwise, if you'd like to update your emuNAND even further and get rid of the battery draining issue, make sure that you agree to the new EULA on your clean sysNAND before you make an emuNAND from it. If you do that, I believe that you shouldn't run into a battery draining issue.

I personally haven't run into that issue because I never had any real NNID linked to any of my profiles (only fake ones with linkalho) so I can only tell based on what I've gathered from other users.

 

[viper3344]

Can anyone verify if atmo 1.9.1 works with 20.1.1? And real confirmation yet on that?

Thanks!

 

[impeeza]

Can anyone verify if atmo 1.9.1 works with 20.1.1? And real confirmation yet on that?

Thanks!

YES YOU CAN CONFIRM ON SEVERAL POST BEFORE YOURS AND ON THE RELEASE PAGE OF ATMOSPHERE.

 

[viper3344]

YES YOU CAN CONFIRM ON SEVERAL POST BEFORE YOURS AND ON THE RELEASE PAGE OF ATMOSPHERE.

On the actual github release of atmo is mentions NOTHING about 20.1.1 ONLY 20.1.0

 

[Blythe93]

On the actual github release of atmo is mentions NOTHING about 20.1.1 ONLY 20.1.0

It works from what I've gathered around here, but it might need an update. I'm still on 20.1.0 and waiting. Even 19.0.1 should be fine for a while.

 

[viper3344]

It works from what I've gathered around here, but it might need an update. I'm still on 20.1.0 and waiting. Even 19.0.1 should be fine for a while.

Got it sounds good. I wonder if this will be the final SDK release of the original switch!

 

[mathew77]

@viper3344
Nope lol, it won't.

 

[Blythe93]

Got it sounds good. I wonder if this will be the final SDK release of the original switch!

Most likely not as it'll probably get updated alongside Switch 2 (which is more like a beefed up Switch Pro to me).