Old 3DS data can't be read after repair

[SyrusHedgie]

I recently sent my 3DS in to be repaired because the top LCD screen stopped working. After about a week, they determined that there was a bunch more issues than before, so bad that the motherboard itself needed to be replaced. Don't remember it be having that many problems before I sent it off, but whatever. So because of this, it was sent back to me with a new motherboard, making the old data inaccessible.

Luckily, I had backups from the old motherboard on hand, including the nand backup, boot9 and movable.sed. I heard there were ways to decrypt the save data or make it so all the data is accessible again. What should I do from here? I've researched certain things like CTR transfers or using ninfs and 3ds save tool, but I'm hoping there's a more automatic solution where I can just restore everything completely. Any ideas?

 

[Kwyjor]

I've researched certain things like CTR transfers or using ninfs and 3ds save tool

Maybe you should provide links to what you found? That way people won't waste time providing solutions you already rejected.

While you might be able to inject your old movable.sed into your new unit, that is likely to cause problems and is usually not recommended.

https://gbatemp.net/threads/restore-save-data-from-dead-3ds-2ds.606907/ is as automated as it gets.

 

[SyrusHedgie]

Maybe you should provide links to what you found? That way people won't waste time providing solutions you already rejected.

While you might be able to inject your old movable.sed into your new unit, that is likely to cause problems and is usually not recommended.

https://gbatemp.net/threads/restore-save-data-from-dead-3ds-2ds.606907/ is as automated as it gets.

I didn't "reject" anything. I was simply researching other options and then I wondered if there was an easier way. And if anyone has the best solution, I'm more than willing to see what I can do. I will check that link out.