Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[impeeza]

I have net framework...

Finally, it work for me. Just it's so long (10 - 15 minutes). Normaly ?

May be. For me took 6 minutes

1.2.0 launches just fine, games work just fine, but whenever I try to run the homebrew menu, either from title+R or the album it crashes with error pointing to title "01000000001000" which is usually related to a custom theme, but I don't even have that folder in the contents folder.
Going back to 1.1.1 fixes the problem.

You don't have the correct sigpatches

 

[petspeed]

You don't have the correct sigpatches

The homebrew menu doesn't need sigpatches?

 

[attaklouise]

May be. For me took 6 minutes

it's a shame it's a command line script. On youtube, a subscriber (deejay87) created a Windows executable but you have to register on discord to get it.

 

[impeeza]

Yes is a exe created from the file on the Atmosphére release page, I did use pyInstaller to create the EXE file. you can download the original file from Atmosphére gitHub https://github.com/Atmosphere-NX/Atmosphere/blob/master/utilities/insert_splash_screen.py , the latest version reduce the time from 10 minutes to aprox 0.6 minute:

I just download the new script and ran using python 3.8 tooks 10 seconds. I am attaching the new script converted to exe using pyInstaller (nope is too big to fit ).

 

[attaklouise]

Yes is a exe created from the file on the Atmosphére release page, I did use pyInstaller to create the EXE file. you can download the original file from Atmosphére gitHub https://github.com/Atmosphere-NX/Atmosphere/blob/master/utilities/insert_splash_screen.py , the latest version reduce the time from 10 minutes to aprox 0.6 minute:

View attachment 280535

I just download the new script and ran using python 3.8 tooks 10 seconds. I am attaching the new script converted to exe using pyInstaller (nope is too big to fit ).

Thaks but https://github.com/Atmosphere-NX/Atmosphere/blob/master/utilities/insert_splash_screen.py
isn't a windows exe file.
i am looking for the same windows exe file as deejay. Could you create it and share it ? It would be nice. I'm not good with python.
Louise.

 

[impeeza]

I had to upload to another site, the URL is:

https://app.box.com/s/fskfn4j9tvq7mhsdobz5hebpj6qz54cu

 

[attaklouise]

I had to upload to another site, the URL is:

https://app.box.com/s/fskfn4j9tvq7mhsdobz5hebpj6qz54cu

thank you so much. Indeed, it is much faster (a few seconds).

 

[impeeza]

We al have to thanks a lot to @SciresM his effort has been a bless for all of us.

 

[wiitendo84]

OMG. I had to reformat my entire microsd card. Trying to redo my atmosphere files and at the moment, I can't even get it to boot past 2 errors one involving something

Fatal error: [NXBOOT]: Unable to identify package1!​

I checked that post but couldn't get it to resolve. Then I got it to show something about a stat stage2 fusee primary,bin
I've formatted it and can't get it to work. Losing my mind over this. Any suggestions?

 

[impeeza]

You are using an outdated hekate_ipl.ini file.



Notice about Atmosphere 1.0.0 and up: The fss0=atmosphere/fusee-secondary.bin in hekate_ipl.ini must be changed to fss0=atmosphere/package3

 

[wiitendo84]

You are using an outdated hekate_ipl.ini file.



Notice about Atmosphere 1.0.0 and up: The fss0=atmosphere/fusee-secondary.bin in hekate_ipl.ini must be changed to fss0=atmosphere/package3

I formatted the card and tried the 1.2.0 atmosphere and same thing. So I formatted it again, and tried 1.1.1 and it boots just fine. I don't get it.

 

[impeeza]

You have a ghost on your SD

 

[RichardTheKing]

I just updated my Switch and homebrew to the latest versions using the latest Atmosphere and Hekate releases. I can boot to the hekate v5.6.4 menu just fine, but trying to go to CFW (emuMMC) just gets me a yellow screen.

Is there a way to fix that? Because using the fusee.bin payload does get me to emuMMC just fine...except the cart reader doesn't work, and I've always use Hekate in the past so I'm used to that.

 

[impeeza]

for sure you didn't modify your hekate_ipl.ini as instructed on the release page:
Notice about Atmosphere 1.0.0 and up: The fss0=atmosphere/fusee-secondary.bin in hekate_ipl.ini must be changed to fss0=atmosphere/package3. And make sure that atmosphere/contents folder does not have old Atmosphere components.

 

[RichardTheKing]

for sure you didn't modify your hekate_ipl.ini as instructed on the release page:
Notice about Atmosphere 1.0.0 and up: The fss0=atmosphere/fusee-secondary.bin in hekate_ipl.ini must be changed to fss0=atmosphere/package3. And make sure that atmosphere/contents folder does not have old Atmosphere components.

What's classified as "old Atmosphere components", though? That part wasn't clear; fusee-secondary.bin is almost definitely counted, but fusee-mtc.bin?
And I did indeed miss the fss0 thing, thanks!

 

[impeeza]

Firmware 13.1.0 is out there, please do not start with <<accidental>> updates, you are the owner of your switch!

If you update, please do not start screaming out about an Atmosphére update, if you have lot of urgency you can decompile the new firmware and make the necessary changes on the code and publish the new version yourself.

 

[M7L7NK7]

They will, don't even bother

 

[PHiLiPZ]

According to the changelog of Atmosphere 1.2.0 the “target firmware” checking changed, which should “improve our compatibility with micro firmware releases, making it more likely that atmosphere "just works" if nothing important has changed”. So maybe current Atmosphere works also with firmware 13.0.1.

 

[Snomannen_kalle]

According to the changelog of Atmosphere 1.2.0 the “target firmware” checking changed, which should “improve our compatibility with micro firmware releases, making it more likely that atmosphere "just works" if nothing important has changed”. So maybe current Atmosphere works also with firmware 13.0.1.

Not a according to SciresM this time around

Atmosphere will need an update to support booting 13.1.0.

There are changes to a service we reimplement, so after the usual version-support fixes we currently get a fatal on boot. I'll be fixing this as soon as I can.

Thank you for your patience, in the meantime. https://t.co/p1ejkK2tL3

— Michael (@SciresM) October 26, 2021

 

[PHiLiPZ]

Hm, it’s 13.1.0 (not 13.0.1 like someone above wrote) so the changes are probably bigger.