Ok here's the merged result:
LINK REMOVED
This contains just the data and private folder. The movable.sed is already modified to work on the console you will move it too. I included the ctrnand.bat file as well.
Make sure you name the emunand dump you will be modifying "emunand.bin" and place it in the same folder as the batch file and the fat16tool.py batch script. (if the py file does not have that file name, rename it to have that filename) Also make sure padxorer.exe is in the same folder too.
Run the batch script. It will extract and decrypt the fat16 partition. You should see emunand.img appear so that you can open it in Winimage. Do NOT close or press a key in the command window yet. Minimize it for later.
you can just replace the movable.sed in the private folder with the one from the above link. But for the data folder it's a bit different. Go into the data folder. You will see a folder with a long string of letters and numbers. rename the folder (but do not delete it!) to match the filename of folder in the data folder of the files I sent you. Then go into that folder and delete extdata folder. (it's not needed). Then go into "sysdata" folder and delete all existing folders.
Then go in to that folder of the extracted files from the link above and copy the contends of sysdata folder into winimage at the same location. (make sure it's in the sysdata folder found withen the folder with the long string of letters and numbers)
Once you do that you are done editing it. Close winimage and go back to the command window and press any key to make it continue. It will reencrypt and inject the fat16 file for you. Then take that and boot it as your emunand.
Your n3DS will act like it was reset. This is normal. Just select language and go through the usual setup process (also make sure you had copied over the SD card content from the o3DS)
Once you get back to home menu you should see all the games (and home menu theme if one was enabled on the o3DS) and such. Though until you get the tickets transferred over they may not boot yet. (you'll have to call nintendo to move the NNID account from the bricked console to the new one. Once you do that relink NNID and visit eShop at least once. Then you should have the tickets. If any apps vanished, just copy the SD card backup of your o3DS back over to restore them. From that point on they should stick around and their saves will also work just as they did on the o3DS).
The only potentioal issue you might run into is if the xorpad is larger then the decrypted file. (or smaller. I don't recall. If it fails. Let me know what the size difference is) If that's the case you have a certain nand chipset that the current python script didn't take into account. If the batch file does not produce a file after the encryption stage, then that would be the case. Backup your emunand.img file before continuing the batch file as it will auto delete the file after it's done to keep things tidy. This is incase encryption stage failed due to xorpad producing a different size encrypted file then the injector expected. At least then you won't have to redo the winimage edits.
Let me know once you are able to give this a try.
Oh and I also included a screenshot of the movable.sed in my hexeditor. Near the start of the file you will see a single hex pair highlighed in red. That's what you should change on a movable.sed before moving it to a new console. The highlighed data at the bottom should be deleted. The resulting file should be 288 bytes exactly.
Once done that movable.sed and it's data folder pair can be moved to any 3DS.
