Hacking Firmware 8.0.1 is out

  • Thread starter Thread starter SomeGamer
  • Start date Start date
  • Views Views 32,185
  • Replies Replies 65
  • Likes Likes 1
Hi, I have a Nintendo Switch on 7.0.1 with autorcm and with 2 fuses burned, today I downloaded the 8.0.1 update with 213 files, but a friend told me that I can update my Switch without using ChoiDuJourNX and without burning fuses, is that true? (I use Atmosphere in Kosmos and normally I'm in stock firmware, I only use CFW to make a backup of my saves with Checkpoint).
Thanks in advance.
Atmosphere should preserve autorcm after doing a system update (which prevents fuse burning as well). It worked fine when I updated from 6.2.0 ---> 7.0.1, 7.0.1 ---> 8.0.0, and 8.0.0 ---> 8.0.1

edit: you must be in CFW when you do the system update for it to preserve autorcm
 
Last edited by ZachyCatGames,
Atmosphere should preserve autorcm after doing a system update (which prevents fuse burning as well). It worked fine when I updated from 6.2.0 ---> 7.0.1, 7.0.1 ---> 8.0.0, and 8.0.0 ---> 8.0.1

edit: you must be in CFW when you do the system update for it to preserve autorcm
so I'm on 6.0.0 with Atmosphere and autorcm do i just update in system settings
 
how do you get access to reswitched discord?
i sent my username and number on that channel but the bot just keeps saying something is missing
 
SysNAND can be on whatever firmware you want but EmuNAND cannot be updated to 8.X since SX OS does not support that firmware yet. Also AutoRCM was never broken. If your SysNAND firmware exceeds what SX OS supports, you will not be able to boot into SysNAND because the "OFW" option is not really OFW. Its just a way of turning the console on without any patches or homebrew but prevents fuses from being burnt.
Just updated the sysnand to 8.1 and the autorcm is indeed broken as I was saying. Now sysnand will give blackscreen. Fortunately emunand is still booting fine with autorcm so I can use it for that.
Please guys stop giving advice if you're not very sure about what you're saying.
Hope we don't have to wait months again for the new SX update.
 
so I'm on 6.0.0 with Atmosphere and autorcm do i just update in system settings
yea, that should work fine

You could or use hombrew to update and not burn fuses.
updating through system settings also won’t burn fuses if you have autoRCM and are using atmosphere when doing the update :P
 
Last edited by ZachyCatGames,
  • Like
Reactions: Deleted User
The one that was on xbins was missing exfat files. If you choose regular fat32 it's 209/209 but with exfat it is 209/211 which throws the error. But haven't found anywhere else that has it yet.

Edit: Yeah xbins didn't have all the files, found the right one, with 213.

Sorry about that guys, didn't realize it was missing exfat! It has been updated to the full version.

Thanks!
 
Just updated the sysnand to 8.1 and the autorcm is indeed broken as I was saying. Now sysnand will give blackscreen. Fortunately emunand is still booting fine with autorcm so I can use it for that.
Please guys stop giving advice if you're not very sure about what you're saying.
Hope we don't have to wait months again for the new SX update.
I have AutoRCM on firmware 8.0 and I can boot the console into Stock and CFW. Its not AutoRCM that is broken, its your CFW.
 
Updated Switch to 8.0.1 through the prompt as I read it was safe and now I get a black screen after booting to the Nintendo logo. Also, it seems harder to get into RCM. When I do, I get the Sept logo, then the Atmosphere logo and after the Nintendo logo, it shuts off. What's going on here.
 
Last edited by skydancer93,

Site & Scene News

Popular threads in this forum