Tutorial  Updated

Pairing the joy-con on emunand and sysnand

Hello guys! I had the same issue of this thread:
Practically, my joy-con and pro controller weren't synched anymore between EMUnand and SYSnand because I connected them to another console... so when I was switching from SYSnand to EMUnand (and vice versa) I had to redo the controllers pairing

In that thread, that's a way to re-sync the joy-con but you have to transfer a file from EMUnand to SYSnand and for me it's not very safe... So I found a way to transfer that file from SYSnand to EMUnand and keep the SYSnand clean!

So here is the tutorial:


WARNING:

SOMETIMES THIS TUTORIAL CAN LEAD TO THE "RED FIRST SETUP SCREEN" BUT DON'T PANIC! YOUR GAMES AND SAVES ARE SAFE, JUST COMPLETE THE SETUP AND EVERYTHING SHOULD BE AS BEFORE

WE FIGURED OUT THAT SOMETIMES THE SCRIPTS DOESN'T WORK PROPERLY WITH THE NEW HORIZONTAL MODE IF YOU HAVE YOUR JOYCONS ATTACHED SO IS PREFERABLE TO REMOVE JOYCONS BEFORE USING THE SCRIPTS.
I THINK THAT'S A TEGRA EXPLORER BUG AND NOT OUR'S.

I DON'T ASSUME ANY RESPONSIBILITY IF SOMETHING GOES WRONG SO PLEASE FOLLOW THESE STEPS ONLY IF YOU KNOW WHAT YOU ARE DOING


Preparation:
Download the latest version of Tegra Explorer from here: https://github.com/suchmememanyskill/TegraExplorer/releases
Download the right script according to your emunand type from the attached files (and make sure you choose it right)


ATMOSPHERE:

MAKE SURE YOU ARE IN AIRPLANE MODE ON EITHER SYSNAND AND EMUNAND, THIS PROCESS CAN "BREAK" YOUR DNS BECAUSE AS I KNOW, THE 8000000000000050 FILE CONTAINS ALSO WIFI AND OTHER SETTINGS AND THIS CAN LEAD TO BAN.
IF YOU'RE USING INCOGNITO MODE, YOU DON'T NEED TO BE IN AIRPLANE MODE. (BUT IS RACCOMANDED TO DO THAT)



1. Launch TegraExplorer.bin trough whatever you want (RCM loader, TegraRCM ecc…)


2. Go to [SD:/] SD CARD -> tegraeplorer -> syncfix -> Syncfix.te -> Launch Script
and follow the script instructions!

3. DONE!


If you pair your joy-cons/controllers to another console or you format your NAND (SYS or EMU), you have to launch again Syncfix.te to fix the sync issue!



SX OS EMUNAND AS HIDDEN PARTITION:
IF YOU'RE USING SXOS STEALTH MODE OR INCOGNITO MODE, YOU DON'T NEED TO BE IN AIRPLANE MODE.
ON THE CONTRARY, IF YOU ARE NOT USING THOSE, YOU HAVE TO BE IN AIRPLANE ON EITHER SYSNAND AND EMUNAND BEFORE PROCEDING.



DON'T USE TEGRAEXPLORER V2 OR LATER, INSTEAD USE THIS VERSION: https://github.com/suchmememanyskill/TegraExplorer/releases/tag/2.0.5

1. Launch TegraExplorer.bin trough whatever you want (RCM loader, TegraRCM ecc…)

2. Go to
[SD:/] SD CARD -> tegraeplorer -> syncfix -> Preparation.te -> Launch Script
and follow the script instructions!

3. REBOOT TO TEGRA EXPLORER

4. Go to
[SD:/] SD CARD -> tegraeplorer -> syncfix -> Syncfix.te -> Launch Script -> Launch Script
and follow the script instructions!

5. DONE!


You have to launch Preparation.te only the first time you follow this tutorial.
(Obviously, if you delete the emuMMC folder, you have to launch Preparation.te again but… dunno why you should delete it)

This script will create the following path on your micro sd:
sd:/emuMMC/emummc.ini
sd:/emuMMC/ER00/raw_based

This script is necessary to let Tegra Explorer read/write on your emunand and won’t affect it nowise.
If you pair your joy-cons/controllers to another console or you format your NAND (SYS or EMU), you have to launch again ONLY Syncfix.te to fix the sync issue!



SX OS EMUNAND AS FILE
IF YOU'RE USING SXOS STEALTH MODE OR INCOGNITO MODE, YOU DON'T NEED TO BE IN AIRPLANE MODE.
ON THE CONTRARY, IF YOU ARE NOT USING THOSE, YOU HAVE TO BE IN AIRPLANE ON EITHER SYSNAND AND EMUNAND BEFORE PROCEDING.
THIS SCRIPT IS TESTED ONLY ON FAT32 FILE SYSTEM, SO I DON’T KNOW IF IT WORKS ALSO ON EXFAT, LET ME KNOW IF THE EMUNAND CONFIGURATION IS DIFFERENT FOR EXFAT


DON'T USE TEGRAEXPLORER V2 OR LATER, INSTEAD USE THIS VERSION: https://github.com/suchmememanyskill/TegraExplorer/releases/tag/2.0.5

1. Launch TegraExplorer.bin trough whatever you want (RCM loader, TegraRCM ecc…)

2. Go to
[SD:/] SD CARD -> tegraeplorer -> syncfix -> Preparation.te -> Launch Script
and follow the script instructions!

3. REBOOT TO TEGRA EXPLORER

4. Go to
[SD:/] SD CARD -> tegraeplorer -> syncfix -> Syncfix.te -> Launch Script
and follow the script instructions!

5. DONE!


You have to launch Preparation.te every time you follow this tutorial.

This script will create the following paths on your micro sd:

sd:/emuMMC/emummc.ini
sd:/emuMMC/EF00/file_based
sd:/emuMMC/EF00/eMMC

Then, the script will move and rename all your Sxos emunand files from sd:/sxos/emunand/ to sd:/emuMMC/EF00/eMMC like this:

sd:/sxos/emunand/full.00.bin -> sd:/emuMMC/EF00/eMMC/00
.
.
.
sd:/sxos/emunand/full.07.bin -> sd:/emuMMC/EF00/eMMC/07
sd:/sxos/emunand/boot0.bin -> sd:/emuMMC/EF00/eMMC/boot0
sd:/sxos/emunand/boot1.bin -> sd:/emuMMC/EF00/eMMC/boot1


As I said, if you’re using exfat as your file system, please let me know if you have seven “full.XX.bin” files or less (or even more)!

This script is necessary to let Tegra Explorer read/write on your emunand.
As you can imagine, after launching Preparation.te, you aren’t able to boot to Sxos emunand, SO DON’T DO IT, just REBOOT TO TEGRA EXPLORER and launch Syncfix.te.
In Syncfix.te there’s a part that will revert the process so you can boot to Sxos Emunand again!

If you pair your joy-cons/controllers to another console or you format your NAND (SYS or EMU), you have to launch again FIRST Preparation.te, REBOOT TO TEGRA EXPLORER and THEN Syncfix.te to fix the sync issue!


Unfortunately, the Sxos version is still not running on tegragraexplorer v2 or later... so please, if you want to run the script safely on sxos, use this version of tegraexplorer until i'll update it to a newer version: https://github.com/suchmememanyskill/TegraExplorer/releases/tag/2.0.5
 

Attachments

Last edited by MezBar,
hello. i have error [FatFS] Error: NOFAT end don't know what to do. please help me, i tried everything! my sd card on 128 gb, miunted in fat32
Is your SD card formatted in fat32 or exfat? Exfat causes all sorts of issues.

You could try copying the files off the fat32 partition reformat that partition and copy back. Also is it a new SD card. Test it's not fake.
 
Hello,
I'll add my experience to this thread, as this was the one which helped me the most.
Situation : Sysnand with version 15.0.1, Emunand SXOS version 11.0.0 (emunand on file), joycons not sync between sysnand and emunand
I tried the scripts to restore settings from sysnand to emunand but the joycons wouldn't connect.

I ended thinking that there might be some kind of update in the settings between firmware 11 and 15...
Settings from FW15 might not be working when restored to FW11.
So I modified the scripts to restore the settings from emunand to sysnand (yeah, this is more pressure ;) )

And, as expected, it worked ;)

Here attached the modified scripts if you want to use them.
EmummcRenameToSxos.te => will rename the EMUMMC files to files used by SXOS for Emunand
SxosRenameToEmummc.te => will rename the files used by SXOS for Emunand back to EMUMMC files
SyncFix_EmunandToSysnand.te => will write the Emunand settings to Sysnand (the one I used)
SyncFix_SysnandToEmunand.te => will write the Sysnand settings to Emunand

To be used with latest TegraExplorer binary (use the latest, the scripts won't work with the 2.0.5 version of TegraExplorer)

Process :
1. Execute SxosRenameToEmummc.te in TegraExplorer
2. reboot
3. Execute SyncFix_EmunandToSysnand.te in TegraExplorer
4. Execute EmummcRenameToSxos.te in TegraExplorer
5. Reboot to Sysnand or SXOS and enjoy the sync ;)

Hope this will help others !
Cheers,
T.
 

Attachments

I'm actually really scared because I followed the instructions to the letter but when the red opening screen showed up, it automatically bypassed the airplane mode and my usual wifi connection was considered to be registered

I don't know if I was quick enough to 90DNS the connection but it sure scares me
 
I'm actually really scared because I followed the instructions to the letter but when the red opening screen showed up, it automatically bypassed the airplane mode and my usual wifi connection was considered to be registered

I don't know if I was quick enough to 90DNS the connection but it sure scares me
you will be fine
 
hello. i have error [FatFS] Error: NOFAT end don't know what to do. please help me, i tried everything! my sd card on 128 gb, miunted in fat32
Just a thought and I don't know if this makes a difference. When you created your emunand did you use the SD partition or the SD file based system?

If youre unsure check your micro SD card in a pc. If it sees 2sd cards and asks you to format one (don't do that) then it's a partition. I'm wondering if syncfix supports file based nand??? That might not be it. But if anyone knows please enlighten me.

Sorry for the late response. I'm just thinking of modding another switch and moving to a file based system.... But I'm sure there are still things that need ironing out.
 
I feel like I'm being saved by Atmosphere's anti-redirection loop system
You don't actually get banned for running cfw. Just don't make any changes to the system with it or update anything.

As long as you have a emummc.txt or sysmmc.txt in the hosts folder (depending on which nand you use) in atmosphere it does the same job as 90 dns... default does both nands.

I think if you chainload atmosphere through hekate that also offers some protection??
 
Just a thought and I don't know if this makes a difference. When you created your emunand did you use the SD partition or the SD file based system?

If youre unsure check your micro SD card in a pc. If it sees 2sd cards and asks you to format one (don't do that) then it's a partition. I'm wondering if syncfix supports file based nand??? That might not be it. But if anyone knows please enlighten me.

Sorry for the late response. I'm just thinking of modding another switch and moving to a file based system.... But I'm sure there are still things that need ironing out.
File-based emunand user here and Synfix is not working for my Switch. It always stuck at "Mounting emuEMMC", so I think script should be modified.
 
File-based emunand user here and Synfix is not working for my Switch. It always stuck at "Mounting emuEMMC", so I think script should be modified.
I did wonder... Although it might be tegra which needs updating rather than syncfix. More than likely it is the app but keep updating both. Fingers crossed the developer will update it to include file based systems.
 
Does that make a difference? Also does a 30gb file based nand actually use 30gb? Or does it just use the space used by the games/saves?


Well, I wasn't able to manually change the needed files in my emunand when it was a rezised files base emunand... In a full size emu I changed the files with success.
 
You don't actually get banned for running cfw. Just don't make any changes to the system with it or update anything.

As long as you have a emummc.txt or sysmmc.txt in the hosts folder (depending on which nand you use) in atmosphere it does the same job as 90 dns... default does both nands.

I think if you chainload atmosphere through hekate that also offers some protection??
Even if that cfw has installed nsp?
 
Even if that cfw has installed nsp?
Then you'll get banned yes. I did say just don't make any changes to the system. If you install nsp and try to go online with it Nintendo will know it's not your game.

Each game has an NCA (like a serial number) and. There's a handshake protocol so they want to know who owns the game owns the switch and what's the serial.

You shouldn't really be making changes to the sysnand it's best kept clean for legit stuff. But you can run cfw on it, just don't use the cfw to change things out it'll be a red flag.

If you have nsp installed don't update the switch remove it and hope it doesn't get spotted.
 
  • Like
Reactions: binkinator

Site & Scene News

Popular threads in this forum