10 May 2026, 15:44 UTC≈301,000 viewsread 13 August 2026
File
无法规避的Magisk识别方案已经公开：https://github.com/eltavine/Duck-Detector-Refactoring/pull/22 检测方法说明和概念验证app：https://github.com/LSPosed/DirtySepolicy
Channel
Magisk alpha
@magiskalpha
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
65,281subscribers
+49 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001303307491 |
|---|---|
| Type | Channel |
| Username | @magiskalpha |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/magiskalpha |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:03 | 65,281 | +1 |
| 12 Aug 2026, 05:33 | 65,280 | +27 |
| 11 Aug 2026, 08:05 | 65,253 | +11 |
| 10 Aug 2026, 05:25 | 65,242 | +1 |
| 9 Aug 2026, 05:21 | 65,241 | +6 |
| 7 Aug 2026, 09:26 | 65,235 | +2 |
| 6 Aug 2026, 08:30 | 65,233 | +1 |
| 6 Aug 2026, 04:06 | 65,232 | first reading |
Engagement
20 posts held, back to 7 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 22
- Links
- 88
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
24 Feb 2026, 07:39 UTC≈119,000 viewsread 13 August 2026
File
e8a58776-alpha 30700 https://github.com/LSPosed/Magisk/commits/76dbeef1beabe45ba60262ccd70f12206eb21679
2 Feb 2026, 04:11 UTC≈137,000 viewsread 13 August 2026
看来攻击者想把这个频道也屏蔽掉，但由于消息是转发消息，所以只有这一条死掉了，连原消息都正常。从这条消息的统计报告看，其它频道转发的都存活。 攻击者在大量举报上传了apk的频道，建议从私有频道转发避免公开频道被完全屏蔽。
2 Feb 2026, 04:02 UTC≈149,000 viewsread 13 August 2026
Photo
ccb264f3-alpha 30600 这条转发消息被屏蔽了，但原消息正常，请进群下载：https://t.me/c/1414270883/143996
13 Jan 2026, 17:35 UTC≈124,000 viewsread 13 August 2026
https://pki.consumer.huawei.com/ca/ 发现华为公示了根证书，但是没有发现 RootDeviceAttestationCa 的实际使用样本，可能仅鸿蒙设备使用 （没有计划开发鸿蒙版本或者苹果版本的密钥认证
2 Dec 2025, 05:38 UTCviews —
Posted without readable text
2 Oct 2025, 12:54 UTC≈195,000 viewsread 13 August 2026
File
c3db2e36-alpha 30400 https://github.com/LSPosed/Magisk/commits/ab751a4d70ccbe267c098db8670eaa9836dd51a1
30 Sept 2025, 09:47 UTC≈176,000 viewsread 13 August 2026
Magisk v30.3 的su坏了，部分设备上不能工作，更新通道已经撤回推送，安装v30.4。 https://github.com/topjohnwu/Magisk/issues/9373
30 Sept 2025, 09:39 UTC≈145,000 viewsread 13 August 2026
File
f16e93c7-alpha 30300 https://github.com/LSPosed/Magisk/commits/f893a39eb7a2af649fe94e17fe1c5281c0f1b41d
20 Sept 2025, 17:16 UTC≈124,000 viewsread 13 August 2026
Pixel 设备的官方 Root 方法 Android允许解锁设备获得Root权限，这是官方Root方法，至少对 Pixel 设备有效。 需要在RamDisk中加入3个文件： /force_debuggable 空文件，这是开关； /adb_debug.prop，设置需要的属性，例如： ro.adb.secure=0 ro.debuggable=1 ro.force.debuggable=1 /userdebug_plat_sepolicy.cil，设置需要的SELinux政策。 开机时，init会检查开关然后读取并加载属性和政策，开机后可以使用adb root获得root权限。 你可以使用MagiskBoot工具重新打包RamDisk，不过SELinux政策需要自行编写。
16 Sept 2025, 09:43 UTC≈114,000 viewsread 13 August 2026
为密钥认证引入新的根证书 此更改增强了敏感应用程序认证流程的安全性和可靠性。已为 Android 密钥认证生成了新的根密钥。新的根密钥是 ECDSA P-384 密钥，未来计划使用 ML-DSA（后量子数字签名算法）密钥。 使用 RKP 的设备将于 2026 年 2 月开始接收以此新证书为根的证书。到 2026 年 4 月 10 日，使用 RKP 的设备将只使用新的根证书。
16 Sept 2025, 09:42 UTC≈105,000 viewsread 13 August 2026
使用远程密钥配置淘汰工厂密钥配置 对于搭载 Android 16 的设备，系统仅支持 RKP，此政策将逐步淘汰工厂密钥配置。它改进了配置和管理认证密钥的方式，并在 Android 15 政策（其中 RKP 支持为可选）的基础上进行了扩展。 RKP 可防止密钥泄露，因为系统不会将密钥直接编程到设备上。无法从设备中删除这些密钥，如果需要撤销某个密钥，可以将撤销操作定向到单个设备。
Showing the 12 most recent of 20 posts we hold for @magiskalpha. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank
Citation-graph rank — 9,531 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 8 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
CharlieOS || Marble
@CharlieOS_Marble · 2044 postsDuck Apps
@duck_detector · 13,4392 postsGeekOS || Updates
@GeekOS_Updates · 7161 postGinkgo Development
@GinkgoDevelopment · 301 postMagisk Lite
@MagiskLite · 2,0621 postOnePlus | Склад
@oneplus_rep · 4041 postBackup
@rmx1911indo · 5031 postULTRA的DP合集
@ultra_dp · 9291 post
@CharlieOS_Marble · 2044 postsDuck Apps
@duck_detector · 13,4392 postsGeekOS || Updates
@GeekOS_Updates · 7161 postGinkgo Development
@GinkgoDevelopment · 301 postMagisk Lite
@MagiskLite · 2,0621 postOnePlus | Склад
@oneplus_rep · 4041 postBackup
@rmx1911indo · 5031 postULTRA的DP合集
@ultra_dp · 9291 post
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Magisk alpha” (@magiskalpha), 65,281 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/magiskalpha.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.