Hacking Is AutoRCM still useful?

  • Thread starter Thread starter tayshun12
  • Start date Start date
  • Views Views 24,677
  • Replies Replies 74

Are you still using autoRCM?

  • Yes!

    Votes: 85 81.7%
  • No!

    Votes: 19 18.3%

  • Total voters
    104

tayshun12

Well-Known Member
Newcomer
Joined
Jul 16, 2011
Messages
66
Reaction score
15
Trophies
0
XP
342
Country
United States
Hey all,

I was wondering if autoRCM is still useful now a days? I have my 4.2 backup but I don’t think I’ll ever downgrade. I don’t think I’m online banned but I’ve never gone online (apart from home brew with incognito) and do not plan on ever going online with this switch. I know the purpose of AutoRCM is the ability to downgrade. I’m currently on SW 10. I just don’t like the fact that if I fully shut down my switch and someone else tries to turn it on I would never know until it was too late.

so I guess my question is:
Is AutoRCM still important and are many of you still using it?

thanks!
T
 
From my point of view AutoRCM only useful if you have trinket m0 installed. In other cases it often causes deep battery drain when console goes to RCM and waits for payload until it dies.
 
  • Like
Reactions: de9ed
From my point of view AutoRCM only useful if you have trinket m0 installed. In other cases it often causes deep battery drain when console goes to RCM and waits for payload until it dies.

well yaa when the console is On it tends to drain the battery but i have 4 AutoRCM enabled units here i use only one and when they are off usually you see the same discharge few % for several months less if theres no joycons attached
so if you leave your Switch in RCM mode with AutoRCM enabled or not it will drain the battery cause the console is ON
plus you can completely Turn OFF the console from CFW and Hekate while AutoRCM is on for a Very Very Long time now
 
Autorcm is dead useful. Imo, the battery drain arguement is incredibly pointless, because you dont leave your switch in rcm mode.
You either power it off completely, or leave sleep mode, like 95% of the people that own a switch.
If you don’t want to constantly remove your right joycon & require a jig to enter rcm, then yes its useful.
 
Doesnt AutoRCM prevent the device from completely turning off? From what I remember (and this is from a long time ago), every time you'd try to turn the Switch off, it would automatically reboot and return to a black screen which might look like its off, but is actually on and waiting for a payload.
 
Doesnt AutoRCM prevent the device from completely turning off? From what I remember (and this is from a long time ago), every time you'd try to turn the Switch off, it would automatically reboot and return to a black screen which might look like its off, but is actually on and waiting for a payload.

Yeah they fixed that a long time ago
 
  • Like
Reactions: BigOnYa
I don’t see a reason not to use it since my hacked switch never goes into OFW, so I don’t need to mess around getting it into RCM mode.

It also means that my fuse count should stay low, as unlikely as it may be we’ll see a dongle/trinketless CFW.
 
I don’t see a reason not to use it since my hacked switch never goes into OFW, so I don’t need to mess around getting it into RCM mode.

It also means that my fuse count should stay low, as unlikely as it may be we’ll see a dongle/trinketless CFW.

You can easily boot stock from hekate, OFW with SXOS & genuine firmware with SXOS. None cause problems.
Dongleless cfw wont make a difference if you only use cfw. You can always reboot to payload unless your using official firmware, and their is never going to be a coldboot method that lets you switch from official firmware to CFW without getting banned.
Its pretty much a trinket for that, or youre basically wasting your time and hopes for something that will not happen. Even with a trinket you need to go from the payload to swap between cfw/ofw.
 
Last edited by Basketto,
You can easily boot stock from hekate, OFW with SXOS & genuine firmware with SXOS. None cause problems.
Dongleless cfw wont make a difference if you only use cfw. You can always reboot to payload unless your using official firmware, and their is never going to be a coldboot method that lets you switch from official firmware to CFW without getting banned.
Its pretty much a trinket for that, or youre basically wasting your time and hopes for something that will not happen. Even with a trinket you need to go from the payload to swap between cfw/ofw.

As I said, the Switch never uses OFW. I have a second 'stock' Switch for OFW.
 
I haven't had to use my jig/ injector for months, even on crashes, I have hekate.bin setup as reboot_payload so no pushing payload anymore either, so yes it is awesome.
As for me, I like to keep reboot_payload to Atmo (when It crashes), and prefer to use FastCwf switch overlay to push any payload I need from Atmo or Sxos (currently Atmo, Sxos, Hekate, Lockpick).
You can push as many payloads you want/need, and also organise them in folders.

I very barely power off my switch, only when not using it over few weeks. So AutoRcm is really convenient for me.
 
Last edited by Maupiti,
As I said, the Switch never uses OFW. I have a second 'stock' Switch for OFW.

Fair enough . Considering emunand exists though, for me personally it would be a massive waste of $$. Carting two switches everywheres cuts portability in half aswell.
Incognito/emunand has basically been ban proof from day 1 of their existance. If that 0.0001% chance of a ban does happen i suppose I could always get another then.
I like being able to boot stock from autorcm.
 
  • Like
Reactions: Maupiti
Fair enough . Considering emunand exists though, for me personally it would be a massive waste of $$. Carting two switches everywheres cuts portability in half aswell.
Incognito/emunand has basically been ban proof from day 1 of their existance. If that 0.0001% chance of a ban does happen i suppose I could always get another then.
I like being able to boot stock from autorcm.
Concerning the “debate “ of AutoRCM, it’s a temporary state of the switch, when a CFW or OFW is launched, the battery drain is the same. The only issue, is effectively if the shutdown was not done properly. I do prefer to just plug my dongle after powering off, and not to have to do the “trick” jig.,Even if I have a very reliable jig (RCM-one dongle, 6 entries, as for me the best dongle on the market, never failed over 2 years since I use it). I, personally hate to open a device to put a chip on it, unless there’s no other choice. “Software “ hack is so much “elegant “.
The only downside, is that it can be effectively patched, on firmwares updates, when, chips, are harder to be blocked.
 
Last edited by Maupiti,
I installed AutoRCM when it first became available, and I've never looked back. It's primarily a convenient way to enter RCM, but it also keeps my fuse count at 3.

The first thing (after backups) I do whenever I'm messing with anyone's Switch is install AutoRCM. It's only later that I explain the pros and cons and give the option of disabling it.
 
Last edited by Lacius,
I installed AutoRCM when it first became available, and I've never looked back. It's primary a convenient way to enter RCM, but it also keeps my fuse count at 3.

The first thing (after backups) I do whenever I'm messing with anyone's Switch is install AutoRCM. It's only later that I explain the pros and cons and give the option of disabling it.
Same for me ;)

And, I would add, that when an Emunand option is available, it’s a lot better than messing with the sysnand. BUT, it’s only my “point a view “.
 
Fair enough . Considering emunand exists though, for me personally it would be a massive waste of $$. Carting two switches everywheres cuts portability in half aswell.
Incognito/emunand has basically been ban proof from day 1 of their existance. If that 0.0001% chance of a ban does happen i suppose I could always get another then.
I like being able to boot stock from autorcm.

I think this was before emunand and even then it didn't work out that much considering that I also wanted the second dock, joycons, etc.
 
I use a modded right-joycon so I never bothered with autoRCM. Even if I fail to trigger RCM when I coldstart the Switch (it can happen sometimes), the fuses are safe since I use an emuNAND. I just turn off the console and retry.
 

Site & Scene News

Popular threads in this forum