This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from ReZygisk CIs
ReZygisk-v1.0.0-452-7102fcd-debug.zip
680.3 KB
Trusted CI #138: 7102fcd3ac1d2fa78bb3d3a76f2ffb56292a2254
fix: failed injection of libzygisk.so
fix: failed injection of libzygisk.so
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from KowSU
KowSU_v3.0.0-140-g738ecb5e_32319-release.apk
10.2 MB
Manager
Branch: master
#ci_2319
Compare
Workflow run
Add home screen shortcut support for modules with action and webui.
For module developers, refer to official guide for custom shortcut icon.
Long press module card to open shortcut dialog
Branch: master
#ci_2319
manager/userspace: Add desktop shortcut support for module action/webui (tiann#3159)
---
manager: Add expandable module description support (tiann#3161)
Compare
Workflow run
Add home screen shortcut support for modules with action and webui.
For module developers, refer to official guide for custom shortcut icon.
Long press module card to open shortcut dialog
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from ZalexDev Blog | Stryker | Developer (ZalexDev)
GitHub
GitHub - zalexdev/wpair-app: WPair is a defensive security research tool that demonstrates the CVE-2025-36911 (eg WhisperPair)…
WPair is a defensive security research tool that demonstrates the CVE-2025-36911 (eg WhisperPair) vulnerability in Google's Fast Pair protocol. This vulnerability affects millions of Blueto...
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from Rene's Channel (Rene)
BRENE-v0.0.18.zip
115.3 KB
BRENE - A SuSFS module for custom kernels with SuSFS patches
- remove: invalid paths
- improve: hide_sus_mnts_for_all_procs to follow latest SUSFS patches
- release: v0.0.18
You need to rebuild your kernel with latest SUSFS patches for better hiding results, thanks to Simon for the update the SUSFS patches.
And you can use the latest ReZygisk CI 452+ for better hiding results.
Source Code - GitHub
- remove: invalid paths
- improve: hide_sus_mnts_for_all_procs to follow latest SUSFS patches
- release: v0.0.18
You need to rebuild your kernel with latest SUSFS patches for better hiding results, thanks to Simon for the update the SUSFS patches.
And you can use the latest ReZygisk CI 452+ for better hiding results.
Source Code - GitHub
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
No deleted account found from
💬 Send /lang to change language of the bot
90 scanned users from this group 🚫👻💬 Send /lang to change language of the bot
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
Forwarded from PerformanC (Pedro)
Recently, quite a lot of rather interesting commits were committed to ReZygisk. Some of those include quite big changes, and I'm here to information the community about the most memorable changes.
1. Full rewrite of the codebase
Since June 15th of 2024, our focus has been always two things: transparency, and the rewrite to C. While transparency had been achieved in the first button clicked, the rewrite was being performed slowly over time.
However, today, January 18th of 2026, we finally completed our goal, porting the last pieces of C++ code to C (while -release reduced 10kb only, debug reduced by 120kb!), finalizing and starting a new era on ReZygisk's development (and licensing state).
This will ensure a much more seamless development experience, and stability since we won't need to worry with messing C++ anymore.
2. Remote CSOLoader
Since the start, all Zygisk implementations relied on the system linker to load Zygisk modules and the Zygisk library itself. Both Zygisk Next and ReZygisk were the first to step up the game few months ago, and utilize custom linkers to load the Zygisk modules.
However, the libzygisk.so was still being loaded with the system linker. ReZygisk, a day ago, got a huge improvement: the utilization of a custom linker to load libzygisk.so remotely, removing the need of heuristics or any code to hide Zygisk traces from the linker.
This makes it impossible for ReZygisk to be detected through such vectors, which were the most abused by RASPs (Runtime application self-protection) to detect the existence of Zygote injectors.
3. Installation size reduced
ReZygisk and other forks of Zygisk Next, changed a lot of things. However, one behavior was kept: copy the library files to a temporary folder to change their permissions. This made the installation size be significantly bigger.
Now we removed that, not only leading to the simplification of the system architecture of ReZygisk, but also reducing the installation size by around 30%.
It takes time, but they come as they should be in the end. We expect to deliver more improvements over time, to soon release Release Candidate 5.
Also, an update for translators to update their respective language's README, as it has been updated.
Your dedication is for nothing, their criticism will not ever stop.
They never left their minds, but in the end you will get to the top.
It is subjective, but what matters are the eyes of those who cares,
And to the eyes-less, find the answer for all of their questionnaires.
1. Full rewrite of the codebase
Since June 15th of 2024, our focus has been always two things: transparency, and the rewrite to C. While transparency had been achieved in the first button clicked, the rewrite was being performed slowly over time.
However, today, January 18th of 2026, we finally completed our goal, porting the last pieces of C++ code to C (while -release reduced 10kb only, debug reduced by 120kb!), finalizing and starting a new era on ReZygisk's development (and licensing state).
This will ensure a much more seamless development experience, and stability since we won't need to worry with messing C++ anymore.
2. Remote CSOLoader
Since the start, all Zygisk implementations relied on the system linker to load Zygisk modules and the Zygisk library itself. Both Zygisk Next and ReZygisk were the first to step up the game few months ago, and utilize custom linkers to load the Zygisk modules.
However, the libzygisk.so was still being loaded with the system linker. ReZygisk, a day ago, got a huge improvement: the utilization of a custom linker to load libzygisk.so remotely, removing the need of heuristics or any code to hide Zygisk traces from the linker.
This makes it impossible for ReZygisk to be detected through such vectors, which were the most abused by RASPs (Runtime application self-protection) to detect the existence of Zygote injectors.
3. Installation size reduced
ReZygisk and other forks of Zygisk Next, changed a lot of things. However, one behavior was kept: copy the library files to a temporary folder to change their permissions. This made the installation size be significantly bigger.
Now we removed that, not only leading to the simplification of the system architecture of ReZygisk, but also reducing the installation size by around 30%.
It takes time, but they come as they should be in the end. We expect to deliver more improvements over time, to soon release Release Candidate 5.
Also, an update for translators to update their respective language's README, as it has been updated.
Your dedication is for nothing, their criticism will not ever stop.
They never left their minds, but in the end you will get to the top.
It is subjective, but what matters are the eyes of those who cares,
And to the eyes-less, find the answer for all of their questionnaires.
This media is not supported in your browser
VIEW IN TELEGRAM