Much of these faults are because of the adapter. FORScan will recognize and likely fail with poor quality adapters.
The best for any type of programming are high quality Bluetooth and USB connections.
A personal choice are the OBDLink devices with firmware and the general duty BAFX.
The chinese clones are garbage. The tools that have been tested sucessfuly are versions 1.4 to 1.5.
These so called 2.1 versions are quite questionable.
Just because those are cheap to purchase, doesn't mean it was a smart purchase.
The J2534 device are very stable and much faster. The issue being the cost of such a device.
Again, chinese close are questionalble and the best will be from high end manufacturers like Bosch, DrewTech, Actia etc.
When it comes to keys, the best solution are OEM keys, not some cloned fleaBay or amazonia POS from wherever they are created.
At least one key should start the vehicle. If no keys are available, a minimum of two OEM keys are required.
Get a wiring schematic and follow the connection from the PATS module to the controller that "Authorizes" the key and sends authorization to the PCM to enable a start sequence. In many cases, the Instrument Panel addresses the Tx and Rx lines. (Tx = Transmit, Rx = Recieve)
1) A power supply is a must and attached at the battery.
2) A complete scan must be performed first and saved.
3) Have the OEM keys ready. Make sure the DLC fits the device snug and ALL the connecting pins are clean and tight.
4) Look at the controller and save the image of where the keys are stored. View the changes later.
5) Perform the function and wait for the the complete allotted time.
6) Follow the instructions for your model exactly as described.
One last piece of advice, if for any reason As-Built data was changed for any controller that is associated with PATS, you've been warned.
As with any immobilizer, the As-Built should be the factory version.
Do not ask for help in PM. Use the forum to ask and answer questions!