
Three root tools all said "doesn't support your phone", so a compatibility table gained 113 stars in a week
What it is A compatibility index for temporary root on Android phones with locked bootloaders: by brand, model, firmware and kernel, it lists which tool to use and who has verified it, with a module compatibility table and a website on the side.
Why it took off In 2026 H2, several kernel vulnerabilities made temporary root workable again, and dozens of tools appeared, each covering a few models, leaving users unsure which to use. The author funneled traffic from his own awesome-android-root repo with 6k stars, and someone posted it on Reddit, bringing in a wave of device reports and stars.
CHow you could follow Don't build another temporary-root table. The next time one hotspot spawns a dozen mutually incompatible small tools, get ahead with a neutral compatibility table: copy the skeleton (README as the source of truth, issue templates to collect reports, tiers by who verified what), then funnel traffic from your own older repo. A Chinese-language temp-root table is a worthwhile bet.
- Data (updated daily) · Repo created 2026-10-19 · 161 stars · 7 days +117
GitHub · stars Data 2026-11-08 → 2026-11-20 (13 days, 13 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
fynks/awesome-temporary-root doesn't build any root tools. It only maintains one table: which phone, which firmware, which kernel, and which tool to use for temporary root. One month after launch it has 149 stars, 113 of them from the past week. It took off on three things: a wave of exploits spawned dozens of single-purpose tools, the author already had an old 6-star repo, and the table itself is detailed enough to be useful. The numbers are still small, but the playbook is worth understanding.
Three screenshots from one iQOO user
On the night of Nov 14, 2026, an iQOO Z9 Turbo user tried three temporary root tools in a row: Shark, RootMyVivo, and DFRoot. All three recognized his phone and kernel (6.1.145), then all refused to run: the first two showed "Current model/kernel not supported," and the third said "DEVICE NOT VULNERABLE." He gathered three screenshots, the full firmware build number, and the security patch date (2026-07-01), and the next day posted them in a GitHub repo issue titled "GhostLock patched, need new payload."
The same morning, a Vietnamese user reported good news in that repo: his HMD Nokia G22 (Android 14, kernel 5.15) got temporary root using DFRoot v4.7 with KernelSU 3.3.1. He also listed which modules worked and which two caused the phone to reboot repeatedly.
That repo is fynks/awesome-temporary-root. On 11-14 it received 7 device reports like these, and the next day stars rose by 35, its biggest day since launch.
Why temporary root needs a table
Rooting Android normally requires unlocking the bootloader first, but vivo, iQOO, some Samsung models, and carrier-locked phones don't allow it. In the second half of 2026, several kernel exploits went public: DirtyFrag (CVE-2026-43284), GhostLock (CVE-2026-43499), and a POSIX CPU timer bug. With them, temporary root that works without unlocking and disappears on reboot became possible again. Dozens of tools followed, such as GhostLock-App (3,101 stars), Root My Galaxy for Samsung only (1,648 stars), Root-My-Pixel (516 stars), Shark, RootMyVivo, TimerRoot, and KSuRoot in the Chinese community. Each tool only supports the devices and kernels it has adapted to, and each keeps its own compatibility list.
So the user's question becomes: for this phone, this firmware, and this kernel, which tool should I use? The only option is to check them one by one. Someone in a Facebook group put it this way: "Tried GhostLock, DirtyFrag, DFRoot, none support my kernel. A lot of people are asking."
What it is
An awesome list plus a site built with VitePress (awesome-temporary-root.pages.dev), MIT licensed, created 10-19. It doesn't touch exploits and doesn't ship a one-click tool. It's a neutral index that doesn't favor any single tool:
- 12 brand pages, about 130 device records: each entry lists the exact model, firmware build number, full kernel version, and which tool or root manager was used;
- Every entry is tagged with who verified it: maintainer-verified, user-reported, tested, experimental, upstream source, or unverified candidate;
- A module compatibility table (about 160 rows): it pulls in two community lists from r/androidroot and XDA, with sources credited;
- Anti-brick warnings: for each exploit, which kernel version it was patched in, and "don't test on the closest model."
- Three issue templates: report a device, report a module, or correct an entry, each requiring the full build number and kernel version.
The site works offline and includes an llms.txt so AI search can read it. The repo has an AGENTS.md stating that the README is the single source of truth and that site pages are generated by scripts, which suggests the author maintains it with a coding agent. It had 59 commits in its first month, 11-14 of them in just 11-16 to 27.
How the stars came in, day by day
| Date | star | What happened |
|---|---|---|
| 10-19 ~ 11-08 | 0 → 23 | Launch, 20 days, only 23 stars |
| 11-09 ~ 11-14 | 29 → 48 | 3 to 8 per day; launch posts appeared on r/androidroot and r/HyperOS (inferred to be between 11-12 and 11-14) |
| 11-14 | 48 | 7 device reports in one day |
| 11-15 | 83 | +35, the single biggest day |
| 11-16 ~ 11-19 | 100 → 149 | 8 to 26 per day, plus 10 more device reports (Pixel 7a, Pixel 10 Pro, vivo X300, Rokid glasses...) |
(Daily GitHub star counts and issue timing, as of 11-19.)
The stars came mainly from three places:
The author's older repo. fynks is effectively the only maintainer of awesome-android-root (6,060 stars). He has made 2,632 commits to it, and the second-place contributor has only 13. An old guide in that repo, "Root without unlocking bootloader," says "Our sister project Awesome Temporary Root maintains device/build lists, tool links and module reports," followed by a table pointing Samsung, Pixel, OnePlus, and vivo entries to the new repo. The split is clear: the old repo covers concepts and steps, and all device tables live in the new one.
A Reddit launch post. On r/androidroot, u/Hot-Lengthiness193 posted "[News] Awesome Temporary Root has just been created" in the voice of a passerby: "I came across a pretty interesting project... it's a repository where compatibility results for different devices using Temporary Root methods are collected." A post with the same title also appeared on r/HyperOS. Whether the poster is the author's alt account can't be confirmed.
Easy to find. The repo is tagged with 12 topics, including dirtyfrag, ghostlock, and temporary-root. Searching "awesome temporary root" puts both the repo and the site at the top.
It hasn't appeared on HN, no one on X has mentioned it, no media has covered it, and it hasn't made trending. Total: 149 stars, and it's still circulating in a small circle.
Why this one
Many people build tools, but in open source so far, only this one is building an index that spans all tools and goes down to firmware and kernel. The nearby projects look like this:
| Who | Scale | Compared with alternatives |
|---|---|---|
| The support table in GhostLock-App | 3,101 stars | Lists only its own kernel adaptations and ignores other exploit routes |
| Root My Galaxy | 1,648 stars | Samsung only, and a tool itself; it cites this table as an upstream source |
| KSuRoot (Chinese community) | 292 stars | One-click tool with 122 built-in device payloads matched automatically; it's a tool, while this project is an index |
| awesome-android-root-exploits | 48 stars | Collects exploit links only, doesn't organize by device or firmware, and is essentially not updated |
| Blog posts like droidrooter, Smzdm, and Bilibili tutorials | Article-level | Explain the steps but don't maintain a per-device table |
(GitHub stars, 11-19.)
It can take off because of four things:
- Fragmentation is the demand. The more tools and devices there are, the harder it is to answer "which one do I use?" Instead of building the Nth tool, it built the table everyone looks up.
- No need to recruit from scratch. The old repo points traffic to it, and the author is already a familiar name on r/androidroot.
- The table is real work. A wrong tool can brick a phone, so users will trust a table that lists build numbers and says who verified each entry.
- Users help fill it in. People who look something up and don't find their device submit a report using the template. Since 11-14, new reports have come in daily, so the table grows on its own, and the author mainly collects and checks them.
How long it stays hot depends on how long the exploits last
The iQOO user's screenshots already show the problem: the July security patch closed his device. Every vendor patch knocks out a batch of devices in the table, and the September patch has already shut down a number of them. The table stays hot only as long as the exploit wave lasts.
If it were you
C: The playbook is worth learning, but don't chase this topic. Someone already holds the temporary root compatibility table, and the author gets traffic from an older repo with 6 thousand stars, which late entrants can't match. Exploits keep getting patched, the window is narrowing, and the star ceiling is probably a few hundred. What's worth learning is the approach: when a hot topic spawns a pile of mutually incompatible small tools, don't build the Nth tool. Build the neutral compatibility table.
Good fit for: people who already run an awesome list with a few hundred to a few thousand stars, or who are known in a community and want to spin off a sub-list; people already deep in a rooting, hardware, or tooling scene who can read vendor support tables and are willing to check data every day.
Bad fit for: anyone wanting to build another temporary root index (fynks already syncs upstream and collects community reports, so you'd only be competing for leftovers); anyone without any channels (this repo had only 20 stars in its first 23 days, and it grew through the traffic and posts described above); anyone aiming for several thousand stars.
How to do it, from best to worst:
- Change topics: watch for the next moment when a hot topic spawns a dozen tools and users in groups ask "which one should I use?" and build the compatibility table first. Possible directions include whether local LLM quantization formats run on various GPUs and inference frameworks, and whether the same Skill or MCP works across coding agents (inferred; I haven't verified whether anyone is already doing this).
- Change language: the Chinese community is the hardest-hit area for temporary root (vivo, iQOO, and Xiaomi the most). The Smzdm post "All Android devices can now be temporarily rooted" has 918 bookmarks, and KSuRoot is a tool, not an index. There may be room for a Chinese compatibility table full of China-market firmware numbers. The bet rests on two points: it's already collecting reports from Chinese users, and the exploits are being patched.
- Whatever the topic, copy the skeleton: the README as the single source of truth, scripts generating the site and llms.txt, three issue templates, every entry tiered by "who verified it," and existing community lists pulled in with sources credited.
How to get users: put a sister-project link in your most-starred older repo, with a "what to find where" table; post "XX has just been created" in the relevant subreddit or forum; credit sources when you pull in community lists, since the original authors usually link back; fill in topics so you show up first when people search keywords.
When to move: within one or two months of the topic heating up, once there are more than ten tools and users start asking in groups "which one do I use?" Once someone publishes the first table, the index spot is taken.
Signs you've misread it: ① after the December patch, this repo's stars are still climbing and device reports keep coming, which means the exploit wave is lasting longer than estimated here, and the Chinese-language route is worth betting on; ② a compatibility table you build for another tool wave gets fewer than 30 stars within a week of posting, which means this approach can't take off without an older repo driving traffic; ③ conversely, if someone with no older repo reaches a thousand-plus stars on a single compatibility table, the ceiling is higher than estimated here and you should move faster.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one YuKongA/ghostlock-app SUPPORTED_DEVICES table Open source 2026-07-29 3,101 star Lists only its own GhostLock kernel profiles and doesn't cover DirtyFrag, TimerRoot, or other routes BuSung-dev/Root-My-Galaxy(+Payloads) Open source 2026-07-17 1,648 / 544 star Samsung only, and a tool itself; ATR cites it as an upstream data source Single-brand loaders such as Root-My-Pixel, TimerRoot, RootMyVivo, and Shark Open source 2026-08 to 11 Tens to 500 stars (Root-My-Pixel 516, Shark 241) Each has its own support table, and users have to compare them one by one; ATR aggregates and compares them hmascs/KSuRoot Open source 2026-08-14 292 star One-click tools ship with 122 payloads and auto-match; ATR is a neutral index and builds no tool ShivamXD6/Temporary-Root(Build Bytes) Open source 2026-10-20 Snapshot at 17 stars, now 404 In-app compatibility check, covering only the two built-in exploits awesome-android-root temporary root guide Open source 2024-07 (guide page rewritten 2026-10) Main repo 6,060 stars Same author; covers concepts and steps only, with device tables linked out to ATR DuncanParSky/awesome-android-root-exploits Open source 2025-09-06 48 star Only collects exploit links, no compatibility tables by model and firmware droidrooter.com temporary root guide Web 2026-10 Ranks high in search, traffic unknown SEO articles and release snapshots, no per-model build tracking r/androidroot "Temp root working modules" thread / XDA module list thread Other 2026-10 Thread-level Covers module compatibility only; ATR has absorbed it into its module pages - Where users come from
- Confirmed Traffic funneled from its own larger repo: awesome-android-root (6,060 stars, fynks has 2,632 commits) has a temporary root guide that says "Our sister project Awesome Temporary Root" and links every brand entry to ATR
- Confirmed Reddit (r/androidroot, r/HyperOS): u/Hot-Lengthiness193 posted "[News] Awesome Temporary Root has just been created" (1xvkdkv). Estimated from the post ID to be around 11-12 to 11-14, which lines up with the repo's 11-14 7 issues and 11-15 +35 stars. The original post was blocked by 403, so its upvote count is unknown, and whether the poster is the author has not been verified.
- Inferred Search and GitHub topics: 12 topics (dirtyfrag/ghostlock/temporary-root…). Brave and Jina both rank it first for "awesome temporary root" searches. The site ships an llms.txt.
- Confirmed Issue templates collect user reports: three templates (device_report / module_report / correction). External device reports arrive daily after 11-14, some with XDA or Reddit evidence links.
- Inferred X / HN / press: Live X search and x-radar turned up no related posts. No HN or press coverage found.
fynks/awesome-temporary-root: a cross-tool device compatibility index for "temporary root" on locked-bootloader Android
Research date 2026-11-18 (data card refreshed 11-19). Repo: github.com/fynks/awesome-temporary-root, site: awesome-temporary-root.pages.dev (VitePress, with PWA offline support and llms.txt), MIT, created 2026-10-19.
Bottom line
In the second half of 2026, kernel bugs DirtyFrag (CVE-2026-43284), GhostLock (CVE-2026-43499) and the POSIX CPU timer (CVE-2026-98260) made "root without unlocking the bootloader, gone on reboot" workable again. Dozens of loaders followed, each covering a few models (GhostLock-App, Root My Galaxy, RootMyVivo, TimerRoot, Shark, KSuRoot…). Each loader keeps only its own support table, and the question ordinary users most want answered, "which tool works for my phone, firmware and kernel," had no single place to check. This repo is a cross-loader compatibility index built to answer it. The author, fynks, is the active maintainer of awesome-android-root, which has 6.1k stars, and that repo points readers to this one as a "sister project" in its temporary root guide. In mid-November someone posted "[News] Awesome Temporary Root has just been created" to r/androidroot and r/HyperOS. Device report issues then started flooding in and stars jumped in a single day. In short, good timing on a trend, traffic from the author's larger repo, and solid content all stacked together. The scale is still small (149 stars), not a breakout.
1. Data
- Star curve (our GitHub repo, repo_day): 11-08 23 → 11-14 48 → 11-15 83 (+35, single-day peak) → 11-16 100 → 11-18 123 → 11-19 149. Over the last 7 days: +113, forks 11. 10-19 From repo creation to 11-08, those 20 days added only 23 stars. repositorystats.com's snapshot on day 20 of the repo (around 11-08) also shows 29 stars.
- Author: fynks (135 GitHub followers, bio reads "Just a random guy", no X account listed). Their largest repo is actually the org repo awesome-android-root/awesome-android-root (6,060 stars, created 2024-07). In the contributor list, fynks has 2,632 commits, while second place has only 13, so it is effectively a one-person project. Personal repos include debrid-services-comparison (639), awesome-kernelsu (125) and email-aliasing-comparison (85), all in the "comparison table / curated list" genre.
- Commit cadence: 59 commits from 10-19 to 11-18. 27 of them fell in the three days from 11-14 to 11-16 (switching to a VitePress site, adding structured device data, refreshing the module table). 11-18 includes commits like "updated data from upstream" that sync from upstream. The repo ships an AGENTS.md stating that the README is the single source of truth and that site pages are generated by script, which suggests the author maintains it with a coding agent.
- Issues: 30 (including PRs). External device reports and corrections began on 11-02, 11-14 brought 7 in one day (Nokia G22, iQOO Neo7, vivo Pad, Galaxy A15, Redmi Note 14 4G, and more). 11-15 to 11-18 brought 10 more (Pixel 7a/10 Pro, Vivo X300, Rokid Glasses, Doogee U10, and others), with Portuguese and Chinese-speaking users among them. This shows real people bringing their own devices to look up and report.
- Content volume (rough figures): 12 brand pages with about 250 device-table rows in total (excluding the status-definition table on each page, roughly 130 device records). About 160 rows on module pages. Every row must name the specific model, firmware build, full
uname -rkernel, and the loader and manager used, and is graded into Maintainer Verified / User Reported / Tested / Experimental / Upstream profile / Unverified candidate tiers. - The site awesome-temporary-root.pages.dev is not in Tranco's top 1M (our traffic database has no record), so traffic is very small or unmeasurable.
2. Competitors (doing the same job: telling you "can your device be temporarily rooted, and with which tool")
| Name | Where | Launched | Scale | How it differs |
|---|---|---|---|---|
| YuKongA/ghostlock-app ships a built-in SUPPORTED_DEVICES table | Open source | 2026-07-29 | 3,101 star(11-19) | Lists only its own GhostLock kernel profiles and ignores routes like DirtyFrag, TimerRoot and Adreno |
| BuSung-dev/Root-My-Galaxy(+Payloads) | Open source | 2026-07-17 | 1,648 / 544 star | Covers Samsung only, and as a tool; ATR references its payload table upstream |
| alex193a/Root-My-Pixel, TimerRoot, RootMyVivo and other single-brand loaders | Open source | From ¥2026-08 | Dozens to 500 stars | One table per vendor; users have to compare them one by one |
| hmascs/KSuRoot | Open source (Chinese community) | 2026-08-14 | 292 star | A one-click tool with 122 vendor payloads built in, matched on a three-level key of model + kernel + commit. It is a tool; ATR is a neutral index. |
| ShivamXD6/Temporary-Root(Build Bytes) | Open source / Telegram | 2026-10-20 | Exa snapshot shows 17 stars; techkaran.com wrote about it 10-31. The GitHub API now returns 404 (repo deleted or made private, unverified). | In-app compatibility check, covering only the built-in DirtyFrag/GhostLock |
| Temporary root guide page in awesome-android-root | Open source / site awesome-android-root.xyz | 2024-07 (guide page rewritten 2026-10) | Main repo 6,060 stars | Same author; the main repo covers concepts and steps only, and all device tables are linked out to ATR |
| DuncanParSky/awesome-android-root-exploits | Open source | 2025-09-06 | 48 star | Collects various root / bootloader-unlock exploit links, with no compatibility tables by model and firmware, and rarely updated |
| droidrooter.com blog (temporary root guide, "2026 phones that can still be rooted") | Web | 2026-10 | Ranks high in search results, traffic unknown | Only SEO articles and release snapshots, with no per-model build comparison |
| r/androidroot "Temp root working modules [List]" thread, XDA "List of modules working on temporal root" thread | Community | 2026-10 | Post | Covers module compatibility only; ATR absorbed both into its own module pages and credits the sources |
| Chinese community: What's Worth Buying "All Android devices can now be temporarily rooted" (546 upvotes / 918 saves), Zhihu, Bilibili tutorials | Chinese-language content | 2026-10/11 | Thread-level | Tutorials and overviews, no device tables maintained |
Bottom line: many people build loaders, but as far as the open-source scene goes, only this project has been seen building a "cross-loader compatibility index down to firmware and kernel." A Facebook group post said "tried GhostLock, DirtyFrag, DFRoot, none support my kernel, lots of people asking," which is exactly the pain point this project addresses.
3. Growth tactics (where users come from)
- Traffic from its own larger repo (confirmed): awesome-android-root's
docs/rooting-guides/root-without-unlocking-bootloader.mdsays "Our sister project Awesome Temporary Root maintains device/build lists, tool links and module reports." Below that is a "Looking for → Sister project sections" table that points Samsung, Pixel, OnePlus, vivo and other entry points to ATR. The larger repo's own PR #216 also mentions this. The larger repo's README step 4 directs readers with "don't want to unlock the bootloader? See temporary root." fynks maintains both. - Reddit post (confirmed, timing inferred): u/Hot-Lengthiness193 posted "[News] Awesome Temporary Root has just been created" in r/androidroot (post id 1xvkdkv), and r/HyperOS got a same-titled post too. The original wording in the search snippet is "I came across a pretty interesting project: Awesome Temporary Root, created by fynks. Basically, it's a repository where compatibility results for different devices using Temporary Root methods are collected", a third-party referral tone. Whether the poster is the author's alt account can't be verified. Going by the Reddit id and nearby post dates, the post went up around 11-12 to 11-14, right when 11-14 issues came pouring in and stars jumped +35 in a single day (11-15). Reddit blocked our scrape of the original post (403), so upvotes and comment counts are unavailable.
- GitHub search and topics (inferred): The repo carries 12 topics including dirtyfrag, ghostlock, temporary-root and kernelsu. When searching "awesome temporary root", both Brave and Jina rank it and the site first. The site also ships an llms.txt so AI search can cite it.
- Issue templates turn readers into contributors (confirmed): .github/ISSUE_TEMPLATE has three templates, device_report / module_report / correction, requiring the full build and kernel. Users who report their own device come back, and some issues link the XDA and Reddit posts as evidence, creating back-references.
- Not found: No X posts mentioning it turned up (the x live real-time search returned nothing relevant); it hasn't hit HN and has no media coverage; the repo is under 60 days old, so it couldn't have made trending.
4. Why it took off
- Timing: The temporary root thread has been hot from 9 through November. Upstream V4bel/dirtyfrag has 5,295 stars, ghostlock-app has 3,101 stars and is still climbing 20 to 50 a day, and Shark (a new repo from November) gained over 170 in a week. Many exploits, many loaders, fragmented devices: the resulting "fragmented information" is the most direct source of demand.
- Built-in author channel: The 6k-star large repo plus community awareness on r/androidroot means the new repo didn't have to start from zero. The large repo also had its own +166 jump at 11-12, which may have carried traffic over (causation unverified).
- The content isn't an empty shell: Every row is precise to the build and kernel, each entry is tagged with its verification source, and it spells out the patched-version floor for each CVE and safety warnings like "don't try the closest model number". In a context where a wrong flash can brick a device, this rigor is why users trust it.
- Retention mechanism: Users come to look up their own device and stay because they can submit reports. After 11-14, new device reports keep arriving every day, and the index grows on its own.
5. Differentiation
It doesn't do exploits or one-click tools. It only does a neutral, cross-loader, firmware- and kernel-precise compatibility index, plus a module compatibility table, and clearly labels who verified what. Others doing this either only cover their own loader's support list, or don't maintain device-level data at all, just tutorials and blog posts. This position was genuinely empty, which is the main reason it got stars and community reports. Still, the stars mostly came from referral traffic and the launch post; differentiation determines whether people stay after they arrive.
6. What to borrow
- "Build a large awesome list first; when a hot topic arrives, split out a specialized sub-repo; cross-link sister project entries inside the big repo." One person can reuse their own channels and repeat the same playbook.
- In a "fragmentation tooling wave" (lots of small tools, each covering one slice), a neutral compatibility matrix is more likely to become the link everyone cites than yet another tool.
- Use issue templates to collect structured user reports, tier them by verification source, and let the content grow itself; treat the README as the single source of truth, generate the site and llms.txt from it with scripts, and maintain it with a coding agent so one person can sustain high-frequency updates.
7. Risks and uncertainties
- The content depends entirely on unpatched vulnerabilities. Once a vendor's SPL update ships, the affected devices break (the September patch already disabled a batch), so the repo's lifespan is tied to how long the exploit wave lasts.
- The exact date and upvote count of the Reddit launch post, and whether the poster is the author, are unverified (Reddit returned 403 to our scrape).
- No star breakdown available (this token's stargazers endpoint returns 404), so we can't tell who the stars came from or which countries.
- The repo is very small. Whether the past week's 113 stars can carry it onto trending 60 days later is uncertain.
Sources
- Our github repo_day / repo_profile tables (2026-10-28 to 11-19)
- GitHub API: repo info, issues, commits, awesome-android-root contributor list (2026-11-18)
- github.com/awesome-android-root/awesome-android-root/blob/ma… (sister project section)
- www.reddit.com/r/androidroot/comments/1xvkdkv/news_awesome_t… (Jina / Brave search snippet)
- repositorystats.com/fynks/awesome-temporary-root (Exa snapshot)
- www.techkaran.com/2026/10/this-1-app-can-root-your-android-p…
- www.droidrooter.com/blog/temporary-root-android-without-unlo…
- post.m.smzdm.com/p/al38pmno/, zhuanlan.zhihu.com/p/2085027984361243848 (search snippets)
- x-radar local corpus and x live real-time search (no relevant posts)