Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

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...")
 
No edit summary
Line 5: Line 5:
Doing a System Transfer with homebrew is possible, but titles that were not downloaded from the eShop will disappear at the end.
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 ==
=== Does the target console have custom firmware? ===
{{System version outdated article|console=ctr|sysversion=11.15.0-47}}


{{ambox
{{Buttonlist|
| 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?
* {{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}}
}}
}}
== Target console already has CFW ==
If both consoles have CFW, follow the steps at [[/Target has CFW]].

Revision as of 02:27, 18 June 2022

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?