Hacking Question Dumping SX OS Emunand partition

[nachuz]

So I updated my emunand to 7.0.0 due to nobody telling that updating via local wireless updates the system too and since I don't have tickets from nsps installed on the emunand on my sysnand and my saves are on the emunand, I want to backup the emunand, restore it on sysnand and switch to Atmosphere because SX OS doesn't seem to update anytime soon (and Atmosphere is better anyways, I don't care about $25 spent one year ago)
The problem is that the SX payload doesn't let you backup your emunand and as far as I know, there's no software to backup your emunand on another partition, so how I do that, I'm fucked up for using fucking SX?

 

[Idontknowwhattoputhere]

So I updated my emunand to 7.0.0 due to nobody telling that updating via local wireless updates the system too and since I don't have tickets from nsps installed on the emunand on my sysnand and my saves are on the emunand, I want to backup the emunand, restore it on sysnand and switch to Atmosphere because SX OS doesn't seem to update anytime soon (and Atmosphere is better anyways, I don't care about $25 spent one year ago)
The problem is that the SX payload doesn't let you backup your emunand and as far as I know, there's no software to backup your emunand on another partition, so how I do that, I'm fucked up for using fucking SX?

Use win32 disk imager to img your sd to dump it

 

[nachuz]

Use win32 disk imager to img your sd to dump it

and what I'm supossed to do then? I'm not going to switch the microSD, I want to have the emunand to install it into the sysnand, not get a img of my whole microSD card

 

[Idontknowwhattoputhere]

and what I'm supossed to do then? I'm not going to switch the microSD, I want to have the emunand to install it into the sysnand, not get a img of my whole microSD card

it imgs the whole sd card partition so the sx emunand hidden partition will be there

 

[nachuz]

it imgs the whole sd card partition so the sx emunand hidden partition will be there

and how I get the nand from it

 

[thaikhoa]

Backup

dd bs=512 if=/dev/disk2 of=/Users/khoa/Desktop/boot0.bin skip=2 count=8192
dd bs=512 if=/dev/disk2 of=/Users/khoa/Desktop/boot1.bin skip=8194 count=8192
dd bs=512 if=/dev/disk2 of=/Users/khoa/Desktop/rawnand.bin skip=16386 count=61071360

Restore

dd bs=512 if=/Users/khoa/Desktop/boot0.bin of=/dev/disk2 seek=2 conv=notrunc
dd bs=512 if=/Users/khoa/Desktop/boot1.bin of=/dev/disk2 seek=8194 conv=notrunc
dd bs=512 if=/Users/khoa/Desktop/rawnand.bin of=/dev/disk2 seek=16386 conv=notrunc

 

[Idontknowwhattoputhere]

and how I get the nand from it

ffs its in the dump

 

[nachuz]

Backup


Restore

when I use it, it says that "/dev/disks" doesn't exist

 

[josete2k]

https://gbatemp.net/threads/moving-from-sx-os-sd-emunand-to-sd-hidden_emunand.526587/

 

[thaikhoa]

when I use it, it says that "/dev/disks" doesn't exist

Check on the physical address where is the location of your sd.

 

[gizmomelb]

old post, but following up since nachuz is still whining about emuNAND in other threads - this is how you extract the hidden partition emuNAND and convert it to files.

I highly recommend to ALL SX OS users that use emuNAND to use it as files on SD, not the hidden partition. Makes it easier to backup, you can edit it with hacdisk etc.

https://gbatemp.net/posts/8602506

 

[josete2k]

old post, but following up since nachuz is still whining about emuNAND in other threads - this is how you extract the hidden partition emuNAND and convert it to files.

I highly recommend to ALL SX OS users that use emuNAND to use it as files on SD, not the hidden partition. Makes it easier to backup, you can edit it with hacdisk etc.

https://gbatemp.net/posts/8602506

But when your sd becomes corrupt your emunand could be too...

 

[gizmomelb]

But when your sd becomes corrupt your emunand could be too...

while it is possible it is also as possible for hidden partition to become corrupt. FAT32 at least has some ''protection'' to file allocation tables due to two copies of it on the storage media, EXFAT corrupts more easily due to it only having one file allocation table - so if that corrupts, goodbye all data.

my personal obervation - I have less errors from coming out of sleep more since I have converted to SD files, than what I had when running a hidden partition emuNAND.

But everyone may have different experiences.

 

[xs4all]

But when your sd becomes corrupt your emunand could be too...

Yes this is true, think of it this way, what if you want to backup your EmuNand?

EmuNand as files on microSD <= Copying your EmuNand files is quick, fast and easy.
EmuNand as hidden partition <= Very slow using DD method.

If your using a minimum 64GB SD CARD and combined that with a USB3 card reader, the transfer speeds are pretty fast if you want to make backup of your EmuNand.
Try to do the same backup using DD command for EmuNand as hidden partition, since it's doing a raw backup, it takes ages!

Touch wood I haven't had any SD CARD corruptions but I'm one of those that prefer EmuNand as files on microSD over EmuaNand as hidden partition for backup purposes.

 

[josete2k]

I made a backup with DD in 2 hours... Not bad.

Restoring is faster... Around 45 minutes because I use a bigger block size.

 

[xs4all]

I made a backup with DD in 2 hours... Not bad.

Restoring is faster... Around 45 minutes because I use a bigger block size.

I was going to ask how long it takes on average to backup using DD? Your 2 hours seems to be quicker than me.

I've tried on a couple different laptops with built in SD CARD readers and also USB card readers and I followed your detailed guide on that Spanish site that you posted. For some reason the backup process was very slow, nothing like your 2 hours completion time, from memory it took me more that 8 hours to complete to backup using DD.
Restore is roughly the same as yours, anything I should know about the DD backup process? I pretty much followed all the steps to backup, but still slow, that is why in my previous reply I said it was slow, but maybe slow only for me?

 

[josete2k]

I had long time for backup too... Until I tested this MicroSD adapter:

https://www.amazon.es/dp/B07416LQVM/ref=cm_sw_r_cp_awdb_t1_L3TXCbD4EGKX6

 

[xs4all]

I had long time for backup too... Until I tested this MicroSD adapter:

https://www.amazon.es/dp/B07416LQVM/ref=cm_sw_r_cp_awdb_t1_L3TXCbD4EGKX6

Interesting, with this adapter, are you still using the bs=1024 when dumping in the dd command?

I managed to find a few more SD CARD readers lying around, I did a test of dumping for about 1 minute, in that 1 minute, with all my readers, I manage to find a reader that dumps roughy about 80mb per minute, all the other readers I have dumps at around 50mb per minute.

So it works out, the reader that was the fastest that I had will take roughly 6 hours to fully dump the 29.1GB rawnand, while the slower ones take about 9.7 hours to fully dump the 29.1GB rawnand. The 9.7 hours which it took to backup my hidden emunand backup a few weeks back sounds about right.

So the SD CARD reader does play a role as to how fast it dumps the rawnand from hidden EmuNand partition, does changing the bs=1024 when dumping makes a difference? I did a test with bs=1M and 5M and the backup speeds was pretty fast, but I assume this will mess up the dumping process of the rawnand?

 

[Garou]

I did a test with bs=1M and 5M and the backup speeds was pretty fast, but I assume this will mess up the dumping process of the rawnand?

pretty sure it will
because the skip parameter used in dd means skipping data based on the block size. so if you're using bs=1M then the starting offset of your dumped data will change too

 

[xs4all]

pretty sure it will
because the skip parameter used in dd means skipping data based on the block size. so if you're using bs=1M then the starting offset of your dumped data will change too

Thanks for the reply, I had a suspicion this was the case regarding the skip parameter command.