Hacking Discussion How do we completely uninstall Kosmos from the micro-SD Card?

[Dothackjhe]

Having learned from experience that Kosmos, beginning on v15, no longer supports sigpatches, I came to the conclusion of wanting to eradicate it from my micro-SD Card.

Question is, what are the files I must remove in order to do so and how do I configure the system to boot to Atmosphere directly when chainloading via Hekate i.e. [CFW (SYSNAND)]?

 

[The Real Jdbye]

Having learned from experience that Kosmos, beginning on v15, no longer supports sigpatches, I came to the conclusion of wanting to eradicate it from my micro-SD Card.

Question is, what are the files I must remove in order to do so and how do I configure the system to boot to Atmosphere directly when chainloading via Hekate i.e. [CFW (SYSNAND)]?

It supports sigpatches. You need to get them from here: https://github.com/Joonie86/hekate/releases
Kosmos uses the official versions of Hekate/Atmosphere, there's nothing special about it, they just provide a preset so you don't have to put much effort in to making it work.

Edit: Seems like this is a recent change.
If indeed Kosmos has removed support for sig patches then simply grab the latest Hekate and Atmosphere and extract them onto the SD to get clean versions.
https://github.com/CTCaer/hekate/releases/
https://github.com/Atmosphere-NX/Atmosphere/releases (don't include the .ini files in the atmosphere folder, in case you have any custom settings there you want to keep)

You may also have to add kip1patch=nosigchk to the main boot entry in hekate_ipl.ini. Also, make sure you have the latest sig patches from https://github.com/Joonie86/hekate/releases

 

[Dothackjhe]

It supports sigpatches. You need to get them from here: https://github.com/Joonie86/hekate/releases
Kosmos uses the official versions of Hekate/Atmosphere, there's nothing special about it, they just provide a preset so you don't have to put much effort in to making it work.

Edit: Seems like this is a recent change.
If indeed Kosmos has removed support for sig patches then simply grab the latest Hekate and Atmosphere and extract them onto the SD to get clean versions.
https://github.com/CTCaer/hekate/releases/
https://github.com/Atmosphere-NX/Atmosphere/releases (don't include the .ini files in the atmosphere folder, in case you have any custom settings there you want to keep)

You may also have to add kip1patch=nosigchk to the main boot entry in hekate_ipl.ini. Also, make sure you have the latest sig patches from https://github.com/Joonie86/hekate/releases

My main concern right now is how to completely remove Kosmos from the micro-SD Card. Or, at least, configure the system to function in such a way that has nothing to do with Kosmos.

I have a good reason for wanting to do this: apparently, booting the system via CFW (SYSNAND) allows for an Atmosphere-running environment that CANNOT run previously installed games (has something to do with the sigpatches not kicking in). Whereas if I booted the system by choosing the "fusee-primary.bin" (pure Atmosphere) as a starting point, I CAN run my previously installed games. It's as if though I am getting two versions of Atmosphere at this rate (one influenced by Kosmos and one which is not), which gives two different results.

 

[The Real Jdbye]

My main concern right now is how to completely remove Kosmos from the micro-SD Card. I have a good reason for wanting to do this: apparently, booting the system via CFW (SYSNAND) allows for an Atmosphere-running environment that CANNOT run previously installed games. Whereas if I booted the system by choosing the "fusee-primary.bin" as a starting point, I CAN run my previously installed games. It's as if though I am getting two versions of Atmosphere at this rate (one influenced by Kosmos and one which is not), which gives two different results.

I suggest not booting CFW sysNAND, best to launch sysNAND normally from boot, to avoid any risks. If you have AutoRCM and can't boot sysNAND normally, there is an option in Hekate (think you have to press the + button or something) to boot OFW, just be aware that it's not 100% stock, there are some patches applied like disabling fuse checks and bypassing the AutoRCM brick, so there is a ban risk, however small)

 

[Dothackjhe]

How do I configure the system to boot to sysNAND from cold boot if I'm chainloading via Hekate?

 

[The Real Jdbye]

How do I configure the system to boot to sysNAND from cold boot if I'm chainloading via Hekate?

Don't use AutoRCM. and turn the console off and on again. Not a good idea to load OFW sysNAND from Hekate as there are always some patches applied, which come with a small ban risk. Which means also with AutoRCM it's impossible to boot a 100% clean OFW. It might be fine but you never know.

 

[Dothackjhe]

Don't use AutoRCM. and turn the console off and on again. Not a good idea to load OFW sysNAND from Hekate as there are always some patches applied, which come with a small ban risk. Which means also with AutoRCM it's impossible to boot a 100% clean OFW. It might be fine but you never know.

I use CFW (SYSNAND) usually, not OFW (SYSNAND). But since having used Kosmos, booting to CFW (SYSNAND) starts an environment where my previously installed games will not work.