Hacking New 2ds xl to new 3ds xl transfer.

[Stephen_Falken]

Hi, is there any way to transfer content of 128 gb card from:
A-new 2ds xl
(11.6.0-39e) /b9s /cfw luma
to
B-new 3ds xl
(10.6.0-31E) /soundhax /cfw luma
?
Luma version is not the same as I remember.
Microsd is almost full, so downloading is not an option:/

Thx!

 

[TurdPooCharger]

• Clone SD from one console to the other
• CFW to CFW system transfer
• 3DS system transfer today- Whats the best way?

When backing up your games / DLCs / updates, you'll have to split and group your title subfolders.

• Nintendo 3DS/<ID0>/<ID1>/title/00040000/00####00

Cut and paste them over to your computer in batches so that you'll have enough free space on the SD to dump them as *.cia in GodMode9.

Edit - You might first want to back up your saves and extdata first with Checkpoint or JKSM.

 

[Stephen_Falken]

Thank you.
I did not know, that I can save installed game as .cia reversely! I will check how to do it, sounds great.

One more thing - do I have to copy anything from B 4gb microsd card to A 128 microsd card?
CFW has been made differntly and firmware is different as well.
In my opinion I shall erase 128 gb, copy all the content from 4gb, and then instal cias, as usual. Am I right?

 

[TurdPooCharger]

CFW has been made differntly and firmware is different as well.
In my opinion I shall erase 128 gb, copy all the content from 4gb, and then instal cias, as usual. Am I right?

One more thing - do I have to copy anything from B 4gb microsd card to A 128 microsd card?

Hold on a minute.

- Is the micro SD card that is almost full the 4 GB one from the (A) n2DSXL?
- You want to transfer stuff from the 4 GB card → 128 GB card to be use on the (B) n3DSXL?

Here's what you can do:

1. Update the custom firmware for both (A) n2DSXL and (B) n3DSXL with the latest Luma3DS v9.1, boot9strap v1.3, and GodMode9 v1.7.1 on both their SD cards and CTRNAND drives.

• Aktualizowanie B9S (Updating B9S)
• Sekcja VI - CTRNAND Luma3DS (Section VI - CTRNAND Luma3DS)

-or- for a combined guide of the two above:​

• The totally-not-freeShop guide in updating your custom firmware.

Edit - If the 128 GB card was already being used on the (B) n3DSXL before this, you'll need to copy and keep intact the (B) Nintendo 3DS folder. That way, all you'll need to do is add and installed *.cia made from (A) n2DSXL.

2. Copy everything off and reformat your new 128 GB card as FAT32 + 32 KB cluster size with guiformat.

• Optional: Because your card meets the minimum 128 GB capacity criteria, you can instead format it as FAT32 + 64 KB cluster size. This will make it load a little faster in HOME Menu and games. Do not use 64 KB cluster size on SD cards that are 64 GB and smaller.

3. While it's empty, do a Full Write + Verify Test with H2testw. Do not skip this step.
4. If an error occurred, your card is either fake or defective. If the card's result comes back clean, delete the *.h2w test files.

• Replace the card if it's bad. There's no way to fix hardware defects.

5. Copy and paste the stuff from the 4 GB card over to the 128 GB card.

• It's better you don't use cut in case you need to keep the original files intact on the 4 GB. Delete those later after everything is done.

6. Insert the 128 GB card into (A) n2DSXL and dump all the titles into *.cia files with GodMode9.
7. Still in the (A) n2DSXL, backup all your saves and extdata with either Checkpoint or JKSM.

• Read the other threads about how to dump and restore saves from GBA Virtual Console games.

8. Delete the Nintendo 3DS folder on the 128 GB card. Use the card on (B) n3DSXL.
9. Reinstall all your games with FBI and restore the saves + extdata with whichever save manager you used.​

 

[Stephen_Falken]

Thank you for reply.
-My 4gb is almost empty, I only used it for soundhax -> cfw.
-I want to use my 128gb card from n2ds xl(A) on n3ds xl(B), and all the content. Card is an original Sandisk ultra, works great for a few months already, so there is no need to double check it.
Thanx for 64kb hint, it might be useful!

What suprises me is the point 6 is after 5. Atter reading your post, I was about to:
-build cias straight from my n2dsxl(A),
-save them to my pc, and then
-after collecting all of them, simply
-format 128gb,
-copy the content from 4gb to 128, and
-install the cias as always.

I can not understand why do I need to copy 4gb content to 128gb, before I will make cias. I am affraid, that once I do it, my n2dsxl (A), will not work with this modified 128gb. Am I right?

 

[TurdPooCharger]

-I want to use my 128gb card from n2ds xl(A) on n3ds xl(B), and all the content. Card is an original Sandisk ultra, works great for a few months already, so there is no need to double check it.

Check the card with H2testw if you've never done so. If not only to make sure your card is real, you should be absolutely certain it doesn't have any problems. 128 GB is a lot of data to entrust to 15x10 mm piece of high-tech precision made glass * (silicon wafer manufacturing is not perfect). That card has to be known without a doubt it's 100% fully functional. It is the foundation of your entire 3DS setup, like the ground on which your house is built on.

What suprises me is the point 6 is after 5. Atter reading your post, I was about to:
-build cias straight from my n2dsxl(A),
-save them to my pc, and then
-after collecting all of them, simply
-format 128gb,
-copy the content from 4gb to 128, and
-install the cias as always.

Yah... Adjust the instructions in building the CIAs from your (A) n2DSXL, in batches and then install those *.cia on (B) n3DSXL. Read the explained confusion below.

I can not understand why do I need to copy 4gb content to 128gb, before I will make cias. I am affraid, that once I do it, my n2dsxl (A), will not work with this modified 128gb. Am I right?

I wasn't sure which card was full and the other that's empty. Your post made it seem like you were upgrading from 4 GB to 128 GB.

 

[Stephen_Falken]

Hi, sorry it is my second language, and I am not familiar with all of these procedures in final Everything seems to be clear now, I will try it out in a few days, thank you!

 

[Stephen_Falken]

Hi, is there any other way to biuld cias straight from my pc? I copied the content of the 128 gb card to my pc, and it would much faster to batch convert them without using n2dsxl, and godmode 9...
In other way it simply take ages to sort everything out.

 

[TurdPooCharger]

Hi, is there any other way to biuld cias straight from my pc? I copied the content of the 128 gb card to my pc, and it would much faster to batch convert them without using n2dsxl, and godmode 9...
In other way it simply take ages to sort everything out.

What you seek does not exist; I cannot think of a homebrew app that has Nintendo 3DS folder → *.cia rebuilding capability other than GodMode9.

However, I sent a feature request at ihaveamac's GitHub for fuse-3ds found here. In my opinion, his project is the closest desktop analogy to the primer.

Don't hold your breath if something like this doesn't happen or anytime soon. You'll have to add back your stuff to the SD card and dump them the old fashion way on the n2DSXL.

 

[Stephen_Falken]

Thank you for helping me in this topic, have a nice evening

 

[Aquadraws]

I don't think op knows how but he could transfer the movable.sed and tickets manually and then just switch sdcard(just saying xd)

 

[TurdPooCharger]

I don't think op knows how but he could transfer the movable.sed and tickets manually and then just switch sdcard(just saying xd)

I don't recommend this method. If one uses a 3DS with a duplicate movable.sed that's not registered to it and uses a Nintendo online service, it is possible that both originator and copied *.sed 3DS systems can get banned.

 

[Aquadraws]

Well they also check movab?? WTF i never knew. But this would sure be the fast and easy way out

 

[TurdPooCharger]

Well they also check movable?? But this would sure be the fast and easy way out

I'm not entirely clear of the details, but supposedly, a part of the movable.sed is derived from the LocalFriendCodeSeed_B (or _A). Not sure how the exact mechanism of triggering the ban occurs:

• Both first and second 3DS with that same *.sed are both online at the same time. Nintendo sees this and realizes you have CFW.

or??

• Second 3DS with the first 3DS movable.sed goes on eShop → Nintendo detects unauthorized System Transfer (ie: Again, impossible except if custom firmware was involved).

The only time one should use a different movable.sed is to temporarily recovery and backup games, DLCs, updates, saves, and extdata because the original 3DS is kaput.

 

[Aquadraws]

How about me using a public seed b(not because banned but because lost it) and my original movable that came with the console... i could understand if they check if 2 consoles(by console id not serial) have the same fc and they ban but there is no way they check movable unless spotpass has to do somerhing with that

 

[TurdPooCharger]

How about me using a public seed b(not because banned but because lost it) and my original movable that came with the console... i could understand if they check if 2 consoles(by console id not serial) have the same fc and they ban but there is no way they check movable unless spotpass has to do somerhing with that

Eh, beats me. I think the LocalFriendCodeSeed_B has more to do with online play and the movable.sed (with a linked NNID and/or Nintendo Account) deals with purchasing digital goods on the eShop.

We can speculate a number of reasons why Nintendo doesn't outright ban you for using a public seed that's not your own.

Perhaps:

1. Their ID checks aren't very stringent for the 3DS. Nintendo might not have thought cross checking the *.sed and seed were necessary security measures.

• You can see they learned their lesson and wisen up for their Switch. That shit is on Fort Knox level of lock down in doing anything not explicitly allowed by Nintendo.

2. Nintendo does not care that much about people with custom firmware on their 3DS at this point in time. *

• The 3DS is close to retirement. Why put that much effort in hunting down homebrewers so long as * they don't rock the boat cheating online?

3. Even if some 3DS CFW users pirate their games, Nintendo does not want to ban you from their store if you still legitimately purchase their goods.

• Money is money. Why turn away good paying customers?

There's also the (serial number) super ban where LocalFriendCodeSeed will not save you. This type of ban is reserved for special occasions like reported stolen 3DS systems or customers who conduct business in bad faith doing a credit card charge back.

Sorry, I'm not that knowledgeable about this aspect of the 3DS, but I hope that answers some of your questions.

 

[Aquadraws]

Eh, beats me. I think the LocalFriendCodeSeed_B has more to do with online play and the movable.sed (with a linked NNID and/or Nintendo Account) deals with purchasing digital goods on the eShop.

We can speculate a number of reasons why Nintendo doesn't outright ban you for using a public seed that's not your own.

Perhaps:

1. Their ID checks aren't very stringent for the 3DS. Nintendo might not have thought cross checking the *.sed and seed were necessary security measures.

• You can see they learned their lesson and wisen up for their Switch. That shit is on Fort Knox level of lock down in doing anything not explicitly allowed by Nintendo.

2. Nintendo does not care that much about people with custom firmware on their 3DS at this point in time. *

• The 3DS is close to retirement. Why put that much effort in hunting down homebrewers so long as * they don't rock the boat cheating online?

3. Even if some 3DS CFW users pirate their games, Nintendo does not want to ban you from their store if you still legitimately purchase their goods.

• Money is money. Why turn away good paying customers?

There's also the (serial number) super ban where LocalFriendCodeSeed will not save you. This type of ban is reserved for special occasions like reported stolen 3DS systems or customers who conduct business in bad faith doing a credit card charge back.

Sorry, I'm not that knowledgeable about this aspect of the 3DS, but I hope that answers some of your questions.

I know about the 022-* error that ban Device/Console ID NOT the serial number.... and blocks the said thing from accessing the CDN...
In my opinion when you enable sending of sys inforomations or share usage data with nintendo they can also see your movable but from XMas 2016(thanks soundhax) that my unit is modded, and from half 2018 that i did "that" ctrtransfer that made me force use a LFCS_B haven't got ban yet and i regualary cheat in online games i even posted pictures of it in miiverse. I totally agree with you that big N is not giving a f about 3ds

 

[TurdPooCharger]

I know about the 022-* error that ban Device/Console ID NOT the serial number.... and blocks the said thing from accessing the CDN...
In my opinion when you enable sending of sys inforomations or share usage data with nintendo they can also see your movable but from XMas 2016(thanks soundhax) that my unit is modded, and from half 2018 that i did "that" ctrtransfer that made me force use a LFCS_B haven't got ban yet and i regualary cheat in online games i even posted pictures of it in miiverse. I totally agree with you that big N is not giving a f about 3ds

Edit - When I said serial number, I meant Console ID; I think they're the same thing. * The sticker on the bottom back of the 3DS.

WARNING: LocalFriendCodeSeed_B and movable.sed were randomly hex generated. Actual use may result in a brick and/or ban.

If you want to extract your original LFCS_B from the movable.sed ← (if this was never swapped out), here's their relation.

• [3dbrew.org, wiki] movable.sed
• [3dbrew.org, wiki] LocalFriendCodeSeed_B

From the movable.sed, copy from 0x008 to 0x117 offsets for the total length of 0x110 bytes.

 

[Aquadraws]

Console ID and Serial Number are different things or 022's would be easy to bypass, i will try the hex edits thanks for the hint

 

[Aquadraws]

ummm my lfcs_B is 272 bytes seems legit, but... my friend code is unchanged