Fortin EVO-ONE Install Questions

May someone can tell me what is the correct order of installation EVO ONE as soon as we have the unit on our hand:
1- Connect to our vehicle via T harness to do Dcryptor programming --> Connect to computer via The Updater to do Key Bypass programming + update firmware for the EVO unit.
Or
2- Connect the Evo unit to computer via The Updater to get the unit firmware updated first---> Connect to our vehicle via T harness to do Dcryptor programming --> Connect to computer via Updater to do Key Bypass programming.

Hope you guys all understand my concerns and give me your advices.

Thank you
 
May someone can tell me what is the correct order of installation EVO ONE as soon as we have the unit on our hand:
1- Connect to our vehicle via T harness to do Dcryptor programming --> Connect to computer via The Updater to do Key Bypass programming + update firmware for the EVO unit.
Or
2- Connect the Evo unit to computer via The Updater to get the unit firmware updated first---> Connect to our vehicle via T harness to do Dcryptor programming --> Connect to computer via Updater to do Key Bypass programming.

Hope you guys all understand my concerns and give me your advices.

Thank you
Just follow steps in this video. Just make sure you use Firmware Ver. 85.11

 
I just installed the Evo One and noticed this same error. I should be on the latest FW but I can't recall the version.

For those of you who experienced the "Mazda cruise control disabled under 20mph" error, once you updated to FW ver 85.11, did it address the issue with the error?

In addition, I did not install the hood pin switch, but considering that I should. Just learned last night that the car does allow to autostart with the hood open. On my other vehicles, with Evo One, it won't autostart with the hood open.
 
I just installed the Evo One and noticed this same error. I should be on the latest FW but I can't recall the version.

...

Update.... just checked and it seems I have fw 85.09... For some reason it does not allow me to update to 85.11 or 85.12

I'Ve contacted support, waiting to hear what they say. anyone else had this issue?
 
After a number of FW changes the software/device gets locked. Just fill out a support ticket on their website and they will reset it on their end so you can then flash the newest version.
 
  • Like
Reactions: rzc
Done deal.... I'm now on 85.12 and so far the "Mazda cruise control disabled under 20mph" is gone. Only time will tell.

I'm just glad that my Linkr LT2 is still working.
 
Quick update.. on the CX5, still working great! So I finally installed the Evo One on my 2023 CX30... Everything went smooth until I did the final test before putting everything back. Need assistance with the "Push Button Start Malfunction. Have the Vehicle Inspected." error. I get this immediately after I enter the vehicle and push the start/stop button of the vehicle. I tried multiple times and get the same results. As soon as I press the brakes, engine stops, as normal. Its appears that the Evo One is not recognizing when I press the start/stop button. When I restart the car, the error is gone; only get it during takeover. I already reached out to support. Thoughts?
 
As soon as I press the brakes, engine stops, as normal.
Interesting. On my 2023 CX-50 the engine does NOT stop when I press the brakes (on my 2019 CX-5 it does stop the engine). I contacted Fortin and they said that's just how it is. I would think the CX-30 is more like the CX-50 and would do the same. It makes me wonder if you should just take it out and reload the firmware in your unit from scratch. Make sure you have the correct car identified.
 
I would also make sure you are on bypass FW version 90.[05] and remote starter FW version 1.[26] or higher.
 
Well it turns out, I wasn't reading the instructions properly.... it appears the turn-over for this one is not the start button but rather just step on the brake pedal (per Fortin support). I'm about to try it out again and see what happens. For the last 4 installs I did, throughout the years, it was the start button. This is true even with my 2019 CX5
 
Well it turns out, I wasn't reading the instructions properly.... it appears the turn-over for this one is not the start button but rather just step on the brake pedal (per Fortin support).
Yeah, that's what I said :)
 
Well obviously I didn't read your write up all the way through or read page 11 on the instruction..... duh! Thanks again.
 
@Candurin , @RedBaron - check out the video of me testing the RS. Question, I noticed when it starts, it beeps (same beep as when you walk away when the car is running) for about 10 seconds. Does yours do the same? My 2019 CX5 doesn't do this.

 
Last edited:
I expect it's a bypass setting. It's still looking for the key fob.

I have not seen that happen on my CX-5 nor my wife's 2018 CX-9.
 
I posted this in the support QA....

I tried the RS this morning and it didn't do it this time


Then I tried it again, now it did it.


And here's the worse part. I get to the car while it was running and it wouldn't unlock with the door handle sensor or keyfob. You can see that it would respond to the unlock by flashing the light but does not unlock the actual car door. I had to have kid go through the trunk. Not good!

 
And here's the worse part. I get to the car while it was running and it wouldn't unlock with the door handle sensor or keyfob. You can see that it would respond to the unlock by flashing the light but does not unlock the actual car door. I had to have kid go through the trunk. Not good!
I've had this happen a couple of times (not often). I found that if you just lock it again with the remote, then unlock, it will open.
 
I found that if you just lock it again with the remote, then unlock, it will open.

I believe I tried that and it was a no go.if it happens again, I will try it out. I'm just glad that at least the trunk unlocked.

In the meantime, I heard back from support via QA and they want me to call in.
 
Back