I want to update my sysnand and emunand to 6.1.0. I read earlier that for updating from 6.0 to 6.0.1 you can just backup boot0 then update sysnand then restore boot0. Is that still true for 6.1? and i think for emunand i can just update offline using choidujournx. Also anyone know what new telemetry is in this new update?
If you have emunand why would you update your sysnand too? The entire point of emunand is to keep your sysnand at a lower version
The entire point of emunand on SX os is to play games online which usually requires updating to the last fw.
No you need to go online in Sysnand (emunand will get you banned for too-small-partition, NSP installs, etc.). Hence the desire to update sysnand while maintaining the emunand as-is if possible.
Last edited by stewacide,
The POINT of Emunand is to keep that updated to the latest OFW version and SUPPOSEDLY safely play online(I say supposedly because there hasn't been enough concrete proof that it's safe) while you keep your sysnand at a lower version in case a untheared coldboot solution comes along(Which most likely wont). As suchm updating both Sysnand and "emunand" makes no sense
You got the facts wrong, most people play legit ofw online and use emunand for homebrew and warez without connecting to Nintendo. There is no point in updating emunand if it is not needed by a game that you use but sysnand has to be on latest to play online/use the eshop.
Most sx users are quite happy with RCM coldboot, waiting for untethered coldboot/warm boot is mostly pointless unless you find jig/autorcm and dongle very annoying.
emuNAND is not safe to go online on and these misconceptions are why people are getting banned when using it.
emuNAND is no different from regular sysNAND CFW, it has the same ban risks, the only difference is that you can keep your CFW and homebrew stuff separate from OFW, so sysNAND can't see what you're doing in emuNAND and in theory there's no way for Nintendo to tell that you've been doing anything they don't like, and because the two are completely separate it allows you to have different firmware versions on them, but the only reason to do that would be to keep sysNAND on 4.1.0 or below so you can use the warmboot exploit in the future, which means sacrificing online. As soon as you go online in emuNAND that all goes out the window because the system will phone home.
So you can have online, or you can have future warmboot, but you can't have both because booting sysNAND without burning fuses or going online on emuNAND would result in a ban.
Last edited by The Real Jdbye,
I think you misunderstood what TX meant, I'm pretty sure they meant you could go online in sysNAND.
Similar threads
