Hacking [Help] Atmosphere 0.17.0 for Mariko

[k1ng_f1sh]

After seeing Atmosphere implement support for Mariko Consoles, I have been trying to get Atmosphere to work on my console with no luck. My Mariko console at the moment is running 11.0.1 on its SYSNAND and my sdcard is a 128GB Sandisk Ultra formatted as ExFAT

I have downloaded and merged the following into one folder
-Atmosphere 0.17.0
-latest fusee-primary (placed into /atmosphere of my sdcard)
-hekate 5.5.2
-sigpatches for AMS 0.17.0

My hekate_lpl.ini at the moment looks like this
[config]
autoboot=0
autoboot_list=0
bootwait=1
verification=1
backlight=100
autohosoff=0
autonogc=1

{--- Custom Firmware ---}
[CFW (EMUMMC)]
payload=atmosphere/fusee-primary.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp
{}

I created a brand new EmuMMC (files on sd card) through Hekate and when I select the cfw (emummc) launch option it constantly gives me the error "Couldn't parse boot0: Success!". I have tried tinkering around with the hekate_lpl file but it does not seem to want to boot.

Would anyone by any chance have some insight into what I am doing wrong.

 

[kerelenko]

Here is a guide for migrating from SX to AMS. Might be helpful.

https://rentry.co/mys8q

 

[mrgone]

ditch the exfat

 

[k1ng_f1sh]

ditch the exfat

Tried the same process just then using a Kingston Canvas GO 256GB SD Card formatted as FAT32 and its still the same error

 

[izy]

Tried the same process just then using a Kingston Canvas GO 256GB SD Card formatted as FAT32 and its still the same error

follow the guide linked above

 

[k1ng_f1sh]

follow the guide linked above

Still the same error.

Is this error occurring because I haven't flashed Spacecraft-NX to SX Core chip?

At the moment I'm launching Hekate through the SXOS payloads menu. SXOS is currently 3.1.0

 

[izy]

Still the same error.

Is this error occurring because I haven't flashed Spacecraft-NX to SX Core chip?

At the moment I'm launching Hekate through the SXOS payloads menu. SXOS is currently 3.1.0

spacecraft isnt needed

At the moment I'm launching Hekate through the SXOS payloads menu. SXOS is currently 3.1.0

see thats your problem you didnt follow the guide linked above

grab it and rename ctraer.bin to payload.bin on root of memory card
and replace old boot.dat with new one

you HAVE to load it through sxgear like in guide

 

[k1ng_f1sh]

No i did not. I updated it my Sysnand through System Settings.

spacecraft isnt needed



see thats your problem you didnt follow the guide linked above

grab it and rename ctraer.bin to payload.bin on root of memory card
and replace old boot.dat with new one

you HAVE to load it through sxgear like in guide

Holy shit it works. I was originally thinking that the sx gear boot.dat didn't apply to me because i was on sxcore but i was wrong.

What confuses me is why some youtube guides in relation to atmosphere for mariko show the person being able to boot it using the normal sxos boot.dat

 

[izy]

No i did not. I updated it my Sysnand through System Settings.


Holy shit it works. I was originally thinking that the sx gear boot.dat didn't apply to me because i was on sxcore but i was wrong.

What confuses me is why some youtube guides in relation to atmosphere for mariko show the person being able to boot it using the normal sxos boot.dat

sounds like they using retro reloaded or erista units

 

[NotACat]

I have a question, my emunand partition on my switch lite was created with NXNand manager - which is said to be compatible with both SX and Atm, do I still have to migrate it with hekate like in the tutorial? And if I want to update FW I must use daybreak right?

 

[k1ng_f1sh]

sounds like they using retro reloaded or erista units

I have a question, my emunand partition on my switch lite was created with NXNand manager - which is said to be compatible with both SX and Atm, do I still have to migrate it with hekate like in the tutorial? And if I want to update FW I must use daybreak right?

i believe you do or otherwise hekate wont recognise it. you can use the migrate emummc function in hekate to do it.

I personally haven't tried daybreak. I used choidujournx to upgrade my emunand to 11.0.1 after updating my sysnand to 11.0.1 through Nintendo updater. Once emunand was updated then patched boot0 and boot1 with a clean copy from my sysnand

 

[LeyendaV]

Why exFAT? True that you can store bigger files in the card that way, but aside that it's an awful format for the scene. Format the card to FAT32

 

[k1ng_f1sh]

Why exFAT? True that you can store bigger files in the card that way, but aside that it's an awful format for the scene. Format the card to FAT32

because I came from SXOS and I have about 120GB worth of XCI files that I really don’t want to spend time splitting

I do get what you mean

 

[godreborn]

because I came from SXOS and I have about 120GB worth of XCI files that I really don’t want to spend time splitting

I do get what you mean

I don't know about splitting files, but converting to nsp takes seconds. I have all the games I bought on my external hdds in every format (including compressed), so I do have a lot of experience with that.

 

[tinnie]

Hey guys, not wanting to hijack this thread for myself but I have some noob questions. I accidentally updated my Mariko Switch with SX OS to 11.0.1 and now can't run it. I'm new to Switch and didn't really know about the Sysnand and Emunand difference and all that until I already screwed it up. Does it matter that I don't already have Emunand created if I want to follow the guide linked here? Also, I guess not a question you can really correctly predict, but is there a possibility that I somehow fuck this up more? I think I'm pretty good at following step by step guides but I've had so much misfortune with my Switch in the 2 weeks I've had it that I'm scared to even touch it again.
Also, if, hopefully SX OS updates again to support 11.0.1 will I be able to seamlessly transition back to it after I already swith to Atmosphere? The one guide I've watched so far that involved taking the Switch apart and using Spacecraft-NX (whatever that is) mentioned not being able to switch to SX OS again.

 

[k1ng_f1sh]

Hey guys, not wanting to hijack this thread for myself but I have some noob questions. I accidentally updated my Mariko Switch with SX OS to 11.0.1 and now can't run it. I'm new to Switch and didn't really know about the Sysnand and Emunand difference and all that until I already screwed it up. Does it matter that I don't already have Emunand created if I want to follow the guide linked here? Also, I guess not a question you can really correctly predict, but is there a possibility that I somehow fuck this up more? I think I'm pretty good at following step by step guides but I've had so much misfortune with my Switch in the 2 weeks I've had it that I'm scared to even touch it again.
Also, if, hopefully SX OS updates again to support 11.0.1 will I be able to seamlessly transition back to it after I already swith to Atmosphere? The one guide I've watched so far that involved taking the Switch apart and using Spacecraft-NX (whatever that is) mentioned not being able to switch to SX OS again.

If you don't have an emunand created then create one? it takes like 15 minutes to create via hekate

No not really. Since you probably ran pirated games through SXOS while on your Sysnand its probably already been logged down a telemetry log somewhere and has probably been uploaded to Nintendo Servers already.

Yes you can. Its a relatively simple process that involves moving the emunand files to sxos/emunand and then renaming the emunand files so that sxos recognises it. No need to go to the effort of flashing spacecraft-nx to the chip

 

[LeyendaV]

because I came from SXOS and I have about 120GB worth of XCI files that I really don’t want to spend time splitting

I do get what you mean

Install those on the SD as game instead of just having the files loose.

 

[dragon184]

Sorry to hijack this thread, I think the question i need to ask is related to the topic. So i migrated SXOS to Atmosphere using the https://rentry.co/mys8q. Everything went smoothly including restoring boot0 and boot1 for my hidden emuNAND. Except i am not able to boot into Stock sysNAND. I updated my hekate_ipl.ini but that take me straight to emuNAND without asking.

 

[kerelenko]

Sorry to hijack this thread, I think the question i need to ask is related to the topic. So i migrated SXOS to Atmosphere using the https://rentry.co/mys8q. Everything went smoothly including restoring boot0 and boot1 for my hidden emuNAND. Except i am not able to boot into Stock sysNAND. I updated my hekate_ipl.ini but that take me straight to emuNAND without asking.

I assume you have a mariko switch with sx core or lite modchip? You'll need to restore the SX OS boot.dat file first then go back into the SX bootloader and select boot OFW

 

[dragon184]

I assume you have a mariko switch with sx core or lite modchip? You'll need to restore the SX OS boot.dat file first then go back into the SX bootloader and select boot OFW

Yeap, I have the Mariko and sx core installed. I'll keep 2 boot.dat files on the SD then with one of them name slightly different and switch around whenever i need to boot to either cfw or ofw.

Thanks!