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

marhalloweenvt

Well-Known Member
Member
Joined
Oct 2, 2014
Messages
235
Trophies
0
Age
29
XP
912
Country
I wrote the PR for the atmosphere bluetooth synchronisation setting. Allow me to clarify a few things...

Firstly, this hasn't been released yet. It was merged into master a few days ago and the changelog was updated, but it's not present in the 1.5.0 prerelease. The only way to use it currently is to build atmosphere master for yourself.


That's more or less correct. Basically, it intercepts the calls that read or write the pairing database to the system save file, and stores a copy on the sd card. On first boot with the setting enabled, the bluetooth_devices.db file will be created from the current environment when the console reads the database from system save. Subsequent attempts to read the database from the system save will load the one from sd instead, allowing for a common database between all sys/emummc. Writes store the current database to both sd card and system save, meaning that any changes to the database will also end up synchronised in the system saves too (only for sys/emummc you've booted with the setting enabled, of course). Because this relies on atmosphere to mitm the relevant IPC functions for loading and storing the database, it can't be used to synchronise with OFW.


This can't automatically sync the databases between consoles, if that's what you're asking. You could however manually copy the database file from one switch to another with the setting enabled in order to have the same pairings on both consoles. Note that you would also have to use Mission Control to spoof the bluetooth MAC address of the original console on the second in order for the controllers to consider the pairings valid. Also note that doing this and using the two consoles in the vicinity of one another may cause unpredictable behaviour with the consoles fighting over the connection.


It's just a binary dump of the array of bluetooth device settings documented here
Thank for your marvelous work. I have just update Atmosphère to 1.5.1 and your PR works flawlessly. Every controllers, joycons, ... which I have sync with OFW now can be used with EmuNAND.
 
Last edited by marhalloweenvt,

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
6,511
Trophies
2
XP
6,152
Country
United States
Hekate can dump joycon data too, for use with L4T and lakka. So we have two different sync systems?
Hekate dumps the MAC addresses of the joycons in a file. They are not read by Atmosphere thereafter (that I’m aware of).

This AMS feature puts the data in a .db file that will be picked up and read back in and synced.

So yeah, two different methods For two different application audiences.
 

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
Thank for your marvelous work. I have just update Atmosphère to 1.5.1 and your PR works flawlessly. Every controllers, joycons, ... which I have sync with OFW now can be used with EmuNAND.
I'm still having trouble. It's not throwing up an error now I've updated. But it's not creating the .dB file.

Can you upload a copy of your system_settings. Ini and I'll check against it?
 

marhalloweenvt

Well-Known Member
Member
Joined
Oct 2, 2014
Messages
235
Trophies
0
Age
29
XP
912
Country
I'm still having trouble. It's not throwing up an error now I've updated. But it's not creating the .dB file.

Can you upload a copy of your system_settings. Ini and I'll check against it?
Of course, please take a look at attachment (delete ".txt" before opening) and make sure you have updated to newest Atmosphere 1.5.1.

Edit1: For checking after apply settings, you just need to run Atmosphere with SysNAND, wait until you can access Homescreen, then Power Off and check if there is any .db file in /atmosphere folder in your SD.
 

Attachments

  • system_settings.ini.txt
    3.8 KB · Views: 89

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
Hekate can dump joycon data too, for use with L4T and lakka. So we have two different sync systems?


I could only get that partially working. My joycons week work fine. My pads not so much. I did get lakka to sync with the pad but it wouldn't work. In the end I went for an 8 bit do adapter. My. Theory was Hekate could actually only sync what it used.... And since I wasn't/couldn't use my pad in Hekate the Bluetooth dump wouldn't work either (I figured it wasn't getting the info from atmosphere but I'm not sure). It's not an official pad so it could be that.... But it works fine with the adapters.


It would be nice if the .dB file was interchangeable between applications.... But this is be so if that happens Im not expecting it soon.
 

ndeadly

Well-Known Member
Member
Joined
Nov 5, 2018
Messages
460
Trophies
0
Age
36
XP
2,564
Country
Australia
It would be nice if the .dB file was interchangeable between applications.... But this is be so if that happens Im not expecting it soon.
The .db file is just a dump of the binary data stored in the system save with the array size prepended. I imagine it should be relatively trivial to make hekate, TegraExplorer etc. read/write the .db file instead of the system save. Even better would be to just have a startup/shutdown script running under lakka to synchronise directly with the .db file and cut out the need to run any RCM payload altogether.
 
  • Like
Reactions: Kallim and ber71

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
The .db file is just a dump of the binary data stored in the system save with the array size prepended. I imagine it should be relatively trivial to make hekate, TegraExplorer etc. read/write the .db file instead of the system save. Even better would be to just have a startup/shutdown script running under lakka to synchronise directly with the .db file and cut out the need to run any RCM payload altogether.
I could possibly see that happening. I think it'd be far more likely if it was the default setting though. How compatible is it compared with the Hekate dump? I'm assuming you can't just rename it.
Post automatically merged:

Of course, please take a look at attachment (delete ".txt" before opening) and make sure you have updated to newest Atmosphere 1.5.1.

Edit1: For checking after apply settings, you just need to run Atmosphere with SysNAND, wait until you can access Homescreen, then Power Off and check if there is any .db file in /atmosphere folder in your SD.
Thanks it worked great. The only difference was I had the line at the very bottom and you had enable_dns_mitm = u8!0x1. You also had cheats enabled but I doubt that would affect it.

I'm pretty sure it's the dns_mitm I had it remarked out. I didn't have a system_settings.ini until now so thought this was enabled by default. I guess it's not once the file has been created.
Post automatically merged:

I could possibly see that happening. I think it'd be far more likely if it was the default setting though. How compatible is it compared with the Hekate dump? I'm assuming you can't just rename it.
Post automatically merged:


Thanks it worked great. The only difference was I had the line at the very bottom and you had enable_dns_mitm = u8!0x1. You also had cheats enabled but I doubt that would affect it.

I'm pretty sure it's the dns_mitm I had it remarked out. I didn't have a system_settings.ini until now so thought this was enabled by default. I guess it's not once the file has been created.
Luckily I also use incognito on the emunand.
 
Last edited by Kallim,

ndeadly

Well-Known Member
Member
Joined
Nov 5, 2018
Messages
460
Trophies
0
Age
36
XP
2,564
Country
Australia
I could possibly see that happening. I think it'd be far more likely if it was the default setting though. How compatible is it compared with the Hekate dump? I'm assuming you can't just rename it.
I'm not really familiar with dumping using Hekate, are you talking about the "Dump Joy-Con BT" option? I just tried that on my console and it seems it only dumps the joycons and not the other controllers. This leads me to believe that it's maybe reading the info directly from the controller memory via UART, and not actually looking at the system save.

The (.ini) format looks like this
[joycon_00]
type=1
mac=XX:XX:XX:XX:XX:XX
host=XX:XX:XX:XX:XX:XX
ltk=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
It seems to be storing pretty much the bare minimum, and nothing like the .db file. mac and ltk are present in the .db file and type could be inferred from the controller name. The host address isn't available in the .db though. That would have to be obtained separately
 
  • Like
Reactions: Kallim

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
That's the one... And I'm pretty sure it is the minimum which is why my pad didn't work in lakka so I hope "they" adopt your code.

Anyway well done. I take my hat off to you that's great work. I still think it's worth running syncfix so I hope development continues.... But if you either want to setup a switch for a noob or want to use 2 switches, other apps and SD nands this is awesome.

Changing the subject slightly I've never used the system settings ini file before. Will it accept if snd then commands (like .bat files)? I'm assuming not but I'd like DNS redirect on my sysnand but not on emunand as it affects other apps. So I set it to 0 instead of 1.

The workaround if is to have emummc.txt and sysmmc.txt as host files.... but I'd like 2nd layer of protection on the sysnand as I can't really use incognito on it. So I'd like maybe to add maybe this:

If sysnand =1 enable_dns_mitm = u8!0x1
Or possibly if sysnand=u8!0x1???


I'm assuming that won't work? And apologize if it's a stupid question. With this being a new process I just want to be extra cautious about Nintendo (maybe I'm paranoid).
 
Last edited by Kallim,

r-miheev

New Member
Newbie
Joined
Mar 23, 2023
Messages
1
Trophies
0
Age
39
XP
18
Country
Russia
Good afternoon, everyone! I apologize for my English. There was a question about using the Syncfix.te script. On the Nintendo Switch Led (Mariko), Sysnand for online games and Emunand for pirated games are configured. There was a problem using JoyCon in two systems, you have to constantly synchronize them when rebooting to different systems. I came across your topic on the use of this script by searching, I figured out everything about its use. My actions are as follows: I log into Emunand and delete the synchronized Joi-Con, then reboot into Sysnand and do the Joi-Con synchronization. Then I load into Hekate-Payloads-Tegra Explorer and select the script on the SD Card and run it. There are no errors, the script works 100%. I do a reboot in Emunand and see that ALL settings (wifi, bluetooth, system) are copied, but the settings of the synchronized Joi-Con are not transferred - I have to synchronize them manually. I tried various options, including airplane mode on one and on both systems. Nothing helps - Joi-Con noses are not transferred in any way. What else can I try to do? Thank you so much for more.
 
  • Like
Reactions: paulofloresjunior

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
Good afternoon, everyone! I apologize for my English. There was a question about using the Syncfix.te script. On the Nintendo Switch Led (Mariko), Sysnand for online games and Emunand for pirated games are configured. There was a problem using JoyCon in two systems, you have to constantly synchronize them when rebooting to different systems. I came across your topic on the use of this script by searching, I figured out everything about its use. My actions are as follows: I log into Emunand and delete the synchronized Joi-Con, then reboot into Sysnand and do the Joi-Con synchronization. Then I load into Hekate-Payloads-Tegra Explorer and select the script on the SD Card and run it. There are no errors, the script works 100%. I do a reboot in Emunand and see that ALL settings (wifi, bluetooth, system) are copied, but the settings of the synchronized Joi-Con are not transferred - I have to synchronize them manually. I tried various options, including airplane mode on one and on both systems. Nothing helps - Joi-Con noses are not transferred in any way. What else can I try to do? Thank you so much for more.
You need to delete all the controllers in the sysnand not emunand and then run syncfix.

Ignore emunand for now... Syncfix will overwrite it. Launch sysnand disconnect all controllers. This will find the joycons in sysnand. Then connect any pads headphones etc. Then launch tegra and run syncfix. That should be it.

I think the problem is you disconnected controllers in emunand. That would have connected the joycon to emunand so it wouldn't be paired with sysnand. You then overwrite that setting so it wasn't paired with any nand (both the joycon and the nand have to accept the pairing). They probably still worked attached if I'm right?
 

paulofloresjunior

New Member
Newbie
Joined
Mar 23, 2023
Messages
3
Trophies
0
Age
42
XP
49
Country
Brazil
You need to delete all the controllers in the sysnand not emunand and then run syncfix.

Ignore emunand for now... Syncfix will overwrite it. Launch sysnand disconnect all controllers. This will find the joycons in sysnand. Then connect any pads headphones etc. Then launch tegra and run syncfix. That should be it.

I think the problem is you disconnected controllers in emunand. That would have connected the joycon to emunand so it wouldn't be paired with sysnand. You then overwrite that setting so it wasn't paired with any nand (both the joycon and the nand have to accept the pairing). They probably still worked attached if I'm right?
I getting same problem here. I already tried first sync in Sysnand then run the script and first sync in emunand then run the script.

The script says the "Copying 8000000000000050 file from SYSMMC to EMUMMC" so the joycons and gamepads must be paired in sysnand to run script.

Maybe is any issue with Firmware 16.

Anyone can help?
Post automatically merged:

Good afternoon, everyone! I apologize for my English. There was a question about using the Syncfix.te script. On the Nintendo Switch Led (Mariko), Sysnand for online games and Emunand for pirated games are configured. There was a problem using JoyCon in two systems, you have to constantly synchronize them when rebooting to different systems. I came across your topic on the use of this script by searching, I figured out everything about its use. My actions are as follows: I log into Emunand and delete the synchronized Joi-Con, then reboot into Sysnand and do the Joi-Con synchronization. Then I load into Hekate-Payloads-Tegra Explorer and select the script on the SD Card and run it. There are no errors, the script works 100%. I do a reboot in Emunand and see that ALL settings (wifi, bluetooth, system) are copied, but the settings of the synchronized Joi-Con are not transferred - I have to synchronize them manually. I tried various options, including airplane mode on one and on both systems. Nothing helps - Joi-Con noses are not transferred in any way. What else can I try to do? Thank you so much for more.
I tried same thing as you but I have v1 unlocked version in firmware 16 and get same behavior.

Hoping someone can helps us.

I have two pair of joycons and 3 pro controllers. I already tried the new version of TegraExplorer "Hotfix 16.0.0" and after execute the scrip in emunand says all 7 controllers are synchronized, but no one works.
 
Last edited by paulofloresjunior,
  • Like
Reactions: r-miheev

Kallim

Well-Known Member
Member
Joined
Jan 12, 2021
Messages
291
Trophies
0
Age
47
XP
652
Country
United Kingdom
I getting same problem here. I already tried first sync in Sysnand then run the script and first sync in emunand then run the script.

The script says the "Copying 8000000000000050 file from SYSMMC to EMUMMC" so the joycons and gamepads must be paired in sysnand to run script.

Maybe is any issue with Firmware 16.

Anyone can help?
Post automatically merged:


I tried same thing as you but I have v1 unlocked version in firmware 16 and get same behavior.

Hoping someone can helps us.

I have two pair of joycons and 3 pro controllers. I already tried the new version of TegraExplorer "Hotfix 16.0.0" and after execute the scrip in emunand says all 7 controllers are synchronized, but no one works.
Are you on the latest tegra, syncfix? Also sometimes Nintendo update the bluetooth when they update so your nands may both need to be in the same fw if there's been a Bluetooth update?
 

paulofloresjunior

New Member
Newbie
Joined
Mar 23, 2023
Messages
3
Trophies
0
Age
42
XP
49
Country
Brazil
Are you on the latest tegra, syncfix? Also sometimes Nintendo update the bluetooth when they update so your nands may both need to be in the same fw if there's been a Bluetooth update?
Yes, I'm using latest TegraExplorer from github, latest syncfix.te and both nands are at same version 16.0.1. One year ago I used the syncfix with success, at the time I remember to face some issue but after update TegraExplorer it worked fine.

Now I don't have any clue what is going wrong
 

hartleyshc

Well-Known Member
Member
Joined
Oct 2, 2008
Messages
512
Trophies
2
Age
42
Location
Gainesville, FL
XP
1,419
Country
United States
Yes, I'm using latest TegraExplorer from github, latest syncfix.te and both nands are at same version 16.0.1. One year ago I used the syncfix with success, at the time I remember to face some issue but after update TegraExplorer it worked fine.

Now I don't have any clue what is going wrong
I think you're correct.
I used the script in the past as well and didnt have any issues. Recently paired my joycons on another switch and messed up the syncing.
Went to run the script again and I am getting the same issue as you. It says it succeeded, but the files aren't synced. Or I should say that the files are synced (I've deleted and watched them be copied over), but it doesn't allow the pairings from sys to emu to work as they should. Fairly sure its an issue with everything that was updated under the hood in fw 16+, but I couldnt find enough info on the Reswitched discord or the switchbrew wiki. (I didn't ask, just searched for info).

Edit: FIXED: In my case it was having the bluetooth db setting enabled in Atmosphere. Even though I was killing the actual save file, the db kept restoring the old bluetooth info. Deleted db, and then commented out enabling the feature in system_settings. Rebooted and ran the script again. Issue resolved.
 
Last edited by hartleyshc,

paulofloresjunior

New Member
Newbie
Joined
Mar 23, 2023
Messages
3
Trophies
0
Age
42
XP
49
Country
Brazil
I think you're correct.
I used the script in the past as well and didnt have any issues. Recently paired my joycons on another switch and messed up the syncing.
Went to run the script again and I am getting the same issue as you. It says it succeeded, but the files aren't synced. Or I should say that the files are synced (I've deleted and watched them be copied over), but it doesn't allow the pairings from sys to emu to work as they should. Fairly sure its an issue with everything that was updated under the hood in fw 16+, but I couldnt find enough info on the Reswitched discord or the switchbrew wiki. (I didn't ask, just searched for info).

Edit: FIXED: In my case it was having the bluetooth db setting enabled in Atmosphere. Even though I was killing the actual save file, the db kept restoring the old bluetooth info. Deleted db, and then commented out enabling the feature in system_settings. Rebooted and ran the script again. Issue resolved.
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
 
  • Like
Reactions: Blythe93

reirahul

Active Member
Newcomer
Joined
Oct 3, 2022
Messages
33
Trophies
0
Age
30
Location
Florida
XP
401
Country
United States
I added the line enable_external_bluetooth_db = u8!0x1. into atmosphere config and I then run the script and its now working just fine but I couldn't find "/atmosphere/bluetooth_devices.db" anywhere on my sd card? Should I be worried? also I happened to have incognito on my emunand and a clean cfw sysand, so nothing happened to sysnand right?
Post automatically merged:

also How to produce this file "bluetooth_devices.db" if it not there if I want to use the pairing on multiple switches?
 
Last edited by reirahul,

ndeadly

Well-Known Member
Member
Joined
Nov 5, 2018
Messages
460
Trophies
0
Age
36
XP
2,564
Country
Australia
I added the line enable_external_bluetooth_db = u8!0x1. into atmosphere config and I then run the script and its now working just fine but I couldn't find "/atmosphere/bluetooth_devices.db" anywhere on my sd card? Should I be worried? also I happened to have incognito on my emunand and a clean cfw sysand, so nothing happened to sysnand right?
Post automatically merged:

also How to produce this file "bluetooth_devices.db" if it not there if I want to use the pairing on multiple switches?
If the file isn't being created then either you haven't configured the ini file correctly, or you're not booting cfw. When it's working correctly it will dump your current pairings on boot if the file isn't there.

You can copy the file to other switches if you want to use the pairings on multiple consoles, but you will also need to use Mission Control to spoof the host address of the original console that the controllers paired with.
 
  • Like
Reactions: reirahul

reirahul

Active Member
Newcomer
Joined
Oct 3, 2022
Messages
33
Trophies
0
Age
30
Location
Florida
XP
401
Country
United States
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?
 

Attachments

  • system_settings.txt
    3.8 KB · Views: 23

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
  • Veho @ Veho:
    The fuuuuu---
  • Veho @ Veho:
    I thought it was an actual xBox at that price.
  • Sicklyboy @ Sicklyboy:
    I wanna grab a 360 Slim and a 360 E one of these days. Missed the boat of getting them at their lowest though, once they were discontinued. Could've got them for cheap back when I was a broke 20 something working at Target, but then again, I was a broke 20 something working at Target
  • Veho @ Veho:
    Being broke is no fun.
  • K3Nv2 @ K3Nv2:
    @Sicklyboy, $150 isn't that bad for a jtag slim on ebay
  • Veho @ Veho:
    I only wish it was actually playable.
  • Veho @ Veho:
    There's a guy on the Tube of You that makes playable mechanical arcade games out of Lego. This could work on the same principle.
  • Veho @ Veho:
    Just a couple of guys taking their manatee out for some fresh air, why you have to molest them?
  • Veho @ Veho:
    Stupid Chinese shop switched their shipping company and this one is slooooooow.
  • LeoTCK @ LeoTCK:
    STOP BUYING CHINESE CRAP THEN
  • LeoTCK @ LeoTCK:
    SUPPORT LOCAL PRODUCTS, MAKE REVOLUTION
  • LeoTCK @ LeoTCK:
    THEY KEEP REMOVING LOCAL SHIt AND REPLACING WItH INFERIOR CHINESE CRAP
  • LeoTCK @ LeoTCK:
    THATS WHY MY PARTNER CANT GET A GOOTWEAR HIS SIZE ANYMORE
  • LeoTCK @ LeoTCK:
    HE HAS BIG FOOT AND BIG DUCK
  • LeoTCK @ LeoTCK:
    d*ck i mean*
  • LeoTCK @ LeoTCK:
    lol
  • Veho @ Veho:
    Mkay.
  • Veho @ Veho:
    I just ordered another package from China just to spite you.
  • SylverReZ @ SylverReZ:
    Communism lol
  • SylverReZ @ SylverReZ:
    OUR products
  • The Real Jdbye @ The Real Jdbye:
    @LeoTCK actually good quality products are dying out because they can't compete with dropshipped chinese crap
    +1
    The Real Jdbye @ The Real Jdbye: @LeoTCK actually good quality products are dying out because they can't compete with dropshipped... +1