About "yellow" devices
Before reading further it is necessary to understand that everything written below applies only to devices with serial numbers 968590115000 and beyond. Other devices do not have problems.
Devices with serial numbers 968590115000 and further, can be divided into 4 types.
1. These are the devices that did not connect to the original program.
(These devices do not work on firmware 11.54 but work fine on firmware 11.52, until they are connected to the original program)
2. These are devices that were connected to the original program and work with the original EOBD2 22.49 or 22.51 but do not work with third-party programs (infinite download or "really get out?" Error).
(Additional protection is activated on these devices (the second verification factor), in order to bypass this protection, it is necessary to include two-factor verification on the server and the device works fine, as I will write below.)
3. This device is connected to the original program, but does not work with the original EOBD2 22.49 and 22.51.
(On such devices, when trying to start the original EOB2, the "Networck abnormal" error appears. Such devices will not work until the error is fixed. (Why this error appears and how to fix it I will write below))
4. These are devices that, when starting the brand, produce a long beep which stops only when the power is turned off.
(This problem may occur if the internal memory of the device is damaged or blocked, we are still looking for a solution.)
How to activate the second factor on the server?
On the client side
1.Connect the device to the car, download and run the original program with EOBD2 22.54 or newer (Enter the brand menu. It is mandatory!).
2. Close the program and turn off the power of the device.
On server
We on the server do the verification.
Then you can download the brands and check the operation of the device.
(This is an experimental function and until all brands are supported, specify the brand before use)
Why does the error "Networck abnormal" appear and the device does not work even with the original program?
This is a problem solely on the side of the server.
When the device is connected for the first time, the program requests the activation code of this device from the server and for some reason the server does not send it. Most likely this is due to the inadequacy of the security system itself. As a result of this, the device remains in the border state, locked but not unlocked for operation even with the original software.
In this case, there is only one solution. Write to the seller or the company that they solve the problem on their..