Downloaded softwares from our download section are encrypted and packed to avoid cracking. This encryption also block anti virus from analysing our software and sometime it cause false alert. We recommand you to add our software list in your exclusion.

1) Disable antivirus firewall defender windows
2) Try using another internet connection.
3) Sync your pc time, Allow/enable Windows automatic hour synchronisation

ECU BOSCH MED17/EDC17 AND CONTINENTAL SIMOS8 to 18 can be full read with a lot of different tool.
We recommand AUTOTUNER, ALIENTECH KTAG, CMD FLASH, BFLASH

Our system will automatically send the token key to the email from which the purchase originated. Allow 15-20 minutes to get the email.

The price of the tokens can be found in the “BUY TOKENS” section.

Your token will expire after one year from the date of your last purchase. Example: If you have 100 left tokens in your account and leave them for more than 365 days, the system will block your token. At that time, if you order, say 20 tokens, your account will be unlocked and you will get 120 tokens in total. This way you never lose your token.

No, Tokens are only subtracted if the file process is complete, you can run software and open a file to see if it is compatible without token subtraction. A message will appear with your total remaining token and cost before any transaction.

Yes, the software is not pc-attached. It does require internet to work.

The prospect of unlimited software is not viable, considering the support we provide for these solutions. Offering unlimited support for a fixed fee would be impractical.

Taking an exemple, like PCR2.1 solution, introduced in 2020. It was exclusive at the time, resulting in four years of algorithmic improvements over any other software available today. If you frequently perform PCR2.1 immo off procedures and prioritize reliability for your customers, opting for a limited but refined immo off software is more prudent than any "unlimited" one.

Moreover, IMMOFF17 remains the sole software capable of accurately correcting checksums. The checksum issue has plagued the majority of our customers, as many writing tools only correct checksum on the calibration sector while immo bytes are located in another sector. Choosing IMMOFF17 ensures comprehensive checksum correction, addressing a prevalent concern among our user base.

Here is two different pattern that you can follow:
U0XXX = PCXXX
and
U1XXX = PDXXX

Follow the link to get the tested files list: https://www.neurosuite.ca/immoff17_medc17_filelist.html

Yes.
We suggest to load unmodified original file first and FULL read, if possible.

IF your file is not listed, DTC Disabler will ask you to upload the file on our server. In few secondes you should be able to open your file. Our algo will work better if you have a complete file reading not virtual read.

If your file can't be processed for whatever the reason, you will be prompted to FLAG that file. Flagging the file will alert us to manually add it to the serveur. We add them generally in the same day. You will be notified by email as soon the file is ready.

It could take from 15 minutes to 48 hours.

1) ESP is OFF ?
2) Clutch signal is working ? (Check with VCDS, engine cruise switch, google it!)
3) if car is AUTOMATIC or DSG, have you selected DSG option ?
4) Engine rev hit a soft limiter ? If car has NO ESP button, you will need to RAISE "standby nmax" map in the calibration map. If you are not able to do this, you can set launch control under this soft limiter rpm.

We recommand to start with default setting.

That's depend of the setup (turbo size, exhaust, engine size).

You can see setting/result in that video:
https://www.youtube.com/watch?v=T3Gub4-WnTQ

Some preset:
VW/AUDI 2.0T MANUAL with stock turbo
SPEED: 5km/h
RPM ATDC: 4000
TIMING ATDC: 15
RPM IGN CUT: 4200
RPM NLS: 5800


VW/AUDI 2.0T DSG with stock turbo
SPEED: 5km/h
RPM ATDC: 3950
TIMING ATDC: 15
RPM IGN CUT: 4010
TCU DSG LAUNCH RPM: 4000 (You must reflash tcu)

VW/AUDI 2.5
SPEED: 5km/h
RPM ATDC: 4400
TIMING ATDC: 16
RPM IGN CUT: 4600
RPM NLS: 6300

VW/AUDI 3.6
SPEED: 5km/h
RPM ATDC: 4300
TIMING ATDC: 12
RPM IGN CUT: 4500
RPM NLS: 6300

First you need to know what more agressive setting = more dangerous for the engine.
More ATDC timing degree = louder bang

TIMING ATDC (exemple 18)
RPM IGN CUT (exemple 4800) will give a very hard cut.

You need to set TCU DSG Software 50RPM more than launch ecu maximum rpm set.
IE: DSG Launch at 3500, Launch17 timing: 3350, ignition: 3450

Yes, you can edit setting but you must use the exact same file as you did the first time.

Yes, you can. For both MED9 and MED17. MED17, we tested it with PCMFLASH.

Error can happen if you tryed to process a non-complete virtual file. ERROR: "Can't locate freespace offset" or "Can't locate variable". It will also work with ANY tool using boot and/or bench service mode method to read and write. Such as MPPS, Bflash, Autotuner, Ktag, Trasdata, Kess and more. Only PCMFLASH will completely work by OBD at this moment.

** Always perform a mass-clear code operation after ECU installation. If old IMMO codes persist in the system, it could potentially prevent the vehicle from starting. **

1) File Compatibility: Ensure that files have not been interchanged between different ECUs. It is essential to use files specific to the same ECU.

2) Software Match: Verify that the software being used corresponds to the specific engine or model revision of your vehicle.

3) Diagnostic Trouble Codes (DTC): Investigate for Diagnostic Trouble Codes (DTC). In case of replacing a malfunctioning ECU, rule out any other underlying vehicle issues.

4) File Verification: Confirm that the file has been written correctly by performing a re-read of the ECU. Compare this re-read file with your IMMO Off file.

5) Data Submission: If all previous checks have been carried out without success, kindly submit the following files appropriately zipped:
A) Replacement ECU files + Original ECU files (if available)
B) Generated IMMO Off file + Re-read of non working immo off ECU files.
C) Name of the tool used to read/write your ecu.
D) If IMMOFF17 prompted for the MCU ID, kindly inform us of the MCU ID that you have written in order to generate the file.
E) DTC list if you have
F) Explain the situation: total key lost, ecu replacement, etc.

1) Start by identifying the original car software version (e.g., "03L906023DM 03L906023DL").
2) Procure a replacement ECU with the exact same software version or consider updating your existing ECU (see additional instructions below).
3) Perform a complete read of the replacement ECU and apply IMMOFF17 to deactivate the immobilizer in the FLASH or MPC.
4) Write the saved flash file to your replacement ECU.

Why Avoid Using a Different Software Version?
SIMOS and PCR2.1 ECUs incorporate a distinctive "POWERCLASS" feature. This is deliberately designed to prevent the use of a more powerful software on a vehicle with a lower power rating. For example, installing 180hp software on a 150hp car. Once the ignition is switched on, the ECU transmits its powerklass to the BCM and other CAN components. All components must operate with the same powerklass ID. If the ECU possesses a different one, all other components will reject the mismatched component (the ECU, in this scenario), resulting in the car's failure to start.
To rectify this situation, adhere to the following set of instructions (How to Flash IMMO Off and Update ECM to a Newer or Compatible Software Version).

1) Initiate a boot or bench mode read to acquire the complete ecu read.
2) Choose the obtained flash/mpc and apply the IMMO OFF patch using IMMOFF17.
3) Write the immo off file to the ECU.
4) Connect the ECU for standard ECU programming by OBD or BENCH, using CAN LOW HIGH.
5) Proceed to write the newer correction version (FRF/ODX/BIN) as you would typically with your OBD writer tool.
6) After completing this update, the ECU will be updated, but the IMMO feature will be reactivated.
7) Perform another boot or bench mode read to obtain the complete ecu read once more.
8) Choose the obtained updated flash/mpc and apply the IMMO OFF again, (that time for free).
9) Write the new immo off file to the ECU once again.
10) Following these steps, the ECU will be updated and the IMMO feature will be successfully disabled, ensuring proper functionality.
STEP RESUME: BACKUP ECU, APPLY IMMO OFF, FLASH UPDATE (FRF/ODX/BIN), RE-READ ECU, RE-APPLY IMMO OFF.

1) Initiate a boot or bench mode read to acquire the complete ecu read.
2) Choose the obtained flash/mpc and apply the IMMO OFF patch using IMMOFF17.
3) Write the immo off file to the ECU.
4) Connect the ECU for standard ECU programming by OBD or BENCH, using CAN LOW HIGH.
5) Utilize your tuning flash tool, opt for the V-Read, and flash the ECU.
6) After this step, the ECU will be unlocked, but the IMMO feature will be reactivated.
7) Perform another boot or bench mode read to obtain the complete ecu read once more.
8) Choose the obtained unlocked flash/mpc and apply the IMMO OFF again (that time for free).
9) Write the new obd-unlocked immo off file to the ECU once again.
10) Following these steps, the ECU will be unlocked, with the IMMO OFF setting preserved. This ensures that the ECU is prepared for tuning through OBD and allows for tuning/flashing operations via OBD without any IMMO-related constraints.

Yes, it is. IMMO5 is named as "WFS5" in our software suite. IMMO6 is WFS6

Every time you utilize the IMMO OFF feature for ANY FLASH IMMO OFF, it's MCUID is registered in our database and linked to your account. This ensures that you won't be charged twice if you need to update the ECU with FRF and subsequently reapply the IMMO OFF patch. This system is designed to provide you with a seamless experience and avoid any redundancy in charges.

In cases where you've lost all keys for a more recent vehicle (Model Year 2009 and beyond), the engine may start, but you might encounter issues with the windows' up/down function due to problems with the BCM (Body Control Module). Additionally, the cluster could display an immobilizer message (key not found). It's crucial to understand that the immobilizer system typically follows this sequence:
KEY -> CLUSTER -> BCM -> WINDOWS CONTROL
KEY -> CLUSTER -> ECU -> ENGINE
Please note that we do not offer BCM immobilizer deactivation services. Some have reported success by placing a new/virgin "ID48" chip near the key sensor, but this approach may not be effective on all vehicle models.

The initial file saved by Autotuner will be named "BENCH_NR.BIN." This file serves as a "virtual file" and exclusively contains the MAP calibration area. It can be flashed through either OBD or BENCH methods but is not used for disabling immo.

1) After the reading process is complete, locate and copy the Bench-backup.zip file typically found in "Documents\Autotuner ECU backups" to your Desktop.

2) Extract the contents of Bench-backup.zip into a new folder. The files encompass the comprehensive ECU read, with those starting with DFLASH representing the "EEPROM" and IFLASH denoting the "FLASH."

*If Autotuner saved the FLASH into two separate files (iflash0 and iflash1), IMMOOFF17 will prompt you to MERGE THEM. Merging is essential for applying the immo off.

3) Execute IMMOFF17 and select the FLASH file then save it to iflash0_IMMOOFF.bin.

* Unlike other tools, AUTOTUNER does not automatically correct the checksum on backup file writes. If any modifications are made to the binaries inside the zip file, checksum correction is required. IMMOOFF17 will correct checksums on all EEPROM and all FLASH, except for TRICORE (MEDC17, MG1).

4) If necessary, proceed with iflash checksum correction.

5) Delete the original IFLASH0.bin and rename your new IFLASH0_IMMOOFF.bin to its old name, IFLASH0.bin.

6) Zip the entire folder again, naming it something like IMMO_OFF_BACKUP.zip. (You can use the extension .zip_noread to skip the complete ECU reread).

7) In the Autotuner software, click on WRITE and select the .ZIP file for the writing process.

Done.

By selecting the FLASH, EEPROM EDITOR will let you know.

1) Make a full read of original ecu, make sure to have "ORI_FLASH.bin" and "ORI_EEPROM.bin" files
2) Make a full read of original replacement ecu, make sure to have "REP_FLASH.bin" and "REP_EEPROM.bin" files
3) Select CLONE, Next, then select files, click NEXT
4) Save new eeprom as "REP_EEPROM_CLONE.bin"
5) Write "REP_EEPROM_CLONE.bin" and "ORI_FLASH.bin" to your replacement ecu
6) Don't forget to change SOFT CODING by OBD using VCDS/VCPK or any appropriate tools.

1) Make a full read of original ecu, make sure to have "ORI_FLASH.bin" and "ORI_EEPROM.bin" files
2) Execute eeprom editor and save decrypted original info by using "Export" button
3) Make a full read of replacement ecu save file as "REP_FLASH.bin" and "REP_EEPROM.bin" files
4) Import decrypted original info by using "Import" button
5) Save this eeprom as "REP_EEPROM_CLONE.bin"
6) Write "REP_EEPROM_CLONE.bin" and "ORI_FLASH.bin" to your replacement ecu
7) Don't forget to change SOFT CODING by OBD using VCDS/VCPK or any appropriate tools.

1) Make a full read of original ecu, make sure to have "ORI_FLASH.bin" and "ORI_EEPROM.bin" files
2) Execute eeprom editor and save decrypted original info by using "Export" button
3) Make a full read of replacement ecu save file as "REP_FLASH.bin" and "REP_EEPROM.bin" files
4) Import decrypted original info by using "Import" button
5) Save this eeprom as "REP_EEPROM_CLONE.bin"
6) Write "REP_EEPROM_CLONE.bin" and "ORI_FLASH.bin" to your replacement ecu
7) Don't forget to change SOFT CODING by OBD using VCDS/VCPK or any appropriate tools.