Hacking How can we generate a CTR Transfer Image?

[ScarletDreamz]

As you know, there are 2 CTR transfers for 2 different system versions of the 3ds.

• We got the CTR transfer for 9.2.

• And the CTR Transfer for 2.1.

How can we generate a CTR Transfer image on our own?

 

[gamesquest1]

use decrypt and go to sysnand/emunand options---->ctrtransfer. ...----->dump transferable ctrnand

 

[ScarletDreamz]

use decrypt and go to sysnand/emunand options---->ctrtransfer. ...----->dump transferable ctrnand

Thanks, will do! ;D

 

[gamesquest1]

Thanks, will do! ;D

just a heads up iirc the ctrtransfer image will include your personal secure info file etc, while normally the users own file replaces your's automatically if someone uses a different region system yours will be given to them as a donor file (or people can manually extract your files from the image)

so if your planning to share this file it might be an idea to swap out your secure info for a already publicly shared obe durine the creation of the image

 

[ScarletDreamz]

just a heads up iirc the ctrtransfer image will include your personal secure info file etc, while normally the users own file replaces your's automatically if someone uses a different region system yours will be given to them as a donor file (or people can manually extract your files from the image)

so if your planning to share this file it might be an idea to swap out your secure info for a already publicly shared obe durine the creation of the image

So, the 2.1 and the 9.2 images have the secure info from a donor 3ds? and n3ds?

 

[HyperT]

So, the 2.1 and the 9.2 images have the secure info from a donor 3ds? and n3ds?

No decrypt9 dumps a few files from nand; transfers the ctrnand then adds these files in.

 

[gamesquest1]

they do contain the source consoles localfriendcodeseed_b and secureinfo_a, which is why a ctrtransfer can be applied to a console from a different region, you can also open the file in osfmount and go to /rw/sys you can see that the files are embedded

as I mentioned normally decrypt9 will automatically dump your own and replace the donor ones once the ctr partition is restored, but if you publicly share your ctrtransfer image you are publicly sharing your secure info and local friend code seed (which can lead to your system being banned)

 

[adrifcastr]

they do contain the source consoles localfriendcodeseed_b and secureinfo_a, which is why a ctrtransfer can be applied to a console from a different region, you can also open the file in osfmount and go to /rw/sys you can see that the files are embedded

as I mentioned normally decrypt9 will automatically dump your own and replace the donor ones once the ctr partition is restored, but if you publicly share your ctrtransfer image you are publicly sharing your secure info and local friend code seed (which can lead to your system being banned)

someone would have to dump localfrinedcodeseed:B out of it inject into its own 3ds and get banned with it. nobody who is able to do that is that dumb to get banned. also there is no game you can get banned with atm. so stop spreading incorrect/misleading informations.

 

[gamesquest1]

someone would have to dump localfrinedcodeseed:B out of it inject into its own 3ds and get banned with it. nobody who is able to do that is that dumb to get banned. also there is no game you can get banned with atm. so stop spreading incorrect/misleading informations.

the last public friend code seed was banned within a few days of it being shared publicly, not to mention as I already said it takes 2 minutes to dump the files and inject them with decrypt9, and also I would prefer to encourage people take safety precautions that be a jerk and just encourage people do stuff that can backfire and negatively effect them, if I was them I would prefer to be given the info than just having people pretend something is totally secure because probably nothing bad will happen

especially given 6000 people were apparently banned from pokemon a few days ago for cheating......so I'm sure there will be lots of people actively looking to find a bypass, all it would take is one person to notice these facts, dump the lfcsa and upload it to one of the iso sites and then the op ends up getting his system banned because of a flood of people using his file when he could simply have heeded my advice and switched out his own personal files for already publicly shared and banned files so then he has nothing to worry about

that's ignoring the fact that someone could also just decide to be a jerk and get him banned on purpose by cheating on badge arcade or spamming miiverse......but ofc I'm the bad guy for offering help rather than just spamming hurrr dur 3ds.guide!!!

 

[adrifcastr]

especially given 6000 people were apparently banned from pokemon a few days ago for cheating......so I'm sure there will be lots of people actively looking to find a bypass

thats a save ban -> create new save -> link new pgl acc -> import your stuff with pkhex -> done.

 

[gamesquest1]

thats a save ban -> create new save -> link new pgl acc -> import your stuff with pkhex -> done.

honestly I don't think it matters, I am helping the op understand what he is doing, not just blindly following instruction, he may not care at all, his system may even already be banned, but I would prefer people know exactly what they are doing and any potential risks no matter how slim they are, and how they can avoid it

the mentality of "just follow the guide blindly even if you don't understand it" is kinda why there is so many people who don't know anything at all and end up bricking or panicking screaming brick when their battery goes flat because they don't understand what they have even done to their system at all

I mean look at the thread where the guy was pressing start instead of select for 10 days with people trying to help

 

[HyperT]

they do contain the source consoles localfriendcodeseed_b and secureinfo_a, which is why a ctrtransfer can be applied to a console from a different region, you can also open the file in osfmount and go to /rw/sys you can see that the files are embedded

as I mentioned normally decrypt9 will automatically dump your own and replace the donor ones once the ctr partition is restored, but if you publicly share your ctrtransfer image you are publicly sharing your secure info and local friend code seed (which can lead to your system being banned)

No. Ctrtransfer for region change uses the original SI_A; it's copied and edited to new region and used as SI_C. Personally I don't think ctrnand backups have any console specific files -- I guess I could be wrong on that...

 

[gamesquest1]

No. Ctrtransfer for region change uses the original SI_A; it's copied and edited to new region and used as SI_C. Personally I don't think ctrnand backups have any console specific files -- I guess I could be wrong on that...

ok just to clearup how the process works as i just took the time to check and make sure i had the correct info using the latest decrypt9 built, and yeah a ctrtransfer image created by decrypt9 does include your secureinfo_A file and localfriendcodeseed, but these files are not used during the ctrtransfer process, even if i restore a US ctrnand image, it will indeed keep my original EUR secure info despite having a region valid secureinfo_A built into the ctrtransfer image,

@d0k3 i know this is kinda against what this thread is about, but do you think it would be better to check if the ctrtransfer is going to a different region, and if it is opt to use the included secureinfo_A and automatically use the consoles original secureinfo and rename it to secureinfo_C as used by luma, this could avoid any potential bricks during region changes when people try to do them on a non a9lh system, which i seem to remember seeing a few bricks, when in actual fact these could have been avoided by automatically accepting the donor file as secureinfo_A and automatically using the original system's secureinfo_C, for most people this will make the region swap much safer

and maybe have a option for a "anon" ctrtransfer image that strips out the console unique files to avoid people inadvertently sharing their personal files

 

[d0k3]

ok just to clearup how the process works as i just took the time to check and make sure i had the correct info using the latest decrypt9 built, and yeah a ctrtransfer image created by decrypt9 does include your secureinfo_A file and localfriendcodeseed, but these files are not used during the ctrtransfer process, even if i restore a US ctrnand image, it will indeed keep my original EUR secure info despite having a region valid secureinfo_A built into the ctrtransfer image,

@d0k3 i know this is kinda against what this thread is about, but do you think it would be better to check if the ctrtransfer is going to a different region, and if it is opt to use the included secureinfo_A and automatically use the consoles original secureinfo and rename it to secureinfo_C as used by luma, this could avoid any potential bricks during region changes when people try to do them on a non a9lh system, which i seem to remember seeing a few bricks, when in actual fact these could have been avoided by automatically accepting the donor file as secureinfo_A and automatically using the original system's secureinfo_C, for most people this will make the region swap much safer

and maybe have a option for a "anon" ctrtransfer image that strips out the console unique files to avoid people inadvertently sharing their personal files

That is exactly how D9 already does it. If you're not on A9LH, the secureinfo etc... from the transferable image is used instead of your own. That is the only reason why we can ctrtransfer CHN / KOR / TWN consoles to 2.1 btw, cause these regions never had their own 2.1 to begin with.

 

[Zidapi]

someone would have to dump localfrinedcodeseed:B out of it inject into its own 3ds and get banned with it. nobody who is able to do that is that dumb to get banned.

You have way too much faith in humanity.

You forgot to account for those who would intentionally get it banned, because they oppose cheating and/or think that users who are banned should stay banned.

 

[gamesquest1]

That is exactly how D9 already does it. If you're not on A9LH, the secureinfo etc... from the transferable image is used instead of your own. That is the only reason why we can ctrtransfer CHN / KOR / TWN consoles to 2.1 btw, cause these regions never had their own 2.1 to begin with.

I knew it did at some point, I just figured that people were so sure that wasn't the case that I had to test it myself, I didn't realise it would behave differently between a9lh and non a9lh systems automatically, again, your always ahead of suggestion thanks for clearing it up