Tutorial Running Atmosphere on Patched SX Core Switch

  • Thread starter GCS
  • Start date
  • Views 95,506
  • Replies 335
  • Likes 22

GCS

Well-Known Member
OP
Member
Joined
Sep 10, 2020
Messages
519
Trophies
0
XP
773
Country
Turkey
Running Atmosphere on Patched Sx Core Consoles (Erista, Mariko) is actually possible. You can use the Homebrew that aren't compatible with SX OS.
WARNING
1- I do not take responsibility for what happens to your switch!
2- Don't enable AutoRCM!
3- There might be issues on installation in Marikos.
4- DO NOT use this guide to downgrade your SysNAND.


REQUIREMENTS: Latest Hekate, Latest Atmosphere with fusee-primary, and you may need 30gb free space on your sd, check the 2nd Part.


PART 1: BASIC SETUP
There are 2 methods that you can follow during this process. "Spacecraft-NX Method" requires you to open the back of your Switch and when you follow this method you won't be able to boot to SX OS. I would recommend the "Clean Up Method" since it is both easier to do and gives you the same end result as Spacecraft without all the hassle of flashing the chip. Aditionally, before trying any of these methods you may want to back up your save data on your emuNAND via JKSV or Checkpoint.

Step 1: Extract and copy downloaded files to your Switch's Micro SD card. Copy fusee-primary to \bootloader\payloads and rename hekate bin file to "payload.bin". Also download hekate ipl from this thread remove the .txt extension from it by renaming the file, then and copy it to /bootloader/.
Step 2: Download sx gear boot.dat from the sx portal, don't copy it to SD Card yet.
Step 3: Put Micro sd card back to Switch and boot it up while holding +.
Step 4: Choose Options, click Sx Core, and than cleanup.
Step 5: Press Payloads, launch Hekate.
Step 6: Set your date, time.
Step 7: Launch CFW EmuMMC (Make sure you have an emuNAND first, see Part 2 of the guide.) [Take precautions for not getting banned like setting up 90DNS or by simply closing your modem for now.]
Step 8: Close your Switch and insert SD Card to PC.
Step 9: Delete the existing boot.dat file in the SD and copy over the SX Gear boot.dat and boot.ini.
Step 10: Download the latest sigpatches and copy them.
Step 11: Now you can boot via Launch EmuMMC without the need of CleanUp.

(The new clean up method is from Switchway discord server.)
You should follow this guide to install Spacecraft-NX to your modchip. After that you should download Hekate and Atmosphere files to your SD Card. Rename hekate bin to payload.bin.


PART 1: SETUP
There are 2 methods that you can follow in here. First one requires to open up your Switch's back plate and get your modchip to debug mode. The second one will be done via SD Card. I would recommend the second method. Aditionally, before trying any of these methods you may want to back up your save data on your emuNAND via JKSV or Checkpoint.
PART 1.A:
You should follow this guide to install Spacecraft-NX to your modchip. After that you should download Hekate and Atmosphere files to your SD Card. Rename hekate bin to payload.bin .

PART 1.B:
1- You need to have an EmuMMC to do this method. Create one if you don't have it already.

2- If you haven't configured a wifi protection for your EmuNAND (90DNS, Incognito) then turn off your router after the 3rd step.


3- If you updated via ChoiDujourNX on your emuNAND then you have to either get a donor boot0/boot1 or backup your sysNAND boot0/boot1 and then restore it via NxNandManager or EMUtool (if you're using a partition based emuNAND) or simply replace the files in your sxos/emunand/ folder (if you're using a file based emuNAND). This is because your ChoiDuJourNX corrupts your boot0/boot1 and will prevent you from being able to boot into emuNAND on Atmosphere.
Hekate also has this function for emuNAND. If you use that, please be sure you're NOT flashing sysNAND!


Step 1: Download SX Gear (can be found on SX Portal), Latest Hekate and latest atmosphere (fusee-primary too). (If the SX Site is down then you can get SX Gear from the SX Discord Server.)
Step 2: Extract downloaded archives to your SD Card.
Step 3: Create a file called hekate_ipl.ini in the /bootloader/ folder and copy this code inside to it:
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
emummcforce=1

[Stock sysNAND]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Step 4: Rename hekate bin to payload.bin.
Step 5: Create a file called exosphere.ini in the SD Card's root and paste this code inside it:

# Key: debugmode, default: 1.
# Desc: Controls whether kernel is debug mode.
# Disabling this may break Atmosphere's debugger in a future release.

# Key: debugmode_user, default: 0.
# Desc: Controls whether userland is debug mode.

# Key: disable_user_exception_handlers, default: 0.
# Desc: Controls whether user exception handlers are executed on error.
# NOTE: This will cause atmosphere to not fail gracefully.
# Support may not be provided to users tho disable these.
# If you do not know what you are doing, leave them on.

# Key: enable_user_pmu_access, default: 0.
# Desc: Controls whether userland has access to the PMU registers.
# NOTE: It is unknown what effects this has on official code.

# Key: blank_prodinfo_sysmmc, default: 0.
# Desc: Controls whether PRODINFO should be blanked in sysmmc.
# This will cause the system to see dummied out keys and
# serial number information.
# NOTE: This is not known to be safe, as data may be
# cached elsewhere in the system. Usage is not encouraged.

# Key: blank_prodinfo_emummc, default: 0.
# Desc: Controls whether PRODINFO should be blanked in emummc.
# NOTE: This is not known to be safe, as data may be
# cached elsewhere in the system. Usage is not encouraged.

# Key: allow_writing_to_cal_sysmmc, default: 0.
# Desc: Controls whether PRODINFO can be written by homebrew in sysmmc.
# NOTE: Usage of this setting is strongly discouraged without
# a safe backup elsewhere. Turning this on will also cause Atmosphere
# to ensure a safe backup of calibration data is stored in unused
# mmc space, encrypted to prevent detection. This backup can be used
# to prevent unrecoverable edits in emergencies.

# Key: log_port, default: 0.
# Desc: Controls what uart port exosphere will set up for logging.
# NOTE: 0 = UART-A, 1 = UART-B, 2 = UART-C, 3 = UART-D

# Key: log_baud_rate, default: 115200
# Desc: Controls the baud rate exosphere will set up for logging.
# NOTE: 0 is treated as equivalent to 115200.

# Key: log_inverted, default: 0.
# Desc: Controls whether the logging uart port is inverted.

[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0

Step 6: Put the SD Card back to the Switch and you'll boot into Hekate.

Step 7: Select emuMMC in the main menu, then select Migrate emuMMC and finally select Emunand.

Step 8: Once the process is done, choose Close.

Step 9: Click on Launch and then Atmosphere CFW. If you would need to boot into SysNAND without cfw, you need to choose Stock SysNAND from Launch Options.

DONE (You don't need to follow Part 2: EmuNAND Setup)

If you would like to install sigpatches than you should change the hekate_ipl.ini like this:
#kip1patch=nosigchk changed to kip1patch=nosigchk

(This part of the guide has been adapted)

PART 2: EMUNAND SETUP
You have 2 options in here. If you already have an EmuNAND on SX OS as hidden partition follow " USING THE SAME EMUMMC ON BOTH CFWs", if not follow the other part. You shouldn't do both of them.

Step 1: Close your switch and take your sd back to pc.
Step 2: Create a folder called EmuMMC and than create a text file named emummc.txt.
Step 3: Copy this to text to file and then save it.
Code:
[emummc]
enabled=1
sector=0x2
path=emuMMC/ER00
id=0x0000
nintendo_path=Emutendo
Step 4: Enable see file extensions for Windows.
Step 5: Rename the file to emummc.ini .
Step 6: EmuMMC is now ready. You can run from EmuNAND, by clicking Launch and then "CFW EmuMMC " on Hekate.
You should have 30gb space for EmuNAND on micro sd card(You can use another sd card too, make sure to copy boot.dat , license files, hbmenu.nro and all the files that we downloaded to new sd).

Step 1: Click emuMMC and than create emunand as partition.
Step 2: Go back to menu, press Launch and than CFW emuMMC.


DONE! Now you can use the sys-mods or hb apps that aren't compatible with SX OS!

NOTE: It may take some time to boot up after restarts, it's normal.
NOTE 2: If you are going to download sigpatches you should use these (NOT for fusee-primary).
IF YOU WEREN'T ABLE TO BOOT:
A. If your Switch Stuck at Switch Logo During Boot (Mariko):
- Try deleting exosphere.ini and try booting up your switch. Turn off your router in case of a ban.
B. Try Fusee-Primary:
1- Boot into Hekate again.
2- Click Payloads and then choose fusee-primary. See if it works now.
THIS SHOULD BE DONE ON EVERY BOOT INTO ATMOSPHERE.
 

Attachments

  • hekate_ipl.ini.txt
    359 bytes · Views: 138
Last edited by GCS,

Lightyose

True Light
Member
Joined
Jan 26, 2016
Messages
977
Trophies
1
Website
gbatemp.net
XP
1,578
Country
United States
Interesting, I guess for those who have patched switches, may have the advantage using another CFW with SX Core.

I haven't seen atmosphere running on Mariko yet. But I expect for it to be available sooner or later.
 
  • Like
Reactions: Hmed and GCS

masbass

Well-Known Member
Newcomer
Joined
Jul 17, 2009
Messages
73
Trophies
0
Location
Athens
XP
450
Country
Greece
Thanks for the checklist, my SX Core arrived today and will work on it in the weekend and was looking for such a list of actions. Wouldn't mind using SX OS as my plans for my Switch uses are rather limited but my worry is that TeamXecuter will at one point understandably abandon this project in the future and Atmosphere being open source will continue with updates and improvements.
 

GCS

Well-Known Member
OP
Member
Joined
Sep 10, 2020
Messages
519
Trophies
0
XP
773
Country
Turkey
I tried this... Not your tutorial, exactly.. But I followed similar steps and was greeted with a Boot0 error. Rip me.
I got the same error, too and after some research in the forum, HenryMin said in a thread that you should do cleanup before running atmosphere. After I did that I was able to boot to atmosphere
 

Memoir

Hi, I'm Cynical!
Member
Joined
Jun 24, 2007
Messages
10,841
Trophies
1
Location
In the Murderbox!
Website
www.twitch.tv
XP
12,483
Country
United States
I got the same error, too and after some research in the forum, HenryMin said in a thread that you should do cleanup before running atmosphere. After I did that I was able to boot to atmosphere

I did that, and got the error. So I started from scratch and got the system to boot. Atmosphere requires a bit more setup than SX...
 
  • Like
Reactions: GCS

Qwertindo

Member
Newcomer
Joined
Sep 23, 2020
Messages
10
Trophies
0
XP
89
Country
United States
You need to repeat cleanup + launch Hekate steps on every boot. You need to create emuNAND for just once.
Have some risk to brick if I do something wrong?

--------------------- MERGED ---------------------------

Have some risk to brick if I do something wrong?

I create this post suggestion for some doubts I have about V1 Erista, can you clarify some of this doubts, please?

I’ve looking for some tutorial for SX CORE on iPatched Erista model and is not cleared.

Questions about Homebrews compatibility, Atmosphere CFW on it, what works or don’t in comparative with Mariko V2 model.

All works fine on Erista V1 iPatched like the original Fusee hackable Swich?

What can I do or not? What can brick my console?

Can someone make a updatable guide on these terms?


Have you tested all homebrews like, MissionControl, Nand backup, Keys Backups, Icognito etc..?

I don’t found a organize post about V1 erista iPatched. Only posts talking about Marino version.
 

GCS

Well-Known Member
OP
Member
Joined
Sep 10, 2020
Messages
519
Trophies
0
XP
773
Country
Turkey
Have some risk to brick if I do something wrong?

--------------------- MERGED ---------------------------



I create this post suggestion for some doubts I have about V1 Erista, can you clarify some of this doubts, please?

I’ve looking for some tutorial for SX CORE on iPatched Erista model and is not cleared.

Questions about Homebrews compatibility, Atmosphere CFW on it, what works or don’t in comparative with Mariko V2 model.

All works fine on Erista V1 iPatched like the original Fusee hackable Swich?

What can I do or not? What can brick my console?

Can someone make an updatable guide on these terms?


Have you tested all homebrews like, MissionControl, Nand backup, Keys Backups, Icognito etc..?

I don’t found a organize post about V1 erista iPatched. Only posts talking about Mariko version.
-As far as you follow the tutorial, the chance of brick is nearly impossible.
-Most of the RCM apps will work fine on Erista, but Mariko can get bricked.
-You can give unpatched switch tutorials a try on your Patched Erista since they are similar, I can't say if it will brick your switch or not, but in most cases it won't.
-You can't even load Hekate in Mariko, they aren't compatible. A new version for Marikos can come out.
 

Qwertindo

Member
Newcomer
Joined
Sep 23, 2020
Messages
10
Trophies
0
XP
89
Country
United States
-As far as you follow the tutorial, the chance of brick is nearly impossible.
-Most of the RCM apps will work fine on Erista, but Mariko can get bricked.
-You can give unpatched switch tutorials a try on your Patched Erista since they are similar, I can't say if it will brick your switch or not, but in most cases it won't.
-You can't even load Hekate in Mariko, they aren't compatible. A new version for Marikos can come out.


Ok, thanks man! Helps a lot!
 
  • Like
Reactions: GCS

Aditzu

Well-Known Member
Newcomer
Joined
Jan 20, 2016
Messages
53
Trophies
0
XP
138
Country
Romania
Sorry if reviving old thread, but is it a must to create a new emunand if I already have the one created for SX OS, or is it that Atmosphere needs a separate emunand in order to work. Would want to know if it's possible to kind of dual boot SX OS along with Atmosphere using the same emunand I have right now.

So, ideally, the process would be this. If I want to boot into SX OS, I turn the system on normally, it should boot me into the emunand with SX OS. If I want to boot into atmosphere, power on holding the + button -> options -> cleanup (also, what exactly does the cleanup actually clean? just curious) -> boot hekate via payloads -> launch emunand (should ideally be the same one). That should boot me into the same emunand, but using atmosphere. Is that possible?

EDIT: Would want to mention that my emunand is file based (not hidden partition). Maybe adding it into a hidden partition would allow it to work with Atmosphere?
 
Last edited by Aditzu,

GCS

Well-Known Member
OP
Member
Joined
Sep 10, 2020
Messages
519
Trophies
0
XP
773
Country
Turkey
Sorry if reviving old thread, but is it a must to create a new emunand if I already have the one created for SX OS, or is it that Atmosphere needs a separate emunand in order to work. Would want to know if it's possible to kind of dual boot SX OS along with Atmosphere using the same emunand I have right now.

So, ideally, the process would be this. If I want to boot into SX OS, I turn the system on normally, it should boot me into the emunand with SX OS. If I want to boot into atmosphere, power on holding the + button -> options -> cleanup (also, what exactly does the cleanup actually clean? just curious) -> boot hekate via payloads -> launch emunand (should ideally be the same one). That should boot me into the same emunand, but using atmosphere. Is that possible?
As far as I know you can’t use the same emunand in both cfws (I might be wrong.). So you will have 2 seperate emunands.

The process you wrote is correct. I don’t have that much knowledge about cleanup too. But, I think it does do something with boot0 and boot1. Btw liked your avatar:)

--------------------- MERGED ---------------------------

can it run lockpick while on hekate/
You can copy lockpick_rcm to root of the sd and run it from sx boot menu. And yes, you can still run it from hekate. Just copy the payload to bootloader/ payloads folder.
(Make sure that your Switch is Erista, not red-boxed one or you might brick it.)
 
  • Like
Reactions: Aditzu

HenryMin

Well-Known Member
Member
Joined
Jun 19, 2020
Messages
126
Trophies
0
XP
619
Country
Korea, South
Sorry if reviving old thread, but is it a must to create a new emunand if I already have the one created for SX OS, or is it that Atmosphere needs a separate emunand in order to work. Would want to know if it's possible to kind of dual boot SX OS along with Atmosphere using the same emunand I have right now.

So, ideally, the process would be this. If I want to boot into SX OS, I turn the system on normally, it should boot me into the emunand with SX OS. If I want to boot into atmosphere, power on holding the + button -> options -> cleanup (also, what exactly does the cleanup actually clean? just curious) -> boot hekate via payloads -> launch emunand (should ideally be the same one). That should boot me into the same emunand, but using atmosphere. Is that possible?

EDIT: Would want to mention that my emunand is file based (not hidden partition). Maybe adding it into a hidden partition would allow it to work with Atmosphere?


You can same emuNAND on both CFW, by just editing /emuMMC/emummc.ini

[emummc]
enabled=1
sector=0x2
path=emuMMC/ER00
id=0x0000
nintendo_path=Emutendo

Also, 'Clean up ' makes clean, original BOOT0 since the modchip modifies nand BOOT0.
https://twitter.com/hexkyz/status/1278304294865907712

cleanup.png
 
Last edited by HenryMin,
  • Like
Reactions: de9ed and Aditzu

GCS

Well-Known Member
OP
Member
Joined
Sep 10, 2020
Messages
519
Trophies
0
XP
773
Country
Turkey

HenryMin

Well-Known Member
Member
Joined
Jun 19, 2020
Messages
126
Trophies
0
XP
619
Country
Korea, South
Thank you for explaining:). The emuMMC config that you said, is it for the emuMMC that is created with sx os or hekate?

Created with SX bootmenu, it creates emuNAND starts on sector 0x2
Or you can use NXNandManager instead, it also creates emuNAND compatible on both SXOS and Atmosphere.
 
Last edited by HenryMin,
General chit-chat
Help Users
    KennieDaMeanie @ KennieDaMeanie: https://youtube.com/shorts/VRZomCYpwY8?feature=share