Do you have AutoRCM active? If so, you should probably disable it. Also, AFAIK, if you are in regular sysMMC, restarting to reboot_payload won't work, you have to be in CFW sysMMC.
Hacking 11.0.1 firmware and still no SXOS update
- Thread starter Aglae Pheryl
- Start date
- Views 205,144
- Replies 446
- Likes 2
- Status
Do you have AutoRCM active? If so, you should probably disable it. Also, AFAIK, if you are in regular sysMMC, restarting to reboot_payload won't work, you have to be in CFW sysMMC.
https://cdn.discordapp.com/attachments/816607839082643479/817391167242895380/image0.png
If you ever have any ODM6 fuses burnt, you effectively have all 32 ODM7 fuses burnt
How? Is there a way to switch between them without running emuland but also have 11.0.1 & 11.0.0? I think the answer is no, you must have emuland setup to run 2 different versions of the OS?
My main question is how can I run SXOS & Atmosphere switch between without reboot and have 11.0.0 and 11.0.1? That is either impossible or possible only with emuland and I believe hekate
Last edited by 00diabolic,
Hekate is your best option among restarting the switch under emunand/sysnand cfw to switch payloads. Honestly tho anyone thinking about online privileges should have an emunand setup. Your playing with Ban fire hacking on sysnand. I kinda dont understand the question b/c both sxos and atmosphere/hekate can reboot the switch back into their respective payload screen to let you choose a different payload or nand.
Sorry, im such a noob I probably did not explain it right.
1. OK first do I need emuland to have 2 different versions of the OS? say I want to keep using SXOS on 11.0.0, atmo on 11.0.1? Please confirm that is true or false. or if there is another way to run SXOS & atmo side by side on 11.0.1?
2. Once I have emuland I can go online as long as I have no piracy stuff and sysnand has to be updated I'm assuming via online which means fuses need to be burned? Never been online or even on wifi with my switch so just curious. I've been updating with choi and never burned fuses, so it seems online i would need to.
3. So hiktate is only needed if I want to change the RCM menu from SXOS to Hikate and then you can boot SXOS, or Atmo or whatever is on sysland or emuland?
If all the above is correct what your saying is atmo, SXOS and hikate can jump between any of the others weather they are on sysland or emuland without reboot?
ok I think that is clearer i hope.
Last edited by 00diabolic,
Why should I disable autorcm?
Btw so you confirm too the reboot doesn't work from sysnand so that's already a point for SX, I've never seen this mentioned anywhere but it's a cool feature to have, much faster for people that play both online and offline.
@00diabolic
1. No you cannot run atmo/sxos at the same time on both nands if thats what you mean.
It is highly recommended that you have emunand to keep your sysnand clean for online play
So if you want to switch payloads to whatever nand your using you still need to use either hekate or sxos's payload screen to choose.
2. Yes once you have emunand you can do all of the dirty piracy/cheat stuff on it while playing legit on sysnand with no piracy and online play.
3. No hekate menu is basically the same as sxos menu screen they are payloads themselves that let you choose other payloads such as atmosphere primary fusee.
4. No you still need to reboot whether you have emunand or sysnand cfw to choose another payload. I think the confusion is that no one has told you that both sxos and atmosphere are cfw payloads.
1. No you cannot run atmo/sxos at the same time on both nands if thats what you mean.
It is highly recommended that you have emunand to keep your sysnand clean for online play
So if you want to switch payloads to whatever nand your using you still need to use either hekate or sxos's payload screen to choose.
2. Yes once you have emunand you can do all of the dirty piracy/cheat stuff on it while playing legit on sysnand with no piracy and online play.
3. No hekate menu is basically the same as sxos menu screen they are payloads themselves that let you choose other payloads such as atmosphere primary fusee.
4. No you still need to reboot whether you have emunand or sysnand cfw to choose another payload. I think the confusion is that no one has told you that both sxos and atmosphere are cfw payloads.
Last edited by MasterJ360,
Due to your issue reboot payload supposedly not working. Also, seeing that you are using CFW with sysMMC, there really isn't any point in using AutoRCM, which is meant to remind you not to use CFW with sysMMC.
If you use SX with sysMMC, you are already using CFW with sysMMC. You can do the same with Atmosphere. I was saying that if you load sysMMC without CFW, you can't use the reboot to payload feature.
Last edited by Mrperson0,
1. So that is the RCM screen right (boot holding vol up) basicly can only switch between atmosphere and sxos via RCM either SXOS or Hekata menu?
1.1. So there is no way from within CFW that I can then boot over to sysnand or vice versa to emuland without reboot/RCM menu?
2. My current setup is only sysnand, so if I want to move all my stuff over to emunand, is it as simple as removing saves, homebrew apps, and any installed NSP apps? Or do I need to go back to before I updated with choi? like burn fuses etc. seems to be overkill.
The rest makes sense.. THANKS
Last edited by 00diabolic,
What you want is what you can do. If you've correctly replaced the reboot payload on the atmosphere folder, your Switch will reboot to Hekate when you select reboot. This works regardless of whether you're using a sysMMC or an emuMMC. This is what I do, and I only use a sysMMC.
Last edited by Lacius,
1. Yes its the RCM menu screen
1.1 No the only way to boot into sysnand within cfw is by restarting the switch using "reboot to payload" which should already be configured with hekate files - sxos just simply restart the switch and let it boot into the RCM menu screen to choose a nand or payload.
2. Setting up emunand will require the SD card to be formatted during the process so you need to backup everything thats important on your SD card first. But the process making emunand is it will be an exact clone of the sysnand with all the save/dlc/updates/games you have on it. The emunand will be stored on your sd card and will have the option to choose between both nands on hekate or sxos
Last edited by MasterJ360,
There's a lot to unpack here. You only need an emuMMC if you want to go online for legitimately online play with a clean sysMMC, or you have an ipatched unit stuck on 4.1.0 on its sysMMC. There's no need to use an emuMMC if you aren't using online play and your Switch isn't ipatched.
Your clean sysMMC (or your clean emuMMC you're using for online play if your sysMMC is trapped on 4.1.0 because it is ipatched) must be on the latest system version to play online.
--------------------- MERGED ---------------------------
We know for a fact that newer games will require newer system versions. If SX OS isn't updated, which appears likely at this point, then newer games will eventually be unable to be playing on SX OS. That's a fact due to how software development kits work, and there's nothing that can be done about it.
Ok awesome, so the only question left is related to sysnand clean up, if I simply remove all save files, and homebrew apps is that enough to have a "clean sysnand"? Or is it more involved IE need to reflash updates due to unknown items that could remain and could trigger a ban? its mentioned here: https://www.codedonut.com/switch-ha...endo-switch-play-games-online-without-banned/
In the guide above he says you need to go back to your original shipped OS and start the update process from there to ensure you have a clean system, again seems like overkill but perhaps there is something to that, it would mean burning fuses cuz you could not use choi to do it cuz nintendo keeps track of where you got your updates.
I've always been curious about online, and my nephews have also. I keep telling them its to risky.
Last edited by 00diabolic,
You absolutely do not know that there will be no update. Stop lying. You may be right you may be wrong but it doesn't matter. SX OS is useful and will remain that way. Advising people to ditch in the first place is myopic. Set up atmosphere if you want. Leave SX alone so you can keep using your USB. And go away troll. You are top-tier worst troll out there. Go away. I never said that higher firmwares wouldn't be necessary by the way. More bullshit
Last edited by mikefor20,
I'm using autorcm because I don't want to use the jig. Btw I think I get it now, so to have that feature I should use the CFW - sysMMC option. I'm using the stock sysnand to play online to be as safe as possible.
Actually I have completely removed cfw sysnand reboot from the ini file, didn't sound safe at all to use a cfw on sysnand.
Don't want to risk it I'll continue as it is I think.
You cannot clean one but you can restore one. If you had the foresight to back it up.
SO if i go back to my shipped nintendo OS and then use choi to update from that point, is that clean or does choi mess it up? Ive got my original untouched OS, and could restore back to that and update from there but i hate to burn fuses just to play online, but perhaps thats the price.
Truth be told you don't have to burn fuses. Restore your old backup with zero hacks. 100% clean. You can make an EmuNAND out of it even if you wanted to. Thats what i do. You can go online using atmosphere with a clean emunand or system nand. No patches. No hack save games. No piracy of any kind. That's what I do. I have my fuses at 4.1 as well as my system nand. I use fake news to boot into hekate or argon nx and choose between my clean nand and Dirty nand
To be clear i keep my SysNAND at 4.1. Then i made an EmuNAND from it. Boot the Clean EmuNAND with atmosphere and went online and updated the EmuNAND using Nintendo servers. Only do legit stuff with it. No PATCHES. Then i use another EmuNAND for all the fuckery. There's several ways to have multiple EmuNAND. Just use separate SD cards to be safest. There are people who have no SysNAND at all doing this or have linux installed to SysNAND for a long time doing this. Using EmuNAND only for online.
After everything was said and done i installed fake news to my 4.1 SysNAND . I used that to boot for a while no jig. Then I just decided to activate Auto RCM. That's how it sits now. I have a dragon injector anyway LOL
So far so good. Over a year now no ban.
In fact if you go on the reswitched discord SiresM has a post talking about how running atmosphere itself will not get you banned nor will an emulated nand. Just piracy and messing with saved games and things like that. So don't do that shit and don't put any patches and you're good to go as long as your nand backup is in fact clean
I would also like to point out that although what I said is currently accurate Nintendo can change the game anytime they want with a future update. You never know.
To be clear i keep my SysNAND at 4.1. Then i made an EmuNAND from it. Boot the Clean EmuNAND with atmosphere and went online and updated the EmuNAND using Nintendo servers. Only do legit stuff with it. No PATCHES. Then i use another EmuNAND for all the fuckery. There's several ways to have multiple EmuNAND. Just use separate SD cards to be safest. There are people who have no SysNAND at all doing this or have linux installed to SysNAND for a long time doing this. Using EmuNAND only for online.
After everything was said and done i installed fake news to my 4.1 SysNAND . I used that to boot for a while no jig. Then I just decided to activate Auto RCM. That's how it sits now. I have a dragon injector anyway LOL
So far so good. Over a year now no ban.
In fact if you go on the reswitched discord SiresM has a post talking about how running atmosphere itself will not get you banned nor will an emulated nand. Just piracy and messing with saved games and things like that. So don't do that shit and don't put any patches and you're good to go as long as your nand backup is in fact clean
I would also like to point out that although what I said is currently accurate Nintendo can change the game anytime they want with a future update. You never know.
Last edited by mikefor20,
That makes sense. FWIW, I did a quick test with AutoRCM enabled, and reboot_payload still works.
Exactly. Using stock sysMMC is not the same as SX sysMMC or Atmosphere sysMMC, which is why you weren't able to use the reboot_payload feature.
- Status
Similar threads
-
Xdqwerty
what are you looking at?
-
-
-
-
@
SylverReZ:
@Psionic Roshambo, The Doom NES cartridges, a few batches were made. One was given to AVGN as seen in his Doom video.+1 -
-
@
Sicklyboy:
I finally modeled and 3d printed the new HDD cages I need in order to build my 2nd NAS. Original ones don't fit the mounting holes on the hdds I'm using. Been sitting on this project for over 2 years smfh -
-
@
Sicklyboy:
I'm finally gonna get this NAS racked and powered on tonight, install truenas core, and burn the disks in with badblocks
-
@
Sicklyboy:
Also another 70TB going in the front mount drive bays of this server. 182tb raw, going to probably use a zfs RAID-Z3 for 3 parity disks, so 140TB usable
-
@
Sicklyboy:
I could claw back 14tb by only doing 2 parity disks but I feel like with 13 disks in the RAID I'd be kind of pushing my luck on rebuild time if I encounter a disk failure
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
