[Help] Error code 028-3136 during DSiWare Save Injection system transfer

Discussion in '3DS - Flashcards & Custom Firmwares' started by Doogie Boogie, Aug 8, 2017.

  1. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    I did a system transfer for the DSiware save exploit:
    https://3ds-guide.b4k.co/installing-boot9strap-(dsiware-save-injection)

    Source: Old 3DS XL
    Target: New 2DS XL

    I followed all steps successfully and picked picked PC-Based Transfer as the method. After transfer the source 3DS said transfer was successful. Target finished the transfer then tried to connect to the router again and I got error code 028-3136.

    What went wrong? The target was not connected to my NNID after the transfer. It also did not download any save files. On the source system there is a new folder in exdata called "Nintendo DSiWare" with a .bin file called "4B513945". It's not on the target system.

    Can anyone explain to me what went wrong? And can someone also tell me why Plailect didn't include any troubleshooting for this error in the guide? Was this due to using the PC transfer method as the guide suggested?

    The game I used for injection was Four Swords, if that matters at all. The exploit was successfully added to the game but it did not transfer to the target 3DS.
     


  2. Joom

    Joom  ❤❤❤

    Member
    3,703
    2,471
    Jan 8, 2016
    United States
    Did you legitimately purchase 4 Swords before it was pulled from the eShop? You can't use a pirated copy.
     
  3. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    Yes its legitimate.
     
  4. Joom

    Joom  ❤❤❤

    Member
    3,703
    2,471
    Jan 8, 2016
    United States
    Last edited by Joom, Aug 8, 2017
  5. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    I was right next to the router when doing the transfer and had 3 bars on both systems. I don't know what else I could do to improve the connection beyond that.
     
  6. Joom

    Joom  ❤❤❤

    Member
    3,703
    2,471
    Jan 8, 2016
    United States
    This error is apparently common. If you Google the error code there are a lot of people that have experienced it. Seems like all you can do is restore the NAND of your source console and reattempt the transfer.
     
  7. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    That sucks but it would at least be nice to know what went wrong so that in 7 days I can keep the error from happening again. I don't even know what happened or how to prevent it. Maybe use wireless transfer instead of PC based transfer next time? I don't know what else I could do.
     
  8. Quantumcat

    Quantumcat Dead and alive

    Member
    9,832
    5,137
    Nov 23, 2014
    Australia
    Canberra, Australia
    Are you sure it is making you wait seven days? If the transfer failed it might not impose that restriction.
     
  9. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    I'll check, but the NNID is not on the source 3DS. It moved to the target. I just had to log in on the target for it to take effect. I'm fairly sure if that is the case, server side, the transfer was completed. I can always check but I don't think I can use a 3DS disconnected from a NNID as a source 3DS during a transfer. There is no harm in trying, I just assume it won't work.

    Update: Transfer was completed server side. I have to wait 6 days.
     
    Last edited by Doogie Boogie, Aug 9, 2017
  10. Quantumcat

    Quantumcat Dead and alive

    Member
    9,832
    5,137
    Nov 23, 2014
    Australia
    Canberra, Australia
    So, the transfer did work? Did you try moving the game again? (Backup NAND on source, move to SD in source, put SD in target, move to system on target)?
     
  11. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    Aren't DSIware games installed on the NAND though? I can download the game easily on the target but it's the save I need and it doesn't seem to be in the system memory.
     
  12. Quantumcat

    Quantumcat Dead and alive

    Member
    9,832
    5,137
    Nov 23, 2014
    Australia
    Canberra, Australia
    Just inject the save again on the source. Move it to SD, then move it to system on the target. Restore the pre-transfer NAND backup and the game will come back on the source.
     
  13. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    So what you're saying is, just so I'm clear:

    -inject the save
    -move the save onto the SD card
    -move the contents of the SD card over to the micro SD card of the target
    -download the DSiware game on the target to the SD card and not the system memory

    And then when I open the game it should use the exploit and I can install b9s. If I'm understanding you correctly? Or are you just explaining what I can do once I'm able to transfer again?
     
  14. squall14716

    squall14716 GBAtemp Maniac

    Member
    1,086
    601
    May 16, 2011
    United States
    Quantumcat likes this.
  15. Olmectron

    Olmectron GBAtemp Addict

    Member
    2,040
    1,239
    Dec 31, 2012
    Mexico
    A game
    Follow the troubleshooting @squall14716 shared. Before doing so, you must have restored the NAND backup to the source 3DS. This backup should have been done when following the actual DSiWare transfer guide in 3ds.guide, right before the transfer.
     
  16. Quantumcat

    Quantumcat Dead and alive

    Member
    9,832
    5,137
    Nov 23, 2014
    Australia
    Canberra, Australia
    No.

    1. Inject the save like you did in the beginning of the guide
    2. Go to System Settings -> Data Management -> DSiWare
    3. Choose to move the game to the SD card
    4. Put this SD card in the target
    5. Go yo System Settings ->Data Management -> DSiWare
    6. Choose to move the game to the system memory
    This is probably explained in the troubleshooting section linked above.
     
  17. Doogie Boogie
    OP

    Doogie Boogie Member

    Newcomer
    30
    19
    Jan 21, 2016
    United States
    I can't place the source SD card into the target because the source is an O3DSXL and the target is a N2DSXL. I would have to move the contents of one card over to the other.
     
    Olmectron likes this.
  18. Olmectron

    Olmectron GBAtemp Addict

    Member
    2,040
    1,239
    Dec 31, 2012
    Mexico
    A game
    Well, yes. Do that.
     
    Quantumcat likes this.
  19. Quantumcat

    Quantumcat Dead and alive

    Member
    9,832
    5,137
    Nov 23, 2014
    Australia
    Canberra, Australia
    If you never moved the SD card this would explain why the game never showed up.
     
  20. Olmectron

    Olmectron GBAtemp Addict

    Member
    2,040
    1,239
    Dec 31, 2012
    Mexico
    A game
    Just to add. If you did follow the System Transfer instructions (and 3ds.guide´s), you should have know to move the contents from one SD card to the other by using a PC (like you said).

    It should work. Give it a try.
     
    Quantumcat likes this.