Guide to Bypass DexProtector Apps

Thanks to Govind Sharma for being willing to share the error code.
Also thanks to everyone who develop modules to hide everything

This will guide you on bypassing apps that use protectors such as DexProtector. To avoid misinformation inside this guide, contact me at Telegram: t.me/NVG064.

Table of Content

• List Apps That Use DexProtector
• Check Apps That Use DexProtector
• Read Error Code
• Error Code Reference and How to Fix
• Additional Tools
• DexProtector's Demo App
• The End

List Apps That Use DexProtector

Feel free to contact me at Telegram: t.me/NVG064 so I can keep it updated

• Livin' Merchant by Mandiri
• Indomaret Poinku
• Bank Saqu
• Tata Neu
• Revolut

Check Apps That Use DexProtector

You can recognize this by the UI: a QR Code

Let's take an example below. The figures I attached, are from Tata Neu.

Read Error Code

Let's take an example: Bank Saqu

Try to open it. If you can't pass, you'll get a QR Code like this:

There are two methods to get an error code:

• Manually read the QR Code using the QR Code Scanner

• Use AppErrorsTracking Xposed module

After you get the error code, take note of the number: 775

How to resolve this? Ahead to the next section :)

Error Code Reference and How to Fix

Thanks to Govind Sharma for being willing to share the error code

Thanks to llcheff (Telegram @llcheff) for getting more codes

789 -> Found Injection with Xposed

Fix: do not inject into any Xposed modules

Alternative Fix: use Xposed with a fully disabled log

781 -> dev minor diff in mount (inconsistent mount)

Fix: no clue. I'll update later :)

779 -> ro.boot.xxx prop

Fix: use TrickyStore module by 5ec1cff, then put it on /data/adb/tricky_store/target.txt. Last, force stop the app

Alternative Fix: use VBMeta Fixer module by Reveny

Others: no clue. I'll update later :)

778 -> KernelSU

Fix: update your KernelSU manager

Alternative Fix: uninstall KernelSU manager

Others: no clue. I'll update later :)

777 -> LineageOS

Fix: use SusFS4KSU by simon punk (if you don't know how to do it, use alternative fix)

Alternative Fix: change custom ROM which have less string containing "lineage" (try getprop | grep lineage) or try Native Detector by Reveny to check string containing "lineage"

Alternative Fix: use Stock ROM

Others: no clue. I'll update later :)

775 -> Magisk's DenyList

Fix: put the app to Magisk's DenyList

Others: no clue. I'll update later :)

773 -> Installed outside Play Store

Fix: install the app from Play Store

772 -> Magisk svc calls

Fix: enable App Data Isolation (use Hide My Applist by Dr-TSNG)

Others: no clue. I'll update later :)

770 -> Magisk prop

Fix: use Shamiko by LSPosed team

Others: no clue. I'll update later :)

769 -> Magisk's .so file

Fix: use Shamiko by LSPosed team

Others: no clue. I'll update later :)

768 -> Zygisk

Fix: use ZygiskNext by 5ec1cff (use version 1.2.5 at least)

Alternative Fix: do not use Zygisk :(

Others: no clue. I'll update later :)

767 -> Riru

Fix: migrate to use Zygisk

Alternative Fix: do not use Riru

Others: no clue. I'll update later :)

764 -> Root packages

Fix: use Hide My Applist by Dr-TSNG, try Whitelist + Exclude System App. If failed, use Blacklist + xx apps hidden (xx refers to non-negative real numbers greater than zer0, like 1, 2, 3, etc.)

Alternative Fix: uninstall suspicious apps (such as MT Manager, root manager, Lucky Patcher, Game Guardian, apps from magisk modules, apps from xposed modules, and others)

Others: no clue. I'll update later :)

759 -> Xposed

Fix: change to other LSPosed version, like LSPosed Fork by npm (make sure to untick "Enable Watchdog logs" in settings), LSPosed Fork by Irena, and LSPosed Internal Test

Alternative Fix: remove props if you use setprop to disable LSPosed logs. Check this link to do

Alternative Fix: update your LSPosed version

Others: no clue. I'll update later :)

758, 719 -> Custom ROM

Fix: Use SusFS4KSU by simon punk (if you don't know how to do it, use alternative fix)

Alternative Fix: remove or rename /system/addon.d folder and install-recovery.sh if exist

Alternative Fix: use stock ROM

Others: no clue. I'll update later :)

Additional Tools

In this section, I'll discuss the Native Detector by Reveny. This root detector helps you recognize root detections with an explanation.

The figure above is an example of detection. Native Detector says that it found injections, which means the main cause of the failure to bypass DexProtector.

What do we do? Because this is found injection, you need to:

• Check Magisk/KernelSU/APatch modules which require Zygisk to work properly
• Check Xposed modules which inject into the right way

DexProtector's Demo App

Yes, the demo app exists on Play Store: https://play.google.com/store/apps/details?id=com.dexprotector.detector.envchecks

You can experiment with it to get other error codes which didn't mention in this guide :)

The End

I know my grammar sucks. But, I hope this guide helps you to pass DexProtector :)