They are not recognized...afaik.Can games installed with Atmosphere also be played with OFW or are they not recognized?
installed games with atmosphere need sigpatches to run. in ofw you cant apply the sigpatches b/c you dont have cfw. will likely say "insert cartridge" in ofw if you installed games to a cfw-sysnand.Can games installed with Atmosphere also be played with OFW or are they not recognized?
I've been away a while.
I'm currently on FW 9.1.0|AMS 0.10.1 and would like to update to 13.2.0 to use the bluetooth audio feature and play some of the newer games. My Switch hacking expertise is pretty obsolete though as I'm noticing a lot of newer stuff in current walkthroughs that my older setup doesn't have.
Can someone provide (or point me to) a step-by-step on the exact method I should follow for making a big leap between firmwares? I've gone as far as downloading the 13.2.0 firmware, newest Atmosphere, newest sigpatches, newest tegra, and hekate (which I've never used before). But, I've taken no steps other than backing up my entire SD card. I don't want to end up with a brick.
installed games with atmosphere need sigpatches to run. in ofw you cant apply the sigpatches b/c you dont have cfw. will likely say "insert cartridge" in ofw if you installed games to a cfw-sysnand.
Thank you so much,i asked why they asked me,i only use atmosphere to start games and i didn't know this thing.They are not recognized...afaik.
yesis your switch system settings clock is set to automatic?
Thanks for your help.If you're not using partition-based emuMMC, you can copy everything from one SD card to the other. If you are using partition-based emuMMC, you can still copy everything over but you will also have to dump your emuMMC then flash it into the new SD card. Hekate can do this for you.
Following the guide @binkinator linked to upgrade Atmosphere (from 0.10.1 to 1.2.5), I've ran into a couple things I wanted to check on before continuing;https://rentry.org/SwitchHackingIsEasy
This page specifically:
https://rentry.org/MigrateToAtmosphere1_0_0
Then upgrade your FW
https://rentry.org/UpgradeDowngrade
Following the guide @binkinator linked to upgrade Atmosphere (from 0.10.1 to 1.2.5), I've ran into a couple things I wanted to check on before continuing;
There was no fusee-primary.bin file to my bootloader/payloads folder to delete.
And on the last step, overwriting contents of hekate_ipl.ini file in the bootloader folder with one of the following configurations... no such file exists in this folder at all.
I've followed the guide in every detail aside from these two steps which could not be completed. Am I clear to move on, or does the hekate_ipl.ini file have to be in the bootloader folder, and if so, how do I get it there?
Thanks guys for all the support and advice. I've reinstalled the latest sig patches and Tinfoil is working with the shop now. I could add a shop easy this time and I can see all the games there but I have a problem with the installation of the game now. When I start the game installation, it stops or sometimes doesn't even start. The installation counter is stuck at 0% and disappears after a while.
I've gotten everything moved over to the SD card. Firmware is ready to be upgraded. Only question I have at the moment is I normally boot into Atmosphere by injecting a fusee-primary.bin payload via TegraRcmGUI (2.6). Will this still work after the changes I've made?If you don’t have them then you’re set! The point is to make sure they are replaced completely with the new files. Not removing old files can cause problems and makes troubleshooting harder. Onward! You’re almost there…
I've gotten everything moved over to the SD card. Firmware is ready to be upgraded. Only question I have at the moment is I normally boot into Atmosphere by injecting a fusee-primary.bin payload via TegraRcmGUI (2.6). Will this still work after the changes I've made?
Ah, I see. I was able to get in using fusee.bin and ran the update. Seems to have worked. Testing now. I do see the bluetooth audio feature now in the settings, which was the main lure for me to do this. Thank you for pointing me in the right direction and answering my questions.You should probably update to the new fusee.bin while you’re at it.
I personally inject hekate.bin (which is just a renamed copy of hekate_ctcaer_x.x.x.bin). Since you’ve followed the guide this far I recommend injecting helate.bin but it’s easy to try both.
I do Hekate so I can interrupt the boot and use the Hekate/Nyx tools, boot other payloads, etc, etc.
Ah, I see. I was able to get in using fusee.bin and ran the update. Seems to have worked. Testing now. I do see the bluetooth audio feature now in the settings, which was the main lure for me to do this. Thank you for pointing me in the right direction and answering my questions.
I've never used Hekate before, but I like what I've seen of it. There's so much new info and utilities in the two years I've been content with FW 9.1.0. Am I interpreting things right when I see that it is now possible to have your Switch connected to the internet without getting banned by Nintendo? I'd love to put my Switch on my wifi network and use the themes installer, but back when I was actively modding this thing the holy grail was never connect it to the internet.
Thanks again for your help. Things seem to be working, although the Switch isn't finding my Sony earbuds.Awesome!
Yeah, Hekate is it’s own rabbit hole to dive into. Topic for another time.
As for ban risks, it’s kinda like risk reduction, rather than 100% prevention. The only safe switch is a completely unmodified switch. Anything you do with a CFW afterwards introduces some amount of risk. I’ve had good luck being online with exosphere which gives me a blanked out prodinfo and a hosts file that prevents me from hitting most (known) Ninty servers. I use themes and Themezer and tinfoil shops. It’s worked GREAT for me so far but YMMV. Chose your own risks wisely.