I agree on your advise regarding which Key programmer to get. It is best to have both if budget permits, the KM100 and the Xhorse VVDI Keytool MAX pro. The Xhorse has the special function which is unique but I have yet to actually try. Its the "VVDI Smart key Clone". The KM100 does not have that.
What are the differences between the XM38 smart key to the XE series that are not designated XM? Are they interchangeable? I notice that the non XM ones such as XE…. Will still appear to generate even though the Xhorse app list under Remotes: XM38-smart or XM-Toyota etc. appreciate all your videos. They have been very useful
@@Beginner-locksmith Thank you. That explains that after I add the XE non xm38 key into a 2015 Mitsubishi Lancer GT CVT, all keys such as the OEM key appear to program using the KM100, but at the end of the successful complete message, no remotes work nor can the engine start. I have a XM-smart Key on order and will update this thread so that fellow viewers will see it. Thank you for great videos.
@@Beginner-locksmith Got the XM38-smart (XSCH01EN) key today and generated the key with the VVDI mini for 2015 mitsubishi lancer GT which comes with a Semi-Smart Proximity key and turn to start column mounted Off/On/start. The KM100 was able to program the Key to the vehicle. my mistake originally was using a non Xm38 XS series key.
Have you had consistent success when programming the Xhorse generated XS keys to the car with the KM100? Or have you found that it is a must to use the Xhorse ODB capable VVDIs such as the pro max ?
I’ve had lots of success with the Toyota XM38 versions. I’ve never used the normal XS ones successfully but lately I lean towards the autel keys for push to starts anyway. On the Toyotas and Lexus I have successfully used the key tool max pro successfully.
Car companies put all this electronic accessories just to start the car.not much difference with the old car..only the new you have to buy all the expensive tools..it does the same job
