How we verify fixes
Every number on this site is a count of community reports. Here is how those counts are made.
1. Collect reports
We read exports of public AI box owner communities, mainly a large Russian-language forum that has been active since 2023. Each question thread is tagged by what happened next: the person who asked confirmed a fix worked, someone else confirmed it, or the thread stayed open.
Pinned community FAQs, which forum moderators maintain from many earlier reports, are treated as confirmed sources too.
2. Turn threads into cases
A case is one combination of device, symptom and fix. When the same fix for the same symptom appears in several threads, the cases are merged and the confirmation count goes up. Every case keeps the IDs of the messages it came from, so a claim on a page can always be traced back to its source.
3. Rank the fixes
On each page, fixes under Fixes, ranked are ordered by the number of confirmations first, then by risk (safer fixes before riskier ones when the counts are equal). A fix only appears there if at least one report confirmed it. Suggestions nobody has confirmed go under Things to try (unverified).
“Worked for 3 of 4 reports” means four reports tried that fix and three said it worked. It is not a success rate for all owners.
4. Label the risk
| Label | What it means |
|---|---|
| Safe | Settings only. Nothing here can damage the box. |
| Advanced | ADB, engineering menus or a local firmware update. Reversible if you follow the undo steps. |
| Brick risk | QFIL/EDL, root, verity or system-file edits. A mistake can leave the box unbootable. |
Every Advanced or Brick-risk fix includes an Undo / rollback block and a warranty warning.
5. Check against manufacturer documentation
Device facts (chipset, Android version, official firmware pages) are checked against manufacturers’ own pages before a device hub is published. We link only to official download pages and never host files.
6. Keep it fresh
New community exports are processed monthly. New confirmations raise the report count, a firmware that fixes a problem changes the status to “Fixed in firmware”, and the “Last reviewed” date on the page changes only when we actually re-read the new reports.
What we do not claim
We have not tested these fixes on our own hardware, and we say so on every page. If you try a fix, tell us whether it worked; your report counts like any other.