Shamiko-v1.0-290-release.zip
1.9 MB
Changelog
- Hide more traces of Zygisk, passing more detection (e.g., ACE, GoTyme Bank, MyTransport.SG, ZainCash, DBS PayLah!, Singpass, Marriott, BPI, Apps using liapp, Apps using Arxan like CaixaBank Sign, etc.)
- Better support KSU
- Hide some traces introduced by other modules (e.g. PlayIntegrityFix)
- Guards the peace of Machikado
- Hide more traces of Zygisk, passing more detection (e.g., ACE, GoTyme Bank, MyTransport.SG, ZainCash, DBS PayLah!, Singpass, Marriott, BPI, Apps using liapp, Apps using Arxan like CaixaBank Sign, etc.)
- Better support KSU
- Hide some traces introduced by other modules (e.g. PlayIntegrityFix)
- Guards the peace of Machikado
LSPosed
Shamiko-v1.0-290-release.zip
Shamiko-v1.0.1-300-release.zip
1.9 MB
1.0.1
- Fix Android 10 support
- Fix Android 10 support
There's an annoument of a new detection of Magisk's resetprop revealed by others. But no worries, Shamiko v1.0 has fixed this. The only hiding solution that has this fix. (Mechanism in Chinese: https://t.me/CanyieChannel/188)
BTW, Shamiko also has many other fixes that other hiding solutions do not have😚.
Note that Storage Redirect will introduce extra traces that Shamiko is not hiding. This is bug from Storage Redirect and Shamiko is not responsible to hide it. You should disable it for better hiding.
BTW, Shamiko also has many other fixes that other hiding solutions do not have😚.
Note that Storage Redirect will introduce extra traces that Shamiko is not hiding. This is bug from Storage Redirect and Shamiko is not responsible to hide it. You should disable it for better hiding.
Microsoft is ending support for the Windows Subsystem for Android (WSA). As a result, the Amazon Appstore on Windows and all applications and games dependent on WSA will no longer be supported beginning March 5, 2025.
https://learn.microsoft.com/en-us/windows/android/wsa/
Right after we made MagiskOnWSA work again
https://learn.microsoft.com/en-us/windows/android/wsa/
Our simple native inline hook now works on RISCV 🤩. The next step is of course LSPosed on RISCV 😏.
LSPosed
Our simple native inline hook now works on RISCV 🤩. The next step is of course LSPosed on RISCV 😏.
And YES! We finally have a working LSPosed on RISCV64 architecture! 😉
Would you like LSPosed to resume
maintenance? / 阁下是否希望 LSPosed 恢复维护？
maintenance? / 阁下是否希望 LSPosed 恢复维护？
Final Results
4%
No / 不希望
48%
Yes, and do NOT care if it's open-source / 希望，并且不介意是否开源
48%
Yes, and will only use the open-source version / 希望，并且只会使用开源版本
在经过团队讨论后，LSPosed 项目组决定招募内部测试人员。该测试将采用内部部署方式进行，测试版本将仅通过内部渠道分发。
选定的内测人员应具有基本的操作能力，知道如何恢复变砖的设备，能向开发者提供日志。内测人员将无偿提供测试服务，并履行保密义务，严禁向他人分享任何测试软件包。请注意，内测人员无权访问软件的源代码。
软件测试完成后，根据测试结果和其他相关因素，项目组将决定是否恢复对外发布，并考虑将软件开源或部分开源。
内部测试版本将通过一个私有的 Telegram 群组进行分发。希望参与测试的用户需提交申请，并提供其 GitHub ID 以供审核。审核通过后，用户将被授权加入该群组。
具体的申请入群方式将在后续公布。
After team discussions, LSPosed project group has decided to recruit internal testers. The testing will be conducted through internal deployment, and the test versions will only be distributed through internal channels.
Selected beta testers should possess basic operational skills, know how to recover a bricked device, and be able to provide logs to developers. Beta testers will provide their testing services voluntarily and are required to adhere to confidentiality obligations, strictly prohibiting the sharing of any test software packages with others. Please note that beta testers will not have access to the software's source code.
Upon completion of the software testing, depending on the results and other relevant factors, the project team will decide whether to resume public releases and consider open-sourcing the software entirely or partially.
The internal test versions will be distributed through a private Telegram group. Users wishing to participate in the testing must submit an application and provide their GitHub ID for review. Once approved, users will be authorized to join the group.
Details on how to apply to join the group will be announced later.
选定的内测人员应具有基本的操作能力，知道如何恢复变砖的设备，能向开发者提供日志。内测人员将无偿提供测试服务，并履行保密义务，严禁向他人分享任何测试软件包。请注意，内测人员无权访问软件的源代码。
软件测试完成后，根据测试结果和其他相关因素，项目组将决定是否恢复对外发布，并考虑将软件开源或部分开源。
内部测试版本将通过一个私有的 Telegram 群组进行分发。希望参与测试的用户需提交申请，并提供其 GitHub ID 以供审核。审核通过后，用户将被授权加入该群组。
具体的申请入群方式将在后续公布。
After team discussions, LSPosed project group has decided to recruit internal testers. The testing will be conducted through internal deployment, and the test versions will only be distributed through internal channels.
Selected beta testers should possess basic operational skills, know how to recover a bricked device, and be able to provide logs to developers. Beta testers will provide their testing services voluntarily and are required to adhere to confidentiality obligations, strictly prohibiting the sharing of any test software packages with others. Please note that beta testers will not have access to the software's source code.
Upon completion of the software testing, depending on the results and other relevant factors, the project team will decide whether to resume public releases and consider open-sourcing the software entirely or partially.
The internal test versions will be distributed through a private Telegram group. Users wishing to participate in the testing must submit an application and provide their GitHub ID for review. Once approved, users will be authorized to join the group.
Details on how to apply to join the group will be announced later.
Shamiko-v1.1-344-release.zip
2.3 MB
Changelog
- Support Magisk Canary 27003
- Provide better hiding for font modules
- Minor bug fixes and compatibility updates
- Drop redundant resetprop handling
- Support Magisk Canary 27003
- Provide better hiding for font modules
- Minor bug fixes and compatibility updates
- Drop redundant resetprop handling
Shamiko-v1.1.1-357-release.zip
2.5 MB
Changelog
- Improve compatibility with some modules and upcoming ZygiskNext update
- Require Magisk Canary 27005+ or KernelSU 11903+ due to XZ zip format change
- Improve compatibility with some modules and upcoming ZygiskNext update
- Require Magisk Canary 27005+ or KernelSU 11903+ due to XZ zip format change
To everyone in our discussion group:
We have noticed that many users delete all their messages after speaking in our discussion group. We understand that you may do this for various reasons, but deleting a large number of messages at one time will cause the group recent actions to load very laggy, causing inconvenience to group admins. Regardless of your reason, such behavior will be regarded as malicious interference with group management. Doing so may get you muted or banned. Please do not abuse the function of deleting messages.
致我们讨论群组中的所有人：
我们注意到很多用户会在发言后删除自己所有消息。我们理解您这样做可能出于各种原因考虑，但一次性删除大量消息会导致群组操作记录加载极为缓慢，给管理员带来不便。无论您出于何种原因，此种行为会被视为恶意干扰群组管理。操作者可能会遭到禁言或封禁。也希望大家请勿滥用删除消息的功能。
We have noticed that many users delete all their messages after speaking in our discussion group. We understand that you may do this for various reasons, but deleting a large number of messages at one time will cause the group recent actions to load very laggy, causing inconvenience to group admins. Regardless of your reason, such behavior will be regarded as malicious interference with group management. Doing so may get you muted or banned. Please do not abuse the function of deleting messages.
致我们讨论群组中的所有人：
我们注意到很多用户会在发言后删除自己所有消息。我们理解您这样做可能出于各种原因考虑，但一次性删除大量消息会导致群组操作记录加载极为缓慢，给管理员带来不便。无论您出于何种原因，此种行为会被视为恶意干扰群组管理。操作者可能会遭到禁言或封禁。也希望大家请勿滥用删除消息的功能。