Hacking Kosmos is no more

[regnad]

Sorry, I do have the latest Hekate on my SD card (mainly to create or migrate emuMMC, change AutoRMC, etc) then I just use the Fusee payload to boot into Atmosphere.

I have no Hekate patches in Atmosphere (although I don't see a problem having it), Hekate payload is only used if I ever want to go into non CFW sysMMC.

I'll check to see if the latest Hekate with patches still gives me problems with Tinfoil, since moving from Kosmos all my sysmodules work as intended.

Edit: Just checked booting with Hekate, Tinfoil sees it as Kosmos.

I really don't see a a point in booting with Hekate unless you really care about the 3 seconds it shaves of booting into Atmosphere.

Game (Doom 2016) loading times were the same for both. Tinfoil does not give you a message with Fusee and who know which files it changes in order to uninstall it's claim on Hetake offending files.

I never boot with Hetake anymore, it's more of utility for ease of SD setup there days than a payloader to boot into Atmosphere.

Even my Lanuch icon(s) in Hetake are configured to chainload Fusee emuMMC and Stock sysMMC (removed CFW sysMMC) but that's not the method I use to boot.

I have Fusee on my RCMLoader as the first payload and Hetake as my second payload if I ever want to boot into sysMMC or configure something in Hetake.

I’m kind of a noob, but I remember having to use Hekate to enable the game cart to work after updating. Is this not necessary with fusee?

 

[Nemix77]

I'm pretty new to the Switch hacking scene myself, for my carts, I only use them in Stock firmware.

I haven't tried dumping my own carts yet because I do not go online in CFW.

But yeah, loading carts in CFW is a Atmosphere thing not Hetake thing.

To my knowledge, usually when a new release of Atmoshpere comes out it goes hand in hand with a new release of Hetake since many use Hetake as a bootloader and configuration of emuMMC for Atmosphere.

Where as Fusee is built right into Atmosphere and gets updated (the payload) with every new Atmosphere release but rarely are there any new features added to Fusee.

It's a simple payloader that just works without any extras and it's updated for the sake of loading new patches and compatibility with the latest Atmosphere CFW.

 

[DuveltjeDG]

It's a shame that Kosmos stopped because of the scene issues. But Kosmos was just a package which made everything easy to install. Just read about how Hekate works and how Atmosphere works. Everything else become make more sense after that. I used Kosmos in the past but went over to do it manually myself. This way I now understand more about everything.

The only thing I miss right now is there discord. There were the developers of Goldleaf, Edizon etc. Is there a new discord where those guys went?

 

[urherenow]

sigh... Kosmos was good because it took guesswork out of it for newbs. sdfiles still does the job, to my knowledge, though.

People simply need to understand the boot process, and what does what.
As of the latest Atmosphere and latest hekate, you don't need any custom kips. Delete them. Delete any mention of kips in hekate_ipl.ini.

If the entry you're using is fss0 and using fusee-secondary, then you are using hekate's bootloader. All of your settings are controlled by hekate_ipl.ini.

If the setting that you launch uses "payload=fusee-primary.bin", then you're using Atmosphere. Period. All of your settings in this case are in atmosphere/config (and in multiple .ini files), and your patches need to be the Atmosphere patches.

If you want to use your game carts and don't mind the firmware getting updated in your came cart slot, then force-disable the nogc setting.
For the EXACT lines needed to configure Atmosphere, study the template files: https://github.com/Atmosphere-NX/Atmosphere/tree/master/config_templates

 

[Imancol]

hate them? Why don't you HATE the asshole that put their name on it? That was done on purpose. And it served the purpose. Putting their name on it, suggesting that people donate to their patreon, puts them in real-world danger of lawsuit and prison. You simply can't make money off of Nintendo's IP and come out clean.

I have 1 and only 1 name in mind of who is responsible. Sad part is, he's actually the biggest stinking pirate of them all, and deserves to be in prison. Now, on top of jacking up the scene, he's also jacking up people's lives. This is NOT a game.

Very soon it will fall under its own weight, and the Scene will be free again, without absurd utopias.

 

[WiiHomebrew+Snes]

\As of the latest Atmosphere and latest hekate, you don't need any custom kips. Delete them. Delete any mention of kips in hekate_ipl.ini.

IIRC isn't that for sig patches? could you elaborate on that?

 

[Oracleofire]

I'll survive, but I will definitely miss them. They made things a lot easier to follow and streamlined the process for keeping up to date. I feel like I got kicked out of my parents house or something. Time to do my own groceries.

 

[urherenow]

IIRC isn't that for sig patches? could you elaborate on that?

up to like the first cycle of updates for HOS 10, having certain things installed (and working) required a custom loader.kip since a certain category of patches via patches.ini were broken for hekate. That has been fixed, and all you need is up-to-date ams+hekate, and the proper patches.. And tinfoil yells at you for having kips (unless you have an sxos license)...

 

[RedHunter]

The drama continues nothing is changed it seems. Laugh in SX.

 

[DuveltjeDG]

up to like the first cycle of updates for HOS 10, having certain things installed (and working) required a custom loader.kip since a certain category of patches via patches.ini were broken for hekate. That has been fixed, and all you need is up-to-date ams+hekate, and the proper patches.. And tinfoil yells at you for having kips (unless you have an sxos license)...

Not really true when you chainload fusee and have the patches.ini in the bootloader folder Tinfoil still nags about it. When removing or changing the name of the ini file there is no issue.

 

[urherenow]

Not really true when you chainload fusee and have the patches.ini in the bootloader folder Tinfoil still nags about it. When removing or changing the name of the ini file there is no issue.

did I say otherwise? Probably forgot to mention it because I don't get that nag. I have an SX license. Anyway, it doesn't make anything I said false. It's trivial to change the name of patches.ini in the source and build it yourself, if you really want to.

 

[DuveltjeDG]

did I say otherwise? Probably forgot to mention it because I don't get that nag. I have an SX license. Anyway, it doesn't make anything I said false. It's trivial to change the name of patches.ini in the source and build it yourself, if you really want to.

Maybe I did read it wrong. It's not all that complicated but a little bit frustrating that one does not work with the other with the only difference being the ini file instead of ips patches.

 

[hippy dave]

Don't run hostile software?

 

[MissingComma]

Now thats kosmos is down, whats the ALTERNATIVE for kosmos

 

[linuxares]

Now thats kosmos is down, whats the ALTERNATIVE for kosmos

Deepsea

 

[MissingComma]

Deepsea

Hey, man thanks for the reply, new at the switch scene. Can u guide me the to a link or a Google search.

 

[Hayato213]

Hey, man thanks for the reply, new at the switch scene. Can u guide me the to a link or a Google search.

https://github.com/Team-Neptune/DeepSea

 

[Draxzelex]

Now thats kosmos is down, whats the ALTERNATIVE for kosmos

Honestly you should go with SDSetup as unlike Kosmos or DeepSea, they let you customize what you want so you don't end up with unnecessary bloat.