Or all of themno, you either gotta boot atmosphere with hekate using fsso, use a modified version of atmosphere that enables kips, or you gotta use sys-patch
Or all of themno, you either gotta boot atmosphere with hekate using fsso, use a modified version of atmosphere that enables kips, or you gotta use sys-patch
sys-patch was't working anymore for me on 18.0 and latest ams (games was unable to start), so i just manually downloaded the kip sigpatch and now everything workYou can NO LONGER use OFFICIAL Atmosphere with signature patches. They're no longer supported.
You HAVE TO USE Hekate or Sys-Patch
Guide for how to setup Sys-Patch (interface requires Tesla on your Switch)
https://www.gamebrew.org/wiki/Sys-patch_Switch
Borrowing from @impeeza hekate_ipl.ini file
Your hekate_ipl.ini need this to launch with Patches via Hekate
Code:[config] autoboot=0 autoboot_list=0 bootwait=0 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [CFW - sysMMC] fss0=atmosphere/package3 kip1patch=nosigchk atmosphere=1 emummc_force_disable=1 icon=bootloader/res/icon_payload.bmp [CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 atmosphere=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp
Yeah sys-patch have been updated to work with the latest version. It's on the Cat sitesys-patch was't working anymore for me on 18.0 and latest ams (games was unable to start), so i just manually downloaded the kip sigpatch and now everything work
not sure what cat sit refer to, but eh, i thought the project was dead due to the recent dmcaYeah sys-patch have been updated to work with the latest version. It's on the Cat site
and here on the sys-patch thread there is a link to: https://gitflic.ru/project/impeeza/sys-patch/releaseYeah sys-patch have been updated to work with the latest version. It's on the Cat site
I tried and can connect the switch to wifi with internet connection not turned on, this is the point of the patch.
Bootlogo lockup normally have nothing to do with sigpatches, maybe a currupted SDCard or emunand, can you boot in to OFW?I can't get past the switch logo when booting atmosphere, I've updated the sigpatches, atmosphere and hekate and I also have 18.0 on the switch (don't know if that matters), I'm pretty sure I'm booting trough fs0 but i tried the modified fusee.bin and ended up the same. Is it bc the sigpatches are not for atmosphere latest version? Can anyone help me pls?
The color will not change once it works and stays working. The logs don't get completely rewritten every time you boot. Delete your logs and see what color it is. Your "belief" doesn't negate reality.I don't believe that and I've already explained why several times over. For the last time.... If using both sigpatches and sys-patch, the sys-patch overlay should show ctest in orange.
The color will not change once it works and stays working. The logs don't get completely rewritten every time you boot. Delete your logs and see what color it is. Your "belief" doesn't negate reality.
because you turned the setting off. Now, didn't I start off with "As long as they are working and STAY WORKING"? Before the repo went down, there was an issue about this very thing. Deleting the logs was the solution.You're late to the party. This has already been discussed and cleared up. Also, the log does in fact change at boot. If you turn patches off in the setting and reboot, the log will reflect that. Soooooooo.... yeah.
EDIT: Or maybe I'm not getting enough sleep. I seem to have completely missed the replies from duckbill007 and iTotalJustice
Yeah, OFW works fine, but i can't get to CFW, I think i've had this problem before but i don't remember how I solved itBootlogo lockup normally have nothing to do with sigpatches, maybe a currupted SDCard or emunand, can you boot in to OFW?
Try to backup and remove the /atmosphere/config folder and try to boot CFWYeah, OFW works fine, but i can't get to CFW, I think i've had this problem before but i don't remember how I solved it
Still freezes at the logoTry to backup and remove the /atmosphere/config folder and try to boot CFW
test your card may be is corrupted.Still freezes at the logo
Sorry for jumping in without going back to find out... but are you launching with a game cart inserted? Does removing it make a difference? I mean... since you've booted OFW, it shouldn't really matter, unless your emummc is a really old version (using sxos would be the only reason I can think of to do that). And another thing, that I don't think I've heard of locking at the boot logo, but rather triggering a crash early after startup, would be having your serial number blanked in CFW, while not having the proper servers blocked in the hosts file...Still freezes at the logo
Your problem is in your emuNAND its corrupted, you can either opt to fix it or generate a new one.Still freezes at the logo