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 research and tally reports from many places where AI box owners compare notes: owner forums, social media groups, chat communities and comment threads, in several languages. 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 FAQs and announcements from community moderators are recommendations, not owner reports. A fix they recommend is marked “Recommended in the community FAQ” and never adds to a count. A step-by-step guide written by an owner who did it themselves counts as one report.
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. One owner counts once per fix, however many threads repeat the story, and one message is never counted on two fixes of the same page. 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 owners reported the result of trying that fix and three said it worked. It is not a success rate for all owners.
Each report is one of three things:
- Worked: the owner said the fix solved it. Counted in both numbers.
- Did not work: the owner tried it and the problem stayed. Counted in the second number only.
- No result yet: the owner got the fix (a file, instructions, a reply from support) but has not said how it ended. Counted in neither number; the page may mention it as pending, never as a failure.
4. Label the risk
| Label | What it means |
|---|---|
| Low risk | Normal Android or app settings, an app from an official store, a cable, power supply or accessory. No developer access and no system changes. A setting change can still reset your preferences, and a cable or part must match exactly what the fix names (a different Y-cable or charger is a different fix). |
| 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; once we have checked it is not a duplicate of a report already counted, it counts like any other.