Hacking RELEASE Kosmos - A Hekate CFW-package

[tomGER]

must i wait for update to use Atmosphere 0.7.5 with hekate?

no, just put fusee-secondary.bin on your root and run fusee-primary.bin either through hekate or some fusee gelee program lol

Besides, only creport was updated when you really want to use 0.7.5 - You could in theory even overwrite your current SD files with the 0.7.5 release zip and it could (possibly) work

 

[Pyro1992]

I must

no, just put fusee-secondary.bin on your root and run fusee-primary.bin either through hekate or some fusee gelee program lol

Besides, only creport was updated when you really want to use 0.7.5 - You could in theory even overwrite your current SD files with the 0.7.5 release zip and it could (possibly) work

With only drag and drop my Switch crashed at start. I have to copied the 0.7.5 kips, then it works

 

[Marchombre]

Just a stupid question : for someone who took the default package to run Atmosphere, what should I remove from the old version, after the v11, to clean up my sd card ?

thanks !

 

[focusonme]

thank you for your continuous hard work

 

[Asia81]

Hi,
Custom bootlogo is not working for me.

AutoBoot : CFW + FTP
Boot time delay: 1s
Custom boot logo: Enable
Auto HOS power off: Enable
Backlight: 100%

And it still showing the tiny logo "Hekate-ipl'

 

[Pyro1992]

Hi,
Custom bootlogo is not working for me.

AutoBoot : CFW + FTP
Boot time delay: 1s
Custom boot logo: Enable
Auto HOS power off: Enable
Backlight: 100%

And it still showing the tiny logo "Hekate-ipl'

"
The bootlogo can be any size with a maximum of 720 x 1280.

When it's smaller than 720 x 1280, it is automatically centered and the background takes the color of the first pixel.

When saving a landscape bootlogo, it should be rotated 90 degrees counterclockwise.

Lastly, the supported format is 32-bit (ARGB) BMP. Classic 24-bit (RGB) BMPs are not supported for performance reasons."

Look at the right 32 Bit BMP Format and put it into bootloader/bootogo.bmp

 

[Asia81]

"
The bootlogo can be any size with a maximum of 720 x 1280.

When it's smaller than 720 x 1280, it is automatically centered and the background takes the color of the first pixel.

When saving a landscape bootlogo, it should be rotated 90 degrees counterclockwise.

Lastly, the supported format is 32-bit (ARGB) BMP. Classic 24-bit (RGB) BMPs are not supported for performance reasons."

Look at the right 32 Bit BMP Format and put it into bootloader/bootogo.bmp

I'm using the original kosmos bootlogo

 

[huma_dawii]

Is this the thread for SDFiles? D: I cant find the old one :v

EDIT: It is... WTF why to change the name this late in the project? NOBODY will call this Komos xD

 

[tiliarou]

Is this the thread for SDFiles? D: I cant find the old one :v

EDIT: It is... WTF why to change the name this late in the project? NOBODY will call this Komos xD

Nobody for sure, however we will call it Kosmos.

 

[Asia81]

Nobody for sure, however we will call it Kosmos.

Meh you're not funny

 

[huma_dawii]

Meh you're not funny

They are ridiculous, but still we will call it SDFiles, they can call it Kosmos, Pyra, Mythra or Shulk if they want xDDDDD,

 

[ScottNBNP]

Just a stupid question : for someone who took the default package to run Atmosphere, what should I remove from the old version, after the v11, to clean up my sd card ?

thanks !

I second that. With the update I don't see any files in the bootloader so should I keep some files and move em around?

 

[OrGoN3]

Fusee-primary and fusee-secondary, along with the BCT.ini are no longer in Kosmos, yet are still included on the SDFiles site. Are these needed when booting from hekate?

 

[tiliarou]

Fusee-primary and fusee-secondary, along with the BCT.ini are no longer in Kosmos, yet are still included on the SDFiles site. Are these needed when booting from hekate?

They are needed only if you chainload hekate with fusee, i.e. if within hekate you choose to boot fusee primary payload.

 

[Semaphor]

Hi,
i wanna patch my Switch (FW: 3.0.1) for the first time, with this All-in-One Package.
1. Are these SigPatches for the Atmosphere-CFW included or do i need to add them manually?
2. I wanna update my Switch with the help of ChoiDujourNX but at the same time i wanna make sure
my gamecard controller works after i downgrade back to < 4.0.0. In the ChoiDujourNX FAQ the write:
"When flashing the firmware image for any 4.0.0 or later firmware, ChoiDujourNX will generate a protective hekate_ipl.ini on your microsd, with a "PreventGCUpdate" launch target. You must ALWAYS boot using this launch target (or add kip1patch=nogc to any launch target you wish to use in the future) and use a Hekate that supports the kip1patch option if you want to prevent use and updating of your GC controller firmware on firmware versions 4.0.0 and up."

So this is a little bit confusing. After first time booting the cfw i start ChoiDujourNX and update my switch and that`s all?
Is the package still working after that or do i have to do someting else?

 

[Draxzelex]

Hi,
i wanna patch my Switch (FW: 3.0.1) for the first time, with this All-in-One Package.
1. Are these SigPatches for the Atmosphere-CFW included or do i need to add them manually?
2. I wanna update my Switch with the help of ChoiDujourNX but at the same time i wanna make sure
my gamecard controller works after i downgrade back to < 4.0.0. In the ChoiDujourNX FAQ the write:
"When flashing the firmware image for any 4.0.0 or later firmware, ChoiDujourNX will generate a protective hekate_ipl.ini on your microsd, with a "PreventGCUpdate" launch target. You must ALWAYS boot using this launch target (or add kip1patch=nogc to any launch target you wish to use in the future) and use a Hekate that supports the kip1patch option if you want to prevent use and updating of your GC controller firmware on firmware versions 4.0.0 and up."

So this is a little bit confusing. After first time booting the cfw i start ChoiDujourNX and update my switch and that`s all?
Is the package still working after that or do i have to do someting else?

1. They're pre-included
2. After you download the files, in the /bootloader folder, there is a hekate_ipl.ini. Simply pick the Launch Configuration you will mainly be using (preferably CFW) and add the line kip1patch=nogc

 

[Grand-Master]

Your contributions to the scene are transcendental Hero, continue the adventure!

 

[Semaphor]

They're pre-included
After you download the files, in the /bootloader folder, there is a hekate_ipl.ini. Simply pick the Launch Configuration you will mainly be using (preferably CFW) and add the line kip1patch=nogc

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?

 

[notimp]

1. They're pre-included
2. After you download the files, in the /bootloader folder, there is a hekate_ipl.ini. Simply pick the Launch Configuration you will mainly be using (preferably CFW) and add the line kip1patch=nogc

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.

There are nogc sigpatches you guys opted to NOT include into your sdfile package - that would do that on newer Atmosphere (without being called via the hekate_ipl.ini first). They simply load if in the correct folder, and work.

The entire hekate_ipl.ini kip1patch=nogc stuff is legacy, and as far as I've researched wouldnt even work with CTCaers Hekate at all. (You'd need an even older hekate fork with that kip patch included into the hekate binary - thats even more legacy, and whose kip patch almost certainly doesnt work on current firmwares.)

So wrong answer and this guys GC slot will get updated.

As far as my knowledge goes - please discuss or confirm.
(I can confirm that nogc sigpatches for newer Atmosphere builds get loaded, if they are in the correct folders - without the ini tweak - but you guys dont have them in the SDfiles package.)

NOGC patches for current Atmosphere can be found here:
https://gbatemp.net/threads/i-heard-that-you-guys-need-some-sweet-patches-for-atmosphere.521164/

(Also relying on people that dont care for certain use cases - and build packages - is the bane of going with a package and not learning basic stuff on your own.)

Also - thats the issue with having someone just posting a "i come with sweet patches" thread as a release posting at first, with no dev input whatsoever, because thats considered swag.

Also I asked for confirmation before - then got nagged by people that thought I was too harsh on noobs, then no one answered. Then I responded with "this information isnt out there - I still would like to get a dev reaction" - which was seen as me not surcuming to an extraordinarily silly "look - now the tables have turned, and you need help" argument for feels sake. Oh, it was a whole fun thing. Like an old man on a mountain situation, where the old man had no answers at all, but still wanted to have the young man see the wrongs of his ways - of not being polite to everyone. I have to say, I was a little irritated.

I eventually took the plunge, copied over the NOGC patches, used a current CTCaers Hekate version, didn't set the ini entry, and the NOGC patch got applied on boot ("GC slot not working please call Nintendo" message). This is as much input as I can give.

 

[Metion]

I'm using the latest Kosmos 11.0.1 and i have that issue where your console will freeze if you open too many games/apps without rebooting. It is fixed in Atmosphere 0.7.4 (and i have no issues if use stock Atmosphere with fusee-primary and fusee-secondary) , but with Kosmos it's still there, am i doing something wrong or it's a known issue?