Toggle search
Toggle menu
283
265
380
6.1K
Hacks Guide Wiki
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

3DS:System Transfer/Target is stock: Difference between revisions

From Hacks Guide Wiki
More actions
(removed Picross requirement, fixed typos and revised info, removed page WIP (system transfer section WIP still active))
(add steps that (mostly) account for a wireless transfer)
Line 47: Line 47:
=== Section III - System Transfer ===
=== Section III - System Transfer ===


{{Section WIP|notes=Steps if someone could not use "PC-Based Transfer"}}
# Perform the system transfer as usual. If at all possible, choose a "PC-Based Transfer".
#* If you cannot follow a PC-Based Transfer and must instead use a Wireless Transfer, be aware that with this method, homebrew software, cartridge dumps, and any other data only obtainable with CFW will not be transferred over.<br>If you choose a Wireless Transfer anyway, you will need to take extra steps to move over the lost data. '''Select "Do not delete" during the transfer to preserve all data on the source system, or else you will have to reobtain all lost data again by hand.'''


# Perform the system transfer as usual.
#* It is recommended to use "PC-Based Transfer" if possible, especially if transferring from an Old 3DS to a New 3DS. The "Wireless Transfer" option is very slow (taking up to 2 hours to transfer 1GB depending on conditions - an Old 3DS to New 3DS will always be on the slower end)


{{info|text='''The source console is finished.''' The following pages can be performed on '''the target console only'''.}}
=== Next Steps - Branching of the Way ===
Were you able to perform a '''PC-Based Transfer''' in Section III?
----
<tabber>
 
|-|Yes=
{{info|text='''The source console is finished.''' The following pages should only be performed on '''the target console'''.}}
 
{{success|image=none|text='''Continue to [[3dsguide:installing-boot9strap-(usm)|Installing boot9strap (USM)]]'''}}


== After the setup ==
After CFW is installed, place [[3DS:faketik|'''faketik''']] on the console's SD card. After this, once you finish Section IV of [[3dsguide:finalizing-setup|Finalizing Setup]], run '''faketik''' before opening FBI. This will restore all homebrew applications that disappeared after the transfer.


You will want to use [[3DS:faketik|'''faketik''']] to restore homebrew applications that disappear after the transfer. You should do this after "Finalizing Setup".
|-|No=
{{Section WIP|notes=Provide more detailed instructions on how to use ninfs.}}


----
{{success|image=none|text='''Continue to [[3dsguide:installing-boot9strap-(usm)|Installing boot9strap (USM)]], but return here immediately after finishing that page'''}}
 
If you were not able to perform a PC-Based Transfer, you will want to manually restore all the homebrew data <u>after CFW is installed but before following Finalizing Setup</u>.<br>
To do this, do the following:
# Copy all folders other than <code>Nintendo 3DS</code> and <code>DCIM</code> from the '''source console's''' SD card onto the '''target console's''' SD card.
# Insert the '''source console's''' SD card into your PC, mount its <code>Nintendo 3DS</code> folder using [[ninfs]], and copy out all games/savedata that was not transferred onto the '''target console'''.
# Unmount the '''source console''', mount the '''target console''' in ninfs, and copy all obtained games/savedata into the '''target console's''' <code>Nintendo 3DS</code> folder.
# [[3DS:Rebuild Title Database|Rebuild title.db]] on the '''target console''' to force all the new games/savedata to appear.


{{success|image=none|text='''Continue to [[3dsguide:installing-boot9strap-(usm)|Installing boot9strap (USM)]]'''}}
</tabber>


[[Category:Nintendo 3DS guides]]
[[Category:Nintendo 3DS guides]]

Revision as of 07:35, 9 April 2023

Due to seedminer being the current exploit method, it is easier to perform a System Transfer before setting up custom firmware on the target console. Dumping the source console's movable.sed before performing the transfer means that seedminer can be bypassed entirely on the target console after.

If the target console does already has CFW, follow this guide instead.

What You Need

  • The latest release of GodMode9 (the GodMode9 .zip file)

Instructions

Section I - Prep Work

  • For the source console only, perform the following steps:
    1. Power off your device
    2. Insert your SD card into your computer
    3. Copy GodMode9.firm from the GodMode9 .zip to the /luma/payloads/ folder on your SD card
    4. Copy the gm9 folder from the GodMode9 .zip to the root of your SD card
    5. Reinsert your SD card into your device

Section II - NAND Backup and movable.sed

  1. Press and hold Start, and while holding Start, power on your device. This will launch GodMode9
  2. Press Home to bring up the action menu
  3. Select "Scripts..."
  4. Select "GM9Megascript"
  5. Select "Dump Options"
  6. Select "System File Dump Options"
  7. Select "Dump movable.sed"
  8. Press A to confirm
  9. Press A to continue
  10. Press B twice to return to the main menu
  11. Select "Backup Options"
  12. Select "SysNAND Backup"
  13. Press A to confirm
    • This process will take some time
    • If you get an error, make sure that you have at least 1.3GB of free space on your SD card
  14. Press A to continue
  15. Press B to return to the main menu
  16. Select "Exit"
  17. Press A to relock write permissions if prompted
  18. Press and hold R, then press Start to power off your device
  19. Insert your SD card into your computer
  20. Copy <date>_<serialnumber>_sysnand_00.bin, <date>_<serialnumber>_sysnand_00.bin.sha, and <serialnumber>_movable_00.sed> from /gm9/out to a safe place on your computer, then delete the .bin and .bin.sha files from the SD card
  21. Reinsert your SD card into your device
OOjs UI icon information-progressive.svg The above files should be kept safe, preferably in multiple locations. Use the movable.sed for tools like PicHaxx Injector or unSAFE_MODE Exploit Injector.

Section III - System Transfer

  1. Perform the system transfer as usual. If at all possible, choose a "PC-Based Transfer".
    • If you cannot follow a PC-Based Transfer and must instead use a Wireless Transfer, be aware that with this method, homebrew software, cartridge dumps, and any other data only obtainable with CFW will not be transferred over.
      If you choose a Wireless Transfer anyway, you will need to take extra steps to move over the lost data. Select "Do not delete" during the transfer to preserve all data on the source system, or else you will have to reobtain all lost data again by hand.


Next Steps - Branching of the Way

Were you able to perform a PC-Based Transfer in Section III?

OOjs UI icon information-progressive.svg The source console is finished. The following pages should only be performed on the target console.
Continue to Installing boot9strap (USM)
After CFW is installed, place faketik on the console's SD card. After this, once you finish Section IV of Finalizing Setup, run faketik before opening FBI. This will restore all homebrew applications that disappeared after the transfer.

Continue to Installing boot9strap (USM), but return here immediately after finishing that page

If you were not able to perform a PC-Based Transfer, you will want to manually restore all the homebrew data after CFW is installed but before following Finalizing Setup.
To do this, do the following:

  1. Copy all folders other than Nintendo 3DS and DCIM from the source console's SD card onto the target console's SD card.
  2. Insert the source console's SD card into your PC, mount its Nintendo 3DS folder using ninfs, and copy out all games/savedata that was not transferred onto the target console.
  3. Unmount the source console, mount the target console in ninfs, and copy all obtained games/savedata into the target console's Nintendo 3DS folder.
  4. Rebuild title.db on the target console to force all the new games/savedata to appear.
Retrieved from "https://wiki.hacks.guide/w/index.php?title=3DS:System_Transfer/Target_is_stock&oldid=3108"