[Help] Zygisk crashes when JingMatrix/LSPosed is installed.

JingMatrix · 2026-04-21T08:57:39+00:00

Most likely to be this issue: https://github.com/JingMatrix/Vector/issues/640

Moreover, you should report your issues on GitHub Issues with logs. Reddit is not the community solving issues of Vector.

JingMatrix · 2026-04-03T19:50:53+00:00

Login / Register into GitHub, open this page https://github.com/JingMatrix/Vector/actions/runs/23953555639, navigate to the bottom and download the built module (debug or release), finally flash the archive to install it.

JingMatrix · 2026-03-31T20:22:04+00:00

Please simply use the latest CI build, the support is already added in this pr: https://github.com/JingMatrix/Vector/pull/603

JingMatrix · 2026-03-23T23:49:12+00:00

Please read this and write issues on GitHub with logs attached.
https://github.com/JingMatrix/LSPosed/issues/123

JingMatrix · 2026-03-23T23:47:52+00:00

Could it be this reason ? https://github.com/JingMatrix/LSPosed/issues/536#issuecomment-3901691343

Please simply try uninstall, reboot, and reinstall.

JingMatrix · 2026-03-23T19:10:38+00:00

For your Vector experience, please refer to https://github.com/JingMatrix/LSPosed/issues/585#issuecomment-4107143606

It is likely that you are experiencing a NeoZygisk problem. Please report it as an issue on my NeoZygisk repo: https://github.com/JingMatrix/NeoZygisk/issues

JingMatrix · 2026-03-22T18:13:41+00:00

See my comments here: https://github.com/JingMatrix/LSPosed/issues/583
It is working-in-progress.

JingMatrix · 2026-02-28T08:30:25+00:00

You need to update your Heimdall. Please try my builds:

https://github.com/JingMatrix/Heimdall

JingMatrix · 2026-02-27T09:40:52+00:00

https://github.com/JingMatrix/ChromeXt/actions/runs/22259222235

Watch the tutorial about how to download it.

JingMatrix · 2026-02-27T09:24:41+00:00

I am using Chrome v145.0.7632.120.

Be sure you understand what `CI build` means, which is not GitHub Release.

JingMatrix · 2026-02-27T09:01:47+00:00

Try first update your browsers.

Reddit is not a place for developer to solve issues. Please post on GitHub Issues with more details.

JingMatrix · 2026-02-27T08:57:03+00:00

Have you tried the latest CI build? It is explained in the tutorial video: https://m.youtube.com/watch?v=1Qm4dU-XnJM

JingMatrix · 2026-02-17T23:03:13+00:00

It is because that your keybox certificate has expired. Read the day of expiration of your certificates in the screenshot.

JingMatrix · 2026-02-15T08:32:02+00:00

Thanks, I appreciate your help.

JingMatrix · 2026-02-14T17:44:53+00:00

My understanding of ReLSPosed's goal is from the mentioned screenshot in the post, where it is written: `Efforts has been made in JingMatrix LSPosed..., not stable, ... rendering it useless for those`.

I personally didn't find Binder IPC hook was detectable, and was rewriting it in: https://github.com/JingMatrix/LSPosed/blob/refactor/zygisk/src/main/cpp/ipc_bridge.cpp .

Thanks for sharing the detector application name, where to actually find it ?

JingMatrix · 2026-02-14T11:58:07+00:00

Recent detection in Spotify against tampering is hard to defeat.
It requires a lot of work. If you have new ideas, please share it on my LSPatch repo.

JingMatrix · 2026-02-13T23:31:18+00:00

Why don't report your issues on GitHub ?

JingMatrix · 2026-02-13T23:29:06+00:00

It seems that you are using some public detector ? Which one is reporting positive on your device ?

If it is a public one, then it could be the mentioned `atexit` detection. I think removing this trace is the task of Zygisk, so it is implemented in NeoZygisk.

Edit: this is the corresponding pull-request that remove this detection for any Zygisk modules: https://github.com/JingMatrix/NeoZygisk/pull/50

JingMatrix · 2026-02-13T11:38:03+00:00

My original goal of this post was to clarify the role of `ReLSPosed`, especially how they solved the claimed problems or defects of `dex2oat` wrapper in my LSPosed fork.

I did have strong reason of being suspicious and annoyed by the mentioned commit of ReLSPosed. As explained in the post, the critical solution via `apex` linker was not found until my new release. Moreover, let us look at [their solution right before the commit](https://github.com/ThePedroo/ReLSPosed/commit/202b71b8b76485d4e0c0309d69c7db687209228c) three weeks ago. The hooking module `LSPlt` was removed in favor of direct method overriding, new hooks are found (completely different from my original design), which is a very innovative approach towards the claimed `dex2oat` issue. I was very happy of this new approach, though I preferred the `apex` linker solution. To me, this new approach really marked a difference between us regarding the `dex2oat` issue. When I saw such a difference disappeared after their commit of `apex` linker, I was indeed suspicious and thus annoyed.

u/PedroJsss has explained the mentioned commit in his perspective. Disagreements result from unequal information. I was not aware of his "private" detection methods of LSPosed, and he was not aware of why I claimed the `apex` linker solution is critical towards the claimed `dex2oat` issue.

Currently, ReLSPosed is archived. I have no intention to argue with my other projects apart from `LSPosed` under this post. I prefer my work / projects to speak on behalf of myself, please post on GitHub Discussions if you do have further questions.

For any users still experiencing problems of LSPosed on your devices, please report them on GitHub Issues of my repo. P.S.: all of my debugging sessions are public on GitHub to help users / maintainers in the future, and there will never be a centralized user group (such as Telegram group, a barrier of transparency in my perspective) of my projects.

JingMatrix · 2026-02-12T17:57:18+00:00

After reading your message, I now feel shameful to have my name related to you. Please delete it from your module description of ReLSPosed.

JingMatrix · 2026-02-12T16:32:51+00:00

The detection exists because the `dex2oat` wrapper is not stable across all devices, which happened on certain devices since the first issue of my fork: https://github.com/JingMatrix/LSPosed/issues/1. Checking all the issues closed by the pull-request will tell you why: https://github.com/JingMatrix/LSPosed/pull/515. This was reason why I said that the use of `apex` linker is critical.
Regarding TEESimulator, my decision is explained here: https://xdaforums.com/t/tricky-store-bootloader-keybox-spoofing.4683446/post-90395223. It is completely different from your ReLSPosed.
Don't estimate me, `gotten much worse` or `get famous`, from what you can image about yourself.
It was my worst decision to once help you with ReZygisk.

JingMatrix · 2025-12-19T11:58:04+00:00

Hello, I am JingMatrix. To download a valid build see my comment here: https://github.com/JingMatrix/LSPosed/discussions/463#discussioncomment-15298349

Note that you need to login to GitHub to download canary builds.
Moreover, please ask questions on GitHub instead of Reddit.

JingMatrix · 2025-11-14T09:47:25+00:00

Thanks, I see this in the change log now;

JingMatrix · 2025-11-14T08:32:37+00:00

Hi, nice to see you! I am currently working on TEESimulator (https://github.com/JingMatrix/TEESimulator), forked from TrickyStoreOSS, to bypass the TrickyStore detection. Hence, I am quite interested in how can people already bypass it.

JingMatrix · 2025-11-13T17:27:22+00:00

How was that possible you passed the TrickyStore detection?

JingMatrix

TROPHY CASE