It would only allow exploits that were patched by the newer revision to work again (like mch2) and while the overall concept is unpatchable, it is possible for them to make it impossible for us to reach a workable firmware version by making a new kernel version release.
Actually nevermind, I found his other posts. I'll decrypt them myself.Really the only reason we can downgrade native_firm like this in the first place without bricking the console is because the kernel/firm check only checks major/minor versions, not the revision. So we can go from 2.50-11 (10.4) all the way down to 2.50-1 (9.6), but not to 2.49-0 (9.5).
Yeah but "everyone" are asshole's unlike youlol. I'm flattered that you would say I came up with this idea. I'm probably just the first to fully explain the process here. I didn't come up with the idea. As 3DBrew has said. It was discovered by "everyone".
Really the only reason we can downgrade native_firm like this in the first place without bricking the console is because the kernel/firm check only checks major/minor versions, not the revision. So we can go from 2.50-11 (10.4) all the way down to 2.50-1 (9.6), but not to 2.49-0 (9.5).
Now all we need is to find a kernal exploit... which at the most will take a year.
Get to work slave monkey I wanna have a go at thisGotta have it on every page...
Can I do this without a hard mod?
I became the mod Nazi like Seinfeld's soup Nazi. "NO MOD FOR YOU!"Get to work slave monkey I wanna have a go at this
Next page dammit!Can you acheive this without a hardmod?
jk. I'll read your instructions when they're done being under revision and then make a video tutorial (after i get enough money to buy another 3ds).
So, after we get to 10.2 from 10.4/10.5, we can use sysUpdater to downgrade to 9.2?[/spoiler
Are you replying to my spoiler or my joke?No, as it clearly states.