Channel

Magisk alpha

@magiskalpha

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

66,221subscribers

+989 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 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	6 August 2026
Last confirmed live	25 October 2026
Measurements held	47
Confirmed unchanged	1 time, most recently 25 October 2026
On Telegram	t.me/magiskalpha

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

47 measurements spanning 80 days, net +989. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 65,084–66,369 and does not start at zero.

Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)	Subscribers	Change
25 Oct 2026, 03:14	66,221	+2
24 Oct 2026, 04:58	66,219	+30
23 Oct 2026, 07:21	66,189	+12
22 Oct 2026, 06:49	66,177	+9
20 Oct 2026, 23:45	66,168	+23
20 Oct 2026, 00:46	66,145	+9
19 Oct 2026, 00:47	66,136	+8
18 Oct 2026, 01:07	66,128	+39
17 Oct 2026, 01:09	66,089	+20
16 Oct 2026, 03:18	66,069	+9
15 Oct 2026, 01:08	66,060	+4
13 Oct 2026, 18:40	66,056	+34
10 Oct 2026, 02:02	66,022	+51
5 Oct 2026, 20:01	65,971	+93
30 Sept 2026, 08:02	65,878	+172
18 Sept 2026, 05:56	65,706	+26
16 Sept 2026, 02:19	65,680	+51
14 Sept 2026, 05:59	65,629	+17
12 Sept 2026, 14:00	65,612	+37
10 Sept 2026, 14:37	65,575	first reading

Engagement

21 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 162 pages of 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 21 posts for this entry, the most recent from 5 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos: 22
Links: 89

Lifetime counters from Telegram’s own channel header, read 25 October 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

5 Sept 2026, 07:18 UTC≈42,200 viewsread 25 October 2026

File

96221b69-alpha 31000 https://github.com/LSPosed/Magisk/commits/8b98ae6b8c9aa45f4722eaa9917416e484e6279f

10 May 2026, 15:44 UTC≈411,000 viewsread 25 October 2026

File

无法规避的Magisk识别方案已经公开：https://github.com/eltavine/Duck-Detector-Refactoring/pull/22 检测方法说明和概念验证app：https://github.com/LSPosed/DirtySepolicy

24 Feb 2026, 07:39 UTC≈162,000 viewsread 25 October 2026

File

e8a58776-alpha 30700 https://github.com/LSPosed/Magisk/commits/76dbeef1beabe45ba60262ccd70f12206eb21679

2 Feb 2026, 04:11 UTC≈173,000 viewsread 25 October 2026

看来攻击者想把这个频道也屏蔽掉，但由于消息是转发消息，所以只有这一条死掉了，连原消息都正常。从这条消息的统计报告看，其它频道转发的都存活。攻击者在大量举报上传了apk的频道，建议从私有频道转发避免公开频道被完全屏蔽。

2 Feb 2026, 04:02 UTC≈180,000 viewsread 25 October 2026

Photo

ccb264f3-alpha 30600 这条转发消息被屏蔽了，但原消息正常，请进群下载：https://t.me/c/1414270883/143996

13 Jan 2026, 17:35 UTC≈145,000 viewsread 25 October 2026

https://pki.consumer.huawei.com/ca/ 发现华为公示了根证书，但是没有发现 RootDeviceAttestationCa 的实际使用样本，可能仅鸿蒙设备使用（没有计划开发鸿蒙版本或者苹果版本的密钥认证

2 Dec 2025, 05:38 UTCviews —

Posted without readable text

2 Oct 2025, 12:54 UTC≈210,000 viewsread 25 October 2026

File

c3db2e36-alpha 30400 https://github.com/LSPosed/Magisk/commits/ab751a4d70ccbe267c098db8670eaa9836dd51a1

30 Sept 2025, 09:47 UTC≈188,000 viewsread 25 October 2026

Magisk v30.3 的su坏了，部分设备上不能工作，更新通道已经撤回推送，安装v30.4。 https://github.com/topjohnwu/Magisk/issues/9373

30 Sept 2025, 09:39 UTC≈154,000 viewsread 25 October 2026

File

f16e93c7-alpha 30300 https://github.com/LSPosed/Magisk/commits/f893a39eb7a2af649fe94e17fe1c5281c0f1b41d

20 Sept 2025, 17:16 UTC≈132,000 viewsread 25 October 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≈121,000 viewsread 25 October 2026

为密钥认证引入新的根证书此更改增强了敏感应用程序认证流程的安全性和可靠性。已为 Android 密钥认证生成了新的根密钥。新的根密钥是 ECDSA P-384 密钥，未来计划使用 ML-DSA（后量子数字签名算法）密钥。使用 RKP 的设备将于 2026 年 2 月开始接收以此新证书为根的证书。到 2026 年 4 月 10 日，使用 RKP 的设备将只使用新的根证书。

Showing the 12 most recent of 21 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

笨蛋不是笨蛋
@BDovo_Pro · 4151 post FolkPatch(Aster)
@FolkPatch · 11,7981 post LSPosed
@LSPosed · 199,1491 post WeaveMask
@WeaveMask · 7171 post MA了解一下~⛱
@toknowma · 751 post

Republishes

Channels on the register whose posts this channel has forwarded.

新钱庄
@newqianzhuang · 2,4251 post

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 10 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.

Duck Apps
@duck_detector · 16,3035 posts CharlieOS || Marble
@CharlieOS_Marble · 1964 posts GeekOS || Updates
@GeekOS_Updates · 7111 post Ginkgo Development
@GinkgoDevelopment · 291 post 零七八碎
@lingqibasui42 · 51 post Magisk Lite
@MagiskLite · 2,0131 post 𝕬𝖙𝖑𝖆𝖓𝖙𝖊𝖆𝖓'𝖘 𝕯𝖚𝖒𝖕 & 𝕲𝖚𝖎𝖉𝖊𝖘 🇵🇸
@native_atlantean · 2821 post OnePlus | Склад
@oneplus_rep · 3991 post Backup
@rmx1911indo · 4901 post ULTRA的DP合集
@ultra_dp · 9371 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

LSPosed
@LSPosed · 199,149#1

5ec1cff
@real5ec1cff · 39,067#2

Real Nullptr
@nullptr_dev · 21,223#3

HyperCeiler | Canary Test
@cemiuiler_canary · 20,790#4

Voyager HyperOS Update
@VoyagerMIUIUpdate · 22,042#5

InstallerX
@InstallerX · 8,872#6

HyperCeiler | Release & Notice
@cemiuiler_release · 27,642#7

akashaProxy ci channel
@akashaProxy · 1,806#8

QAuxiliary CI Builds
@QAuxiliary_CI · 19,675#9

Pillboard
@Pillboard · 3,483#10

AdClose Official
@AdClose · 12,311#11

NPatch
@NPatch · 19,791#12

橘橘橘子汁 & 🍊
@microblock_pub · 15,793#13

XiReiki
@xiayinlily · 2,876#14

RandomFree
@c001apk · 6,598#15

不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 22,277#16

Wa Enhancer Updates & Tips
@waenhancher · 36,410#17

Pixel Props
@PixelProps · 14,323#18

Reveny
@reveny1 · 7,529#19

Play integrity fix NEXT
@PifNEXT · 6,786#20

Hakuma is cute ~
@huskydg · 4,126#21

GApps Leaks
@GappsLeaks · 21,564#22

Sakion Team
@Sakion_Team · 2,017#23

Peter's Space - Repo
@PeterSpaceXiaomi · 2,545#24

SafetyNet, CTS, and Play integrity
@ctsfixes · 2,423#25

Android dumps
@android_dumps · 5,728#26

Pzqqt's News Channel
@pzqqt_c · 4,006#27

LibChecker CI
@libchecker_ci · 3,583#28

🌿 ReZygisk (δ) 🧬
@rezygisk · 3,812#29

Magisk Base || Magisk modules and other
@magiskmodules22 · 12,938#30

WSTprojects
@WSTprojects · 28,105#31

DataBackup
@databackupchannel · 2,294#32

Loop Projects | #TeamFiles
@loopprojects · 9,710#33

XPL-EX
@xpl_ex · 3,073#34

DrDisagree's Projects
@DrDsProjects · 9,623#35

rootArt
@rootart · 830#36

Mishaal's Android News Feed
@MishaalAndroidNews · 11,727#37

Rem01 Project
@rem01schannel · 10,978#38

Yigit Cloud
@xiaomichinacloud · 533 (as read 21 August 2026)#39

PUI The Newsroom 😍
@PUINewsroom · 13,936#40

Read from Telegram’s recommendation API, most recently 21 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

LSPosed
@LSPosed · 199,149
Telegram ranks this channel #4 of 57 here — alongside 56 others — read 17 August 2026

5ec1cff
@real5ec1cff · 39,067
Telegram ranks this channel #7 of 51 here — alongside 50 others — read 2 September 2026

Hide My Applist
@HideMyApplist · 41,672
Telegram ranks this channel #8 of 24 here — alongside 23 others — read 30 August 2026

Real Nullptr
@nullptr_dev · 21,223
Telegram ranks this channel #9 of 54 here — alongside 53 others — read 28 September 2026

LSPosedArchives
@LSPosedArchives · 26,326
Telegram ranks this channel #17 of 36 here — alongside 35 others — read 14 September 2026

SCENE Downloads
@scene2023 · 56,799
Telegram ranks this channel #17 of 50 here — alongside 49 others — read 12 September 2026

APatch Updates
@APatchChannel · 25,743
Telegram ranks this channel #19 of 37 here — alongside 36 others — read 14 September 2026

HyperCeiler | Release & Notice
@cemiuiler_release · 27,642
Telegram ranks this channel #21 of 51 here — alongside 50 others — read 12 September 2026

KernelSU
@KernelSU · 69,828
Telegram ranks this channel #34 of 49 here — alongside 48 others — read 14 September 2026

This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 25 October 2026 — this entry's latest reading, not the date you are reading this.

“Magisk alpha” (@magiskalpha), 66,221 subscribers as measured 25 October 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.