Hacking SXOS Emu Question

  • Thread starter Thread starter runetoonxx2
  • Start date Start date
  • Views Views 2,403
  • Replies Replies 15
Is better to always unlink your Nands.

Now depends on what you have or you want.

If you already have a sysnand with XCI, and NSPs installed, and you wanna keep your emunand with that and clean your sysnand, then format your sysnand and keep emunand intact (Thats what Im using)
 
Unlinking nands is not needed with the switch sx emunand. It uses another folder called emutendo instead of using the nintendo folder sysnand uses. That way they don't conflict with each other like it used to happen on the 3ds.
 
Last edited by JJTapia19,
Unlinking nands is not needed with the switch sx emunand. It uses another folder called emutendo instead of using the nintendo folder sysnand uses. That way they don't conflict with each other like it used to happen on the 3ds.
This is actually true, but if you dont format one of the Nands, then you have a copy of everything in boths Nands
 
This is actually true, but if you dont format one of the Nands, then you have a copy of everything in boths Nands
Yeah. The only downside of formating one of the nands is that you'll have to pair the controllers each time you switch from one to another. It can be avoided by manually deleting the copied unwanted games instead of formating.
 
as per above.. I change my theme and have a new user named ''EMU'' so I can see at a glance whether I am in emu or sysNAND.
 
I hear of bugs on emunand when booting sx os 2.6.1, anyone experience it?
Yeah I have low boot rate on mine. It takes me up to 5 times to boot it. Some are saying that if you create a new emunand using 2.6.1 it works. I'll try it out if a fix doesn't come soon.
 
Yeah I have low boot rate on mine. It takes me up to 5 times to boot it. Some are saying that if you create a new emunand using 2.6.1 it works. I'll try it out if a fix doesn't come soon.
5 times sounds crazy, might be finger prints on the microsd if you took it out to copy files
 
5 times sounds crazy, might be finger prints on the microsd if you took it out to copy files
Just tried cleaning it. First boot was successful. Three boots after just got a black screen sometimes after the nintendo logo and sometimes the nintendo logo did not even showed up. The fifth time it booted up correctly. This test were all one after another with the exact same setup and without removing the sd card. Sd card is 200gb sandisk fat32 class10 A1 and to inject the payload I used the rcmloader dongle. I never had this problems until the 2.6 update.:(
 
Just tried cleaning it. First boot was successful. Three boots after just got a black screen sometimes after the nintendo logo and sometimes the nintendo logo did not even showed up. The fifth time it booted up correctly. This test were all one after another with the exact same setup and without removing the sd card. Sd card is 200gb sandisk fat32 class10 A1 and to inject the payload I used the rcmloader dongle. I never had this problems until the 2.6 update.:(
seems a minority of people is having some kind of problems, it could be microsd related or corrupted files
so far, it's booting 100% for me since 2.6 day1 on average 5 boots per day
 
seems a minority of people is having some kind of problems, it could be microsd related or corrupted files
so far, it's booting 100% for me since 2.6 day1 on average 5 boots per day
Yeah I'll backup my files and reformat again. I'll let you know if it works.
 
  • Like
Reactions: dsrules
seems a minority of people is having some kind of problems, it could be microsd related or corrupted files
so far, it's booting 100% for me since 2.6 day1 on average 5 boots per day
Turns out my SD was the problem and formatting it worked! I thought that by already being on fat32 that couldn't be the problem but formatting it again and bringing the files back seems to have fixed my emunand boot rate issue completely. Thanks for everything.
 
  • Like
Reactions: gizmomelb
Turns out my SD was the problem and formatting it worked! I thought that by already being on fat32 that couldn't be the problem but formatting it again and bringing the files back seems to have fixed my emunand boot rate issue completely. Thanks for everything.
glad to hear that you got it sorted out and Thanks for the update.
 
  • Like
Reactions: JJTapia19

Site & Scene News

Popular threads in this forum