Toggle Side Panel

Shopping Cart

No products in the basket.

Shopping Cart

No products in the basket.

Close search
Home / DTC / B1013 — ROM Checksum Error

B1013 — ROM Checksum Error

Detailed page for trouble code B1013.

34,405codes
59brands
11,914generic
22,491specific
All codes P-codes (Powertrain) B-codes (Body) C-codes (Chassis) U-codes (Network/User) Tesla Alerts
Reset
Code

B1013

HUMMER B — Body

ROM Checksum Error

Brand: HUMMER
Type: B — Body
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Corrupted or incomplete module programming/reflash
  • Low or unstable battery/voltage during programming or operation
  • Internal flash/EEPROM failure or memory corruption
  • Water intrusion, corrosion, or physical damage to the module or connectors
  • Broken solder joints or PCB/component failure inside the module
  • Interruption of communications during a software write (tool disconnect, bus fault)

Symptoms

  • Related body/control module functions inoperative or intermittent (locks, lights, windows, instrument cluster, etc.)
  • Permanent or recurring B1013 stored in the module
  • Possible loss of CAN communication to the affected module
  • Symptoms may appear after a software update, battery replacement, or water intrusion
  • Warnings or malfunction indicators for affected systems may be present

What to check

  • Record full DTC list and freeze frame with a capable scan tool
  • Verify vehicle battery state-of-charge and system voltage (battery >12.4 V; during programming >12.6–13.0 V recommended)
  • Inspect module connectors and harness for corrosion, bent pins, water ingress, heat damage, or loose terminals
  • Check vehicle service history for recent module programming, battery replacement, jump-starts, or water damage
  • Confirm CAN/bus communication to the module (module appears/responds on scan tool)
  • Check for related codes in other modules (communication or power supply faults)

Signal parameters

  • Battery voltage (key on, engine off and during operation)
  • Module supply voltage and ground integrity readings
  • Module firmware/calibration part number and software version
  • Module reported checksum/CRC or ROM integrity status (if available from scan tool)
  • Security/immobilizer status and VIN/part number match
  • CAN bus traffic to/from the module (messages per second)

Diagnostic algorithm

  1. Connect a professional scan tool; read and record all DTCs and module data (firmware version, part number, checksum if available).
  2. Verify battery voltage and charging system; charge battery to recommended level and maintain stable voltage during testing/programming.
  3. Visually inspect the module, mounting area and connectors for water, corrosion, damaged pins, or evidence of thermal damage; repair harness or connectors as necessary.
  4. Check grounds and power feeds to the module for voltage drop and continuity; clean and secure ground connections.
  5. Attempt to communicate with the module using OEM scan tool. If module does not respond or shows corrupted data, note behavior.
  6. If communication is present and OEM guidance allows, attempt a reprogram/reflash using the correct, latest OEM calibration and follow manufacturer reprogramming procedure (ensure stable battery/charger and proper tool connection).
  7. If reflash succeeds, clear codes, perform relearns/reset procedures as required, then verify normal operation and re-scan for codes.
  8. If reflash fails or module will not accept correct software, inspect for internal module faults (consult OEM for repair/rework options). Replace the module only with correct part and perform required programming and security pairing procedures.
  9. After repair or reprogramming, verify all related systems, clear codes, and perform road/functional tests to confirm issue resolved. If faults recur, escalate to module replacement or factory service as directed by OEM.
  10. Document findings, performed procedures, and any software versions applied.

Likely causes

  • Previous failed or interrupted reflash/software update
  • Weak battery or poor charging system while module was programmed
  • Internal module hardware fault (flash memory failure)
  • Corroded/loose connector or damaged wiring to module causing corrupted data transfers

Fault status

⚠️ Status
ROM checksum error: module firmware or stored calibration failed internal integrity check; requires inspection of programming, power, connectors, and possible reflash or module replacement.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-3.0 hours

Similar codes

B1010 B1011 B1014 B1000 U0100 U0121
Repair manuals

Manual library for HUMMER

138

Browse 138 HUMMER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

HUMMER

Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email
Code

B1013

MITSUBISHI B — Body

Outside temperature sensor open

Brand: MITSUBISHI
Type: B — Body
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Corrupted or incomplete module programming/reflash
  • Low or unstable battery/voltage during programming or operation
  • Internal flash/EEPROM failure or memory corruption
  • Water intrusion, corrosion, or physical damage to the module or connectors
  • Broken solder joints or PCB/component failure inside the module
  • Interruption of communications during a software write (tool disconnect, bus fault)

Symptoms

  • Related body/control module functions inoperative or intermittent (locks, lights, windows, instrument cluster, etc.)
  • Permanent or recurring B1013 stored in the module
  • Possible loss of CAN communication to the affected module
  • Symptoms may appear after a software update, battery replacement, or water intrusion
  • Warnings or malfunction indicators for affected systems may be present

What to check

  • Record full DTC list and freeze frame with a capable scan tool
  • Verify vehicle battery state-of-charge and system voltage (battery >12.4 V; during programming >12.6–13.0 V recommended)
  • Inspect module connectors and harness for corrosion, bent pins, water ingress, heat damage, or loose terminals
  • Check vehicle service history for recent module programming, battery replacement, jump-starts, or water damage
  • Confirm CAN/bus communication to the module (module appears/responds on scan tool)
  • Check for related codes in other modules (communication or power supply faults)

Signal parameters

  • Battery voltage (key on, engine off and during operation)
  • Module supply voltage and ground integrity readings
  • Module firmware/calibration part number and software version
  • Module reported checksum/CRC or ROM integrity status (if available from scan tool)
  • Security/immobilizer status and VIN/part number match
  • CAN bus traffic to/from the module (messages per second)

Diagnostic algorithm

  1. Connect a professional scan tool; read and record all DTCs and module data (firmware version, part number, checksum if available).
  2. Verify battery voltage and charging system; charge battery to recommended level and maintain stable voltage during testing/programming.
  3. Visually inspect the module, mounting area and connectors for water, corrosion, damaged pins, or evidence of thermal damage; repair harness or connectors as necessary.
  4. Check grounds and power feeds to the module for voltage drop and continuity; clean and secure ground connections.
  5. Attempt to communicate with the module using OEM scan tool. If module does not respond or shows corrupted data, note behavior.
  6. If communication is present and OEM guidance allows, attempt a reprogram/reflash using the correct, latest OEM calibration and follow manufacturer reprogramming procedure (ensure stable battery/charger and proper tool connection).
  7. If reflash succeeds, clear codes, perform relearns/reset procedures as required, then verify normal operation and re-scan for codes.
  8. If reflash fails or module will not accept correct software, inspect for internal module faults (consult OEM for repair/rework options). Replace the module only with correct part and perform required programming and security pairing procedures.
  9. After repair or reprogramming, verify all related systems, clear codes, and perform road/functional tests to confirm issue resolved. If faults recur, escalate to module replacement or factory service as directed by OEM.
  10. Document findings, performed procedures, and any software versions applied.

Likely causes

  • Previous failed or interrupted reflash/software update
  • Weak battery or poor charging system while module was programmed
  • Internal module hardware fault (flash memory failure)
  • Corroded/loose connector or damaged wiring to module causing corrupted data transfers

Fault status

⚠️ Status
ROM checksum error: module firmware or stored calibration failed internal integrity check; requires inspection of programming, power, connectors, and possible reflash or module replacement.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-3.0 hours

Similar codes

B1010 B1011 B1014 B1000 U0100 U0121
406

Browse 406 MITSUBISHI manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

MITSUBISHI

Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .