Hacking System Transfer O3DS 9.9 to N3DS 9.5 possible?

[SpencerlyEverly]

NOTE: This is not a side answer to the 9.9 SysNAND to the 9.0 System Transfer thread.

Well, my time has come for me to about buy a N3DS that is Gateway compatible.

After mine is delivered, I'll start away with an unboxing video and setup about this 3DS which shows my face n' stuff. Then perhaps maybe a Sparta Madhouse ZE Remix of me beholding this N3DS (It'll be considered when I think about it). But my O3DS's EmuNAND has been region-changed to the Japan network, and I need to sign out/unlink the system and sign in/relink it with the old USA EmuNAND I used to have. Really, just need a tutorial.

But that's not all. I need to System Transfer it to the N3DS, but I am not totally sure if the AM patches from FreeMultiPatcher actually work on the System Transfer work.

So, before I do all that, does anybody confirm it works on FreeMultiPatcher?

Or should I wait until the RxTools N3DS support IF it works on 9.9 EmuNAND?

And I just realized something while I wrote this thread: I don't think FreeMultiPatcher works on Gateway. If that's true, tell me.

 

[Zidapi]

But that's not all. I need to System Transfer it to the N3DS, but I am not totally sure if the AM patches from FreeMultiPatcher actually work on the System Transfer work.

So, before I do all that, does anybody confirm it works on FreeMultiPatcher?

Or should I wait until the RxTools N3DS support IF it works on 9.9 EmuNAND?

And I just realized something while I wrote this thread: I don't think FreeMultiPatcher works on Gateway. If that's true, tell me.

FreeMultiPatcher will allow you to perform the system update without needing to be on the latest firmware. But, you're going to need a third exploitable old3DS or 2DS to act as a surrogate, because you're going to need to downgrade your source to 9.5 or a lower 9.x version.

The latest rxTools betas already support the new3DS, and while there seems to be issues running it from MSET, I'm launching it via Ninjhax and haven't encountered any bugs.

I can personally confirm that FreeMultiPatcher works just fine with Gateway.

 

[SpencerlyEverly]

FreeMultiPatcher will allow you to perform the system update without needing to be on the latest firmware. But, you're going to need a third exploitable old3DS or 2DS to act as a surrogate, because you're going to need to downgrade your source to 9.5 or a lower 9.x version.

The latest rxTools betas already support the new3DS, and while there seems to be issues running it from MSET, I'm launching it via Ninjhax and haven't encountered any bugs.

I can personally confirm that FreeMultiPatcher works just fine with Gateway.

So basically, rxTools work the New 3DS 9.9 firmware fine?

Why do I need a third O3DS? My SysNAND on my O3DS was already on 4.2 (The downgraded version from my version 9.2). My Japanese EmuNAND is on 9.9, and my old USA EmuNAND is on 9.5, I also have a copy for 9.2. Is there a problem?

And what I will say now, will it work the System Transfer like it was on 9.9?

Thanks for confirming it works with Gateway.

 

[Apache Thunder]

There's a more convoluted way of doing it if you really want try. My plan should I get a N3DS is to simply format/unlink the o3DS, relink the N3DS emunand to the same NNID my o3DS was on, and then "manually" transfer the content by moving the movable.sed file and the data folder from emunand partition to the n3DS emunand partition.

The only thing I can't copy over is the tickets. I assume the tickets for most of the apps I had bought/downloaded will be added back when I visit eShop on the n3DS. Otherwise I will have to redownload all of them from eShop. (which will take quite awhile).

Though once done I can just move over the save files/overwrite the SD card content with the one from my o3DS and get my save games/extdata back. This process also allows me to copy over my friendcode too since that's controlled by movable.sed/save game for friends list system module.

The big thing you need to know about the above method is to know how to decrypt your emunand partition, modify it, and reencrypt back. That and there's certain files in the data folder you should not copy over like the config system module save game. (well you could copy it over anyway, but you'll likely have flicker/brightness problems with the screens + other possible issues). Refer to the 3DBrew website for the folder location for that particular save game. Once done emunand should boot up.

It will act like it was reset. Just re-enter your profile data like date of birth and such. The only thing lost during this process is your Mii Studio Miis (at least the first one. I don't know if others get lost too or just the main Mii). You'll have to make a new Mii before you can visit the Friends list applet. But once you do you can visit it and see the FC and any friends you had added on your o3DS. Save games and installed games will directly transfer over afterwords too. Just copy the Nintendo 3DS folder from your o3DS SD card to the microSD card for your n3DS. If you see apps not showing up, you may have to visit eShop to get their tickets.

Oh and you have to modify the movable.sed file before copying it over. If you just move it over unchanged all you will manage to do is brick emunand. You have to delete some data at the end of the file and set the first 4 bytes after the "SEED" header to zero. (usually only one byte in this range actually needs to be changed).

I already did that with mine since I had already manually transfered my movable.sed/data folder pair from a bricked 3DS to my current o3DS XL.

And yes assuming you copied all the files over correctly, the NNID on your o3DS (be sure to extract emunand partition before you unlink it from your NNID!) will work on your n3DS provided you had linked your n3DS back to the same NNID account before you started the process. This also means you should not change the password. You may have problems if you had changed the password to the NNID account in the time between you unlinked o3DS and transferred to n3DS.

I never did a proper system transfer from my bricked 3DS. I called Nintendo to report it nonfunctional so that they can unlink that console on their servers. I was then able to link my o3DS XL to my NNID. After I transferred my bricked o3DS stuff over, my NNID still worked as well as getting my original friend code back!

Oh and I don't think any of the new games using the 9.5+ eShop seed crypto will transfer correctly with this method (as I originally did this transfer my self before the new crypto came out). While the seed crypto data is stored in the data folder, the seed crypto data is most likely unique to the console they were generated on so the games that use it won't work on the n3DS. Just uninstall them and redownload them from eShop. You can manually restore the save games or use SaveDataFiler to backup the saves first. (even though the games won't be in a bootable state at this stage, the save games should still be accessible to SaveDataFiler. )

 

[Aroth]

So basically, rxTools work the New 3DS 9.9 firmware fine?

Why do I need a third O3DS? My SysNAND on my O3DS was already on 4.2 (The downgraded version from my version 9.2). My Japanese EmuNAND is on 9.9, and my old USA EmuNAND is on 9.5, I also have a copy for 9.2. Is there a problem?

And what I will say now, will it work the System Transfer like it was on 9.9?

Thanks for confirming it works with Gateway.

not even rxTools will allow a N3DS emunand to run 9.9, sorry.

 

[SpencerlyEverly]

not even rxTools will allow a N3DS emunand to run 9.9, sorry.

Oh WOW...

Hopefully it'll be fixed including with Gateway's soon.

EDIT: I brought the New 3DS yesterday. I also brought some headphones as well. The headphones has been shipped today. Not sure about the N3DS. Hopefully I'll receive both next week.

As such, I have TONS of plans to do with it.

 

[Aroth]

Oh WOW...

Hopefully it'll be fixed including with Gateway's soon.

EDIT: I brought the New 3DS yesterday. I also brought some headphones as well. The headphones has been shipped today. Not sure about the N3DS. Hopefully I'll receive both next week.

As such, I have TONS of plans to do with it.

Believe me, I wish they would get it out too. Unfortunately everything points to that being the hard stop for some time for the N3DS. I don't fully understand the issue but I know it has to do with a chance in the encryption keys used on the N3DS for 9.6+. Not sure if it's just a new key, or a different type of encryption or what. I suspect the delay is because the key has to be brute-forced (which can take a good while with modern encryption algorithms). Keep in mind that there is a very good chance that one of the changes in 10.0 will provide yet another barrier.

 

[Zidapi]

Believe me, I wish they would get it out too. Unfortunately everything points to that being the hard stop for some time for the N3DS. I don't fully understand the issue but I know it has to do with a chance in the encryption keys used on the N3DS for 9.6+. Not sure if it's just a new key, or a different type of encryption or what. I suspect the delay is because the key has to be brute-forced (which can take a good while with modern encryption algorithms). Keep in mind that there is a very good chance that one of the changes in 10.0 will provide yet another barrier.

Yeah, I don't think even Gateway have the time or money to brute force this particular problem away.

 

[Ronhero]

http://gbatemp.net/threads/system-transfer-old-3ds-to-new-3ds-gateway-emunand.395656/

this may help

 

[SpencerlyEverly]

Believe me, I wish they would get it out too. Unfortunately everything points to that being the hard stop for some time for the N3DS. I don't fully understand the issue but I know it has to do with a chance in the encryption keys used on the N3DS for 9.6+. Not sure if it's just a new key, or a different type of encryption or what. I suspect the delay is because the key has to be brute-forced (which can take a good while with modern encryption algorithms). Keep in mind that there is a very good chance that one of the changes in 10.0 will provide yet another barrier.

It possibly might be a new key, not sure.

The key for the N3DS seed might just be some different characters from the O3DS seed key, or it might just be an AES encryption. We are still not sure.

Unfortunately, we are just guessing.

If anybody posts the seed key for the O3DS from that warez site, anybody can. Cause I think we need to take a look at it.

--------------------- MERGED ---------------------------

http://gbatemp.net/threads/system-transfer-old-3ds-to-new-3ds-gateway-emunand.395656/

this may help

I read it, and I need to relink my old EmuNAND from my O3DS before doing this.

My linked EmuNAND as of right now is an Japanese EmuNAND.

 

[SpencerlyEverly]

That and there's certain files in the data folder you should not copy over like the config system module save game. (well you could copy it over anyway, but you'll likely have flicker/brightness problems with the screens + other possible issues). Refer to the 3DBrew website for the folder location for that particular save game. Once done emunand should boot up.

Can you give out a full video tutorial about this? Because, I don't know what to delete and keep in the data folder.

Oh, and the N3DS is not in yet. Estimated delivery is on the 31st.