Hacking RELEASE Kosmos - A Hekate CFW-package

[Draxzelex]

Thanks.
So i downloaded the files from the first post (GitHub) and
added the line: kip1patch=nogc in the hekate_ipl.ini.
So this is now my ini file:
{-- Custom Firmwares --}
[CFW]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
kip1=modules/required/fs_mitm.kip
secmon=modules/required/exosphere.bin
kip1patch=nosigchk
kip1patch=nogc
atmosphere=1
{ }

Is this correct? Now i can restore my Nand and can go
back to firmware 3.0.1?

Yes. This is optional but you can also set the kip1patches together like kip1patch=nosigchk,nogc and Hekate will read both,

I think you might be wrong here. Not sure though. my understanding is, that newer Atmosphere builds dont "react" to the kip injection via hekate and the hekate_ipl.ini. AT ALL.

Hekate can launch Atmosphere and supports nogc all by itself. To load the nogc patch without Hekate but with Atmosphere, you have to use IPS patches that support nogc as compiled here.

 

[SageIsSerious]

There aren’t any down sides to removing the archive attribute for all files, other than it being slow as hell to do it.

Yeah this didn't work. Used hekate archive bit option for full SD multiple times throughout tinkering, HB menu still not opening by pressing album or holding R bumper and pressing album.

ReinX works no prob

 

[notimp]

Yes. This is optional but you can also set the kip1patches together like kip1patch=nosigchk,nogc and Hekate will read both,
Hekate can launch Atmosphere and supports nogc all by itself. To load the nogc patch without Hekate but with Atmosphere, you have to use IPS patches that support nogc as compiled here.

Can you elaborate please.

The intro text to choixdujournx makes sure to recommend to you a specific hekate fork that hasnt been updated in ages, that comes with that kip patch backed in for kip1patch=nogc to work.

So three questions are open at this point.

1. Does every newer version of hekate (or at least CTCaers hekate, which is the currently most popular one) come with the nogc kip patch baked in?

This is especially important, as features have been taken out of hekate builds already, because they scraped along the size limit of what can be put in a payload bin.

2. Are you certain, that the kip patch for nogc stays the same on every new firmware that got released so far, because the choixdujournx tutorial only talkes about it in the context of 5.1.0 with a legacy hekate fork that isnt CTCaers mod.

3. Are you certain that kip1patch=nogc works on newer versions of Atmosphere, because they apparently changed the loading structure of Atmosphere (first stage, second stage), so kip patches wouldnt be able to be applied by Hekate anymore - at least thats what I read, when reading up on this.

Thank you for giving me the proper word for the second set of patches - thats "easier" to work with (IPS patches), the ones that get applied by Atmosphere on boot, if they are in the correct folders (without hekate ini settings). At least we know that they work.

Are you sure, or can you get it conformed, that 1, 2 and 3 - currently work as well - and are likely to work on future firmwares (because f.e. the kip patch for nogc had not to be changed in the past). Because all we have as public information about that kip patch right now is, that it worked wih 5.1.0 with an unpopular version of Hekate that isnt CTCaers mod.

Its easy to just proclaim, that both methods work - are you certain?
(Sorry to be so anal about this, but this information really is not public as of now - I'm quite certain of that. So confirmation is required.)

 

[notimp]

Yeah this didn't work. Used hekate archive bit option for full SD multiple times throughout tinkering, HB menu still not opening by pressing album or holding R bumper and pressing album.

ReinX works no prob

Sounds like hbloader (https://github.com/switchbrew/nx-hbloader/releases/) not being in the correct place - or having been updated with a version that doesnt work with Atmosphere.

(There are probably two types of .nsp's one that only works while installed, and one that has to be used as a hbl loader for Atmosphere by being loaded directly off the sdcard.)

See the problem with prefabed packages is...

Or maybe filesystem corruption on exfat (brought to you by our good friends "piracy for 40 bucks - tell everyone to go with xcis and exfat").

 

[focusonme]

When i start games on atmosphere it first checks the game and then gives me an error message that my microsd is corrupted.
When i start the game with reinx, it works like a charm
But i want that atmosphere works
(Atmosphere 0.7.4)
Tried atmosphere 0.7.5 but with that Version i get an error message after boot (power off 12 seconds)

 

[WonderBoom]

When i start games on atmosphere it first checks the game and then gives me an error message that my microsd is corrupted.
When i start the game with reinx, it works like a charm
But i want that atmosphere works
(Atmosphere 0.7.4)
Tried atmosphere 0.7.5 but with that Version i get an error message after boot (power off 12 seconds)

You need the sigpatches. Paste the folders inside the atmosphere folder and you should be good to go.

 

[focusonme]

You need the sigpatches. Paste the folders inside the atmosphere folder and you should be good to go.

worked like a charm thank you! sagol

 

[SageIsSerious]

.

(There are probably two types of .nsp's one that only works while installed, and one that has to be used as a hbl loader for Atmosphere by being loaded directly off the sdcard.)

See the problem with prefabed packages is...

Or maybe filesystem corruption on exfat (brought to you by our good friends "piracy for 40 bucks - tell everyone to go with xcis and exfat").

Where can I find the nsp that I can install and it be a game icon instead of going to the album?

 

[Draxzelex]

Can you elaborate please.

The intro text to choixdujournx makes sure to recommend to you a specific hekate fork that hasnt been updated in ages, that comes with that kip patch backed in for kip1patch=nogc to work.

So three questions are open at this point.

1. Does every newer version of hekate (or at least CTCaers hekate, which is the currently most popular one) come with the nogc kip patch baked in?

This is especially important, as features have been taken out of hekate builds already, because they scraped along the size limit of what can be put in a payload bin.

2. Are you certain, that the kip patch for nogc stays the same on every new firmware that got released so far, because the choixdujournx tutorial only talkes about it in the context of 5.1.0 with a legacy hekate fork that isnt CTCaers mod.

3. Are you certain that kip1patch=nogc works on newer versions of Atmosphere, because they apparently changed the loading structure of Atmosphere (first stage, second stage), so kip patches wouldnt be able to be applied by Hekate anymore - at least thats what I read, when reading up on this.

Thank you for giving me the proper word for the second set of patches - thats "easier" to work with (IPS patches), the ones that get applied by Atmosphere on boot, if they are in the correct folders (without hekate ini settings). At least we know that they work.

Are you sure, or can you get it conformed, that 1, 2 and 3 - currently work as well - and are likely to work on future firmwares (because f.e. the kip patch for nogc had not to be changed in the past). Because all we have as public information about that kip patch right now is, that it worked wih 5.1.0 with an unpopular version of Hekate that isnt CTCaers mod.

Its easy to just proclaim, that both methods work - are you certain?
(Sorry to be so anal about this, but this information really is not public as of now - I'm quite certain of that. So confirmation is required.)

1. The latest version of Hekate does support the nogc patch but you have to setup a launch configuration with the line kip1patch=nogc in the .ini file (its literally stated in the GitHub page)
2. 5.1 was the latest firmware when ChoiDujourNX has been released and OP has not been kind enough to update the thread to indicate it supports technically all firmware. When firmware 6.0 first rolled around, Hekate and all other CFW/bootloaders needed to be updated since major things were changed. However those were done a long time ago so everything supports the latest firmware which is currently 6.1
3. Atmosphere is traditionally loaded with their bootloader, Fusee. Fusee has certain patches and sysmodules baked directly into it thus allowing less to be customized on the user's behalf (although most of these don't need to be disabled in the first place). Fusee is missing certain patches due to ReSwitched's policy on piracy but can be added externally via the IPS patches I linked earlier. Another alternative is simply booting Atmosphere via its individual components with Hekate instead of Fusee which the former is arguably superior

 

[notimp]

Doesnt answer a single one of the questions asked. Seriously, specifics please.

I ask again, this time condensed into one question.

Are you sure, that CTCaer Hekate, current version, includes the nogc kip patch, in a way that it can be called via kip1patch=nogc in the hekate ini, so that Atmosphere 0.7.5 will be patched to disable the gamecardslot, on 6.1.0?

Because from things I've read, I somewhat doubt that.

I know that IPS patches work to do so, and I use hekate to load fusee-primary.bin almost every day so I'm not asking in a personal support case, I'm literally asking for factual confirmation.

To me it sounds odd, maybe even impropper, that Atmopheres entire patch ecosystem and the way it is loaded (fusee-primary > fusee-secondary) changed, and the kip patch for nogc would still be applied as in the olden days, with 5.1.0 - when the choixdujournx author got out of his way to link to a hekate fork that includes the nogc kip - that today no one uses.

So please, specifics.

A "yes I'm sure" is fine as well - if you are certain about it. I just want to prevent people not using the NOGC ips patches - and then having their GC slot updated, because kip1patch=nogc didnt work on CTCaer Hekte or 6.1.0.

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

Where can I find the nsp that I can install and it be a game icon instead of going to the album?

https://gbatemp.net/threads/homebrew-menu-loader-legal-nsp.518433/

Remember that if you install NSPs and Nintendo sees it (online), you have a increased ban risk.

 

[naddel81]

what is the difference exactly between this https://github.com/AtlasNX/Kosmos/releases and rajNX?

 

[notimp]

what is the difference exactly between this https://github.com/AtlasNX/Kosmos/releases and rajNX?

On is a "package" for need easy package people, including several apps and several CFWs.

The other one is a CFW (Custom Firmware).

 

[naddel81]

On is a "package" for need easy package people, including several apps and several CFWs.

The other one is a CFW (Custom Firmware).

I still do not get the difference since both do basically the same, right?

 

[Draxzelex]

Doesnt answer a single one of the questions asked. Seriously, specifics please.

I ask again, this time condensed into one question.

Are you sure, that CTCaer Hekate, current version, includes the nogc kip patch, in a way that it can be called via kip1patch=nogc in the hekate ini, so that Atmosphere 0.7.5 will be patched to disable the gamecardslot, on 6.1.0?

Because from things I've read, I somewhat doubt that.

I know that IPS patches work to do so, and I use hekate to load fusee-primary.bin almost every day so I'm not asking in a personal support case, I'm literally asking for factual confirmation.

To me it sounds odd, maybe even impropper, that Atmopheres entire patch ecosystem and the way it is loaded (fusee-primary > fusee-secondary) changed, and the kip patch for nogc would still be applied as in the olden days, with 5.1.0 - when the choixdujournx author got out of his way to link to a hekate fork that includes the nogc kip - that today no one uses.

So please, specifics.

A "yes I'm sure" is fine as well - if you are certain about it. I just want to prevent people not using the NOGC ips patches - and then having their GC slot updated, because kip1patch=nogc didnt work on CTCaer Hekte or 6.1.0.

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


https://gbatemp.net/threads/homebrew-menu-loader-legal-nsp.518433/

Remember that if you install NSPs and Nintendo sees it (online), you have a increased ban risk.

I find it impossible to get anymore specific so I'm gonna risk sounding like a broken record and repeat everything I just said but use a visual aid. Now I wish I could link specific parts of a webpage to show you what the hell I'm talking about, but since I cannot I'll just link the page and show an excerpt from said page. The following is information posted on CTCaer's GitHub page of Hekate V4.2: (Source: https://github.com/CTCaer/hekate/tree/v4.2)

Spoiler

These "config options" are designated lines that go under your "Launch Configurations" which you can name, customize, and do everything as specified above. One of the specifications is the kip1patches of which Hekate supports two, nosigchk (for custom/unsigned applications such as homebrew) and nogc (disables the gamecart slot). There are other kip1patches but that's not important right now. Right here is definitive proof Hekate supports the nogc patch.

Now unfortunately one thing this page is lacking is information is whether this is supported across all firmwares or not. While it is a safe assumption that it does, because it doesn't specify there are any firmwares that are not supported, you can easily test if the nogc patch is working on firmware 6.1 by loading a Launch Configuration with the line "kip1patch=nogc" then seeing if a retail cartridge works or not (the end result should be fairly obvious).

Lastly, I think part of the problem you have understanding is mixing up Hekate, which is a bootloader, with Atmosphere, which is a CFW. To the laymen, the differences are negligible but to the astute, both can accomplish similar goals, especially in tandem. Meaning both Hekate and Atmosphere can patch the Switch firmware simultaneously. Therefore, if Hekate is able to apply the nogc patch all on its own, then its irrelevant which CFW you use since Hekate's job is merely to load CFW. When Hekate launches any CFW, both Hekate's and whichever CFW you are using will have both of their patches applied.

 

[notimp]

Yes - its easy to test out - and if the retail cartridge works, than your gamecardslot firmware is updated.

Answer is you dont know. If the kip patch method still works with newer Atmosphere builds (which changed the launch structure to a two stage process despite how they worked, when kip nogc was build), and you think that it is a safe assumption, that it works with newer firmwares as well.

Untested, undocumented. But you recommend it to people.

Thank you for finding out, that CTCaer hekate includes the nogc kip patch. That was new information to me.

edit: This is why they ended up in CTCaers hekate, it was a submit from July of this year and probably hasnt been touched since:
https://gbatemp.net/threads/ctcaer-hekate-that-can-automatically-patch-fs-kip1.512323/

Here is the other part of that logic - Atmosphere since 0.7.0 doesnt need nosigchk either to load signature patches - the entire patch loading structure has changed (kips are now loaded as IPS patches).

 

[Draxzelex]

Yes - its easy to test out - and if the retail cartridge works, than your gamecardslot firmware is updated.

Answer is you dont know. If the kip patch method still works with newer Atmosphere builds (which changed the launch structure to a two stage process despite how they worked, when kip nogc was build), and you think that it is a safe assumption, that it works with newer firmwares as well.

Untested, undocumented. But you recommend it to people.

Thank you for finding out, that CTCaer hekate includes the nogc kip patch. That was new information to me.

edit: This is why they ended up in CTCaers hekate, it was a submit from July of this year and probably hasnt been touched since:
https://gbatemp.net/threads/ctcaer-hekate-that-can-automatically-patch-fs-kip1.512323/

Here is the other part of that logic - Atmosphere since 0.7.0 doesnt need nosigchk either to load signature patches - the entire patch loading structure has changed (kips are now loaded as IPS patches).

I'd like to congratulate on now wasting a good half hour of my time updating to firmware 6.1, downloading Atmosphere, and setting up the nogc patches. With both Hekate having the line "kip1patch=nogc" and Fusee using the nogc patches provided by the The-4n, my Switch could not read my retail cartridge meaning the nogc patch was working meaning it still prevents the slot from being updated even on firmware 6.1. Now if you want to continue this farce any longer, major future firmware updates may require the nogc patch to be updated (such as when firmware 6.1 came out which temporarily broke atmosphere's patches but not ReiNX's). Unfortunately I cannot test if the slot still works on firmwares below 4.0 because my console was on 4.1 when Fusee Gelee was released but I think this is all the evidence you, me, and everyone else needs to know that the nogc patch works on 6.1

 

[Semaphor]

Hey,

i have a problem with this packaga/tutorial.
My Switch is on fw: 3.0.2 without exfat update.
I followed the tutorial but atmosphere will not start.
After pressing "launching CFW" in Hekate, i can see the nintendo logo and
my screen is getting black. Afterwards the switch-logo shows up
and then the screen gets black again.

Ok everything is working now. My sd-card was formated as exfat.
Because of the missing exfat update on my switch, atmosphere could not start.

 

[Stoned]

Is there any way to use rpx patches on Kosmos?

 

[LeMageFro]

Just to be extra sure, can someone confirm that the "kip1patch=nogc" option is recognized by hekate 4.2 and that I can just add this line to the hekate_ipl.ini provided in this pack (under every boot option I intend to use obviously) to disable the gamecard reader ?
Thanks in advance.

 

[Draxzelex]

Just to be extra sure, can someone confirm that the "kip1patch=nogc" option is recognized by hekate 4.2 and that I can just add this line to the hekate_ipl.ini provided in this pack (under every boot option I intend to use obviously) to disable the gamecard reader ?
Thanks in advance.

Yes you can, its listed on Hekate's GitHub page.