Hacking RELEASE Kosmos - A Hekate CFW-package

  • Thread starter Thread starter tomGER
  • Start date Start date
  • Views Views 559,292
  • Replies Replies 1,640
  • Likes Likes 120
What's the difference between this and atmosphere. Also on first page why does it have to bullet points. 1.atmosphere and 2. Full atmosphere? Sounds like I might as well just keep using atmosphere. No offence
It has sig patches as well and uses hekate instead of atmosphère's fusée payload. Hekate has more features.
 
  • Like
Reactions: tiliarou
What's the difference between this and atmosphere. Also on first page why does it have to bullet points. 1.atmosphere and 2. Full atmosphere? Sounds like I might as well just keep using atmosphere. No offence
1. Atmosphere <---all CFW is based on a version of Atmosphere.
2. Full Atmosphere <---meaning they include all modules, like creport, fatal, etc. Other CFW, such as ReiNX, does not include creport by default (although does support it).

I do not like that is says both, but I did not write the OP. It does seem a bit redundant. As someone already said though, the main difference with Kosmos is that it comes preconfigured with Hekate (preconfigured ini file), which is a superior bootloader to plain Fusee, even though Fusee gets updated first and is sometimes the only bootloader that works, and it comes with sigpatches, which enables piracy (or playing downloaded or backed up versions of the games). By default, Atmosphere does not include these patches and it does not allow you to play pirated games.
 
  • Like
Reactions: jammybudga777
Hey guys I am running my switch on an older version of Kosmos. I want to update to the latest version as I want to move to FW 6.2. I have disabled wifi so I dont think i can use the Kosmos updater from HBM. What is the other way to do this?
 
Is there any way future updates can preserve loader.ini? Sick of having to set it back to my one downloaded switch game every time I update Kosmos.

It also downloads a lot of apps that I already have, so I end up with duplicates. Goldleaf, Appstore, Checkpoint. I just have them in different spots.
 
Is there any way future updates can preserve loader.ini? Sick of having to set it back to my one downloaded switch game every time I update Kosmos.

It also downloads a lot of apps that I already have, so I end up with duplicates. Goldleaf, Appstore, Checkpoint. I just have them in different spots.
I want that option too.
Tought it was me doing something wrong.
When updating Kosmo with the toolkit. The config file is back to default so Hekate will not boot Komos automatically anymore.
 
The competition is hot right now, absolutely fantastic work from each dev team. You guys literally rock. Keep it up! There are some of us that truly do appreciate the work you do.
 
  • Like
Reactions: Ivellios and tomGER
Is there any way future updates can preserve loader.ini? Sick of having to set it back to my one downloaded switch game every time I update Kosmos.

It also downloads a lot of apps that I already have, so I end up with duplicates. Goldleaf, Appstore, Checkpoint. I just have them in different spots.
I want that option too.
Tought it was me doing something wrong.
When updating Kosmo with the toolkit. The config file is back to default so Hekate will not boot Komos automatically anymore.
>I just have them in different spots.
Problem is that there is no unified agreed place for them so it's hard to place them in the same location - We however try to format it to either the creators or appstore's vision
>Is there any way future updates can preserve loader.ini?
Yes, Kosmos Updater has a "ignore file" feature for quite some time now - Take a look here: https://github.com/AtlasNX/Kosmos-Updater/blob/master/README.md

Hey guys I am running my switch on an older version of Kosmos. I want to update to the latest version as I want to move to FW 6.2. I have disabled wifi so I dont think i can use the Kosmos updater from HBM. What is the other way to do this?
Just update manually by grabbing the github release and putting it on your SD

The competition is hot right now, absolutely fantastic work from each dev team. You guys literally rock. Keep it up! There are some of us that truly do appreciate the work you do.
Thank you :) There is something even cooler coming very very soon
 
What's the most correct way to update Kosmos offline? Should I simply rewrite files on the SD or delete some files from prior setup?
I believe this was explained before, but my google-fu is weak.
 
Last edited by lordelan,
Updated to 0.8.3 Atmosphere from SDcardsetup and getting a NCA error when I try to install a .NSP file in Goldleaf. I installed the sig patches too, what is wrong please?
 
So I want to switch from rajnx to kosmos (generated from the sdsetup wizard). Thing is, I have updated without burning fuses, from 3.0 to 5.1. Does the included payload have the option to boot cfw+nogc fuse check?

Also this wouldn't burn fuses on reboot to hekate, right?
 
What's the most correct way to update Kosmos offline? Should I simply rewrite files on the SD or delete some files from prior setup?
I believe this was explained before, but my google-fu is weak.
Yeah, deleting and writing is ofc the cleanest but overwriting works too I guess
@tomGER Is the new Homebrew Menu Loader which is based on nx-hbloader v2.1 included in Køsmos v11.9 - Fighting Gold?
In the release notes it says

but that's a bit too general. :)

Edit: Also does the new reboot from error screen to payload feature in Køsmos reboot to hekate instead of Atmo's fusee primary? I hope so. :P
Yes to your first question (Just guessing, @jakibaki added it) - And yes, it boots to Hekate :)

Updated to 0.8.3 Atmosphere from SDcardsetup and getting a NCA error when I try to install a .NSP file in Goldleaf. I installed the sig patches too, what is wrong please?
No idea, try using the one from the release page I guess
So I want to switch from rajnx to kosmos (generated from the sdsetup wizard). Thing is, I have updated without burning fuses, from 3.0 to 5.1. Does the included payload have the option to boot cfw+nogc fuse check?

Also this wouldn't burn fuses on reboot to hekate, right?
You can select a "nogc" option from Kosmos Updater but otherwise we haven't added support yet - You can however just add "kip1patch=nogc" to each boot option in "bootloader/" - There will be a better option very very soon, sorry about that
 
You can select a "nogc" option from Kosmos Updater but otherwise we haven't added support yet - You can however just add "kip1patch=nogc" to each boot option in "bootloader/" - There will be a better option very very soon, sorry about that

So just for clarification, I just need to add the option to the boot list, and nothing else? No additional files needed?
 
Hi, i updated using kosmos updater to atmosphere 0.8.3 and after the update my game carts no longer work and i get "the game could not be read" error. is it kosmos disabling game carts for some reason? the cart game was working right before i updated!
 
Since we can now boot directly into CFW: Can I shut the switch down by pressing the shutdown button on the switch's top? Or will it still reboot into RCM when AutoRCM is enabled?
 
When you choose the "shut down" option in horizon os the console will boot into rcm. You can hold the power button fr ~12 seconds or use the hekate bootloader option "power off"

--------------------- MERGED ---------------------------

Or will it still reboot into RCM
But yes. It reboots into rcm.
 

Site & Scene News

Popular threads in this forum