MediaTek scatter file: what it is and how not to get it wrong
Updated 2026-11-04
A scatter file is the partition map of a MediaTek firmware pack: it tells the flasher which image belongs in which partition. It is a table of contents, not the whole Android system.
Where it is used
Classic SP Flash Tool asks for a scatter and loads images from it. Service tools often hide the map behind model selection, but the need for a correct partition map remains.
What it means
Partition names, layout and image filenames. A map from another model will not match the silicon and can fail or worse.
Scatter vs DA/auth
Scatter describes what to write; DA/auth decide whether you may enter. On protected chips, scatter alone is not enough.
Typical mistakes
| Situation | Risk | Fix |
|---|---|---|
| Scatter from another model | wrong writes | use the pack for this model |
| Incomplete archive | missing images | download the full pack |
| Hand edits | brick risk | do not edit without expertise |
| Old scatter on new build | mismatch | use a matching release |
Practice
- Firmware only for the exact model code.
- Do not mix files across archives.
- In SP Flash Tool, point to scatter from the same pack.
- On auth errors, do not blame scatter first.
- Backup before risky operations.
SP Flash Tool vs service tools
SP Flash Tool shows scatter openly. UnlockTool/TSM hide it behind model choice. On protected chips, a service tool with auth is usually wiser than fighting SP Flash Tool.
Real example
A lookalike-line scatter caused mismatch errors. Replacing it with the scatter from the native pack cleared the fault immediately.
Two scenarios
Scenario 1: scatter mismatch - take the native archive. Scenario 2: scatter accepted, auth error - that is DAA/SLA, not scatter.
Checklist
- model equals pack;
- scatter from same archive;
- full image set;
- auth status understood;
- ownership confirmed.
Bottom line
Scatter must come from the firmware pack for your model. Do not treat auth failures as scatter problems.
Scatter and preloader
Scatter almost always references preloader. Knowing Preloader versus BROM is separate from having the right map. The map does not replace correct mode entry.
Why franken-packs fail
Mixing system from one build with scatter from another is a classic brick path. Use one complete release for the exact model code.
Storage habit
Keep firmware in folders named with full model codes and dates. A folder called new becomes a wrong-scatter trap months later.
Shop rhythm
Download pack, verify model, select scatter from it, decide if auth is required, then write. Any other order raises risk.
Legal use
Flash only owner devices and warn about data loss.
Final reminder
Scatter is the table of contents of a native pack, not a skeleton key and not a substitute for authorization.
Do not chase auth errors by swapping scatter files.
Quick summary
- scatter is a partition map;
- use it from the native pack only;
- do not mix images across builds;
- auth errors are not scatter errors;
- full archives only.
Pre-Download checklist
- full firmware archive;
- scatter from that archive;
- model code matches;
- VCOM installed;
- auth status known;
- customer warned about data.
Keep incomplete archives out of the active firmware library so they cannot be selected by mistake.
Bottom-line reminder
Identify the device and ownership first, prepare the PC second, choose the matching tool third, then operate. Refuse cleanly when support or ownership is missing.
Working bench habits
Keep verified drivers, a known-good data cable, a model job-log template and a dedicated backup folder. An organized bench prevents more failures than any mystery file from a chat group.
In disputed ownership or missing-support cases, a clear refusal protects both the customer and the shop better than a risky attempt.
FAQ
What is scatter?
A text map of MediaTek partitions for the flasher.
Is it the firmware itself?
No, it describes which images go where.
Why must it match?
A foreign scatter risks errors and damage.
Do service tools need it?
Often hidden behind model selection; SP Flash Tool needs it explicitly.
Related to DA?
Yes, they travel together, but DA is not scatter.
Should beginners edit scatter?
No.
Can renaming fix a mismatch?
No.
What first on error: scatter or DA?
Read the error; they are different stages.
Where should a beginner start?
Exact model, mode/driver and support check before payment.
What belongs in the job log?
Model, build/patch, mode, tool, error and result.
Can success be promised up front?
No: diagnose and match the list first.
Do I need a dedicated data cable?
Yes, keep a known-good data cable on the bench.
Should risks be noted for the customer?
Yes: model, operation and data or identity risks in the job record.
What if support is missing?
Do not start; suggest another tool or wait for coverage.
Is remote flashing without the device realistic?
No: modes and drivers need the phone on the bench.
How often should tool lists be rechecked on new Android?
Before every job, especially on 14/15.