Hacking Discussion SX EmuNAND is not real EmuNAND.

[Creatable]

SX OS EmuNAND is not EmuNAND.
Let me explain what I mean.
SX OS EmuNAND does not emulate the NAND, instead it resizes your original nand, and then makes a new partition where it copies stuff from your main partition.
Now, real EmuNAND would emulate the NAND, by reimplementing functions to have the nand read from SD. This is not what Team Xecuter did.
This is essentially a dualboot.

So you may be asking "So what? It works, that's just some technical nonsense!"
Reasons why this is bad:
Having another NAND partition is NOT NORMAL. Nintendo can instantly detect this, and also instantly ban you.
This is essentially ban in 1 easy step.
This is also particularly bad because you cannot use the storage their "EmuNAND" takes up on original firmware.
One final issue, is that if your Switch dies while their "EmuNAND" process is going (while it's resizing your nand partitions) it will brick you.
EmuNAND is meant to avoid bricks and stop bans / allow you to update. This does the opposite of two of those things.

This method is also particularly easy to recreate, so no this was not something special from them.
Congrats on not stealing something for once TX, you made something that is a complete mess.

 

[altorn]

So why do you need a new thread about this?

 

[Creatable]

So why do you need a new thread about this?

To avoid bans or bricks.

 

[altorn]

To avoid bans or bricks.

How about posting it in that thread where most of the SX users (potentials) will read it easier?

 

[Creatable]

How about posting it in that thread where most of the SX users (potentials) will read it easier?

Already did that <3

 

[altorn]

yes... yes you did. sorry

 

[Deleted-442439]

Indeed, Nintendo has already had a system in place to detect this since 3.0.0, erpt includes a NANDTotalSize parameter in error reports, very very easy for Nintendo to detect this the second you boot into stock FW.

Be patient and wait for actual emunand people, not this dual boot dangerous nonsense.

Although TX actually made something original this time, its a mess and will cause more issues than it attempts to solve.

 

[Paulsar99]

I think having a separate topic is much more easier to see immediately about the dangers of sx os emunand.

 

[Cubuss]

Very cool how you know exactly how their emunand works by just reading the release notes,

You obliviously have no clue what you are talking about and just spreading propaganda against tx os

 

[Kubas_inko]

Very cool how you know exactly how there emunand works by just reading the release notes,

You obliviously have no clue what you are talking about and just spreading propaganda against tx os

Then tell us how are we wrong?
or even better. Tell us how the "emunand" really works?

 

[Deleted-442439]

Very cool how you know exactly how there emunand works by just reading the release notes,

You obliviously have no clue what you are talking about and just spreading propaganda against tx os

We know because you can already fucking download it, we know for a fact what it does, and we also know for a fact that the resize of the NAND will be detectable by stock HOS, this stuff is literally trivial basics.

 

[SpaceJump]

Is it actually confirmed that a new partition is created and Nand is resized? The release notes state "emuNand lives inside Nand...", which could also mean stored as copied files on Nand, couldn't it?

 

[Deleted-442439]

Is it actually confirmed that a new partition is created and Nand is resized? The release notes state "emuNand lives inside Nand...", which could also mean stored as copied files on Nand, couldn't it?

It is confirmed, people have already used the feature, it creates a new partition.

 

[Cubuss]

It is confirmed, people have already used the feature, it creates a new partition.

Who?

 

[SpaceJump]

It is confirmed, people have already used the feature, it creates a new partition.

Source? Edit: Ninja'd

 

[stewacide]

Is it actually confirmed that a new partition is created and Nand is resized? The release notes state "emuNand lives inside Nand...", which could also mean stored as copied files on Nand, couldn't it?

I'm thinking the same: if emunand is a disk image that lives in the normal userspace of an unmodified user partition then that would be OK (say, masquerading as a gallery image or something), but I doubt it.

 

[Cubuss]

99% people here on gbatemp are talking out there ass and have 0 clue what they are talking about they just trying to look cool by seeming they know everything about everything,
While they really know shit,

 

[Reploid]

Useless feature anyway. Just get your ban like a big boy and exhale with redemption.

 

[Kubas_inko]

99% people here on gbatemp are talking out there ass and have 0 clue what they are talking about they just trying to look cool by seeming they know everything about everything,
While they really know shit,

then prove it.

 

[Deleted-442439]

99% people here on gbatemp are talking out there ass and have 0 clue what they are talking about they just trying to look cool by seeming they know everything about everything,
While they really know shit,

You have demonstrated zero technical knowledge to backup your claims, all you do is spew ad hominem attacks against users making legitimate points based in factual information. Please enlighten us with actual information on how we are wrong, instead of redundant noise.

I will make this easy for you:

Claim 1: SX OS resizes the NAND, creating a 15gb partition to dual boot HOS.
Claim 2: Erpt does report NandTotalSize in error reports.

Now simply point out why you think this is incorrect.