Hacking [Poll] The recent bandage and the highest firmware version you have ever updated to

[PrincessLillie]

As @Quantumcat has said:

I think what it is, is that when you update to 11.3 or 11.4, the update tries to write to firm, and if it can't it sends info back to Nintendo. Instead of asking what firmware version people are on, you should ask what is the highest firmware version they have ever updated to. I bet the people on 11.2 who got banned updated to 11.3 or 11.4 and then later on downgraded, for whatever reason (e.g. NTR streaming or Gateway).

This is entirely possible. So now, I pose the question: What is the highest firmware version you have ever updated to and are you banned? (example: I update to 11.4.0-37 and later downgrade to 11.2.0-35. The highest firmware version I have ever updated to is 11.4.0-37.)

 

[PrincessLillie]

Woops, autocorrect. Ignore title, pls fix it mods. It was supposed to say, banwave, not bandage.

 

[Elveman]

*watches thread*

Some clarifications need to be made in this theory. Does firm writing happen every time the 3DS is powered on?
If no (only with the update), can we bypass this by modifying sysUpdater to download updates from Nintendo servers?
If yes, can we even bypass it (with the help of B9S)?

 

[V0ltr0n]

I don't think this is the issue. A9lh/b9s don't stop firm from being written to.

To add to the data being collected here, i'm on 11.4.0-37U with b9s, am not banned and have never downgraded.

"bandage"

Also, firm writing does not happen every time you boot. I don't see a reason one would need to block firm writing either, assuming they already have cfw.

 

[RustInPeace]

This isn't the issue. Unbanned console was 11.3, then 11.4, then back down to 11.3 to retain streaming. Banned console, regular updating, I NAND restored on February for a different reason, it had the same firmware anyways.

 

[PrincessLillie]

"bandage"

I know... Stupid autocorrect.

This isn't the issue. Unbanned console was 11.3, then 11.4, then back down to 11.3 to retain streaming. Banned console, regular updating, I NAND restored on February for a different reason, it had the same firmware anyways.

Did you check before replying? Is it banned now?

Some clarifications need to be made in this theory. Does firm writing happen every time the 3DS is powered on?
If no (only with the update), can we bypass this by modifying sysUpdater to download updates from Nintendo servers?
If yes, can we even bypass it (with the help of B9S)?

Don't ask me. @Quantumcat is the one that made the theory. I simply just made the poll.

 

[Ryccardo]

Also, firm writing does not happen every time you boot.

It does since 11.3, actually, or so I heard - that's why many N3DS owners bricked by running 11.3 sysnand with Brickway's CFW

But the write protection patches work by just making the "install kernel title to boot partition" do nothing, so doesn't it just claim success?

If active verification code was added in the past updates, it would most likely have been caught in the massive comparison efforts done on 3dbrew on every update...

 

[RustInPeace]

Did you check before replying? Is it banned now?

Sigh, it's not banned, I'm telling you this isn't an issue.

 

[PrincessLillie]

Sigh, it's not banned, I'm telling you this isn't an issue.

:| Just answer the poll.

 

[RustInPeace]

:| Just answer the poll.

Done, you can see the results yourself, frankly it's a waste of time, I get the need of speculation and trying to grasp a reason, but this is too out there in my opinion.

 

[Quantumcat]

*watches thread*

Some clarifications need to be made in this theory. Does firm writing happen every time the 3DS is powered on?
If no (only with the update), can we bypass this by modifying sysUpdater to download updates from Nintendo servers?
If yes, can we even bypass it (with the help of B9S)?

I believe the firm writing happens every time the console loads the home menu - hence Gateway users losing a9lh/b9s when booting to sysNAND. Installing updates with sysupdater wouldn't help, the code that does the writing is in the update files. If the theory turns out correct then the probable solution would be to downgrade back to 11.2 and use a new friend code. Then use CTR-httpwn to play online. Unless someone was able to modify the update files. Keep in mind this is only a theory with no evidence yet :-) (except for the huge number of people banned with nothing in common but having CFW).

--------------------- MERGED ---------------------------

It does since 11.3, actually, or so I heard - that's why many N3DS owners bricked by running 11.3 sysnand with Brickway's CFW

But the write protection patches work by just making the "install kernel title to boot partition" do nothing, so doesn't it just claim success?

If active verification code was added in the past updates, it would most likely have been caught in the massive comparison efforts done on 3dbrew on every update...

That's also true. It's hard to see how they could get such functionality through. We can reverse engineer the updates and see the code, can't we?

 

[Geezerdorf]

In theory, it can be done. The persons with the correct equipment can look and see the commands described on all the sysupdates, but they would need to check almost every single line of code (interpreted or otherwise, look into the HEX coding to check ALL the changes that occur when running the sysupdate).

What i'd like to check is if the updates, or something inside the system, "behaves" strangely whenever it touches a NAND that has had installed BS9 or A9lh. I think that there's something people weren't looking at whenever a normal update was done on the system itself.

I really would like to have both, a good sacrifical lamb (3ds/2ds), and really proper knowledge of hacking to actually check it myself.

 

[YourHero]

Maybe it's because I've hardly touched my 3DS since the switch came out, but I'm on the latest FW and not banned. I played MH4U the other day online too. My Unit has always "sent info to Nintendo" as well as shown people what I'm playing. I updated to B9S even though I don't really use my 3DS as well. Maybe it's because I keep my 3DS off if I'm not playing it since the times I play are far and wide between.

 

[The Catboy]

My Goat system is always up to date for testing purposes. So it was actually on 11.4 when it got banned.
Main however is also on 11.4 and not banned

 

[Geezerdorf]

My Goat system is always up to date for testing purposes. So it was actually on 11.4 when it got banned.
Main however is also on 11.4 and not banned

Yeah. i've been gathering info, and i think it can be narrowed down with some internal insight (given the changes), but unfortunately, neither i have the tools, nor the knowledge to check it myself. I just hope the people that is adept in such are already checking in those same venues.

 

[The Catboy]

Yeah. i've been gathering info, and i think it can be narrowed down with some internal insight (given the changes), but unfortunately, neither i have the tools, nor the knowledge to check it myself. I just hope the people that is adept in such are already checking in those same venues.

I've been running tests on my extra 3DS (that I've since just named Goat.) My first tests was leaving Spotpass on with FBI running and online. The system was promptly banned a few hours later. I then unbanned my system and turned off spotpass and repeated the same test. Which has been just leaving the system online with FBI, then swapping over MK7 (since it just gives you an error code the second you try to go online, so it's the fastest game to test on.) Thus far it's been since Friday and Goat has not been banned again. So I am guessing Nintendo is getting their information from Spotpass, although that's purely speculation on my end.