X-431 Thinkdiag 2 and EdiagPlus testing 1.1.3

srinivas said:

dpu link manager services andriod 14 realme pad 2 not installing problem

Click to expand...

Your issue looks separate from the language/patch problem javicho999 hit — everything else installs for you, so the shell and the download side are fine. A downloaded APK that refuses to install manually on Android 14 usually comes down to one of these:

• targetSdk too low — Android 14 flatly refuses to install any APK targeting below API 23. If DPULink Manager is an old build, no permission toggle will fix it. Error text is usually "App not installed as package appears to be invalid".
• Restricted setting / unknown sources — on ColorOS you need Settings > Apps > Special app access > Install unknown apps, and grant it to the exact app doing the install (your file manager, not just the browser). Android 13+ also silently blocks some sideloads until you clear the "Restricted setting" prompt.
• Signature conflict — if an original Launch/DPULink service app is already on the tablet, the new one won't overwrite it. Uninstall the old package first, including for other users/work profile.
• Truncated download — re-download and compare size, a partial APK gives a parse error.

Start with the second and third points since they cost nothing to check. If it still fails with a parse/invalid package error, it's almost certainly the targetSdk limit and you'd need either a rebuilt APK or a device on Android 12 or older to run that service.

To narrow it down, post a preview screenshot of the exact error dialog, the APK filename and version you're installing, and whether any Launch/DPULink app is already installed on the tablet.

srinivas said:

@Gemini DPU Link Manager services installation issue on Android 14 Realme Pad 2

Click to expand...

Dpulink was not necessary in tests with td2. I haven't tested it online; offline it is not necessary. From what I read, it is for the original Launch tablet.

Gemini said:

Your issue appears to be unrelated to the idioma/parche issue that javicho999 had; everything else installs correctly, so the interface and download are working properly. A downloaded APK file that refuses to install manually on Android 14 is usually caused by one of the following:

• targetSdk too low: Android 14 outright refuses to install any APK targeting an API level below 23. If DPULink Manager is an old version, changing permissions will not fix it. The error message is usually "The app wasn't installed because the package appears to be invalid."
• Restricted settings / Unknown sources: in ColorOS, you need to go to Settings > Apps > Special app access > Install unknown apps and grant permission to the app performing the installation (your file manager, not just the browser). Android 13 and later also silently block some sideloaded installations until you disable the "Restricted settings" option.
• Signature conflict: if an original Launch/DPULink service app is already installed on the tablet, the new one will not overwrite it. Uninstall the previous package first, including for other users or work profiles.
• Truncated download: download it again and compare the file size; a partial APK causes a parsing error.

Start with the second and third points, since they can be checked at no cost. If it still fails with a parsing/invalid package error, it is almost certainly due to the targetSdk limit, and you would need a recompiled APK or a device running Android 12 or earlier to run that service.

To narrow down the issue, post a screenshot of the exact error window, the name and version of the APK file you are installing, and indicate whether any Launch/DPULink app is already installed on the tablet.

Click to expand...

It may have issues on Android 14. Apparently, when I installed it, I got a message saying that the app was created for an earlier version of Android. I installed it on Android 13 and everything worked fine without any message. It also works on Android 14, but the message was the only difference. I tested it on two A72 Android phones (13–14), same phone model but different operating systems.

javicho999 said:

Puede ser que tenga problemas en android14, al parecer cuando instale me salio que la app fue creada...

Click to expand...

Your data point actually helps split the two failures apart. What you saw on Android 14 is the benign "built for an older version of Android" notice — that appears when targetSdk is below the current platform but still at or above the minimum, so the install goes through and the app runs, exactly as you describe. The dialog srinivas posted is different: "App not installed as app isn't compatible with your phone" is a hard rejection by the package installer, not a warning, so it never gets to the point of running.

That points away from targetSdk in his case. The usual causes for that specific wording are:

• ABI mismatch — the APK only ships native libs for an ABI his device doesn't have.
• A <uses-feature android:required="true"> the device lacks. Worth noting he's on a Realme Pad 2, a tablet, while you tested two A72 phones. If the manifest requires telephony or a phone-class feature, a Wi-Fi-only tablet gets rejected while your phones install fine.
• minSdk/maxSdk or screen-size declarations excluding the device.

So the same APK being fine on your A72 under both 13 and 14 is consistent with this being device-class, not Android-version, related.

On your other point — that DPULink isn't needed for offline TD2 work and is aimed at the original Launch tablet — that matches what you observed in testing; I haven't verified what the service is used for on the online side, so I'd leave that open until someone tests an online session without it.

If you still have both A72 units handy, the one useful check would be the APK filename and version you installed successfully, so it can be compared against the V1.00.030 build in his screenshot.

Gemini said:

Your data point actually helps split the two failures apart. What you saw on Android 14 is the benign "built for an older version of Android" notice — that appears when targetSdk is below the current platform but still at or above the minimum, so the install goes through and the app runs, exactly as you describe. The dialog srinivas posted is different: "App not installed as app isn't compatible with your phone" is a hard rejection by the package installer, not a warning, so it never gets to the point of running.

That points away from targetSdk in his case. The usual causes for that specific wording are:

• ABI mismatch — the APK only ships native libs for an ABI his device doesn't have.
• A <uses-feature android:required="true"> the device lacks. Worth noting he's on a Realme Pad 2, a tablet, while you tested two A72 phones. If the manifest requires telephony or a phone-class feature, a Wi-Fi-only tablet gets rejected while your phones install fine.
• minSdk/maxSdk or screen-size declarations excluding the device.

So the same APK being fine on your A72 under both 13 and 14 is consistent with this being device-class, not Android-version, related.

On your other point — that DPULink isn't needed for offline TD2 work and is aimed at the original Launch tablet — that matches what you observed in testing; I haven't verified what the service is used for on the online side, so I'd leave that open until someone tests an online session without it.

If you still have both A72 units handy, the one useful check would be the APK filename and version you installed successfully, so it can be compared against the V1.00.030 build in his screenshot.

Click to expand...

Thanku sir

srinivas said:

Thanku sir

Click to expand...

You're welcome. If you decide to test that ABI theory or need help checking the manifest, feel free to post back.

Gemini said:

You're welcome. If you decide to test that ABI theory or need help reviewing the manifest, feel free to write again.

Click to expand...

X431-8.00.048-apbnu.apk, I haven't tested the older versions.

javicho999 said:

X431-8.00.048-apbnu.apk , las versiones antiguas no las probé ,

Click to expand...

Good to know — so version 8.00.048 works on A72 phones under both Android versions, which confirms the APK itself isn't fundamentally broken on Android 14. That makes the tablet-specific rejection on srinivas's Realme Pad 2 even more likely to be an ABI or device-feature issue rather than a platform version problem.

Gemini said:

Good to know: version 8.00.048 works on A72 phones with both Android versions, confirming that the APK has no fundamental issues on Android 14. This makes it even more likely that the tablet-specific rejection on srinivas's Realme Pad 2 is due to an ABI or device feature issue rather than a platform version issue.

Click to expand...

After installing everything, I tested it with a new, sealed td2 on my own 2009 Ford, and it worked without any problems on Android 14. The only issue is that it occasionally displays a server connection error message, but it works very well offline. I tried it on a 2008 Corsa, and it worked. After that, I performed the language tests to make it complete. The remaining question is whether it will work on a tablet with Android hyperOS or on more generic phones.

javicho999 said:

Al instalar todo hize la prueba con un td2 nuevo sellado en un ford 2009 mio y trabajo sin problemas...

Click to expand...

That's solid real-world confirmation that the app and offline diagnostics work on Android 14 when the device is compatible — Ford and Corsa coverage with actual TD2 hardware is more useful than theory. The server connection errors you saw are almost certainly unrelated to the Android 14 / language fixes; that's typically network or backend availability, not client-side.

On your HyperOS / generic phone question: HyperOS (Xiaomi's Android fork) shouldn't be fundamentally different from what you tested on Samsung's One UI, as long as the device meets the ABI and feature requirements. The Realme Pad 2 rejection we saw with srinivas is more likely tablet-specific (missing phone features in the manifest, or an ABI the pad lacks) than OS-flavor-specific. If you can test on a Xiaomi or Redmi phone running HyperOS, that would answer it directly.

For generic/budget phones, the main risks are older ARM chips with only 32-bit support (armeabi-v7a) if the APK ships arm64-v8a only, or MediaTek SoCs with unusual ABI combinations. If you have a candidate device, check its ABI with CPU-Z or similar before installing — if it lists arm64-v8a, it should behave like your A72.

srinivas said:

@Gemini Installation issue with DPU Link Manager services on Android 14 Realme Pad 2

Click to expand...

Apparently, the problem may lie with the processor. The most practical way to check is to try a 32-bit app and see if it runs. That's the downside of Chinese processors: to cut costs, they reduce essential features.

srinivas said:

DPU link manager download completed, but there is a manual installation problem.

Click to expand...

I happened to encounter the same problem on a Xiaomi Pad tablet that I was thinking of buying for automotive programs.
AI DATA.
The problem: The Helio G100 DOES NOT support 32-bit applications. Although the Helio G100 is a modern processor manufactured in 2024, MediaTek (following ARM's guidelines) completely removed hardware support for 32-bit instructions from its high-performance rendimiento.El Helio G100 hardware is 100% pure 64-bit.bits.Si The modified X431 APK you are trying to use contains old diagnostic libraries, dependencies, or modules that are still compiled in 32-bit (armeabi-v7a), so the phone's processor simply will not know how to read that code, and the application will fail (it will give an installation error, close by itself when opened, or fail to recognize the Bluetooth connector). How can this limitation be fixed or bypassed? VPhoneGaga, VMOS Pro, or F1 VM. These applications create a virtual Android operating system inside your phone that emulates 32-bit support through software. Install the cloning app, and within that virtual environment, install and open the modified APK from X431.Buscar an updated 64-bit modified version: Many developers of automotive patches (such as the Diagzone, XDiag, or ProDiag communities) have been forced to update their base APKs to 64-bit (arm64-v8a) precisely because new phones no longer run the old versions. Try to obtain a more recent revision of your software.modificado.Instala a code "Translator" (Requires Root): If your phone has Root access, there are Magisk modules such as Tango or A64B that force the operating system to translate 32-bit instructions into 64-bit instructions in real time, allowing old applications to run on new processors.

Thanks to the creator of this software, I tested fiat and iveco truck. So far, everything is great, I haven't seen any problems. One note about iveco trucks, the latest software for iveco is v22.22 not v22.27. it was a test version only. My question is how to pay a one year subscription outside of Russia?

Has anyone updated the firmware on the thinkdiag2 for key programming? Does it work?

Really nice work anyway! Got it on my tablet with android 15 and almost everything works

@kaptensea
The firmware version, or more precisely the V0 value in this screenshot, has nothing to do with the VCI, meaning TD2!

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

miouser said:

@kaptensea
the firmware version, or rather the V0 value in this screenshot, has nothing to do with the VCI, that is, TD2!

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

Click to expand...

It can be used, but it is more expensive due to a lack of inventory. A cheaper option is the Xhorse Key Tool Lite for Android from its official website, XT27 chips, and remotes.

Thanks for answering, I should’ve known But isn’t that just for cloning? Not programming/adding new key?

Next problem, I can’t install this in the picture.
The first three is because my android is v15 and to new. But the other ones downloads to 100% but gets stuck there, never installs

Any solution?

kaptensea said:

Thanks for replying; I should have known that. But isn't that only for cloning? Not for programming/adding a new key?

The next problem is that I can't install this in the image.
The first three are because my Android is version 15 and is too new. But the others download to 100% and then get stuck there and never install.

Any solution?View attachment 7786

Click to expand...

It was a bug that has already been fixed. You need to set the device to English so that the app installs everything in English, and that's it. You can use a screen translator to translate the options into your language.

kaptensea said:

Thanks for replying; I should have known. But isn't that only for cloning? Not for programming/adding a new key?

The next problem is that I can't install the items shown in the image.
The first three fail because my Android version is 15 and is too new. But the others download to 100%, then get stuck there and never install.

Any solution?View attachment 7786

Click to expand...

The app includes immo by brand for programming and deleting keys, Key Tool for cloning, and Immo Prog for xprog3. It's complete, so we should help the creator by testing it to improve the app and also be able to purchase the 1-year license. The project is excellent.

Motorcycles all mt models downloaded
But not showing in local diagnostic menu inside please add thanks