XCI to NSP super hard

  • Thread starter Thread starter viper3344
  • Start date Start date
  • Views Views 2,870
  • Replies Replies 12

viper3344

Well-Known Member
Member
Joined
Aug 18, 2011
Messages
633
Reaction score
213
Trophies
1
XP
1,659
Country
United States
hey all!

Trying to use SAK to convert some recent XCI's to NSP's and every single time it keeps telling my my prod keys are wrong. I literally used the latest lockpick to grab them from my emunand (19.0.1) and still wont work.

XCI-explore keeps saying it needs key 17??? As far as I know they arent even up to 17 yet?

What gives??
 
hey all!

Trying to use SAK to convert some recent XCI's to NSP's and every single time it keeps telling my my prod keys are wrong. I literally used the latest lockpick to grab them from my emunand (19.0.1) and still wont work.

XCI-explore keeps saying it needs key 17??? As far as I know they arent even up to 17 yet?

What gives??
You're confusing the hex key 11 which is decimal key 17, Actually we are up to hex key 12 (decimal 18). You can't convert because you are not decrypting the nca files because you are indeed missing keys. You probably have an older version of lockpick_rcm that is not updated and that's why your keys are wrong.

You will need these:
master_key_11 = 03d1xxx.........................
master_key_12 = 32ECxxx.........................
 
I do have 11 and 12 which I got from lockpick. For example. 12 ends with........88e
is prod.keys broken for SAK or something?
 
I do have 11 and 12 which I got from lockpick. For example. 12 ends with........88e
is prod.keys broken for SAK or something?
No Sak works great. In windows sometimes you will have this file - c:/users/yourusername/.switch/prod.keys. If that file exists hactool (which sak uses) will use that prod.keys instead of the one you have in your sak folder. You should check that file and add the correct keys to it.
 
No Sak works great. In windows sometimes you will have this file - c:/users/yourusername/.switch/prod.keys. If that file exists hactool (which sak uses) will use that prod.keys instead of the one you have in your sak folder. You should check that file and add the correct keys to it.
Just checked. No such file or folder there. If you wanted to test it. Its the XCI of the Neo Geo collection Vol 1. See if its happening for you? Thanks!
 
The bigger issue is that there's no reason to convert XCI to NSP.
Huh? What am I missing? Is there a new way to run an XCI? Is there a safe hack of SXOS that works with the latest firmware? OP wants to use it on hardware, not an emulator... right?

EDIT: Oh, yea. The XCI can be installed as well. Nevermind. Very late (more like early morning) and I've had a few...
 
Last edited by urherenow,
The bigger issue is that there's no reason to convert XCI to NSP.
There absolutely is. Even though DBI can install XCI's I want the trimmed NSP and for storage sake, keep them all the same (as NSP)

My pre FW11 XCI's boot from my SXOS partition but I want everything post FW11 with atmo to be in NSP format. Quick way for me to know what is SXOS compat and what is not. So yeah, pleanty of reasons.

*and yeah this is hardware. I have no need for switch emulators.
 
There absolutely is. Even though DBI can install XCI's I want the trimmed NSP and for storage sake, keep them all the same (as NSP)

My pre FW11 XCI's boot from my SXOS partition but I want everything post FW11 with atmo to be in NSP format. Quick way for me to know what is SXOS compat and what is not. So yeah, pleanty of reasons.

*and yeah this is hardware. I have no need for switch emulators.
You can trim xci to roughly the same size as the nsp variant. If your wanting them smaller for storage purposes. Convert it to nsz
 
I dumped my prod.keys from my switch and got the same error i had to download the latest prod.keys from the internet to get it to work.
 

Site & Scene News

Popular threads in this forum