so if ya downgrade sysnand you cant boot it without hekate then cause your fuses are burned due ya boot without hekate
That's how Tegra should behave....are you sure it's not in CFW? Check system settings and see what the firmware says. If you see atmosphere boot logo I can't imagine you're not in CFW
Right now, as far as I can tell, Sigpatches still don't work for 17.0.0, so I wouldn't go over 16.1.0 just yet.Basically, i have an ofw with latest firmware and an emunand with an old firmware. I'm afraid or bricking my switch, so i didn't try anything, and now im reading that its not possible to boot cfw from emunand if you have the latest firmware, or that you can boot but would not be able to do anything because of sigpatchs. I'm fucked? Can I use CFW? what should i do?
thank you very much, this was the response i needed. i did all that in less than 20min, and it was flawless, now i can try mario wonder with my brother tomorrow one week earlier than expected. thank you so muchRight now, as far as I can tell, Sigpatches still don't work for 17.0.0, so I wouldn't go over 16.1.0 just yet.
Provided you can boot into CFW emuNAND, you should update Hekate, grab latest stable Atmosphere (not pre-release) and Sigpatches for FW 16.1.0 and Atmosphere 1.5.5 and upgrade your emuNAND's firmware to 16.1.0 via Daybreak (I believe we aren't allowed to link to the files you need so you'll need to find them by yourself, it shouldn't be too hard).
Super Mario Wonder works just fine on 16.1.0 as far as I can tell, so there's no need to update to 17.0.0 for now unless you know what you're doing.
Hope that helps.
THX!Alright next we're gonna try something a little different. Have you ever heard of Maintenance Mode? Its fine if you haven't. What you're going to do is turn off your console if it isn't powered down already. Then you're going to turn it on but as you're turning it on, you're going to hold down the volume + and - buttons. If successfully executed, you will enter Maintenance Mode. From here, there is nothing else you need to do. Simply exit or turn the console off then try launching or installing the games again.
Right now, as far as I can tell, Sigpatches still don't work for 17.0.0, so I wouldn't go over 16.1.0 just yet.
Provided you can boot into CFW emuNAND, you should update Hekate, grab latest stable Atmosphere (not pre-release) and Sigpatches for FW 16.1.0 and Atmosphere 1.5.5 and upgrade your emuNAND's firmware to 16.1.0 via Daybreak (I believe we aren't allowed to link to the files you need so you'll need to find them by yourself, it shouldn't be too hard).
Super Mario Wonder works just fine on 16.1.0 as far as I can tell, so there's no need to update to 17.0.0 for now unless you know what you're doing.
Hope that helps.
Right now, as far as I can tell, Sigpatches still don't work for 17.0.0, so I wouldn't go over 16.1.0 just yet.
Provided you can boot into CFW emuNAND, you should update Hekate, grab latest stable Atmosphere (not pre-release) and Sigpatches for FW 16.1.0 and Atmosphere 1.5.5 and upgrade your emuNAND's firmware to 16.1.0 via Daybreak (I believe we aren't allowed to link to the files you need so you'll need to find them by yourself, it shouldn't be too hard).
Super Mario Wonder works just fine on 16.1.0 as far as I can tell, so there's no need to update to 17.0.0 for now unless you know what you're doing.
Hope that helps.
Is it safe to downgrade via cfw sysnand? Since I can't acess emunand (Failed to apply nosigchk)?
Post automatically merged:
Is it safe to update via cfw sysnand? It's the only way for me, since I can't acess emuNAND (Failed to apply nosigchk)
ERROR
An error ocurred attempting to install the NSP:
Error: 2145-0001 (0x291)
Hello, I'm trying to install .nsp game files in Goldleaf. I get a similar message every time.
Any ideas what is going on? Should I try a different method?
I got an error when trying to launch Atmosphere, and idea what went wrong? See attached error report.
I got an error when trying to launch Atmosphere, and idea what went wrong? See attached error report.
"
Panic occurred while running Atmosphere.
Title ID: 010041544D530000
Error: std: :abort (0xFFE)
"
Like Hayato213 said, just wait for a proper release of Atmosphere and working sigpatches, update your SD card contents and you'll be good to go. Downgrading sysNAND is not a good idea. It probably won't even work as far as I know, I only update my emuNAND whenever it's 100% safe to update (i.e. when Hekate, Atmosphere and sigpatches are working properly).Is it safe to update via cfw sysnand? It's the only way for me, since I can't acess emuNAND (Failed to apply nosigchk)
But you think it's safe to downgrade EmuNand?Like Hayato213 said, just wait for a proper release of Atmosphere and working sigpatches, update your SD card contents and you'll be good to go. Downgrading sysNAND is not a good idea. It probably won't even work as far as I know, I only update my emuNAND whenever it's 100% safe to update (i.e. when Hekate, Atmosphere and sigpatches are working properly).
But you think it's safe to downgrade EmuNand?
FAT32, with SD Partition emuMMC.