Hacking Restore from emuNand is possible

[dawgslayer69]

So I could not find anything on this anywhere.

Here is my story.

A few weeks ago I set up an emuMMC as an SD file from Hekate. (You can apparently use the files created by this to do a restore in Hekate)
Yesterday I thought I would update my sysnand (no really good reason). I don't know the specific rules around when fuses will burn so I used ChoiDujournx just to be sure. It worked. I got all upgraded to 9.0.1. However, when the switch started booting up into the sysnand I was greeted with a message something like "The MicroSD card was used by another Nintendo Switch" followed by a message asking me to delete everything on the sd card. This is obviously not what I wanted.

This sucks I would love another solution to this in case I want to upgrade my sysnand int the future. However, I was lucky my emuMMC was still in a good state.

So here is how I restored my emuMMC to my sysnand.

1. I copied the files from SDCARD/emuMMC/<foldername>/eMMC to SDCARD/backup/<foldername>/restore
2. I then renamed all the numbered files example: "00" => "rawnand.bin.00", "01" => "rawnand.bin.01" ...etc
3. I then went into Hekate and did a full restore.

This worked fine for me. I'm not a crazy person I tested this beforehand by combining the rawnand chunks on a pc then using hacdiskmount to browse the files.

I suspect if you have a fuse mismatch that could be a problem. You might not want to try this.
Also I already had a pretty dirty sysnand before emuMMC support came out. So I am just fine with my dirty sysnand for now.

Hopefully, this helps somebody else.

 

[Draxzelex]

So I could not find anything on this anywhere.

Here is my story.

A few weeks ago I set up an emuMMC as an SD file from Hekate. (You can apparently use the files created by this to do a restore in Hekate)
Yesterday I thought I would update my sysnand (no really good reason). I don't know the specific rules around when fuses will burn so I used ChoiDujournx just to be sure. It worked. I got all upgraded to 9.0.1. However, when the switch started booting up into the sysnand I was greeted with a message something like "The MicroSD card was used by another Nintendo Switch" followed by a message asking me to delete everything on the sd card. This is obviously not what I wanted.

This sucks I would love another solution to this in case I want to upgrade my sysnand int the future. However, I was lucky my emuMMC was still in a good state.

So here is how I restored my emuMMC to my sysnand.

1. I copied the files from SDCARD/emuMMC/<foldername>/eMMC to SDCARD/backup/<foldername>/restore
2. I then renamed all the numbered files example: "00" => "rawnand.bin.00", "01" => "rawnand.bin.01" ...etc
3. I then went into Hekate and did a full restore.

This worked fine for me. I'm not a crazy person I tested this beforehand by combining the rawnand chunks on a pc then using hacdiskmount to browse the files.

I suspect if you have a fuse mismatch that could be a problem. You might not want to try this.
Also I already had a pretty dirty sysnand before emuMMC support came out. So I am just fine with my dirty sysnand for now.

Hopefully, this helps somebody else.

This will help all 5 people who use file-based emuMMC. Also you shouldn't be using file-based emuMMC in the first place.

 

[eliboa]

This will help all 5 people who use file-based emuMMC. Also you shouldn't be using file-based emuMMC in the first place.

Nonsense

 

[Basketto]

I think both come with their own advantages. Emu mmc stored as files is easier to delete/manage but more detetable by Nintendo. Having said that I find it hard to believe Nintendo would check contents stored on sd cards. The legal issues they would have to bypass are something that not even their highly paid lawyers can get around imo.

 

[smf]

The legal issues they would have to bypass are something that not even their highly paid lawyers can get around imo.

What legal issue is there for them banning you if they detect you are using a modified system? They seem to be willing to do that generally.

I thought file based emunand was discouraged because it was really slow.

 

[MasterJ360]

What legal issue is there for them banning you if they detect you are using a modified system? They seem to be willing to do that generally.

I thought file based emunand was discouraged because it was really slow.

It was discouraged b/c ppl seem to believe its not the real emunand style so to speak. But its biggest advantage is that you can easily make a copy of it in case the SD card gets corrupted or needs a format. Then you can just copy/paste it back to the SD card. I used to do hidden partition, but found it annoying to rebuild emunand after a format.

 

[pcwizard7]

but since the emunand is separate if the sd files become corrupted you would only need to format the visible partition. having it on the same partition makes more likely to become corrupted. there are tools to backup the emunand in hidden partition

 

[smf]

It was discouraged b/c ppl seem to believe its not the real emunand style so to speak.

Nope, it was hoped it could be sped up. It's got nothing to do whether it's "real" or not.

It's not really ready yet

 

[The Real Jdbye]

So I could not find anything on this anywhere.

Here is my story.

A few weeks ago I set up an emuMMC as an SD file from Hekate. (You can apparently use the files created by this to do a restore in Hekate)
Yesterday I thought I would update my sysnand (no really good reason). I don't know the specific rules around when fuses will burn so I used ChoiDujournx just to be sure. It worked. I got all upgraded to 9.0.1. However, when the switch started booting up into the sysnand I was greeted with a message something like "The MicroSD card was used by another Nintendo Switch" followed by a message asking me to delete everything on the sd card. This is obviously not what I wanted.

This sucks I would love another solution to this in case I want to upgrade my sysnand int the future. However, I was lucky my emuMMC was still in a good state.

So here is how I restored my emuMMC to my sysnand.

1. I copied the files from SDCARD/emuMMC/<foldername>/eMMC to SDCARD/backup/<foldername>/restore
2. I then renamed all the numbered files example: "00" => "rawnand.bin.00", "01" => "rawnand.bin.01" ...etc
3. I then went into Hekate and did a full restore.

This worked fine for me. I'm not a crazy person I tested this beforehand by combining the rawnand chunks on a pc then using hacdiskmount to browse the files.

I suspect if you have a fuse mismatch that could be a problem. You might not want to try this.
Also I already had a pretty dirty sysnand before emuMMC support came out. So I am just fine with my dirty sysnand for now.

Hopefully, this helps somebody else.

Your sysNAND is now no longer clean and can't be used safely online (not that it would have been clean anyway since you ran CFW and homebrew on it)
I hope you have a clean NAND backup.

 

[annson24]

Wait, so atmosphere's emuMMC is now stable enough to use on a daily basis?

Sent from my SM-N975F using Tapatalk

 

[MasterJ360]

Nope, it was hoped it could be sped up. It's got nothing to do whether it's "real" or not.

It's not really ready yet

Actually the file version being a real emunand or not was the very first complaint among its release to the sxos.. well Atmosphere users started this rumor. Personally I find the file version ok for what it does. I think we are just nick picky which is why the community is always debatable on things that have a simple purpose. Its a portable emunand at best, If speed was a huge deal then maybe ppl should buy sd cards with more speed as well.

 

[smf]

Actually the file version being a real emunand or not was the very first complaint among its release to the sxos..

No, the complaint about sxos is it repartitioned your mmc and stored your "emunand" in there. That isn't real emunand, because the contents were stored in the same nand chips as the sysnand. By definition emunand is supposed to be emulating nand using some other storage.

Does sx os even support file based?

 

[MasterJ360]

No, the complaint about sxos is it repartitioned your mmc and stored your "emunand" in there. That isn't real emunand, because the contents were stored in the same nand chips as the sysnand. By definition emunand is supposed to be emulating nand using some other storage.

Does sx os even support file based?

Yes the file based emunand was its first emunand they released then they created a hidden partition version.

 

[smf]

Yes the file based emunand was its first emunand they released then they created a hidden partition version.

Can you post a link showing that? The criticism against SXOS I saw was always using the mmc, nothing to do with files. Everybody wants files & would be the recommended way, except they are just slow.

https://gbatemp.net/threads/how-to-make-a-file-based-emunand-for-atmosphere.541810/#post-8690685

 

[MasterJ360]

Can you post a link showing that? The criticism against SXOS I saw was always using the mmc, nothing to do with files. Everybody wants files & would be the recommended way, except they are just slow.

https://gbatemp.net/threads/how-to-make-a-file-based-emunand-for-atmosphere.541810/#post-8690685

I''ll show you what it looks like since I have a backup of my entire SD card. Yeah its slow upon boot but SD card upgrade friendly.
https://imgur.com/Y4jM37Q
https://imgur.com/oMVkhMM
If something happens to the sd card where it gets corrupted/formatted or even lost its just a matter of copy/paste everything back to normal

 

[smf]

I''ll show you what it looks like since I have a backup of my entire SD card.

I meant show me something that proves sx os supported file based emunand before it supported hidden partition on mmc.

If something happens to the sd card where it gets corrupted/formatted or even lost its just a matter of copy/paste everything back to normal

I know, that is why they are working on the speed so it can become the recommended way of doing it.

 

[MasterJ360]

I meant show me something that proves sx os supported file based emunand before it supported hidden partition on mmc.

The 2 pictures i just posted is the file based emunand

 

[smf]

The 2 pictures i just posted is the file based emunand

Right, but those pictures don't tell me that sx os supported it before it supported hidden partition.

You said that everyone was ganging up on you saying that file based was not proper, I disagreed and said it was the sx os mmc hidden partition that wasn't proper & you tried to still "win" by saying it was sx os file based that came first which was criticized. I firmly believe you're wrong.

 

[MasterJ360]

Right, but those pictures don't tell me that sx os supported it before it supported hidden partition.

You said that everyone was ganging up on you saying that file based was not proper, I disagreed and said it was the sx os mmc hidden partition that wasn't proper & you tried to still "win" by saying it was sx os file based that came first which was criticized. I firmly believe you're wrong.

Im not here to win the last words like every argument we have together kek. Im just telling you emunand SD files exists and the speed isn't that big of a deal its really just petty nitpicking to choose hidden partition over it, but in the end what really matters is the ease of use between upgrading your SD card or recover your data from formatting. I'm not going to dig deep into gbatemps archives of old sxos threads to justify what i read last year. Honestly tho sxos is always criticized for whatever that comes out by atmo users you of all ppl should know that.

Oh... btw the whole reason they created the hidden partition was b/c ppl were upset about the emunand file version. So yes it had everything to do with it not being proper, mmc was just part of the reason. Im not even making this up ive had the sxos pro since June 2018 before emunand was even supported.

 

[smf]

Im just telling you emunand SD files exists and the speed isn't that big of a deal its really just petty nitpicking to choose hidden partition over it

We all know emunand sd files exists, it's just disappointing that it's so slow.

Oh... btw the whole reason they created the hidden partition was b/c ppl were upset about the emunand file version. So yes it had everything to do with it not being proper, mmc was just part of the reason. Im not even making this up ive had the sxos pro since June 2018 before emunand was even supported.

Storing on mmc was the only reason. But you seem sure, so I asked you to prove it. You don't want to.

I'll show you some proof to back up what I'm saying though https://medium.com/@pokemonhack/sx-...to-install-it-to-nintendo-switch-1546851ed77e
However, it must be borne in mind that the SX OS EmuNAND is within a partition of the original NAND,

https://gbatemp.net/threads/how-does-sx-os-emunand-work.518936/

You seem to want to believe that everyone is against file based emunand, like it makes you feel better because you are using something that is not "proper". It wouldn't have been added to atmosphere if everyone was against it, it's not some kind of rebellious plucky underdog that has to fight to survive. Sorry to disappoint you.