【恢复更新】SOMCP 项目恢复更新

Goxwax

1111111

先生王

谢谢分享

ias乐

首先感谢大佬提供的工具 请问一下怎么和mt管理器的mcp协同工作了 能否出一期教程。

liu2514

最新版设置目录时崩溃，m40p手机
SOMCP crash report
Time: 2026-08-23 22:15:22.501 +0800
Version: 1.0.19 (20)
Process: com.soreverse.mcp (25417)
Thread: main
Android: 12 (SDK 31)
Device: HUAWEI NOH-AN01
ABI: arm64-v8a, armeabi-v7a, armeabi

Exception
=========
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.OPEN_DOCUMENT_TREE }
        at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2177)
        at android.app.Instrumentation.execStartActivity(Instrumentation.java:1785)
        at android.app.Activity.startActivityForResult(Activity.java:5730)
        at g60.startActivityForResult(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:8)
        at e60.b(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:342)
        at xa2.U(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:32)
        at n6.c(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:11)
        at o20.u(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:127)
        at ek2.e(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:167)
        at ek2.e(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:146)
        at ek2.e(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:146)
        at ek2.e(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:146)
        at wa1.b(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:34)
        at m00.a(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:134)
        at p8.H(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:95)
        at p8.m(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:369)
        at p8.dispatchTouchEvent(r8-map-id-95c5c572962ddf9c4fe2f53d9d1e1365d2bda450028e0cffee0ef524ae79aea9:78)
        at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3343)
        at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:3004)
        at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3343)
        at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:3004)
        at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3343)
        at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:3004)
        at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3343)
        at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:3004)
        at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:898)
        at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:2077)
        at android.app.Activity.dispatchTouchEvent(Activity.java:4431)
        at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:817)
        at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:805)
        at android.view.View.dispatchPointerEvent(View.java:15242)
        at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:8344)
        at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:8084)
        at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:7459)
        at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:7516)
        at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:7482)
        at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:7664)
        at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:7490)
        at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:7721)
        at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:7463)
        at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:7516)
        at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:7482)
        at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:7490)
        at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:7463)
        at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:10956)
        at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:10858)
        at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:10811)
        at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:11209)
        at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:310)
        at android.os.MessageQueue.nativePollOnce(Native Method)
        at android.os.MessageQueue.next(MessageQueue.java:374)
        at android.os.Looper.loopOnce(Looper.java:163)
        at android.os.Looper.loop(Looper.java:293)
        at android.app.ActivityThread.loopProcess(ActivityThread.java:10022)
        at android.app.ActivityThread.main(ActivityThread.java:10011)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:586)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1242)


Recent application logs
=======================
22:15:05.100 I SignatureVerifier: rz_native load OK
22:15:05.142 I RizinNativeEngine: librz

ChatGPT4

liu2514 发表于 2026-8-23 22:18
最新版设置目录时崩溃，m40p手机
SOMCP crash report
Time: 2026-08-23 22:15:22.501 +0800

已修

liu2514

ChatGPT4 发表于 2026-8-24 01:07
已修

大佬神速。佩服！

lickumap

大佬，六六六

超级小萌新

大佬，牛批 感谢分享，给力支持！

cqzy520

看看隐藏

ChatGPT4

cqzy520 发表于 2026-8-24 18:42
看看隐藏

我们这篇文章没有隐藏

oin

反馈下

【SOMCP 缺陷反馈】so_open 打开大型 SO(20MB/数万符号)长时间卡住,后续工具全 SERVER_BUSY

现象:
- 打开约 21MB 的 arm64-v8a .so(4.5万+动态符号、6.9万+重定位),so_open 数分钟不返回;
- 或已返回 workspaceId,但后续所有重型工具持续 SERVER_BUSY,直到后台分析结束(真机数分钟,模拟器数十分钟);
- 真机/模拟器表现一致,仅时长不同;小 SO 无此问题。

根因(EngineRuntimeSources.kt open() L124-130):
so_open 打开时在重型闸门内同步调用 NativeEngine.functions() → Rizin rzFunctions 全量函数分析。该返回值仅用于 counts.analyzedFunctions 展示,却承担了最重的分析成本,导致打开卡死 + 闸门被占。

建议修复(改动最小):
1. so_open 打开时不触发 rzFunctions,analyzedFunctions 直接用 symbolFunctions.size(轻量 ELF 符号计数);函数级分析留给 analyze_functions 主动调用。
2. SettingsStore: requestTimeoutMs 默认 30000→120000+, maxConcurrentTools 默认 1→2。
3. 顺带: Storage.kt scanApk 缓存键用 size=0 + modified=currentTimeMillis 导致缓存永远 miss,每次扫描全量解压大 APK,建议传 walk 的真实 size/modified。

涉及文件: engine/EngineRuntimeSources.kt, core/SettingsStore.kt, engine/Storage.kt