-PLEASE NOTE THIS /WILL/ REQUIRE FLASHING A MODIFIED NAND BACKUP TO YOUR CONSOLE. ALWAYS MAKE SURE YOUR MODIFIED NAND BACKUP WORKS IN EMUNAND BEFORE FLASHING TO AVOID A BRICKED CONSOLE!!!!!!!!!!
-AFAIK, THIS ONLY WORKS WITH ESHOP CONTENT DOWNLOADED ON THAT CONSOLE. NO YOUR DOWNLOADED CIA'S WILL NOT WORK IN SYSNAND WITH THIS METHOD.
-MYSELF/GBATEMP ARE NOT RESPONSIBLE IF YOU BRICK YOUR CONSOLE DOING THIS. (As long as you test your modified NAND backup inside of emuNAND before flashing it, you should be fine.)


Shoutouts to cearp and liomajor for helping me with this.


Requirements:

-4.x Console (9.x downgraded to 4.x will work. It's just to get XORPads. You /can/ modify your 9.x backup if you wish to restore back to 9.x with your eShop content).
-LINKED emuNAND and sysNAND (If you've system transferred from another console to your current emuNAND, this will also work. Adding moving the file "movable.sed" makes this possible).
-emuNAND with wanted eShop content downloaded and installed
-Backup of sysNAND that you want to move eShop content to
-Backup of emuNAND with eShop content (you will be overwriting this emuNAND to test your modified sysNAND before flashing it to your console. You can always write it back with emuNANDTool)
-File pack located below
-Hex Workshop

Guide:
Step 1: Make a backup of the sysNAND you want to add eShop content to. Store this somewhere safe.
Step 2: Make sure your emuNAND has the eShop content you want moved. Back this up with emuNANDTool. Store it somewhere safe.
Step 3: Copy the TOSD folder to your 3DS' BIG SD card.
Step 4: Install the DS Profile Exploit if needed. Follow the usual steps to get into 3DS_Multi_Decryptor.
Step 5: Choose the "NAND FAT16 XORPAD" Option
Step 6: Let the process finish, then power off your console
Step 7: Copy the newly created nand.fat16.xorpad file to your working directory.
Step 8: COPY your EMUNAND WITH ESHOP CONTENT to your working directory.
Step 9: Rename the previously mentioned emuNAND backup to emuNAND.bin.
Step 10: Drag the "emuNAND.bin" onto "dragNandDumpForFat16.bat"
Step 11: Let the process finish
Step 12: Double click "decrypt.bat". If you haven't renamed any files, this should spit out a file named emuNAND.bin.out
Step 13: Open up emuNAND.fat16.bin.out inside of WinImage.
Step 14: Navigate to the "dbs" folder.
Step 15: Copy the ticket.db file to your working directory/somewhere safe.
Step 16 (ONLY IF YOU'VE SYSTEM TRANSFERRED TO EMUNAND): Go back to the root of your emuNAND in WinImage. Navigate to the "private" folder. Copy the movable.sed file to your working directory/somewhere safe.
Step 17: Close winimage. Move "emuNAND.bin, emuNAND.fat16.bin, emuNAND.fat16.bin.out" to a backup folder, just in case.
Step 18: Copy the SYSNAND IMAGE YOU WANT TO MODIFY to your working directory. Rename this to emuNAND.bin. Follow steps 9-13 to get this image open in WinImage.
Step 19: Navigate to the "dbs" folder. Copy the previously extracted ticket.db to that folder, overwriting the old one.
Step 20 (ONLY IF YOU'VE SYSTEM TRANSFERRED TO EMUNAND): Navigate to the "private" folder. Copy the previously extracted "movable.sed" into that folder, overwriting the old one.
Step 21: Close WinImage.
Step 21.5: Rename "emuNAND.fat16.bin.out" to "test.bin"
Step 22: Open a command prompt window, CD to your working directory
Step 23: Paste the following command into the prompt "padxorer.exe test.bin nand.fat16.xorpad". Let the process finish.
Step 24: Open up "emuNAND.bin" and "test.bin.out" inside of Hex Workshop. Shrink the bar with '0 1 2 3 4 5 6 7 8 9 A B C D..." so your workspace looks like this in BOTH FILES: http://i.imgur.com/kZOUWa0.png
Step 25: Go to your "emuNAND.bin" tab, and press CTRL+G to open the "goto" prompt
Step 25: Make sure the offset is "Hex", "From Where" is "Beginning of File", and paste "B930000" in the Offset box. Click ok
Step 26: Go to test.bin.out, Press CTRL+A to highlight everything and CTRL+C to copy all the data.
Step 27: Go back to emuNAND.bin, Highlight everything from the B930000 offset to the bottom of the file. Press CTRL+V to overwrite it with the content of test.bin.out.
Step 28: Inject the newly modified emuNAND.bin to your emuNAND. (If you did the System Transfer steps, it will take you to the 3DS' setup screen. Follow the steps.)
VERIFY THAT THIS BOOTS PROPERLY IN EMUNAND BEFORE FLASHING TO YOUR SYSNAND. IF IT DOESN'T, START THE PROCESS OVER AND DOUBLE CHECK YOUR DID THE STEPS IN HEX WORKSHOP PROPERLY.
Step 29: Double check that all your eShop content is showing up properly in the newly modified emuNAND.
Step 30: Power off your 3DS. Copy the newly modified emuNAND to your 3DS' BIG SD Card. Rename the file to NAND.bin.
Step 31: Boot into the GW menu holding "L". Scroll over to the "Downgrade Console" option, and select it while holding "up". Let the process finish and reboot your console.
Step 33: Pop your 3DS' big SD card back in your computer. Restore your ORIGINAL EMUNAND backup you made earlier.
Step 34: Congratulations! You should now have your emuNAND eShop content on sysNAND!

 

[cearp]

if it was just the movable.sed i have a launcher.dat for that, but since the ticket.db is like 36mb, i have to implement a loop and write to the file many times, not just once (the movable.sed is small)
a shame about the tricky method, but thanks for helping people

 

[liomajor]

If anything goes wrong, as always you can restore your original NAND.BIN with Hardware mod and Rasberry Pi.

Why not just installing your eShop content with sysNAND? Because you need aktual Firmware to access it!

Known Limitations? Only if your eShop content requires for real a higher Firmware Version to make use of it.

 

[DSoryu]

I would love to try, but atm I'm using MT Emunand (I have no Gateway) and the emuNAND tool doesn't reognize that emuNAND yet.

 

[liomajor]

I would love to try, but atm I'm using MT Emunand (I have no Gateway) and the emuNAND tool doesn't reognize that emuNAND yet.

The detection is @ Offset 47 when you open the SD Card Drive with HxD "GATEWAY".

 

[DSoryu]

The detection is @ Offset 47 when you open the SD Card Drive with HxD "GATEWAY".

Then should be possible to modify the emuNAND tool to recognize MTCard Emunand right? Is there a source code for said program?

 

[liomajor]

HxD? You can grab it here: http://mh-nexus.de/en/hxd/

It's free, but you can use other tools you prefer.

 

[DSoryu]

HxD? You can grab it here: http://mh-nexus.de/en/hxd/

It's free, but you can use other tools you prefer.

Thanks, I'll try and then post results, it's annoying how all my eShop titles are shown on sysNAND but can't play them, specially the ambassador GBA games.

 

[DSoryu]

The proccs to selct everything from B930000 to th bottom is taking ages... isn't there a command or something to select everything from there?

EDIT: NVM, I forgot that thre is a "End" Button...

EDIT2: It seems that both hx workshop and HxD have a problm when pasting the data... both have an "out of memory" error... fuck

 

[sonic2756]

The proccs to selct everything from B930000 to th bottom is taking ages... isn't there a command or something to select everything from there?

EDIT: NVM, I forgot that thre is a "End" Button...

EDIT2: It seems that both hx workshop and HxD have a problm when pasting the data... both have an "out of memory" error... fuck

System specs?

 

[zero2exe]

I have a 9.2 console, I'm wondering if after doing this process (obviously going through downgrade first) of moving the eshop content would it be possible to restore the sysnand to 9.2 and still be able to use all the games and patches downloaded from the eshop?

 

[sonic2756]

I have a 9.2 console, I'm wondering if after doing this process (obviously going through downgrade first) of moving the eshop content would it be possible to restore the sysnand to 9.2 and still be able to use all the games and patches downloaded from the eshop?

As long as you edit the 9.2 NAND backup, yes. 4.x is only needed to get xorpads.

 

[liomajor]

EDIT2: It seems that both hx workshop and HxD have a problm when pasting the data... both have an "out of memory" error... fuck

You can use another Hex Editor like Hex Workshop or WinHex. Dunno why some ppl have problems with HxD and Memory if there is enough in their PC.

 

[DSoryu]

System specs?

Windows 8.1 32 bit, Intel core i3, 3 GB RAM.

You can use another Hex Editor like Hex Workshop or WinHex. Dunno why some ppl have problems with HxD and Memory if there is enough in their PC.

Hex Workshop gives me the same error, I'll try WinHex, I really hope that one works.

BTW sorry for some in correct words, my "e" key is faulty

 

[Deboog]

I CAN FINALLY PLAY GBA AND DSI GAMES. HALLELUJAH.

 

[liomajor]

Windows 8.1 32 bit, Intel core i3, 3 GB RAM.

Ok i see the problem, 32Bit can only allocacte up to 3,25GB RAM without tweaks.

~1 GB File + ~800MB + System + Reservation == not gonna work properly.

 

[apoptygma]

Sorry, total dumb question here - what would be the kind of scenario where you'd be doing this? I don't see the real-world application for this.

 

[DSoryu]

Ok i see the problem, 32Bit can only allocacte up to 3,25GB RAM without tweaks.

~1 GB File + ~800MB + System + Reservation == not gonna work properly.

Well, time to dust off my old laptop, is very weak but it runs Seven 64bits, 1GB RAM and Intel Pentium 4 MT

 

[DSoryu]

Sorry, total dumb question here - what would be the kind of scenario where you'd be doing this? I don't see the real-world application for this.

Because my scenario, here the brief story:

I had a cosmo black 3DS since launch day, so I got my ambassador games and purchased many games before any hack was ever known. I didn't gave a fuck about the warnings about to update above 4.5 (FY Monster Hunter). I bought more and more games from the eShop, and keeping my console up to date because I lost my hopes for a newer exploit to surface... until Smealum and GW team warned about the 9.3 update. I stayed at 9.2 and when the exploits were released, I entered to the newly born 3DS scene.

Unfortunately, something happened to my 3DS main board: some very, very little circuits started to malfunction, and the Y, L and R buttons stopped to work. There was no repair for that problem, neither change the buttons nor cleaning them, they were still not working properly (They acted as being keep pressed, I kept trying to fix them but no luk, I even bought three more sets of buttons).

The only way left: Buy another 3DS (Bought a Red one). But everyone knows what that means... UPDATE TO 9.4, and my new 3DS (not n3DS, only new normal 3DS) came with 4.5 FE yay!!)

So I came up for something; instead of doing a system transfer, I called Nintendo, and told them that my Black 3DS was stolen, and I wanted to recover all my eShop purhases. They told me that it was possible, and asked for both 3DS serial numbers (old and new) among some questions about what tittles did I have in my acount, my e-mail and my NNID. They told me that my eShop purhases would be arried over to the new console within two days.

Two days after, my old Black 3DS refused to load any game, and when entering to the system settings>Data Management>software, it deleted everything, so obviously that meant that my eShop account got unlinked from there, so here comes the tricky part.

I installed a MT-Card emuNAND to the Red 3ds, so I cannot loose my 4.5 sysnand, and then updated the emuNAND to 9.4. Entered the eSHop and linked my existing NNID from the old console, and boom!! My mii appeared, and on the eShop, under the "Downloaded content" section all my game purchases where there!! Even the ambassador games. So I started to download everything to emuNand... I thought I was saved and feeling like a boss, until I returned to sysNAND to play my GBA games...

THIS HAPPENS:

Spoiler

And here I'am, trying to get my games playable on sysNAND with this tricky method...

 

[liomajor]

1 GB... that must be real slow. Adding more RAM would speed it up.

The best solution is 64Bit on a decent PC with 4+GB RAM