OBD/Enhance Trouble Codes Pro v1.3

APK · 12.9 MB · version code 3 · Android 4.0.3+ · uploaded Sep 10, 2016

MD5 4b2b8e6ae98a7aef23e410def24b5390 UNKNOWN

Quick check before downloading

Answer this to unlock the download. It keeps automated downloaders away.

File information

Version
v1.3 (3)
Uploaded
Sep 10, 2016
Size
12.9 MB
Requires
Android 4.0.3+ (API 15)
CPU support
x86 32-bit, ARM (legacy), ARM 32-bit
Screen
Small screens and larger
MD5
4b2b8e6ae98a7aef23e410def24b5390
Signing certificate (SHA-1)
94:CE:DC:BC:DE:5C:C0:28:A2:F1:65:66:F2:8A:35:D3:6F:54:21:91
Signed by
CN=Hieu Van Diep, O=OBD High Tech, C=84
File name
obd2-enhancecode-diagnosticscode-possiblecause-giudecode-codes-dtc-troublecode-oht-obd2codesfixpro-3-23591874-4b2b8e6ae98a7aef23e410def24b5390.apk
Package
obd2.enhancecode.diagnosticscode.possiblecause.giudecode.codes.dtc.troublecode.oht.obd2codesfixpro
Downloads (all versions)
398
Age rating
PEGI 3 · Everyone

What's new in v1.3

1.3 - Update Audi/Volkswagen (100 DTCs and Possible Cause) - Add Renault (5500 OBD2/OEM DTCs) - Add SsangYong (5000 OBD2 DTCs) - Add Peugeot (5000 OBD2 DTCs) - Fix Nissan/Infinity can't get OEM DTCs. 1.2 - Updated Hyundai (1000 DTCs) - Updated Kia (1200 DTCs) - Fix User Interface Tablet 7" and Tablet 10"

Security & authenticity

Security rating: Unknown

Signing certificate

  • Certificate issued to “OBD High Tech” The developer's name — though anyone can put any name in a certificate.

Store checks

  • Developer signature not checked yet Sep 10, 2016
  • Antivirus scan passed May 28, 2020
  • Uploaded by “7777777” 317 followers · uploading since 2012

Scans come from the source store; the certificate comparisons are AAPKs's own, made from the files' published signatures. AAPKs doesn't scan files itself.

How to install OBD/Enhance Trouble Codes Pro on Android 4.0.3+

You'll need about 25.8 MB of free space.

  1. Download the APK — tap Download APK above (12.9 MB). Chrome shows “File might be harmful” for every APK file; choose Download anyway only if you trust this file.
  2. Open the file — tap the download notification, or open Files › Downloads and tap obd2-enhancecode-diagnosticscode-possiblecause-giudecode-codes-dtc-troublecode-oht-obd2codesfixpro-3-23591874-4b2b8e6ae98a7aef23e410def24b5390.apk.
  3. Allow the install (first time only) — Android 8 and later asks for permission the first time an app opens an APK: tap Settings in the prompt, turn on Allow from this source, then go back. Manual path: Settings › Apps › Special app access › Install unknown apps (on Samsung: Settings › Apps › ⋮ › Special access). On Android 7 and older: Settings › Security › Unknown sources.
  4. Check the file (optional) — the MD5 of the downloaded file should be 4b2b8e6ae98a7aef23e410def24b5390. If it differs, the file is damaged or was changed: delete it and download again.
  5. Tap Install — Android asks “Do you want to install this app?”. This file has no malware rating from the source store. If Play Protect warns about it, tap Cancel. If an earlier version is installed, this one only installs as an update when it is signed with the same certificate (SHA-1 shown above).
  6. Open OBD/Enhance Trouble Codes Pro — tap Open on the install screen, or find it in your app drawer.
Common install problems
  • “App not installed” — a version signed with a different certificate, or a newer version, is already installed (Android doesn't allow downgrades). Uninstall it first; back up your data, because uninstalling deletes it.
  • “There was a problem parsing the package” — the file is incomplete, or your Android is too old (this version needs Android 4.0.3+). Download it again, or pick an older version.
  • “App not compatible with your device” — this build contains native code for x86 32-bit, ARM (legacy), ARM 32-bit only. Devices with other processors can't install it.
  • Blocked by Play Protect — Play Protect checks apps from outside the Play Store. Only continue if you trust the source.

Other versions (1)

Back to all versions