2024 VW Taigun 1.5 TSI DSG (India)

[Overboost]

Hi,
I own a VW Taigun 1.5 TSI DSG (India) which is essentially a Tcross with lots of cost cutting involved
I got it recently so the modules are SFD locked. I got the unlock code from Vaglogins and VCDS seemed to have unlocked it but when I tried to change adaptation parameters kept getting a security error exception.
I tried keeping the hood open and I tried the security access keys for 017- Instruments module as well, but none of them worked.


any thoughts or anyone who ran into the same issue ?

https://imgur.com/NmWtZtH

 

[AINils]

Coudl you maybe provide an autoscan? I know India is not involved in UNECE, but I think your car is.

 

[Owen in Scotland]

Regardless of VCDS screen status, I doubt you can unlock SFD with VCDS as yet. Ref Uwe's Jan update above, access and unlock still not authorised via VCDS. Best and easiest way to do it currently is with the help of someone who has VAG version of OBD11. Buying OBD11 would be an expensive but guaranteed alternative, but not possibly justified for you if you only use it occasionally, due to annual subscription cost.

 

[Uwe]

I doubt you can unlock SFD with VCDS as yet.

Oh, you can, if you can get a an unlock token "off-line".

However, as AINils stated, it's not possible to address this without seeing a scan from the car.

-Uwe-

 

[Owen in Scotland]

Ah, okay, good to know Uwe thanks. I'd like to try this. Can you outline the process to go through to obtain an "offline" token for VCDS and the supporting scan for us. Thanks. Owen.

 

[Uwe]

Can you outline the process to go through to obtain an "offline" token

Not really. Ross-Tech cannot provide these tokens.

As for how you use them, see:

Ross-Tech: VCDS Tour - SFD

-Uwe-

 

[Overboost]

Coudl you maybe provide an autoscan? I know India is not involved in UNECE, but I think your car is.

Oh, you can, if you can get a an unlock token "off-line".

However, as AINils stated, it's not possible to address this without seeing a scan from the car.

-Uwe-

Apologies for the delay, here is the autoscan from the car.

Wednesday,05,March,2025,08:33:39:35322
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 25.3.0.2 (x64)  HEX-V2 CB: 0.4660.4
Data version: 20250228 DS364.1
www.Ross-Tech.com


VIN: MEXM24CWXRT051124   License Plate:



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: CW-VW27 (2Q0)
Scan: 01 02 03 05 08 09 15 17 19 2B 44 47 5F

VIN: MEXM24CWXRT051124   Mileage: 3871km-2405miles

01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
05-Acc/Start Auth. -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
15-Airbags -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
2B-Steer. Col. Lock -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
47-Sound System -- Status: OK 0000
5F-Information Electr. -- Status: OK 0000
-------------------------------------------------------------------------------
Address 01: Engine (J623-DUMA)       Labels: None
   Part No SW: 05E 906 018 DP    HW: 05E 907 309 BC
   Component: R4 1.5l TFS   H80 2844 
   Revision: 8EH80000    CVN: 9D2D41B9
   Coding: 012500122324090810000000000000000000000000000000
   Shop #: WSC 00000 000 00200
   ASAM Dataset: EV_ECM15TFS01105E906018DP 004002
   ROD: EV_ECM15TFS01105E906018DP_VW27.rod
   VCID: 76B5F73FF84FA21AA5D-8022
   VINID: 755A1D0844E7A2290014104210E0B90521

No fault code found.
Readiness: 0000 0000

-------------------------------------------------------------------------------
Address 02: Auto Trans (J743)       Labels: 0CW-927-769.clb
   Part No SW: 0CW 300 020 L    HW: 0AM 927 769 N
   Component: GSG DQ200G2_M H07 2203 
   Revision: 00007009    Serial number: 5ZV02402053356 CVN: 468413A7
   Coding: 0014
   Shop #: WSC 17734 418 534600
   ASAM Dataset: EV_TCMDQ200021 001001
   ROD: EV_TCMDQ200021.rod
   VCID: 3B23260B83ED3F729A3-806E

No fault code found.

-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104)       Labels: None
   Part No SW: 5QP 614 517     HW: 2Q0 614 517 L
   Component: ESC_base      H13 0201 
   Serial number: 17601312240924
   Coding: 9A058B645F4659AED1FDFA1872DE42A649B6B106336A262424541254454E4265926D8D60CC566424242A482AA231D6431F8C6BC2F8A8AC5015350A
   Shop #: WSC 00793 648 00200
   ASAM Dataset: EV_Brake1BOSCHESPMQBA0 005001
   ROD: EV_Brake1BOSCHESPMQBA0_005_VW27.rod
   VCID: 0E45BFDFE0DFFADA0DD-805A

No fault code found.

-------------------------------------------------------------------------------
Address 05: Acc/Start Auth. (J518)       Labels:* None
   Part No SW: 3Q1 959 435 C    HW: 3Q1 959 435 C
   Component: VWKESSYMQB    037 1501 
   Revision: 00037000    Serial number: 0648760814 Dataset Number: V03935393KK 0001
   Coding: 032C0C0723
   Shop #: WSC 00793 648 00200
   ASAM Dataset: EV_KessyHellaMQBAB 004056
   ROD: EV_KessyHellaMQBAB_VW27.rod
   VCID: 3B23260B83ED3F729A3-806E

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J255)       Labels:* None
   Part No SW: 6JM 907 057 C    HW: 6JM 907 057 C
   Component: Climatronic   035 0215 
   Coding: 012100001400003101000400004011050101350000000000000000000000
   Shop #: WSC 00793 648 00200
   ASAM Dataset: EV_ACClimaBHBMQBA0Touch 001008
   ROD: EV_ACClimaBHBMQBA0Touch.rod
   VCID: 4CC175D7D64388CA239-8018

No fault code found.

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels: None
   Part No SW: 2Q0 937 089 F    HW: 2Q0 937 089 F
   Component: BCM A0 Std    H15 0982 
   Serial number: 014251024A0092 Dataset Number: V03935441JZ 0001
   Shop #: WSC 00000 000 00000
   ASAM Dataset: EV_BCMA0 209001
   ROD: EV_BCMA0_209_VW27.rod
   VCID: 3D2728139DF93142A47-8068 SFD

   Rain/Light Recognition Sensor:
   Subsystem 1 - Part No SW: 5Q0 955 559 C    HW: 5Q0 955 559 C  Labels: 5Q0-955-547.CLB
   Component: RLS  054 0206
   Serial number: S2Y24M08D07H01M38S12
   Coding: 00184D

   Driver door control module:
   Subsystem 2 - Part No SW: 5QR 959 801 C    HW: 5QR 959 801 A
   Component: FHSG_DRV  003 0012
   Serial number: AP0883RHNA3724000115
   Coding: 0D2203

   Rear Driver Side Door Control Module:

   Rear Passenger Door Control Module:

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags (J234)       Labels:| 2Q0-959-655.clb
   Part No SW: 2Q0 959 655 AP    HW: 2Q0 959 655 AP
   Component: VW22Airbag    020 0511 
   Revision: --------    Dataset Number: V03935398ST 0001
   Coding: 88CCC000000000007C540000008840000065
   Shop #: WSC 00793 648 00200
   ASAM Dataset: EV_AirbaVW22BPAVW27X 001036
   ROD: EV_AirbaVW22BPAVW27X.rod
   VCID: 0B43B6CB93CDCFF2EA3-805E

   Crash sensor for side airbag: driver side:
   Subsystem 1 - Part No SW: -----------    HW: 442 061 207 24
   Component: SideSensor_Df  1E2 0887
   Serial number: 3577Y209D155ED232174
   Coding: 2D2D2D

   Crash sensor for side airbag: passenger side:
   Subsystem 2 - Part No SW: -----------    HW: 442 061 207 24
   Component: SideSensor_Pf  1E2 0887
   Serial number: 3587Y209B146CCD303FJ
   Coding: 2D2D2D

   Rear Side Airbag Crash Sensor (on driver's side):
   Subsystem 3 - Part No SW: -----------    HW: 442 0B2 906 24
   Component: SideSensor_Dr  1C7 0148
   Serial number: 3517736069E527AAF6E1
   Coding: 2D2D2D

   Passenger side rear thorax airbag crash sensor:
   Subsystem 4 - Part No SW: -----------    HW: 442 0B2 906 24
   Component: SideSensor_Pr  1C7 0148
   Serial number: 3527734189E527A7167M
   Coding: 2D2D2D

   Crash sensor for front airbag: driver side:
   Subsystem 5 - Part No SW: -----------    HW: 442 131 007 24
   Component: FrontSensor_D  290 118A
   Serial number: 355AG13ACAEDF2350266
   Coding: 2D2D2D

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels:| 5G0-920-XXX-17.clb-SRI3
   Part No SW: 2GP 920 310 D    HW: 2GP 920 310 D
   Component: KOMBI         075 5882 
   Coding: 252400182180000C02082A001000000000000509
   ASAM Dataset: EV_DashBoardJCIMQBAB 012005
   ROD: EV_DashBoardJCIMQBAB_012_VW27.rod
   VCID: 3C21251786E3384A939-8068 SFD

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels:* Redir Fail!
   Part No SW: 2Q0 909 901 G    HW: 2Q0 937 089 F
   Component: GW MQB A0     H15 0982 
   Serial number: 014251024A0092
   Coding: 030100042F00570000000000000F00010000000000000000000000000000
   Shop #: WSC 00793 648 00200
   GVL: 01403C0000000600400000000080C80000000000000000000000000000000000
   ASAM Dataset: EV_GatewA0 013028
   ROD: EV_GatewA0_VW27.rod
   VCID: 3635373FB8CFE21A65D-8062

   Generator:
   Component: 4-00-12-00-04 

   Multifunction steering wheel control module:
   Subsystem 2 - Part No SW: 3G0 959 442 AA    HW: 3G0 959 442 AA  Labels: 3C8-959-537.CLB
   Component: E221__MFL-YLG  H07 0120
   Serial number: YLG-0700084270242334
   Coding: 292C00

   Battery Monitoring Control Module:
   Subsystem 3 - Part No SW: 2Q0 915 181 B    HW: 2Q0 915 181 B
   Component: J367-BDMBOSCH  H03 2012
   Serial number: 1050B67B           

No fault code found.

-------------------------------------------------------------------------------
Address 2B: Steer. Col. Lock (J764)       Labels:. 3WA-905-861.clb
   Part No SW: 3WA 905 861     HW: 3WA 905 861
   Component: ELV-MQB_UNECE H05 0063 
   Serial number: 24000171423015
   Coding: 0808000000000000
   Shop #: WSC 00793 648 00200
   ASAM Dataset: EV_ELVMarqUNECE 003006
   ROD: EV_ELVMarqUNECE_003_VW27.rod
   VCID: 084989C782BBA4EAC71-805C SFD

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist (J500)       Labels:. 2Qx-909-144-V3.clb
   Part No SW: 5QR 909 144 C    HW: 5QR 909 144 A
   Component: EPS_ECU       430 4250 
   Serial number: 000026.08.24000 Dataset Number: V03935408NP 0001
   Coding: 00000000000000000101020101000100000001010101
   ASAM Dataset: EV_SteerAssisNSKGEN3MQB 004008
   ROD: EV_SteerAssisNSKGEN3MQB.rod
   VCID: 56F597BF188FC21A85D-8002

No fault code found.

-------------------------------------------------------------------------------
Address 47: Sound System (J525)       Labels:* None
   Part No SW: 5Q6 035 456     HW: 5Q6 035 456
   Component: KonzernAmp 8K H01 2427 
   Revision: --------    Serial number: A1117A00318584 Dataset Number: V03935410BD 0001
   Coding: 0302000000AAAA00000000000000
   Shop #: WSC 00793 648 00200
   ASAM Dataset: EV_AMPCAN8C1PASE 001015
   ROD: EV_AMPCAN8C1PASE_VW27.rod
   VCID: 73B3CE2BEB3DB732823-8026

No fault code found.

-------------------------------------------------------------------------------
Address 5F: Information Electr. (J794)       Labels:| 2GM-035-MIB-REG.clb
   Part No SW: 6JR 035 180     HW: 6JR 035 180
   Component: MU-R--R2      H04 0709 
   Serial number: VWZ7Z2C9103373  Dataset Number: V03935436RG 0001
   Coding: 22162608000000000000000000000000000000000000000000
   ASAM Dataset: EV_MUREGIO 001010
   ROD: EV_MUREGIO.rod
   VCID: 03539EEBBB9D87B2923-8056

No fault code found.

End----------(Elapsed Time: 00:54, VBatt start/end: 12.2V/12.2V)-----------
---------------------------No fault code found.----------------------------

 

[Sebastian]

Thanks for the scan. An interesting case, produced in Pune for the Indian market. A MY 2024 even though it was produced 12/2024 (and should be MY 2025 under normal circumstances). No UNECE per VIN/PR list, but SFD for 09 and 17, 2B.

Please run control module maps for #19 (MVB & ADP) as well as #17 (MVB & ADP) and attach/post them here. Also, which adaptation channels did you try to alter exactly in #17?

 

[Overboost]

Thanks for the scan. An interesting case, produced in Pune for the Indian market. A MY 2024 even though it was produced 12/2024 (and should be MY 2025 under normal circumstances). No UNECE per VIN/PR list, but SFD for 09 and 17, 2B.

Please run control module maps for #19 (MVB & ADP) as well as #17 (MVB & ADP) and attach/post them here. Also, which adaptation channels did you try to alter exactly in #17?

Hi, actually it is a MY24 car, was the last shipment out of the factory in Dec 2024.

Did you want me to run the control module maps for 19 and 17 or 09 Central Elect and 17 Instruments please?

Btw I tried the following adaptations from 09 and 17 :

RPM Bar display in Virtual Cockpit	17 - Instruments​	IDE12211-China variant​
Disable 80/120 speed warning	17 - Instruments​	IDE14220-Vehicle speed warning for India​

Lane change indicator

09 - Cent. Elect.

ENG115854-Außenlicht_Blinker-Komfortblinken_Blinkzyklen​

Tear drop wipe

09 - Cent. Elect.

ENG149242-Windshield wiper-Traenenwischen_Front_Status​

 

[PetrolDave]

even though it was produced 12/2024 (and should be MY 2025 under normal circumstances).

​

Hi, actually it is a MY24 car, was the last shipment out of the factory in Dec 2024.

Usually the Model Year changes in around July of the year before, so usually MY25 vehicles are produced from around July 2024 onwards - seems yours is unusual if it is a MY24 vehicle.

It could be useful if you post either the VIN or an unedited Auto-Scan to clarify this?

 

[Uwe]

Usually the Model Year changes in around July of the year before, so usually MY25 vehicles are produced from around July 2024 onwards

There are occasional exceptions. For example, we had MY 2006 Jetta TDIs here that were made in December of 2006 because emissions regulations changed for MY 2007.

I'm not sure what the reason behind this is, but MEXM24CWXRT0xxxxx is definitely a MY 2024.

-Uwe-

 

[Overboost]

Thanks for the scan. An interesting case, produced in Pune for the Indian market. A MY 2024 even though it was produced 12/2024 (and should be MY 2025 under normal circumstances). No UNECE per VIN/PR list, but SFD for 09 and 17, 2B.

Please run control module maps for #19 (MVB & ADP) as well as #17 (MVB & ADP) and attach/post them here. Also, which adaptation channels did you try to alter exactly in #17?

Hi, actually it is a MY24 car, was the last shipment out of the factory in Dec 2024.

Did you want me to run the control module maps for 19 and 17 or 09 Central Elect and 17 Instruments please?

Btw I tried the following adaptations from 09 and 17 :

RPM Bar display in Virtual Cockpit	17 - Instruments​	IDE12211-China variant​
Disable 80/120 speed warning	17 - Instruments​	IDE14220-Vehicle speed warning for India​

Lane change indicator

09 - Cent. Elect.

ENG115854-Außenlicht_Blinker-Komfortblinken_Blinkzyklen​

Tear drop wipe

09 - Cent. Elect.

ENG149242-Windshield wiper-Traenenwischen_Front_Status​

Hi @Sebastian can you please help me with the modules you would like me to map out?

 

[PetrolDave]

Usually the Model Year changes in around July of the year before, so usually MY25 vehicles are produced from around July 2024 onwards - seems yours is unusual if it is a MY24 vehicle.

There are occasional exceptions. For example, we had MY 2006 Jetta TDIs here that were made in December of 2006 because emissions regulations changed for MY 2007.

I owned an exception to this too, a MY2007 B7 RS4 that was built in June 2006 before the factory shutdown.

 

[Overboost]

I owned an exception to this too, a MY2007 B7 RS4 that was built in June 2006 before the factory shutdown.

Ok let me put some perspective wrt to the Indian scene. So yes the practice has been manufacturing and parking cars in July every year. They are stamped with next year MY VIN as they get shipped in Jan, next MY. But VW and rather all manufacturers have been in a financial soup here in India between 2024-25. They were overloaded with inventory and needed to recover money from the market deperately. The inventory load was a record high for the decade! Even the car I rejected before taking this 1, was a October 2024 VIN.

 

[NEtech]

Did you want me to run the control module maps for 19 and 17 or 09 Central Elect and 17 Instruments please?

Please run control module maps for #19 (MVB & ADP) as well as #17 (MVB & ADP) and attach/post them here.

[Applications]
[Controller Channel Map]
- Controller Address = 19
- Login or security code: Leave blank
- Function: Measuring values And Adaptations
- Output: CSV file
[Go]

Then once again, and write: 17 (instead of 19) for Controller Address

Files are placed in C:\Ross-Tech\VCDS\Logs

 

[Overboost]

[Applications]
[Controller Channel Map]
- Controller Address = 19
- Login or security code: Leave blank
- Function: Measuring values And Adaptations
- Output: CSV file
[Go]

Then once again, and write: 17 (instead of 19) for Controller Address

Files are placed in C:\Ross-Tech\VCDS\Logs

Hi i have uploaded the Zip file with the CSVs to the following link :
CC : @Sebastian

CSV Zip File - Channel Maps

 

[Sebastian]

The map supports the initial assessment, implying that while a general filter exists, this should be purely mechanical (i.e. pop the hood). Since your Gateway does not support SFD, there would also be no additional unlocking required and you should be able to modify this purely by unlocking the instrument cluster and then changing things there.

According to your previous statements, you tried to modify channels in #17 and #09. While those channels in #17 (which you had SFD unlocked according to your screenshot and you claim that the hood was open as well and therefor the firewall inactive) are still not standard channels, it is possible that these cannot be altered purely because your unlock role/permission isn't high enough.

These roles correlate to previously used different security access codes, which also gave different permission sets to the user. Yes, one could try and play with diagnostic modes (end of line, developer etc.) here, but I am not sure I understand the use case and/or benefit of tweaking these specific channels in the first place. If you can, please enlighten us what benefit it would have to tweak those and what your desired values would be.

You also mentioned failing adaptation changes in #09, which seemed reasonable to alter to me. Did you also unlock SFD in #09? Was the hood also open at the time of your attempts?

 

[Overboost]

The map supports the initial assessment, implying that while a general filter exists, this should be purely mechanical (i.e. pop the hood). Since your Gateway does not support SFD, there would also be no additional unlocking required and you should be able to modify this purely by unlocking the instrument cluster and then changing things there.

According to your previous statements, you tried to modify channels in #17 and #09. While those channels in #17 (which you had SFD unlocked according to your screenshot and you claim that the hood was open as well and therefor the firewall inactive) are still not standard channels, it is possible that these cannot be altered purely because your unlock role/permission isn't high enough.

These roles correlate to previously used different security access codes, which also gave different permission sets to the user. Yes, one could try and play with diagnostic modes (end of line, developer etc.) here, but I am not sure I understand the use case and/or benefit of tweaking these specific channels in the first place. If you can, please enlighten us what benefit it would have to tweak those and what your desired values would be.

You also mentioned failing adaptation changes in #09, which seemed reasonable to alter to me. Did you also unlock SFD in #09? Was the hood also open at the time of your attempts?

Thank you so much for looking into the logs and taking the time to help me.

So for #17

RPM Bar display in Virtual Cockpit	17 - Instruments	IDE12211-China variant
Disable 80/120 speed warning	17 - Instruments	IDE14220-Vehicle speed warning for India

The RPM Bar is more of a convenience feature which lays out the RPM bar at the top of the Virtual Cockpit so that all information is available in the same screen:

While the 2nd adaption is pretty important and serious. So in India they have put this horrible speed chime which cannot be customised in terms of volume or tone used for the chime. Its extremely loud and my family member who has a bad case of migraine finds it very difficult to travel as this loud constant chime triggers her migraine horribly.

About Channel 09, I didnt try to unlock that since once the SFD unlock for Channel 17 didnt help me update the parameters, I thought of reaching out to you folks since each unlock costs me a bit of money. But I did confirm with some other coders that they weren't able to update parameters in Channel 09 as well.

So these are the adaptions I wanted to enable from Intrument #17 :

Functional Change	Control Module	Channel​	OE Value	New Value​
RPM Bar display in Virtual Cockpit	17 - Instruments​	IDE12211-China variant​	No	Yes
Disable 80/120 speed warning	17 - Instruments​	IDE14220-Vehicle speed warning for India​	Yes	No
Wheel angle in Virtual Cockpit	17 - Instruments​	MAS01299-Offroad​	No display	Readout
Display Volume to be replenished in Virtual Cockpit	17 - Instruments​	Long Coding - Byte 10, Bit 4 - Check box​	Not Checked	Check

 

[Overboost]

Hi @Sebastian any guidance with my case please? you had mentioned about roles assigned for different access codes. Is there any specific Security Access code that I can try?

 

[Overboost]

@Uwe @Sebastian Can someone please help me with this request?