Did I ruin my WCM with alfaobd?

[SlippinJimmy]

Hi all!
I'm thinking I royally screwed up. The truck is a 2011 Ram ST and it came with only 1 blade type key. No fobs. Not knowing RKE wasn't even installed I used Alfaobd to program 2 new fobiks from ebay(non oem). Everything appeared to go the way one would expect and each procedure was successful. Then , like a bone head , I misread the warning about not running the elv replaced or escl replaced commands if the hardware wasn't present as "THIS WILL DAMAGE THE WCM". I ran the commands and it reported it was successful. Immediately after neither new fob would start the truck. However the original blade key did, 3 times exactly , each time shutting off the engine within a few seconds. After the third time it won't even attempt to crank.
To remedy this I have tried removing all keys and reprogramming which had no effect. I have tried resetting the WIN, sending the secret key to the WIN again no change. Pouring through the dumps I can see the engine kill command is active and that the skim module or rather the ecu received an invalid key from the skim module. My guess is that is the problem I need to solve but I've read somany posts and tried to understand the module status outputs and learn what all the acronyms meant that at this point I feel like I'm chasing my tail. We even had a locksmith out with an autel im508 and a workhorse? device and wasn't able to fix the problem or even get any closer to the problem. I was very surprised AlfaObd was able to access tons of data and functions that his tools werent able to access. Since then I've tried resetting the modules by discvonnecting the battery for 2 plus hours and even leaving the oe key in the ignition turned to run for an hour plus while connected to a battery charger to keep the voltage up.
To make matters even worse this is a friends vehicle I offered to program a key for primarily just to try out my new obdlink mx+ and within 15 minutes made his truck not run anymore. I feel terrible as its the guys only transportation ...Hes even staying on the couch while we figure this out. I figure it was the least I could do.
Thanks for any and all suggestions I'm ready to try everything at this point short of towing it to the dealer. If it comes to that then so be it but if theres still other options that I can try I feel like I owe it to him to do so. Thanks again-

 

[chri5k]

I was going to say the procedure for resetting the node lockout is to leave the fobik in the run position for 1 hour to reset the lockout timeout. However, since you deleted all the fobiks and tried to re-add them this probably will not work but worth a try.

Probably going to have to replace the WIN and re-initialize it. Not sure Alfa can do the re-initialization. Might be a dealer only deal.

Once you get the truck running, I would suggest taking a hammer to the OBDlink MX and deleting the Alfa app.

 

[irnwkrkev]

Had this same situation as OP yesterday. Original key was damaged but would start the car. Haven't erased the keys but when scanning for programmed keys it states "0 found".

SKIM error and it won't turn over. Locks and unlocks but won't start. Any way to fix this or is the WCM screwed from running the ELV replaced. The ESCL stated parameters out of range.

After learning how to read the system status it doesn't have ELV. Anyone know if "reset VIN values" would reset central lock?

 

[ric221]

Hi all!
I'm thinking I royally screwed up. The truck is a 2011 Ram ST and it came with only 1 blade type key. No fobs. Not knowing RKE wasn't even installed I used Alfaobd to program 2 new fobiks from ebay(non oem). Everything appeared to go the way one would expect and each procedure was successful. Then , like a bone head , I misread the warning about not running the elv replaced or escl replaced commands if the hardware wasn't present as "THIS WILL DAMAGE THE WCM". I ran the commands and it reported it was successful. Immediately after neither new fob would start the truck. However the original blade key did, 3 times exactly , each time shutting off the engine within a few seconds. After the third time it won't even attempt to crank.
To remedy this I have tried removing all keys and reprogramming which had no effect. I have tried resetting the WIN, sending the secret key to the WIN again no change. Pouring through the dumps I can see the engine kill command is active and that the skim module or rather the ecu received an invalid key from the skim module. My guess is that is the problem I need to solve but I've read somany posts and tried to understand the module status outputs and learn what all the acronyms meant that at this point I feel like I'm chasing my tail. We even had a locksmith out with an autel im508 and a workhorse? device and wasn't able to fix the problem or even get any closer to the problem. I was very surprised AlfaObd was able to access tons of data and functions that his tools werent able to access. Since then I've tried resetting the modules by discvonnecting the battery for 2 plus hours and even leaving the oe key in the ignition turned to run for an hour plus while connected to a battery charger to keep the voltage up.
To make matters even worse this is a friends vehicle I offered to program a key for primarily just to try out my new obdlink mx+ and within 15 minutes made his truck not run anymore. I feel terrible as its the guys only transportation ...Hes even staying on the couch while we figure this out. I figure it was the least I could do.
Thanks for any and all suggestions I'm ready to try everything at this point short of towing it to the dealer. If it comes to that then so be it but if theres still other options that I can try I feel like I owe it to him to do so. Thanks again-

Where you able to resolve this issue, if so how did you accomplish it? I ask this in case other members who may experience this type of issue can possibly find answers and or solutions.

 

[chri5k]

The OP is probably a one post wonder. Hasn’t been on the forum since the day after the monumental screwup was posted.

 

[patricknola504]

I'm having this same issue fobs stopped working over a month prior then one day 3 starts with 3 second runs and now no crank no start tried another ECU and TIPM no luck

 

[SlippinJimmy]

Hopefully this helps someone save some time but in my case yes I did very much irreparably brick the wcm with alfaobd. Basically from what I can tell is when I asked it to perform a function that there wasn't actual hardware for on the vehicle I bricked it. I believe it had something to do with the column lock off in not mistaken. The truck did not have that feature and when I reset it thinking that it did there is no way of going back or reverting to your previous configuration. Get your wallet out and buy a new one. Hope this helps someone as there wasn't much information out there back when I was pulling my hair out over it. Once replaced and keys programmed it fired right up.

 

[joshiepoo]

I just did the same thing with alpha trying to activate my girlfriends remote start on a 2009 dodge journey and killed the win (key switch)
The good news is you can get a used one from a junkyard and use alpha to reprogram it your vehicle. You just need to copy the secret code from your PCM to it and a few other steps which I think was to change to immo pin to your old pin and then reset the wcm after that you will put your original key in and have alpha program your key again with the old immobilizer pin and you should be all set. After each step you will need to turn off ignition and then turn it back on. Hope this helps someone.

 

[kbelfour]

I did somewhat of the same thing , I reset the wcm and locked it out of rke , fobik , and tpm . Basically deleted it from the can-c and rf network I guess. luckily I have a tech genius of a friend save the day. he used a launch x431 scan tool and ran a pcm - wcm replacement function. he was able to rewrite the vin in the wcm and force the secret key back to the wcm , the back to the pcm. the we programmed the fobiks but I'm still having some issues with rke on one oem fobik. truck runs and drives fine but now only one fobik and no first handshake. i ended up purchasing that same scan tool as it was cheaper then replacing the win module ( $700 ) on amazon

 

[madtrucker2016]

I was going to say the procedure for resetting the node lockout is to leave the fobik in the run position for 1 hour to reset the lockout timeout. However, since you deleted all the fobiks and tried to re-add them this probably will not work but worth a try.

Probably going to have to replace the WIN and re-initialize it. Not sure Alfa can do the re-initialization. Might be a dealer only deal.

Once you get the truck running, I would suggest taking a hammer to the OBDlink MX and deleting the Alfa app.

He didn't know the gun was loaded, it seems like.

 

[iScruffy]

I was going to say the procedure for resetting the node lockout is to leave the fobik in the run position for 1 hour to reset the lockout timeout. However, since you deleted all the fobiks and tried to re-add them this probably will not work but worth a try.

Probably going to have to replace the WIN and re-initialize it. Not sure Alfa can do the re-initialization. Might be a dealer only deal.

Once you get the truck running, I would suggest taking a hammer to the OBDlink MX and deleting the Alfa app.

I was wondering if this is also ment to clear b2254 because I have the same problem but I did not reset the fabik