Skip to main content
NEW New Dedicated KIA Support Portal Are you a KIA customer?
Go to KIA Support Portal →

VCI II(2) Troubleshooting - Connection, Firmware, Power, Communication & Repair Guide

Oscar Eom
Updated

Overview

This guide provides troubleshooting procedures and hardware repair (RMA) criteria for the official vehicle diagnostic interface VCI II(2) (serial number prefix: NHD, NGD) used with diagnostic applications (GDS Smart / KDS 2.0 / GENESIS Smart).

It helps technicians quickly determine whether wireless connection drops, device detection failures, vehicle communication errors, firmware update interruptions, or power issues can be resolved through self-service steps on site, or whether official hardware repair is required.

Applicable Hardware Scope:

  • Applicable Serial Number Prefix: NHD (Hyundai Overseas), NGD (Kia Overseas)
  • Supported Diagnostic Software: GDS Smart, KDS 2.0, GENESIS Smart

If the issue persists after completing the self-service checks and hardware inspection is required, please submit your VCI II(2) for service in accordance with our official Repair Process & Policies.

On this page

1. Wireless (Wi-Fi Direct / Bluetooth) Pairing Failure & Device Not Detected in Diagnostic App

Symptom: VCI II(2) does not appear in the device connection list inside the diagnostic application (GDS Smart / KDS 2.0 / GENESIS Smart) despite being plugged into the vehicle OBD port, VCI II(2) does not appear in the tablet's Android Bluetooth search, pairing hangs or displays an error pop-up, or the wireless connection drops intermittently during diagnosis.

Self-Service Workaround (try these steps in order before requesting repair):

  1. Verify Default Bluetooth Pairing PIN Code:
    When connecting via Bluetooth manually or pairing for the first time, the security PIN code is 0701 (confirm that you are not entering 0000 or 1234).
  2. Unpair Existing Bluetooth Device on Tablet:
    On the tablet PC, navigate to [Settings → Connections → Bluetooth], select any registered VCI II(2) device (NHD*, NGD*), and Unpair (Forget) it.

  3. [Key Step] Clear Communication Service App (GITMCommManager.Service) Data & Cache:

    If the VCI II(2) is properly connected to the vehicle OBD port but fails to appear in the available device list of the diagnostic application, temporary service data corruption in the Android background communication service GITMCommManager.Service may be causing the issue. Follow the steps below to clear its data and cache:

    Important: Communication Manager Service App Reset Procedure

    1. Open the Android Settings app on the tablet PC.
    2. Navigate to Apps (or Applications).
    3. Search for and select GITMCommManager.Service App (or GITMCommManagerService).
    4. Under Permissions, confirm that Nearby devices, Location, and Bluetooth permissions are all set to [Allow].
    5. Tap Storage.
    6. Tap Clear data and Clear cache.

  4. Reboot Tablet PC and Reconnect VCI II(2):

    After clearing the data and cache, you must reboot the tablet PC. With the vehicle ignition ON (IG ON), disconnect the VCI II(2) from the OBD port, reconnect it firmly, and then search and connect in the diagnostic application under [Configuration → Device Manager → VCI II].

  5. Cross-Check with Dedicated USB Cable (Direct Wired Connection):

    If wireless connection continues to fail, connect the VCI II(2) and the tablet PC directly using the dedicated USB wired cable to verify whether the device is recognized in the diagnostic application.

When to Request Repair (Hardware Fault Criteria):

  • VCI II(2) is not detected wirelessly or pairing fails across multiple different tablets even after clearing GITMCommManager.Service data/cache and rebooting the tablet
  • Direct wired connection via the dedicated USB cable also fails to recognize the device on the tablet
  • The wireless connection drops within a few seconds of connecting and the top LED on the VCI II(2) repeatedly blinks red

If any of the above symptoms persist, the internal wireless board (wireless communication module) requires replacement. Please submit your device following the Official Repair Submission Guide.

Back to top

2. Power Failure, No Boot & LED Status Indicator Meanings

Symptom: VCI II(2) does not power on when connected to the vehicle OBD port, no startup beep sound is heard, or VCI II(2) intermittently resets/loses power when the OBD connector is lightly touched or moved.

Before Requesting Repair, Confirm the Following:

  1. Cross-Check on Another Vehicle: Connect the VCI II(2) to another normal vehicle's OBD port to determine whether the power supply issue is specific to the vehicle's OBD terminal or a defect in the VCI II(2) unit.
  2. Check Vehicle OBD Fuse: Check the vehicle-side OBD-II port power fuse for a blown fuse (refer to the vehicle workshop manual).
  3. Check Connector Movement: With the VCI II(2) plugged into the OBD port, if lightly moving the connector body causes the power to turn off or the LED to flicker, there is an internal connector solder joint contact defect that cannot be repaired by the user.

VCI II(2) LED Status Indicator Colors and Actions

LED Color Status Meaning Action
White VCI II(2) is powered on but not yet connected to the tablet. If this is the first-time setup or if communication fails, navigate to [Configuration → Device Manager] to establish the connection.
Green VCI II(2) is successfully connected to the tablet and communicating with the vehicle. No action needed; the device is functioning correctly.
Red VCI II(2) has lost communication. Disconnect the VCI II(2) from the vehicle OBD-II connector, wait a few moments, and then reconnect it.
Blue VCI II(2) is performing an ECU upgrade. Allow the upgrade process to complete without interruption.
Yellow VCI II(2) is in Flight Record mode, communicating only with the Trigger Module and not the tablet. To resume communication with the tablet, disconnect the Trigger Module from the vehicle power outlet (cigar jack).

When to Request Repair (Hardware Fault Criteria):

  • VCI II(2) does not power on in any vehicle or no startup beep sound is heard at all
  • VCI II(2) intermittently loses power when the OBD connector is lightly touched or the cable is moved (internal power board or connector solder joint defect)

Power-related hardware defects require internal power board inspection and re-soldering repair. Please submit your device following the Official Repair Submission Guide.

Back to top

3. Vehicle Communication (CAN/OBD) Failure & DoIP (Ethernet) Limitation Notice

Symptom: VCI II(2) connects normally to the tablet via wireless or USB, but cannot communicate with the vehicle, Auto VIN recognition fails, ECU search displays unsupported systems, or a "Vehicle Communication Error" pop-up appears during diagnosis.

Self-Service Workaround:

  1. Confirm that the vehicle ignition switch is in the ON (IG ON) position (many controllers do not communicate in ACC mode).
  2. Verify that the vehicle battery voltage is stable.
  3. Check the vehicle's OBD port and VCI II(2) connector pins for bent pins, debris, or poor contact.
  4. Connect the VCI II(2) to a different normal vehicle to isolate whether the issue is vehicle-specific or a VCI II(2) hardware fault.

[Mandatory Warning] Do NOT Send VCI II(2) for Repair Due to DoIP (Ethernet) ECU Upgrade Failures

  • VCI II(2) Hardware Specification Limitation:
    VCI II(2) does not have built-in Ethernet (DoIP) communication. DoIP (Ethernet)-based ECU upgrades (such as CCU or infotainment) cannot be performed using a standalone VCI II(2) over wireless (Wi-Fi Direct / Bluetooth).
  • Required Equipment:
    To perform Ethernet-based ECU upgrades, you must connect an external ECI communication adapter module or use a VCI3 (VCI III) diagnostic interface, which natively supports DoIP.
  • Preventing Unnecessary Repair Submissions:
    Communication failure during an Ethernet (DoIP) ECU upgrade is not a VCI II(2) hardware fault. If you submit the device for repair due to this reason, it will be judged as No Trouble Found (Normal), and inspection fees and round-trip shipping costs may be charged.

When to Request Repair (Hardware Fault Criteria):

  • Under IG ON and stable battery voltage conditions, basic CAN/OBD diagnostic communication and Auto VIN recognition consistently fail across multiple different normal vehicles (possible internal CAN transceiver IC fault)
  • The OBD connector pins on the VCI II(2) are visibly bent or broken

Back to top

4. Firmware Update Error & Interrupted Update Recovery

Symptom: During a VCI II(2) firmware update in the diagnostic application (GDS Smart / KDS 2.0 / GENESIS Smart), the progress bar stops at a certain percentage or displays a failure pop-up, or the device does not operate normally after an interrupted update.

Important: Firmware Update Stability Precautions

  • Wired USB Connection Recommended: Performing firmware updates over a wireless (Bluetooth / Wi-Fi Direct) connection carries a risk of packet loss. Always connect the tablet and VCI II(2) directly using the dedicated USB wired cable.
  • Maintain Stable Power Supply: Do not disconnect the device from the OBD port or turn off the vehicle ignition (IG ON) during the update.

Firmware Update Retry Procedure:

  1. Completely close the running diagnostic application on the tablet PC.
  2. Firmly connect the VCI II(2) to the vehicle OBD port to supply power (keep IG ON), and connect it directly to the tablet using the dedicated USB cable.
  3. Launch the diagnostic application (GDS Smart / KDS 2.0 / GENESIS Smart).
  4. Navigate to [Configuration → Device Manager → Select VCI II → Update] in order, and retry the firmware update from the beginning over the wired connection.
  5. Once the update starts after confirming the OK pop-up, do not operate the tablet or disconnect the device until it completes.

When to Request Repair (Hardware Fault Criteria):

  • Firmware update via the dedicated USB wired connection and stable power environment repeatedly fails at the same progress point
  • VCI II(2) does not power on or is not recognized at all in the diagnostic application after an interrupted update (internal flash memory or mainboard damage)

Back to top

5. Physical Damage, Cracked Case & Warranty Seal Policy

Symptom: Cracked or broken outer housing/case due to drops or external impact during service work, broken OBD connector pins, damaged USB port, or internal damage caused by water, oil, or cleaning fluid ingress.

Caution: Paid Repair Criteria & Prohibition of Unauthorized Disassembly

  • Malfunctions or physical damage caused by user carelessness (drops, impact, breakage, liquid ingress) or unauthorized disassembly/modification are excluded from free warranty coverage even within the warranty period and will be processed as paid repairs.
  • If the security seal label on the VCI II(2) body is damaged or there are signs that the case was arbitrarily disassembled, the unit may be excluded from warranty repair. Do not disassemble the unit yourself; please submit it for official repair.

Back to top

Quick Reference Table

Symptom Try Self-Service Check First When Hardware Repair Submission Is Required
Wireless pairing failure / Not detected in diagnostic app Confirm PIN 0701, clear GITMCommManager.Service data/cache and reboot tablet, check dedicated USB cable connection Not detected across multiple tablets after reboot, wired USB connection also fails (wireless board replacement required)
No power / Power turns off when moved Cross-check on another normal vehicle OBD port, check vehicle OBD power fuse, check connector movement No power in any vehicle, no startup beep, power turns off when connector is moved (power board replacement or re-soldering required)
Vehicle communication failure / Auto VIN failure Confirm vehicle IG ON and battery voltage, inspect OBD connector pins for bending/debris, cross-check on another vehicle Basic CAN diagnostic communication consistently fails across multiple vehicles (internal CAN IC or mainboard repair required)
DoIP (Ethernet) ECU upgrade failure Not eligible for repair submission. VCI II(2) does not support built-in DoIP; connect an external ECI adapter or use VCI3 (VCI III) Not a VCI II(2) hardware defect. Submitting for repair may incur inspection fees and shipping costs.
Firmware update error / Interrupted Direct dedicated USB wired connection + vehicle IG ON, then retry via [Configuration → Device Manager → VCI II → Update] Repeatedly fails at the same point over wired connection, fails to boot/recognize after update (flash memory or board repair required)
Physical damage / Liquid ingress / Broken connector pins No self-service workaround (do not disassemble) Immediate official repair submission required (user-induced damage is processed as paid repair)

Back to top

Official Repair (RMA) Submission Guide

If the issue persists after completing the on-site checks and hardware inspection/repair is required, please submit your VCI II(2) through the official regional channel below:

  • Official Escalation & RMA Channel: Authorized dealers must submit repair requests through their regional Distributor / NSC, which forwards the device to the designated regional GIT entity: GIT America (GITA) for North America (United States & Canada) (Dealer → Distributor / NSC → GIT).
  • Detailed Procedures & Customs Rules: For regional return shipping addresses, Commercial Invoice requirements (marking Product Serial Number, "For Repair", Declared Value under USD 100, and DAP Incoterms), please refer to the official Repair Process & Policies article.

Back to top

Related articles

Comments

0 comments

Please sign in to leave a comment.