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: 497
  • SyncfixSxosEmuAsFIle.zip
    5.6 KB · Views: 431
  • syncfix_v3 - Atmosphere.zip
    1.1 KB · Views: 248
Last edited by MezBar,

ndeadly

Well-Known Member
Member
Joined
Nov 5, 2018
Messages
460
Trophies
0
Age
36
XP
2,565
Country
Australia
Yo
Could you take a look at my config file? I changed ini to txt so I can upload it ... I've tried going into cfw sysand and shutdown from there so the file could be created still not luck and I tried to boot into emunand and sysnand several times! Should I try and re sync them and If I did so I guess I will have to run the script again?
You need to remove the ; at the beginning of the line for the setting you want to change.
 

CapitolLimited

Active Member
Newcomer
Joined
Mar 6, 2011
Messages
44
Trophies
1
XP
258
Country
United States
Thanks for this script. Unpaired my joycons recently and this got everything synced back up again. In case anyone was wondering, if you're using Exosphere and DNS-MITM, you don't have to worry about going into airplane mode. Just add that bluetooth line into system settings ini, run the script and you're good to go.
 

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
Could you take a look at my config file? I changed ini to txt so I can upload it ... I've tried going into cfw sysand and shutdown from there so the file could be created still not luck and I tried to boot into emunand and sysnand several times! Should I try and re sync them and If I did so I guess I will have to run the script again?
Everything's commented out. You need to remove the semi colons or the command line is invalid.
Post automatically merged:

Everything's commented out. You need to remove the semi colons or the command line is invalid.
enable_dns_mitm = u8!0x1
enable_external_bluetooth_db = u8!0x1
Post automatically merged:

Everything's commented out. You need to remove the semi colons or the command line is invalid.
Post automatically merged:


enable_dns_mitm = u8!0x1
enable_external_bluetooth_db = u8!0x1
I think those are the lines you need.
 

reirahul

Active Member
Newcomer
Joined
Oct 3, 2022
Messages
33
Trophies
0
Age
30
Location
Florida
XP
401
Country
United States
Does this mean dns_mitm wasn't enabled all this time? isn't supposed to be working by default as I'm already seeing logs in /atmosphere/logs/dns_mitm_startup.log ... Should I be worried? exosphere.ini already enabled and I have the needed files in atmosphere/hosts
 

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
Does this mean dns_mitm wasn't enabled all this time? isn't supposed to be working by default as I'm already seeing logs in /atmosphere/logs/dns_mitm_startup.log ... Should I be worried? exosphere.ini already enabled and I have the needed files in atmosphere/hosts

It's enabled as standard yes. However the Bluetooth devices isn't shared as standard. So with no systemsettings.ini it'll block Nintendo but not share Bluetooth.

As far as I'm aware you need to enable both those options or it won't work. At least that's what happened in my case. Simply enabling Bluetooth didn't work. I had to enable dns_mitm.

You may not need to if your already using exosphere at the time I was using a hosts file emummc.txt to block Nintendo (and incognito). I now use all 3.
 
  • Like
Reactions: reirahul

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,075
Trophies
3
Age
46
Location
At my chair.
XP
17,718
Country
Colombia
Since version 1.5.1, Atmosphère have a new setting enable_external_bluetooth_db = u8!0x1 on SD:/atmosphere/system_settings.ini file:

Once you enable that setting the first instance of atmosphère you run will copy the actual Bluetooth sync database to the file SD:/atmosphere/bluetooth_devices.db then on all instances of Atmosphère you run and if you set the value en on System_Setting.ini file will use the database on the dump file instead of the one on EmuMMC or SysMMC so, all your instances will share the same bluetooth database, including headsets and controllers.

And if you use MissionControl you can even spoof any mac from controllers synced with other consoles or PCs and you don't need to lose your sync with external devices.

More information on:

https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.5.1
 

Blythe93

The Treasure Tracker
Member
Joined
Oct 19, 2022
Messages
719
Trophies
1
Location
Serbia
XP
1,889
Country
Serbia, Republic of
I followed this guide in order to create separated Atmosphere and SX OS emuNANDs on the same SD card, so right now I have: sysNAND on OFW (15.0.1, clean), latest SX OS hidden partition emuNAND and latest Atmosphere hidden partition emuNAND. How do I go about syncing my joycons between three of them, preferably without getting my sysNAND dirty? Thanks in advance!

EDIT: Do joycons need to be synced on sysNAND prior to using any of these scripts provided in the first post?
 
Last edited by Blythe93,

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,075
Trophies
3
Age
46
Location
At my chair.
XP
17,718
Country
Colombia
I followed this guide in order to create separated Atmosphere and SX OS emuNANDs on the same SD card, so right now I have: sysNAND on OFW (15.0.1, clean), latest SX OS hidden partition emuNAND and latest Atmosphere hidden partition emuNAND. How do I go about syncing my joycons between three of them, preferably without getting my sysNAND dirty? Thanks in advance!

EDIT: Do joycons need to be synced on sysNAND prior to using any of these scripts provided in the first post?
First you prepare your SysNAND, then using the links on https://gbatemp.net/threads/have-to...etween-sysmmc-and-emummc.622204/post-10006103 you can sync that between your SysNAND and your SXOS emuNAND.

you can use the same procedure to sync between your SysNAND and the Atmosphère EmuNAND or enable Atmosphères config to keep the sync between SysNAND and the Atmosphère EmuNAND
 
  • Like
Reactions: Blythe93

Blythe93

The Treasure Tracker
Member
Joined
Oct 19, 2022
Messages
719
Trophies
1
Location
Serbia
XP
1,889
Country
Serbia, Republic of
First you prepare your SysNAND, then using the links on https://gbatemp.net/threads/have-to...etween-sysmmc-and-emummc.622204/post-10006103 you can sync that between your SysNAND and your SXOS emuNAND.

you can use the same procedure to sync between your SysNAND and the Atmosphère EmuNAND or enable Atmosphères config to keep the sync between SysNAND and the Atmosphère EmuNAND
I've followed the guide and while it didn't fix my SX OS emuNAND, it surely did fix my Atmosphere emuNAND.
I've tried using the script provided in the first post for SX OS hidden partition emuNAND but I run into the following error after pushing TegraExplorer.bin payload (v2.0.5 version which was recommended in the first post):

Code:
An error occured:

function: dump_biskey
Errcode: 57
Desc: BISKEY DUMP FAILED

Press any button to return

After backing out of that menu, I've tried executing scripts but run into several more errors. What should I do about this?
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,075
Trophies
3
Age
46
Location
At my chair.
XP
17,718
Country
Colombia
I've followed the guide and while it didn't fix my SX OS emuNAND, it surely did fix my Atmosphere emuNAND.
I've tried using the script provided in the first post for SX OS hidden partition emuNAND but I run into the following error after pushing TegraExplorer.bin payload (v2.0.5 version which was recommended in the first post):

Code:
An error occured:

function: dump_biskey
Errcode: 57
Desc: BISKEY DUMP FAILED

Press any button to return

After backing out of that menu, I've tried executing scripts but run into several more errors. What should I do about this?
that's the problem of a unsupported, outdated, and quacked CFW you will not be able to use it anymore.
 
  • Sad
Reactions: Blythe93

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
I followed this guide in order to create separated Atmosphere and SX OS emuNANDs on the same SD card, so right now I have: sysNAND on OFW (15.0.1, clean), latest SX OS hidden partition emuNAND and latest Atmosphere hidden partition emuNAND. How do I go about syncing my joycons between three of them, preferably without getting my sysNAND dirty? Thanks in advance!

EDIT: Do joycons need to be synced on sysNAND prior to using any of these scripts provided in the first post?


The joycons need to be synced to sysnand first. That I'm 100% about.

Syncfix copies the info from sysnand to emunand.... But I'm unsure if it'll do both. You might need to mount emmc in hekate then change it and run it again in not sure.


The new BT option for atmosphere will probably only work in atmosphere.
Post automatically merged:

The joycons need to be synced to sysnand first. That I'm 100% about.

Syncfix copies the info from sysnand to emunand.... But I'm unsure if it'll do both. You might need to mount emmc in hekate then change it and run it again in not sure.


The new BT option for atmosphere will probably only work in atmosphere.

Thinking about it... It's a different script so run the atmosphere one. Then mount the sxos one then back to tegra to run that script. That may work.
 
  • Like
Reactions: Blythe93

reirahul

Active Member
Newcomer
Joined
Oct 3, 2022
Messages
33
Trophies
0
Age
30
Location
Florida
XP
401
Country
United States
Been wondering if it's possible to do this in conjunction with other devices/systems? PC, steam OS or modded ps4 etc
I never owned a wireless controller before so I don't know why it can't behave like headphones? meaning it can pair with multiple devices without having to resync/pair them between devices
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,075
Trophies
3
Age
46
Location
At my chair.
XP
17,718
Country
Colombia
Been wondering if it's possible to do this in conjunction with other devices/systems? PC, steam OS or modded ps4 etc
I never owned a wireless controller before so I don't know why it can't behave like headphones? meaning it can pair with multiple devices without having to resync/pair them between devices
That's dependent of the device firmware, so free devices allows multiple devices partition on his database.

By example I have 8bitDo controller which can be paired up to 4 different devices at same time, but only in 4 different modes, that is: paired to ONE Switch, ONE device on "android" mode other device on Xbox mode and another device on playstation mode.

And I have an iPega clone which can be paired up to 8 devices in total.

With original firmware Nintendo devices only can be paired to a only device at time. That's why Mission Control have a config for impersonate another Bluetooth MAC, so you can sync your controllers whit another device an then simulate what your consoles also have that exactly MAC so the controller can talk whit both devices
 
Last edited by impeeza,

reirahul

Active Member
Newcomer
Joined
Oct 3, 2022
Messages
33
Trophies
0
Age
30
Location
Florida
XP
401
Country
United States
That's dependant of the device firmware, so free devices allows multiple devices partition on his database.

By example i have 8bitDo controller which can be paired up to 4 different devices at same time, but only in 4 different modes, that is: paired to ONE seitch, ONE device on "android" mode other device on Xbox mode and anither device on playstation mode.

And i item a iPega clone which can be paired up to 8 devices in total.

With original firmware Nintendo devices only can be paired to a only device at time. That's why Mission Control have a config for impersonate another Bluetooth MAC, so you can sync your controllers whit another device an then simulate what your consoles also have that exactly MAC so the controller can talk whit both devices
Tell me if I get this right,
So Joy-cons/Pro controller have only ONE slot of connection and when they connect to a firmware, they exchange a unique ID/transferring connection between each other. and when you sync them to another firmware the slot is occupied and they generated another unique ID. as a result it can't interfere with the former ID as its no longer existed in that SLOT?


AND Does this happen with every other controller out there? sony and xbox?
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,075
Trophies
3
Age
46
Location
At my chair.
XP
17,718
Country
Colombia
Tell me if I get this right,
So Joy-cons/Pro controller have only ONE slot of connection and when they connect to a firmware, they exchange a unique ID/transferring connection between each other. and when you sync them to another firmware the slot is occupied and they generated another unique ID. as a result it can't interfere with the former ID as its no longer existed in that SLOT?


AND Does this happen with every other controller out there? sony and xbox?
Yeah, On his storage each Joycon/Pro Controller store the MAC address of the latest paired/Sync host and have only a slot for that, most of console controllers behave like this.

Only few Third party controllers have multiple slot for concurrent multiple host devices pairing.
 
  • Like
Reactions: reirahul

Blythe93

The Treasure Tracker
Member
Joined
Oct 19, 2022
Messages
719
Trophies
1
Location
Serbia
XP
1,889
Country
Serbia, Republic of
Thinking about it... It's a different script so run the atmosphere one. Then mount the sxos one then back to tegra to run that script. That may work.
Interesting. I'll give it a try, though I'm not sure how to mount SXOS in Hekate? Running that script the usual way (without going into Hekate) just gives me the error I've mentioned here.

Code:
An error occured:

function: dump_biskey
Errcode: 57
Desc: BISKEY DUMP FAILED

Press any button to return
 

flaviometal

Member
Newcomer
Joined
Jun 15, 2009
Messages
7
Trophies
1
XP
27
Country
Brazil
Thank you very much!!!
I was giving up, now it is working fine.

For help somebody else, I open the file sd:\\atmosphere\config\system_settings.ini and comment the line enable_external_bluetooth_db = u8!0x1, just add a ; character at start of line and save, after that I delete the bluetooth.db file at sd:\\atmosphere folder and run the script again.
Thanks again
That worked! Thanks, man! Now I've have 3 controllers paired both on SYS and EMUmmc.
 

Titan1907

New Member
Newbie
Joined
Aug 3, 2020
Messages
4
Trophies
0
Age
38
XP
79
Country
Netherlands
Hi guys have a problem aso with my joycons hopefully somebody can help me fix this issue

FW 1610
Ams 155
Switch v1

Joycons, holder are up to date

Problem:

When i mount them on the switch; everything works like i can scroll in the menus with the left or right controller.
But, when i use the right one, i see in the left bottom corner a switch picture and that the left controller is not mounted..
When i press a button on the left joycon, i see in the left bottom, that the switch picture is dissapeared and see 2 hands with controllers.

Ans when starting a game, only wireless work..

Tried to removed them from the settings..afterwards connected them, same issue..restarted the console a few times with no result..tried other joycons , same problem (6 of them)..cleaned the rails but no possitive result..

When i wirelessly press L + R (not detached) it works..

When do the button test in settings it is detecting all the buttons..

With the joycons mounted on the grip its also working..

Hopefully somebody can help me..thnx already
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    A @ anotherthing: The Nintendo servers are going down in 9 days anyway.