Vehicle won't turn on, forscan won't connect, cannot fix, looking for advice

[Ben21]

F150 Lightning, 2023. Anyone know how to connect forscan when the vehicle won't turn on by clicking the ignition start button? I'm looking to fix a corrupt firmware upgrade. The firmware update of the BdyCM as built module was interrupted mid process due to what I believe was a bad obd adapter, though I'm still trying to find the reason.Yikes. Going to explain the current problem and looking for any advice.

Updates. 1/6/25: At the moment, I'm still trying to test out different options to see if I can fix it, but I may need to get help from someone with more specialized tool. I messed up the "brain" of the system, and it's difficult (but obviously not impossible, as we see) to brick it. Without the ability to turn on the vehicle, I'm stuck. This isn't something that others thought was possible due to the safety measures, but seems to happen on rare occasions. I'll continue trying and worst case, expect to buy a new BCM module to get it started. I'll continue to update with the status! If I fail, I think this may be the first device I've ever bricked, though I don't remember. I've done some flashing software of things in the past and might have taken one too many shortcuts this time. For starters, one lesson for me is ensuring you stick to a good forscan adapter before making changes. I was wondering why mine was slow but it makes sense now. And to forscan software credit, they warned about the possibility of failure from using an older obd adapter during the process, but I overrode their recommendation. ​

After the firmware update process was interrupted, I was able to connect with forscan afterwards fine. Later on you'll understand what I mean by "fine". Due to being worried about the battery voltage, I unplugged the 12v battery to manually charge it and try again later (otherwise, it will die). But now, after unplugging and replugging in the battery, and trying to connect again, I'm unable to connect to the vehicle with Forscan.

I unplugged the 12v battery to charge it up to full with a manual battery charger.

To fix this, I need to update the firmware for that corrupted BdyCM Module. But I cannot update the firmware if I cannot see a list of modules because forscan can't connect to the vehicle successfully.

That's where I'm at: I can't connect to the BdyCM Module because that initial forscan connection that is made is failing, so I never see the list of modules. When connecting to forscan to the vehicle, you get a pop up saying to please turn on the car. But I can't turn the vehicle on as clicking the turn on button does nothing. The only thing on in the cabin is the screen (and it hardly works [connects to carplay but will mostly just go black but on). So, as I said, there's the forscan pop up saying to turn on the car. I just proceed past that, and then forscan then asks if you'd like to load your existing configuration. If I say no, forscan immediately says in a pop-up "Error. Unable to connect to vehicle. Please make sure the ignition key is ON and try again". If I instead had said yes (to the pop up about loading old config), it will scan the modules 10 minutes, arrive at module called "PDM - Passengers Door Control Unit" and stay loading that for 2 hours. I do see dtc errors. During those initial 10 minutes scanning modules, there are "Unable to read DTC" errors every other line. I'm not sure if it will ever get past the PDM module after those two hours. I haven't waited past those two hours because it always gets stuck here. I haven't been able to see if it eventually continues finding other modules after those 2 hours because I assume something is wrong.

I need some help from others who may know how (or, if) I can even get forscan eventually connected, so that I can then try updating the software in the module. As I mentioned, I can't get that "fine" connection to forscan that I last had before disconnecting the vehicle's 12v battery.

Any help is appreciated either here or in messages on things to try. Am I out of luck? The vehicle is effectively a paperweight at the moment. The main battery is at 80% charge so that's good. If you have any questions I can answer to help us arrive at a fix, happy to answer with info or screenshots.

Some more info:
- I cannot unlock, lock, or do anything with the fob. I am manually opening the car with the physical key and with the emergency frunk hatch I cannot use the app either. The ford app will say the car is "on" but none of the unlock, lock, or climate buttons work.
- I have no idea if forscan can rescue me here, because it doesn't seem to be able to connect in the first place. I've thought about reaching to forscan support next if I'm unable to get it to work. I was wondering if the fdrs software used by mechanics may be able to do this in a way that forscan is incapable of doing it (maybe it would work even without ignition or accessory mode on with the vehicle.
- I was also thinking of a few other ideas:
--- restarting my computer to see if that's an issue (haven't tried that yet). I'm going to be even more embarrassed if this is what it is.
--- Or, try using a different version of forscan, maybe a different beta or non-beta.
- If I've truly bricked it, I may be looking at getting a hardware replacement of the module.

Sponsored

 

[21st Century Truck]

For info: the BCM is the equivalent of a brain for these vehicles. I once had a bad experience in my younger days, flashing an incorrect version of a BCM software in my Ford Fusion, which also bricked that car just like Your truck now appears bricked.

The good news (if You can call it that) is that the truck is fixable - to do that, You or a kind soul must reload a correct BCM software version into Your truck.

It's been so many years since my mishap that I honestly just won't pretend to remember the HOW TO steps... but with someone's help on that other forum, we managed to reflash my BCM in my driveway. It took a day or two to get it right, and several tries with ASBUILT files of Fusions simular to my model and year.

A dealership can also do this, but of course at Your cost.

Sincere Good Luck!

 

[Ben21]

Thanks for the info. I actually appreciate that there's hope it can be fixed like your Fusion was! I'll continue trying. Hopefully someone here has a lead.

 

[bmwhitetx]

Although there is talk of FORScan doing actual firmware updates, I have not heard of anyone using that functionally on our trucks. Instead Forscan allows you to change parameters/settings that the firmware references when running it's code. FDRS is used to update module firmware.

Odd that writing a parameter failed and caused this issue. I would start with rebooting your laptop but first disconnecting your negative terminal for 20 minutes.

EDIT: What parameter were you attempting to write?

 

[21st Century Truck]

Although there is talk of FORScan doing actual firmware updates, I have not heard of anyone using that functionally on our trucks. Instead Forscan allows you to change parameters/settings that the firmware references when running it's code. FDRS is used to update module firmware.

Odd that writing a parameter failed and caused this issue. I would start with rebooting your laptop but first disconnecting your negative terminal for 20 minutes.

FYI the module flashing program I used for that fiasco wasn't ForScan but another pretty powerful program, also from Russia. I never used it again once the car was running and just don't remember its name.

 

[Ben21]

Although there is talk of FORScan doing actual firmware updates, I have not heard of anyone using that functionally on our trucks. Instead Forscan allows you to change parameters/settings that the firmware references when running it's code. FDRS is used to update module firmware.

Odd that writing a parameter failed and caused this issue. I would start with rebooting your laptop but first disconnecting your negative terminal for 20 minutes.

I will try rebooting the computer and trying again tonight or tomorrow. I should clarify I'm using a different beta version of forscan than the usual version. It's not usually used and not easy to get, but there's an alternative version of the software with the ability to update and modify the firmware itself.

 

[bmwhitetx]

I will try rebooting the computer and trying again tonight or tomorrow. I should clarify I'm using a different beta version of forscan than the usual version. It's not usually used and not easy to get, but there's an alternative version of the software with the ability to update and modify the firmware itself.

Ah, now we know the rest of the story . I would say find someone with FDRS that can reload the BCM firmware. Could be thwarted by the BCM security lockdown though. Good luck.

 

[watts/up]

Although there is talk of FORScan doing actual firmware updates, I have not heard of anyone using that functionally on our trucks.

Don't the beta versions of FORScan allow for firmware updates? That's how the Pro and XLT trims are able to be retrofitted with passive entry and the light bar. In fact, adding passive entry updates the body control module itself to the XLT 312A firmware, I believe...

 

[GDN]

When you are in a pickle - give all the details. There are some good guys on here and they like to help, but they need to know all the info to be able to help. Start by updating your avatar area or signature with the trim of your truck and your location. That would help anyone that might be willing to help locally.

 

[Ben21]

When you are in a pickle - give all the details. There are some good guys on here and they like to help, but they need to know all the info to be able to help. Start by updating your avatar area or signature with the trim of your truck and your location. That would help anyone that might be willing to help locally.

I see what you mean. I'll make some edits.

 

[rugedraw]

What color is the BCM in the toolbox tab of FDRS?

Edit: Wait.....are you saying you were trying to update the BCM with FORScan and not FDRS when this happened?

 

[rugedraw]

@Ben21 After carefully reading your post, your BCM is most likely bricked and will need to be recovered by FDRS. Hard to say if you will be able to do this yourself with a Mongoose since the BCM requires either a dealer login or an NFTSA password to update it.

 

[Ben21]

@Ben21 After carefully reading your post, your BCM is most likely bricked and will need to be recovered by FDRS. Hard to say if you will be able to do this yourself with a Mongoose since the BCM requires either a dealer login or an NFTSA password to update it.

I appreciate you carefully reading my post. Your info is helpful. It makes sense it would lock out like that. No custom shop mechanics in my area (so far) seem to be comfortable with helping me on this after asking their ford specialist mechanics about it. It sounded like they could help but that they weren't confident about it which I understand.

I tried to provide as many details as I could, but there are other details I have to add now. I will edit my post and add them.

So if you don't think it's the low voltage, there are two other things that could've affected it. First, I think I used poor judgement in using a (too slow) Vint OBD adapter affecting it. It's my old one and it always worked with Forscan, but I think it really doesn't like it for this update. It doesn't use the newer protocol like my newer Vlinker one I couldn't find at the time. I have no idea if this is the reason why it failed, but it could have been. Regardless, both adapters don't work now. I will try restarting everything and trying again soon.

Another reason it could have failed: interlock (breathalyzer device) may be the cause of the catastrophic error? I've got an interlock device installed. And if you're thinking, what kind of idiot programs an electric vehicle with an interlock installed... well, here they are. The way the interlock device works (I think, but honestly don't know) is that it manipulates some wires that apparently control the ignition, and it prevents the car from starting until the test is not passed. It was a learning experience getting it installed in the first place with the installers as they've never done anything like it before. I may ask the installers to uninstall it if there's something unique about the bcm that interfaces with it, but it's important to note that the interlock device hasn't prevented me from updating other modules in the past, so I didn't think it could cause an issue. It's like a solonoid activates when it passes the breathalyzer test enabling circuits to connect.

Thanks everyone so far who's been supportive with questions and thoughts as I'm trying to fix this. Any other probing questions let me know.

 

[rugedraw]

The truck needs to be hooked to up FDRS with a proper VCM (Mongoose or better). If the module is purple, it is bricked and a PMI needs to be done to it. There is no other alternative that I know of.

 

[Ben21]

The truck needs to be hooked to up FDRS with a proper VCM (Mongoose or better). If the module is purple, it is bricked and a PMI needs to be done to it. There is no other alternative that I know of.

Ok. I'm guessing purple is something that the VCM shows, right?

Here's the pic I had taken after the firmware install failed, in the image here. I retried again right after and it failed at the same place. When I unplugged the battery to try again later, plugging it back in resulted in not being able to turn on the vehicle and no possible connection to forscan.

Sponsored