No. Cfws block firm 0 and firm1 updates or changes. And firm0/firm1 is where a9lh is located. As its blocked by cfws its impossible to Nintendo to remove a9lh unless they go to your house by themselves and restore a pre-a9lh backupwell a9lh is stored on the nandso if you update your sysnand with a newer update could nintedo make the new update brick your 3ds or overwrite a9lh
CFWs are probably going to patch that.Couldn't they update another partition that would fail to start (like Home Menu) unless you had a certain version of the firm partitions?
Couldn't they update another partition that would fail to start (like Home Menu) unless you had a certain version of the firm partitions?
ARN now loads the firmware.bin from CTRNAND so that's no longer a problem.Couldn't they update another partition that would fail to start (like Home Menu) unless you had a certain version of the firm partitions?
ARN now loads the firmware.bin from CTRNAND so that's no longer a problem.
However, Nintendo could (though it's very unlikely) exploit their own kernel in order to overwrite FIRM0/1 back to stock.
That's why I said it's very unlikely. However, it is still possible that Nintendo can do something.If i'm not mistaken Nintendo will probably not want to do that.
I think its pretty silly to say something like this.Nintendo can't do shit!
And then somebody will update, then comes crying to GBAtemp and we'll know not to make the same mistake until a fix will be made.I think its pretty silly to say something like this.
Nothing is flawless. There is ALWAYS a way.
Just because you cannot think of a way right now does not mean that Nintendo won't find a way eventually.
Now will Nintendo care enough to dedicate time & resources to finding a way? Thats another story.
And then somebody will update, then comes crying to GBAtemp and we'll know not to make the same mistake until a fix will be made.
But if they do that, then we can RE their own kernel exploit and use it to reinstall A9LHARN now loads the firmware.bin from CTRNAND so that's no longer a problem.
However, Nintendo could (though it's very unlikely) exploit their own kernel in order to overwrite FIRM0/1 back to stock.
then we will switch to emunands or wait until someone works around it, like with early n3ds cfwwhat if they make the new update brick your 3ds if you have a9lh
Use A9LH to restore?what if they make the new update brick your 3ds if you have a9lh
Not if it bricks FIRM0/1.Use A9LH to restore?
Not if it bricks FIRM0/1.
All major CFWs now prevent FIRM0 and FIRM1 from being writtenThen I guess we better find a way to keep Nintendo away from firm0/1.