1. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    Hey folks, so I was finally able to send my niece's 2DS in for a warranty repair. It had a physical hardware issue just a couple of months after purchasing it.
    Before sending it in, I used Godmode9 and backed up the NAND. I wasn't clear on game saves, so when I was uninstalling games I may have deleted save files.
    Nintendo sent a new unit with a different serial number so I guess I'm starting at square one. My questions are: 1. Does having the backed up NAND simplify the process
    of installing Luma3DS again? 2. Does a new board mean I have to start over regardless and disregard the NAND because it will be coded differently? 3. What about game
    saves in the case that the NAND is useable? Would they be saved there as well? Do I reinstall games?

    Not sure if I should just redo the whole process from scratch at this point. Any suggestions are much appreciated. My niece has been patiently waiting for months throughout lockdowns etc and I want to get the 2DS back in her hands ASAP>Thanks!
     
    Last edited by intromission, Jul 10, 2020
  2. Hayato213

    Hayato213 GBAtemp Guru
    Member

    Joined:
    Dec 26, 2015
    Messages:
    7,627
    Country:
    United States
    The previous system NAND is no use if they send you a new unit, NAND are console specific, so you can't restore the one you made.
     
  3. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    I thought so, thank you! Looks like I'll be starting over.
     
  4. TurdPooCharger

    Member

    Joined:
    Jan 1, 2018
    Messages:
    6,729
    Country:
    United States
    DarkDengar likes this.
  5. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    I still have to manually reinstall all games though don't I?
     
  6. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    Ok, so this is weird. Just wondering how it changes my situation. I powered on the 2ds, prepared to go through the CFW install again, I'm glad I checked a couple of things. First, I realized that the 2ds didn't go through the first time sign in and new user creation, so I started looking and realized the Parental Code was still in place, used the password I created and it worked, then I checked in the MII app and saw my niece's characters.

    So it looks like maybe only the case was changed that has a new serial number. The board must be the same. The repair was for the charging port, so not sure what would have been involved.

    Does this change things? Can I use the NAND back up? The last thing I want to do is screw this up now. Does the NAND back-up eliminate the need to reinstall games?

    Also, I can't remember what Version I had back when I installed Luma3ds. Everything was successful back in October and my niece enjoyed it without issues. Presently it says Version. 11-13-0-45U. How would I know if they downloaded an update while they had it? And how might that affect the process with NAND restore?

    Thanks!
     
  7. Hayato213

    Hayato213 GBAtemp Guru
    Member

    Joined:
    Dec 26, 2015
    Messages:
    7,627
    Country:
    United States
    If you are not 100% it is the same board then don't do the NAND restore even if you have it, restore a NAND from another unit would just brick. You can try what TurdPooCharger recommended.
     
  8. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    So if those settings and my password, and the MII characters from before were there though, as well as not being prompted to go through the welcome screens on first powering up, wouldn't that indicate 100% that it is the same board/same nand? There is no SD card inserted at the moment. System memory should be part of the board right?

    The notes from Nintendo say:
    Service performed:
    Cleaned, tested and inspected all components.
    Exchanged Min Unit.
     
    Last edited by intromission, Jul 18, 2020
  9. Hayato213

    Hayato213 GBAtemp Guru
    Member

    Joined:
    Dec 26, 2015
    Messages:
    7,627
    Country:
    United States
    You wouldn't know unless you 100% match the serial #.
     
  10. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    Would the tech be able to copy those things over to a new console?
     
  11. Hayato213

    Hayato213 GBAtemp Guru
    Member

    Joined:
    Dec 26, 2015
    Messages:
    7,627
    Country:
    United States
    I assume they didn't or you would have the data when you got back the unit.
     
  12. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    I don't think I'm following you, sorry. I DO have that data though.
     
  13. Hayato213

    Hayato213 GBAtemp Guru
    Member

    Joined:
    Dec 26, 2015
    Messages:
    7,627
    Country:
    United States
    If they did copy the data over while servicing it you would see the data on the new unit, seem like they just give you a replacement that all.
     
  14. TurdPooCharger

    Member

    Joined:
    Jan 1, 2018
    Messages:
    6,729
    Country:
    United States
    @intromission,
    1. Did Nintendo uninstall the custom firmware? Does Luma3DS v#.# configuration shows up when holding the (SELECT) button turning the o2DS on?
    2. Has the console unique KeyY encryption changed? Inserting a different SD card into the o2DS, are the <ID0> folders the same between the second and main card?
      • [​IMG]
    3. Have you attempted to decrypt, extract, and re-encrypt the Nintendo 3DS folder with ninfs {computer} and/or GodMode9 {3DS system} as described in the SDTransfer methods (post #4)?
     
  15. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    Thanks @TurboPooCharger.

    1. So, I used GMode9 to uninstall CFW before sending it in. I created the NAND backup and then deleted anything that was advised for removal, then swapped the orginal 4GB SD Card back in and kept my 32GB card with all the CFW stuff. When I hold select and power on, it turns on normally.
    2. I deleted everything on the original 4GB SD sent back with the 2ds, and inserted it. The folder created says Nintendo 3ds, when I open that folder, I see 1 folder 635dd350c186f95b848b...d66b2a, when I click on THAT folder, I see another folder: da71010a4738b9c05345...02544d. I then put in my 32GB with CFW on it, spot the Nintento 3ds folder, open it, 2 folders there, one matches the other SD card-635dd350c186f95b848b...d66b2a, the ,other says Private. When I click on 635dd350c186f95b848b...d66b2a, the next folder says 57aa0108301020f630303...1b534d, that folder contains 4 subfolders: DBS, EXTDATA, NINTENDO DSIWARE, and TITLE. The second "Private" folder opens up a numerical folder that then ends up at a .bin file phtcache.
    3. I have not tried this. I'll wait for your response on whether I should or not.

    Hope that helps.
     
    Last edited by intromission, Jul 19, 2020
  16. TurdPooCharger

    Member

    Joined:
    Jan 1, 2018
    Messages:
    6,729
    Country:
    United States
    You will need to first reinstall custom firmware on your niece's o2DS before doing anything else.
    After that o2DS has boot9strap, Luma3DS, GodMode9, FBI, etc. up and running again, you will then need to find and isolate the exact folder chain that contains your niece's library of games from that main SD card.
    • sdmc:/Nintendo 3DS/<ID0>/<ID1>/
      • dbs
      • extdata
      • title/
        • 00040000 (games)
        • 0004000e (updates)
        • 0004008c (DLCs)
    1. :!: Do not merge different <ID0> and <ID0> parent folders together.
    2. :!: Do not rename the <ID0> to a different <ID0>.
    3. :!: Do not move the <ID1> child folder from its real <ID0> parent folder to another <ID0> parent folder.
    If you do any of these three (3) actions or variations of them, this will fuck up the original console unique KeyY<ID0> encryption, making it impossible to decrypt, extract, and re-encrypt the SD contents to the replacement o2DS new encryption.

    ***

    Once you find the correct sdmc:/Nintendo 3DS/<ID0>/<ID1> folder chain containing your niece's library of games, dlcs, updates, saves, and extdata, you're going to have to study and familiarize yourself in learning how to install and use that ninfs program.

    You will be hex viewing or image mounting the <MMDDYY>_<serial>_sysnand_###.bin image that was backed up before the o2DS was sent to Nintendo.
    1. Retrieve that original (source) movable.sed.
    2. Mount the Nintendo 3DS folder with that (source) movable.sed.
    3. Copy and paste the {decrypted} dbs, extdata, and title subfolders to your computer.
    4. Retrieve the replacement (target) movable.sed.
    5. Mount the {blank newly created} Nintendo 3DS folder with that (target) movable.sed.
    6. Copy and paste the dbs, extdata, and title subfolders from computer to this Nintendo 3DS folder. {Re-encryption}
    7. Use GodMode9 to correct the CMACs, faketik to restore missing tickets, and Cthulhu to mass unwrap gift icons.

    Refer to post #2 and post #14 for more details on how to do this.
    • :!: Do not under any circumstances restore the (source) movable.sed to the o2DS. This will fuck up access to online services like Nintendo eShop and Theme Shop. This is because that previous (source) movable.sed technically no longer belongs to your niece's replacement o2DS as far as Nintendo server records are concerned.
    • :!: If you take the "easy" route restoring the (source) movable.sed despite the above warning, just know there is a chance Nintendo may notice the discrepancy and decide to ban your o2DS from any further online services if they believe this is a case of stolen or masqueraded identity.

    Here's a thread that goes in depth in why certain NAND files should not restored, shared, cloned, or transferred between different 2DS/3DS systems.

    ***

    If your niece has user profile data (ie, Friend List, Activity Log, Notes, savedata from system titles) that are missing or not restored when signing back in and/or DSiWare games & saves, you will need to extract these constituent nand partition files from the <MMDDYY>_<serial>_sysnand_###.bin image to the o2DS SD card.
    • ctrnand_full.img
    • twln.img
    • twlp.img

    Before making any changes to the o2DS NAND, backup the current SysNAND for extra safety. In case of a poor edit or accident, you'll want to have this to recover from.

    To manually and selectively restore your niece's user setup,
    1. GodMode9 → press (A) on ctrnand_full.imgCTRNAND options...Mount image to drive.
    2. Go in the [7:] FAT IMAGE/data/<ID0> directory. Hold (L)-shoulder and press (RIGHT) d-pad to highlight select the extdata and sysdata subfolders in yellow.
    3. Press (Y) to [CLIPBOARD] select these two (2) folders. If a selection mistake has occurred, press (SELECT) to reset and try again.
    4. Back out with (B) button. Go in the [1:] SYSNAND CTRNAND/data/<ID0> directory. Press (Y) → Copy path(s)<A> yes → button combo → Overwrite all<A> yes.
    5. Back out with (B) button. While under [root], hold (R)-shoulder and press (A) on [1:] SYSNAND CTRNANDFix CMACs for drive<A> yes → button combo → <A> to continue<A> yes.

    To manually restore your niece's DSiWare games & saves,
    1. GodMode9 → press (A) on twln.imgMount as FAT image<A> yes.
    2. Go in the [7:] FAT IMAGE/title directory. Press (Y) on only the 00030004 folder. Do not [CLIPBOARD] select the other folders as those contain TWL system titles.
    3. Back out with (B) button. Go in the [2:] SYSNAND TWLN/title directory. Press (Y) → Copy path(s)Overwrite file(s) → etc.
    4. Add the gm9 script CTRTransfer (Type D9) to this directory. See further instructions in how to dump, reinstall/relist the DSiWare CIAs & saves in the below post.

    To manually restore your niece's photos made from Nintendo DSi Camera (if she has any),
    1. GodMode9 → press (A) on twlp.imgMount as FAT image<A> yes.
    2. Press (Y) on the photo folder to add item to [CLIPBOARD].
    3. Back out with (B) button. Go in the [3:] SYSNAND TWLP directory. Press (Y) → Copy path(s) → Overwrite file(s) → etc.

    :!: Do not deviate from the above instructions. Follow those steps as exactly as advised. Doing something else such as copying and pasting everything within those images to the o2DS NAND partitions,
    • can softbrick the 3DS firmware
    • permanently erase its console unique files that should never be replaced
    • risk receiving a future ban from Nintendo (ie, false identity)
     
    Last edited by TurdPooCharger, Jul 19, 2020
  17. intromission

    OP intromission Member
    Newcomer

    Joined:
    May 17, 2016
    Messages:
    20
    Country:
    United States
    Thank you! Looks like I have a lot of homework to do.
    Just to clarify, the numbers I gave for the ID0 and ID1 folders, do they indicate the motherboard was not in fact changed? What does it mean if both ID0 numbers match?

    Would I be correct in thinking it might just be easier to just go back and reinstall everything manually?
     
    Last edited by intromission, Jul 19, 2020
  18. TurdPooCharger

    Member

    Joined:
    Jan 1, 2018
    Messages:
    6,729
    Country:
    United States
    Matching <ID0> parent folder (before sending the o2DS in & how the o2DS makes it now), could imply the original motherboard was kept but most likely means the Nintendo repair technician System Transferred your niece's user setup to a different o2DS.

    If this o2DS makes the same <ID0> on that second SD card (litmus test), there's no need to decrypt, extract, and re-encrypt the Nintendo 3DS folder from the main SD card with ninfs or GodMode9. Just rehack the o2DS (:!: don't you dare follow a stupid, unofficial video guide that tells you to Format System Memory), run faketik, & unwrap the icons with Cthulhu. Easy-peasy.

    Any pirated/not legitimately bought on Nintendo eShop, DSiWare games & saves will still require the techniques described in the above posts as these do not cross over in a System Transfer.
     
    Last edited by TurdPooCharger, Jul 19, 2020
Loading...

Hide similar threads Similar threads with keywords - Restoring, backed,