Hacking Problem with moving EmuNAND

[Kotomine Kirei]

I installed A9LH today and got to the Move EmuNAND section of Plailect's guide, but I am getting an error message in Hourglass9.
I went to EmuNAND Backup as the guide said to, but it says:
"SD is not formatted for EmuNAND
EmuNAND Backup: failed!"

I did not make a backup of EmuNAND before installing A9LH (only made a backup of SysNAND and my SD card files as the guide said to), so, if I need one, then I am not sure what I should do now.

If I cannot restore EmuNAND, should I just follow the rest of the guide without moving the EmuNAND?
Is there no way of getting the files that I had on EmuNAND to work (saves, games, applications, etc.)?

 

[MelonGx]

How come you didn't backup your EmuNAND?
Yes, all the saves & gamedata were gone.

If you don't need the saves & installed games, then losing an EmuNAND isn't a problem - at least you didn't brick your 3DS.

 

[Kotomine Kirei]

How come you didn't backup your EmuNAND?
Yes, all the saves & gamedata were gone.

I was not really thinking about that, since I was just trying to concentrate on following the guide and not bricking my 3DS (which would have been far worse)
I actually had a backup of my EmuNAND before, but I lost that backup when I made a mistake with my hard drive partitions.

Anyway...so, my SD card files (which has my saves and such) are useless now?
Sigh...

 

[MelonGx]

I was not really thinking about that, since I was just trying to concentrate on following the guide and not bricking my 3DS (which would have been far worse)
I actually had a backup of my EmuNAND before, but I lost that backup when I made a mistake with my hard drive partitions.

Anyway...so, my SD card files (which has my saves and such) are useless now?
Sigh...

SD saves are tied with NAND's movable.sed.
So you have to have either the specific NAND or the movable.sed file which can only be dumped from that specific NAND.
Otherwise they're unable to be recognized.

Maybe there is a last chance:
If your EmuNAND was cloned from SysNAND and then FORMATTED once, then you can try to format SysNAND once (Backup SysNAND before formatting!) - In this situation, the NAND formation can generate a same movable.sed as your lost EmuNAND's.
If your EmuNAND is not in this condition, then there is zero hope.

 

[Kotomine Kirei]

SD saves are tied with NAND's movable.sed.
So you have to have either the specific NAND or the movable.sed file which can only be dumped from that specific NAND.
Otherwise they're unable to be recognized.

Maybe there is a last chance:
If your EmuNAND was cloned from SysNAND and then FORMATTED once, then you can try to format SysNAND once (Backup SysNAND before formatting!) - In this situation, the NAND formation can generate a same movable.sed as your lost EmuNAND's.
If your EmuNAND is not in this condition, then there is zero hope.

I see.
Well, I think that I will just start over.
Thank you for your help though.

 

[Deleted User]

By any chance what did you use to format into emumand before a9lh? This is one of the steps that is also preventing me form switching to a9lh since if my emumand isn't compatible then I lose all my shit and have to start over.Eather way I wish you luck.

 

[Kotomine Kirei]

By any chance what did you use to format into emumand before a9lh? This is one of the steps that is also preventing me form switching to a9lh since if my emumand isn't compatible then I lose all my shit and have to start over.Eather way I wish you luck.

What did I use to format? I am not sure what you mean.
Also, to hopefully save you the trouble that I had, make sure that you backup your EmuNAND.

 

[MelonGx]

By any chance what did you use to format into emumand before a9lh? This is one of the steps that is also preventing me form switching to a9lh since if my emumand isn't compatible then I lose all my shit and have to start over.Eather way I wish you luck.

GW-formatted EmuNAND usually has this problem.
You can
(1) Dump EmuNAND's CTRNAND with D9
(2) Inject EmuNAND's CTRNAND to SysNAND CTRNAND with D9 after the A9LH installation completed
(3) Install everything from
DSi / DS functionality is broken after completing the guide
section of this page: https://github.com/Plailect/Guide/wiki/Troubleshooting

 

[Deleted User]

GW-formatted EmuNAND usually has this problem.
You can
(1) Dump EmuNAND's CTRNAND with D9
(2) Inject EmuNAND's CTRNAND to SysNAND CTRNAND with D9 after the A9LH installation completed
(3) Install everything from
DSi / DS functionality is broken after completing the guide
section of this page: https://github.com/Plailect/Guide/wiki/Troubleshooting

GW-formatted EmuNAND usually has this problem.
You can
(1) Dump EmuNAND's CTRNAND with D9
(2) Inject EmuNAND's CTRNAND to SysNAND CTRNAND with D9 after the A9LH installation completed
(3) Install everything from
DSi / DS functionality is broken after completing the guide
section of this page: https://github.com/Plailect/Guide/wiki/Troubleshooting

Ok......this is what I've been wanting answered for awhile now.I used the go.gateway website to format to emunand from a YouTube tutorial back then last year back when we had the 10.3 downgrade......however I don't use gateway,I use cfw like luma,does that count as a gateway formatted emunand if I used the go.gateway website through the webbrowser and is this a quick and painless fix?

 

[MelonGx]

Ok......this is what I've been wanting answered for awhile now.I used the go.gateway website to format to emunand from a YouTube tutorial back then last year back when we had the 10.3 downgrade......however I don't use gateway,I use cfw like luma,does that count as a gateway formatted emunand if I used the go.gateway website through the webbrowser and is this a quick and painless fix?

This IS a GW-formatted EmuNAND.

 

[Deleted User]

This IS a GW-formatted EmuNAND.

Crap.....So basically I have to do extra steps to my emunand before switching to a9lh since it counts as a gateway NAND and I didn't format my emunand with emunand9 when I first switched to cfw.....Thanks for the clarification.

Btw I got anoughter question,what if you relink your emunand to your sysnand before installing a9lh? Wouldnt everything transfer over after the a9lh install since a9lh unlocks the blank spaces once installed and since the sysnand will have the same code as your emunand again you wouldn't need to do anything.Just a theory here but I know it might not work anyway.

 

[MelonGx]

Btw I got another question,what if you relink your emunand to your sysnand before installing a9lh? Wouldnt everything transfer over after the a9lh install since a9lh unlocks the blank spaces once installed and since the sysnand will have the same code as your emunand again you wouldn't need to do anything.Just a theory here but I know it might not work anyway.

The guide tells you to inject EmuNAND image into SysNAND.
You'll have only one NAND after the A9LH installation.
There is nothing related to relink stuff.