Two Switches, two licenses, one SX Pro, license is invalid on additional switch

iomega311

Full Member
Dec 9, 2011
92
8
Arizona, USA
I purchased an SX Pro last year for my Switch. Everything installed swimmingly... and I have been using it for a year now.
My wife got a Switch and so I am wanting to get SX OS installed on it too.

I didn't see the need to buy an additional SX Pro kit, since I can just share the payload injector with the other Switch.
I purchased an extra SX OS license and started to get it setup.

My new (new to me) Switch is a 1st gen and is currently on 10.0.4
I have tried using both the latest stable (2.9.2) and latest beta (3.0.3) boot.dat files to get the license generated.
I am using my SX Pro to boot into SX OS... and have already dumped the NAND and backed up to my PC.

Once I completed that step, I moved on to getting my license.dat file generated by downloading the payload file from sx.xecuter.com and then booting into SX OS, selecting "Options", then "Payloads", and then injecting the payload obtained from the SX OS website.
I am then selecting to boot into custom firmware... which then generates the license request file...
I am then taking that file and uploading it to the activate license section, entering in my License Key, and it then downloads my license.dat file.

I am then adding that back onto my SD card and then booting back into SX OS via my SX Pro injector.
From here I have tried loading the Custom firmware once the SX OS splash screen has loaded... as well as first hopping over to the payload section and injecting the payload file first... and THEN selecting to boot into custom firmware.

I have also used the TegraRcm tool and the payload from the SX OS site to boot and generate my license request file...

Either way, I am presented with "Oh no! the license.dat file on your microSD card is invalid for this Switch Console!".

Some other posts have suggesting booting into older firmware in order to get the license to create accurately... I have tried 2.9.2, 3.0.2, and 3.0.3...
Am I missing some important step?
Is my OFW too new? (10.0.4)

Any other suggestions? I've been at this for hours and I am finally giving up and asking for help.

Thanks for any help granted.
 

Grimlock97

Loyal Member
Jun 14, 2020
270
28
Austria
SX OS License is only for one switch. If you activated it with your Switch, it will be permanently valid to your Switch. You cant use then the SX OS license on other switch. You have to buy a new license.
 

iomega311

Full Member
Dec 9, 2011
92
8
Arizona, USA
SX OS License is only for one switch. If you activated it with your Switch, it will be permanently valid to your Switch. You cant use then the SX OS license on other switch. You have to buy a new license.
Right, I get that.
So, Switch 1 has a valid license that was assigned to it a year ago via the SX Pro... the one that the SX Pro came with.

Switch 2 had no license. So I bought an extra one... just the license, instead of a whole additional SX Pro injector/jig. I put the SX Pro onto Switch 2, injected the payload, generated a license request, took that to the account activator, provided the brand new license, downloaded the newly created license.dat file, and put that on Switch 2.

So the new license should be assigned to Switch 2. It was never used on Switch 1... I just used the same SX Pro in order to inject the payload.

Hopefully that makes sense.
 

optantic

VIP Member
May 2, 2010
622
48
Don't use the dongle pro to inject the payload on your 2nd Switch, otherwise it would use the license code from the dongle to generate the file. You need to inject payload from a PC then use the purchased license code to generate the file
 

iomega311

Full Member
Dec 9, 2011
92
8
Arizona, USA
Don't use the dongle pro to inject the payload on your 2nd Switch, otherwise it would use the license code from the dongle to generate the file. You need to inject payload from a PC then use the purchased license code to generate the file
OK, so that's kind of what I started realizing after I took the license request file to the Activation site and it generated a license.dat file without requesting a license key code.

So my next step was to download/install the TegraRcm tool onto my PC.
Once that was done, I loaded the payload file that I downloaded from the SX site and put my Switch into RCM mode while it was connected to my PC via USB C. I injected the payload and SX OS loaded up. I then generated a new license request file which I then took to the activation site. This time it requested my SX OS license key code... which was accepted and generated a license.dat file.

This is the file that I put back on my SD card.
I then booted the Switch back up with TegraRcm using the SX payload and then attempted to boot into custom firmware... but this is where it gave me the error involving my license.
 

optantic

VIP Member
May 2, 2010
622
48
Try to use the license.dat on your old Switch and see if it works. If yes, then you had activated it on that Switch, if not then contact the reseller where you purchased the license code from