You're saying that installing "brick" in """EmuNAND""" would still brick your NAND?No, there is no lazy way to prevent stuff like that. Also the tinfoil brick is CONJECTURE at best. There is no magical lazy way to prevent something from bricking your system, the only way is for the user to not be stupid and don't run anything on their system that isn't verified
Thanks for your comments.No, there is no lazy way to prevent stuff like that. Also the tinfoil brick is CONJECTURE at best. There is no magical lazy way to prevent something from bricking your system, the only way is for the user to not be stupid and don't run anything on their system that isn't verified
exactly!!You're saying that installing "brick" in """EmuNAND""" would still brick your NAND?
Yes that's exactly what it's for. If you brick your emunand then boot into your nand and make a new "emunand".Thanks for your comments.
But emunand and sysnand work separately, is not it? So in theory if I use the emunand and brick it, I would have the sysnand preserved. If not, what real use would the SX OS emunand have?
tks
--------------------- MERGED ---------------------------
exactly!!
Yes, if you brick your emunand you can still boot in your sysnand fine or you can simply recreate it from sx boot menu. You will lose all not backed up saves though.Title question guys.
tks.
Anything running in the EmuNAND has no access to the actual NAND, silly. Stop huffing the Atmosphere koolaid.SX emunand will NOT protect you from everything.
(Next atmosphere version will)
This is why it's insane not to use emunand and ergo sxos.
SX emunand will NOT protect you from everything.
(Next atmosphere version will)
Anything running in the EmuNAND has no access to the actual NAND, silly. Stop huffing the Atmosphere koolaid.
None of this makes any sense. Its a corrupted NSP version of the games that are causing the bricks. Common sense would be just to avoid the damn NSP version of the game. XCI in one hand and NSP in the other, why install a NSP, especially one that is unverified.
It makes a copy inside the emunand. Nothing is touched in your normal sysnand. If it didn't protect you then it would be completely pointless. However this needs to be verified. Nobody can claim 100 percent weather it works or not without actually testing it. First you'd have to make a current Nand backup of course. Who's up to the challenge?Could we stop with the tribalism? Especially as it's probably false information.
It's very questionable that the emunand of SX OS would have protected you from a brick through the fake pokémon release.
According to to this research here the emunand is created by copying your USER partition.
The fake release damages your PRODINFO partition among other possible partitions. So how is going to safe you, that you are running a copy of your USER partition?
Stop plugging your favorite OS on every possible occasion. It's such nonsense. You're spreading false information that new users will believe, if they see it repeated often enough.
Matter of fact: Neither SX OS or Atmosphere will miraculously safe you. Even if Scires apparently tries to help out.
This is a common missunderstanding here. The problem doesn't start when you install the fake game through the nsp. The problem starts when you run it.
Malcious codes needs to be executed. This can happen through nsp, xci or a payload. Don't let yourself be fooled by just format.
It makes a copy inside the emunand. Nothing is touched in your normal sysnand. If it didn't protect you then it would be completely pointless. However this needs to be verified. Nobody can claim 100 percent weather it works or not without actually testing it. First you'd have to make a current Nand backup of course. Who's up to the challenge?
I don't use sx-os emunand because I dislike the idea of messing with my nand to begin with. But if what you're saying is correct then sx-os emuand solution really is pretty useless at protecting your Nand. Hopefully this pikabrick fiasco leads TX to create a real sd emunand solution.According to the linked research, emunand resides inside of one or more files. Those files saved on your regular USER partition.
This is important, as it states that only one partition is duplicated and then used as your USER partition.
So now let's have a look at a raw dump of a Switch nand:
So to keep it simple, the emunand is apparently a copy of your original USER partition. Although it is shrunken down to save space.
Now you run the malware and it's writing garbage data to your PRODINFOand SYSTEM partitions.
Those two partitions were not duplicated beforehand. There are now gone. How can anything, expected a backup, save your from this situation?
So no, I have to disagree with your claim. It doesn't need to be tested to be proven. You can also deduct an outcome by looking at the facts you happen to know.
I don't use sx-os emunand because I dislike the idea of messing with my nand to begin with. But if what you're saying is correct then sx-os emuand solution really is pretty useless at protecting your Nand. Hopefully this pikabrick fiasco leads TX to create a real sd emunand solution.
I don't use sx-os emunand because I dislike the idea of messing with my nand to begin with. But if what you're saying is correct then sx-os emuand solution really is pretty useless at protecting your Nand. Hopefully this pikabrick fiasco leads TX to create a real sd emunand solution.
That's bullshit. It's the same system/PRODINFO/... partition. Try to launch the bricker if it's sooo safe.Anything running in the EmuNAND has no access to the actual NAND, silly. Stop huffing the Atmosphere koolaid.