3DS:System Transfer/Target is stock - Revision history

Ihaveahax: Replaced content with "{{mbox|type=content|text=This page has been temporarily removed because it is outdated. Set up custom firmware on the target console and follow 3DS:System Transfer/Target has CFW instead.}}"

2023-10-04T20:58:16Z

Replaced content with "{{mbox|type=content|text=This page has been temporarily removed because it is outdated. Set up custom firmware on the target console and follow 3DS:System Transfer/Target has CFW instead.}}"

← Older revision		Revision as of 20:58, 4 October 2023
Line 1:		Line 1:
	{{~~System version outdated article~~\|~~console~~=~~ctr~~\|~~sysversion~~=~~11.16.0-49}}~~		{{mbox\|type=content\|text=This page has been temporarily removed because it is outdated. Set up custom firmware on the target console and follow [[3DS:System Transfer/Target has CFW]] instead.}}

	~~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 <code>movable.sed</code> 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 [[../Target has CFW~~\|this guide~~]] instead.

	~~== What You Need ==~~
	* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9] (the GodMode9 <code>.zip</code> file)

	~~== Instructions ==~~

	~~=== Section I - Prep Work ===~~

	* For '''the source console only''', perform the following steps:
	*# Power off your device
	*# Insert your SD card into your computer
	*# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
	*# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
	*# Reinsert your SD card into your device

	~~=== Section II - NAND Backup and movable.sed ===~~

	~~# Press and hold {{B\|Start}~~}~~, and while holding {{B\|Start~~}~~}, power on your device. This will launch GodMode9~~
	~~# Press {{B\|Home}} to bring up the action menu~~
	~~# Select "Scripts..."~~
	~~# Select "GM9Megascript"~~
	~~# Select "Dump Options"~~
	~~# Select "System File Dump Options"~~
	~~# Select "Dump movable.sed"~~
	~~# Press {{B\|A}} to confirm~~
	~~# Press {{B\|A}} to continue~~
	~~# Press {{B\|B}} twice to return to the main menu~~
	~~# Select "Backup Options"~~
	~~# Select "SysNAND Backup"~~
	~~# Press {{B\|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~~
	~~# Press {{B\|A}} to continue~~
	~~# Press {{B\|B}} to return to the main menu~~
	~~# Select "Exit"~~
	~~# Press {{B\|A}} to relock write permissions if prompted~~
	~~# Press and hold {{B\|R}}, then press {{B\|Start}} to power off your device~~
	~~# Insert your SD card into your computer~~
	# Copy <code><date>_<serialnumber>_sysnand_00.bin</code>, <code><date>_<serialnumber>_sysnand_00.bin.sha</code>, and <code><serialnumber>_movable_00.sed></code> from <code>/gm9/out</code> to a safe place on your computer, then delete the <code>.bin</code> and <code>.bin.sha</code> files from the SD card
	~~# Reinsert your SD card into your device~~

	~~{{info\|text=The above files should be kept safe, preferably in multiple locations. Use the <code>movable.sed</code> for tools like PicHaxx Injector or unSAFE_MODE Exploit Injector.}}~~

	~~=== Section III - System 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.'''


	~~=== 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:bannerbomb3\|BannerBomb3]]'''}}~~

	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.

	~~\|-\|No=~~
	~~{{Section WIP\|notes=Provide more detailed instructions on how to use ninfs.}}~~

	~~{{success\|image=none\|text='''Continue to [[3dsguide:bannerbomb3\|BannerBomb3]], but return here immediately after CFW is installed'''}}~~

	~~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.~~

	~~</tabber>~~

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

Lily: add outdated notice

2023-08-03T23:27:24Z

add outdated notice

← Older revision		Revision as of 23:27, 3 August 2023
Line 1:		Line 1:
			{{System version outdated article\|console=ctr\|sysversion=11.16.0-49}}

	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 <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.		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 <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.

StarlitSkies: this jumps too far ahead in the guide. direct to bannerbomb3 instead

2023-04-09T07:51:48Z

this jumps too far ahead in the guide. direct to bannerbomb3 instead

← Older revision		Revision as of 07:51, 9 April 2023
Line 59:		Line 59:
	{{info\|text='''The source console is finished.''' The following pages should only be performed on '''the target console'''.}}		{{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)~~]]'''}}		{{success\|image=none\|text='''Continue to [[3dsguide:bannerbomb3\|BannerBomb3]]'''}}

	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.		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.
Line 66:		Line 66:
	{{Section WIP\|notes=Provide more detailed instructions on how to use ninfs.}}		{{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~~'''}}		{{success\|image=none\|text='''Continue to [[3dsguide:bannerbomb3\|BannerBomb3]], but return here immediately after CFW is installed'''}}

	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>		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>

StarlitSkies: add steps that (mostly) account for a wireless transfer

2023-04-09T07:35:17Z

add steps that (mostly) account for a wireless transfer

← Older revision		Revision as of 07:35, 9 April 2023
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]]

StarlitSkies: removed Picross requirement, fixed typos and revised info, removed page WIP (system transfer section WIP still active)

2022-09-23T03:43:24Z

removed Picross requirement, fixed typos and revised info, removed page WIP (system transfer section WIP still active)

← Older revision		Revision as of 03:43, 23 September 2022
Line 1:		Line 1:
	~~{{Page WIP\|notes=Check that this actually makes sense? I might have missed some important steps...}}~~		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 <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.
	~~{{System version outdated article\|console=ctr\|sysversion=11.16.0-49\|reason=''New update may have changed the need for seedminer.''}}~~
	Due to seedminer being the current exploit method, it is easier to perform a System Transfer ~~first,~~ before setting up custom firmware on the target console. Dumping the source console's <code>movable.sed</code> 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 [[../Target has CFW\|this guide]] instead.		If the target console does already has CFW, follow [[../Target has CFW\|this guide]] instead.

	== What You Need ==		== What You Need ==
	* The game "Pokémon Picross" (free on eShop) installed on the source device
	** You can scan [http://api.qrserver.com/v1/create-qr-code/?color=000000&bgcolor=FFFFFF&data=ESHOP://50010000037815&margin=0&qzone=1&size=400x400&ecc=L this QR code] using the Nintendo 3DS Camera for a direct link to the eShop app
	** Your SD card must be inserted in your device to install Pokémon Picross
	* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9] (the GodMode9 <code>.zip</code> file)		* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9] (the GodMode9 <code>.zip</code> file)

Line 21:		Line 16:
	*# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card		*# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
	*# Reinsert your SD card into your device		*# Reinsert your SD card into your device
	*# Power on your device

	=== Section II - NAND Backup and movable.sed ===		=== Section II - NAND Backup and movable.sed ===
Line 39:		Line 33:
	# Press {{B\|A}} to confirm		# Press {{B\|A}} to confirm
	#* This process will take some time		#* This process will take some time
	#* If you get an error, make sure that you have at least 1.3GB of free ~~spaec~~ on your SD card		#* If you get an error, make sure that you have at least 1.3GB of free space on your SD card
	# Press {{B\|A}} to continue		# Press {{B\|A}} to continue
	# Press {{B\|B}} to return to the main menu		# Press {{B\|B}} to return to the main menu
	# Select "Exit"		# Select "Exit"
	# Press {{B\|A}} to relock write permissions if prompted		# Press {{B\|A}} to relock write permissions if prompted
			# Press and hold {{B\|R}}, then press {{B\|Start}} to power off your device
			# Insert your SD card into your computer
			# Copy <code><date>_<serialnumber>_sysnand_00.bin</code>, <code><date>_<serialnumber>_sysnand_00.bin.sha</code>, and <code><serialnumber>_movable_00.sed></code> from <code>/gm9/out</code> to a safe place on your computer, then delete the <code>.bin</code> and <code>.bin.sha</code> files from the SD card
			# Reinsert your SD card into your device

	{{info\|text=~~Your~~ <code>movable.sed</code> ~~file is now available at <code>/gm9/out/</code> with a name that looks like <code><serialnumber>_movable_##.sed</code>. Use this~~ for tools like PicHaxx Injector.}}		{{info\|text=The above files should be kept safe, preferably in multiple locations. Use the <code>movable.sed</code> for tools like PicHaxx Injector or unSAFE_MODE Exploit Injector.}}

	=== Section IV - System Transfer ===		=== Section III - System Transfer ===

	{{Section WIP\|notes=Steps if someone could not use "PC-Based Transfer"}}		{{Section WIP\|notes=Steps if someone could not use "PC-Based Transfer"}}

	# Perform the system transfer as usual		# Perform the system transfer as usual.
	#* ~~If this is from an Old 3DS to a New 3DS, it~~ is ~~best~~ to use "PC-Based Transfer", ~~unless it is impossible~~ to do. The "Wireless Transfer" option is very slow (taking ~~about~~ 2 hours to transfer 1GB)		#* 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'''.}}		{{info\|text='''The source console is finished.''' The following pages can be performed on '''the target console only'''.}}

Ihaveahax: 11.16.0-49

2022-09-13T10:15:43Z

11.16.0-49

← Older revision		Revision as of 10:15, 13 September 2022
Line 1:		Line 1:
	{{Page WIP\|notes=Check that this actually makes sense? I might have missed some important steps...}}		{{Page WIP\|notes=Check that this actually makes sense? I might have missed some important steps...}}
	{{System version outdated article\|console=ctr\|sysversion=11.16.0-48\|reason=''New update may have changed the need for seedminer.''}}		{{System version outdated article\|console=ctr\|sysversion=11.16.0-49\|reason=''New update may have changed the need for seedminer.''}}
	Due to seedminer being the current exploit method, it is easier to perform a System Transfer first, before setting up custom firmware on the target console. Dumping the source console's <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.		Due to seedminer being the current exploit method, it is easier to perform a System Transfer first, before setting up custom firmware on the target console. Dumping the source console's <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.

Ihaveahax: /* After the setup */ swap pichaxx link for USM

2022-09-08T04:18:32Z

After the setup: swap pichaxx link for USM

← Older revision		Revision as of 04:18, 8 September 2022
Line 62:		Line 62:
	----		----

	{{success\|image=none\|text='''Continue to [[3dsguide:installing-boot9strap-(~~pichaxx~~)\|Installing boot9strap (~~PicHaxx~~)]]'''}}		{{success\|image=none\|text='''Continue to [[3dsguide:installing-boot9strap-(usm)\|Installing boot9strap (USM)]]'''}}

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

Ihaveahax: update version

2022-08-31T07:27:34Z

update version

← Older revision		Revision as of 07:27, 31 August 2022
Line 1:		Line 1:
	{{Page WIP\|notes=Check that this actually makes sense? I might have missed some important steps...}}		{{Page WIP\|notes=Check that this actually makes sense? I might have missed some important steps...}}
	{{System version outdated article\|console=ctr\|sysversion=11.15.0-47\|reason=''New update may have changed the need for seedminer.''}}		{{System version outdated article\|console=ctr\|sysversion=11.16.0-48\|reason=''New update may have changed the need for seedminer.''}}
	Due to seedminer being the current exploit method, it is easier to perform a System Transfer first, before setting up custom firmware on the target console. Dumping the source console's <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.		Due to seedminer being the current exploit method, it is easier to perform a System Transfer first, before setting up custom firmware on the target console. Dumping the source console's <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.

Ihaveahax: Undo revision 1908 by Ihaveahax (talk)

2022-08-31T07:27:02Z

Undo revision 1908 by Ihaveahax (talk)

@@ Line 1: / Line 1: @@
-{{ombox
+{{Page WIP|notes=Check that this actually makes sense? I might have missed some important steps...}}
-| type = speedy
+{{System version outdated article|console=ctr|sysversion=11.15.0-47|reason=''New update may have changed the need for seedminer.''}}
-| image = [[File:Gnome-software-update-available.svg|40px|link=]]
+Due to seedminer being the current exploit method, it is easier to perform a System Transfer first, before setting up custom firmware on the target console. Dumping the source console's <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.
-| text = <big>'''This guide will NOT work with the latest system version!'''</big><br>Until things are sorted out, you should set up homebrew and custom firmware BEFORE the transfer, and then follow [[3DS:System Transfer/Target has CFW]].
-}}
+If the target console does already has CFW, follow [[../Target has CFW|this guide]] instead.
-The old steps were removed for the time being. Look at [[Special:PageHistory/{{FULLPAGENAME}}]] to look at them again.

Ihaveahax: replace with notice

2022-08-30T02:09:57Z

replace with notice

@@ Line 1: / Line 1: @@
-{{Page WIP|notes=Check that this actually makes sense? I might have missed some important steps...}}
+{{ombox
-{{System version outdated article|console=ctr|sysversion=11.15.0-47|reason=''New update may have changed the need for seedminer.''}}
+| type = speedy
-Due to seedminer being the current exploit method, it is easier to perform a System Transfer first, before setting up custom firmware on the target console. Dumping the source console's <code>movable.sed</code> before performing the transfer means that seedminer can be bypassed entirely on the target console after.
+| image = [[File:Gnome-software-update-available.svg|40px|link=]]
+| text = <big>'''This guide will NOT work with the latest system version!'''</big><br>Until things are sorted out, you should set up homebrew and custom firmware BEFORE the transfer, and then follow [[3DS:System Transfer/Target has CFW]].
-If the target console does already has CFW, follow [[../Target has CFW|this guide]] instead.
+}}
+The old steps were removed for the time being. Look at [[Special:PageHistory/{{FULLPAGENAME}}]] to look at them again.

← Older revision		Revision as of 07:51, 9 April 2023
Line 59:		Line 59:
	{{info\|text='''The source console is finished.''' The following pages should only be performed on '''the target console'''.}}		{{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)~~]]'''}}		{{success\|image=none\|text='''Continue to [[3dsguide:bannerbomb3\|BannerBomb3]]'''}}

	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.		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.
Line 66:		Line 66:
	{{Section WIP\|notes=Provide more detailed instructions on how to use ninfs.}}		{{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~~'''}}		{{success\|image=none\|text='''Continue to [[3dsguide:bannerbomb3\|BannerBomb3]], but return here immediately after CFW is installed'''}}

	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>		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>