RELEASE SXOS Hidden Emunand Backup Tool

At first glance at title I was thinking SX OS has some hidden feature that you have found.

 

Same here, clickbait title a bit but well atleast you did detail enough in the post itself

 

I will do testing on atmosphere emunand

 

this i gotta wait for.

 

we can start Task Manager to see if it works.
If working, you'll see Sector inspector using your disk (can't send a screen cuz I don't have 5 posts yet)

 

nice work, thanks for including the powershell script

 

sxos emunand starts at sector 0x02

all the tool would need is the sector range in which u place the emumd nand partition, now people who used atmos would place this at end of the card. u would need to know the starting point of where the nand is placed to end of the card.

or something like memloader to mount the partitions first then back them up?

 

Nice tool. Thanks.

 

For atmosphere the ideal way would be to read emummc/emummc.ini to read the start address of the emunand, because it can be anywhere.

 

Guess since I dual boot them from the same emunand I can just dump once and don't have to guess where the atmo one is...Gonna check this out later. It's for sure been something that's been asked for, for a while.

 

I mean, in fairness, it's all in how you read it. When spoken aloud with the correct emphasis, it can easily mean exactly what it's trying to say. I actually read it as the Hidden Emunand + Backup Tool. As opposed Hidden + Emunand Backup Tool, if that makes sense. So, not exactly intentional in the clickbait sense.

 

You don't know either on which MBR partition is located the "emummc" folder, don't you ?

I guess the best way to do this is the way hekate does it (emunand migration tool) :
- Iterate every mmc's MBR partition
- For each partition, look for the GPT signature (EFI PART) of RAWNAND (in most case at offset 0x4001, after both BOOT partition)
- If signature is found, you’ve got your emuMMC partition : break, otherwise : continue to next iteration

That's the way I implemented it in NxNandManager, and it seems to work fine ;-)

 

Nah no real harm was done here so it's all good

But please keep in mind that a title can be misleading ... even though it was not intended that way. (We humans be a strange folk about how that all works really). And then things can spiral a bit out of control. If you can prevent that it's better than in most cases correcting / curing a situation afterwards.

But as I mentioned you detailed the essence in the initial post itself very well so then a title is just that ... a title.

 

The emunand has been corrupted but I managed to make a backup before, now how do I restore it? Thank you

 

How can I check if I actually have a emunand installed? Problem is I had multiple microSD cards and for some of them I dont remember if I have it or not.....