Dump MB Logs for v6.4.60~v6.4.64 where log is hidden
This repository has been archived on 2025-11-28. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Cuynu 15929fde4d feat: customize.sh: also remove path.txt
Signed-off-by: Cuynu <cuynu@proton.me>
2025-08-24 23:17:20 +07:00
META-INF/com/google/android feat: logmb: initial commit 2025-08-24 16:19:39 +07:00
createmodule.sh fix: createmodule.sh: wrong archive name 2025-08-24 16:24:19 +07:00
customize.sh feat: customize.sh: also remove path.txt 2025-08-24 23:17:20 +07:00
module.prop feat: module.prop: bump v1.1-mbcp 2025-08-24 22:35:48 +07:00
README.md fix: README.md: wrong release link 2025-08-24 16:22:23 +07:00

Dump MB Logs

  • Since v6.4.60+, MB hidden the client.log under /data/data/com.mbmobile/cache or /data/data/com.mbmobile/app_flutter even without internet connection. This make debugging even more harder for us.
  • The only place where logs exists since v6.4.60+ is /data/data/com.mbmobile/app_flutter/hive_databases but it's encrypted and cannot be read.
  • Only way for now is force v6.4.59 libraries to current app.

Download from releases

Made module manually

unzip embee_v6.4.59_679_arm64-v8a_armeabi-v7a.apks
unzip split_config.arm64_v8a.apk
  • Grab libapp.so from extracted [split_config.arm64_v8a.apk] to logmb folder, then run
./createmodule.sh

For armeabi-v7a

  • Run this command under logmb folder
sed -i 's|arm64|arm|g' customize.sh
unzip embee_v6.4.59_679_arm64-v8a_armeabi-v7a.apks
unzip split_config.armeabi_v7a.apk
  • Grab libapp.so from extracted [split_config.armeabi_v7a.apk] to logmb folder, then run
./createmodule.sh