Hacking using both SXOS and atmosphere with same EMUNAND

[urherenow]

this is in hidden partion , or does it wors on both . because i have thr Emunand created with sxos on a visible part of the sdcard and i codnt do it

It works either way. I used file-based at first, before the performance was improved, so I changed it up to use a partition. Either way, it works. Several people here other than me have already stated it works, and it has worked for quite a while.

 

[matias3ds]

It works either way. I used file-based at first, before the performance was improved, so I changed it up to use a partition. Either way, it works. Several people here other than me have already stated it works, and it has worked for quite a while.

Thanks for the info when i read the original tutorial i asked , and several people told me that it didnt on sd partition , thanks for the info .

 

[urherenow]

Thanks for the info when i read the original tutorial i asked , and several people told me that it didnt on sd partition , thanks for the info .

Stop. Maybe the migrate isn't the best option now.

Get a working emunand of your choice with SX.

Create your emummc.ini on your own. It must end with a NULL. I use Notepad++ in Windows, and make sure the cursor can go down just under the last line.

Ensure emummc is enabled in hekate_ipl.ini.

OR, before migrating, backup your Emutendo folder. You'll likely need to move it back where SX expects it to be, then adjust the emummc.ini accordingly. I think this is where people are having problems.

[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

(hit enter after Emutendo)
If using files, add a line after sector that points to the path (eg. path=emummc/ER00)

 

[kerelenko]

It is certainly possible to use a single emunand hidden partition (not files based) with both sx os and atmosphere.

Limitations. (mariko only)
If you update your emunand with choidujournx in sx os it will not longer be accessible with atmosphere.
If you update your emunand with daybreak in atmosphere it will no longer be accessible with sx os.

There are work arounds that you can do using nxnandmanager but it's not a straightforward procedure.

I am personally running both SXOS and Atmosphere on my Switch Lite with OFW 10.2 and emunand 11.0.0 and on my Erista Switch with OFW 10.1.0 and emunand 11.0.0

Advice:
Just move on to using Atmosphere. It's easier to do than how it looks.

 

[Maupiti]

Limitations.
If you update your emunand with choidujournx in sx os it will not longer be accessible with atmosphere.
If you update your emunand with daybreak in atmosphere it will no longer be accessible with sxos.

Hi, sorry to say that but you’re wrong. Being using dual boot for 3 years, and never had issues when updating my emunand (Partition based). The same one shared between Atmosphere and Sxos. On my last update of the emunand (11.0.0) I used daybreak under Sxos, and It didn’t break Atmosphere. (Sysnand on 4.0.1 Erista).

 

[JCDinPGH]

I have built and rebuild my sdcard several times now. This is what I did and the result.
1 I used emutool to build a partition on my sdcard using the sxos/emunand files as the source.
2 copied the Emutendo folder from the original sdcard
3 copied Atmosphere, and several BIN files including Hekate.
4 Created a emummc/emummc.ini that looks like
[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo
5 booted SXOS RCM and chose payloads and booted lockpick_RCM and generate keys.from emunand
6 booted SXOS RCM and chose payloads and booted Hekate.
7 reset archive bits with Hekate.
8 booted emummc (emunand) from Hekate which booted successfully.
9 Used all-in-one tool to download latest sigpatches for Hekate/Atmosphere.
10 It looks exactly like my working SXOS SDCARD with the exception that every single installed program says "corrupted data was found"
I have tried all of the above with the sdcard formatted as both fat32 and exfat.
I have done a lot of reading on many forums.
What am I missing?

 

[Maupiti]

I have built and rebuild my sdcard several times now. This is what I did and the result.
1 I used emutool to build a partition on my sdcard using the sxos/emunand files as the source.
2 copied the Emutendo folder from the original sdcard
3 copied Atmosphere, and several BIN files including Hekate.
4 Created a emummc/emummc.ini that looks like
[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo
5 booted SXOS RCM and chose payloads and booted lockpick_RCM and generate keys.from emunand
6 booted SXOS RCM and chose payloads and booted Hekate.
7 reset archive bits with Hekate.
8 booted emummc (emunand) from Hekate which booted successfully.
9 Used all-in-one tool to download latest sigpatches for Hekate/Atmosphere.
10 It looks exactly like my working SXOS SDCARD with the exception that every single installed program says "corrupted data was found"
I have tried all of the above with the sdcard formatted as both fat32 and exfat.
I have done a lot of reading on many forums.
What am I missing?

Well, missing I don’t really know.. but “messing “ with your config..for sure..why in the “hell” are you sticking with sd files ?..when it’s so easy with Partition based....I really don’t understand..
The other obvious advantage of “hidden Partition “ is that it won’t be corrupted..can’t be..,But I understand that you would like to find a solution...so good luck..My emunand is shkrinked just for the system(and saves), everything “else” on the other Partition, so no hassle to backup or “redo”.

 

[JCDinPGH]

Well, missing I don’t really know.. but “messing “ with your config..for sure..why in the “hell” are you sticking with sd files ?..when it’s so easy with Partition based....I really don’t understand..
The other obvious advantage of “hidden Partition “ is that it won’t be corrupted..can’t be..,

See step #1 using emutool to create partition. I gave up on keeping it all file based after everyone telling me to go to partition. Now partition isn't working either.

 

[Maupiti]

See step #1 using emutool to create partition. I gave up on keeping it all file based after everyone telling me to go to partition. Now partition isn't working either.

Obviously.., you need a clean install. For everything related to emunand, use NxNand Manager.

 

[kerelenko]

Hi, sorry to say that but you’re wrong. Being using dual boot for 3 years, and never had issues when updating my emunand (Partition based). The same one shared between Atmosphere and Sxos. On my last update of the emunand (11.0.0) I used daybreak under Sxos, and It didn’t break Atmosphere. (Sysnand on 4.0.1 Erista).

It's not the same with mariko and erista. On my erista switch I can update emunand with either daybreak or choidujournx with no issues. Not so with my mariko.

 

[JCDinPGH]

I can try rebuilding the partition with NxNand Manager. I really really do not want to have to reinstall everything. That is 400G of games and patches. I just don't understand why every single one shows as corrupted data when I used the same emunand files that are working on the original sdcard and the same files from the Emutendo folder. I have backups of all of this so other than it being time consuming, it is relatively easy.

 

[JCDinPGH]

Went through the enite process again. And stil every installed software says "corrupted data found". Again, the emutendo folder was copied from a very working SXOS sdcard. The emunand was moved to a partition this time but instead I used NxNandManager to redo the entire SDCARD from scratch. WTF am I missing?!

 

[JCDinPGH]

I ma going to make a disk image of the original SDCARD and then clone it to the new card and see if it works. I am just not sure what else to try. Even upgraded to atmosphere 18 but still the same "corruption" problems.

 

[kerelenko]

Be sure to have the sigpatches on Atmosphere installed before installing any games.

 

[urherenow]

It's been so long since emummc was a thing, so I don't know if this is even relevant anymore, but have you read through the thread : https://gbatemp.net/threads/how-to-setup-atmosphere-emummc.541060/page-14 ?

Maybe that will help (the bit in the OP about the 1024.bin). I do vaguely recall having issues initially with things installed under SX, but have had none since, so it either got fixed in boot.dat somewhere along the way, or in a newer version of SX Installer.

So, you may very well need to reinstall everything (shouldn't mess up your saves, but backing them up and reinstalling them should work). To test, install a new game using Tinfoil while using SX, then a different game while using Hekate/Atmosphere (both while in emummc), and see if those games run under the different CFW. If they do, you're chasing your own tail here, and the problem lies with how SX originally did installs. Different keys or something silly. In this case, remove the installed games, then reinstall them. No need to keep rebuilding emummc from scratch.

EDIT: relevant thread here if those were originally XCI files: https://gbatemp.net/threads/atmosphere-unable-to-play-installed-xci-games-from-sx-os.547267/

I've used mostly Tinfoil for a while now when installing stuff. Using Nut over USB for large games and xci files, even.

 

[Maupiti]

Be sure to have the sigpatches on Atmosphere installed before installing any games.

Sigpatches don’t throw “corrupted data”, but an error ‘unable to start software...”.

It's been so long since emummc was a thing, so I don't know if this is even relevant anymore, but have you read through the thread : https://gbatemp.net/threads/how-to-setup-atmosphere-emummc.541060/page-14 ?

Maybe that will help (the bit in the OP about the 1024.bin). I do vaguely recall having issues initially with things installed under SX, but have had none since, so it either got fixed in boot.dat somewhere along the way, or in a newer version of SX Installer.

So, you may very well need to reinstall everything (shouldn't mess up your saves, but backing them up and reinstalling them should work). To test, install a new game using Tinfoil while using SX, then a different game while using Hekate/Atmosphere (both while in emummc), and see if those games run under the different CFW. If they do, you're chasing your own tail here, and the problem lies with how SX originally did installs. Different keys or something silly. In this case, remove the installed games, then reinstall them. No need to keep rebuilding emummc from scratch.

EDIT: relevant thread here if those were originally XCI files: https://gbatemp.net/threads/atmosphere-unable-to-play-installed-xci-games-from-sx-os.547267/

I've used mostly Tinfoil for a while now when installing stuff. Using Nut over USB for large games and xci files, even.

Yeah, could be, never used Sx installer, only tinfoil and never had issues...(even under Atmosphere).

 

[JCDinPGH]

What's weird is I have run into both issues., corrupted data and unable to start software. I am just not sure what I am missing and what could have caused the corrupted data or the "couldn't start software issue". The steps I followed seem to be pretty standard.

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

My guess is this could easily be XCI related. I never kept track of what was XCI or NSP installs but I will now. Everything will be converted to NSP first. Good find. After all of the reading I did, somehow I never saw that. Very helpful.

 

[The Real Jdbye]

Stop. Maybe the migrate isn't the best option now.

Get a working emunand of your choice with SX.

Create your emummc.ini on your own. It must end with a NULL. I use Notepad++ in Windows, and make sure the cursor can go down just under the last line.

Ensure emummc is enabled in hekate_ipl.ini.

OR, before migrating, backup your Emutendo folder. You'll likely need to move it back where SX expects it to be, then adjust the emummc.ini accordingly. I think this is where people are having problems.

[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

(hit enter after Emutendo)
If using files, add a line after sector that points to the path (eg. path=emummc/ER00)

A blank line is not the same as null, FYI.

Sigpatches don’t throw “corrupted data”, but an error ‘unable to start software...”.



Yeah, could be, never used Sx installer, only tinfoil and never had issues...(even under Atmosphere).

Wrong, I've had the corrupted data message with custom nsps/xci converts when I didn't have the proper sig patches. Had to reinstall the nsps after fixing the sig patches, they wouldn't work until I did.

 

[Maupiti]

A blank line is not the same as null, FYI.
Wrong, I've had the corrupted data message with custom nsps/xci converts when I didn't have the proper sig patches. Had to reinstall the nsps after fixing the sig patches, they wouldn't work until I did.

My bad, didn’t know about that, by custom you mean an xci with updates build and then converted into nsp ?

 

[The Real Jdbye]

My bad, didn’t know about that, by custom you mean an xci with updates build and then converted into nsp ?

I mean mainly homebrew nsps and scene DLC unlockers. I already mentioned XCI converts too.