DCCTools :: Knowledgebase
Search:     Advanced search

ECU Flash Failure: What to do Next?

Article ID: 118
Last updated: 11 Oct, 2013

When the initial attempt to perform an ECU Flash fails, the following steps should resolve the issue:
 
 
  1. Read all available service documentation (SBs, RRTs, Recalls) from the wiTECH Diagnostic Application to ensure that the flash applies to the connected vehicle. 
    1. This step should actually be done before making any flash attempts. If this was not done, the documentation should be reviewed after an initial flash attempt has failed.
    2. Click the View Service Info button next to the flash file name. The available service documentation will be displayed in a new table that appears below.
 
  1. Ensure that your wiTECH Diagnostic Application and scan tool (wiTECH VCI Pod or StarMOBILE) operating systems are up to date.
    1. View the latest Release Notes (http://kb.dcctools.com/index.php?CategoryID=24) page to determine the latest versions available.
    2. If your wiTECH Diagnostic Application or scan tool operating system are out of date, update them to the latest version(s) and attempt the ECU flash again.
  2. Review all available KB articles that may be related to the particular flash failure you are experiencing. We make every attempt to document known flash issues that the field may be experiencing.
  3. Ensure that the PC running the wiTECH Diagnostic Application is connected to the wiTECH Access Gateway’s wireless or wired network. Ensuring your PC is connected to the wiTECH wireless network will help minimize your risk of being disconnected during a flash session.
  4. Try using a wired network connection to eliminate any potential wireless networking issues. Examples of wired network connections for PCs and scan tools are explained below:
    1. Use an Ethernet cable to connect your PC directly to the wiTECH Access Gateway utilizing one of the wiTECH Access Gateway Ethernet ports (1 through 4). These ports are clearly labeled on the wiTECH Access Gateway.  
    1. Use an Ethernet cable to connect either your wiTECH VCI Pod or StarMOBILE device to the wiTECH Access Gateway by utilizing another wiTECH Access Gateway Ethernet port (1 thru 4). Make sure you change the network settings on the scan tool so that the wired network connection is being used.
 
  1. Restart the wiTECH Diagnostic Application, choose the appropriate device from the Connection Wizard, and attempt the flash again.
 
IMPORTANT NOTE: If you suspect you are having wireless issues, please call the wiTECH Premium Support Help Desk at 1-888-wiTECH-1 (1-888-948-3241) to help address any issues you may be experiencing.
 
  1. If you are still unable to successfully flash the ECU, please contact the wiTECH Premium Support Help Desk at 1-888-wiTECH-1 (1-888-948-3241) for further assistance.
 
 

 

Article ID: 118
Last updated: 11 Oct, 2013
Revision: 1
Views: 20345
Comments: 0
Posted: 23 Mar, 2010 by Rickman B.
Updated: 11 Oct, 2013 by Merriam L.
This article was:   Helpful | Not helpful
Also read
document GPEC PCM Flash (Reprogramming) Failure: “No Response Received from Start Diagnostic Session Extended Request”
document Flash Process Failed: Could Not Open Required Hardware Channel to Vehicle
document 2006 KJ Diesel TCM: wiTECH Diagnostic Application Freezes at “Turn Key to Off then to Run” when Using the wiPOD VCI Device
document CCN Flash Process Failed: No Response Received from Start Diagnostic Session Extended Request
document 2010 RT Cabin Compartment Node (CCN) Flash (Reprogramming) Failure: “No response received from Start Diagnostic Session Extended request,” CCN Unresponsive After Flash Failure
document Sprinter Electronic Shift Module (ESM) Known Flash Reprogramming Failure: Negative Response 0x22
document 2007/2008 WK/XK (Grand Cherokee, Commander) Driver & Passenger Door Module (DDM & PDM) Flash Reprogramming Failure
document 2007/2008 WK/XK (Grand Cherokee, Commander) Heating, Ventilation, & Air Conditioning (HVAC) ECU Flash Failure
document Sprinter ECM (Engine Control Module) flash reprogramming failure
document 2007-2010 JK (Wrangler) KA (Nitro) Cabin Compartment Node (CCN) Flash (Reprogramming) Process Failed
document 2009-2010 DS/DX Ram 1500 Cabin Compartment Node (CCN) Flash (Reprogramming) Process Failed
document Diesel 2009 JC (Journey) & JS (Avenger/Sebring) Transmission Control Module (TCM) Flash (Reprogramming) Process Failed
document U1601 Electronic Control Unit (ECU) Application Software Code 1 Missing OR Corrupted After Flashing (Reprogramming) Cummins Engine Control Module (ECM)
document Flash Reprogramming ECUs Using a Portable Laptop PC
document 2008-2010 ND (Dakota) Occupant Restraint Controller (ORC) Flash Process Failed: "Unlock of ECU Failed"
document 2011-2012 WK/WD (Grand Cherokee/Durango) Antilock Brake System (ABS) Electronic Stability Program (ESP) ECU Reprogramming Failure
document 2006 KJ (Liberty) 2.8L Diesel ECM (Engine Control Module) Reprogramming Error: "STAT: 10"
document 2010 JC (Journey) Occupant Restraint Controller (ORC) Flash Process Failed: Negative Response 0x22 – “Conditions Not Correct” Received
document 2011 JC/JF/LD/LX (Journey/Charger/300) Hands-Free Module (HFM) ECU Flash Failure
document 2012 FF (Fiat 500) PCM (Power Train Module) Flash Reprogramming Failure: No Response Received from Write Data By Identifier Request
document 2005/2006 ND (Dakota) Occupant Restraint Controller (ORC) Flash Process Failure: Negative Response 0x11 - 'Service Not Supported' Received from Start Diagnostic Session Extended Request
document 2011 D2/DD/DP/DJ (Ram Trucks) 6.7L Cummins Diesel Wireless Ignition Node (WIN) Flash Process Failed: No Response from Transfer Data Request
document 2011 JK (Wrangler) Cabin Compartment Node (CCN) Flash Process Failed: No Response Received from Transfer Data Request
document 2012 FF (Fiat 500) PCM (Power Train Control Module) Flash Reprogramming Failure: Negative Response "0x22 - 'Conditions Not Correct'" Received from Start Diagnostic Session Programming Request
document International Only 2006-2009 PM (Caliber) MK (Compass/Patriot) Intrusion Theft Module (ITM) Flash Process Failure: Invalid Response Received from ECU - Response Does Not Contain Original PID
document 2011 LD (Charger) JF (Freemont) JC (Journey) RFHub Flash Process Failed: Negative Response 0x22 - 'Conditions Not Correct' Received from Start Diagnostic Session Programming Request
document 2011 D2/DD/DP/DJ/DS/DX (Ram Trucks) LC (Challenger) RT (Caravan/Town & Country) W2 (Grand Cherokee CKD) WD (Durango) WK (Grand Cherokee) Wireless Ignition Node/Wireless/Wireless Control Module (WIN/WCM) Flash Reprogramming
document 2009 HB/HG (Durango/Aspen) HCP (Hybrid Control Processor) Flash Reprogramming Failure: Negative Response 0x22 - "Conditions Not Correct" Received from Start Diagnostic Session Programming Request
document 2011 JK/KA/KK/RT/DS/DJ/WK/WD (Wrangler/Nitro/Liberty/Caravan/Town&Country/Ram Trucks/Grand Cherokee/Durango) TIPM (Totally Integrated Power Module) flash process failed - no response received from Start Diagnostic Session Extended request
document 2011 JC (Journey) JF (Freemont) Cabin Compartment Node (CCN) Flash Reprogramming Process Failed: "Could Not Open Hardware Channel - Error Received Retrieving Channel Parameter - Device Not Responding," OR Device Does Not Respond When Sending Transfer Data Request
document 2012-2014 FF (Fiat 500) PCM (Powertrain Control Module) Negative Response "0x22 - 'Conditions Not Correct'" Received from Start Diagnostic Session Programming Request
document 2012 LD/LX (Charger/300C) PCM (Power Train Control Module) “Flash process failed - Could not open required hardware channel to vehicle"
document 2012 Fiat 500 (FF) Instrument Panel Cluster (IPC) Flash Process Failed: Could Not Open Required Hardware Channel to Vehicle
document Radio Flash Process Failed: "No Response Received from Start Diagnostic Session Programming Request"
document Global Powertrain Engine Controller (GPEC) Powetrain Control Module (PCM) Flash Process Failure: NR 0x22 - 'Conditions Not Correct or Request Sequence Error' received
document 2012-2013 JC/JF (Journey/Freemont) Antilock Brake System/Electronic Stability Program (ABS/ESP) Flash Process Failure
document Next Generation Controller (NGC) Powertrain Control Module (PCM) Flash Process Failure: "Negative Response 0x12, 'Sub Function Not Supported / Invalid Format' Received from Security Request Download Request"
document Global Powertrain Engine Controller (GPEC) Powetrain Control Module (PCM) Flash Process Failure: "Negative Response 0x12 - 'Sub Function Not Supported / Invalid Format' Received from Security Request Download Request"
document 2012 JC/JF (Journey/Freemont) Electronic Pedestrian Protection Module (EPPM) Flash Process Failed: No Response Received from Start Routine By Identifier Request
document 2011 JC/JF (Journey/Freemont) Diesel PCM (Powertrain Control Module) Flash Process Failed: No Response Received from Start Routine By Identifier request.
document Telemetics Gateway (TGW) Radio Flash (Reprogramming) Failure: “Negative Response 0x22 - 'Conditions Not Correct' Received from Start Routine by Identifier Request”
document 2012/2014 WK/WD (Grand Cherokee/Durango) ABS/ESP Flash Process Failed – Erase of Logical Block Failed
document 2012 PF (Dart) Occupant Restraint Controller (ORC) Flash Process Failure: No Response Received from Write Data By Identifier Request
document 2012-2013 PF (Dart) Radio Frequency Hub (RFHub) Abort Recovery Procedure
document 2011–2012 JC/JF/LD/LX (Journey, Freemont, Charger, 300C) Hand Free Module (HFM) Error: "Flash Process Failure - unexpected error occurred - Executable name has embedded quote, split the arguments"
document 2013 DD/DJ/DP/D2 (Ram Truck 2500/3500) Vehicle System Integration Module (VSIM) Flash Reprogramming Fails or Displays as Unresponsive
document 2013-2014 WK/DS (Grand Cherokee and Ram 1500) Air Suspension Module (ASCM) Unresponsive After a Flash Failure

Also listed in
folder ECU Reprogramming (Flash) -> wiTECH, StarMOBILE, StarSCAN

Prev   Next
PCM Has Been Replaced – What To Do Next?     Flash Reprogramming ECUs Using a Portable Laptop PC