Xenoblades Chronicles X Crash ?

[manmaro]

yup here we go, converting the xci with NSC_builder worked, im on 1.0.1 now aswell, cheers everyone

 

[Deleted member 702243]

morons sharing converted update files online when extracting the untouched signed update from the xci is so trivial is actually funny

 

[Blythe93]

Is there any valid reason to release converted NSPs along with the original XCIs? DBI can handle them just fine or, at the very least, I never had any issue so far.
I do see a point in NSZ and XCZ, but those converted NSPs are kinda redundant as far as I know.

 

[aleher86]

Now is working. But what I don't understand is why the xci file with the 1.0.1 update installed with DBI doesn't work, but converted to nsp format with NSC Builder it works. It's a mystery for me. The important thing is that it already worked for me and this may be a solution for those who still have problems.

 

[Trainer96]

So this converter creates only 1 NSP file?
When I used SAK it created the base game NSP and the update NSP.

Edit: Hooolyyyy, this did it for me!!
Converted the XCI file to a single NSP file using NSC_Builder, had to watch a quick tutorial on how to use it.

The game start screen shows 1.0.1!!

What I've read about NSC_Builder is that it can remove title rights and I think that's the error with the NSP update that we all downloaded from different sources.

I've tried everything, sys-patch 1.5.6
Atmos+Hekate up to date, 19.0.1 switch and nothing worked, 6-7 days of troubleshooting later and now it works.


Thank you!

Do you need prod.key to use nsc builder? Lockpick github is down so i can't get keys.txt

 

[Rodddd]

Do you need prod.key to use nsc builder? Lockpick github is down so i can't get keys.txt

Yes, you need to rename the prod.keys (you can Google it) file to keys.txt on the folder that the instructions mention

 

[Trainer96]

Yes, you need to rename the prod.keys (you can Google it) file to keys.txt on the folder that the instructions mention

oh, i thought u need to extract it yourself. Trying with prod.keys i found online now, hope it work

Update: It works! Thanks you for the tips

 

[Fedeuy]

Hello everyone, im trying to convert the xci file to ncp using NSC builder, with my dumped product keys, but im running into a very weird error, the file just wont get processed, i add it to the list, select my options, and nothing, the software just says that 0 files were processed.

 

[javitox5000]

Hello everyone, im trying to convert the xci file to ncp using NSC builder, with my dumped product keys, but im running into a very weird error, the file just wont get processed, i add it to the list, select my options, and nothing, the software just says that 0 files were processed.

You got a bad dump. Try getting a different one it solved the problem for me.

 

[Fedeuy]

You got a bad dump. Try getting a different one it solved the problem for me.

I did get a new one, and i was able to move a step forward, now i get a list index error after processing

 

[shinraphen]

Seems to be something a select few of us have in common regarding not being able to launch this no matter what we do. My NSP file works just fine on Ryujinx emulator but not on the Switch itself despite having a clean atmosphere and switch folder, and the right sigpatches and syspatch files. Might be some interference from somewhere no one's been able to pinpoint yet

Post automatically merged: Mar 19, 2025

Ok guys I figured it out for myself personally. I had to update my emummc firmware to 18.0.0 using daybreak and it ended up working on the already installed updateless NSP of Xenoblade X. I believe the firmware I was on before was too old to support the game, when usually you can be pretty far back in firmware to run most new games

Post automatically merged: Mar 19, 2025

When updating on the system itself I usually do it through syscfw, and when emummc was still able to work after reboot I forgot that it didn't update since it is a separate instance. I'm definitely going to try to remember this from here on in!

Post automatically merged: Mar 20, 2025

Finally, to get it working with update 1.0.1 you need the absolute latest switch firmware on your emummc (19.0.1) downloaded through daybreak. And for anyone interested in cheats I'm using Ultrahand Overlay and the updated Edizon Overlay linked in the post by impeeza in the Tesla thread on here. (Wish I could link it but Im not allowed to)

could you dm me the link?

 

[Rewinding]

Is NSC Builder the same as Switch Army Knife?

 

[Rodddd]

Is NSC Builder the same as Switch Army Knife?

No. I used SAK first but created 2 NSP files, one for the base game and the other for the update.
NSC_Builder let's you convert a XCI into a single NSP that includes the base game and update.

 

[Rewinding]

No. I used SAK first but created 2 NSP files, one for the base game and the other for the update.
NSC_Builder let's you convert a XCI into a single NSP that includes the base game and update.

I was able to open up NSC bUilder. Which option do I need to pick to convert the xci? Is it "input 2= multi pack mode?
Thanks
Edit: Nvm, I can't use the program... my PC is old. I guess I'm gonna have to play the game without the patch then

 

[darkpyro7860]

could you dm me the link?

Can't dm links either bro, you can add me on discord though, same name as here minus the 0 at the end

 

[ninjastarforcex]

I'm too illiterate to use NSC-Builder
haaaa
I guess I'll stick to 1.0.0

 

[Rodddd]

I'm too illiterate to use NSC-Builder
haaaa
I guess I'll stick to 1.0.0

There are YT tutorials, the GitHub also provides a lot of info

 

[blaww]

Sorry if off topic, but has anyone tried using the physical cartridge version? I was initially on FW 19.0 and the cart said an update is required, so I updated to 19.0.1. Now I get the same "software was closed because of an error" message. I've updated sigpatches, sys-patch, etc. with no luck.

Interestingly, the cartridge comes bundled with the 1.0.1 update that's giving everyone trouble, and I can dump the 1.0.0 NSP, install it, and launch the game fine. I just can't play it from the cartridge. Could the 1.0.1 version have updated something that's incompatible with current sigpatches?

I've been out of the loop for a long time and try not to update things unless I absolutely have to, for this reason.

 

[Endlessfate]

Sorry if off topic, but has anyone tried using the physical cartridge version? I was initially on FW 19.0 and the cart said an update is required, so I updated to 19.0.1. Now I get the same "software was closed because of an error" message. I've updated sigpatches, sys-patch, etc. with no luck.

Interestingly, the cartridge comes bundled with the 1.0.1 update that's giving everyone trouble, and I can dump the 1.0.0 NSP, install it, and launch the game fine. I just can't play it from the cartridge. Could the 1.0.1 version have updated something that's incompatible with current sigpatches?

I've been out of the loop for a long time and try not to update things unless I absolutely have to, for this reason.

Long story short (as someone who spent 20hrs trying to do tech stuff on my hacked switch) the 1.9.1 firmware pair with tinfoil bs is cancer, I would honestly avoid 1.9.1 at all costs… im on day 4 and at the final stretch

all I need now is a save file around ch 3/4/5/ (I’m not picky long as it’s a save that someone actually cared for and isn’t overleveled) as my save file is gone so I’m SoL looking online… I did find one thing on here but lv 43 on ch 456? And barely any care on finding probes/sidequests/etc? Pain

 

[ninjastarforcex]

Sorry if off topic, but has anyone tried using the physical cartridge version? I was initially on FW 19.0 and the cart said an update is required, so I updated to 19.0.1. Now I get the same "software was closed because of an error" message. I've updated sigpatches, sys-patch, etc. with no luck.

Interestingly, the cartridge comes bundled with the 1.0.1 update that's giving everyone trouble, and I can dump the 1.0.0 NSP, install it, and launch the game fine. I just can't play it from the cartridge. Could the 1.0.1 version have updated something that's incompatible with current sigpatches?

I've been out of the loop for a long time and try not to update things unless I absolutely have to, for this reason.

same problem. someone said I have to convert xci with NSC Builder, but python stuff is overwhelming, I really can't into software stuff

can someone PM me link to a working 1.0.1 NSP? I'm really tired of trying out methods where none worked...


---

I tried using a different XCI (Base + 1.0.1) (didn't work) then converted that to single file NSP (Base +1.0.1) and now it worked.
I used NSC Builder