That makes sense, since downloaded software only shows things you originally downloaded from the eshop.
So does that mean the games are now tied to the console? And if I system transfer it will show up as re-downloadable on the target system? Or if I link a NNID the games are now tied to the NNID?
Never experienced any hang while playing and I'm using it from the first day on a 3DS for coding and on other 2 for my kids.
You may have a problrm with your SD or you are booting with L key pressed .
Is this "never hang" experience of yours on your PBT or the Giovanify/Palantine CFW? I was referring to the Giovanify/Palantine CFW hanging on me. The unstable part i mentioned was for been able to boot into these CFW's only like 1 out of 5 tries. And that's after i downgraded my microsd from 64gb to 4gb. Never could get 64GB to work on any CFW. Think i tried about 20 times till i gave up.
They are the same thing.
No. you clearly stated:
I was referring to this sentence.
If it also gets tied to the NNID, does that mean it's possible to distribute amongst multiple consoles? So:
Install legit CIAs to sysNAND.
Create emuNAND, then update.
Make sure it is re-downloadable. Games are now tied to eshop account.
Link NNID. Games are now tied to NNID.
System format to unlink NNID.
Link NNID on different console. Games are now available on that console.
Repeat with different NNID.
Here's something I'm curious about;
So, while I haven't done it yet, you can change your emunand region using a couple tools and a secureinfo file from somebody with the desired region (although getting this seems to be the hard part).
I want to eventually do this so that I can install all the legit EUR .cias onto my US 3DS, and then change emunand region to EUR and update to 9.6 emunand and enjoy those legit .cias.
I don't see any reason why that won't work, but what I wonder is what happens with the eshop when your console is region changed? Assuming the eshop still works normally on a region changed 3DS, what would happen if you followed the process in this thread but then switched your region back to the original (in my case US)? Would you just basically lose the tickets or w/e for the EUR games, or would you be able to download US versions of those games, or would you just not see anything because you wouldn't be on the EUR eshop any more?
I'm not sure if anyone really knows the answer, but if I find a way to get a EUR secureinfo file (no trading allowed on gbatemp) I will probably try the above process and see what happens. At the very least it should allow anybody to play all the EUR legit .cias...
So, while I haven't done it yet, you can change your emunand region using a couple tools and a secureinfo file from somebody with the desired region (although getting this seems to be the hard part).
I want to eventually do this so that I can install all the legit EUR .cias onto my US 3DS, and then change emunand region to EUR and update to 9.6 emunand and enjoy those legit .cias.
I don't see any reason why that won't work, but what I wonder is what happens with the eshop when your console is region changed? Assuming the eshop still works normally on a region changed 3DS, what would happen if you followed the process in this thread but then switched your region back to the original (in my case US)? Would you just basically lose the tickets or w/e for the EUR games, or would you be able to download US versions of those games, or would you just not see anything because you wouldn't be on the EUR eshop any more?
I'm not sure if anyone really knows the answer, but if I find a way to get a EUR secureinfo file (no trading allowed on gbatemp) I will probably try the above process and see what happens. At the very least it should allow anybody to play all the EUR legit .cias...
So if I do all this can I lets say update my sysnand to 9.6 (this is a hypothetical), format the 3ds, link my NNID ,and redownload all the titles on my 3DS (same console used in all steps)?
If I do this can I still play games using a retail cart? Will my save on my retail cart still work? For example, SSB4 or Pokemon OR/AS/X/Y?
Also, do I have to keep my 3DS on always to stay in EmuNAND?
Sorry I'm new to this scene, not sure whats the basics.
Also, do I have to keep my 3DS on always to stay in EmuNAND?
Sorry I'm new to this scene, not sure whats the basics.
If you read through this thread: https://gbatemp.net/threads/i-found-a-eshop-bug-on-this-a-good-one.385185/ it seems like that's what the OP did, although I don't know that you'd need to format your 3DS at all. I think you can basically just follow this tutorial and skip the emunand/rxTools part at the end and just update your Sysnand, though I personally wouldn't update sysnand to 9.6 for any reason since that would basically mean losing all known vulnerabilities aside from using a Sky3DS (and in that case you wouldn't even need to waste time with legit .cias).
This is for 4.x users, so if you're already playing retail carts of SSB4 or Pokemon but don't already know about emunand I'm guessing you're not on 4.x. Good news is if you're on 9.2 or earlier you can downgrade to 4.x using the gateway launcher.dat (look for tutorials, it's pretty simple).
Yes you can play retail carts in emunand - that's the main point of emunand. Saves should work as normal AFAIK.
You boot into emunand by going to a website which uses an exploit in the 3DS browser to boot your emunand (which is stored on the SD card). So I guess technically if you want to "stay" in emunand you would have to leave your console on, but you could just turn it off and go back to the website to re-enter emunand (bookmark the website for easily returning).
I am on 9.2, luckily! Idk, I was confused because in this topic (http://gbatemp.net/threads/guide-the-emunand-save-data-mega-guide-gbatemp-doesnt-deserve.378491/) where it says " Basically, if
you want to continue to be able to play retail games with >6.0 save encryption, you need to
stay on the system NAND version you are currently on. You'll need to stay at that system NAND
version until gateway fixes all of these save compatability issues."
So being on EmuNAND solves this? So I can only play my retail cart and .cia games on EmuNAND? The sysNAND 4.x will be basically useless besides being used to install all this stuff?
ok. just because you have a ticket for a game does not mean it is linked to your nnid!
unless you dump your tickets and actually confirm you have gained another ticket, which now has your eshop/console id in it, then please stop talking about nnid linking.
-- because people will get confused.
unless you dump your tickets and actually confirm you have gained another ticket, which now has your eshop/console id in it, then please stop talking about nnid linking.
-- because people will get confused.
I had actually the opposite effect. Those 4gb cards took more attempts. But using a 32 and 64 gb class 10 made a world of difference. Using the stock palatine files it takes between 1 to 5 attempts at most. Most times it works on 3rd attempt. And once a week it works on 1 attempt. But we only load the cfw once a day in the morning and then shut off at night, inbetween its in sleep mode.
I didn't remember the issue with save encryption, as it has not personally affected me yet. My bad.
I'm not 100% sure about this, as I have currently never been above 4.5 sysNAND or emuNAND, but basically I guess the problem is a key used for signing saves with 6.0+ encryption is loaded when the console boots and is not reloaded by emuNAND booting.
So, in other words, your sysNAND needs to be the same as it was when you made the retail cart save (or at least within a compatible range). At least I think that's the basics of it.
In your case, you made your retail saves on a newer firmware sysNAND, so I don't think they will work if you downgrade your sysNAND to 4.x
BUT in theory you could downgrade to 4.x temporarily, install the legit .cias, then update your sysnand back to 9.2 in which case I think your retail saves would work again (not 100% on that, but it seems like it should work). The tricky part would be updating back to 9.2, since nintendo's servers would only officially give you the 9.6 update files.
I think you would have two options for getting back to 9.2 - 1.) there are apparently certain copies of SSB4 that have 9.2 on them. You could maybe get a retail cart of this if you are in the right region (not sure which region, but you should be able to find out with a search about "smash bros 9.2 update") 2.) I think you could use this program - https://gbatemp.net/threads/3dnus.376488/ to download the necessary .cia files to update from 4.x back to 9.2 (I'm not actually sure if this works, but if you can install update from other regions with that program I don't see why you can't use it to manually update to any version)
I have not actually done any of this and I'm just writing based off what I've read here on gbatemp, so do not take my post as 100% fact. I recommend reading a bit more around gbatemp before you try anything, and good luck.
OK then. What about a system transfer? After re-downloading, the games are now linked to the eshop account right? And system transfer also transfers the eshop account right? So will it be part of the new system?
I didn't reply to the why of your first question as it was such a easy test for you to do. For a system transfer, you can also test this yourself. But before you do crazy things and start moving it to all other consoles please think more about what nintendo can see on their end. Remember it is not only the nnid and eshop accounts tied to your console but also your serial number. So if you go and do transfers every 7 day window, you will most likely get flagged for suspicious activity. And think about the people you are selling those games to preinstalled, what if they called nintendo on a legitimate reason and they get caught. Is it really worth it for making a insubstantial amount?
On another note, this is why things stay private as its because people use the open methods for selfish gains.
Similar threads
