Do a verify in the files you're using. UNKNOWN content seems weird. You can find the verify in both individual mode and info mode. Individual mode is to check several files in one go.*******************************************************
Processing list mlist.txt
*******************************************************
Calculating final content:
Exception: read returned empty 0x1c8b38ea0
Exception: read returned empty 0x1e2a48a0
Filename: UNKNOWN [] .xci
Exception: read returned empty 0x1c8b38ea0
Exception: read returned empty 0x1e2a48a0
- Writing XCI header...
- Writing XCI game info...
- Generating padding...
- Writing XCI certificate...
- Writing ROOT HFS0 header...
- Writing UPDATE partition header...
Calculated multiplier: 1
- Writing NORMAL partition header...
Calculated multiplier: 1
- Writing SECURE partition header...
Calculated multiplier: 1
99%|████████████████████████████████████████████████████████████████████████████▍| 63.0k/63.5k [00:00<00:00, 2.26MB/s]Exception: read returned empty 0x1c8b38ea0
Exception: read returned empty 0x1e2a48a0
...................................................
STILL 0 FILES TO PROCESS
...................................................
What am I doing wrong?
There are many games that doesn't run under lower firmware but my bet is you have a bad nsp. I know that there was a "My friend Pedro" floating around from a scene group that had a bad titlekey, if you generate a xci with that NSCB will generate a wrong header.When I launch My Friend Pedro cxci it crashes after few seconds with message "Software was closed because an error occured". I'm using FW 7.0.1 with SXOS 2.6.2. Game was converted to cxci with latest version of NSB, keygeneration was changed from 8 to 7. Do you think it's NSB problem or is this a special game that won't run on lower FW like Hellblade?
There are many games that doesn't run under lower firmware but my bet is you have a bad nsp. I know that there was a "My friend Pedro" floating around from a scene group that had a bad titlekey, if you generate a xci with that NSCB will generate a wrong header.
Is easy to know, just use the verifier i introduced recently with the original nsp or xci. The original nsp should say the ticket is bad, the xci should fail the first verification on the program nca.
That assuming that you have the bad file. Either way 7.01-8.01 is keygeneration8\master_key_07 so it should run on that firmware and 8.1 is keygeneration9\master_key_08
Did you verify the files with NSCB? It would be good to know if the original files and the result verify properly.A possible bug:
Packing Bomberman R and its update (01007AD00013E000 + 01007AD00013E800) together produces a broken xci, or at least one that can crash XCI-Explorer.
Please look into it.
No, I didn't see it necessary when there's Kefir and before that there was the import account method via a save file. Yes, i know that you loose the unlink accounts and saves, but you can backup the saves and add them to the new account.Is there anyway to remove nintendo link account with this tool
Yes, i can see about adding an option in advance to inject and extract the certs. I can make it so it let you inject the same cert to all games in the list, with a warning about online play and injected certs. I know they work but at the very least it seems that injecting the same one to a ton of games ends in a ban.Thank you so much for making this tool.
Just one suggestion, if you have time, can you implement a way to inject game cert into generated xci?
Possibly by automatically detect "game_cert.dat" file in the folder and inject it.
You mean separate by baseid? That's meant to do several multixci in one go. Like you have game 1 with update1 and dlc1 in one side and game2, update2,dlc2 in other. You generate a list with the content of both games, process it separating by base id and the program will output game1.xci and game2.xci with all content.The menu:
What's the difference between choosing 1-1-2-... and 2-1-2-... ?
I see no difference for building a XCI, even using one or multiple number of files.
I forgot that it's possible to mix several games in one XCI.
I mean, if you don't plan to do multigames you're better always using 2. 2 can make several xci in one go and in the case you add an update or a dlc from a different region it'll add that to other file instead of you having orphaned files inside of your xci\nsp.I forgot that it's possible to mix several games in one XCI.
But I never use that, I only want to build single game XCI incl. update and DLCs.
So for this case there's no real difference using 1-1-2 or 2-1-2, right ?
2 is normally meant to build multi-game-XCI, but it works for one game, correct?
Did you verify the files with NSCB? It would be good to know if the original files and the result verify properly.
Yes, i can see about adding an option in advance to inject and extract the certs. I can make it so it let you inject the same cert to all games in the list, with a warning about online play and injected certs. I know they work but at the very least it seems that injecting the same one to a ton of games ends in a ban.
You're right about xci explorer and that game but the issue can't be related to number of files. I encounter that exception but looking at the number of files:A possible bug:
Packing Bomberman R and its update (01007AD00013E000 + 01007AD00013E800) together produces a broken xci, or at least one that can crash XCI-Explorer.
Please look into it.
Well could be a parsing issue? Either way next realease will use romanji as default and will fix the chinese\asia naming detection that's being haunting the program for a while. Those will be romanized b default since the library i'm using accepts extended kana\chinese and results seem good. There will be an option to dissable that though, it's just that i had reports of SX OS not liking japanese characters.Just came across a weird bug:
NSCB cannot verify file name "無名.xci", but can verify with name "無名無.xci".