kyk ny udhan dlu y a16 ny, lnjut a17
❤3
Signed illxです

Channel
@gt10updates
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2,331subscribers
+216 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001939184472 |
|---|---|
| Type | Channel |
| Username | @gt10updates |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/gt10updates |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @gt10updates/424 · this entry27 Jun 2026, 03:57 UTC | @INFINIXGT10Updates/31527 Jun 2026, 05:30 UTC | 1.00 | 1.6 hours |
| @gt10updates/427 · this entry30 Jun 2026, 11:29 UTC | @INFINIXGT10Updates/31730 Jun 2026, 11:29 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @INFINIXGT10Updates | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 4 June 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @gt10updates — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 10:06 | 2,331 | +2 |
| 6 Nov 2026, 13:27 | 2,329 | +2 |
| 3 Nov 2026, 12:46 | 2,327 | +13 |
| 31 Oct 2026, 14:45 | 2,314 | +11 |
| 28 Oct 2026, 23:40 | 2,303 | +15 |
| 25 Oct 2026, 19:29 | 2,288 | +8 |
| 23 Oct 2026, 02:20 | 2,280 | +14 |
| 20 Oct 2026, 05:56 | 2,266 | +2 |
| 17 Oct 2026, 08:36 | 2,264 | -1 |
| 14 Oct 2026, 14:40 | 2,265 | +12 |
| 10 Oct 2026, 22:01 | 2,253 | +13 |
| 5 Oct 2026, 00:40 | 2,240 | +6 |
| 26 Sept 2026, 06:21 | 2,234 | +13 |
| 17 Sept 2026, 03:19 | 2,221 | +11 |
| 13 Sept 2026, 10:01 | 2,210 | +1 |
| 9 Sept 2026, 15:39 | 2,209 | +11 |
| 4 Sept 2026, 04:19 | 2,198 | +17 |
| 1 Sept 2026, 01:03 | 2,181 | +11 |
| 29 Aug 2026, 05:16 | 2,170 | +14 |
| 26 Aug 2026, 12:55 | 2,156 | first reading |
20 posts held, back to 4 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
90 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 64.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 58 | 64.4% | |
| 🔥 | 22 | 24.4% | |
| 😭 | 6 | 6.67% | |
| 👍 | 2 | 2.22% | |
| 🥰 | 2 | 2.22% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 90 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 June 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
kyk ny udhan dlu y a16 ny, lnjut a17
❤3
Signed illxです
#ROM #ProjectInfinityX #Baklava #QPR2 #X6739 Project InfinityX 3.12 | UNOFFICAL | For Infinix GT 10 Pro | Android 16 Released: 06/08/2026 By fjrXTR ▪️Downloads ▪️Screenshots Changelogs: • Added support Kaeru • Fixed abnormally high clock speed on CPU Prime core • Fixed MTP (Media Transfer Protocol) connection issues • Kernel Upstream to v5.10.260 • Many more under the hood changes and optimization Known issues: • …
❤3
Signed illxです
XOS For GT 16.2.0 | Android 16 | OEM PORT | Stable Ported from Infinix GT 50 Pro For Infinix GT 10 Pro Release Date: 02 August 2026 Download ROM: Here Boot : Click Screenshot : See Update CH • Support Group Brief Changelogs: - Fixed Landscape notifications gone on default clock style - Fixed PIF Updater stuck - Fixed Launcher Clear apps animation and others animation - Fixed Sepolicy Leaks - Updated Boot Image sec…
❤5🔥4🥰1
#ROM #PixelOS #Baklava #QPR2 #X6739 Pixel OS - 16.2 | UNOFFICAL | For Infinix GT 10 Pro | Android 16 Released: 31/07/2026 By RyX27 x CarBeat Downloads Screenshot Changelogs : - June Security Patch - Include Lk patch with Kaeru - Remove PiHooks, we don't want any conflict with kaeru - Many more under the hood changes and optimization Notes: • Recommended to use PixelOS Recovery • User build • Stong Integrity by def…
❤2
Signed Ayunda Risu
#ROM #AxionAOSP #Baklava #QPR2 #X6739 AxionAOSP 2.8 ONEIRA | UNOFFICAL | HOTFIX | For Infinix GT 10 Pro | Android 16 Released: 29/07/2026 By fjrXTR ▪️Downloads ▪️Screenshots Changelogs: • Fixed abnormally high clock speed on CPU Prime core • Fixed MTP (Media Transfer Protocol) connection issues • Many more under the hood changes and optimization Known issues: • U tell me (gib logs or gtfo) Notes: • Do NOT replace…
🔥4❤2
Signed illxです
#ROM #AxionAOSP #Baklava #QPR2 #X6739 AxionAOSP 2.8 ONEIRA | UNOFFICAL | For Infinix GT 10 Pro | Android 16 Released: 28/07/2026 By fjrXTR ▪️Downloads ▪️Screenshots Changelogs: • Added Kaeru support • Many more under the hood changes and optimization Known issues: • U tell me (gib logs or gtfo) Notes: • Do NOT replace the kernel or else hotspot breaks • Strong intergrity if u using lk with kaeru patched • Signed …
❤6
Signed illxです
Satu Lagi, Notes udh disediakan, semua cara / tutorial pemasangan sudah ditulis sedemikian rupa agar mudah dipahami, coba sesekali kalian baca dulu tutorial yang ada di /notes sebelum kalian bertanya. Budayakan membaca!
❤1
Signed Hoshimachi Suiseii
Bagi kalian yang baru terjun ke dunia oprek janganlah bertanya ke ChatGPT atau AI lainnya untuk membantu kalian oprek atau instalasi ROM, ROOT dsb. Kenapa? Karena taruhan kalian 50/50 Hp berhasil nyala atau brick bahkan matot. Kenapa begitu? bukannya AI tau segalanya? Jawabannya simpel AI hanya tau cara oprek atau memasang Custom ROM, Root, dsb secara Generik alias sama rata dan cenderung untuk halusinasi. Sementara…
😭2
🐸 Kaeru For X6739 | Infinix GT 10 Pro Build Date : 19/07/2026 Download Recovery Flashable zip Download LK.img ( For advanced users ) Screenshot Features : - Grant strong integrity on newer ROMs without PIF or Modules - Spoofed device as locked bootloader - fastboot flashing & recovery still works - Enabled VBMeta How to use and complete guide read the following: Doksli Indonesia English Docs Updates Channel …
❤4
How to flash custom rom? after you ubl and flash custom recovery likes orangefox or twrp 1. reboot into recovery orangefox or twrp or whatever custom recovery 2. make sure you download the vendor_boot that rom aosp 3. flash vendor_boot in custom recovery ofox or twrp, in fastboot i dont think will work but try yourself 4. after you flash that vendor_boot from that rom make sure for format data your device in rec…
Signed 𝗙𝗜𝗡𝗢𝗫𝗗
LK Patch Remove orange state message for Infinix GT 10 Pro Credits • Kaeru by R0rt1z2 • Patched by R wantutri Tested by • @Zexshia • @finoxdd • @routaters Download ZIP IMG Notes • DWYOR, I'm not responsible for any risk and harm to your device, use this patch by your own risk • For Base XOS 14 only How to use? • Flash Zip File In TWRP. OR • Flash the lk.img in the fastboot using fastboot flash lk --slot=all lkpa…
❤6👍2
Signed 𝗙𝗜𝗡𝗢𝗫𝗗
lupa taro ges sori
Signed illxです
Showing the 12 most recent of 20 posts we hold for @gt10updates. 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.
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.
Named by 2 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@gt10updates named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“INFINIX GT 10 PRO UPDATES 🇮🇩” (@gt10updates), 2,331 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/gt10updates.
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.