ZFG Racing FAQ Categories
Troubleshooting
Why am I getting an “Operating System ID’s are different” message when flashing my tune?
If your vehicle supports Fast Flash, you may see an“Operating System ID’s are different” message after the vehicle receives an over-the-air (OTA) update or another service/update that flashes the PCM.
This means the vehicle’s strategy has been updated and the current OSID (Operating System ID) no longer matches the OSID of your existing tune file. When this happens, Fast Flash cannot be used and you’ll need to perform a Full Write instead.
If you would like your ZFG Racing tune updated to the newest OSID, purchase a Tune Update and submit a Modify Existing Tune Request through Tuning Central. You do not necessarily need a tune update just because the OSID changed. However, newer factory strategies can sometimes include fixes or improvements, or resolve compatibility issues with other updated modules.
Troubleshooting Tips:
1. Read and save the new stock file from the vehicle so you have a copy of the updated factory calibration. Our tuning guide similarly instructs customers to read their vehicle’s stock calibration through TDN and ensure the file is synced.
2. In the TDN app, press and hold the tune you want to flash and select Full Write.
3. Follow the prompts to complete the flash.
A Full Write allows you to continue using your existing tune even though the vehicle’s OSID has changed.
Helpful Links:
Estimated Time:
8 Minutes
Tags:
Factory Calibration, OTA Update, Troubleshooting
What should I do if an OTA update overwrote my custom tune?
While it's possible for an OTA update to overwrite your custom tune, many OTA updates do NOT impact the tune.
If an OTA update overwrote your custom tune, it does not necessarily mean that a Tune Update is required.
If you suspect your tune was overwritten:
1. Read the vehicle in its current state using READ VEHICLE.
2. Re-apply your existing custom tune.
3. If any errors are encountered or your existing tune will not flash, please submit a Tune Request. In the comments, briefly explain what happened and note that you've already read the vehicle again and attempted to re-flash your existing tune.
Our tuner will review the request and let you know if a Tune Update is required.
Troubleshooting Tips:
Whether to leave OTA updates enabled is 100% personal preference. We don't recommend for or against.
Helpful Links:
Estimated Time:
10 Minutes
Tags:
OTA Update, Tune Update, Read Vehicle, Software Update, Dealer Update, PCM Update, Over The Air Updates
My vehicle will not read the stock file. What should I do?
If your vehicle will not successfully read the stock file, please screenshot the specific error message(s) shown and gather an InfoLog.
Once completed, please email us directly and attach the screenshots, InfoLog, and any other relevant details. Our team will review the information provided and advise of the next steps after the review is completed.
Providing the exact error message and InfoLog helps us identify the cause of the issue as quickly as possible.
Troubleshooting Tips:
To gather and InfoLog from the TDN App:
With the tuning device connected to the vehicle OBD-II port and Key ON / Engine ON or OFF:
1. Open the TDN App → Tools / Settings (gear icon)
2. Select Help → Gather Info Log for Support
3. Tap Gather Info Log and follow the on-screen instructions
4. Wait for the summary screen to appear
5. Tap Share and save the file*
* Note: How the file is saved depends on your device and operating system. If needed, you can email the file to yourself and then save the resulting .txt file for attachment.
Helpful Links:
Estimated Time:
10 minutes
Tags:
Stock Read, Error Message, InfoLog, Troubleshooting, Support, Tuning Process
Can I use FORscan once tuned?
Yes. FORScan changes and custom tuning operate independently, so changes made in one generally do not affect the other.
FORScan modifications made before tuning will remain in place, and flashing a custom tune does not overwrite or undo those changes. Likewise, making FORScan changes after tuning does not require a re-tune.
In rare cases, FORScan may report an OSID mismatch when connecting to a tuned vehicle for the first time. If this occurs, please review the troubleshooting tips provided on this page.
After completing those steps, FORScan should connect normally whether the vehicle is running a stock calibration or a custom tune.
Troubleshooting Tips:
1. Flash Back to the Stock Calibration Temporarily
This is the simplest and most reliable solution. Reinstall the stock calibration, restart FORScan, and create or save the vehicle profile. In most cases, this allows FORScan to identify the vehicle correctly and continue working even after the custom tune has been reapplied.
2. Check for Software Updates
Make sure you are running the latest version of FORScan. Older software versions may not recognize newer operating systems or calibration strategies.
3. Locate the Factory PCM Part Number
If prompted, the factory PCM part number can often be found directly on the PCM itself. In some cases, it may also be available through Ford As-Built Data records.
4. Contact Us
If the issue persists after completing the above steps, please contact our team for assistance.
Please note that these solutions may not apply to all vehicles, software versions, or platforms.
Helpful Links:
Estimated Time:
Tags:
Modifications, Tuning
My RTD4 won't sync. What should I do?
If your RTD4 will not sync, first verify that your internet connection is stable and that you are signed into the correct HP Tuners account within the TDN application. Restart the device and application, then attempt the sync again. If the problem persists, contact our our team and include screenshots of any error messages along with your order number so we can assist with troubleshooting.
Troubleshooting Tips:
- Verify internet connection.
- Verify TDN account login.
- Restart the RTD4 and TDN application.
- Update the TDN application if prompted.
Submit screenshots of any errors when contacting support.
Helpful Links:
Estimated Time:
N/A
Tags:
RTD4, HP Tuners, TDN, Troubleshooting, Devices