Is there any point to preventing eFuse burning anymore? As I understand it, the point of it was to allow systems to be downgraded to earlier OS versions in the event someone ever created an automatic payload delivery system similar to the 3DS. Aside from TX's upcoming soldered in chip, which I assume would combine the functionality of the payload delivery dongle, is there even anyone working on this? I seem to vaguely recall reading something about how Firmware 4.1 had a viable exploit for this, but here we are a year or so later, and it doesn't seem like anything has changed. So is there really any reason to be worrying about preserving eFuses at this point?
The answer to your question is subjective.
If you're content with forever using whichever exploit you're already using, then no, I guess preserving your fuse count doesn't really matter.
Some system versions are also many times more valuable than others. For example, keeping a fuse count that comports with 3.0.0 is arguably valuable, while a fuse count that comports with 9.0.0 arguably is not.
Which system version are you on, and is your system RCM vulnerable?
If you're content with forever using whichever exploit you're already using, then no, I guess preserving your fuse count doesn't really matter.
Some system versions are also many times more valuable than others. For example, keeping a fuse count that comports with 3.0.0 is arguably valuable, while a fuse count that comports with 9.0.0 arguably is not.
Which system version are you on, and is your system RCM vulnerable?
My system came with 4.1 and I've been using AutoRCM ever since I got a SX Pro. I've been hoping that at some point there'd be a way to load the entire exploit chain automagically like my 3DS so I don't need to fish out and charge the payload dongle every time I reboot my Switch.
Probably would be a long time before there is really a coldboot without any modchip involve.
Not as far as I know that someone is publically working on a coldboot, because it can be archieved via hardmod a modchip like trinket M0, along with AutoRCM and Autoboot.
So basically there's probably little point to worry about efuses if my system has the RCM vulnerability if my main reason was to preserve the option of a cold boot solution if/when one becomes available.
Fuse has to do with anti downgrade, if you burn too many fuse and was on a lower firmware the system refuse to boot, the software base exploit Deja Vu only work up to 7.0.1, maybe one day there will be a coldboot exploit, can't tell what firmware it would require, that why some people like to keep their fuse low.
-
-
-
@
SylverReZ:
@Maximumbeans, Indeed. I've been working on getting this Infecutus chip to work on my PS2. But after soldering, I realised that a plastic piece was missing from the power ribbon cable to the power and eject buttons. -
@
SylverReZ:
Now I could go with soldering the contacts from the cable to the connector on the mobo, but doesn't sound like a good permanent solution.
-
@
Maximumbeans:
Man, that's beyond my brain
I'm no good with hardware for now. I'd like to get into hardmods in future though -
@
SylverReZ:
@Maximumbeans, Maybe start practice soldering. Get a cheap-ass soldering iron and follow some good YouTube tutorials.+1
-
@
SylverReZ:
Least my experience has gotten better than over a decade ago. My iron would constantly bump into components and break them.
-
@
Maximumbeans:
Sounds good. I actually did soldering but like 16 years ago for school so uuuuh probably rusty haha
-
@
SylverReZ:
@Maximumbeans, Same here. I did soldering at school from a teacher who I honestly liked since he had plenty of good electronics experience.+1
-
-
-
-
-
@
SylverReZ:
It was like all clear and fancy. Tbf I'm not too experienced with chess, but would like to learn someday.
-
-
-
-
-
-
-
-
-
-
-
