Okay, i have disabled with Hekate.
Now if i power on with jig in and vol +, power buttons and injecting with Tegra RCM GUI, just black screen, but Tegra RCM GUI says payload successfully injected.
reboot pc, sounds like rcmgui bugged
Okay, i have disabled with Hekate.
Now if i power on with jig in and vol +, power buttons and injecting with Tegra RCM GUI, just black screen, but Tegra RCM GUI says payload successfully injected.
reboot pc, sounds like rcmgui bugged
Yes, you can use it to downgrade to any firmware. However when downgrading across major firmwares, you may need to perform a system initialization. 7.0.1 to 6.2 may or may not require one but I believe most people haven't required one.Can i use this to downgrade from 7.0.1 to 6.2 on atmosphere 0.8.4?
7.X is a tad bit unstable with certain homebrew applications such as Goldleaf or Tinfoil by Adubbz.why are people downgrading from 7.x firmwares?
Trying to upgrade to 6.2 again but switch refuses to boot after upgrading to 6.2
Flashed the exfat update upon upgrading. Coming from 5.1 going to 6.2: chose not to initialize. = Reinx and ofw will not boot after restarting switch once upgrade was done.
Restore NAND, 5.1 booting and working again.
Copy over fresh 6.2 firmware files from *cough*. Upgrade, choose exfat, and this time initialize. =Reinx and OFW will not boot. (hang on nintendo switch logo)
Format SD card, try fat32 nothing will boot
Restore NAND 5.1 booting and working again. This time I get atmosphere to work on 5.1 too.
Upgrade to 6.2 again and choose exfat update, no initialize. =Atmosphere will not boot.
Format SDcard (exfat) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Format SDcard (fat32) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Enter maintenance mode, initialize console.
Boot into atmosphere, get the logo, no nintendo logo black screen and top left corner charging icon, then all black.
Boot into atmosphere, get the nintendo logo, then black screen and no switch logo. Stuck
Boot Reinx 2.0, splash screen, black screen
Format SDcard (exfat) clean install reinx, boot, black screen after reinx boot logo.
Restoring my 5.1 nand now, anyone got tips on how the hell to get to 6.2?
I tried again this time initializing. Same thing. Going to try 7.0.1 tomorrow after I restore back to 5.1 tonight
I recently update from 4.0 to 6.2 with auto rcm via hekate. So once it’s been updated, is it still necessary to keep auto rcm on at all times in order to prevent burning the fuse?
- Q: I thought updating the firmware burned fuses, why would I use this instead of the official way of upgrading my Switch firmware (via cartridge or online, if I want the latest version)
- A: Because fuses are burned on first normal boot, not during the install. By default, ChoiDujourNX will enable AutoRCM on any flashed firmware image, meaning that the normal nintendo bootloader will never get the chance to burn the fuses. And therefore, you can downgrade any time you want back to the firmware you started from. You can also arbitrarily downgrade to whatever firmware you want, as long as you are not using the nintendo bootloader to launch it (which will burn fuses if not enough fuses are burned, and panic if too many fuses are burned, check the table here http://switchbrew.org/index.php?title=Fuses#Anti-downgrade).
So could I theoretically downgrade back to the original 4.0 fireware and then take off auto rcm and not worry about the Nintendo boot loader not burning fuses? Or would I have to use system initialize and reformat the microsd in order to avoid detection?I recently update from 4.0 to 6.2 with auto rcm via hekate, once it’s been updated, is it still necessary to keep auto rcm on at all times in order to prevent burning the fuse?
Well you can disable AutoRCM when you return back to your original firmware. But the system initialize isn't for avoiding detection because it is a well-known fact that system initializations don't prevent bans. The purpose of initializing your system is to allow downgrading across major firmware versions such as ones that differ in expected fuse counts. Some people are able to downgrade without doing it while others aren't and I haven't seen any official documentation explaining the requirements.So could I theoretically downgrade back to the original 4.0 fireware and then take off auto rcm and not worry about the Nintendo boot loader not burning fuses? Or would I have to use system initialize and reformat the microsd in order to avoid detection?
I also just don’t want the switch to accidentally somehow boot normally without auto rcm and have the fuses messed with. Not that it’s likely to happen
Awesome, appreciate the help cheers!Well you can disable AutoRCM when you return back to your original firmware. But the system initialize isn't for avoiding detection because it is a well-known fact that system initializations don't prevent bans. The purpose of initializing your system is to allow downgrading across major firmware versions such as ones that differ in expected fuse counts. Some people are able to downgrade without doing it while others aren't and I haven't seen any official documentation explaining the requirements.
Fuses are also only burnt when you boot normally such as without AutoRCM while running a firmware higher than your fuse count. As long as you keep track of your current firmware, AutoRCM status, and number of fuses currently burnt, you will be fine.