Tutorial
Updated
SXOS and atmosphere sharing emunand + android 10 accessing FAT32
In a the tutorial thread https://gbatemp.net/threads/quickes...emunand-to-sxos-style-microsd-emunand.586474/, fellow user @lordelan explained the problems leading to the impossibility of having SXOS and atmosphere share the same emunand when using them on a switch which also has android 10 installed.
Basically, the problem is the combination of these three facts:
_____________________
Updated document to version 1.1:
// Changed backing up and restoring procedures.
// Added Tools & Software: section before Steps: section and removed Tools: section at the end.
// Fixed credits.
Basically, the problem is the combination of these three facts:
- android 10 requires a GPT partition layout, which uses sectors 1,2,… to describe the partitions.
- SXOS hidden partition style emunand is stored in the fixed sectors 1 ( TX NAND mark ) and starting on sector 2 ( actual emunand contents ).
- Atmosphere can describe SXOS hidden partition style emunands and use them, but it needs the contents to be contiguous and it doesn’t support referencing a file based SXOS emunand ( of course some modifications to atmosphere could give this support and maybe some FAT32 file descriptor trickery would also do the trick, but that would be more work, I think ).
- We create an SXOS file based style emunand STRUCTURE and arrange file data in the FAT32 partition so that the file entries are describing data for each file, yes, as it would be the case for a file based SXOS emunand, BUT we also make sure that data is contiguous on disk.
- We create a hekate+atmosphere emummc.ini to use a hidden partition style emunand that uses sector=<sector where the “Ordered and Contiguous” file based SXOS emunand contents start>.
_____________________
Updated document to version 1.1:
// Changed backing up and restoring procedures.
// Added Tools & Software: section before Steps: section and removed Tools: section at the end.
// Fixed credits.
Attachments
Last edited by Inaki,