But that sounds like in an update they can touch arm9 processors, so wouldn't that screw over both anyway?
Maybe menuhax + emuNAND, A9LH not really no because of FIRM0/FIRM1 (i think its only one) are corrupt and there is no way of updating
But that sounds like in an update they can touch arm9 processors, so wouldn't that screw over both anyway?
Lml, but didn't we just go over how a hardware revision can break itMaybe menuhax + emuNAND, A9LH not really no because of FIRM0/FIRM1 (i think its only one) are corrupt and there is no way of updating
Lml, but didn't we just go over how a hardware revision can break it![]()
So therefore they can't break either, without adding some extra shit thenHardware revision, have a think![]()
Maybe menuhax + emuNAND, A9LH not really no because of FIRM0/FIRM1 (i think its only one) are corrupt and there is no way of updating
It's not possible to overwrite A9LH ever, even if you want to?
I doubt they can patch menuhax if your on 9.2 with an emunand set up Maybe they can break your emunand with a sw update but you could just set it up again... maybe a9lh can be broken with an update and brick your device since my understanding of it is your updating your sysnand not emunand but once again you could also restore a backup I don't think it's possible for Nintendo to kill either one of them the worst they can do is try to ruin our day but that's about it
Sent from my Pixel using Tapatalk
Is that you Nintendo?A9lh or menuhax->cfw?
Cause I was thinking about this and read how they needed a hardware revision to block a9lh, but no mention of how they could block menuhax->cfw. But then I thought, can they even do that for someone using menuhax?
I mean, I feel like a9lh is pretty safe cause o dat brick protection it has when I'm using it, and that ninty wouldn't actually do the damn revision XD
well actually, a partition table check could ruin someones day.If they did that, somehow which I highly doubt without physically hardcoding firm0/firm1 then, they'd have many bricks and wouldn't legally be held against it :v
well actually, a partition table check could ruin someones day.
or they can simply try and load firm0 and firm1 and if detects that neither is bootable/changed in some way then it could simply abort the startup![]()

Much like how Google did with Android 7.0 (g.co/ABH), and that was done through software.or they can simply try and load firm0 and firm1 and if detects that neither is bootable/changed in some way then it could simply abort the startup![]()
When the firm01/firm1 is corrupt due to how A9LH works, plus firm protection because of that, goodluck

Well OK, that partition table check. That could potentially fk over menuhax->cfw
But if it's something as obvious as partition table check, why haven't they done it already?
But if it's something as obvious as partition table check, why haven't they patched it already?


