My son's Switch is a Mariko w/ Sysnand 11.0.0 and the latest Atmosphere + SXOS work fine. The only limitations for Mariko switches are you can never update your sysnand beyond 11.0.1 and you can't use any of the dual boot setups that use the RCM payloads. Updating Atmosphere's emuMMC to the latest firmware version also works just fine.
- Status
My son's Switch is a Mariko w/ Sysnand 11.0.0 and the latest Atmosphere + SXOS work fine. The only limitations for Mariko switches are you can never update your sysnand beyond 11.0.1 and you can't use any of the dual boot setups that use the RCM payloads. Updating Atmosphere's emuMMC to the latest firmware version also works just fine.
Haven't looked over whatever has been discussed but if that's some sort of guide please make sure to mention whether or not if it's for Mariko or Erista switches. What works for Erista does not necessarily work with Mariko switches especially RCM payloads.
Did you already updated your Mariko AMS Emunand to latest FW? Then is SXOS still run on emunand/sysnand afterwards?
I had Mariko FW 11.0.0 sysnand previously, and used to play AMS & SXOS on SYSNAND by swapping SD Card. Then I tried dual boot tutor from someone, with option AMS on SYSNAND & leave SXOS on Emunand. It works but with manual replace boot.dat, doesn't work with sxos boot.dat then payload->hekate->launch-> sysnand nor emunand (to open AMS). IT WORKS ONLY IF YOU REPLACE BOOT.DAT WITH AMS BOOT.DAT (only 10 kb size instead).
Then I tried to update my sysnand AMS to FW 13.0.0 by using Daybreak, wonder if I can have Bluetooth audio function and XCI benefit on the otherside. The result, only AMS running on both sysnand & Emunand. SXOS leave blank screen after use its boot.dat, I haven't tweaked with hekate.ini (will let you know I want to and I had done). Maybe somebody can try this too and find the solution for having those goddamn feature (Bluetooth & XCI, even you're not caveman you definitely want it)
@raging_chaos Please let me know if you updated the AMS emunand to FW 13.0.0 with your AMS sysnand leave at FW 11.0.0.
This is the snapshoot of my research.
This is the snapshoot of my research.
Attachments
AMS does not have a 10kb boot.dat , that is SX's boot.dat from SX Gear. You need SX Gear's boot.dat to boot Hekate/Atmosphere. You need SX Core's boot.dat to boot into SX Core's OS. You cannot setup dual boot on Mariko systems at all with just one boot.dat and chain loading through Hekate. Every post you see where it's working is because it is an original RCM Erista v1 Switch. Mariko cannot load RCM payloads, you will never be able to dual boot the way you have been reading. Manual swap of the boot.dat file is the only way unless you write homebrew application to swap the dat and shutdown the system.
As for your second question FW 13.0.0 is working just fine on the Mariko Switch with SX Core and I can still manually boot into SX or Atmos.
I did downgrade firmware on SYSNAND from 13.0.0 to 11.0.0 but SXOS still couldn't run, both on sys nor emu.
Tried Stardust and hekate.ini still shows blank screen. But AMS run smoothly with notice on boot the device took longer (about 1 minute) to show first boot logo (blue led light blips until switched to green). I think it's time to forget SXOS on this device forever.
Tried Stardust and hekate.ini still shows blank screen. But AMS run smoothly with notice on boot the device took longer (about 1 minute) to show first boot logo (blue led light blips until switched to green). I think it's time to forget SXOS on this device forever.
There are custom boot.dat files. One that boots atmo. Supposed to work on mariko too..
You can keep sxos for just usb loading even on mariko....you can have seperate emunands. Seperate cards or 2 on the same card.
Last edited by mikefor20,
If you're referring to the ones that require modification with python scripts and cracks SX's license, those do not work with SX Core/Lite chips.
If you're referring to the 12kb boot.dat that loads whatever payload is defined in boot.ini, that is from SX Gear.
Only Erista (including patched Erista w/ SX Core) can chainload the 28kb SXOS.bin file through Hekate in true dual boot fashion. Mariko cannot since the bin is meant for RCM injection.
Mariko can directly boot to Hekate with the 12kb boot.dat file, but you cannot then chainload into SXOS because that is an RCM payload and Mariko cannot inject RCM payloads. Hekate also cannot chainload the boot.dat that is used for SX Core. The only option for Mariko users are to manually swap the boot.dat file with homebrew and restarting the console or manually launching the Hekate payload through SX Core's payload option.
If there is some magic boot.dat that launches into Hekate and allows for true dual boot setups on Mariko + SX Chip the way RCM Erista then I'd like a link to it. As is only my Erista Switch can dual boot, the Mariko I mess with cannot and requires manual swapping of the boot.dat.
Posting that cheeky link in a reply isn't helpful, however here is a link to a thread that says the exact same thing I'm saying. Warmboot methods of dualbooting do not work on Mariko. A custom boot.dat doesn't do anything differently than the one from SX Gear other than having a payload injected into it vs booting one that's defined in boot.ini. A custom boot.dat also doesn't change the fact an SX Core Mariko can't reboot to payload nor inject one to dualboot into SXOS from Hekate. The only way to boot SXOS on an SX Core Mariko is to use the boot.dat meant for SX Core. No python script I've seen anywhere can modify the boot.dat used on SX Core (unless something has changed in the last few months), those all modify the boot.dat used by SX Gear and can only be used to boot into Hekate/Atmosphere on Mariko.
I have the original v1 unpatched RCM Injectable Erista, a chipped SX Core patched Erista, and an SX Core chipped Mariko, I pretty sure I know what I'm talking about here where as you only have an Erista. Out of the three the only one that can't chainload SXOS through Hekate is the Mariko because it cannot inject RCM payloads. If you have information to a project that does chainload into SX Core's boot.dat through Hekate and works specifically on SX Core Mariko for others to use then please post it, beyond that I'm not going to waste any time researching something I've already found a solution to using self written homebrew.
By the way all you are doing is trolling and your posts will just end up being deleted. It's clear you have no experience with Mariko and it's limitations when it comes to RCM payloads and reboot to payload injections. Writing a limited guide (with text that is obnoxiously large) that only works for Erista does not equate to knowing what you are doing with Mariko.
To clarify no one is asking how to boot into Hekate nor how to setup dual hidden nands in this thread. The last question was how to boot into SX on Mariko after setting up Atmos and from within Hekate's boot menu (which you cannot do on Mariko).
I have the original v1 unpatched RCM Injectable Erista, a chipped SX Core patched Erista, and an SX Core chipped Mariko, I pretty sure I know what I'm talking about here where as you only have an Erista. Out of the three the only one that can't chainload SXOS through Hekate is the Mariko because it cannot inject RCM payloads. If you have information to a project that does chainload into SX Core's boot.dat through Hekate and works specifically on SX Core Mariko for others to use then please post it, beyond that I'm not going to waste any time researching something I've already found a solution to using self written homebrew.
By the way all you are doing is trolling and your posts will just end up being deleted. It's clear you have no experience with Mariko and it's limitations when it comes to RCM payloads and reboot to payload injections. Writing a limited guide (with text that is obnoxiously large) that only works for Erista does not equate to knowing what you are doing with Mariko.
To clarify no one is asking how to boot into Hekate nor how to setup dual hidden nands in this thread. The last question was how to boot into SX on Mariko after setting up Atmos and from within Hekate's boot menu (which you cannot do on Mariko).
Last edited by raging_chaos,
Whatever partition of the sd you want to use as a "dual boot" leave on sd. Move files to a temp direcrory and remove leftover partitions. Sx to boot hekate. Use backup tools and click sd raw emummc at bottom, back up all the raw gpp ad boot0 and boot1 from original emunand then restore them to that extra partion . Then recreate prexisting partitions using emummc create in perhaps another or Linux our Android wheratever sx. Good luck!
I would like to achieve the same setup with my Mariko, 11.0 Emunand SX OS; 13.2 Atmosphere emuMMC(newly created not migrated) ; 11.0 Clean Sysnand. Right now I already have those set up, but I am changing the boot.dat to switch between the 2 Emunands so would really like to know how you are able to chainload to boot to AMS emuMMC with a SX OS boot.dat.
I have followed your steps up to the Launching to AMS CFW-EmuMMC but it gave this error
Pkg1 decryption failed!
BEK is missing!
Failed to launch HOS!
then I proceeded to tools>dump package1/2, got similar error
Found pkg1(xxxxxxxxxxxxxxxxx)
Pkg1 decryption failed!
is BEK missing?
so I'm stuck here but noticed there is this hekate_keys.ini thing that I can attempt.
[Prod]
mariko_bek =
mariko_kek =
package2_key_0a =
master_key_0a =
I understand I need my keys so I have dumped my keys and checked my prod.key. I could find the values for package2_key_0a and master_key_0a but not mariko_bek and mariko_kek. Are there other values in the prod.key that I can use for the bek and kek?
Would really appreciate the help. Thanks in advance.
ArgonNX has a mariko mod. Or use tesla with fastcfwswitch. I don't have a mariko to test but they say it's working.
File-based emunand are known to corrupt. Use partition based instead. I wrote a tutorial to make dual partition based emunand. It's in the tutorial section
I have looked into it but unfortunately after spending quite some time, it didn't work for me though I might be doing something wrong on my end. I might be giving another go in the future.
I tried your guide but it did not work either and most likely only works with Erista units.
This seems to be the logical explanation as to why quite handful of guides floating around do not work with Mariko. @raging_chaos reached out to me and kindly shared his self written homebrew app. Upon testing, setup was very easy, almost idiot-proof even. I must say it works exactly how I want it to without any issues whatsoever.
Until another and better solution comes out (if ever), this for me is the best and the only working temporary solution for Mariko users currently looking to switch between SX OS emunand and Atmosphere emuMMC with very minimal hassle. This homebrew app will also save you the wear & tear impact on the card reader and the microsd itself resulting from frequent ejecting and inserting of your microsd. If you are interested, please reach out to @raging_chaos via PM, I am sure he will be more than happy to help.
Looks like the thread has reached a happy conclusion, users who have a similar issue know who to reach out to. Time to lock it up, before we have more arguments over what works and what doesn’t. If @raging_chaos wouod like to share his app (which apparently can be very helpful!), I encourage a public release in a separate thread (if you’re comfortable with sharing it with the community). 
- Status
Similar threads
-
-
-
-
-
-
-
-
@
BakerMan:
@SylverReZ I didn't say I watched either, did I?
I didn't actively watch them, rather, I had the misfortune of witnessing that shit -
-
tempBOT:
LeoTCK has joined the room. -
-
-
-
-
-
@
SylverReZ:
@K3Nv2, Ah shit, here we go again. I ain't represented Grove Street in five years, but the Ballas won't give a shit. -
-
-
-
-
-
-
-
-
Always touching 
] brb
