autoRCM is already a brick that’s unfixable without a hardmod on ipatched systemsSource: TX
"Guys, Do not update past 7.01, There has been reports of the incoming 8.0 fw bricking systems with auto rcm.
This applies to patched and non patched units."
I cant link the post. Sorry.
>implying that getting access to Switch dev tools/firmwares is difficult
kek
the "fuckers at tx" got proper sigpatches before anyone else on 7.x
--------------------- MERGED ---------------------------
you gotta show them respect kek
--------------------- MERGED ---------------------------
@ZachyCatGames im not saying its difficult
--------------------- MERGED ---------------------------
you gotta show them respect kek
--------------------- MERGED ---------------------------
@ZachyCatGames im not saying its difficult
You know how hard it is to get switch firmware?autoRCM is already a brick that’s unfixable without a hardmod on ipatched systems
>implying that getting access to Switch dev tools/firmwares is difficult
kek
I just type switch x firmware download into google and bam i get links
I'd highly recommend it, it makes things extremely convenient. The chips are pretty cheap too!
No they didn't
The open source devs got the sig patches long before tx supported 7.0
I’m talking about dev firmwares. Getting them isn’t particularly difficult either though
This seems like stupidity.
For one, without a USB-exploit of course a patched unit put into RCM becomes a brick. What exactly do you think happens if you boot the system into permanent recovery with no way to then tell it what to do other than to be permanently in recovery mode?
For two, this is illegal to actually intentionally do and Nintendo cannot "brick" their own recovery mode. That makes like no sense.
For one, without a USB-exploit of course a patched unit put into RCM becomes a brick. What exactly do you think happens if you boot the system into permanent recovery with no way to then tell it what to do other than to be permanently in recovery mode?
For two, this is illegal to actually intentionally do and Nintendo cannot "brick" their own recovery mode. That makes like no sense.
if you can boot to RCM to install autorcm, then you can reboot again to RCM to uninstall autorcm
And Game_Over says:
"
Also the next firmware update from Nintendo is expected to roll out very soon. This update could possibly come today.
DO NOT UPDATE YOUR SWITCH PAST FIRMWARE 7.0.1 if you expect to continue using SX OS or any other CFW. As we have seen in the last few updates, Nintendo has taken great efforts to lock out the console from running CFW. Rumors in the scene are indicating that the next update could possibly introduce some more serious obstacles that could potentially brick consoles that have AutoRCM enabled. This is speculation right now, as we won't know for SURE until the firmware releases. For now, it is best to stay safe and STAY OFFLINE. Also decline any and all updates if you are prompted until news is posted here.
It is also highly advised that users who plan to run CFW on patched units also stay on a firmware 7.0.1 or lower until further notice. (no eta)
I strongly suggest everyone do a full emmc (nand) dump and store it somewhere safe."
"
Also the next firmware update from Nintendo is expected to roll out very soon. This update could possibly come today.
DO NOT UPDATE YOUR SWITCH PAST FIRMWARE 7.0.1 if you expect to continue using SX OS or any other CFW. As we have seen in the last few updates, Nintendo has taken great efforts to lock out the console from running CFW. Rumors in the scene are indicating that the next update could possibly introduce some more serious obstacles that could potentially brick consoles that have AutoRCM enabled. This is speculation right now, as we won't know for SURE until the firmware releases. For now, it is best to stay safe and STAY OFFLINE. Also decline any and all updates if you are prompted until news is posted here.
It is also highly advised that users who plan to run CFW on patched units also stay on a firmware 7.0.1 or lower until further notice. (no eta)
I strongly suggest everyone do a full emmc (nand) dump and store it somewhere safe."
But there are ways to install AutoRCM that don't involve using RCM mode.
Doesn't really make a whole lot of sense though because without RCM you can't run any homebrew, and even if you could it would be user mode only and not have the access needed to install AutoRCM...
Yeah... no. This is false, there's not even code for detecting AutoRCM (let alone brick your device) in 8.0.0.
However, if you try to install developer firmware on a retail unit... that's a different story because 7.0.0 has introduced some changes to how environments (retail vs. dev) are detected and handled.
However, if you try to install developer firmware on a retail unit... that's a different story because 7.0.0 has introduced some changes to how environments (retail vs. dev) are detected and handled.
Similar threads
-
Maximumbeans
-
HoTuan
-
K3Nv2
-
DinohScene
That cat suit twink
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Maximumbeans:
@HoTuan You'll need one that hasn't had its stock firmware updated in quite some time, for starters
@
Maximumbeans:
@HoTuan You'll need one that hasn't had its stock firmware updated in quite some time, for starters