SX emunand has been very "controversial" in the modding scene as well as TX has been very controversial, this leads to some false rumors from very reputable sources such as hexkyz. This thread isn't to ruin anyone's reputation but to spread awareness on the blind hate.
So let's get into it! How does emunand work?
In the case of sxos emunand Team Xecuter made it so when installing it copies system files to the USER partition and writes the nand to 2 files named
1 - nand00.bin
2 - nand01.bin
and the BOOT1 gets modified at the end with the string "EMUNAND0" if the SX bootloader detects EMUNAND0 it loads from nand00 & nand01 (.bin) its not very complicated. Now let's share some screenshots i took from my partitions before & after emunand installation.
This is the stock USER partition before a emunand installation as you can see no nand00 or nand01 files have been created.
this is the USER partition with emunand installed. these are copies of needed files to boot horizon OS.
This is the USER partition size before emunand install.
Now this is not detectable at the current moment with the aparent (getPartitionSize) does not detect how much is used but the max partition size which is not modified with an emunand installation meaning Horizon stock can NOT find the emunand making it safe at the moment. (as of 10/22/18)
This thread isn't to support team xecuter's decision but i do not support the blind hate for Team Xecuter, please do your own research or ask for proof as i have provided.
Thank you
(thread was made because the other one had a lot of community proof instead of OP posting most proof)
So let's get into it! How does emunand work?
In the case of sxos emunand Team Xecuter made it so when installing it copies system files to the USER partition and writes the nand to 2 files named
1 - nand00.bin
2 - nand01.bin
and the BOOT1 gets modified at the end with the string "EMUNAND0" if the SX bootloader detects EMUNAND0 it loads from nand00 & nand01 (.bin) its not very complicated. Now let's share some screenshots i took from my partitions before & after emunand installation.
This is the stock USER partition before a emunand installation as you can see no nand00 or nand01 files have been created.
this is the USER partition with emunand installed. these are copies of needed files to boot horizon OS.
This is the USER partition size before emunand install.
Now this is not detectable at the current moment with the aparent (getPartitionSize) does not detect how much is used but the max partition size which is not modified with an emunand installation meaning Horizon stock can NOT find the emunand making it safe at the moment. (as of 10/22/18)
This thread isn't to support team xecuter's decision but i do not support the blind hate for Team Xecuter, please do your own research or ask for proof as i have provided.
Thank you
(thread was made because the other one had a lot of community proof instead of OP posting most proof)
Last edited by midstor,