I'm interested in why a 4.x 3DS is required. The result of this region change is a region changed emuNAND, which, as we know, can be installed on a 9.2 3DS. OP mentions having this prepared before the newer Gateway exploit, but hasn't yet indicated it's possible on a 9.2 3DS. Perhaps the reason this requires 4.x is because a 9.2 NAND image can't be properly decrypted yet, and in order to apply the region change, you'd need to decrypt your NAND, apply the region change, and re-encrypt it for your specific hardware. And in order to modify the NAND image and still have it working on your specific hardware (as NANDs are hardware-sepcific), we need a 4.x image as it is the only firmware that can be properly modified. But after the region has been changed, you can just update it and it will work. This is all my speculation, of course.
A lot of people (myself included) are specifically interested in this because we've imported our New3DSes. We did this for Gateway, yes, however I'm more glad I imported mine after finding out the US won't be getting the normal-sized New3DS (not at launch, at least). I'd be very happy if I could do an emuNAND to emuNAND system transfer (which we've recently learned is possible), but that would require both emuNANDs to be of the same region and up to date.
So here's what I want to know: when Gateway support for the New3DS comes out, what would need to be done in order to change the region of the emuNAND partition? We of course can't downgrade the New3DS all the way to 4.5, reason being the newer updates have provided support for the super-stable 3D and other hardware-related things. But still, how could it be done? Purely hypothetical, of course. Which is to say, even if it isn't possible, what would the process be (within reason) if we
could do everything?
Thinking about this, I came up with a completely ludicrous solution that won't work out of the bounds of my imagination, but I'd like to share it. Assuming you
can't downgrade the sysNAND of the New3DS to 4.5, let's hypothetically try the following:
- Dump your NAND image on your New3DS
- Create your emuNAND partition
- Copy the NAND image to a computer
- Using a program, attempt to "downgrade" the NAND image in a similar fashion to Gateway's downgrade method
- (This probably won't run on the New3DS, even if you inject it into the emuNAND, but we've "downgraded" this image so that it retains compatibility for our hardware)
- Now that you have a "4.5" New3DS NAND image, make whichever modifications necessary to it to change the region.
- Using black magic, update that newly region-changed NAND image. Yes, from the computer. Using a program. That doesn't exist.
- Use Hex Workshop to inject that NAND image to the MicroSD card's emuNAND partition
- ???
- You now have a "working" region-changed emuNAND partition /s
You guys I promise I'm not insane.