You should be able to just use the saves you care about if you don't want to copy over all your old data. You can't just move the ticket.db of one system to another, as the tickets stored in the file are encoded with the unique identifier of the source console. There is not, as of yet, a proper method for us to write our own complete entries as Nintendo does to the ticket.db file. It is odd that the friend code changed. Some file/piece of information must not have been copied over when you did the process. You may be able to try copying the Friends module save from the source system to the target system again and see if the friend code properly shows up. I am not sure if it is possible to do this transfer method between regions. Did you have all appropriate Mii Plaza updates/DLC installed to match your saves? The saves would show as corrupt/inaccessible if you didn't have the matching Mii Plaza updates/DLC installed as well (I had this same issue during my testing, but my saves worked after installing the corresponding updates/DLC). The guide isn't out of date and vague so much as it is written in a very general manner to outline the basic Manual Transfer process so people can apply the overall concept to many different possible tools/methods, past, present and future. In this way, the overall spirit/message of the guide stays up to date, allowing people to apply the process to new systems/versions/tools as the state of the 3DS homebrew scene progresses. Also, the method for generating Xorpads really hasn't changed significantly between system versions, so the newest version of Decrypt9WIP (https://github.com/d0k3/Decrypt9WIP/releases) should be adequate. Is your target system on 10.6 SysNAND? If it is on 10.6 SysNAND, you would need to downgrade the system to 9.2 SysNAND and then create and update an EmuNAND to 10.6 (or now newest 10.7) to follow this Manual Transfer process.