mbcp/mbbpatch_archive

Archived

Watch

Fork 0

bug: Patched MBCP app does not log in #2

Closed

opened 2026-01-29 17:26:15 +07:00 by vuthanhhai · 6 comments

vuthanhhai commented

2026-01-29 17:26:15 +07:00

I patched the MBCP app according to the documentation from the repository, including hiding VTAP and remove Zimperium, but the app shows error GW934 when logging in.

Hopefully the dev will fix it.

I patched the MBCP app according to the documentation from the repository, including hiding VTAP and remove Zimperium, but the app shows error GW934 when logging in. Hopefully the dev will fix it.

cuynu added the

bug

label

2026-01-29 17:27:42 +07:00

cuynu pinned this

2026-01-29 17:28:47 +07:00

cuynu commented

2026-01-29 17:43:08 +07:00

Owner

thanks for reporting, but this is not a BUG.

the app still works after patching but the login function return with GW934 error, right?

-> it's because the new MB's measure from 2025/09 as their attempt to kill patched apps from server-side to force users stop using patched app by checking app dex and libraries SHA256 hashes.
-> for more details, please read the README.md

workaround for it is still unknown, you can still patch the app but for now, don't use the following patches :

Block adjust volume on sEKYC
Remove invoke to mbshield
Hide VTAP root detection activity & dialog
Legacy hide VTAP activity & dialog
Remove new zimperium check

those patches can only be fixed if I found a method or implement another bypass for GW934, which is MB's measure from server-side.

you wonder what's the point if the interesting patches couldn't be applied? the purpose of mbbpatch is it still remove zimperium detection binaries after unpacking, while the VTAP is currently not usable anymore, but you can still bypass Zimperium with MBZDefend-Fix module as alternative to Remove new zimperium check. yeah, I know it's bad, but it usable.

thanks for reporting, but this is not a BUG. the app still works after patching but the login function return with `GW934` error, right? -> it's because the new MB's measure from 2025/09 as their attempt to kill patched apps from server-side to force users stop using patched app by checking app dex and libraries SHA256 hashes. -> for more details, please read the `README.md` workaround for it is still unknown, you can still patch the app but for now, don't use the following patches : - Block adjust volume on sEKYC - Remove invoke to mbshield - Hide VTAP root detection activity & dialog - Legacy hide VTAP activity & dialog - Remove new zimperium check those patches can only be fixed if I found a method or implement another bypass for `GW934`, which is MB's measure from server-side. you wonder what's the point if the interesting patches couldn't be applied? the purpose of mbbpatch is it still remove zimperium detection binaries after unpacking, while the VTAP is currently not usable anymore, but you can still bypass Zimperium with MBZDefend-Fix module as alternative to `Remove new zimperium check`. yeah, I know it's bad, but it usable.

vuthanhhai commented

2026-01-29 17:58:48 +07:00

Author

Thank you, the app is working now. I patched on Fedora Linux. I hope you can soon fix it further in the future. Goodluck !

vuthanhhai closed this issue

2026-01-29 17:58:49 +07:00

cuynu commented

2026-01-29 18:00:41 +07:00

Owner

@vuthanhhai wrote in http://cuynutt.ddns.net/mbcp/mbbpatch/issues/2#issuecomment-797:

Thank you, the app is working now. I patched on Fedora Linux. I hope you can soon fix it further in the future. Goodluck !

np, I hope if I can code either

@vuthanhhai wrote in http://cuynutt.ddns.net/mbcp/mbbpatch/issues/2#issuecomment-797: > Thank you, the app is working now. I patched on Fedora Linux. I hope you can soon fix it further in the future. Goodluck ! np, I hope if I can code either

vuthanhhai commented

2026-01-29 18:03:47 +07:00

Author

@cuynu wrote in http://cuynutt.ddns.net/mbcp/mbbpatch/issues/2#issuecomment-799:

@vuthanhhai wrote in #2 (comment):

Thank you, the app is working now. I patched on Fedora Linux. I hope you can soon fix it further in the future. Goodluck !

np, I hope if I can code either

You've pushed over 500 commits to the project, and now you're saying you don't know how to code? Are you kidding me?

@cuynu wrote in http://cuynutt.ddns.net/mbcp/mbbpatch/issues/2#issuecomment-799: > @vuthanhhai wrote in #2 (comment): > > > Thank you, the app is working now. I patched on Fedora Linux. I hope you can soon fix it further in the future. Goodluck ! > > np, I hope if I can code either You've pushed over 500 commits to the project, and now you're saying you don't know how to code? Are you kidding me?

cuynu commented

2026-01-29 18:22:48 +07:00

Owner

@vuthanhhai wrote in http://cuynutt.ddns.net/mbcp/mbbpatch/issues/2#issuecomment-800:

@cuynu wrote in #2 (comment):

@vuthanhhai wrote in #2 (comment):

Thank you, the app is working now. I patched on Fedora Linux. I hope you can soon fix it further in the future. Goodluck !

np, I hope if I can code either

You've pushed over 500 commits to the project, and now you're saying you don't know how to code? Are you kidding me?

I only knows the basic. thats it

@vuthanhhai wrote in http://cuynutt.ddns.net/mbcp/mbbpatch/issues/2#issuecomment-800: > @cuynu wrote in #2 (comment): > > > @vuthanhhai wrote in #2 (comment): > > > Thank you, the app is working now. I patched on Fedora Linux. I hope you can soon fix it further in the future. Goodluck ! > > > > > > np, I hope if I can code either > > You've pushed over 500 commits to the project, and now you're saying you don't know how to code? Are you kidding me? I only knows the basic. thats it

vuthanhhai commented

2026-01-29 18:32:17 +07:00

Author