Common issues for MBCPApp

• Quickly find your common issues by clicking [Table of Content] above :)

App detecting root

Important

MB Bank does have 2 root detection layer (VTAP & Zimperium)

Each root detection layers has it's specific method to bypass !

In the past (before v6.4.67 and GW934 messure) MBCP app is actually the app that is not detecting root for both root detection layers as it's already bypassed at the app level, but MB fixed that by pushing GW934 to us since v6.4.64+ (2025/09/09)

• All of above root detection layer can be easily bypassed with MBCP app without advanced root hiding.

First root detection layer (VTAP) with new detection screen present since v6.4.53+ (v6.4.52 or older will be different)

-> If you are using Magisk (both normal & randomized) without basic root hiding or KernelSU (with original me.weishu.kernelsu packageName), VTAP will instantly disconnect the internet connection to app itself, and then show it's own detection screen like this (MBCP with v6.4.75+ will crash itself instead)

-> Engineering / Prototype ROMs usually comes with Root permission by default and some debug props. It does not work unless if the bypass patch Hide VTAP root detection activity & dialog is applied. I need to resolve GW934 measure in order to reuse this patch again.

Solution 1: Install HMAL-OSS and enable it on LSPosed then reboot device.

• After rebooted, open HMAL-OSS app, go to [Manage apps -> MB Bank] and enable it then select [Using %s preset] under Template config option and select [Root managers/Rooted apps -> OK]
• If you have randomized Magisk (like the Magisk app with Android logo and customized app name) then restore it back to original one on Magisk settings.
• Install MBZDefend-Fix module, it'll apply fixes for Magisk
• The app should open right after that, wait for 20 seconds, then press [Try again].

If you are using v6.4.80+, follow solution 2,3,4 too. Ignore if you are using v6.4.78 or lower.

Solution 2 (in case of Runtime Tampering): Download latest LSPosed (7199+) and install. After that, clear app data and try to open app again.

Solution 3 (Magisk): Disable "Zygisk" in Magisk settings, install ReZygisk module and reboot, then try to open app again

Solution 4 (KernelSU 30000+): Install specific 7a72 magic mount module and reboot then try to open app again (mountify / magic-mount-rs is reported as not working)

Bonus: You can also install MBZDefend-Fix module, it'll redirect you to vtapfix wiki for fixing VTAP detection

Secondary root detection layer (Zimperium) that present since v6.4.15+

Important

You must need to pass the first old root detection layer (VTAP) first in order to not facing GW908 error while logging in !

-> Secondary root detection layer (Zimperium) will be like this (Vietnamese only, even if you set app language to English)

-> It's detecting for suspicious mount, system fonts, etc,...

Solution: Download and install MBZDefend-Fix module, it's will open MBCP app with 1005/1007 error, but don't worry, just wait 20 seconds, then press [Try again] and it will enter to app, just login normally then. Don't forget to reboot the device after installed module :>

Notice: This solution might change with a easier solution by a bulit-in C++ hook in the future, so you don't need to do anything than just install the MBCP app just like before GW934 messure (v6.4.62 or lower), but only if i become a real dev with C++ knowledge.

GW525 error / This service has been upgraded when logging in

-> This error usually occurs if the current app version is discontinued from MB's side

Solution: Update to newer version that is not yet discontinued from MB's side or repatch the app with newer version if you are patching the app manually.

GW908 error when logging in

-> This error usually occurs when VTAP is not provisioned or failing to run properly due to VTAP detecting root or the app has no internet connection on the first startup.

Solution: Make the VTAP provision status to isProvisioningDone to true instead of false by trying to re-enter app multiple times or clearing app data then try to open again.

• If that doesn't helpful, use MBZDefend-Fix module and it will try to fix VTAP provision status, be sure to have actual internet connection and root app is hiding correctly first in order to not trigger VTAP.
• Login will work after VTAP is provisioned, which can be checked by installing MBZDefend-Fix module.

GW934 error when logging in

-> This error usually happens if something wrong with the app code and these libraries : [classes1->5.dex] [libmbshield.so] [libapp.so] [libdesignersactivists.so] | [libestimateddistributions.so] [libhumanargued.so] [libcloestmadagascar.so] or if the app is repacked with apktool

-> It's the messure from server-side and partially app-side backed by MB's developer to prevent app with patched libraries and dex from logging in.

Solution: If you are using pre-bulit MBCPApp, try to use another variant with latest available version, and if you are patching MBCP manually, be sure to don't apply any patches that is patching libraries and dex.

Notice: This might disappear as long as i become a real dev with C++ knowledge and implementing another bypass with C++.

Failing to generate 8-digit DigitalOTP code when performing transactions

-> This error are only happening randomly for some peoples. The solution that is reported as working is reset the DigitalOTP PIN code.

Solution: Reset the DigitalOTP PIN code then try again.

Face authentication (eKYC) failling with EKYC3002-MS6998 error

-> Singalarity eKYC system is detecting for su path [/system/bin/su] or some dangerous device fingerprint or some suspicious apps.

-> For some Lineage-based ROMs, it's has dirty fingerprint which causing SIngalarity eKYC system to always throw DF1000 error (it can be checked by logmb module and MB/MBCP with version older than v6.4.65, you can install it to test eKYC authentication by go to forgot password sceen, no need to logging in)

Solution: If you are using Magisk, try to flash MBZDefend-Fix module then try again.

In case if you are using LineageOS-based ROMs: flash Singalarity-LOSFix and reboot then try again.

• If you are using other root solution, be sure that the MBCPApp does not have root permission.

GW926 / GW999 / GW9xx (Transaction not completed)

-> This error happens on some bad ROMs.

Solution: Change another ROMs