Delete and copy the new folders. Make sure you keep your BCT.ini settings if you have edited it. Also keep your hekate_ipl.ini file if you boot with hekate.
So do I delete the old "atmosphere" folder along with the "automatic_backups", "exefs_patches" and "kip_patches" folders?
You can delete the patches if you have updated the firmware of your switch which needs new sigpatches. I am not sure what the "automatic_backups" folder is for... I don't have this one.
My switch is unpatched, before i update to 8.1 could you tell me if i do that that means my firmware on sysnand and emu will change for 8.1?
How about booting on stock after cfw is that will cause burnt fuse?
I don't know how it got created either.
Anyway, I'm going to update SYSNAND to the latest firmware while keeping EMUNAND at 8.1.0.
Should I hold on to those patches then?
how can i downgrade to 6.2.0 i got 9.0.1... I lost my old nand backup and at the moment i cant boot into the ofw or even cfw cos of boot0 and boot1 are messed up. i got 8 fuses burn... any one can help me.. i got the keys i tried used choidujuour pc version but when im fiiling up the prodinfo give error with my biskey
Okay, thanks!
Btw, since we're on this topic, I was told the safest way to update SYSNAND, without burning fuses or risking a ban from online, was to load in with fusee_primary.
But I wasn't able to find info on this process. Do I enter RCM and inject fusee_primary, or choose "Payload" in hekate and launch fusee-primary from there?
I'm asking because I've only ever used the hekate payload through TegraRCMGUI.
No, don't boot with fusee primary to SysNAND. It won't be clean anymore. The best way would be this one: https://gbatemp.net/threads/an-easy...ch-firmware-without-burning-any-fuses.511847/. Make sure to follow every step or you will burn fuses.
I was going to do it that way, but Lacius was telling me to do it the fusee-primary way...
This is probably more than obvious, but I just wanted to confirm it regardless:
Burning fuses up to the latest firmware would result in emuNAND not being able to boot lower firmware, correct?
Burning fuses up to the latest firmware would result in emuNAND not being able to boot lower firmware, correct?
Why would you want to downgrade?
No
Assuming you are using Fusee Gelee to lauch emuMMC, then the number of burnt fuses is irrelevant as all custom bootloaders bypass the fuse check and you cannot boot emuMMC without a custom bootloader.
Nothing would fail. You are able to boot to OFW SysNAND because you have burnt fuses up to your SysNAND firmware and you are also able to boot to CFW EmuNAND with lower firmware because the fuse check is ignored by custom boot loaders.
SX user here, I have updated twice using Choudijour with no issues but am nervous about going from 8.1 to 9.X mainly due to gc slot and fuse issues. I don’t understand anything about patches/sigpatches either. I also know there’s no games currently requiring 9.X but just trying to think ahead to future releases.
I'm sorry, I meant to write "only a lower OFW SYSNAND than the burnt fuses would fail to boot".
-
@ HiradeGirl:
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
NinStar:
quite ironic that brawlhalla has a far superior netcode compared to smash bros ultimate while offering free online play with crossplay support -
