Hacking A better way to Dsiware Transfer

[zoogie]

New DSiWare Transfer method.
(April 7, 2018)
Source 3DS (hacked) =S
Target 3DS (unhacked)=T

On Source:
1. Download seedstarter.cia from FBI's TitleDb feature.

2. Launch app then press X. Movable.sed will be dumped to sdmc:/seedstarter/movable.sed. Copy your movable.sed to somewhere on your PC.

3. System transfer from S to T.

On Target:
Note: this part is basically a continuation of the seedminer process at step 6:
https://gbatemp.net/threads/seedminer-fc-and-mining-help.496114/

1. Buy a compatible dsiware game (but first check if you already have a compatible one).
NOTE: If you already had an eligible game pre-transfer, you can move on to step 2. (a pirated dsiware will NOT work, however)
- Compatible List of DSIgames for EUR: https://pastebin.com/Z7K5zMd2
- Compatible List of DSIgames for USA: https://pastebin.com/eMyPvt29
- Compatible List of DSIgames for JPN: https://3ds.hacks.guide/installing-boot9strap-(dsiware-game-injection-list) (scroll to bottom)
Sudoku is recommended if you don't already have one of the above games. If your existing game is not on the lists, go ahead and try it, there's a good chance it works!

2. Export your dsiware game to sd card in system settings.

3. Take out your sd card and go to sdmc:/Nintendo 3DS/<id0>(the same long hex number in step 3)/<another long hex number>/Nintendo DSiWare/<here>
You take that .bin (example 4b344445.bin) and place it wherever your movable.sed file is (Source: step 2).

4. Go to https://jenkins.nelthorya.net/job/DSIHaxInjector/build?delay=0sec and follow the directions there to upload your dsiware and movable.sed. Press the Build button after you fill out all the fields except the last email one.

5. After the patching is finished, click the latest build number in the left column of the webpage. There should be a filename that looks similar to: example 4B344445.BIN.patched_yourName. Download it.

6. Place this downloaded file back to the same place on the 3ds as step 3. This is where your original dsiware export .bin was.

7. Put the sd card back in the 3ds and turn it on. Go to:
System Settings -> Data Management -> DSiWare -> SD Card Tab (NOT System Memory this time) -> Click on your game.
Then copy it back to system memory, confirm all the prompts.

8. Download the following 3 files and place them on the root of your sd card.
https://github.com/zoogie/b9sTool/releases/latest
https://github.com/AuroraWright/Luma3DS/releases/latest
https://github.com/fincs/new-hbmenu/releases/latest

9. You're almost there! Finish the rest of the steps at:
https://3ds.hacks.guide/installing-...n)#section-vi---flashing-the-target-3dss-firm
--------------------------------------------------------------------------------------------------------------

What's so different to what we already have?
The big important difference, if you can see it, is that you buy the game after the system transfer, and on the target system. No actual hacked dsiware, or its ticket, is transferred during the system transfer process -- so less to go wrong. The only thing that matters in the transfer process is the movable sed transferring -- a very safe bet in making it across unscathed. You still have to buy the game on the target console to be able to import it. Also, the actual dsiwarehax injection is done on a convenient web gui platform instead of the 3ds, which makes things easier and less prone to error.

Advantages:
- Less chance of failure due to not needing to pass a hacked-up srl and/or save injected dsiware game through the complex 3ds system transfer process just to be rejected. In other words, more idiot/fail proof.
- If for some reason the import fails on the target system, you can simple try again with a different game. Although thats extremely unlikely to be necessary.

How this can possibly work without transferring the actual game or ticket?
https://www.3dbrew.org/wiki/3DS_System_Flaws
Ctrl-F "DSiWare_Exports CTCert verification"
tl;dr dsiware exports are only bound to their system's sd encryption key (movable.sed). Therefore, if you know what a given system's movable sed is, you can modify the dsiware contents on another system.

But this isn't in the Guide!
Hopefully it will soon!

Well I did try the Guide's version and it didn't work .... and the Guide did say to make a source system nand backup -- which I did. Could I possibly use this method now since I really don't want to wait a week just to possibly fail gain?
Yes!

 

[Quantumcat]

What about if the source system has an NNID? To get into the eShop after the transfer, the NNID pseudo-link will have to be removed (injecting a blank nnidsave.bin), then won't that interfere with importing it (it isn't owned by the NNID on the target)? Or maybe there won't be a problem until you visit the eShop, removing the non-owned titles. What setup did you test with?

 

[Patxinco]

I have another idea:
I just have a DSi with 4swords and with the transfer tool to 3DS i can keep transfering to a "stock" b9s, hax 4swords, then sytem transfer to the target 3DS and it should be done, not?

 

[The Real Jdbye]

What about if the source system has an NNID? To get into the eShop after the transfer, the NNID pseudo-link will have to be removed (injecting a blank nnidsave.bin), then won't that interfere with importing it (it isn't owned by the NNID on the target)? Or maybe there won't be a problem until you visit the eShop, removing the non-owned titles. What setup did you test with?

You don't ever need to go into eShop on the source system as far as I can tell.

 

[Quantumcat]

You don't ever need to go into eShop on the source system as far as I can tell.

I misunderstood

 

[DarkDengar]

This new take on an old method sounds great! I’m one who had delays installing CFW on an O3DS and due to friends wanting to keep saves, NNINDs, etc. intact on all the systems involved, it took me 3 weeks* because of the transfer “cooldown.” Though it is no longer of use to me, at least at the moment, I’m happy to hear others can skip the potential wait times and get to CFW more quickly and reliably! Thanks for the write-up.

*The 3 weeks came from having a failed hax transfer as well as using a 3rd CFW 3DS as a “save slot” for the OFW 3DS.

 

[carrieshot]

Not exactly sure how you get the 4b344445.bin or export the injected sudoku

 

[LinoyosTorovoltos]

I've been thinking about this for a while and just got around to testing it recently but .... well here, just have a look:

--------------------------------------------
source system (cfw)
1. *freeshop ^sudoku into source system
2. inject old sudoku srl/nds into freeshop sudoku and hax save as well
3. export and import the injected sudoku
4. test it and make sure it boots b9sTool
5. copy the exported injected sudoku (4b344445.bin) to somewhere for safekeeping
6. nand backup this system now - then keep it secret, keep it safe

System transfer source -> target. don't worry about freeshop sudoku not transferring.
the moveable sed being transferred is what's important

target system (stock firmware)
1. buy sudoku from eShop
2. place 4b344445.bin in Nintendo 3DS/<32 digit hex>/<32 digit hex>/Nintendo DSiware/
3. in system settings, import sudoku from SD
4. boot it and dsiwarehax should work

*any well-formed dsiware cia should work, i.e. not make_cia garbage.
^ sudoku is just strongly recommended as it's a known quantity and is the same title as its injected counterpart. any eligible dsiware transfer game is acceptable.
--------------------------------------------

What's so different to what we already have?
The big important difference, if you can see it, is that you buy the game after the system transfer, and on the target system. No actual hacked dsiware, or its ticket, is transferred during the system transfer process -- so less to go wrong. The only thing that matters in the transfer process is the movable sed transferring -- a very safe bet in making it across unscathed. You still have to buy the game on the target console to be able to import it.

Advantages:
- Less chance of failure due to not needing to pass a hacked-up srl and/or save injected dsiware game through the complex 3ds system transfer process just to be rejected. In other words, more idiot/fail proof.
- If for some reason the import fails on the target system, you can restore the nand backup on the source system and repeat the above steps with a different game. Yes, you get a do-over without the 1-week penalty!

How this can possibly work without transferring the actual game or ticket?

Ctrl-F "DSiWare_Exports CTCert verification"
tl;dr dsiware exports are only bound to their system's sd encryption key (movable.sed). Therefore, if you know what a given system's movable sed is, you can modify the dsiware contents on another system.

But this isn't in the Guide!
That's none of my concern. I'm just detailing the process, and that's all I intend to do.

Well I did try the Guide's version and it didn't work .... and the Guide did say to make a source system nand backup -- which I did. Could I possibly use this method now since I really don't want to wait a week just to possibly fail gain?
Yes!

After I switch to homebrew title on download play it errors with this:

I used the new seedminer exploit, but one time I tried soundhax but I didn't follow the instructions and swapped the order of programs in the homebrew launcher. After I updated to 11.6, i deleted the hack. Can someone tell me what is the problem and how to fix it? Crash dump: attached

 

[carrieshot]

After I switch to homebrew title on download play it errors with this: View attachment 113322 I used the new seedminer exploit, but one time I tried soundhax but I didn't follow the instructions and swapped the order of programs in the homebrew launcher. After I updated to 11.6, i deleted the hack. Can someone tell me what is the problem and how to fix it? Crash dump: attached

will it crash everytime?

 

[zoogie]

Alright, this DSiWare transfer method in the OP has just been updated to something more modern, easier, and foolproof (most steps are from seedminer, in fact).

 

[Shokubutsu]

I'm new into 3ds hacking, could someone explain me why the system transfer is needed? The only thing you do in the source 3ds is get the movable.sed and then do the system transfer. Why it won't work if I use the movable.sed from the source 3ds and the target 3ds DSiWare game .bin to do the injection, without transferring the system?

 

[Vrpndt]

Hey, I need to get the DSiWare game to the traget console TO INSTALL CFW. I don't have any DSiWare games on the target console and I'm trying to get the CFW from New 3DS to Old 3DS. Any way this is possible?

 

[Quantumcat]

Hey, I need to get the DSiWare game to the traget console TO INSTALL CFW. I don't have any DSiWare games on the target console and I'm trying to get the CFW from New 3DS to Old 3DS. Any way this is possible?

You can't transfer from new to old. Follow this guide instead: https://jisagi.github.io/FrogminerGuide/