Hacking RELEASE Kosmos - A Hekate CFW-package

[BaamAlex]

What's the point of Hekate saying that my unit is exploitable to the RCM bug? Of course it is if I'm in the menu...

That means you have an unpatched unit.

 

[Fuzzy-v]

Also suffering from updating with Kosmos updater, stuck on Kosmos boot screen - however if I manually inject Fusee it boots but always with Nogc regardless of settings, so in kind of a pickle here. Seen on the Discord there are others with issues too - imagine we'll see a bugfix soon.

Otherwise excellent work, devs.

Edit: just to note, am on 6.20 firmware, no emummc, yet.

 

[mefistos]

Just a heads up, was on 7.0.0 Kosmos 12.2 with AutoRCM on, updated via Kosmos updater, after restart pushed hekate 5.0.0 via my phone and everything works just fine

 

[tomGER]

Hmm since updating to 8.0.1 and using Kosmos v13, my Edizon doesn't seem to recognize cheats anymore. It was working fine right before I updated. Is there something I'm doing wrong?

This is some weird bug introduced with Atmosphere 0.9.2, Scires will hopefully fix it soon.

---

I also want to thank everyone that helps users here, I know that I should probably watch over this thread but I really if you need support and nobody was able to help you here, please ask in the discord ( https://discord.teamatlasnx.com )

I was on 7.0.1 and updated to 8.0.1 with ChoiDujourNX (newest version).
Although I have Atmo 0.8.9 through Kosmos I can't boot into either Atmo with Hekate, Atmo with Fusee Primary or SX OS.
Everything leads to the error stress screen.
However booting Stock through hekate works.
What am I doing wrong?

Error hekate -> atmo:
View attachment 169399

Error Fusee Primary -> atmo:
View attachment 169400

Happens in various situations, not necessarily an error, but still prevents booting. If you got this because you downgraded, it's because you downgraded between major/key versions (7.0.x -> 6.2.0, 6.2.0 -> 6.1.0 etc) without console initialization (deleting system save files). To recover from that: Delete system all save files except 80...120. Keep in mind that this will effectively be a factory reset.

When are you going to add the latest 9.2 ams with it? You made two updates, the first one I get for iPatched owners, but you still only support ams 8.1? Why? I'm glad I stopped using Kosmos, lack of development.

Thanks, it always reminds me why I love this scene so much. We take our time creating something that was never done before, adding support for patched units and by that invest our unpayed freetime and hearts into a project. But hey, 8.1 support was a little bit too late because Hekate added a freaking GUI and Emunand support, better complain to the developer.

 

[ShadowOne333]

This is some weird bug introduced with Atmosphere 0.9.2, Scires will hopefully fix it soon.

---

I also want to thank everyone that helps users here, I know that I should probably watch over this thread but I really if you need support and nobody was able to help you here, please ask in the discord ( https://discord.teamatlasnx.com )



Happens in various situations, not necessarily an error, but still prevents booting. If you got this because you downgraded, it's because you downgraded between major/key versions (7.0.x -> 6.2.0, 6.2.0 -> 6.1.0 etc) without console initialization (deleting system save files). To recover from that: Delete system all save files except 80...120. Keep in mind that this will effectively be a factory reset.


Thanks, it always reminds me why I love this scene so much. We take our time creating something that was never done before, adding support for patched units and by that invest our unpayed freetime and hearts into a project. But hey, 8.1 support was a little bit too late because Hekate added a freaking GUI and Emunand support, better complain to the developer.

Dont listen to the pricks
If he doesn't want to use Kosmos, so be it, he'll brick his console anyway

 

[linuxares]

This is some weird bug introduced with Atmosphere 0.9.2, Scires will hopefully fix it soon.

---

I also want to thank everyone that helps users here, I know that I should probably watch over this thread but I really if you need support and nobody was able to help you here, please ask in the discord ( https://discord.teamatlasnx.com )



Happens in various situations, not necessarily an error, but still prevents booting. If you got this because you downgraded, it's because you downgraded between major/key versions (7.0.x -> 6.2.0, 6.2.0 -> 6.1.0 etc) without console initialization (deleting system save files). To recover from that: Delete system all save files except 80...120. Keep in mind that this will effectively be a factory reset.


Thanks, it always reminds me why I love this scene so much. We take our time creating something that was never done before, adding support for patched units and by that invest our unpayed freetime and hearts into a project. But hey, 8.1 support was a little bit too late because Hekate added a freaking GUI and Emunand support, better complain to the developer.

Well they can go to some other CFW package if they so wish. It's up to them! I for one was very happy that you guys updated so fast after Hekate 5 got released

 

[lordelan]

Happens in various situations, not necessarily an error, but still prevents booting. If you got this because you downgraded, it's because you downgraded between major/key versions (7.0.x -> 6.2.0, 6.2.0 -> 6.1.0 etc) without console initialization (deleting system save files). To recover from that: Delete system all save files except 80...120. Keep in mind that this will effectively be a factory reset.

Thx but as someone else already stated it seem to be the themes (for whatever reason).
After renaming/removing the themes folders from sd:\[cfw]\titles\ all CFWs were working again.

 

[Ian095]

Appreciate your work but please release a newer version with the atmosphere fix for EdiZon cheats.

 

[borngborn]

es patches arnt working for some reason

 

[Deleted User]

My system seems to crash whenever I enter the settings with Kosmos.

Is this a known bug?

 

[GuitarXxX]

I updated my Switch to V13 using Kosmos Updater and everything works fine.
Thanks again for all your hard work.

 

[Melcis]

Hi,

I updated my Switch to Kosmos v13 (tried today v13.0.1 and I got the same behavior) and it gets stuck on Kosmos logo when try to launch atmosphere CFW. My Switch details are:

• AutoRCM enabled
• Current HOS version: 6.2.0 (original version is 3.0.2 and i'm using AutoNoGC)
• Not using Emunand yet
• ES.patches added

The previous Kosmos version I installed was 12.2 and just works, I reverted to this version at the moment.

 

[alba93]

Hi,

I updated my Switch to Kosmos v13 (tried today v13.0.1 and I got the same behavior) and it gets stuck on Kosmos logo when try to launch atmosphere CFW. My Switch details are:

• AutoRCM enabled
• Current HOS version: 6.2.0 (original version is 3.0.2 and i'm using AutoNoGC)
• Not using Emunand yet
• ES.patches added

The previous Kosmos version I installed was 12.2 and just works, I reverted to this version at the moment.

same issue as you
After injecting fusee primary i succeeded in launching atmosphere

I'm on FW 6.2 as you and Fuzzy-v and we all meet the same problem.
Maybe a bug related to this firmware

 

[envirotech]

I finally (after a day of testing) got my switch updated and running properly on Kosmos V13. First I made the same mistake as many here, and tried to update with Kosmos Updater in homebrew. Was on Firmware 6.2, Kosmos 11.7 (fusee-gelee on Auto-RCM) prior to updating. Freeze/Hang on the AtlasNX/Kosmos splash screen. What I finally figured out was to

• revert back to the latest functioning Kosmos version (and appropriate corresponding Hekate version). When changing Kosmos versions from the Github zips, be sure to first clear everything off your SD except for the 'Nintendo' folder (that is where all the installed switch games are kept). For me V12.x all worked.
  
• Download ChoiDujourNX and find your desired firmware files (I went all the way to 8.1).
  
• Get into homebrew channel (note: you must hold R button while selecting Album in order to access HB channel in Kosmos V12).
  
• update the firmware version with ChoiDujourNX (I went to 8.1, but tested 7.0.1 and it seemed to work too).
  
• Then after successful firmware update, update to Kosmos v13.

Back in business now.

 

[rufuszombot]

I just started using Kosmos today with the new update, as well as the updated Hekate and now some of, but not all of my games won't load. Is this a known issue? My games were working just fine last night with Hekate 5.0 and atmosphere 9.1.

 

[jmrodrigues]

I just started using Kosmos today with the new update, as well as the updated Hekate and now some of, but not all of my games won't load. Is this a known issue? My games were working just fine last night with Hekate 5.0 and atmosphere 9.1.

Do you have signature patches?

 

[rufuszombot]

Do you have signature patches?

I did, but then I forgot I did a clean install of Kosmos/Atmos. This was the problem.

 

[Jiro2]

deleted

 

[alba93]

I finally (after a day of testing) got my switch updated and running properly on Kosmos V13. First I made the same mistake as many here, and tried to update with Kosmos Updater in homebrew. Was on Firmware 6.2, Kosmos 11.7 (fusee-gelee on Auto-RCM) prior to updating. Freeze/Hang on the AtlasNX/Kosmos splash screen. What I finally figured out was to

• revert back to the latest functioning Kosmos version (and appropriate corresponding Hekate version). When changing Kosmos versions from the Github zips, be sure to first clear everything off your SD except for the 'Nintendo' folder (that is where all the installed switch games are kept). For me V12.x all worked.
  
• Download ChoiDujourNX and find your desired firmware files (I went all the way to 8.1).
  
• Get into homebrew channel (note: you must hold R button while selecting Album in order to access HB channel in Kosmos V12).
  
• update the firmware version with ChoiDujourNX (I went to 8.1, but tested 7.0.1 and it seemed to work too).
  
• Then after successful firmware update, update to Kosmos v13.

Back in business now.

since you succeeded in fixing the problem by updating your firmware to 8.1, it tends to prove that there is a bug with firmware 6.2.
In addition all those who met this issue are/were on this firmware version

 

[Melcis]

Hi,

I updated my Switch to Kosmos v13 (tried today v13.0.1 and I got the same behavior) and it gets stuck on Kosmos logo when try to launch atmosphere CFW. My Switch details are:

• AutoRCM enabled
• Current HOS version: 6.2.0 (original version is 3.0.2 and i'm using AutoNoGC)
• Not using Emunand yet
• ES.patches added

The previous Kosmos version I installed was 12.2 and just works, I reverted to this version at the moment.

I finally (after a day of testing) got my switch updated and running properly on Kosmos V13. First I made the same mistake as many here, and tried to update with Kosmos Updater in homebrew. Was on Firmware 6.2, Kosmos 11.7 (fusee-gelee on Auto-RCM) prior to updating. Freeze/Hang on the AtlasNX/Kosmos splash screen. What I finally figured out was to

• revert back to the latest functioning Kosmos version (and appropriate corresponding Hekate version). When changing Kosmos versions from the Github zips, be sure to first clear everything off your SD except for the 'Nintendo' folder (that is where all the installed switch games are kept). For me V12.x all worked.
  
• Download ChoiDujourNX and find your desired firmware files (I went all the way to 8.1).
  
• Get into homebrew channel (note: you must hold R button while selecting Album in order to access HB channel in Kosmos V12).
  
• update the firmware version with ChoiDujourNX (I went to 8.1, but tested 7.0.1 and it seemed to work too).
  
• Then after successful firmware update, update to Kosmos v13.

Back in business now.

Thanks @envirotech I liked your proposed workaround and did the same updating to 7.0.1 and worked.