What are the chances that someone will start to offer a service to do the transformation for those of us who can't find a proper region copy of Cubic Ninja?
I don't think anyone has even gotten it working yet.
What are the chances that someone will start to offer a service to do the transformation for those of us who can't find a proper region copy of Cubic Ninja?
I wouldn't say it's dead. There are those of us who are entirely uninterested in eshop access. I've been in the midst of a move over the past few weeks, so I haven't had much time to give this all a go yet, but I plan on using what's gone on in this thread to change my emunand using a public secureinfo. If I ever felt like going whole-hog to sysnand with it, I'd buy up another 3ds and get a secureinfo of my own, but in the mean time it will be nice to at least be able to understand the messages I see, and the menus themselves. Honestly, though, I'll probably just continue to always use my gateway to play my game backups, since it's easier than carrying around several carts, and I can keep the originals all safe and sound in their cases on my media rack.I would be happy to do it for someone, but seeing as at the moment there's seemingly no way to fix the eShop... I'm honestly wondering if this is dead. :/
I would be happy to do it for someone, but seeing as at the moment there's seemingly no way to fix the eShop... I'm honestly wondering if this is dead. :/
I can confirm that, even if the shop is 100% dead it allows carts of a region. As it stands this (albeit updated...) and GW are the only way to get US Xeno on a JP N3DS atm, so there's that.I would be happy to do it for someone, but seeing as at the moment there's seemingly no way to fix the eShop... I'm honestly wondering if this is dead. :/
I'll just use a CFW to make unsigned updates run with my retail US carts. Problem solved!
So I found a way to get eshop working (on my old nnid account nevertheless) but it's EXTREMELY complicated and very hard to use. I don't have the time to go into details but let's try to do this:
1) On N3DS, patch act to use your original serial number. Create and link NNID
2) On N3DS capture the act request. Remember the device cert, and serial.
3) On O3DS, patch act to use N3DS device cert and serial. Also patch it to use your N3DS NNID & password. Attempt to enter the eshop.
4) On N3DS, patch nim to replace return SOAP requests to be US/USA region.
5) On N3DS, patch nim to bypass updates
Every time you reboot, redo step 4-5. You can now enter eshop and buy/download things and they will run.
I would be happy to do it for someone, but seeing as at the moment there's seemingly no way to fix the eShop... I'm honestly wondering if this is dead. :/
So I found a way to get eshop working (on my old nnid account nevertheless) but it's EXTREMELY complicated and very hard to use. I don't have the time to go into details but let's try to do this:
1) On N3DS, patch act to use your original serial number. Create and link NNID
2) On N3DS capture the act request. Remember the device cert, and serial.
3) On O3DS, patch act to use N3DS device cert and serial. Also patch it to use your N3DS NNID & password. Attempt to enter the eshop.
4) On N3DS, patch nim to replace return SOAP requests to be US/USA region.
5) On N3DS, patch nim to bypass updates
Every time you reboot, redo step 4-5. You can now enter eshop and buy/download things and they will run. (Not sure if step 3 is needed. When I tried to get the service token from my N3DS, it just fails. Now it works. Maybe it was because of server issues yesterday).
So let's assume that step 3 is unnecessary (as speculated due to server issues at the time of connection attempts). For step 4, I assume this would require some local server PHP trickery like we did with patching NIM to update to a specific software version? Would it be PHP code as simple as capturing return SOAP requests and throwing out (or changing?) any NON-US/USA region ones to just have a US/USA region flag? Does this method just try to throw away any invalid (out of region) ticket requests like for JPN Swap-Note 3D?
One other question, if I may. When you say the system-transferring systems need to be on the same firmware because of 3 changes to the system transfer protocol, do you mean over the whole life of when system transfers have been available, or just recently (like within the 9.x versions). I ask as my data on my O3DS is at 9.6 EmuNAND with RxTools and obviously my region-changed N3DS is on 9.2 SysNAND. Were there any changes in system transfer protocol between 9.2 and 9.6 that could cause an issue with the System Transfer? Assuming this fix for filtering the return SOAP requests works to allow eShop/System Transfer access, of course. Thanks you for all your help, we couldn't do this without you!
I'm not sure when the protocol changed but only that 9.6 at at v4 and 9.2 is at v3
No one has tested the one that requires a hardmod, but chances are that isn't going to work either.
Here's the problem, as I understand it: EU and JP New 3DS's come with at least one game preinstalled: Swapnote in Japan, and Tomodochi New Life in Europe.
These games are tied to your 3DS's device certificate, a read-only value stored in the CPU which is impossible to modify.
So let's say you change a JP N3DS to NA and connect to the eShop. The eShop sees that your 3DS's certificate owns a copy of Japanese Swapnote. Because Japanese Swapnote doesn't exist in the US eShop, it throws an error and doesn't let you in.
if this were the case would an old system with something else preinstalled also not work? like say one of those ds's with pokemon x/y? maybe someone could test.No one has tested the one that requires a hardmod, but chances are that isn't going to work either.
Here's the problem, as I understand it: EU and JP New 3DS's come with at least one game preinstalled: Swapnote in Japan, and Tomodochi New Life in Europe.
These games are tied to your 3DS's device certificate, a read-only value stored in the CPU which is impossible to modify.
So let's say you change a JP N3DS to NA and connect to the eShop. The eShop sees that your 3DS's certificate owns a copy of Japanese Swapnote. Because Japanese Swapnote doesn't exist in the US eShop, it throws an error and doesn't let you in.
So I found a way to get eshop working (on my old nnid account nevertheless) but it's EXTREMELY complicated and very hard to use. I don't have the time to go into details but let's try to do this:
1) On N3DS, patch act to use your original serial number. Create and link NNID
2) On N3DS capture the act request. Remember the device cert, and serial.
3) On O3DS, patch act to use N3DS device cert and serial. Also patch it to use your N3DS NNID & password. Attempt to enter the eshop.
4) On N3DS, patch nim to replace return SOAP requests to be US/USA region.
5) On N3DS, patch nim to bypass updates
Every time you reboot, redo step 4-5. You can now enter eshop and buy/download things and they will run. (Not sure if step 3 is needed. When I tried to get the service token from my N3DS, it just fails. Now it works. Maybe it was because of server issues yesterday).
I don't know any of the offsets. The way I'm doing it is that I have a debug proxy (Charles) with breakpoints set on nintendo requests. Then I patched NIM to use my SOAP server.
No one has tested the one that requires a hardmod, but chances are that isn't going to work either.
Here's the problem, as I understand it: EU and JP New 3DS's come with at least one game preinstalled: Swapnote in Japan, and Tomodochi New Life in Europe.
These games are tied to your 3DS's device certificate, a read-only value stored in the CPU which is impossible to modify.
So let's say you change a JP N3DS to NA and connect to the eShop. The eShop sees that your 3DS's certificate owns a copy of Japanese Swapnote. Because Japanese Swapnote doesn't exist in the US eShop, it throws an error and doesn't let you in.