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?
Hacking Discussion Is SX OS Emunand safe enough? I don't think so
- Thread starter FortalezaG
- Start date
- Views 8,221
- Replies 23
If you're using the SX Pro dongle or are launching the SX payload using another method, that requires boot.dat to be present to work even if you're just loading another payload. Unless you put the SX Gear firmware on it, which can load other payloads without the need for boot.dat.
You must have booted the SX payload.
I use tegraRCM to inject hekate payload. Before using SX OS I always used tegra to inject payload and it always worked. The point is that SX OS changes something in Sysnand so you need boot.dat. If I removed the memory card and put another was not to be any trace of the SX OS. It was for my console to be as before.
That doesn't make any sense, SX can't be trying to boot if you aren't loading the SX payload. We haven't hacked the Switch enough to load payloads without using RCM yet.
You are switching cards while powered on? That’s stupid enough; don’t do that. Power off, insert new card, power on. Then there is no way in hell your system complains about boot.dat, no matter how much SX stuff is on your nand.
This is the screen that appears when I inject the hekate 4.2 payload by the tegra rcm. I am using a different sd card than I use to start SX OS.
--------------------- MERGED ---------------------------
NO I don't switching the sd cards while powered on. I'm using separeted sd cards to hekate and SX OS with Emunand.
tks
Afaik, Hekate couldn't load sx's payload. You're missing boot.dat anyway.
--------------------- MERGED ---------------------------
You can play free online games in pure sysnand 6.2 while keeping emunand on 5.1 to run hb but sleep mode will be broken because of the fuse.
But is not the boot.dat file exclusive to SX OS?
Also I was not trying to start a CFW. I just inject the hekate payload in order to make the copy of my nand. Does hekate need a boot.dat file?
Last edited by FortalezaG,
So the SX OS's Emunand leaves traces on SYSNAND. That's the only way to explain it. Otherwise how would you explain the lack of a boot.dat file when injecting the hekate payload using the tegra RCM into another micro sd card?
The question is not what kind of CFW should I use. The question is what a certain CFW offers you but which is not exactly what you expected. Especially when you pay for it. If this is really true Xecuter is not being transparent with its customers who pay for something that is not really what they want.
--------------------- MERGED ---------------------------
All spoke badly of the emunad partitioning their sysnand. This was the first emunad released by TeamXecuter. But this version of emunad that runs straight from the sd card was well accepted for thinking that it leaves no trace on sysnand.
But it does not seem that way.
You must have hekate autobooting the sx payload somehow. When entering hekate press and hold the volume - button and disable autoboot.
Emunand is safe as in safe from tampering your sysnand. People are just having wrong impressions of going online with it... it doesn't work like that.
None of this makes any sense you shouldn't even be getting a boot error unless your trying to use the sxos and usually this means your sd card needs formatting or the boot file is missing.
On a side note you can use other cfw payloads using the sxos boot menu instead of switching SD cards. You might wanna disable emunand before using other payloads to reduce any further issues.
None of this makes any sense you shouldn't even be getting a boot error unless your trying to use the sxos and usually this means your sd card needs formatting or the boot file is missing.
On a side note you can use other cfw payloads using the sxos boot menu instead of switching SD cards. You might wanna disable emunand before using other payloads to reduce any further issues.
Last edited by MasterJ360,
Yeah, that "other SD card" has the Hekate autoboot set to SX OS.
OP, try to inject Hekate WITHOUT an SD card.
(Yes, that works)
Then you'll see this is just user error, caused by the hekate autoboot settings on your 2nd sd card.
I totally came into this thread expecting a technical post of someone dissecting a sysnand dump before and after running emunand, with hacdiskmount or even just a checksum comparison.
Was disappointed to see nothing but the SX payload error screen "boot.dat?" being used as "proof".
Last edited by bundat,
Similar threads
-
-
-
-
-
-
-
-
-
@
Sicklyboy:
@Xdqwerty, Osu! Tatakae! Ouendan! is the Japanese version of the game, different settings/characters/songs but otherwise identical mechanics. I played that before I knew about Elite Beat Agents lol. Both fantastic games https://en.wikipedia.org/wiki/Osu!_Tatakae!_Ouendan+1 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
