@Reisyukaku made a post on Twitter showcasing him performing something similar to TX's advertised "AutoRCM" feature.
Rei's Twitter: https://twitter.com/Reisyukaku
Rei's Twitter: https://twitter.com/Reisyukaku
@Reisyukaku made a post on Twitter showcasing him performing something similar to TX's advertised "AutoRCM" feature.
Rei's Twitter: https://twitter.com/Reisyukaku
YupSo is this similar to what was described in A post on here about intentionally bricking your system?
You would have to invalidate the rsa key sitting inside the BCT doing so for all four of the BCTs. You just need to change one byte per key and your switch will always boot into RCM.How can we do this?
I def see A USB cable..Its the jig u can lose with this.No need for a USB-C cable?
I def see A USB cable..Its the jig u can lose with this.
All firms.. since its just using a "corrupt the nand intentionally" technique.@Reisyukaku Is this only sub 4.1 or ...even current firmware? Im wondering if I should stay on 4.1 and its harder tp wait from day to day
So..please correct me if I'm wrong. There's absolutely no point on staying on old firmware anymore is there?All firms.. since its just using a "corrupt the nand intentionally" technique.
In theory no reason. I'm still on 2.0.0 though in just in case. *shrug*So..please correct me if I'm wrong. There's absolutely no point on staying on old firmware anymore is there?
Superb discovery, my hat's off to you!
This will work on all current and all future firmwares. But it can be easily detected by Nintendo if you manage to boot into Horizon without reverting those modifications.Is this only sub 4.1 or ...even current firmware?
Still need a USB host to inject some payload.No need for a USB-C cable?
So..please correct me if I'm wrong. There's absolutely no point on staying on old firmware anymore is there?
Superb discovery, my hat's off to you!
Same on 4.1. That damn ''just in case'' ehIn theory no reason. I'm still on 2.0.0 though in just in case. *shrug*