Hacking o3DS XL region change JPN->EUR, eShop & updates problems

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
Hi all,
After reading the guide for region changing (https://3ds.hacks.guide/region-changing.html), I wanted to test it and decided to buy Japanese old 3DS XL, as they have some pretty nice cases and low prices even including shipping.
I specifically did not buy n3DS XL as there would be problems with the eShop, as stated in the tutorial.

Now, after having formatted the console, installed Luma/GodMode9, and CTRtransferred the 11.5.0 EUR version for o3DS XL, I updated the console and reformatted it to be on the safe side.
--> At first, it seems that it works like a charm with the selected

I created a new NNID in the parameters screen, validated it and everything seemed to be ok.

  • Now, if I'm going to the themes eShop and select a free one to make a test, the console tells me about NNID association (Associating a NNID will imply following modifications / Credit card stuff / account activities tracking). I select ok & it connects. Then: Error code 005-5958.
  • If I get out of the themes eShop and try again to download a theme, the console will ask me again about this NNID association, as if NNID is not associated at all. Then, same error 005-5958.
  • Trying to access the eShop directly leads to the same association of NNID message, and then an error code 007-2001
  • Trying to update a gamecart, again NNID association and error code 005-5958.
It seems that the region change is never really saved to the console, and the console always tries to associate the NNID and fails each time.

Do you think pushing again a CTRtransfer will change anything? Any ideas to make this work?

And yes, I've had a look a threads about this, I knew that occasionaly eshop can not work, but I don't know it this would be the behaviour, or if I miss something and redo the whole process might change a thing or not.

I've seen the threads with the help of @TurdPooCharger but they were for n3DS and I'm not able to see if it's relevant to my case.

Thanks!
 

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
Thanks @tfocosta . One of the reasons I tried was that in the guide, it was stated "all Old 3DSs will be able to access the eShop after creating a new NNID on their new region". I want to create a new NNID, new eShop account, so based on that, it should work.

I'm wondering if I should have deleted the eShop account on the console prior to the CTRtransfer. Formatting it might not have been enough in this specific case.
 

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
Thanks for the link, it seems very relevant to my case. The method used on this site was based on emunand with the initial nand backup, which I cannot do as I was very stupid and did not do a backup prior to the region change...
@techmuse Do you think that I could CTRtransfer again a JPN image, update system and log in to delete eShop account, then CTRtransfer EUR image?

The guide should be updated in order to reflect the fact that the eShop account has to be deleted if that's needed :(
 

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
My idea did not work...

I did a CTRtransfer of the 11.5.0J, started the console, updated it, formatted it, configured it and could access the japanese eShop. Went to delete usage record, provided the 11 digit serial to validate (thanks google translate), and shut down the console.
Then, restarted the CTRtransfer process with 11.5.0E, started the console, updated and tried to access the eShop: no error code, just stating that it's the wrong region.
I formatted the console, configured it again to France, restarted again and tried to access the eShop: Error code 007-2001 :unsure:

At least it's consistent... But is there something else I could try?
 
Last edited by yaum,

laramie

Well-Known Member
Member
Joined
Dec 15, 2014
Messages
828
Trophies
0
XP
1,184
Country
United States
My idea did not work...

I did a CTRtransfer of the 11.5.0J, started the console, updated it, formatted it, configured it and could access the japanese eShop. Went to delete usage record, provided the 11 digit serial to validate (thanks google translate), and shut down the console.
Then, restarted the CTRtransfer process with 11.5.0E, started the console, updated and tried to access the eShop: no error code, just stating that it's the wrong region.
I formatted the console, configured it again to France, restarted again and tried to access the eShop: Error code 007-2001 :unsure:

At least it's consistent... But is there something else I could try?
I'd check on the nintendo website to see what the account is linked to region wise, If the account has information from a different country, it won't access eshop new or old models. Eshop validates payment methods with regions too so it could be that. My 1.0 japan o3ds is a USA transferred one now but it was the OG 1.0 dump that made downgrading possible. It definitely has some special software/rewote from scratch. So while it does work with eshop, I can't be sure if some of my custom rewrites helped with that.
 

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
I did not link a Nintendo account, I only created a NNID via the console menus, and I could select a country (France). I connect using this NNID info and I got this error.

By the way, I managed to associate this NNID to an account created with France as a country. I suppose that if it was the wrong region, I could not have associated the NNID to a European account? There is no payment method linked to this account yet.

The main difference of what I did and the one linked by Techmuse was the fact that he used emunand with the original system (I guess it was a sysnand backup?)
Went into the Emunand with original JAP system, logged into eshop and ... delete eshop account

Is there somewhere a file / link that I could delete using GodMode9 to try resetting it ?
 

laramie

Well-Known Member
Member
Joined
Dec 15, 2014
Messages
828
Trophies
0
XP
1,184
Country
United States
I did not link a Nintendo account, I only created a NNID via the console menus, and I could select a country (France). I connect using this NNID info and I got this error.

By the way, I managed to associate this NNID to an account created with France as a country. I suppose that if it was the wrong region, I could not have associated the NNID to a European account? There is no payment method linked to this account yet.

The main difference of what I did and the one linked by Techmuse was the fact that he used emunand with the original system (I guess it was a sysnand backup?)


Is there somewhere a file / link that I could delete using GodMode9 to try resetting it ?
Have you tried injecting emunand to region swap instead? It's a little safer and if you do mess something up it won't be too painful to fix. You might also have to link your account after the injection to trick the 3ds into thinking it's from your region. Nintendo has some special code to associate geo-location with where the account was made. IE. you should only be able to link accounts with specific regional consoles.
 
  • Like
Reactions: techmuse

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
[Rant]
Actually, I'm not that good with software modding... You could consider I'm a script kiddie, able to follow (properly) a tutorial, but not that much. I'm better off doing hardware mods and console restoring :)

What I'm doing is pushing to sysnand the new images following Plailect's guide, and using only the Nintendo OS to make the small modifications like registering/delete accounts and so on.
[/Rant]

So, therefore I'm not too good with the emunand concept. Is everything I do when booting from emunand contained within emunand (for example: deleting eshop account)? I guess I'll have to dig a bit more info on setting up an emunand, there is only a way to transfer emunand to sysnand in the Plailect's guide. If you have any link to share that you found helpful, that would help.

Next steps: Restore JPN image, update, connect to eshop, dump sysnand to emunand, install EUR image to sysnand, update, boot emunand and delete NNID, delete eshop account, boot sysnand and see if it gives something :unsure:
 

laramie

Well-Known Member
Member
Joined
Dec 15, 2014
Messages
828
Trophies
0
XP
1,184
Country
United States
[Rant]
Actually, I'm not that good with software modding... You could consider I'm a script kiddie, able to follow (properly) a tutorial, but not that much. I'm better off doing hardware mods and console restoring :)

What I'm doing is pushing to sysnand the new images following Plailect's guide, and using only the Nintendo OS to make the small modifications like registering/delete accounts and so on.
[/Rant]

So, therefore I'm not too good with the emunand concept. Is everything I do when booting from emunand contained within emunand (for example: deleting eshop account)? I guess I'll have to dig a bit more info on setting up an emunand, there is only a way to transfer emunand to sysnand in the Plailect's guide. If you have any link to share that you found helpful, that would help.

Next steps: Restore JPN image, update, connect to eshop, dump sysnand to emunand, install EUR image to sysnand, update, boot emunand and delete NNID, delete eshop account, boot sysnand and see if it gives something :unsure:
Emunand is just a copy of your system nand on your sd card. I wouldn't convert your sysnand, I'd leave it alone and use emunand. It's just basically when you boot instead of booting the firmware from the 3ds it will boot from the sd card. That is good because if you mess something up, you can just restore emunand. If you do this with sysnand, and you mess something up without a good backup to fix it will mean you'll need to hardmod it and manually create the firm from scratch. It''s a pain in the butt trust me.
 

lone_wolf323

Well-Known Member
Member
Joined
May 27, 2011
Messages
4,340
Trophies
1
XP
3,388
Country
Canada
Emunand is just a copy of your system nand on your sd card. I wouldn't convert your sysnand, I'd leave it alone and use emunand. It's just basically when you boot instead of booting the firmware from the 3ds it will boot from the sd card. That is good because if you mess something up, you can just restore emunand. If you do this with sysnand, and you mess something up without a good backup to fix it will mean you'll need to hardmod it and manually create the firm from scratch. It''s a pain in the butt trust me.
Would you care to explain now a days when a hardmod would be remotely needed for such a thing? NTRboot will take care of that and allow flashing of a ctrtransfer which fixes most issues.
 

laramie

Well-Known Member
Member
Joined
Dec 15, 2014
Messages
828
Trophies
0
XP
1,184
Country
United States
Would you care to explain now a days when a hardmod would be remotely needed for such a thing? NTRboot will take care of that and allow flashing of a ctrtransfer which fixes most issues.
I'm talking about the kind of mistakes that would otherwise deem the console as a "brick" Which if you truly brick a 3DS, then you've taken it to the worst possible point. It's really really really really hard to fully brick a 3ds since we have things like ntrboot or other things like the twl takeover through ds mode.(idk the official scene name as I was only around to help develop and share the bootrom flaw and the old school Arm9loaderhax). The only real reason to have a hard mod now a days is to plug your 3ds into your pc and opening it in something like HxD to manually adjust bytes in the nand or other reasons, which is out of the scope here, you have to know what every byte you're looking at does and of course not remove data but replace.
 

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
Feedback:
Restore JPN image, update, connect to eshop, dump sysnand to emunand, install EUR image to sysnand, update, boot emunand and delete NNID, delete eshop account, boot sysnand and see if it gives something :unsure:

I now have a japanese emunand on my sd card (on a specific partition), and EUR on sysnand. I got the same behavior. This time, I tried to update a game from a gamecart, and got error 009-1003 (not the good region), because I did not set up the new NNID. After setting up the NNID, back to error 005-5958 :angry:.
eShop gives again the error 007-2001...

The NNID creation clearly does something, but there is still a problem...

@techmuse you said you used a specific method other than Pailect's one, was that because you were having this 007-2001 error initially?
 
Last edited by yaum,

techmuse

Active Member
Newcomer
Joined
Oct 21, 2018
Messages
31
Trophies
0
XP
356
Country
United States
did this an an experiment, deleted burner nnid first then eshop account on jp, switched to us, then went to eshop then I went through the intro and got In eshop
 

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
@TurdPooCharger , I have 3 JPN motherboards, and this is the first one for which I was trying. Do you think there is a chance it's going to work with the others, and if yes, what should I do to secure that it's working in your opinion ?
 

heiyu04

Member
Newcomer
Joined
Dec 1, 2020
Messages
8
Trophies
0
Age
24
XP
115
Country
China
If you have two Jans, you can use the system transfer in the settings transfer.

After the transfer, you get a clean machine.

You can access the eshop by turning the clean machine to any area you want to use.

Sorry, machine translation may not be very friendly. I don't know English very well
 

yaum

Well-Known Member
OP
Member
Joined
Sep 11, 2020
Messages
101
Trophies
0
Age
42
XP
336
Country
France
Hmm, not fully sure I understand how this would be different from a CTRTransfer. Anyone would explain? Thanks!
 
General chit-chat
Help Users
    kenenthk tempBOT: @ kenenthk is always drunk with tempbot