Outcome: This 3DS was later unbricked after sending it to Nintendo for repair. All of my system save data and system ExtData was gone after the repair, but all of my other save data and ExtData remained intact. Lesson learned: Always have a NAND backup even if you are not on an exploitable firmware or using homebrew to modify the system! Original post: I am having a major problem with my first 3DS. Here are the posts that I made about it: http://techforums.nintendo.com/thread/33281 https://www.ifixit.com/Answers/View/178003/My+3DS+will+not+boot.+How+do+I+fix+this I was told that in order to fix the problem, I might need to have the motherboard replaced. Of course, the problem with this is that it would also replace the NAND and would use a different encryption key. I do not want to lose over 3 years worth of save data to fix the problem. If I did get a new motherboard, then would it be possible to swap out certain parts such as the NAND to keep the old encryption? If not, then I have one last (unsual) idea. I now own another 3DS running firmware 4.1. This will probably sound crazy, but would it be possible to solder the NAND on the first 3DS to the new one in a way so that they can both be connected at once? If this did actually work, then I would like to create an encryption tool homebrew program that would run from the new 3DS, but allow me to select the other NAND as the source for the encryption key. Then I could decrypt the data from there and on the SD card from the first 3DS and encrypt it again, but this time selecting the 4.1 3DS NAND as the source of the encryption key. Any help with these questions or the problem that I posted on the other websites would be greatly appreciated. I just do not want to lose my data forever.