Nintendo isn't Gateway, they won't brick your system with a bricker update.Or, they'd have to sneakily drop a malicious arm9loaderhax.bin bricker on your console, and I'm pretty sure they can't do that legally in MANY jurisdictions.
Nintendo isn't Gateway, they won't brick your system with a bricker update.Or, they'd have to sneakily drop a malicious arm9loaderhax.bin bricker on your console, and I'm pretty sure they can't do that legally in MANY jurisdictions.
Nintendo isn't Gateway, they won't brick your system with a bricker update.
Like I said, they aren't that bad. Sony, on the other hand...they would, if it was legal. It isn't, obviously.
I'd go so far as to say that Nintendo wants to patch homebrew but that they may not see it as a direct threat. Especially considering OOTHax, SMCH, etc remain unpatched.
Bet they didn't see the downgrade bullet being as big a thing as it was.
They're probably mad now, I'd imagine 11.1 will do it's best to patch that stuff.
Oh, Oothax is partly patched, it takes a lot of tries to get it to work on the latest firmware.
I'm a CFW dev. Trust me, I'm aware. It's due to removal of internet access and ASLR. They could fix the game on cartridges and it wouldn't be usable on 9.2/whatever, though, and that's more what I'm referring to.
a little off-topic question, but how can I ensure that firm0/1 protection is on?
I'm using Luma3DS+A9LH on a N3DS.
Didn't stop them from bricking a ton of Wii's with a update
Short answer they can't. But new hardware will most likely kill a9lh
A9lh happens to early in boot for the system update to fix it correct me if I'm wrong. Once you have your OTP its a wrap
They said that about boot2 for bootmii, and that still got patched.
That wasn't patched by software. It was a hardware revision.
They also patched it in one of the 4.X FWs for old Wiis
http://wiibrew.org/wiki/Error_003Only wave of bricks I've heard of/read about involved installing a Korean system update on non-Korean Wiis, yet the Wiis received the notification to update because their regions had been changed.
To add to the actual discussion, though, they could probably find a way if they really wanted to. Either through the already mentioned file re-naming, stability update, or what have you. Honestly (without getting into the piracy discussion) I don't think it's worth their time, since the best way to do it seems to be a new hardware revision (but it'd be silly naming it the new new 3ds ).
KernelNintendo don't care that much about security... I mean if it was easy fix they will do it, if not easy they will not do anything most likely.
Boy, it's been 3 month since the Wii U Kernal exploit is out for the latest FW, AND IT STILL NOT PATCHED