𝒀𝒖𝒓𝒊 – Telegram
𝒀𝒖𝒓𝒊
18.4K subscribers
843 photos
108 videos
468 files
473 links
👨‍💻 Yuri Root Group – Root Community:
⚙️ All method Root & Hide Root
🛡️ Bypass Play Integrity, Detector Root, share latest keybox & modules
📚 Need help or want to learn? Join the discussion:
💬 Group Chat: t.me/yurichattt
📬 Contact me: @Yurii0307
Download Telegram
Yurikey26.xml
13 KB
Softban Keybox ( 3 certificates, 2 line Integrity, can pass Device Integrity )
Please open Telegram to view this post
VIEW IN TELEGRAM
28🔥5👍4
Anyway, 2 lines integrity are better than no integrity ( Device Integrity > No integrity ). No spoof provider
👍292👌2
My guess. Zygisk Next 1.3.0. Will be released tomorrow
13🎉3👌1
Zygisk next has built-in shamiko. So apatch won't have compatibility issues with shamiko anymore ( sure). The ability to hide root will probably be better too (maybe).
21😁1🤝1
And will you choose zygisk next + shamiko 1.3.0 or continue with rezygisk 417 + treatwheel 004 ?
12
Now rezygisk 417 + treatwheel better zygisk next + shamiko
14👍1
Zygisk no hello is outdated, it is inferior to shamiko and treatwheel
👍3
𝒀𝒖𝒓𝒊
Yurikey26.xml
I also updated the key in the YuriKey module. Just restart the device after a single action and you're done.😉
21👀3
Forwarded from 5ec1cff (5ec1cff)
Zygisk-Next-1.3.0-RC1-599-21e857e-release.zip
5.9 MB
ZygiskNext 1.3.0-RC1 预览版

1. 推出内置的 Zygisk 模块加载器——Zygisk Next linker,详细介绍请参考 Wiki
2. 整合 Shamiko 的大部分功能,排除列表增加「仅还原挂载」模式,允许在对应用加载模块的同时还原挂载变更 ^1;
3. 允许以匿名内存形式加载模块;
4. 正确实现对多个 zygote 的支持(如一加 zygote_ocomp);
5. 修复对低版本内核和部分 32 位设备的支持;
6. 修复一些其他问题。

注:

- ^1: ZN 并未整合 Shamiko 的 prop 隐藏与字体模块处理功能。若需要 prop 隐藏,请自行提取 Shamiko 的 service.sh,并通过 service.d 等方式开机启动;若需要在 A12+ 设备上使用字体模块,请安装 FontLoader 。安装 ZN 前无需卸载 Shamiko,Shamiko 即使安装也不会被加载。

- 可以使用 WebUI 或 CLI 配置新功能,CLI 命令如下:

/data/adb/modules/zygisksu/bin/zygiskd enforce-denylist <disabled|enabled|just_umount>
/data/adb/modules/zygisksu/bin/zygiskd memory-type <default|anonymous>
/data/adb/modules/zygisksu/bin/zygiskd linker <system|builtin>


所有选项即时生效。

Zygisk Next 1.3.0-RC1 Preview Release

1. Introduce a built-in Zygisk module loader — Zygisk Next Linker. For detailed information, please refer to the Wiki.
2. Integrate most of Shamiko’s functionality. Add a new “Unmount only” mode to the denylist, allowing module injection while restoring mount changes. ^1
3. Add support for loading modules to anonymous memory.
4. Properly implement multi-zygote support (e.g. OnePlus devices using zygote_ocomp).
5. Fix compatibility issues with older kernels and some 32-bit devices.
6. Fix several bugs and stability issues.

Note:

- ^1: ZN does not include Shamiko’s prop hiding or font module handling. If you need prop hiding, please extract service.sh from Shamiko and start it manually via service.d or similar methods. If you need to use font modules on Android 12+ devices, please install FontLoader. You do not need to uninstall Shamiko before installing ZN — even if Shamiko is installed, it will not be loaded.

- New features can be configured with WebUI and CLI. CLI command is as follows:

/data/adb/modules/zygisksu/bin/zygiskd enforce-denylist <disabled|enabled|just_umount>
/data/adb/modules/zygisksu/bin/zygiskd memory-type <default|anonymous>
/data/adb/modules/zygisksu/bin/zygiskd linker <system|builtin>


All changes will take effect immediately.

SHA256: c2dbd89a8d74b1ea2ed65d2f387728a2cc7f9a2d0f2bd80694c243579fccea55

real5ec1cff | Github
12👍6
𝒀𝒖𝒓𝒊
My guess. Zygisk Next 1.3.0. Will be released tomorrow
Just as I predicted
👍14👌731
Guys!

Since we have kernel integrated BBG (Baseband-guard):

https://github.com/vc-teahouse/Baseband-guard

1. Selinux is always enforcing.
2. Apps requiring selinux permissive won't work.
3. Tell the root apps developer to make it support selinux enforcing instead of telling users to set permissive! (You already have root access)
4. Don't use in development roms which requires selinux permissive.


This is a must have security feature especially since the growing count of malicious modules and new users who flash without knowing. This doesn't eliminate everything but reduces the risk of complete brick by 98%.

Only risk from malicious modules now is lose of data and maybe soft brick by removing boot and init_boot and other non critical partitions.. which can be solved by reflashing and restore from backups!


Hope everyone stays safe!

Also will be sharing a noscript if anyone wants to test BBG though!
10🔥1
BBG_TEST_CODE_v1.2.3.sh
3.8 KB
Run this noscript ( permisson root ) to check BBG work or not
🔥31
New setting to hide root better on Zygisk Next 1.3.0+
26🔥7👍2
I will go back to being a zygisk next user. Rezygisk and treatwheel are poorly compatible with my zygisk modules.
👌142
BBG_TEST_CODE_v1.2.3.sh
3.8 KB
This is a must have security feature especially since the growing count of malicious modules and new users who flash without knowing. This doesn't eliminate everything but reduces the risk of complete brick by 98%.
👌31
I will update the kernel soon to integrate this functionality.
👌1
𝒀𝒖𝒓𝒊
BBG_TEST_CODE_v1.2.3.sh
Run noscript this to check you have BBG or not
𝒀𝒖𝒓𝒊
BBG_TEST_CODE_v1.2.3.sh
This is just to test if you have it or not. It is not a BBG integration.