So you might wonder what are these two booting methods you should use and how to apply the patches correctly. There are 2 different methods to boot into Atmosphere.
- Boot using fusée-primary
This is the primary method of booting atmosphere supported by the developers.
Example1: You send Atmosphère fusée-primary payload directly to the console in RCM.
Example2: You send Hekate_CTR payload to the console in RCM, which boots Atmosphère using “payload=fusée-primary” functionality.
The scenario in example 2 is the same way of launching Atmosphère as in Example1, except it's chain-loaded by Hekate.
- Using Hekate to boot fusée-secondary
Hekate can boot Atmosphère by extracting Atmosphere modules directly from fusée-secondary.bin, which can then be loaded or replaced independently.
Example3: You send Hekate_CTR payload to the console in RCM, which boots Atmosphère using “fss0=fusée-secondary” functionality.
Note that "sending" here refers to using your preferred Fusée Gelée payload sending method with your console in recovery mode: computer(TegraRCM), USB dongle, phone apps, etc.
You still haven't explained which version to use, better if someone creates a ready-made package?