Hacking Question Atmosphere and SXOS 11.0.0 dual Emunand boot - where do I start?

LiborNX

Active Member
OP
Newcomer
Joined
Aug 31, 2021
Messages
26
Trophies
0
Age
41
XP
52
Country
Czech Republic
Hi there,

I have an NSW v1 unpatched with Atmosphere (latest FW) installed as EmuNAND (files) on the SD card (FAT 32). Is there a recommended approach to add a separate EmuNAND with SXOS 11.0.0 on the same SD card?

Must have: separate EmuNANDs due to SXOS being stuck at 11.0.0 for now; easily switch from one CFW to another with reboot to payload (or Tesla overlay) rather than physical SD card swap.
Nice to have: still allows for adding other systems (android, lakka...) in the future.

Cheers,
Libor

UPDATE - SOLVED

Required basics (I will not detail the steps to much for that):
- Installation of Atmosphere on EmuMMC (Partition) - there are multiple tutorials out there
- Installation of SXOS on EmuNAND (Files) - very straightforward once you boot the payload while pressing "+"

Here is the process I landed to have ATM and SXOS on the same SD card. Note they will have different firmware versions, games and saves won't be shared, homebrew apps will be shared. For noobs like me, note EmuMMC and EmuNAND are the same concept (i.e. a copy of SysNAND) but technically slightly different and respectively used by Hekate/Atmosphere and SXOS.

If your SysNAND is <= FW 11.0.0
This is basically just installing SXOS EmuNAND (Files) on the same SD card where you have an EmuMMC (Partition) for Atmosphere.
Tested: NO (should be straightforward)
### Skip steps 1,2,3 if you already have Atmosphere partition based ###
1. Hekate: set partitions. Allocate 29 Gb for the EmuMMC.
Optional (but you have to decide at this stage): allocate partitions for Android and Linux e.g. 32GB each, you'll be able to come back later and go Flash Android or Flash Linux (just remember how much space you allocated because it doesn't display when you come back to the partition menu).
2. Hekate: Generate an EmuMMC (partition)
3. Install the Atmosphere files on the SD Card
4. Drop SXOS boot.dat and license.dat at the root of your SD card -you should have from your previous SXOS installation or the Free SXOS script for file based EmuNAND by Reacher17 Le Grand (https://gbatemp.net/threads/hack-sxos.582831/page-63)
5. Edit hekate_ipl.ini adding these lines so that you only need to boot to Hekate then choose your CFW moving forward
[SX OS]
payload=bootloader/payloads/sxos.bin
6. Press "+" while launching for the first time to see the SXOS options (otherwise it will boot SXOS on your SysNAND) and follow the SXOS manual to create an EmuNAND (File based because they can't be two partition based EmuMMC/EmuNAND on the same SD card)
7. Boot to sxos via Hekate or direct, upgrade to FW 11.0.0 via Album>Homebrew>Daybreak

If your SysNAND is > FW 11.0.0
This involves setting one EmuMMC (Partition) for Atmosphere and another EmuMMC (Files) which you will downgrade to FW 11.0.0 with Atmosphere, then convert to an EmuNAND to be able to boot SXOS on it. Thanks Deejay87, you paved the way.
Tested: SUCCESS

### Skip steps 1,2,3 if you already have Atmosphere partition based ###
1. Hekate: set partitions. Allocate 29 Gb for the EmuMMC.
Optional (but you have to decide at this stage): allocate partitions for Android and Linux e.g. 32GB each, you'll be able to come back later and go Flash Android or Flash Linux (just remember how much space you allocated because it doesn't display when you come back to the partition menu).
2. Hekate: Generate an EmuMMC (partition)
3. Install the Atmosphere files on the SD Card
4. Hekate: Generate an EmuMMC (File based because they can't be two partition based EmuMMCs on the same SD card) - at this point Hekate will select the File based partition as the default EmuMMC location because it is the last created
5. Boot atmosphere, make sure you are on the EmuMMC, "E" at the end of the Firmware version, downgrade to FW 11.0.0 via Album>Daybreak
6. Hekate: Mount the SD card on your computer via Tools.
7. Open NxNandManager (https://github.com/eliboa/NxNandManager/releases) on your PC, open your File based EmuMMC, resize User to 9760Mb (Total: 12.5 Gb), export as File based EmuMMC (I tried to Save as SXOS EmuNAND but it fails at 99% - hence step 7 below instead)
8. Open Kenny's Emutool (https://gbatemp.net/threads/emutool...er-sd-switch-emu-type-on-sxos-and-more.550756). Convert your reduced File based EmuMMC (in EmuMMC\SD00 on your Sd card) to File based EMUNAND for SXOS (choose to root of your SD file as Target path, it will export to sd:/sxos/emunand). Delete the File based EmuMMC on your Sd card.
9. Drop SXOS boot.dat and license.dat at the root of your SD card -you should have from your previous SXOS installation or the Free SXOS script for file based EmuNAND by Reacher17 Le Fantastique (https://gbatemp.net/threads/hack-sxos.582831/page-63)
10. Hekate: let's fix the side effect of step 4. Redefine the partition based EmuMMC as the active one via EmuMMC tools > Migrate EmuMMC > Fix Raw
11. Edit hekate_ipl.ini adding these lines so that you only need to boot to Hekate then choose your CFW moving forward
[SX OS]
payload=bootloader/payloads/sxos.bin
12. Press "+" while launching for the first time to see the SXOS option and make sure the Emunand is active (i.e. not booting SXOS on Sysnand) which should be the case because SXOS will detect the existing File based Emunand if it was created correctly.
 
Last edited by LiborNX,
  • Like
Reactions: Kallrkyle

wurstpistole

GBAtemp MVP
Member
Joined
Nov 19, 2015
Messages
4,526
Trophies
1
XP
4,516
Country
United Kingdom
Could add another partition-based Emunand on the same card. Wouldn't recommend though, way too much going on on one SD card. If it fails, that's going to be really annoying to re-setup.
 

Shadow#1

Wii, 3DS Softmod & Dumpster Diving Expert
Member
Joined
Nov 21, 2005
Messages
10,499
Trophies
1
XP
6,062
Country
United States
Hi there,

I have an NSW v1 unpatched with Atmosphere (latest FW) installed as Emunand (files) on the SD card (FAT 32). Is there a recommended approach to add a separate Emunand with SXOS 11.0.0 on the same SD card?

Must have: separate Emunands due to SXOS being stuck at 11.0.0 for now; easily switch from one CFW to another with reboot to payload (or Tesla overlay) rather than physical SD card swap.
Nice to have: still allows for adding other systems (android, lakka...) in the future.

Cheers,
Libor
Really highly not recommend to do file based emunand of any type because the very high chance of corruption so u should make the atmos emunand partition based
 

LiborNX

Active Member
OP
Newcomer
Joined
Aug 31, 2021
Messages
26
Trophies
0
Age
41
XP
52
Country
Czech Republic
Hi
Really highly not recommend to do file based emunand of any type because the very high chance of corruption so u should make the atmos emunand partition based

I never had any corruption issue on at emunand file based (FAT32) but nothing against moving to partition :). Is moving atm emunand to partition the first step you would recommend to achieve the dual emunand boot atm/sxos?

1. Set atmos emunand partition based via Hekate
2. Set sxos emunand via sxos payload: ¿¿¿partition based / file based???
...

Cheers
 
Last edited by LiborNX,

Kallrkyle

Well-Known Member
Member
Joined
Jul 23, 2021
Messages
195
Trophies
0
Age
50
XP
189
Country
Denmark
Don't think its possible to have 2 partition based emunand on same SD, but could be wrong
why use sxos payload, isen't it possible to boot sxos from hekate ?
 

LiborNX

Active Member
OP
Newcomer
Joined
Aug 31, 2021
Messages
26
Trophies
0
Age
41
XP
52
Country
Czech Republic
That would be great to boot sxos from hekate if it is possible but setting the SXOS style Emunand is only possible from SXOS payload afaik. I wasn't sure whether it is possible to have 2 partition based emunands (sxos and atm) on one sd. If not, would you recommend the below approach?

### Draft ####
1. Set atmos emunand partition based via Hekate
2. Set sxos emunand: must be file based because two partition based emunands are not supported (???)
3. Add a config in hekate to launch sxos (how-to: ???)
...
###########


Sorry if I am asking the obvious. I tried to find other threads that might help before asking but...
...As my status say: "Newbie"
 
Last edited by LiborNX,

Kallrkyle

Well-Known Member
Member
Joined
Jul 23, 2021
Messages
195
Trophies
0
Age
50
XP
189
Country
Denmark
I have personaly always used file based emunand though some say partition based is a bit quicker, but i have never been abel to make patition based Atmos EmuMMC work on mine, before Atmos i was using SXOS, but that was also file based

Booting SXOS from Hekate you should put the SXOS payload.bin into the bootloader\payloads folder on sd card, then either use payload from Hekate or edit hekate_ipl.ini adding these lines
[SX OS]
payload=bootloader/payloads/sxos.bin
 
  • Like
Reactions: LiborNX

Maupiti

Hacking is so « Nice »
Member
Joined
Sep 16, 2018
Messages
535
Trophies
0
XP
1,050
Country
France
Don't think its possible to have 2 partition based emunand on same SD, but could be wrong
why use sxos payload, isen't it possible to boot sxos from hekate ?
I
It’s working..,a bit WIP , but working, booting emunand (11.0.) Sxos from an hidden partition, and Atmosphere from another hidden partition .

Booting straight from my dongle ( RCM loader one, which is a hell of a good injector when fiddling with multiple payloads), need to finalise to configure Hekate, import my saves , and see if everything works as intended.

First hidden partition (8 go) Sxos , unallocated, second partition Fat32 , SD with all the « stuff », third partition (hidden, with a drive letter but system files other, roughly 29,2 g at the end.

Take note, that what I will explain worked for me , but could not for you, It’s not a tutorial.

I have many backups of all my emunand/EmuMMC , sysnand.. I wanted to start from a “scratch working configuration/sd”.

And do as much “less consuming time” and “switching sd” from the switch as possible.

1. My switch (with my 400 go sd card fully functional with dual boot Emunands Sxos 11.0.(8 go sd files based, 32 go Atmosphere 12.0.1 on hidden partition), connected to my PC (running windows 10 X64,) via usb under Hekate/Tools.

2. I created a specific folder on my desktop for all the backups/downloadings following.

3. I did a full dump of Sxos emunand files based ( 8 go) via NxNandManager ( and therefore converted in a full raw nand backup), and save it on my desktop on a folder specific folder.

4. I converted my Atmosphere hidden partition to sd files using emutool and saved it on my PC to a specific folder.

5. I inserted the card I wanted to use for the tests on my PC Card reader.
I created an Sxos emunand partition based using NxNandManager with my backup (therefore wiping everything and cleaning).

6. I used mini partition wizard tool free to modify sd partition once NxNandManager finished .
I resized the fat32 partition to leave 29,2 go at the end of the sd.

7. I copied under mini partition wizard the hidden and working partition related to atmosphere on my current 400 go sd (remember? connected to Pc via Hekate ums) to the new created partition on the test sd card.

8. Ended up with a few 48 mo unallocated space at the end but doesn’t matter.

9. I copied latest Hekate (from GitHub) on the sd, atmosphere 19.5 (as it was the version of my EmuMMC and didn’t want to change loaders on my injector), bootdat, licence.dat.

10. I inserted my test sd card (note that’s the first physical move of the sd on the switch), launched Hekate, migrate emunand (atmosphere) to create the right EmuMMC.ini , checked values with partition wizard.

Tried both CFW on emunands using my injector, and they both work. 😂

Need to adjust some settings, but I think it should be alright.

To be mentioned, the hidden partition of atmosphere i copied (from my 400 go sd to my test sd was initially created by tegraExplorer payload). But to be sure , and didn’t mentioned, after the copy of this partition, I flashed back using emutool the backup of my EmuMMC on this partition. What is relevant for this atmosphere hidden partition is the start in hex of the first sector.
But I would say, it’s more because I wanted to know if possible, than a real “benefit “. 🤔
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • The Real Jdbye @ The Real Jdbye:
    very dark scenes are more common than very bright scenes so i think i made the right choice
    Gift
  • The Real Jdbye @ The Real Jdbye:
    there was also a sony with worse local dimming and the glow was really apparent
    Gift
  • SG854 @ SG854:
    Human vision is non linear anyway. 100 nits is about 50% of the peak output of a 10,000 nit display.
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    "very dark scenes are more common than very bright scenes" not in the games i play
    Gift
  • The Real Jdbye @ The Real Jdbye:
    really have to buy the top end model to get a tv that doesnt have any of those compromises and that would've had more dimming zones too but i am not made o money
    Gift
  • The Real Jdbye @ The Real Jdbye:
    @Julie_Pilgrim "very bright" is essentially pure white
    Gift
  • The Real Jdbye @ The Real Jdbye:
    pure white doesn't show up all that much it's mainly when looking at a bright sky
    Gift
  • The Real Jdbye @ The Real Jdbye:
    and if the clouds in the sky have slightly less definition to them because i turned on the contrast enhancer who cares
    Gift
  • The Real Jdbye @ The Real Jdbye:
    that's not important
    Gift
  • The Real Jdbye @ The Real Jdbye:
    i can't tell the difference
    Gift
  • The Real Jdbye @ The Real Jdbye:
    but i can certainly tell the difference with black crush if i'm watching a scifi movie and i can't see wtf is going on
    Gift
  • SG854 @ SG854:
    Human vision is logarithmic, it's not linear. And nits doesn't tell the whole story of perceived brightness. OLED'S look brighter then LCD's even when both are set to the same nit values because of the higher contrast ratio on OLED's
    Gift
  • SG854 @ SG854:
    OLED's have a 3D look
    Gift
  • kenenthk @ kenenthk:
    Charging port is more likely to fry up or battery fail before the display tbh lol
    Gift
  • The Real Jdbye @ The Real Jdbye:
    "And nits doesn't tell the whole story of perceived brightness" it's not about perceived brightness it's about all HDR content in TV and movies being mastered for 1000 nits so it doesn't look right with anything lower, it's also about dynamic range
    Gift
  • The Real Jdbye @ The Real Jdbye:
    "OLED's have a 3D look" no they don't lol
    Gift
  • SG854 @ SG854:
    As an owner of a OLED and you saying that you never seen an OLED I think I know what I'm talking about lol. I'm not talking about 3D as in 3D glasses. I'm talking about depth and pop in the picture
    Gift
  • kenenthk @ kenenthk:
    I mean to be fair og vitas are still kicking and not many have suffered from pixel bleed and they're going on nearly 10 years
    Gift
  • SG854 @ SG854:
    OLED's can get away with a lower peak brightness and still provide punchy HDR because of their contrast ratio. Like I said human vision is logarithmic. The higher the peak brightness the diminishing returns in perceived brightness.
    Gift
  • kenenthk @ kenenthk:
    Just get 5 years enjoyment out of it until Nintendy releases something and everyone forgets about switch games lol
    Gift
  • SG854 @ SG854:
    @The Real Jdbye Oleds hit around 750 nits nowadays. The difference between a 1000 nit and a 750 nit isn't huge. It's only about a 4% increase in perceived brightness. Not huge at all. You'll need at least 2000 nit displays to notice a bigger difference.
    Gift
  • SG854 @ SG854:
    Read this thread it explains it. 1000 nits is not a huge jump from 750 the LG OLEDs can hit. As I said human vision is non linear.
    +2
    Gift
  • Gift
  • mr_switch @ mr_switch:
    Not exactly 3D but the colors does pops out more
    Gift
  • mr_switch @ mr_switch:
    I just want a true dark mode theme
    for OLED Switch
    Gift
    mr_switch @ mr_switch: I just want a true dark mode theme for OLED Switch