Last Updated on November 12, 2026
If you’ve just pressed Erase on an OBD2 scanner and realized you needed the code, start by checking where it might still be recorded. A previous scan report can contain the original code and freeze frame. The vehicle may also still have a permanent DTC or a fault stored in a different module. Knowing where to look can save you from waiting for the symptom to return.
Most U.S. passenger cars and light trucks use the standardized emissions diagnostic system known as OBD2 from model year 1996 onward. When a monitor detects a fault, the computer can record a diagnostic trouble code, or DTC. If you are trying to recover erased OBD2 codes, find out whether a copy was saved and which module and code category the erase command affected.
What is an OBD2 Scanner?
An OBD2 scanner connects to the car’s diagnostic connector and requests data from the vehicle. A basic reader can display generic emissions-related codes, depending on the tool and vehicle. More capable tools may also support manufacturer data from systems such as the transmission or ABS. The app or tool might keep a report if you saved or exported it during the original scan.
If you’re choosing an OBD2 scanner for a diagnostic job, check that it shows the code categories you need and lets you save a report. If you already have a tool, see our detailed guide on how to use an OBD2 scanner for connecting it and recording the results.
Can You Recover Erased OBD2 Codes?
A standard OBD2 erase command has no undo function. If it removed a code and its associated freeze frame from the module, a later generic scan cannot bring that record back. You may still be able to find a copy that was saved elsewhere, read a code that wasn’t erased, or record a new code if the vehicle detects the fault again. Each record tells you something different about the fault.
- Original record: Look for a screenshot, PDF, printout or scan-tool history from before you cleared the code. This is the best place to recover the exact code status, mileage or operating conditions from that scan.
- Record that remains in the car: Check permanent emissions DTCs where supported and any relevant modules outside the scope of the erase command. A manufacturer-specific event or code in another module can give useful clues.
- New record: If the monitor detects the fault again, save the new code and snapshot. Note the date and mileage so you can tell it apart from the original scan.
Possible Solutions to Recover or Re-Diagnose Erased Trouble Codes
If you need to recover erased OBD2 codes, start with places that might have a copy. Then check what the vehicle still reports and investigate the symptom under the conditions that originally brought it on.
1. Check the Freeze Frame Data
Freeze frame is a snapshot of operating conditions attached to a fault. The erase command commonly removes the affected generic frame along with resettable emissions codes. A screenshot or saved report from before the clear can still contain the snapshot. Look for the code associated with the frame, along with coolant temperature, RPM, speed and load. If a remaining frame belongs to a different code, use it as evidence for that fault.

2. Drive the Vehicle to Recreate the Issue
If the vehicle is safe to drive, see whether the symptom returns under the conditions you remember. For example, a fault that appeared on a cold start may need the engine to cool again before the relevant monitor can run. A normal warm idle in the driveway gives limited evidence about a cold-start problem.
Note the temperature, speed and load if the fault returns. Start a data log before moving or have a passenger handle the tool. If the car is running roughly or the check engine light is flashing, follow the warning instructions in the owner’s manual before attempting a road test.
3. Use an Advanced Diagnostic Scanner
A tool with coverage for the relevant modules can check fault records that a generic reader doesn’t display. For example, the Autel MK808s has a vehicle history feature and the XTOOL D7 has a reports function. Look there if the tool was used for the earlier scan. Those features can display previously saved information. The current scan only sees records the vehicle still reports.
If the warning was for a specific system, confirm the tool supports that system on your exact vehicle. A generic engine scan after clearing cannot tell you what the ABS or airbag module may still have recorded.
4. Refer to the Repair Manual
Use the service information for your year, make, engine and system. A manufacturer’s diagnostic chart can tell you which conditions run the monitor and which tests are useful before replacing anything. If you remember only the symptom, write down when it occurred and which light came on so you can choose the right starting point.
5. Look into Scanner Software Logs (if applicable)
Open the history or reports section of the app or scan tool you used. Check downloaded reports, saved screenshots, emails and printed work orders. Match the record to the vehicle, date and mileage. An app can retain a prior scan even after the vehicle has cleared the corresponding records. If a shop scanned the vehicle earlier, ask whether it still has the report.
Where Are Trouble Codes Stored in a Vehicle?
The engine or powertrain module commonly reports generic emissions-related codes. Other modules may store their own faults and event records. An automatic transmission module, ABS controller and body module can each have different data even when you reach them through the same connector.
A pending entry may appear when a monitor first detects a possible fault. A confirmed entry means that the fault met the criteria for storing that code as confirmed. Some entries can age out after the vehicle sees a series of successful tests. Where supported, a permanent emissions DTC stays after a routine erase and clears when the vehicle’s monitor verifies that the problem is gone.
How to Retrieve Stored Trouble Codes
When you are trying to recover erased OBD2 codes, start with a read-only scan. Write down what still appears before making another change.
- Connect your scanner to the DLC, usually near the driver’s side of the dashboard. Follow the tool’s ignition instructions. Many code reads can be done with the ignition on and the engine off.
- Select the correct vehicle and module. Check generic OBD2 and any other system relevant to the warning you saw.
- Check the pending, confirmed and permanent menus where supported. Note any history codes and which module reported them.
- Save a new report with the date and mileage. Keep it separate from any report that was made before the erase.
Understanding and Decoding Trouble Codes
A DTC usually has five characters, such as P0019 or U0100. Copy the complete identifier, including any letters in the later positions. Look it up with the system and vehicle that reported it.
1. The First Character – Letter
- P: Powertrain.
- B: Body.
- C: Chassis.
- U: Network communication.
2. The Second Character and Code Range
The code range helps identify whether it is standardized or assigned by the manufacturer. For example, P0 codes are standardized and P1 codes are manufacturer controlled. Use the full code and vehicle information because other ranges have different assignments.
3. The Third Character – System Identifier
In many generic powertrain codes, this position groups related faults such as fuel metering, ignition and misfire, emissions, idle control or transmission. Read the full code before deciding which system to test.
4. The Last Two Characters Complete the Identifier
The full description gives you the condition the module detected. A correlation code, for example, can lead to checks of sensor signals, timing and wiring. Use the test steps for your specific engine to verify the cause.
Where to Look Up Diagnostic Trouble Codes
Whether you used a code reader or OBD2 scanner, check the meaning against information for the vehicle and module that reported it.
1. Car Repair Manual
Manufacturer service information is the first place to check for the code description, conditions required to set it, and diagnostic steps. The owner’s manual can also explain which dashboard warning needs immediate attention.
2. Scan Tool Manual
Use the tool manual to find code status, freeze frame, vehicle history and any report functions. Check the exact model. Some menus depend on the vehicle, software version or scan type.
3. Online Car Repair Forums
Owner discussions can suggest conditions to reproduce or checks to make. Compare the year, engine and symptoms with your own car, then verify the proposed checks against service information.
4. Automotive Websites
Search for the full code with the year, make, model, engine and module. A description for a different engine or an enhanced code from another manufacturer may point you to the wrong test.
How to Recover Erased OBD2 Codes From a Saved Report
If you want to recover erased OBD2 codes exactly as they were, a pre-clear copy is the most useful evidence. The image below shows a BMW key-learning and module-coding screen. Restore Coding is part of that coding menu. To find an earlier diagnostic scan, open the scan tool’s Vehicle History, Diagnosis Report or saved report files.

Steps to Check What Is Still Available
- Open the app or scanner history first. Export or photograph any older record before you start a new diagnostic session.
- Ask any shop that scanned the vehicle before the clear for the report, including the module, code status and snapshot where available.
- Scan the vehicle again. Keep the remaining permanent or module-specific entries separate from a newly detected code. If you’re unsure which data was cleared, see what the scan tool clears when you erase OBD2 codes.
- If no useful record remains, write down the original symptom and work through the vehicle’s diagnostic procedure. Save the next code and frame before using Erase again.
How Long Before Trouble Codes Reappear?
There is no fixed mileage. Some faults can be detected again quickly. Others require a particular cold start, temperature, load or speed before the monitor runs. For example, the engine may need to warm up before a catalyst monitor can check its result. Look at readiness and the code category before deciding whether you have seen enough to verify the repair.
If a newly detected code matches the old number, compare the conditions in the new snapshot with what you remember. The same code can be triggered on a different trip. Keeping both sets of information helps you avoid assuming every occurrence had the same cause.
Final Thoughts
If you accidentally cleared the codes, check for the old scan report before trying to recreate the symptom. Then read what the vehicle still reports and save the next scan before erasing anything. Bring the report and a description of the symptoms if a technician will be checking the car.
❓FAQs: Recovering Erased OBD2 Codes
1. Can I read deleted OBD2 codes after clearing them?
You can read any record that remains and check for a copy saved before the clear. A normal scan has no undo function for data the erase command deleted.
2. What happens when you delete a trouble code without fixing the issue?
The fault may be detected again when its monitor runs. Clearing can also erase its freeze frame and reset emissions readiness.
3. Will a cleared code come back?
It can return if the vehicle detects the same fault again. Save the new code and conditions, then test the system.
4. Where are OBD2 codes stored in the car?
Generic emissions-related records usually come from the powertrain controller. Other control modules can have their own fault records.
5. Can I recover erased OBD2 codes without a scanner?
Look for a saved report, screenshot, email or printout. You’ll need a compatible tool to check what the vehicle currently reports.
6. How can I prevent accidental code deletion?
Save a report before choosing Erase and confirm the module you are working on. If a tool can’t export the scan, photograph the code, status and snapshot screens.
7. Do permanent codes stay even after clearing the OBD2 memory?
Where supported, permanent emissions codes can remain after a standard erase. The vehicle clears them after verifying the fault is gone under its monitor rules.
8. How long does it take for OBD2 readiness monitors to reset after clearing codes?
A clear can mark supported monitors incomplete. They become ready after their required tests run, which depends on the vehicle and operating conditions.
9. Can I retrieve old codes from a repair shop’s scanner history?
Ask for a pre-clear report from the original visit. Check the date and vehicle details so you know which scan it came from.