Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,728,730
  • Replies Replies 9,269
  • Likes Likes 92
JigoKuu said:
I am very very sorry if I ask this in the wrong topic (let me know if it is OFF topic here and I will figure something out) or if my question is stupid...

I have Picofly chip + Hekate bootloader, Atmosphere CFW on my Switch. I have a certain microSD card, but many of my games do not fit (not enough place on it, haha). Can I prepare another microSD card with the very same settings (just different games on it) and can I simply... swap them depending on which game I want to play? I could buy a bigger microSD card, too, but since I couldn't really use or sell my current ones, I wanted to ask if maybe swapping microSD cards could also work as an option to save money and not to "waste" my microSD cards.
Click to expand...
If you have a V1 Switch, you don't want to keep swapping micro SD cards, as there is a design weakness where the card reader board connects to the motherboard, and they regularly break with too much swapping. I know the OLED Switch does NOT have this problem, I'm not sure about Lite or V2.
 
  • Like
Reactions: Blythe93
SamyKn said:
is there any guide to install Argos NX? i read that it stops hekate to boot but i can't find any guide for installation.
Click to expand...
No it not «stops» anything to work.

You extract the zip file from releases to the root of your SD card, the archive have this files:


Code: 
SDMC:
|   argon-nx.bin
|   ArgonNX-SE_0104449039444000_Mariko.nsp
|   payload.bin
|
+---argon
|   |   background.bmp
|   |   splash.bmp
|   |
|   +---logos
|   |       argon-nx.bmp
|   |       bootlogoLineageOS.bmp
|   |       bootlogoUbuntu.bmp
|   |       cpr.bmp
|   |       default.bmp
|   |       emunsw.bmp
|   |       fusee.bmp
|   |       hekate.bmp
|   |       lakka.bmp
|   |       LineageOS.bmp
|   |       Lockpick.bmp
|   |       Reinx.bmp
|   |       switchboot.bmp
|   |       sxos.bmp
|   |       Tegraexplorer.bmp
|   |       Ubuntu.bmp
|   |
|   +---payloads
|   \---sys
|       |   argon-nx-gui.bin
|       |   color.ini
|       |   hw.ini
|       |   lang.ini
|       |   lp0.bso
|       |   minerva.bso
|       |   res.emunsw
|       |
|       \---logos-gui
|               about.bmp
|               atmosphere.bmp
|               autolaunch.bmp
|               colorconf.bmp
|               confini.bmp
|               emummc1.bmp
|               emummc2.bmp
|               emummc3.bmp
|               emunand1.bmp
|               emunand2.bmp
|               emunand3.bmp
|               fileman.bmp
|               lang.bmp
|               power.bmp
|               rtc.bmp
|               sxos.bmp
|               theme.bmp
|               umssd.bmp
|               update.bmp
|
+---atmosphere
|   \---contents
|       \---010000000000100B
|               exefs.nsp
|
\---switch
    +---.overlays
    |       ArgonRTP.ovl
    |
    \---ArgonRTP
            ArgonRTP.nro


now on the folder SDMC:/argon/payloads you must copy the payloads you want to load from ARGON.

on the file SDMC:/argon/autolaunch.bin YOU PUT THE PAYLOAD you like to be auto chainloaded from Argon

I do recommend to use https://github.com/Storm21CH/ArgonNX-SE/releases
 
  • Like
Reactions: Blythe93
impeeza said:
No it not «stops» anything to work.

You extract the zip file from releases to the root of your SD card, the archive have this files:


Code: 
SDMC:
|   argon-nx.bin
|   ArgonNX-SE_0104449039444000_Mariko.nsp
|   payload.bin
|
+---argon
|   |   background.bmp
|   |   splash.bmp
|   |
|   +---logos
|   |       argon-nx.bmp
|   |       bootlogoLineageOS.bmp
|   |       bootlogoUbuntu.bmp
|   |       cpr.bmp
|   |       default.bmp
|   |       emunsw.bmp
|   |       fusee.bmp
|   |       hekate.bmp
|   |       lakka.bmp
|   |       LineageOS.bmp
|   |       Lockpick.bmp
|   |       Reinx.bmp
|   |       switchboot.bmp
|   |       sxos.bmp
|   |       Tegraexplorer.bmp
|   |       Ubuntu.bmp
|   |
|   +---payloads
|   \---sys
|       |   argon-nx-gui.bin
|       |   color.ini
|       |   hw.ini
|       |   lang.ini
|       |   lp0.bso
|       |   minerva.bso
|       |   res.emunsw
|       |
|       \---logos-gui
|               about.bmp
|               atmosphere.bmp
|               autolaunch.bmp
|               colorconf.bmp
|               confini.bmp
|               emummc1.bmp
|               emummc2.bmp
|               emummc3.bmp
|               emunand1.bmp
|               emunand2.bmp
|               emunand3.bmp
|               fileman.bmp
|               lang.bmp
|               power.bmp
|               rtc.bmp
|               sxos.bmp
|               theme.bmp
|               umssd.bmp
|               update.bmp
|
+---atmosphere
|   \---contents
|       \---010000000000100B
|               exefs.nsp
|
\---switch
    +---.overlays
    |       ArgonRTP.ovl
    |
    \---ArgonRTP
            ArgonRTP.nro


now on the folder SDMC:/argon/payloads you must copy the payloads you want to load from ARGON.

on the file SDMC:/argon/autolaunch.bin YOU PUT THE PAYLOAD you like to be auto chainloaded from Argon

I do recommend to use https://github.com/Storm21CH/ArgonNX-SE/releases
Click to expand...
Thanks mate , appreciate your explanation :grog: :bow:

One last question please if you don't mind :
After placing the files as you guided ==> while in the hekate environment when switch boots up , do i need to inject argon payload from the payload section and reboot? and if i want not to use argon anymore , i launch hekate payload and reboot?


Thanks again for your help!
 
Last edited by SamyKn,
SamyKn said:
Thanks mate , appreciate your explanation :grog: :bow:

One last question please if you don't mind :
After placing the files as you guided ==> while in the hekate environment when switch boots up , do i need to inject argon payload from the payload section and reboot? and if i want not to use argon anymore , i launch hekate payload and reboot?


Thanks again for your help!
Click to expand...
Hello there,

Argon, ArgonNX, ArgonNX-SE, fusee and Hekate all of them are bootloaders

Argon(NX-SE) is a chainloader, a bootloader designed to bootload any other payload, the main purpose or Argon is to avoid the need of update the payload of your injector.

On the V1 switch you can use an external or internal device to inject the payload and sometimes is a pain on the buttocks to update the device's payload and you must do it each time your bootloader get updated

On V2 Switch you install a modchip which loads the SDMC:/payload.bin file so you need to upgrade that file each time your bootloader get updated.

The preferred bootloader is Hekate, and most people setup Hekate to autoboot a configuration. other people prefer hekate GUI (NYX) to load and there select the config to boot.

Here is where Argon(*) born, Argon replace your first step of bootloader so you have not to upgrade the payload. Argon chainload any other bootloader you like, by example, hekate so you only upgrade the needed files and forgot about your injector.


The most common setup is:

Your injector (external, internal or modchip) loads Argon, then you setup Argon to auto chain-load Hekate.bin. then hekate loads your configuration or NYX if you like.
 
  • Like
Reactions: Blythe93 and FanNintendo
impeeza said:
Hello there,

Argon, ArgonNX, ArgonNX-SE, fusee and Hekate all of them are bootloaders

Argon(NX-SE) is a chainloader, a bootloader designed to bootload any other payload, the main purpose or Argon is to avoid the need of update the payload of your injector.

On the V1 switch you can use an external or internal device to inject the payload and sometimes is a pain on the buttocks to update the device's payload and you must do it each time your bootloader get updated

On V2 Switch you install a modchip which loads the SDMC:/payload.bin file so you need to upgrade that file each time your bootloader get updated.

The preferred bootloader is Hekate, and most people setup Hekate to autoboot a configuration. other people prefer hekate GUI (NYX) to load and there select the config to boot.

Here is where Argon(*) born, Argon replace your first step of bootloader so you have not to upgrade the payload. Argon chainload any other bootloader you like, by example, hekate so you only upgrade the needed files and forgot about your injector.


The most common setup is:

Your injector (external, internal or modchip) loads Argon, then you setup Argon to auto chain-load Hekate.bin. then hekate loads your configuration or NYX if you like.
Click to expand...


Hekate does it too...
 
  • Like
Reactions: Blythe93
josete2k said:
Hekate does it too...
Click to expand...
Yes and No. Theorically if you boot with a older hekate payload, hekate detect it on start and reboot using the most recent payload. BUT! that has failed on the past, and sometimes a breakthrough is done and the older payloads become incompatible so you need upgrade it. argon avoid it. argon had needed no upgrade on years.
 
  • Like
Reactions: josete2k, Blythe93 and FanNintendo
impeeza said:
Yes and No. Theorically if you boot with a older hekate payload, hekate detect it on start and reboot using the most recent payload. BUT! that has failed on the past, and sometimes a breakthrough is done and the older payloads become incompatible so you need upgrade it. argon avoid it. argon had needed no upgrade on years.
Click to expand...
My v1 is at 3.0.0 sysmc and emmc is 19.0.1 the less burning fuse right? if im wrong can you explain? also is it okay to go on update all the way on emmc or stay on 19.0.1 ? thanks if you get to read this
 
FanNintendo said:
My v1 is at 3.0.0 sysmc and emmc is 19.0.1 the less burning fuse right? if im wrong can you explain? also is it okay to go on update all the way on emmc or stay on 19.0.1 ? thanks if you get to read this
Click to expand...
I'm new too, As far as I understand OFW, and sysMMC is store on your console, and emuMMC is store on your SD card what ever you do on that emuMMC will not effect on the other 2.
 
FanNintendo said:
My v1 is at 3.0.0 sysmc and emmc is 19.0.1 the less burning fuse right? if im wrong can you explain? also is it okay to go on update all the way on emmc or stay on 19.0.1 ? thanks if you get to read this
Click to expand...
burned fuses affect only booting OFW if you boot a OFW version lower to the burnt fuses a panic occurs and the console do not start.

if you use CFW the burnt fuses are ignored by SYSNand or EmuNAND.

Only upgrade your *NAND if you need it, and you understand the changes on the memory available for Homebrew and Mods and all the homebrew and sysmodules you use has been upgraded to the latest atmosphère support.
Post automatically merged:

SnowStormAkikaze said:
I'm new too, As far as I understand OFW, and sysMMC is store on your console, and emuMMC is store on your SD card what ever you do on that emuMMC will not effect on the other 2.
Click to expand...
OFW is the Original FirmWare. CFW es Custom Firmware,

OFW is achived when you boot WITHOUT any modification of the bootload process (or a hekate setup to boot directly to OFW) and is only possible to the console NAND

CFW is a startup using modifications made by Atmosphère to the console firmware. and can be loaded using the console NAND or any EmuNAND created on the SD Card (you can have up to 4 of them)
 
Last edited by impeeza,
  • Like
Reactions: Blythe93 and SnowStormAkikaze

Site & Scene News

Go to forum More news

Popular threads in this forum

Homebrew Homebrew game  Chrono Trigger - Switch port

Emulation Homebrew PS1/2 Emulator  ARMSX2-NX Initial Release

Homebrew Homebrew game  GTA: Chinatown Wars - Switch port

Homebrew Homebrew game  Half Life 2 (Source Engine) - Switch Port

Feedback Homebrew  Essential Homebrew

Homebrew Homebrew game  Lego Star Wars: The Complete Saga · Switch Port

Homebrew Homebrew game  Final Fantasy IV 3D Remake - Switch port

Homebrew Homebrew game Project  So... Dan didn't want to reveal his Vulkan, so I made mine.