[Question] System Transfer from emuNAND-A to emuNAND-B

Discussion in '3DS - Flashcards & Custom Firmwares' started by MelonGx, Jan 23, 2015.

  1. MelonGx
    OP

    MelonGx GBAtemp Advanced Maniac

    Member
    1,634
    439
    Jan 8, 2009
    China
    1) Enter source console (emuNAND-A)'s GW3D 9.4 System Setting.
    2) Enter target console (emuNAND-B)'s GW3D 9.4 System Setting.
    3) Enter both consoles' emuNAND System Transfer.
    4) Do the System Transfer.
    5) Error at Step 3/5. Once it entered Step 3/5, target console (emuNAND-B) gave out an error code and disconnected immediately.

    I have a 3rd 3DS but it requires 3 days to be able to be a target.
    So I can't find whether it's the target console's problem or not.

    Source console has e-shop logs so it cannot be changed.
     
  2. Queno138

    Queno138 Ravens

    Member
    2,413
    782
    Sep 18, 2010
    Senegal
    Luigi's Dark Mansion
    Maybe you installed .cias on source system, so it doesn't allow transfer?
     
  3. MelonGx
    OP

    MelonGx GBAtemp Advanced Maniac

    Member
    1,634
    439
    Jan 8, 2009
    China
    I created 2 new emuNANDs on both consoles to try to avoid this problem. Is it enough?

    I don't know Step 3/5's English name since my consoles are all Japanese.
    It seems to be the step of "Internal contents' transferring".
     
  4. Queno138

    Queno138 Ravens

    Member
    2,413
    782
    Sep 18, 2010
    Senegal
    Luigi's Dark Mansion
    I would assume that .cia are not allowed to be transferred,
    because when your 3ds does a network check, it sees files without proper signatures,
    but hey thats just an assumption.


    You could try deleting the cias on your source 3DS, and see if it transfers after.
    Do backup your saves onto your computer before doing so, preferably with savedatafiler.

    Anyone else who knows better feel free to correct me,
    as the only system transfer I did, was before I got a Gateway.
     
  5. MelonGx
    OP

    MelonGx GBAtemp Advanced Maniac

    Member
    1,634
    439
    Jan 8, 2009
    China
    I'll say:
    1) When logging-in the e-shop, the 3DS console auto-deletes all same-region-contents haven't been purchased.
    2) Creating new emuNAND vanishes all CIAs so it will not have a CIA-transferring problem.
    3) I have already succeeded System Transferring an emuNAND with CIAs to a SysNAND. So it will be probably an emuNAND-to-emuNAND problem, or a hardware problem, more than a CIA-transferring problem.

    Anyway, I'm going to log-in new-source-emuNAND's e-shop to completely avoid it. Thanks for your advice.
     
  6. lebad

    lebad Advanced Member

    Newcomer
    86
    19
    Nov 10, 2009
    Luxembourg
    Hi do you know if we could perform a system transfer on a new 3ds 9.2 using a normal 3ds 9.2 without updating the firmwares ?
     
  7. Yoshi9288

    Yoshi9288 GBAtemp Regular

    Member
    104
    33
    Jun 3, 2008
    Germany
    Not possible, both Consoles must be up to date. In this case 9.4.0-21 to do an System Transfehr.
     
  8. troa11

    troa11 Older Than You

    Member
    248
    71
    Apr 11, 2006
    United States
  9. MelonGx
    OP

    MelonGx GBAtemp Advanced Maniac

    Member
    1,634
    439
    Jan 8, 2009
    China
    The Step 3/5 failure happened during your step 3.
    If you never saw that, then it could be my hardware problem.
    BTW, my source console is downgraded 4.4 + emuNAND 9.4s. My target is native 4.4 + emuNAND 9.4s.
    Tomorrow I can go for another SystemTransfer from source to another target DG44-emu94.
     
  10. MelonGx
    OP

    MelonGx GBAtemp Advanced Maniac

    Member
    1,634
    439
    Jan 8, 2009
    China
    Problem solved.
    It was a hardware problem.
    I changed the target 3DS console then it fixed.