Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[hippy dave]

Nice to have. But not really neccessary because you can "avoid" these corruptions when you use fat32. Furthermore, it is actually pointless to use exFAT anyway. Files larger than 4GB are not stored on the SD anyway. Unless you would play the games as a virtual gamecard, like in SX OS. But since Atmosphère doesn't support that, it doesn't matter.

The character encoding issues have caused problems with homebrew, usually with ROMs for emulators with funky characters in their filenames, actually that can apply to media files for media players too. ROMs bigger than 4GB can come in to play for emulation homebrew too, and said media files for said media players.
Like you said tho, also just nice to have.

 

[mspy]

Nice to have. But not really neccessary because you can "avoid" these corruptions when you use fat32. Furthermore, it is actually pointless to use exFAT anyway. Files larger than 4GB are not stored on the SD anyway. Unless you would play the games as a virtual gamecard, like in SX OS. But since Atmosphère doesn't support that, it doesn't matter.

There are files (XCI & NSP) that are larger than 4GB so unless you install them via USB or use some tools to divide them into smaller parts you won't be able to just drag and drop them to the SD Card like some people do.

 

[impeeza]

There are files (XCI & NSP) that are larger than 4GB so unless you install them via USB or use some tools to divide them into smaller parts you won't be able to just drag and drop them to the SD Card like some people do.

you can always use DBI or AtmoXL Titel Installer to install via USB or Network so you don't need the double of space on you SD card for installing a title.

 

[nomnaut]

I’m a developer taking some time off from work. Is there anyway I can contribute to the project? Not sure if it needs any help, but I have spare time and experience as a software dev.

 

[impeeza]

Yes, you can contact the developers on discord and or github https://github.com/Atmosphere-NX/Atmosphere
The help is always welcome on the community

 

[zenjiki]

So noob questions, if my switch current firmware is 12.0.2 which atmosphere version should I use? Should I be using Atmosphere 0.19.3 since that was the version made for that firmware? Or can I use the latest version of Atmosphere 1.3.2? Or do I need to update switch firmware to 14.0.0+ to use the latest atmosphere?

 

[impeeza]

So noob questions, if my switch current firmware is 12.0.2 which atmosphere version should I use? Should I be using Atmosphere 0.19.3 since that was the version made for that firmware? Or can I use the latest version of Atmosphere 1.3.2? Or do I need to update switch firmware to 14.0.0+ to use the latest atmosphere?

Atmosphère 1.3.2 support firmwares from 1.0.0 to 14.1.2 so go for the latest, DO NOT FORGET to read the readme.md of atmosphère 1.0.0 https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.0.0 because you need to change some files like hekate_ipl.ini and you need to delete folders from you SD Card (SEPT) principally

and when you update Atmosphère your MUST TO UPDATE your sigpatches and any MOD/CHEAT/SYSMODULE you use.

 

[zenjiki]

Atmosphère 1.3.2 support firmwares from 1.0.0 to 14.1.2 so go for the latest, DO NOT FORGET to read the readme.md of atmosphère 1.0.0 https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.0.0 because you need to change some files like hekate_ipl.ini and you need to delete folders from you SD Card (SEPT) principally

and when you update Atmosphère your MUST TO UPDATE your sigpatches and any MOD/CHEAT/SYSMODULE you use.

So in general my switch can stay the same firmware version forever, and I can just update atmosphere. And just to make sure to update sigpatches, mods, cheats sysmodules I use?

 

[impeeza]

So in general my switch can stay the same firmware version forever, and I can just update atmosphere. And just to make sure to update sigpatches, mods, cheats sysmodules I use?

basically yes.

 

[BaamAlex]

So in general my switch can stay the same firmware version forever, and I can just update atmosphere. And just to make sure to update sigpatches, mods, cheats sysmodules I use?

Yes. But when atmosphere works on said firmware, you can stay on that version and on that sigpatches. No need to update them until you update your firmware.

 

[impeeza]

You need update the sigpatches, because they have Atmosphère and firmware components. So, if you update Atmosphère you need the new Atmosphère sigpatches 8D.

Always use latest sigpatches.

 

[Milenko]

I’m a developer taking some time off from work. Is there anyway I can contribute to the project? Not sure if it needs any help, but I have spare time and experience as a software dev.

It's not a welcoming scene unless you can provide something major

 

[zenjiki]

Thanks for all the info. So I can stay with same switch firmware and atmosphere until I need to update switch firmware cause a new game requires it.

 

[impeeza]

A new Rebootless firmware update is on the air,

https://twitter.com/i/web/status/1541580024154685441

it do not need to reboot your system, and only update the list of "bad" words for the Switch:

https://twitter.com/i/web/status/1541607830205173762

So, if your dog, cousin, wife's boyfriend, etc. "Accidentally" update your Switch, do not need to make a fuzz about it.

 

[Bonovox40]

Question: If I followed Renpy's guide to updating Atmos using the PC method (used Tinfoil to browse via USB and transfer files over in Windows desktop) Why after rebooting, it still shows 13.0.0|AMS 1.2.4|E ?

The idea was to update atmos first and then use daybreak to jump to 14.1 FW. I have no system mods/hacks/cheats/etc. Just plain atmosphere. Any idea why it's not updating to show AMS 1.3.2? Everything else is working as expected, just seems that Atmosphere didn't update.

 

[binkinator]

Question: If I followed Renpy's guide to updating Atmos using the PC method (used Tinfoil to browse via USB and transfer files over in Windows desktop) Why after rebooting, it still shows 13.0.0|AMS 1.2.4|E ?

The idea was to update atmos first and then use daybreak to jump to 14.1 FW. I have no system mods/hacks/cheats/etc. Just plain atmosphere. Any idea why it's not updating to show AMS 1.3.2? Everything else is working as expected, just seems that Atmosphere didn't update.

this guide? https://rentry.org/UpdateCFW#pc-method

Since you don’t have mods hacks or cheats, simply rename your /atmosphere directory to /atmosphere.bk and your /bootloader directory to /bootloader.bk and go back and unzip atmosphere and hekate zip files at the top of your SDCard and then continue with the guide.

e: Be sure you don’t skip fusee.bin step
e2: you might want to consider mounting the SDCard using Hekate UMS rather than Tinfoil.
e3: see @impeeza important note below about hekate_ipl.ini

 

[impeeza]

and do not forget to copy HEKATE_IPL.INI file from bootloader.bak to the new bootloader folder.

 

[Bonovox40]

this guide? https://rentry.org/UpdateCFW#pc-method

Since you don’t have mods hacks or cheats, simply rename your /atmosphere directory to /atmosphere.bk and your /bootloader directory to /bootloader.bk and go back and unzip atmosphere and hekate zip files at the top of your SDCard and then continue with the guide.

e: Be sure you don’t skip fusee.bin step
e2: you might want to consider mounting the SDCard using Hekate UMS rather than Tinfoil.
e3: see @impeeza important note below about hekate_ipl.ini

Thanks for the reply bink. I did the fusee.bin step. And I can't launch into Hekate for some reason. Every since the conversion from SXOS to atmos, the only thing I can do is get it to boot into atmosphere. It's a non issue generally speaking so no biggie.

e3: bootloader.bak? This isn't mentioned in the renpy guide. Where should this file come from/be created by? I don't see any reference to this.

 

[binkinator]

Thanks for the reply bink. I did the fusee.bin step. And I can't launch into Hekate for some reason. Every since the conversion from SXOS to atmos, the only thing I can do is get it to boot into atmosphere. It's a non issue generally speaking so no biggie.

e3: bootloader.bak? This isn't mentioned in the renpy guide. Where should this file come from/be created by? I don't see any reference to this.

This is just to move the old deployments out of the way for both atmosphere and bootloader.

When you unzip the files at the top of your SDCard you will have new atmosphere and bootloader directories with nothing left over from the original deployment (but you have a .bk for backup if you want to roll back).

In the odd case you don’t have a new /atmosphere and /bootloader then we know there’s an issue with the transport method.

Make sense?

 

[petspeed]

Thanks for the reply bink. I did the fusee.bin step. And I can't launch into Hekate for some reason. Every since the conversion from SXOS to atmos, the only thing I can do is get it to boot into atmosphere. It's a non issue generally speaking so no biggie.

e3: bootloader.bak? This isn't mentioned in the renpy guide. Where should this file come from/be created by? I don't see any reference to this.

The Bootloader folder is from Hekate. If you don't use Hekate you don't have it and you can skip that part.