GM Module Programming Fails Through SPS2 / Techline Connect: Where to Start
When a GM module flash fails through SPS2 or Techline Connect, the cause is almost always one of five things. This guide tells you which one you're looking at and where to fix it.
When a GM module flash fails partway through SPS2 or Techline Connect, the module itself is rarely the cause. GM programming failures almost always come down to one of five things, and each has a dedicated fix. Use this page to identify which one you're dealing with, then follow the linked article for the full procedure. Most "programming failed" tickets are resolved by working these in order - communication and voltage first, because they cause the majority of mid-flash failures.
1. Communication faults / U codes on the vehicle
This is the most common cause. While programming, the target module talks to other modules on the network — if the vehicle already has communication faults, the flash fails. Errors E4399 and UEH101, or modules dropping offline mid-flash, all point here.
What to do: scan the whole vehicle for DTCs and repair any U codes (communication codes) before reprogramming. Don't retry the flash until the network scans clean. Full procedure: Techline Connect Error Codes E4399 / UEH101 - Diagnostic Procedure - https://knowledgebase.aetools.us/techline-connect-error-codes-e4399-/-ueh101-diagnostic-procedure
2. Battery voltage drop during the flash
A voltage drop mid-flash will fail the programming and can damage the module. This is the cause when a flash dies at a consistent percentage every time. What to do: connect a battery maintainer and hold stable voltage throughout the flash - not a trickle charger.
Full procedure: Battery maintainer best practices for ECU and ECM flashing - https://knowledgebase.aetools.us/-why-you-should-always-use-a-battery-maintainer-while-flashing
3. Unsupported or under-spec laptop
GM programming requires Windows 11 Pro and adequate RAM. On Windows 10 / Windows 11 Home, or an under-spec machine, programming may start and then fail.
What to do: confirm the laptop meets GM's requirements; upgrade or replace if it doesn't. Full procedure: Windows 11 Pro requirements for AE Solutions diagnostic software - https://knowledgebase.aetools.us/windows-11-pro-requirements-for-ae-solutions-diagnostic-software
Setup reference: Installing GM Techline Connect on a New Laptop - Complete Setup Guide - https://knowledgebase.aetools.us/installing-gm-techline-connect-on-a-new-laptop-complete-setup-guide
4. Older GM vehicle (tool/module speed mismatch)
Older GM vehicles communicate at slower speeds than modern J2534 tools expect, so the handshake fails and the flash aborts. This is the cause when programming repeatedly fails on an older vehicle specifically.
What to do: use the AEZ Flasher 3 with the reset-and-jumper procedure for older GM vehicles.
Full procedure: Why Does My GM Programming Keep Failing on Older Vehicles? Root Cause and Fix Using AEZ Flasher 3 - https://knowledgebase.aetools.us/-why-does-my-gm-programming-keep-failing-on-older-vehicles
5. MDI / MDI 2 firmware or drivers
If the MDI isn't detected, won't communicate, or stalls at "reading vehicle data," the interface firmware or drivers are usually behind.
What to do: reinstall the MDI drivers and update the firmware through GM MDI Manager.
Full procedure: GM MDI / MDI 2 Won't Connect to Vehicle - Driver Reinstall and Compatibility Fix - https://knowledgebase.aetools.us/gm-mdi-/-mdi-2-wont-connect-to-vehicle-driver-reinstall-and-compatibility-fix
If the module appears bricked after a failed flash
A module that looks bricked after a failed flash can often be recovered. Stabilize the battery voltage and reattempt programming - SPS2 may detect the partially-flashed module and offer a recovery path. If no recovery is offered, call AE Tools at 913-856-6678; additional GM-side recovery procedures may apply before the module is considered failed.