daxt0r

yes, for example the MITSUBISHI above not work with the LICENSE.DAT file, i get disaccording serial no. Normally i just replace LICENSE.DAT from original EasyDiag EOBD activation (like instructed in page 1) and it works. Any workaround?

hey i normally just copy my LICENSE.DAT from my EOBD 22.53 to all the brands and it works. However with latest brands i get either disaccording serial number. If i replace libstd, adap.ver and dpu.ver, i hear three beeps as if to connect but then it says diagnostic failure. I have yellow connector (EasyDiag 2.0) and using F65 Shell on firmware 11.74. Older brands from April/May 2019 work fine once restored. hey i normally just copy my LICENSE.DAT from my EOBD 22.53 to all the brands and it works. However with latest brands i get either disaccording serial number. If i replace libstd, adap.ver and dpu.ver, i hear three beeps as if to connect but then it says diagnostic failure. I have yellow connector (EasyDiag 2.0) and using F65 Shell on firmware 11.74. Older brands from April / May 2019 work fine once restored. Also one more question, which is correct firmware for my connector, PRO3 or PRO3S? Can anyone help me or point me in the right direction, i read over 100 pages i think looking for solution.

thank you!! btw i got my whistle working in AndroidX86 finally was Google TLS change causing ARM library download error.

i too would like to know as i have EasyDiag 2.0 (yellow whistle ) and not too sure which 11.70 firmware to flash, i.e. PRO3S or PRO, or does it even matter?

tried looking , even searched but not seeing what shell, i tried F62 and 3.12.007 but same crash, going to try to redownload vehicles package.. thx

ok will try an let you know, but strange, i never had any problems!! thx!!

i too have a similar problem. I recently upgraded my Easydiag 2.0 from 11.65 to 11.70 and upgraded the VEHICLES to Jan2019 by replacing the license.dat file and now no matter what shell launched it says Application encountered an error.. Any ideas? Greetings from the Caribbean!