GOOD NEWS EVERYBODY!!! I have decided to make a..

How to have
SEPARATE ATMOSPHERE AND SXOS EMUNAND HIDDEN PARTITIONS ON THE SAME SD TUTORIAL!

​

PLEASE READ THE ENTIRE GUIDE BEFORE PROCEEDING. I WILL DO MY BEST TO MAKE THIS COMPLETE AND EASY TO FOLLOW.

I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS DUE TO THE USE OF THIS GUIDE. I DO THIS FOR FUN AND AM NOT A PROFESSIONAL. i HAVE TESTED THIS METHOD AND HAVE SET UP A COUPLE SD CARDS.

USE AT YOUR OWN RISK!!!!

The intent of this guide is to make ONE SD CARD with TWO HIDDEN EMUNANDS. One on 11.0 for SXOS and one with current firmware for Atmosphere.

More than likely the currently installed games WILL NOT WORK IN ATMOSPHERE if they were installed with the SXOS installer.

Tinfoil/awoo installed games may work fine. This is SXOS 's fault as the installer patched stuff in a way that is not compatible with the other CFWs.

There is also a section on SHRINKING the SXOS partition if you intend to only use it for USB loading. To minimize the impact it has on your SD and keep your HDD functionality for all 3000+ compatible games.. If you do this the current SXOS EmuNAND will break including installed games and saves.. IF you made backups of the save data you can restore them later.

Bottom line is, you will probably be reinstalling games and you need a backup of everything.

This guide make a few assumptions.. I will assume you are a current SXOS user with a working 11.0 Hidden Partition EmuNAND with a FAT32 SD. No Atmosphere installation required. There many ways to accomplish most things in this guide. I am doing the bulk of the work on the PC to limit the amount of times we take the SD out of the fragile Switch SD slot.

If you do not understand the above then this tutorial may be out of your league. Please google beginner switch hacking and learn some basics.

EmuNAND is the same thing as EmuMMC. It's just an older term. I call it by the old school term. Old habits..

This guide starts with a SXOS installation in place. If you wanted to go the other direction, adding a SXOS partition to an Atmosphere EmuNAND SD you would have to adjust accordingly but the main concept still stands.


DO NOT USE EXFAT!!! EVER! NINTENDO'S FAULTY DRIVER WILL CAUSE DATA LOSS!! DONT BE LAZY! FORMAT TO FAT32 AND DO IT RIGHT TO AVOID FUTURE ISSUES! I KNOW YOU DON'T WANT TO. DO IT ANYWAY! ANY EXPERIENCED PERSON WILL TELL YOU THE SAME. WHY WOULD WE ALL GO THROUGH THE HASSLE IF IT WASN'T NECESSARY? DO IT!


THERE ARE OTHER MULTI BOOT METHODS. THIS ONE IS THE MOST STABLE. YOU COULD JUST MAKE A FILE BASED EMUNAND FOR ATMOSPHERE. FILE BASED EMUNANDS ARE KNOWN TO CORRUPT. Good way to lose all your saves.

You will need a few things

• Latest version of Hekate.
• Latest NxNandManager
• Latest EmuTool
• Atmosphere SD files
• Latest Sig Patches (the GBATemp thread)
• A Raw Backup Of your SXOS EmuNAND (if you don't have one we will make one.)
• A Backup of your current Atmosphere EmuNAND (if you don't have a current Atmosphere EmuNAND we will convert your SXOS EmuNAND)
• A partition manager capable of moving and making partitions installed on your PC, I will be using MiniTool Partition Wizard but any capable partition manage should work.
• A PC. Any should do, this guide is written with Windows in mind
• A WORKING FOLDER ON YOUR COMPUTER (NxNandMnager and EmuTool can be quite finicky about external drives and things. Just make a new folder. For the sake of this tutorial I will use a folder CALLED C:\NANDS)
• Keys.txt You can get these using Lockpick RCM or find them online.

BACK UP YOUR SAVES!!! I USE JKSV
BACK UP YOUR ENTIRE SD TO YOUR PC
This process will FORMAT YOUR SD!!!!!!

PREPARATIONS

Now we will set up the programs

On your PC:

1. Make a folder for NXNandMananger. Folder can be anywhere except the working folder as long as you can find it.
2. Unzip the NXNandManager .ZIP file to this folder
3. Place the Keys.txt in the same directory as NXNandManager.
4. Open NXNandManager, click OPTIONS then CONFIGURE KEYSET then IMPORT FROM FILE and point it to the Keys.txt.
5. Unzip EmuTool and put the emutool.exe file anywhere except the Working folder as long as you can find it.

BACKUP CURRENT SXOS EMUNAND

If you have a raw backup already you may skip this step. Just put it in the working directory.

1. Using a SD Reader insert SD with your SXOS EmuNAND in to computer.
2. Run NxNandManager
3. Select File > Open Drive> Select your SD.
4. Select Full Dump
5. Select Output Directory and choose your WORKING DIRECTORY. Name your backup. For the guide I name it SXOSemunandFULL
6. Wait Until done
7. Press OK

If you have a current Atmosphere EmuNAND you can back it up using the same steps now. Name it ATMOemunandFULL

OPTIONAL: Shrink SXOS EmuNAND

If you shrink your EmuNAND make sure you backup all saves first! Back them saves up even if you don't shrink the EmuNAND

If you would like to shrink your SXOS EmuNAND now is the time. This will make all installed NSP stop working. You can reinstall but it won't hold much. The intent is to make SXOS's impact minimal. I make SuperXCI (XCI files that contain all updates and DLC for the game) I convert NSP files and make Super XCIs out of them as well. This way Everything for SXOS compatible games is on the HDD. Except a Small EmuNAND.

You can select whatever USER data size you want. I only intend to have SAVE data on this EmuNAND so 8GB is enough for me. I play all NSP off of my SD in Atmosphere. SXOS is just for XCI USB loading.


In NxNandManager

1. Select File>Open File and select your EmuNAND raw backup.
2. Select Options > Resize EmuNAND
3. Check Format User (this is optional, however this process will render the current USER data useless anyway so just format it to make it clean, Input file will not be altered)
4. Select New Size.. I went with 5504 MB for user partition (8 GB Total) to keep enough room for saves.. some games have fairly large save files, you can choose whatever you want,
5. Click Save As,, name the file whatever you want and choose the working directory. I call mine SXOSemuRESIZED
6. Click Save.

Convert Hidden SXOS EmuNAND to Atmosphere File Based EmuNAND.

This will convert your Hidden Partition SXOS EmuNAND to Atmosphere EmuNAND files in the event that you don't have a Atmosphere EmuNAND backup. You should be able to migrate your saves and games over. GAMES INSTALLED USING THE BUILT IN SXOS INSTALLER WILL NOT WORK IN ATMOSPHERE.

If you have a raw backup from an Atmosphere Nand you can use that instead and skip this step. This section duplicates and converts your SXOS backup if you don't have an Atmosphere EmuNAND.

1. Open EmuTool
2. Under source select SXOS Hidden Partition
3. Click "Select SD card" and select the SD with the SXOS Hidden Partition
4. Under Select target select Atmosphere File.
5. Under TARGET Click "Click to Select SD Card" Name the backup and save to the working directory. Ill Call it SX2ATMOemu
6. Click START

Create New SXOS EmuNAND Partition

IF YOU ALREADY HAVE A SXOS EMUNAND IN A HIDDEN PARTITION ON THE TARGET SD YOU MAY SKIP THIS STEP
THIS SECTION WILL REFORMAT YOUR SD WITH THE NEW SHRUNKEN EMUNAND! YOU WILL LOSE ALL DATA!!! BACK UP THE SD FILES

In NxNandManager

1. Select File > Open file and select the (Shrunken or not) backup of the SXOS EmuNAND
2. Select Options > Emunand Creation Tool
3. Check NAND path is pointing to your SXOS EmuNAND backup (Shrunken or not)
4. Under "Select Emunand Type" Select SD partition
5. Under "Select Target Disk" Select your target SD.
6. Click "Create Emunand"

Resize FAT32 Partition and Make New Hidden Partition

THIS WILL MAKE ROOM FOR A SECOND HIDDEN PARTITION.


Now we will RESIZE your FAT32 Partition to leave a 29.2GB Unallocated Partition at the end of the SD

1. Open MiniTool Partition Wizard
2. Find the TARGET SD
3. Right Click on the FAT32 partition
4. Select Resize
5. Reduce the size of the FAT32 Partition by 29.2GB using the slider. Make sure that the unllocated space AFTER the FAT32 partition is 29.2GB and DON'T MESS WITH THE UNALLOCATED SPACE BEFORE THE FAT32 PARTITION! THIS IS SXOS EMUNAND!!
6. Press OK
7. Right Click on the New Unallocated Partition after the FAT32 partition. (once again not the first one. That is your SXOS Partition.)
8. Click CREATE
9. In the "CREATE NEW PARTITION" window Select the following:
   1. Create As: PRIMARY
   2. Drive Letter: NONE
   3. File System: UNFORMATTED
   4. Cluster Size:; NONE
   5. Click OK
10. In the MAIN WINDOW press Apply

That should format the unallocated space so the tools can see it.

Make new Atmosphere Hidden Partition EmuNAND

In EmuTool

1. Under "Select source" select Atmosphere files (Or hekate back up files if that's what you have)
2. Select "Click to select SD Card" and point to the Converted SXOS to Atmosphere Backup files (SX2ATMOemu) or your Atmosphere Backup, You must point to the directory with the BOOT1 BOOT2 00,01 etc etc files, Probably emummc\(A Numeric Code)\eMMC\
3. Under "Select Target" Select Atmosphere Hidden partition
4. Select "Click to select SD card" and point to your Target SD card.
5. Press START.

Restore SD backup and install Atmosphere
If all went well you should be able to copy your SD files you backed up in the beginning of the guide. That should get SXOS back up and running. then you can install Atmosphere. There are a TON of guides. just get the newest SDfiles and toss them on the SD. You'll need sigpatches too if you want to play downloaded content.

1. Copy FILES YOU BACKED UP IN THE BEGINNING OF THE GUIDE back to the SD FAT32 Partition .
2. Copy all Atmosphere files to your SD
3. Copy Sigpatches to the SD

If you are converted your EmuNAND from SXOS to Atmosphere and you didn't shrink your EmuNAND you need to copy the files in the EMUTENDO folder contents from SXOS to the Atmosphere NINTENDO folder (emuMMC/XXXX/Nintendo, XXXX is a Alpha Numeric 4 digit ID) this should make everything compatible work.
(Remember games installed with the built in SXOS installer will probably need to be reinstalled.)

Make EmuNAND visible to Atmosphere.

1. Unzip Hekate files to the ROOT of your SD.
2. Insert SD in to the Switch
3. Boot Hekate using the hekate payload and your favorite payload launching method.
4. Select EmuMMC
5. Select Migrate EmuMMC
6. Select Fix Raw
7. Select OK

Now you should be able to boot in to SXOS and Atmosphere each with their own EmuNANDS!!! Just boot the payload for the CFW you want using your favorite injection method.

Now you can update the firmware for your Atmosphere EmuNAND using daybreak. There are MANY guides on the subject. Google it!

Make sure your games work. Then you can uninstall duplicate games from the SXOS. You can move games from SD to System NAND in the Switch Data management Menu while in EmuNAND. This will move them from the FAT32 partition to the Hidden EmuNAND to free up the FAT32 even more. Remember to leave room for save files.


EXTRAS!

Here I would like to make a few suggestions....

TESLA with the FastCFWSwtich overlay,

If you would like a convenient way to switch between the CFWs (and other things too) I recommend you install TESLA with the FastCFWswitch overlay. Once installed you can Hold down L and DPad Down then Click the right joy stick to bring up Tesla at any time. It allows you to run "overlays" that are basically just homebrew programs. Emuiibo is a great Amiibo emulator, there is a fast reboot, a UMS feature, FTP etc. in this case I recommend FastCFWswitch.

FastCFWswitch allows you to switch between different CFWs with a few clicks.

TESLA page on GBATemp
This is the page for Tesla. In this instance the trick is to install it for BOTH SXOS AND ATMOSPHERE.

1. Download the latest fastCFWswitch NX-ovlloader and Tesla-Menu
2. Unzip all to the root of the SD
3. You must manually copy all the \atmosphere\contents files from NX-ovloader zip file to SXOS\titles\ to make it work in SXOS too, (I will make a pack if the developer gives me the green light.)

That's it. in SXOS or Atmosphere you can press the hotkey combo.. (hold down L and DPad Down and Click the right joy stick) to bring up the TESLA menu, then select fastCFWswitch and the CFW you want and off you go.

I suggest using different themes on your EmuNANDs so that you can tell them apart at a glance. There are SXOS and Atmosphere versions of my skeletal themes,

Skeletal Switch Theme
Skeletal TV theme
Skeletal HDD for SXOS Theme <-- Made this today

I will add more stuff and tweak this out as I have time. Please feel free to ask questions. It will help me fine tune this tutorial.

CHEERS!

Thanks to Maupiti for all the help.

 

[binkinator]

If I don't plan on going online, is there still a reason to have both EmuNANDs? My oldest NAND backup is post-SXOS. Should I just save the extra space by having one hidden partition for SXOS and putting Atmosphere on my SysNAND?

Having something to copy and fiddle with as necessary is comforting. also helps knowing that if the odd brickware somehow makes it in, the grenade will blow up inside a copy rather than inside the system itself. This guide goes through how to shrink an emunand as well, so you’re not saving that much space.

 

[simbin]

helps knowing that if the odd brickware somehow makes it in, the grenade will blow up inside a copy rather than inside the system itself

Good point, thanks

 

[mikefor20]

Good point, thanks

Yes, EmuNANDs are protection. While in EmuNAND it's like a completely separate Switch. In fact, you can have as many EmuNANDS on many SD cards. I made separate EmuNANDS for Kids and for Adults. That way I keep my save files safe and I can have kid friendly games only for them.

I would also like to point out that the EmuNAND space is not wasted. You can install to it. The majority of it will be used by your games.When in EmuNAND if you install to System you are installing to the EmuNAND. IIRC about 2GB is for the system files. The remainder is used when installing to EmuNAND.

Plus you can shrink the EmuNAND.

I use 6GB for SXOS. I only use it for archival purposes. During the guide I copied and converted the SXOS EmuNAND to an Atmopshere EmuNAND. Bringing with it All my saves and my installed games. I have >11.0 Games on the USB drive in Super XCI. That way all the DLC and UPDATES are in the XCI on the HDD as well.. I deleted all installed games and DLC then I shrank down the SX EmuNAND (this breaks installed content in the SXOS EmuNAND anyway but not the saves) . The SXOS EmuNAND is only for save files on my system. 6GB has been enough for me. Mileage may vary. Consider your needs.

 

[simbin]

I use 6GB for SXOS.

Wow! That's even better than I expected. Does the shrinking process just hard cut all your installed data, so you only need to delete whatever tiny amount of broken remnants are left afterwards?

Am I also understanding correctly that I can build both EmuNANDs from the rawnand.bin I dumped of SysNAND?

 

[mikefor20]

Emunand files is basically a portable emunand folder structure that allows you to make backup copies of the said emunand to store on a PC or USB drive. It holds all the cache data like game icons user accounts ect
I think the key point that most ppl are missing is that Emunand files is a great option to have if you decided to upgrade your SD card b/c its a simple drag and drop on the new card. There are ways to back up partition, but its more complicated and requires specific software to do it. So personally if you don't care enough to upgrade the SD card just go hidden partition.

This is terrible advice. While most of the above is true it's missing the most important part.The important difference between Files based vs Hidden EmuNAND is corruption. Hidden EmuNANDs are very stable. No R/W issues. No corrupting if you power off at the wrong time. Outside of removing the SD during a write operation you're okay. SDs can fail anyway but when you are dealing with a file based EmuNAND you're dealing with the switch's shitty SD drivers. The FAT32.standard is better than ExFAT on switch but it's still shit. Just use hidden EmuNANDs. No.corruption or allocation errors.

To backup your EmuNAND or move it, you can use the tools in the tutorial. Or clone your SD bit by bit. It's easy and definately not a reason to stick with a shoddy file based EmuNAND.

 

[MastaG]

Thanks for the detailed guide.
I currently have Hekate + Atmosphere installed and I'm using the AIO switch updater app for everything.
It has a copy_files.txt file which will copy the Hekate update.bin payload to the root of my SD called "/payload.bin" which gets picked up by the RCM x86 chip.
This makes it so I don't have to connect the switch to my PC ever for updates.

I find atmosphere a very good CFW and I like his detailed changelogs very much.

What's the benefit of having SX OS compared to Hekate/ams?

 

[MasterJ360]

This is terrible advice. While most of the above is true it's missing the most important part.The important difference between Files based vs Hidden EmuNAND is corruption. Hidden EmuNANDs are very stable. No R/W issues. No corrupting if you power off at the wrong time. Outside of removing the SD during a write operation you're okay. SDs can fail anyway but when you are dealing with a file based EmuNAND you're dealing with the switch's shitty SD drivers. The FAT32.standard is better than ExFAT on switch but it's still shit. Just use hidden EmuNANDs. No.corruption or allocation errors.

To backup your EmuNAND or move it, you can use the tools in the tutorial. Or clone your SD bit by bit. It's easy and definately not a reason to stick with a shoddy file based EmuNAND.

Yes I know Fat32 is better its pretty basic in the scene. Ive been using the Emunand SD file for sxos ever since 2018. Yes I did have 3 SD failures simply b/c I was using homebrew heavy apps with an exfat dumping copies of my owned games/dlc. But thats not a daily use issue atleast for me from years of experience, thats all im saying. SD Emunand file recovery is just a simple drag/drop no tutorials or steps needed.

I do use hidden Emu for my Atmosphere switch b/c its fat32. Overall, corruption is not a problem aslong you have a backup to recover data.

 

[binkinator]

Thanks for the detailed guide.
I currently have Hekate + Atmosphere installed and I'm using the AIO switch updater app for everything.
It has a copy_files.txt file which will copy the Hekate update.bin payload to the root of my SD called "/payload.bin" which gets picked up by the RCM x86 chip.
This makes it so I don't have to connect the switch to my PC ever for updates.

I find atmosphere a very good CFW and I like his detailed changelogs very much.

What's the benefit of having SX OS compared to Hekate/ams?

one feature and one feature only…

SXOS can mount XCIs like a virtual game card instead of having to install it like an NSP. Unfortunately it can only do this for games that require 11.0.0 or less. Still cool af.

 

[simbin]

[SX OS]
payload=bootloader/payloads/sxos.bin
logopath=/graphics/splash/sxos.bmp
icon=/graphics/icons/current/icon_sxos.bmp
id=sxos

How are you doing this part?
I tried renaming boot.dat to sxos.bin

 

[mikefor20]

Yes I know Fat32 is better its pretty basic in the scene. Ive been using the Emunand SD file for sxos ever since 2018. Yes I did have 3 SD failures simply b/c I was using homebrew heavy apps with an exfat dumping copies of my owned games/dlc. But thats not a daily use issue atleast for me from years of experience, thats all im saying. SD Emunand file recovery is just a simple drag/drop no tutorials or steps needed.

I do use hidden Emu for my Atmosphere switch b/c its fat32. Overall, corruption is not a problem aslong you have a backup to recover data.

It's not just FAT32 that's the issue. the file based option on top of FAT32 is an issue. Just it right. If you like having to back up your EmuNAND frequently and are okay with losing save files, enjoy! I am not here to debate the issue.

FILE BASED EMUNANDS ARE UNSTABLE! Period. Use hidden partitions. They are stable. You cut corners and get what you deserve. I don't care what you do. Please don't come to my thread and promote lazy solutions that lead to more issues. The dual hidden EmuNAND option is sturdy and smart. I don't want to deal with the issues that may arise from noobs making lazy irrational choices due to your misinformed recommendations. I appreciate your intentions but this is the wrong thread for that.

 

[mikefor20]

Wow! That's even better than I expected. Does the shrinking process just hard cut all your installed data, so you only need to delete whatever tiny amount of broken remnants are left afterwards?

Am I also understanding correctly that I can build both EmuNANDs from the rawnand.bin I dumped of SysNAND?

The shrinking process IIRC deletes the data. I still deleted everything maually before hand.for my OCD OCD OCD.. iirc it tells you it is formatting the user partition It may delete the saves. I honestly don't remember. Back everything up and be prepared to restore saves.i dont recall.

You can use the dump to build both. The difference between SX and Atmo EmuNANDs is the location on the SD. The Nand Manager software can convert it. The guide covers that too. Please read it from cover to cover. If something isn't clear let me know and I can fix the guide.

 

[simbin]

Thanks everyone for the help today. I'm going to give it a rest before I mess something up. The good news is that I got all the partitions setup; AMS emuMMC is booting from hekate, and I can manually swap to the SXOS boot.dat for EmuNAND. . so I just need to figure out that little bit, update AMS firmware, and start fixing my games/saves etc. Overall a pretty good day.

 

[mikefor20]

Thanks for the detailed guide.
I currently have Hekate + Atmosphere installed and I'm using the AIO switch updater app for everything.
It has a copy_files.txt file which will copy the Hekate update.bin payload to the root of my SD called "/payload.bin" which gets picked up by the RCM x86 chip.
This makes it so I don't have to connect the switch to my PC ever for updates.

I find atmosphere a very good CFW and I like his detailed changelogs very much.

What's the benefit of having SX OS compared to Hekate/ams?

one feature and one feature only…

SXOS can mount XCIs like a virtual game card instead of having to install it like an NSP. Unfortunately it can only do this for games that require 11.0.0 or less. Still cool af.

I think you forgot to mention,XCI loading AND Usb loading.

Not only can you mount and run XCIs without installing you can mount them directly from any USB storage. You can use HDD,SD with a reader,SSD,Flash drives etc. You can even use a USB -C device or an OTG cable in handheld mode. I use a SSD.or 2 512GB USB C thumb drives in handheld and a 5TB HDD in docked. It's all so easy an 8 yo does it. Best feature ever

Thanks everyone for the help today. I'm going to give it a rest before I mess something up. The good news is that I got all the partitions setup; AMS emuMMC is booting from hekate, and I can manually swap to the SXOS boot.dat for EmuNAND. . so I just need to figure out that little bit, update AMS firmware, and start fixing my games/saves etc. Overall a pretty good day.

Did you go hidden partitions?

 

[simbin]

Did you go hidden partitions?

Yes. 8GB SXOS and full 29.2GB AMS. I was a little worried because NxNandManager didn't show an [Ok] or [Close] button once it finished. I just had to [X] out. I'm not sure if that's why my FAT32 had some garbled text in its name. I just reformatted in MiniTool Partition Wizard, rebuilding lost bits with Migrate emuMMC in Hekate.

Also: EmuTool wouldn't let me convert Hekate Backup Files (rawnand.bin) to Atmosphere Files, even tho the latest changelog said that was fixed. I had to instead create a full SXOS EmuNAND first, to then create my AMS files from there.

 

[MasterJ360]

It's not just FAT32 that's the issue. the file based option on top of FAT32 is an issue. Just it right. If you like having to back up your EmuNAND frequently and are okay with losing save files, enjoy! I am not here to debate the issue.

FILE BASED EMUNANDS ARE UNSTABLE! Period. Use hidden partitions. They are stable. You cut corners and get what you deserve. I don't care what you do. Please don't come to my thread and promote lazy solutions that lead to more issues. The dual hidden EmuNAND option is sturdy and smart. I don't want to deal with the issues that may arise from noobs making lazy irrational choices due to your misinformed recommendations. I appreciate your intentions but this is the wrong thread for that.

Explaining vs promoting are 2 different things. Your right its not a debate its preference - opinionated choice that I took. Lazy & super convenient for SD upgrading, but it works fine for me 4 years straight even with the "unstable" warnings so forgive me if you think im trying to defame your thread. If you don't want my input, anti-sheep wagon or criticism then cry to the Mods about it. I can voice wherever I want.

 

[binkinator]

How are you doing this part?
I tried renaming boot.dat to sxos.bin

It’s just SXLoader‘s payload.bin renamed to something at little more memorable/less generic.

 

[simbin]

It’s just SXLoader‘s payload.bin renamed to something at little more memorable/less generic.

This is where I'm getting stuck. I'm using the SX payload from TegraRcmGUI, but it just goes back to Hekate after launching it. License file is still in root. What am I missing here?

 

[mikefor20]

Explaining vs promoting are 2 different things. Your right its not a debate its preference - opinionated choice that I took. Lazy & super convenient for SD upgrading, but it works fine for me 4 years straight even with the "unstable" warnings so forgive me if you think im trying to defame your thread. If you don't want my input, anti-sheep wagon or criticism then cry to the Mods about it. I can voice wherever I want.

Wrong again. It's not a preference, it's a mistake. And a stupid one at that. Don't spread your bullshit. I don't care what you think. It's not a sheep wagon situation. This thread is about the correct, long term solution. There are already a ton of threads where lazy idiots circle jerk and pat each other on the back for their laziness. Go there. To come to this thread to promote your fail and look for approval is sad. And against policy. You are an irritant and not "in the spirit of the thread". I believe in complete information. I presented the other options. That's why i already addressed the reasons to avoid file based nands. You advice is piss poor. You have no viable argument. Just feelings. What's next? Tell people to use the EmuNAND on your NAND option? Please! You never had an issue? That's like me telling people not to use a condom because "I never had an issue". Go somewhere else. I don't need nor appreciate your erroneous input Leave. Troll.

 

[binkinator]

This is where I'm getting stuck. I'm using the SX payload from TegraRcmGUI, but it just goes back to Hekate after launching it. License file is still in root. What am I missing here?

To get the original files from TX you‘re gonna have to use the way back machine, my friend. It’s out there.

 

[simbin]

To get the original files from TX you‘re gonna have to use the way back machine, my friend. It’s out there.

Good idea. I forget what their website address was now though lol

I already have one payload.bin of theirs, but I think that was just to inject the license code or something. And of course I have the latest boot.dat file.

Update: found it
SX Loader 1.0 (payload.bin) is what I already had (from TegraRcmGUI)

Launching from latest Hekate, just goes back to Hekate