3DS:System Transfer: Difference between revisions

(One intermediate revision by the same user not shown)

Line 1:

Doing a System Transfer with homebrew is possible, but titles that were not downloaded from the eShop will temporarily disappear at the end.

=== Does the target console have custom firmware? ===

== Does the target console have custom firmware? ==

~~{{Buttonlist|~~

=== Yes ===

* {{Clickable button 2|/Target has CFW|Yes, my new console already has CFW|class=mw-ui-progressive}}

* {{Clickable button 2|/Target ~~is stock~~|~~No, my new~~ console ~~has no CFW~~|class=mw-ui-~~destructive~~}}

{{Clickable button 2|/Target has CFW|Yes, my new console already has CFW|class=mw-ui-progressive}}

}}

=== No ===

It is highly recommended that you set up CFW first using [[3dsguide:|3DS Hacks Guide]]. This will make it easier to restore software after the transfer.

{{Clickable button 2|/Target has CFW|I have set up CFW on the target console|class=mw-ui-progressive}}

== FAQ ==

=== Is setting up CFW first really required? ===

Strictly speaking it is not. In this case any software that was not purchased and downloaded from Nintendo eShop will be invisible and not fixable until CFW is installed.

Since it is more convenient and sometimes easier to set up custom firmware on a freshly-formatted console, it is recommended to set it up first.

=== Is there a workaround for the 7-day cooldown? ===

No, this is enforced server-side.

[[Category:Nintendo 3DS information]]