Hacking Discussion SX OS - Error and Solutions Thread

  • Thread starter Thread starter OhhSheetz
  • Start date Start date
  • Views Views 256,003
  • Replies Replies 807
  • Likes Likes 20

Have you checked that your SD card Isn't Fake

  • Yes

    Votes: 195 76.2%
  • No

    Votes: 48 18.8%
  • Will verify soon

    Votes: 13 5.1%

  • Total voters
    256
Thank you. Got one more question: should I do anything regarding the fuses? The last update I did was without burning fuses. Is there any reason to apply the update process in a way (is that even possible?) not to burn fuses? Thanks!
I personally never bothered with that so my information could be outdated. But afaik if you want to play legit games online you have to boot normally which will always burn the fuses to match the firmware.
So either you play online or you keep your fuses. At least with sxos.

Atmosphere recently released an update that lets you make an emunand too. I heard of some people making two emunands with it. One for hacking and one of playing online with the latest firmware, all while keeping their sysnand with low firmware + no burned fuses. rn I heard it's still unstable, so you should wait for the fix (which usually comes pretty quick)! Also since it is so new I also would personally wait a bit to see if using it online leads to a ban.
 
I just got a upgraded eMMC memory to 128GB, but that has changed my Console Fingerprint it would seem.
Is there any way to transfer my license or should I just get a new one?

Cheers.
How you did that? Where i can get compatible eMMC?
 
I updated SXOS to 2.8 beta that has support for 8.1.0 supposedly, Updated firmware to 8.1.0 and it boots to switch splash, then crashes, any suggestions?
 
Hello, first timer here, so I have encountered a problem where the update data is not integrating with my xci
in particular the xci i am using is azure striker gunvolt striker pack, so I installed the update via the sx installer and I mount the xci,
in the switch menu it now shows the game with the game card icon and a duplicate with the cloud icon.
Could anybody figure out how to fix this?

I am currently using sx os v2.8 beta
where my emunand is on firmware 8.1.0


edit: Solved! If anyone encounters this problem, it means the xci and update/dlc regions are not the same.
 
Last edited by eatmycoconut,
I switched to SX OS 2.8 Beta and updated my firmware to v8.1.0. Everything was working great...... other than having to reinstall practically all my NSP's (due to some SX OS bug?!) but oh wells. So then, I copied a single, new NSP file to my exFAT SD card and booted SX OS and when I went into the album, my Switched crashed. I forget the error code but after a few attempts and not being able to launch the album (so I can install my new NSP), I went into HBG and while it was scanning the SD card, I got an error about 'Invalid NCA magic'. I removed the newly copied over NSP and then, I was able to get into the album to run homebrew again via SX OS.

I grabbed the NSP from that dark site..... wondering if the dump was bad or is there some weird bug with SX OS 2.8 in conjunction with fw 8.1.0 that is giving that 'invalid NCA magic' error? When I get home, I'm going to grab another random NSP file and see if I can reproduce the problem.

Speaking of problems.... has T-X ever figured out why people like me needed to reinstall pretty much all of our NSPs after updating? I've always installed all of my NSPs with SX OS.
 
Today I tried to boot into the boot menu (power - vol +) and it just loads straight into the nintendo firmware. It was working fine last time i used it (probably a couple weeks back).
I've tried with dongle (autorcm was on) and dongle + jig and neither works. It always just loads straight into ofw. I've tried a fresh boot.dat and no luck as well. I'm on 8.1.0 (on a non patched switch). Not sure if it makes any difference, but I did have emunand set up (though I appear to be booting into regular nand). Also worth noting that my microsd card is using exFAT. Any ideas what's going on?
 
Today I tried to boot into the boot menu (power - vol +) and it just loads straight into the nintendo firmware. It was working fine last time i used it (probably a couple weeks back).
I've tried with dongle (autorcm was on) and dongle + jig and neither works. It always just loads straight into ofw. I've tried a fresh boot.dat and no luck as well. I'm on 8.1.0 (on a non patched switch). Not sure if it makes any difference, but I did have emunand set up (though I appear to be booting into regular nand). Also worth noting that my microsd card is using exFAT. Any ideas what's going on?
You hold Vol +?
 
Seems as though it was related to the card being exFAT and not FAT32. I tried a second SD card, formatted it to fat32 and it worked. Reformatted it to exFAT and it stopped working. Formatted it to fat32 once again and it worked again.
 
Seems as though it was related to the card being exFAT and not FAT32. I tried a second SD card, formatted it to fat32 and it worked. Reformatted it to exFAT and it stopped working. Formatted it to fat32 once again and it worked again.
Maybe you have updated your console with ChoiDujourNX but didn't choose the exFAT option during the installation?
 
Hello guys. Anyone having a problem with nsps files after the last update?
I have 2 nsp files that I just downloaded and I can’t find them on my switch.
I’m doing everything that I usually do. This started after the last update.
Does anyone have any clue on what is happening?
Thank you so much!
 
Hello guys. Anyone having a problem with nsps files after the last update?
I have 2 nsp files that I just downloaded and I can’t find them on my switch.
I’m doing everything that I usually do. This started after the last update.
Does anyone have any clue on what is happening?
Thank you so much!

Is it named weird? maybe rename to something short like if its mario odyssey to marioOD
are you on the latest firmware 9?
 
My Switch keeps crashing on OFW 9.0.1/SX 2.9.2, no matter what games I play. The length of play time before it crashes varies, but it always inevitably happens. No error code or anything. Just tells me to press the power key to reboot.
 
I hadn't read the patch notes so I was PLEASANTLY SURPRISED when I was able to reboot straight to SX OS after a crash for the first time and yes....I know this feature probably has existed for a year or more on other solutions.
 
I hadn't read the patch notes so I was PLEASANTLY SURPRISED when I was able to reboot straight to SX OS after a crash for the first time and yes....I know this feature probably has existed for a year or more on other solutions.

Not that I'm aware of.
 
Was trying to update to 9.0.1 via choi and got this right before it finished update and now the switch seems loke its soft bricked

How do I go about fixing this?
Cant seem to boot into sx or horizon


Someone mentioned booting into atmos ?

81b50ae4ceb5d675a44d9831e23db72a.jpg


Sent from my SM-G965U using Tapatalk
 

Site & Scene News

Popular threads in this forum