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

  • SyncfixSxosEmuAsPartition.zip
    5.4 KB · Views: 501
  • SyncfixSxosEmuAsFIle.zip
    5.6 KB · Views: 434
  • syncfix_v3 - Atmosphere.zip
    1.1 KB · Views: 253
Last edited by MezBar,

Ropiel

New Member
Newbie
Joined
Apr 15, 2021
Messages
2
Trophies
0
Age
27
XP
36
Country
France
activated by mistake wifi while on airplane mode sysnand and then did the syncfix,hope i won't get banned ;(
 

Neville_Shorttop

Active Member
Newcomer
Joined
May 7, 2020
Messages
40
Trophies
0
Age
32
XP
372
Country
United States
activated by mistake wifi while on airplane mode sysnand and then did the syncfix,hope i won't get banned ;(

Running CFW on it's own doesn't appear to lead to bans. See ban risks.

.
image0.png

If the above doesn't apply to, the rest of this is irrelevant, otherwise, keep reading.

  • If you have blanked your prodinfo on Atmosphere, you are probably safe. However, this strategy is not recommended because at any time, Nintendo could start accepting connections from blanked Switches.
  • If your version of Atmosphere is 0.18 or newer, you are probably safe. This is because 0.18 and newer have the ability to do DNS redirection locally and by default blocks telemetry servers. By default, Atmosphere only blocks telemetry servers while 90DNS blocks all known Nintendo domains that the Switch connects to. To configure Atmosphere's DNS redirection like 90DNS, make sure Atmosphere is up to date and follow the AMS DNS redirection section here: https://nh-server.github.io/switch-guide/extras/blocking_updates/
 

Ropiel

New Member
Newbie
Joined
Apr 15, 2021
Messages
2
Trophies
0
Age
27
XP
36
Country
France
Not banned yet,like you said i think Incognito helped a lot with that and if i'm not mistaken 90DNS has been replaced by something more efficient built in Atmosphere recently so i didn't really set it up (i also disabled sending informations in nintendo account setting cause i'm from Europe),i've heard Nintendo ban with waves so i'll cross fingers they let me be :)

Anyway thanks for your help and the information you provided,really appreciate it.
 
  • Like
Reactions: MezBar

sevenpastzeero

Member
Newcomer
Joined
May 23, 2021
Messages
9
Trophies
0
Age
38
XP
123
Country
Iraq
Thank you very much. I've been pulling my hair for the past few days because didn't know what is wrong with these refurbished joy-cons. This fixed it for me.
 
  • Like
Reactions: MezBar

Arakon

Well-Known Member
Member
Joined
Apr 24, 2008
Messages
445
Trophies
1
XP
1,034
Country
Gambia, The
Can confirm. Got a bit of a scare after booting back into emuNAND, though, since all text was suddenly almost unreadable.. turns out, the script also copies other settings, such as power settings, theme settings, etc. After changing them back to before, it's all good.
 

reannu123

Active Member
Newcomer
Joined
Dec 1, 2018
Messages
27
Trophies
0
Age
24
XP
140
Country
Philippines
Thank you for this! I have questions about this:
1. Does this work on Mariko switches with sx core?
2. Does this need to be done every after system update on either Nands?

Ty in advance!
 

Neville_Shorttop

Active Member
Newcomer
Joined
May 7, 2020
Messages
40
Trophies
0
Age
32
XP
372
Country
United States
Thank you for this! I have questions about this:
1. Does this work on Mariko switches with sx core?
2. Does this need to be done every after system update on either Nands?

Ty in advance!
1. If you're using SX core to boot into Atmosphere, I don't why it would make a difference.
2. No. You should only need to do this if your controller pairs to another device and you're wanting to pair the controller back to the Switch. In which case, pair it to sys and execute the script.
 

reannu123

Active Member
Newcomer
Joined
Dec 1, 2018
Messages
27
Trophies
0
Age
24
XP
140
Country
Philippines
1. If you're using SX core to boot into Atmosphere, I don't why it would make a difference.
2. No. You should only need to do this if your controller pairs to another device and you're wanting to pair the controller back to the Switch. In which case, pair it to sys and execute the script.

I see thank you so much. So if I don't pair my controllers to other switches (which will create a different bluetooth key when I re-pair them to my switch) then regardless of firmware, they will still be in sync. Thank you!
 

reannu123

Active Member
Newcomer
Joined
Dec 1, 2018
Messages
27
Trophies
0
Age
24
XP
140
Country
Philippines
Hi can anyone help me?
I'm getting errors [FatFS] Error: NOFAT every time i try to run the script

EDIT:
I have a file based emummc resized to 7gb. I can successfully boot into emummc.
Running the script through tegraexplorer chainloaded through hekate.
sd card is in exfat. and also MBR
currently trying to repartition my sd card following instructions here https://github.com/CTCaer/hekate/issues/278

EDIT2:

Still getting the same error

EDIT3:

Okay it looks like it needed keys from lockpick rcm first. Got it to work. Thanks!
 
Last edited by reannu123,

Neville_Shorttop

Active Member
Newcomer
Joined
May 7, 2020
Messages
40
Trophies
0
Age
32
XP
372
Country
United States
I see thank you so much. So if I don't pair my controllers to other switches (which will create a different bluetooth key when I re-pair them to my switch) then regardless of firmware, they will still be in sync. Thank you!
I can't speak to syncing across different firmware versions. However, I have updated sysMMC and emuMMC together and had controller parings preserved.
 
Last edited by Neville_Shorttop,

Theroid

Member
Newcomer
Joined
Jun 19, 2017
Messages
15
Trophies
0
Age
27
XP
81
Country
Germany
Thanks for the script. Works also on mariko.
But maybe you should add that SysNand keys are needed. I had to use lockpick_rcm beforhand. Without I got a NOFAT error.
 

Tac 21

Well-Known Member
Member
Joined
Feb 2, 2008
Messages
913
Trophies
1
XP
941
Country
Canada
I wasn't able to get this to work recently...that may be due to me not needing it this time- nintendo sent back my same joycons it seems.
 

GR-DRACULA

Well-Known Member
Member
Joined
Sep 14, 2015
Messages
281
Trophies
0
Age
24
Location
crete
XP
520
Country
Greece
For some reason it doesn't work on the TegraExplorer version which released recently.
I am getting this error.
20210817_125845.jpg
EDIT: It seems that the issue is the new TegraExplorer v3 script schema. I tried porting some parts of the script but I am stuck on line 29 (and an alternative instruction should be on line 19).
 

Attachments

  • Syncfix v3_NOT_WORKING_YET.zip
    998 bytes · Views: 111
Last edited by GR-DRACULA,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Xdqwerty @ Xdqwerty: good night