Hacking SafeCTRTransfer safety method

[ossay78]

hello guys, apparently 3ds.guide have updated the guide with new tool named safectrtransfer v.0.0.4

May I ask some question related to the safety method, does anyone here know wether the tool itself automatically reject the 2.1.0 ctrtransfer image if the region of the ctrtransfer image itself is NOT matched with the console region?

IMO, if it DOES REJECT the different ctrtransfer image region it would save many people WHOM accidentaly installed the wrong 2.1.0 ctrtransfer image.

thank you

 

[adrifcastr]

hello guys, apparently 3ds.guide have updated the guide with new tool named safectrtransfer v.0.0.4

May I ask some question related to the safety method, does anyone here know wether the tool itself automatically reject the 2.1.0 ctrtransfer image if the region of the ctrtransfer image itself is NOT matched with the console region?

IMO, if it DOES REJECT the different ctrtransfer image region it would save many people WHOM accidentaly installed the wrong 2.1.0 ctrtransfer image.

thank you

using the wrong region is nothing bad, just changes the region, then you'll have to edit secureinfo_a and done

 

[ossay78]

using the wrong region is nothing bad, just changes the region, then you'll have to edit secureinfo_a and done

thanks for the explanation.

 

[Quantumcat]

using the wrong region is nothing bad, just changes the region, then you'll have to edit secureinfo_a and done

Not true, I bricked a US system by installing a 2.1 E image (I got so used to doing Eur systems I just forgot).
Edit: it's alright if your system already has a9lh (you could always restore a backup or do a 9.2 CTR transfer of the right region). But if you are doing a 2.1 CTR transfer then that means you don't have a9lh yet and using the wrong region is very BAD.

 

[ossay78]

Not true, I bricked a US system by installing a 2.1 E image (I got so used to doing Eur systems I just forgot).
Edit: it's alright if your system already has a9lh (you could always restore a backup or do a 9.2 CTR transfer of the right region). But if you are doing a 2.1 CTR transfer then that means you don't have a9lh yet and using the wrong region is very BAD.

I'm sorry for your loss. Your testimony provide very useful information for us. So, it means that SafeCTRTransfer (which before a9lhax) is very dangerous thing and the tool itself cannot distinguish wether the ctrtransfer image is out of region.

 

[Quantumcat]

I'm sorry for your loss. Your testimony provide very useful information for us. So, it means that SafeCTRTransfer (which before a9lhax) is very dangerous thing and the tool itself cannot distinguish wether the ctrtransfer image is out of region.

This was with Decrypt9 when DSiWare downgrades were a thing. It didn't check you had the right region, but @addi33's information suggests SafeCTRTransfer doesn't either.

 

[gamesquest1]

ctrtransfer should just swap out the region rather than brick unless the original image you use has a edited secureinfo_a


that said you should still try to stick to your own region etc just to be safe

 

[ossay78]

ctrtransfer should just swap out the region rather than brick unless the original image you use has a edited secureinfo_a


that said you should still try to stick to your own region etc just to be safe

so, we can assume that out of region ctrtransfer image is harmless yet we have to be very careful to not swapped the file by accident.
That's all I want to know. Thanks

 

[thekarter104]

Not true, I bricked a US system by installing a 2.1 E image (I got so used to doing Eur systems I just forgot).
Edit: it's alright if your system already has a9lh (you could always restore a backup or do a 9.2 CTR transfer of the right region). But if you are doing a 2.1 CTR transfer then that means you don't have a9lh yet and using the wrong region is very BAD.

Are you sure you bricked your 3DS by that?

I thought the same thing when I regionchanged my emuNAND to another region, but all you had to do is delete the Home Menu's exData on the SD Card.

 

[pixelmasher]

Are you sure you bricked your 3DS by that?

I thought the same thing when I regionchanged my emuNAND to another region, but all you had to do is delete the Home Menu's exData on the SD Card.

I don't think she was using EmuNAND. You can't brick the system messing with EmuNAND. You just brick your EmuNAND.

 

[thekarter104]

I don't think she was using EmuNAND. You can't brick the system messing with EmuNAND. You just brick your EmuNAND.

Yes, true. But what I meant was how I fixed it, and the same method applies to sysNAND ofcourse. What I did was clear the exData and the region works too.
This might have happened to him with his sysNAND although I'm not sure.

 

[Quantumcat]

Yeah, no good. Does not boot with or without SD (without SD being without the pesky extdata).