I'm considering buying an N3DS from Japan because the not-xl special editions in the US are expensive and I can get a japanese one easily for $170. I really don't want to get another XL, my O3DS XL frustrates me because of how big it is. I know you can do region changing with secureinfo_a but the eshop won't work, right? I've heard about secureinfo_c but I don't really understand the complexities of the whole process. Can someone clarify?
Solution
SecureInfo_C is used by 3ds_injector, Luma3DS includes it by default so when you inject a SecureInfo_C file to CTRNAND/rw/sys it should be used by default. Theoretically you should be able to just edit the region byte of your own SecureInfo_A file and inject it as SecureInfo_C, as 3ds_injector disables the signature checking when it finds a SecureInfo_C file on NAND. eShop should work automatically since 3ds_injector also patches the eShop to make it work on region changed NANDs.
I didn't have much success with my attempt to make a region changed emuNAND this way though, not sure what went wrong, maybe something with the update pack I used to region change or maybe I shouldn't have used FBI to install it. I've never region changed a NAND before but I did follow a (rather old and obsolete) guide.
I didn't have much success with my attempt to make a region changed emuNAND this way though, not sure what went wrong, maybe something with the update pack I used to region change or maybe I shouldn't have used FBI to install it. I've never region changed a NAND before but I did follow a (rather old and obsolete) guide.
I read somewhere the SecureInfo_C has to be taken off a fresh 3ds, and won't let it go online at all after you take it, is that not true? My O3DS is far from fresh, plus I'm going to give it away to someone after I get it and do the System Transfer.
I was planning on using updated sysnand for this, too. Is it a emunand thing for security or is it possible to do it with updated sysnand?
This whole process would be much less of a headache if NoA decided that people could use a 3ds that isn't gigantic and can barely fit in a pocket.
I was planning on using updated sysnand for this, too. Is it a emunand thing for security or is it possible to do it with updated sysnand?
This whole process would be much less of a headache if NoA decided that people could use a 3ds that isn't gigantic and can barely fit in a pocket.
Similar threads
- Solved
- No one is chatting at the moment.
