just to confirm again, there won't be any problem if i restore from the "partial" backup (i.e.BOOT0/BOOT1 and eMMC SYS), that is, to restore cfw sysnand to a clean state sysnand with the partial backup (besides losing user save/game data)?Technically you are correct as eMMC USER only contains save and game data.
- You don't have to turn off the console to boot into sysMMC with Hekate
- Yes
- Yes since the save data is stored within the internal memory
Technically you are correct as eMMC USER only contains save and game data.
- You don't have to turn off the console to boot into sysMMC with Hekate
- Yes
- Yes since the save data is stored within the internal memory
The gamecard slot has its own updates introduced in firmware 4.0 and 9.0 that once applied prevents it from being used on firmware versions below the one it was installed from. To update your firmware, you can use the homebrew application ChoiDujourNX. To update your CFW, simply download the latest boot.dat from TX's website. I wouldn't say the latest firmware is stable with SX OS as it still relies on a beta but firmware 9.2 is plenty stable.
Depends on what you are doing and how many sysmodules you have running.
Switch back to using ReiNX.
What do you mean?Damn even new reinx won’t let me play retroarch flycast. Just did a fresh install any suggestions to how play flycast?
OFW is your firmware. CFW are just the files you put on your SD card. CFW is not a firmware. Different versions of CFW support different firmware versions but booting different versions of CFW do not boot different firmware versions. Also ChoiDujour only supports up to firmware version 6.1. Lastly, while on their site they state it only supports up to 10.1, 10.2 is so incredibly similar to 10.1 that a new update was not needed.so i forgot a little. i have to update the ofw cia choidujour and also the cfw or are they linked? i thought it was possible to have different firmwares on both?
and i saw the newest ofw is 10.0.2 but the latest sx beta says support only to 10.0.1?
i really just want to have the ofw to the latest to play some smash online again...
just to confirm again, there won't be any problem if i restore from the "partial" backup (i.e.BOOT0/BOOT1 and eMMC SYS), that is, to restore cfw sysnand to a clean state sysnand with the partial backup (besides losing user save/game data)?
Technically you are correct as eMMC USER only contains save and game data.
What do you mean?
Well hold on, why would you use such a low version of ReiNX? That is more likely to be the source of your issue.installed 1.6 reinx and flycast just crashes. I give up.
Unfortunately there is no tool that can display the gamecard reader's fuses. Also you can only use one controller per console.I can use bricmii to know the number of antidowngrade count, but is there any way to have the same kind of count for the gamecard reader?
Also, can I use one pro controller on multiple consoles? Or do I have to switch (pun unintended) between them?
Kosmos is Atmosphere and SDSetup can basically provided the same package as Kosmos but with a different name (its the first option from the left). You can either switch to using SDSetup or downloading vanilla Atmosphere.I've been using the Kosmos/hekate method for Atmosphere. Now that Kosmos updates are done, I'm wondering If I should "get rid of" Kosmos and reinstall vanilla Atmos. Not using emuMMC either.
I don't care about using Tinfoil, is there any point for me "reinstalling" atmosphere? I'd like to update to AMS 0.12 soon, so just get the 'minimal' package from SDsetup and copy/paste to update Atmos? No need to worry about kosmos stuff?
Draxzelex, you really are a legend. Been reading this thread backwards for several pages looking for an answer to my question and you basically run this thread! Found an answer where you said you don't need to delete anything to get rid of Kosmos. Sorry if this was a dumb post but I want to be sure I understand.
Sounds like you constantly remove the SD card from your console which can damage the SD card reader in the Switch.Any one else have issues with their sd card. I have read its usually a hardware problem which it looks like to me. I can load atmosphere and it can be running smoothly for any period of time and suddenly I will get the sd card error message mid game and will have to power off and reboot to atmosphere. The only thing in my mind is I have updated a number of times by dragging the updated files in and letting them replace their existing counterparts. Is there any chance this repeated process over a number of updates has caused a bug? Just really hoping I don't have to mess with the sd card slot.
Just keep everything (cores, RA itself and your CFW) up to date, that's all. You can configure/remap controls as you want inside RA.finally, just updated everything and got flycast to work. Is there more packages im not aware of that improves the graphics or performance? Or joypad profiles to dl? Just happy to get it to work finally!
i’m on 1.8.4 RA
Unfortunately there is no tool that can display the gamecard reader's fuses. Also you can only use one controller per console.
Kosmos is Atmosphere and SDSetup can basically provided the same package as Kosmos but with a different name (its the first option from the left). You can either switch to using SDSetup or downloading vanilla Atmosphere.
Sounds like you constantly remove the SD card from your console which can damage the SD card reader in the Switch.
everything you mentioned works in vanilla atmosphereusing neutos atm, cheats on edizon show for some games and not others though, i have checked all the title id's and BID's and they match yet still some games are missing, tried installing tesla overlay and using that way but it crashes the switch on payloaad send, is there any way to use normal atmosphere, with tinfoil and get tesla overlay to work or the cheats in edizon to work properly?
Just reinstall all your cfw files from scratch (and don't install that one sys module that was the cause of your issue this time).Installed a few things today. Sys-clk, an app for an available updates list, sys-clk editor, tesla menu and sys-clk plugin for it, and a thing called autopower or auto reboot. Something like that. Went to use the last one to restart the switch and now it is 'bricked.' By bricked I mean that Atmosphere will not load. I can get to rcam and hekate ok but loading atmosphere will just basically turn off the switch or at least put it in a state that seems off. I do not have emummc. Any help?
Just reinstall all your cfw files from scratch (and don't install that one sys module that was the cause of your issue this time).