You can disable AutoRCM by entering the same menu above and selecting ‘Disable AutoRCM’.įrom now on, to boot into stock firmware, select ‘Launch > Stock’ in Hekate. Select ‘Tools > Archive Bit - AutoRCM > Enable AutoRCM’ Push the Hekate payload to your Switch while holding Vol- to skip autoboot and enter the menu This might sound scary but is not actually dangerous, and can be undone at any time.īy doing this, you will need to use a payload sender to boot your Switch after every restart/shutdown. Essentially, you are purposefully bricking your Switch in a controlled matter that forces it to launch into recovery. Failure to heed this warning will result in a bricked Switch.ĪutoRCM is an optional software method of forcing your Switch to go into RCM on every launch, without the need of a jig or hardmod. For instance, to use a different version of the SLF4J library and the Spring Data release train, you could add the following. To achieve the same result, you need to add entries in the dependencyManagement section of your project before the spring-boot-dependencies entry. I restored computer to original factory settings (to rule out possible causes) 2. The preceding sample setup does not let you override individual dependencies by using properties, as explained above. I'm having trouble with my very new computer (Lenovo Y480 with Windows 7 Home Premium 64 bit), which I've narrowed down to the following sequence: 1. If you cannot run payloads from RCM with fusee-gelee, DO NOT ENABLE AUTORCM. 'System Configuration Cannot Save The Original Boot Configuration For Later Restoration' Nov 15, 2012. Enabling AutoRCM on an IPATCHED Switch will literally BRICK your Switch. This section is only intended to be used on consoles with a vulnerable RCM. Use Original Boot Configuration Sets the computer to process the original boot configuration on startup instead of one youve created by modifying the boot. WARNING Never enable AutoRCM on an IPATCHED Switch

Use original boot configuration