Homebrew Could we avoid any future console bans using an EmuNAND/RedNAND?

[Storm Eagle]

I imagine Nintendo is not going to let up with their bans as we've been shown that Nintendo is certainly capable of detecting and banning everyone who has CFW, even false positives on top of that.
This begs the question: Will EmuNANDs/RedNANDs make a return, and permanently this time? We have been shown that EmuNANDs and RedNANDs have no connection to the SysNAND whatsoever and any .CIAs installed on one NAND will not show up on the other provided they are linked.
Using this to our advantage, could we avoid any future console bans and reduce the need of public friend code seeds? Here's the general idea:

1. We create an EmuNAND/RedNAND and format it to unlink the NANDs.
2. If you are already banned, a new localfriendcodeseed_b is used to unban your SysNAND or EmuNAND, depending on what NAND you want to use online features on.
3. Based on your preference, all forms of homebrew will be deleted on either the SysNAND or EmuNAND, depending on the NAND you want to use online features on.
4. (Optional) If you plan on using EmuNAND to play your games online, you would make a new NNID and move all of your tickets to the EmuNAND to redownload them on the eShop.

With one NAND having custom .CIAs on it and the other NAND being completely clean, there would likely be no way of Nintendo detecting CFW and handing out future bans short of reading your SD card for boot.firm, etc. This would be the ideal scenario due to EmuNAND being a completely sandboxed environment. It would be borderline impossible for Nintendo to detect and ban anyone who did this.
Would it be possible to move back to EmuNAND and avoid any future bans?

 

[Deleted User]

The question is if the ban would effect both NANDs since the id's would still be linked to the 3ds.The reason changing your localfriendcodeseed_b works so well is because it tricks Nintendo to think your 3ds is a different 3ds,otherwise if the emunands where truly different we could randomly spoof the localfriendcodeseed_b's,but we can't now can we. Since the emunand is a clone of the sysnand under a different format I'd but still encrypted under your system persay.

 

[Storm Eagle]

The question is if the ban would effect both NANDs since the id's would still be linked to the 3ds.The reason changing your localfriendcodeseed_b works so well is because it tricks Nintendo to think your 3ds is a different 3ds,otherwise if the emunands where truly different we could randomly spoof the localfriendcodeseed_b's,but we can't now can we. Since the emunand is a clone of the sysnand under a different format I'd but still encrypted under your system persay.

I definitely think that the bans are separate. I was asking whether the EmuNAND and SysNAND could have two different localfriendcodeseeds. I imagine the homebrew NAND would use your private seed while the legitimate NAND would use a public seed. Even if they don't use two different seeds now, I imagine it would certainly be possible to modify how EmuNANDs work and allow for two different seeds altogether.

If both NANDs have two different seeds, then it wouldn't really matter if the homebrew NAND is banned, because the legitimate NAND would use a different seed.

 

[Deleted User]

I definitely think that the bans are separate. I was asking whether the EmuNAND and SysNAND could have two different localfriendcodeseeds. I imagine the homebrew NAND would use your private seed while the legitimate NAND would use a public seed. Even if they don't use two different seeds now, I imagine it would certainly be possible to modify how EmuNANDs work and allow for two different seeds altogether.

If both NANDs have two different seeds, then it wouldn't really matter if the homebrew NAND is banned, because the legitimate NAND would use a different seed.

Well if the bans are truly separate someone should test it by making a emunand on a dummy 3ds and see if the the emunand remains unbanned when the sysnand gets banned or vice versa.If that works then we could also generate localfriendseedcodes.

 

[Storm Eagle]

Well if the bans are truly separate someone should test it by making a emunand on a dummy 3ds and see if the the emunand remains unbanned when the sysnand gets banned or vice versa.If that works then we could also generate localfriendseedcodes.

If the NANDs are linked at the time of being banned, then yeah the EmuNAND will be banned, but there should be a way to inject a localfriendcodeseed specifically to EmuNAND after it is unlinked from the SysNAND.
Or the EmuNAND can be unlinked and stay banned with the homebrew apps on it while the SysNAND has all of it's homebrew removed while the localfriendcodeseed is injected into SysNAND.
Provided you are using the SysNAND without homebrew, if the SysNAND is unlinked from the EmuNAND, I don't see EmuNAND using the SysNAND localfriendcodeseed, and even if it does use the SysNAND localfriendcodeseed, you could just disable WiFi before entering the EmuNAND to avoid sending data to Nintendo.

 

[Deleted User]

If the NANDs are linked at the time of being banned, then yeah the EmuNAND will be banned, but there should be a way to inject a localfriendcodeseed specifically to EmuNAND after it is unlinked from the SysNAND.
Or the EmuNAND can be unlinked and stay banned with the homebrew apps on it while the SysNAND has all of it's homebrew removed while the localfriendcodeseed is injected into SysNAND.
If the SysNAND is unlinked from the EmuNAND, I don't see EmuNAND using the SysNAND localfriendcodeseed, and even if it does use the SysNAND localfriendcodeseed, you could just disable WiFi before entering the EmuNAND to avoid sending data to Nintendo.

Well yeah linked of course will be banned on both lol.But unlinked is a mystery to me since we generate a new encryption id in the Nintendo 3DS folder when when we format the system but its unique to that specific 3ds.

 

[stl25]

That would just be funny if emuNAND was to make a comeback. I remember when emuNAND was the shit and then it was sysNAND master race. I honestly don't think emuNAND is the answer to any of this and I am an emuNAND user.

 

[Deleted User]

The point I'm trying to make is each time we inject a localfriendcodeseed_b,it comes from a different 3ds.So if the emunand comes from the same system then it probably doesn't count.

 

[Quantumcat]

This isn't useful, you still need a donor console for the second friend code to use in your emuNAND. Otherwise, don't you think people would have been creating emuNANDs to get new friend codes, instead of using other consoles?

 

[Storm Eagle]

This isn't useful, you still need a donor console for the second friend code to use in your emuNAND. Otherwise, don't you think people would have been creating emuNANDs to get new friend codes, instead of using other consoles?

Public friend code seeds exist, though.

 

[TheDarkGreninja]

Public friend code seeds exist, though.

Which can get easily banned since, crazily enough, Nintendo has access to the internet.

 

[Storm Eagle]

Which can get easily banned since, crazily enough, Nintendo has access to the internet.

Considering they haven't been banned yet, I'm not sure they even would ban them unless someone breaks the ToS again using that public friend code seed, which I would hope people would have the decency not to do that, assuming they are using an EmuNAND like I suggested.

 

[TheDarkGreninja]

Considering they haven't been banned yet, I'm not sure they even would ban them unless someone breaks the ToS again using that public friend code seed, which I would hope people would have the decency not to do that.

pretty sure seed 1 and 2 have been banned on the unban thread.

 

[Storm Eagle]

pretty sure seed 1 and 2 have been banned on the unban thread.

The others? How do we know that those two seeds weren't banned due to something stupid such as going online before a game releases, etc.?

 

[TheDarkGreninja]

The others? How do we know that those two seeds weren't banned due to something stupid such as going online before a game releases, etc.?

You've just answered why we should use public seeds, thanks.

 

[Quantumcat]

Public friend code seeds exist, though.

They'd get banned pretty fast, if there's no controls over who has access to them. And there's only a limited supply of them.

 

[Deleted User]

pretty sure seed 1 and 2 have been banned on the unban thread.

Well there is one I'm using,but it's not on the chaos site.

 

[JayTD]

Give the developers two weeks and they'll have something sorted, these bans are concrete but they arent unavoidable.

Nintendo didnt hire a competent network developer to hand out bans, they spaghetti coded something together based off their Sun/Moon bans to look like they're actually trying to stop piracy. The reason Sun/Moon bans weren't a major call for ban protection is because if you were dumb enough to play a unreleased game online you deserved the ban, but im sure someone learnt something from that and will bring it up within the week.

All homebrew CIA's will more than likely come with something to hide themselves from Activity Log, that should be the most obvious step. That was the first thing 360/PS3 devs found out, if you were caught playing Multiman/XEXMenu on Xbox Live/PSN you were as good as dead.

Next is SysCalls, which Nintendo probably wont bother with for another couple years, and at that point the 3DS will be the least of their worries.

The way you're describing is DualNand, something used often in Xbox 360 modifications, which requires two NAND chips and two FriendSeed equilivants to separate the unsigned code from the legitimate code and allows people to still play normally on top of playing their homebrew/whatever on the same console instead of buying another.

Im sure its possible, but how many people will go for it considering the legitimate NAND wouldnt be able to play the non-legitimate code is probably not alot.

 

[TheDarkGreninja]

Well there is one I'm using,but it's not on the chaos site.

Thats great for you, you're unlikely to get banned again, although I wouldnt risk it.

 

[Storm Eagle]

Give the developers two weeks and they'll have something sorted, these bans are concrete but they arent unavoidable.

Nintendo didnt hire a competent network developer to hand out bans, they spaghetti coded something together based off their Sun/Moon bans to look like they're actually trying to stop piracy. The reason Sun/Moon bans weren't a major call for ban protection is because if you were dumb enough to play a unreleased game online you deserved the ban, but im sure someone learnt something from that and will bring it up within the week.

All homebrew CIA's will more than likely come with something to hide themselves from Activity Log, that should be the most obvious step. That was the first thing 360/PS3 devs found out, if you were caught playing Multiman/XEXMenu on Xbox Live/PSN you were as good as dead.

Next is SysCalls, which Nintendo probably wont bother with for another couple years, and at that point the 3DS will be the least of their worries.

This is somewhat relieving. All we need are methods to get more (public?) friendcodeseeds.