Full access to the system will be possible only if you're under certain firmware. I think that's good enough.More importantly, nothing will ever be gained from downgrading a Switch aside from research.
Full access to the system will be possible only if you're under certain firmware. I think that's good enough.More importantly, nothing will ever be gained from downgrading a Switch aside from research.
Full access to the system is possible under RCM regardless of one's system version. Any exploits inherent to a low system version require that the console can boot into that system version without RCM, so downgrading is entirely useless.Full access to the system will be possible only if you're under certain firmware. I think that's good enough.
In particular, I'm talking about what @SciresM mentions in this post:Full access to the system is possible under RCM regardless of one's system version. Any exploits inherent to a low system version require that the console can boot into that system version without RCM, so downgrading is entirely useless.
Full access to the system will be possible only if you're under certain firmware. I think that's good enough.
I'm lost. Then why are we recommend to stay on 4.10 max?It seems that there is a bit of confusion. To clarify, in order for you to disable fuse checks, you would need full access/privileges to do so. And if you have full access/privileges, there is no purpose to downgrade except for research purposes.
So you can run hax without a jig and usb later on when deja vu is releasedI'm lost. Then why are we recommend to stay on 4.10 max?
The software exploits on lower system versions mentioned in that post require a functional OFW that can boot on its own and hasn't been downgraded.
If you don't want to use a jig/AutoRCM and a USB-C payload, you need to be on a lower system version to launch CFW from something like the web browser. In the future, lower system versions might even get an untethered coldboot exploit. Downgrading is pointless, because you would have to use a jig/AutoRCM and a USB-C payload to get into your Switch each time you turn it on after the downgrade.I'm lost. Then why are we recommend to stay on 4.10 max?
So -and cope with me, it's late and it has been a very long day of work- doesn't make sense to downgrade to 4.10 then?So you can run hax without a jig and usb later on when deja vu is released
Downgrading is possible but will have no advantages because of the efuses plus the downgrade process can brick the switch if something goes wrongSo -and cope with me, it's late and it has been a very long day of work- doesn't make sense to downgrade to 4.10 then?
If you don't want to use a jig/AutoRCM and a USB-C payload, you need to be on a lower system version to launch CFW from something like the web browser. In the future, lower system versions might even get an untethered coldboot exploit. Downgrading is pointless, because you would have to use a jig/AutoRCM and a USB-C payload to get into your Switch each time you turn it on after the downgrade.
So -and cope with me, it's late and it has been a very long day of work- doesn't make sense to downgrade to 4.10 then?
If you downgrade to 4.1.0, you will be unable to use your Switch without a jig/AutoRCM and a USB-C payload. Because of this, you will get no benefit from the downgrade. None of your 4.1.0 exploits will work without first using RCM to load your Switch OS. There is no way around it.Ok, and I promise now I go to sleep: so if we downgrade, and then we avoid the fuse checking g, then the coolbot would be factible?
I think I will re-read all this tomorrow. Thanks for your patience!
If you downgrade to 4.1.0, you will be unable to use your Switch without a jig/AutoRCM and a USB-C payload. Because of this, you will get no benefit from the downgrade. None of your 4.1.0 exploits will work without first using RCM to load your Switch OS. There is no way around it.
Do you understand now why downgrades are entirely pointless?
It will probably never be possible to disable the efuse check without using a jig/AutoRCM and a USB-C payload every single time you turn the Switch on, so downgrades are pointless.Ok. So the reason for using a jig/autoRCM in a downgraded 4.10 is because it checks the fuses. As we can't disable that check, we need the jig or autoRCM. We can't disable that yet, so it's pointless doing any downgrade... Right?
Sorry guys, my confusion was why it was not possible boot once, disable fuse check, so no more cable was needed. I forgot it's something that can't be done yet.
I think I will call it a day, guys. Thanks for being so patient explaining this. ^^ Tomorrow I will respond read everything and I will feel ashamed of not understanding this with the first explanation.
Ok, now I got it. And it's something you already mentioned earlier. Sorry, I really feel knacked right now.It will probably never be possible to disable the efuse check without using a jig/AutoRCM and a USB-C payload every single time you turn the Switch on, so downgrades are pointless.
You can't factory reset the fuses once they are burned. Those are permanent hardmods made to your system every few system updates.Is there no way to factory reset your switch to it's original firmware?