Hacking RELEASE Latest FS and Acid Patches for Kosmos

  • Thread starter Thread starter HarukoNX
  • Start date Start date
  • Views Views 319,688
  • Replies Replies 505
  • Likes Likes 57
Status
Not open for further replies.
Last edited by Tokiwa,
Ok, I am starting to get confused with so many versions out there.

I have an unpatched 4.1 switch, from which I installed Hekate 4.2 and was playing some NSPs installed in my SD card through a kosmo/atmosphere with sigpatches. I am locked into playing games up to 4.1 FW.

I followed the NH switch hacking guide to create an EmuNAND that I can update with ChoijoudourNX to 9.2 (or 10.0 if necessary) and that I can run sigpatches and use a NSP installer to play newer games.

What would be my best choice of a clean CFW, with what sigpatches and using tinleaf (don't like the waifu nonsense of the Awoo installer)?
 
What would be my best choice of a clean CFW, with what sigpatches and using tinleaf (don't like the waifu nonsense of the Awoo installer)?
There is an option to remove her on Settings menu: Remove Anime.

I don't like her as well...
 
  • Like
Reactions: Mar2ck
Sure I can add that. Seems easy enough.

Edit: Go ahead and give this a shot, as I don't have DevMenu to test.

Thank you for those changes. :bow:

I already tried them on my side on FW 9.2.0, this is how I could be sure when I posted my second issue which was rejected on Atmosphere official Github. :shy:

However, since the FW 10.0.0 update, DevMenu doesn't work anymore: it doesn't stop with a "return to HOME" message (which is the case when this modification is not present), it just displays a black screen.
I think this new problem is probably due to the fact that my DevMenu version is from SDK 6.0.1 and it's not compatible anymore with FW 10.0.0 (there was a similar issue with DevMenu from SDK 5 under FW 6.0.0).
To be sure about this theory, we have to hope for a leak of the latest SDK. But, one thing is sure: with this new code "if not under development unit, return invalid", even latest DevMenu version won't work. ;)
 
Last edited by OperationNT,
My patches are just for Kosmos or if you are using Atmosphere with Hekate.
firstly thanks for your work on this. It is very much appreciated during this time.

so should i undo the changes that i made to kosmos with =>


"kip1patch=nosigchk
kip1=atmosphere/kips/*"


I didnt revert back to changing the .ini file just applied the "patches" folder to root and eveything works

thankyou
 
Last edited by Slim45,

Your hekate_ipl.ini should look something like this, mine may be a bit different as I don't use Kosmos:

Code:
[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=0
autonogc=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
kip1=atmosphere/kips/*

[CFW (emuMMC)]
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
kip1=atmosphere/kips/*

[Stock]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
 
  • Like
Reactions: Lupla and Slim45
ok so, im trying this patches now and games work fine, homebrew too, but i can't get emuiibo to work, seems like some sys module causes a crash
 
Your hekate_ipl.ini should look something like this, mine may be a bit different as I don't use Kosmos:

Code:
[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=0
autonogc=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
kip1=atmosphere/kips/*

[CFW (emuMMC)]
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
kip1=atmosphere/kips/*

[Stock]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
thank you:)
 
My patches are just for Kosmos or if you are using Atmosphere with Hekate.

It also works with vanilla Atmosphere (using "fusee-primary") as it automatically loads modules in "/atmosphere/kips" (and override internal ones when the name matches).
But, of course, "loader" patches must be removed: no need to patch something that is already "fixed" by source code modifications and recompilation :).
 
Last edited by OperationNT,
  • Like
Reactions: HarukoNX
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum