Rumor AntiPiracy extreme measures from ninty !

[izy]

While I think this is BS, I don't know why everyone is "Nintendo would never do such a thing", everyone already forget about the intentional bricking of region changed Korean Wiis?

Nintendo already crossed that line.

you mean the fact Korean Wiis had an encryption key and people kept updating their system menus and other wads from another region without removing the encryption key

they didnt cross any lines there it wasnt like they actively messed with your console
the encryption was in place
people just tried hacking foreign consoles without removing encryption and got error 003

it was still fixable

thats like saying people flashed custom firmware without changing the bootloader to support it and complain their object doesnt boot

 

[sudeki300]

has someone from xecuter got a job at nintendo then...

 

[Armadillo]

you mean the fact Korean Wiis had an encryption key and people kept updating their system menus and other wads from another region without removing the encryption key

they didnt cross any lines there it wasnt like they actively messed with your console
the encryption was in place
people just tried hacking foreign consoles without removing encryption and got error 003

it was still fixable

thats like saying people flashed custom firmware without changing the bootloader to support it and complain their object doesnt boot

It wasn't there/used until a certain update.


Up until X update (I can't remember the update), you could update region changed Koren Wii's fine. After the update, 003.


Nintendo intentionally changed it to encrypt something with Korean key and check the result, if it match=003.


There was 0 need for the U/E/J system menus to try and encrypt against the Korean key to check for it's presence and yet Nintendo added it and made it throw 003 if it was there and at the time, that was effectively a brick.


It was an intentional check to see if had been region changed, not some random "incompatblity", but an intentional choice by Nintendo. How is an intentional check not "actively messing with your console"?

thats like saying people flashed custom firmware without changing the bootloader to support it and complain their object doesnt boot

Yeah, because that is of course, exactly the same as an intentionally check and intentional result.

Intentionally adding a piece of code, on E/U/J system menus, to encrypt something against the Korean key, and if the result matches, intentionally give you 003, is exactly the same as something like a incompatible bootloader.

Not shocked that when it's Nintendo getting their hands dirty, it's the users fault.

 

[halfashark]

the amount of stupid children who would put random crap on their SD card including homework would trigger potentially millions of false positives
not to mention the amount of people who just find a random microSD at the bottom of a drawer and would slot it in without a second thought.

what a ridiculous thread.

 

[Ettino]

Put on a tin foil hat.

Nintendo did the same to Wii U last update! Look at how many consoles the update 5.5.6U killed? Dozen of them! Dozen, I say!

It's magic bullet theory all over again!

 

[tech3475]

Are we sure they didn’t just hire Samsung to handle the firmware?

 

[izy]

It wasn't there/used until a certain update.


Up until X update (I can't remember the update), you could update region changed Koren Wii's fine. After the update, 003.


Nintendo intentionally changed it to encrypt something with Korean key and check the result, if it match=003.


There was 0 need for the U/E/J system menus to try and encrypt against the Korean key to check for it's presence and yet Nintendo added it and made it throw 003 if it was there and at the time, that was effectively a brick.


It was an intentional check to see if had been region changed, not some random "incompatblity", but an intentional choice by Nintendo. How is an intentional check not "actively messing with your console"?



Yeah, because that is of course, exactly the same as an intentionally check and intentional result.

Intentionally adding a piece of code, on E/U/J system menus, to encrypt something against the Korean key, and if the result matches, intentionally give you 003, is exactly the same as something like a incompatible bootloader.

Not shocked that when it's Nintendo getting their hands dirty, it's the users fault.

so what your saying is the encryption key was there and wasnt under use

then nintendo in their infinite wisdom added a security update that prevented you booting custom firmware

until someone released a patch to support it





looks at every custom firmware currently actively being updated

ahem literally every major nintendo switch, 3ds firmware update etc

the difference here is op is fearmongering with saying that their new update will actively scan sd card for 3rd party content and brick your emmc because of it which in fact would be illegal

also it would be more detrimental to none cfw users than cfw users

because it would work like this

ninty release firmware than scans sd card and bricks emmc
cfw users that this effect (if they somehow released atmos update that allows you to even boot this and they dont discover its bricking emmcs lmao)
they all have emmc backups in some form so a switch could easily be restored and b then it would be patched out in cfw in the 0.000001% that even happened

stock users who tried to even put rcm files etc on their sd cards would be SoL

 

[binkinator]

Innocent users borrows a spare SDCard from a neighbor and it has old hax on it (that don’t even work!)

BAM…bricked Switch.

Lawsuit incoming in 3…2…1

 

[dehydrated_lemur]

When did Microsoft do this?

 

[Armadillo]

so what your saying is the encryption key was there and wasnt under use

Korean key always existed on Koreans Wii's, yes.

then nintendo in their infinite wisdom added a security update that prevented you booting custom firmware

Not custom firmware, just the stock E/J/U system menu on a Korean wii and even if you want to claim stock other region menu counts as "custom" firmware, it didn't just stop you booting a cfw, but intentionally bricked it and gave you the 003 modified error. You could do nothing with the console until eventual community fixes (drivechips, savemii and other options came out).

Even Nintendo's site says 003 renders the console inoperable and can't be fixed (clearly not true once the community found fixes,). So trying to frame it as just "stops you booting custom firmware" is disingenuous.

looks at every custom firmware currently actively being updated

I don't recall any custom firmware bricking you if you do a system update before it's ready. If you do, you can just stay on system firmware and carry on using your console until the cfw is updated. Not so with Nintendo's intentional patch, you were bricked until eventually the community came around with a solution.

Stuff.

I never said this was a thing, just that Nintendo are happy to cross that line and already have.

 

[Purple_Shyguy]

Source: Dad (he works at Nintendo)

 

[linuxares]

I think we lock this topic since it will provide nothing properly without proof.