Channel
@r0rt1z2_dumpster
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,299subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002584705594 |
|---|---|
| Type | Channel |
| Username | @r0rt1z2_dumpster |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/r0rt1z2_dumpster |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 02:36 | 1,299 | -1 |
| 12 Aug 2026, 09:44 | 1,300 | -1 |
| 9 Aug 2026, 12:01 | 1,301 | +1 |
| 6 Aug 2026, 08:05 | 1,300 | no change |
| 6 Aug 2026, 02:38 | 1,300 | first reading |
14 posts held, back to 18 November 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 1 pageof 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 14 posts for this entry, the most recent from 18 April 2026. An engagement rate over an empty window would be a number about nothing.
It's been a while since the last Penumbra update here, but 1.1.0 is now out! Mostly internal improvements, cleanup, and a lot of bug fixes, but there's also some new stuff. GPT parser was rewritten, BROM auth support was added, and there were updates across the DA/extensions side. There's also RPMB support (EMMC only for now) and USB logging. CLI got a few new commands (poke, rpmb, read-offset, write-offset, etc.)…
I wanted to post this earlier, but I hadn't had the chance to sit down and record a video about it. I've been working on refactoring and improving amonet-fastbrick to make it as generic as possible, and I'm really happy with the results! The exploit can now be used on any previously supported Echo, regardless of the FireOS version. This opens up a lot of possibilities for people who were stuck on unsupported firmwa…
Due to Crecker's uncooperative attitude, the original, and not vibe‑coded ;) PoC is now open source. Go give it some love: https://github.com/halal-beef/houston-pub
This is not related to my projects, but I'd like to raise awareness since, in my opinion, this is a bit fucked up and a real shame for the reverse engineering community. As some might know (or not), Umer (halal-beef) primarily, and others spent months reversing an Exynos iROM exploit that was originally discovered by a friend of mine (hello AA) (but was never made public). I knew about the PoC because of the latter…
I went ahead and extended support to the Nothing Phone 2A Plus (PacmanPro). THIS IS ONLY FOR THE NOTHING PHONE 2A PLUS. FLASHING A PRELOADER FROM ANOTHER DEVICE WILL HARD-BRICK YOUR PHONE. PROCEED WITH EXTREME CAUTION. Nothing has patched this vulnerability. READ CAREFULLY before attempting to use it on NothingOS 4, as it now requires additional steps and manual flashing. This release adds support for the latest N…
Since Motorola patched the previous exploit, we decided to release a new version of the unlock tool. This version !!!!!!! ONLY WORKS ON LINUX-BASED MACHINES !!!!!!!. If you use Windows, either stick to a locked bootloader or switch to an OS that actually works. Seriously, Windows USB and driver stack is so fundamentally broken that supporting it isn't worth anyone's time. Do yourself a favor and install Linux. Thi…
Back in 2024 (before this channel existed) I released a writeup on how I exploited the 2014 Amazon Fire HD6, which has a MT8135 SoC. Nobody had ever done this before and this SoC is very quirky. BROM USBDL mode is disabled, the Preloader is split into two parts, and only 3 devices in the world use this SoC. I managed to do everything, even gain PL3 (ARMv7 equivalent of EL3) arbitrary code execution, but every attem…
MediaTek DA2 exploit: heapb8 After weeks of reverse engineering and countless hours of debugging, shomy and I finally cracked the DA2 V6 exploit everyone's been talking about! We decided to call it heapb8 ("heapbait"), because Chimera baited us into chasing the wrong vulnerability for way too long. Full writeup with all the technical details: https://blog.r0rt1z2.com/posts/exploiting-mediatek-datwo/ Code is live …
I actually managed to create something useful out of what I was experimenting with back then. It’s probably not as cool as fenrir to most people (since, sadly, most people nowadays are only interested in "passing Play Integrity"), but it’s still useful for what shomy and I have been working on lately. This is a tiny PoC / payload that, in the hackiest way possible, exposes an insecure Preloader port that you can co…
Not tech-related, but here’s a picture channel that a few others and I run, in case anyone here is interested in photography. It’s not professional photography, but you can still find some nice wallpapers :) https://t.me/gsmc_pics
The 2nd Generation Echo Show 5 (2021), "cronos", joins the party! Special thanks to @jackmthws, @J0SH1X and @gilderchuck for all the testing and support! Have fun and happy hacking! MAKE SURE to read the thread carefully and CREATE A BACKUP of the STOCK FireOS installation IN CASE you ever want to go back. https://xdaforums.com/t/unlock-root-twrp-unbrick-amazon-echo-show-5-2nd-gen-2021-cronos.4772596/ LineageOS …
I really wonder whether the Lab126 employee who developed the Echo Dot firmware and “backported” A/B got fired. If the device fails to boot properly three times in a row (for example, due to a bad boot image or a bad recovery image), it will brick itself and refuse to go past the Preloader. At that point, you’re forced to open it and short the eMMC data lines to access BROM and reset the BCB boot counter. This isn…
Showing the 12 most recent of 14 posts we hold for @r0rt1z2_dumpster. 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 — 170,967 of 1,480,975entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 5 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.
@r0rt1z2_dumpster 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“R0rt1z2’s Dumpster” (@r0rt1z2_dumpster), 1,299 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/r0rt1z2_dumpster.
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.