Reply to thread

Message: <blockquote data-quote="Ichii Giki" data-source="post: 5478315" data-attributes="member: 362683">This is an annoying limitation, but for how I did it, it is required. Going full Gateway hasn't been that painful, especially with the new MSET downgrade option allowing for no more card swapping. I haven't even seen any noticeable battery drain from leaving in the Gateway card all the time. Also, using Gateway all the time allowed me to finally rip all my carts and now I don't have to carry any around, all installed on my EmuNAND! Convenient!  You can just move over the saves you want, but the problem with moving Mii Plaza and not Mii Maker is that the Mii Plaza data will be expecting your default Mii from the source system. I would recommend exporting your existing Miis on the target system with QR codes, copying the Mii Maker save as well, then re-importing your saved Miis from the QR codes. However, to reiterate about your original question, you can just move over the data you want from the source system (Mii Plaza/Activity Monitor/etc.) and it should be fine. Still, any existing saves on your target console would be invalidated/unreadable after the movable.sed change, so you would have to reset them.  I am aware of rxTools and I use it on my O3DS. I was just trying to give general instructions for each step that would be consistent from Source system to Target system. Note that each step of my tutorial is a general instruction (such as, "Dump/extract your Source NAND"), with many possible ways to accomplish the prescribed instruction (in this example, Gateway/Hardmod/EmuNANDTool/etc.). In this way, my High Level tutorial instructions can apply to many different scenarios (for example: a 9.x O3DS -> 9.x N3DS, or a 4.5 CFW O3DS -> 4.5 CFW O3DS). Ticket.db IS recommended for my scenario. The ticket.db file simply contains your tickets for all the titles you have purchased (albeit with your console ID encoded). However when you use a script such as "FunkyCIA2", this script downloads CIAs from Nintendo with your tickets so they can then be installed on another console with a different console ID. This is why I included this file in my tutorial. I assume in your tutorial you were transferring between systems of the same region, so your situation/requirements differed from my own. I understand your tutorial is more for transferring data after a failed, legit system transfer where at least your NNID does get moved to the Target system by Nintendo. My method was mostly born from the O3DS to region-changed N3DS scenario where a legit system transfer is not possible/extremely complex and moving over your NNID to the target system is very difficult. I bypass this by using an unsigned code execution option (like Gateway). I believe both tutorials are valid and serve different scenarios. Thank you for your input! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite51" alt="^_^" title="happy    ^_^" loading="lazy" data-shortname="^_^" /></blockquote>

Verification

Search

Search

Reply to thread

Settings Notifications

Options