3DS:System Transfer: Difference between revisions

From Hacks Guide Wiki
(Created page with "{{ambox | issue = This page is a work in progress. }} Doing a System Transfer with homebrew is possible, but titles that were not downloaded from the eShop will disappear at the end. == Target console does not already have CFW == {{System version outdated article|console=ctr|sysversion=11.15.0-47}} {{ambox | text = TODO: someone could dump movable.sed from their current console first, then transfer, then use pichaxx or something after and bypass seedminer entirely. Ma...")
 
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{ambox
Doing a System Transfer with homebrew is possible, but titles that were not downloaded from the eShop will temporarily disappear at the end.
| issue = This page is a work in progress.
}}


Doing a System Transfer with homebrew is possible, but titles that were not downloaded from the eShop will disappear at the end.
=== Does the target console have custom firmware? ===


== Target console does not already have CFW ==
{{Buttonlist|
{{System version outdated article|console=ctr|sysversion=11.15.0-47}}
* {{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}}
{{ambox
| text = TODO: someone could dump movable.sed from their current console first, then transfer, then use pichaxx or something after and bypass seedminer entirely. Maybe put steps here on how to set up pichaxx before the transfer?
}}
}}


== Target console already has CFW ==
[[Category:Nintendo 3DS information]]
 
If both consoles have CFW, follow the steps at [[/Target has CFW]].

Latest revision as of 07:28, 24 January 2023

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?