ROM Hack RELEASE NSC_Builder. Nintendo Switch Cleaner and Builder. (Game+updates+dlc in a single xci)

  • Thread starter JRoad
  • Start date
  • Views 724,819
  • Replies 2,824
  • Likes 74

pcwizard7

Well-Known Member
Member
Joined
Aug 2, 2013
Messages
1,409
Trophies
0
XP
1,688
Country
Australia
The thing there is that I would need to see those tickets. Basically I have to support 2 offsets for the keygeneration on tickets since some programs dumped it incorrectly before. Some dumps deviating from the standards format of tickets doesn't help there I guess but as I said I would need to see those tickets. Are you using the last version? I added something before to be able to support both offsets and some nxdumptool dumps that deviated from the standard dump format.
Basically I would need to see the ticket myself if someone made more changes on it because I don't have access to any dump that doesn't have the standard scene format.
Other way would be to ignore the ticket completely and trust the key is encrypted with the same masterkey as the nca headers which should be true. Alternatively I could make it pass a key verification check and force standardize the ticket to avoid issues.
One issue here is that I don't have time lately but I should at least release something this weekend since I added the RSV for 9.2.0 in the beta and well I also added the ability to show info for xc0, ns0 and 00 splitter files in the interface though is still missing the verification stuff. I'll probably add an option to ignore the ticket keygeneration check.
dd

I ve re dump the games again and come to the conclusion that they won't dump correct and file corruption

But running file verify each file for the new dlc, and they all check out except it couldn't verify the ticket even tho I could create a custom xci with them. So u may need to update them

if you want to check them here are the dlc in question

Code:
Xenoblade Chronicles 2 v0 (0100E95004039006) (DLC)
Xenoblade Chronicles 2 v131072 (0100E95004039001) (DLC)
Xenoblade Chronicles 2 v196608 (0100E95004039004) (DLC)
Xenoblade Chronicles 2 v327680 (0100E95004039002) (DLC)
Xenoblade Chronicles 2 v327680 (0100E95004039003) (DLC)
Xenoblade Chronicles 2 v720896 (0100E95004039005) (DLC)
 

markmcrobie

Well-Known Member
Member
Joined
May 24, 2008
Messages
623
Trophies
0
XP
1,247
@JRoad

I'm getting more and more of these type of errors when trying to incorporate updates into XCI files. I have verified all keys, I have up to and including Masterkey 10.

Code:
Exception: Failed to decrypt NCA header: b'\x86\x10\xe8\x85'
        G:\games\FM20 Touch [0100DA500EFB0000] [v65536] (1G+1U).xci
Exception: Failed to decrypt NCA header: b'\x0b\xe9\xdan'
        G:\games\Pine [01002BA00D662000] [v327680] (1G+1U).xci

See also post #2186
 
Last edited by markmcrobie,

JRoad

Developer
OP
Developer
Joined
May 18, 2018
Messages
1,003
Trophies
0
XP
1,746
Country
Spain
dd

I ve re dump the games again and come to the conclusion that they won't dump correct and file corruption

But running file verify each file for the new dlc, and they all check out except it couldn't verify the ticket even tho I could create a custom xci with them. So u may need to update them

if you want to check them here are the dlc in question

Code:
Xenoblade Chronicles 2 v0 (0100E95004039006) (DLC)
Xenoblade Chronicles 2 v131072 (0100E95004039001) (DLC)
Xenoblade Chronicles 2 v196608 (0100E95004039004) (DLC)
Xenoblade Chronicles 2 v327680 (0100E95004039002) (DLC)
Xenoblade Chronicles 2 v327680 (0100E95004039003) (DLC)
Xenoblade Chronicles 2 v720896 (0100E95004039005) (DLC)
Those are keygeneration 2 I think the fix I had to do for the nxdumptool thing may be influencing those since keygeneration 2 is different than the others. A slightly order version should not present that issue.
@JRoad

I'm getting more and more of these type of errors when trying to incorporate updates into XCI files. I have verified all keys, I have up to and including Masterkey 10.

Code:
Exception: Failed to decrypt NCA header: b'\x86\x10\xe8\x85'
        G:\games\FM20 Touch [0100DA500EFB0000] [v65536] (1G+1U).xci
Exception: Failed to decrypt NCA header: b'\x0b\xe9\xdan'
        G:\games\Pine [01002BA00D662000] [v327680] (1G+1U).xci

See also post #2186
The header key is independent of the keygeneration. Is what's used to read the ncaheader so you can read the keygeneration. Are you sure those files are actually ok?
By using that key the first bytes read on each nca should be NCA3, if that doesn't happen you know the file is bad or corrupted. The decryption shouldn't fail with that.
 

pcwizard7

Well-Known Member
Member
Joined
Aug 2, 2013
Messages
1,409
Trophies
0
XP
1,688
Country
Australia
does sxos have the masterkey issue for 9.1 or latest one as it couldn't read my custom pokemon sword v1.1.1 xci file and i just patch the keygen for 9.0.0 fw and it worked and it could read it
 

JRoad

Developer
OP
Developer
Joined
May 18, 2018
Messages
1,003
Trophies
0
XP
1,746
Country
Spain
does sxos have the masterkey issue for 9.1 or latest one as it couldn't read my custom pokemon sword v1.1.1 xci file and i just patch the keygen for 9.0.0 fw and it worked and it could read it
Dunno, I didn't update to be honest and I've had mine on autopatch for a while or set them with the autoloader. As far as I remember cartridges did mount even if they didn't show the icon. I guess I can update and check this weekend.
 

pcwizard7

Well-Known Member
Member
Joined
Aug 2, 2013
Messages
1,409
Trophies
0
XP
1,688
Country
Australia
Dunno, I didn't update to be honest and I've had mine on autopatch for a while or set them with the autoloader. As far as I remember cartridges did mount even if they didn't show the icon. I guess I can update and check this weekend.

It doesn't show the icon if the filename has a character it shouldn't be able to and you just rename it. dragon quest 11 was the first to show this

the error where it can't read a xci was when sxos it had bug where it couldn't read the latest masterkey (keygen) and i was wondering if the case for latest one atm (9.1)

I know there have been update files for games that up the requirement as well
 

JRoad

Developer
OP
Developer
Joined
May 18, 2018
Messages
1,003
Trophies
0
XP
1,746
Country
Spain
It doesn't show the icon if the filename has a character it shouldn't be able to and you just rename it. dragon quest 11 was the first to show this

the error where it can't read a xci was when sxos it had bug where it couldn't read the latest masterkey (keygen) and i was wondering if the case for latest one atm (9.1)

I know there have been update files for games that up the requirement as well
Yeah, I meant white icon. I'm aware of that error, I think I put it on the changelog of one release, though they claimed they fixed it, I think, but I heard both versions. I myself I'm still on FW9.0 mostly because I haven't been playing much with the switch these days.
There are updates with the latest keygeneration like Murder by numbers but I didn't check it yet on the switch. I'm mostly playing with my PC these days.
Anyway my idea was to make a new release on the weekend so I'll check that out and issue a warning if they made the same mistake with master_key_10 (0a)\keygeneration 11 (0b)
 

JRoad

Developer
OP
Developer
Joined
May 18, 2018
Messages
1,003
Trophies
0
XP
1,746
Country
Spain
New locations for the db. I'm thinking about adding a method to update them automatically when needed, warning the user to change back their parameters. Trying to keep them would be a pain.
 

Attachments

  • NUT_DB_REGIONS_URL_MIRROR.txt
    3.8 KB · Views: 215
  • NUT_DB_URL.txt
    671 bytes · Views: 264
  • NUT_DB_URL_mirror.txt
    708 bytes · Views: 225
  • NUT_DB_REGIONS_URL.txt
    3.5 KB · Views: 188
  • Like
Reactions: aionbr and Moko

JRoad

Developer
OP
Developer
Joined
May 18, 2018
Messages
1,003
Trophies
0
XP
1,746
Country
Spain
anyone have any luck converting kentucky route zero to xci from nsp?
My patched one is working fine. It's base+update patched to keygeneration 9.
Base was keygeneration 10 and update keygeneration 11. As i said before i didn't update yet to 9.2 but i imagine it's the same issue as @pcwizard7 .Pending confirmation on my part i'd assume sx os has an issue with keygeneration 11 and start patching the xci to keygeneration 10 or 9.
My system is still on FW 9.0 btw.
 
Last edited by JRoad,
D

Deleted User

Guest
My patched one is working fine. It's base+update patched to keygeneration 9.
Base was keygeneration 10 and update keygeneration 11. As i said before i didn't update yet to 9.2 but i imagine it's the same issue as @pcwizard7 .Pending confirmation on my part i'd assume sx os has an issue with keygeneration 11 and start patching the xci to keygeneration 10 or 9.
My system is still on FW 9.0 btw.

Makes perfect sense le game de le cat and le mouse continues. Thanks for the info!
 

JRoad

Developer
OP
Developer
Joined
May 18, 2018
Messages
1,003
Trophies
0
XP
1,746
Country
Spain
Is there a way to get the new 11 keys (0B) or do we have to wait for a Lockpick RCM update?
There's not 0b key. 0b means keygeneration 11, the keay is the 0a key (masterkey10 or masterkey 0a)
Remember that keygeneration is normally masterkey +1. So since the files work in hex we'll have.
decimal hexadecimal hexadecimal
keygeneration 10 -> keygeneration 0a -> master_key_09
keygeneration 11 -> keygeneration 0b -> master_key_0a
keygeneration 12 -> keygeneration 0c -> master_key_0b
keygeneration 13 -> keygeneration 0d -> master_key_0c
keygeneration 14 -> keygeneration 0e -> master_key_0d
keygeneration 15 -> keygeneration 0f -> master_key_0e
keygeneration 16 -> keygeneration 10 -> master_key_0f
keygeneration 17 -> keygeneration 11 -> master_key_10

So at 16\17 things may get a little confusing, if we reach those numbers.

I only had to update the RSV for verification of future files that have been patched. Is currently on the beta. Since all the things i wanted to add in 0.99 aren't ready i may do a prerelease tomorrow.
 
Last edited by JRoad,
  • Like
Reactions: 18Phoenix

JRoad

Developer
OP
Developer
Joined
May 18, 2018
Messages
1,003
Trophies
0
XP
1,746
Country
Spain
@JRoad any idea about this error?

Code:
G:\games\DRAGON BALL FighterZ [0100A250097F0000] [v524288] (1G+1U+31D).xci
Exception: Not a valid PFS0 partition b'{\n "'
you're adding new files? did you verify the new files you're adding. It normally means the nsp header is blank. A nsp needs to start by the bytes equivalent to 'PFS0'. Like this :
pfs0.PNG

You can check with a Hex Editor like HxD. There are also internal PFS0s in the nca files but that error sounds like the nsp header is blank due to the dumping interrumping in the middle, since some tools write the nsp header at the end of the process.
Basically PFS0 is 50465330
 

markmcrobie

Well-Known Member
Member
Joined
May 24, 2008
Messages
623
Trophies
0
XP
1,247
@JRoad got this error trying to incorporate ACNH patch into main XCI:

Code:
Filename: Animal Crossing New Horizons [01006F8002326000] [v0].xci
Exception: object of type 'NoneType' has no len()
 

Puppydogpals

Well-Known Member
Member
Joined
Feb 19, 2018
Messages
193
Trophies
0
Age
43
XP
1,424
Country
United Kingdom
Got a lot of time on my hands at the moment, so thought of converting all my games to NSZ and XCZ using 0.98 to save storage space

Couple of questions.

1. Is it safe to do it... will it can it break any games.

2. Am I better off converting xci-nsp-nsz or would xci-xcz be same file size result.

I use primarily use xci files but the time to takes to convert from file to file does not bother me

Sent from my SM-G965F using Tapatalk
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    LeoTCK @ LeoTCK: hmm