yes, i have updated those, also now it doesnt turn onDid you update the sigpatches and also hekate? All must be updated every time you update.
i have used hekate but it doesnt load and i have used my physical rcm to get into rcm mode but it doesnt let me inject the payloadYou're not supposed to be able to turn it on unless you send the payload through TegraRCM for Hekate or fusee.bin. It's black screen waiting for one of the payloads to be sent. You're using AutoRCM, thus you msut hack your Switch each time you boot it. When you get it up and running I would use sleep mode if you don't want to send the payload all the time.
nothing, it doesnt load me to hekae, it doesnt even let me inject the payloadThe only explanation is that you didn't update something, Hekate Atmosphere or patches.
What happens when you try to send the payload?
nothing, it doesnt load me to hekae, it doesnt even let me inject the payload
usb c cableThen something is wrong with your injection method. Are you using a type-c cable through your computer or one of those handheld RCM devices?
what do you mean to copy the patches inside atmosphere
WAIT, so you have to do more steps than just swapping out the old files with the new files?Also you're sure you properly updated to 19.0 you used Daybreak or another method and they fully installed and told you to reboot correct?
Post automatically merged:
The sigpatches that you said you already installed when I asked you before. They are on this site.
https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
I would read the entire first post on that link for further instructions. It seems some changes have been made for 19, since I'm on 18.1 I can't help you further. Ask on that thread for further assistance.
WAIT, so you have to do more steps than just swapping out the old files with the new files?
WAIT, so you have to do more steps than just swapping out the old files with the new files?
Post automatically merged:
also do i have to copy the files inside the atmosphere folder or the root of the sd
well tell me what more information so i can post it0100000000000005 is often a sys module, you really need to write out more of the error page. I bet its a Tesla plugin