I discovered something that bothered me about emunand. My emunand and sysnand were both on FW 6.1.0. I then decided to upgrade my sysnand to 6.2.0 (I was aware of the risks and the problem with sleep mode). It worked. Only now I decided to make a backup of my sysnand using hekate. And to my surprise I discovered that SX OS leaves traces in sysnand. How did I find this out? Well, in theory, if there is no trace of modification in sysnand I can remove my memory card with SX OS and then my system is clean with no traces at all. However when I put a new memory card with a new unlock (eg Hekate) the system returns an error. A message appears informing the lack of the file boot.data that is a file of sx os. So to appear this information it is necessary that some trace of the sx stay in the sysnand is not it? This, in my opinion, calls into question the idea that emunand leaves no trace in sysnand. Can somebody get a better understanding of this?