Match the exact model number, region code, and branch name. Similar model numbers are different devices.
Firmware lives here. USB drivers, flash tools, and tutorials are on FlashGuideHub.
This collection covers every major firmware branch released for the OPPO A9 (PCAM10) and its China Mobile variant (PCAT10), plus the global export build (CPH1969EX). The files span three package formats: original OPPO OFP/RAR payloads for use with the MSM Download Tool or OPPO Flash Tool, MediaTek scatter packages for SP Flash Tool partition-level flashing, and one ISP/chip-level full userdata dump for UFI Box or similar ISP equipment. Not every format is right for every job — pick based on what the device is doing and what tools you have on the bench.
The OFP/RAR originals (the non-SCATTER files) are the cleanest option for a standard stock restore after a bad OTA, bootloop, or post-root recovery. The SCATTER variants are for when the device won’t negotiate USB at all and you need to push partitions directly via SP Flash Tool. The UFI dump is a chip-read full userdata backup — it belongs in ISP recovery workflows, not routine reflashing. Last updated: May 2026
Included Models
- PCAM10 — OPPO A9 (2019), China full-netcom (all-carrier) variant. MediaTek Helio P70 (MT6771WT), 4GB / 6GB / 8GB RAM tiers, 128GB eMMC 5.1 storage. Ships with ColorOS 6 on Android 9.
- PCAT10 — China Mobile-specific subvariant of the same A9 hardware. Identical Helio P70 chipset and storage config; band selection is tuned for China Mobile network requirements. Functionally interchangeable with PCAM10 firmware for most repair purposes, but cross-flashing should be done deliberately, not accidentally.
- CPH1969EX — Global export build, present only in the converted scatter package. Same MT6771WT silicon; regional differences are in the ColorOS regional package and carrier defaults, not in the hardware.
Firmware by Model
- PCAM10 — OPPO A9 (China Full-Netcom)
- PCAT10 — OPPO A9 (China Mobile)
- CPH1969EX — OPPO A9 Global Export
PCAM10 — OPPO A9 (China Full-Netcom)
The PCAM10 is the standard domestic A9 unit and the one most of these files target. On the Helio P70, the most common failure pattern leading people here is a stuck OTA — the A-to-F branch upgrade has a documented history of partial writes that leave the phone in a recovery loop with a corrupted system partition. The OFP payloads from the F-branch (F.13, F.14, F.15, F.17) are the correct fix for that. Don’t try to push a scatter file for that job unless the phone won’t show up in SP Flash Tool’s USB device list at all.
The CONVERTED files in this collection are community-produced scatter packages derived from the original OFP images. They work, but they carry a caveat: partition alignment was handled by whoever did the conversion, not OPPO’s build system. For a device that powers on and can enter download mode, use the original OFP file first. The CONVERTED packages are the fallback when OPPO’s tool chain isn’t cooperating.
PCAT10 — OPPO A9 (China Mobile)
The PCAT10 shares its silicon and board design with the PCAM10 — same MT6771WT, same eMMC, same physical layout. The practical difference is the modem firmware tuning and the preloaded carrier apps in the system partition. Filenames in this collection that carry both PCAM10 and PCAT10 in the name (e.g., PCAM10_PCAT10_11_F.17_200828) confirm dual-model support for that build. Those packages can restore either variant. Single-model PCAM10 files should not be pushed to a PCAT10 as a first choice — the modem partition can end up mismatched, which presents as missing LTE bands or SIM non-recognition after flash.
CPH1969EX — OPPO A9 Global Export
The global build appears only in one file here: A9(PCAM10_CONVERTED_GLOBAL_CPH1969EX_11_C.31_SCATTER.rar. It’s a scatter package of the C.31 global build, converted from the original OFP. The CPH1969EX designation is the export model identifier and carries the global ColorOS regional package — different default language set, different regional app bundle, and no China carrier features. This is the right restore target if the phone was originally sold as a global unit and got flashed with a CN build somewhere along the way; pushing the CN branch back onto it will work electrically but leaves the regional package in a mismatched state.
Firmware Table
These packages are original stock ROMs mirrored for preservation, as the manufacturer no longer provides public downloads for this model.
| Model | Filename | Version | Region | Android | ROM Type | Size | File Hash | Notes | For | Download |
|---|---|---|---|---|---|---|---|---|---|---|
| PCAM10 | Oppo_A9_PCAM10_11_A.11_190729.zip | A.11 | CN | Android 9 | OFP/ZIP payload | 5 GB | Not provided — verify file size before flashing | Earliest A-branch build in this collection; baseline Android 9 stock. No hash embedded in filename. | Android 9 baseline restore, post-root stock recovery | Download A.11 ZIP (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.17_200828_dc90228f.rar | F.17 | CN (dual-model) | Android 11 | OFP/RAR payload | 4.82 GB | dc90228f (partial hash in filename) | Most recent F-branch build in this collection; covers both PCAM10 and PCAT10. Use this for F-branch restores unless there’s a specific reason to go earlier. | General stock restore, failed F-branch OTA recovery | Download F.17 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.15_200730_956c7d3a.rar | F.15 | CN (dual-model) | Android 11 | OFP/RAR payload | 4.75 GB | 956c7d3a (partial hash in filename) | F-branch intermediate; use F.17 unless you need this specific build. | General stock restore, F-branch rollback | Download F.15 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.14_200719_4c11acd7.rar | F.14 | CN (dual-model) | Android 11 | OFP/RAR payload | 4.9 GB | 4c11acd7 (partial hash in filename) | F-branch build dated July 2020. | General stock restore, F-branch rollback | Download F.14 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.13_200826_75a61388.rar | F.13 | CN (dual-model) | Android 11 | OFP/RAR payload | 5.13 GB | 75a61388 (partial hash in filename) | Note: build date (200826) is later than F.14 (200719) — F.13 may be a re-signed or regional variant build, not an older binary. | General stock restore, F-branch rollback | Download F.13 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_C.43_200918_c87bc03e.rar | C.43 | CN (dual-model) | Android 10 | OFP/RAR payload | 6.66 GB | c87bc03e (partial hash in filename) | Largest file in the collection; C-branch is the Android 10 / ColorOS 7 line. C.43 is the highest C-branch build here. | Android 10 stock restore, C-branch OTA failure recovery | Download C.43 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_C.31_200918_4564331f.rar | C.31 | CN (dual-model) | Android 10 | OFP/RAR payload | 4.32 GB | 4564331f (partial hash in filename) | C-branch intermediate build. | Android 10 stock restore, C-branch rollback | Download C.31 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_C.15_200918_d2cbdcfc.rar | C.15 | CN (dual-model) | Android 10 | OFP/RAR payload | 5.36 GB | d2cbdcfc (partial hash in filename) | Earlier C-branch entry point build. | Android 10 baseline restore | Download C.15 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_A.09_190626_1cca1a33.rar | A.09 | CN (dual-model) | Android 9 | OFP/RAR payload | 4.46 GB | 1cca1a33 (partial hash in filename) | Earliest dual-model A-branch build; Android 9 / ColorOS 6 launch-period firmware. | Android 9 baseline restore | Download A.09 (Google Drive mirror) |
| PCAM10 | PCAM10_11_F.11_2022072319323225.rar | F.11 | CN | Android 11 | OFP/RAR payload | 3.34 GB | Not provided — verify file size before flashing | Later-dated F-branch build (July 2022 timestamp); no embedded hash. | General stock restore, F-branch OTA failure recovery | Download F.11 (Google Drive mirror) |
| PCAM10 | PCAM10_11_F.07_2021101921225089.rar | F.07 | CN | Android 11 | OFP/RAR payload | 3.43 GB | Not provided — verify file size before flashing | October 2021 F-branch build; no embedded hash. | General stock restore, F-branch rollback | Download F.07 (Google Drive mirror) |
| PCAM10 | PCAM10_11_A.11_190729_1cca1a33.rar | A.11 | CN | Android 9 | OFP/RAR payload | 4.42 GB | 1cca1a33 (partial hash in filename) | RAR-format equivalent of the A.11 ZIP above; same build date (190729), same hash suffix. | Android 9 baseline restore, post-root stock recovery | Download A.11 RAR (Google Drive mirror) |
| PCAM10 (converted) | PCAM10_CONVERTED_TO_F11_C.17_OS10_SCATTER.rar | C.17 / F11 conversion | CN | Android 10 | MTK scatter package (community conversion) | 2.1 GB | Not provided — verify file size before flashing | Community-converted scatter package. Not an OEM-issued scatter image. Use only when SP Flash Tool direct partition flashing is required and original OFP is not viable. | SP Flash Tool partition-level restore, unresponsive device recovery | Download C.17 Scatter (Google Drive mirror) |
| PCAM10 (converted) | PCAM10_CONVERTED_GLOBAL_OS10_SCATTER.rar | Global / OS10 | Global | Android 10 | MTK scatter package (community conversion) | 2.09 GB | Not provided — verify file size before flashing | Global-region converted scatter package; Android version confirmed by OS10 in filename. Community conversion — not OEM scatter output. | Global region stock restore via SP Flash Tool | Download Global Scatter (Google Drive mirror) |
| PCAM10 (converted) | PCAM10_11_F.07_2021101921225089_SCATTER.rar | F.07 | CN | Android 11 | MTK scatter package (community conversion) | 3.2 GB | Not provided — verify file size before flashing | Scatter conversion of the F.07 OFP. Community-converted. Smaller than the OFP variant despite being the same build — expected after partition image extraction. | SP Flash Tool partition-level F-branch restore | Download F.07 Scatter (Google Drive mirror) |
| PCAM10 (converted) | PCAM10_11_A.18_200220_10d3a3db_SCATTER.rar | A.18 | CN | Android 9 | MTK scatter package (community conversion) | 4.54 GB | 10d3a3db (partial hash in filename) | A.18 is a later A-branch build not represented in the OFP collection above — this scatter is the only source for this specific build version. | SP Flash Tool Android 9 partition-level restore | Download A.18 Scatter (Google Drive mirror) |
| PCAM10 | PCAM10_11_A.11_FILE_DUMP_FULL_USERPART_OS9_UFI.rar | A.11 | CN | Android 9 | ISP full userdata chip dump (UFI Box) | 1.85 GB | Not provided — verify file size before flashing | Not a flashable ROM package. This is a raw chip-read dump of the user partition from an A.11 device. Use only with UFI Box or compatible ISP tool for chip-level write operations. Wrong use of this file on a live device will overwrite personal data partitions completely. | ISP/chip-level recovery, dead eMMC restoration | Download A.11 UFI Dump (Google Drive mirror) |
| PCAM10 (converted) | PCAM10_11_A.11_190729_1cca1a33_SCATTER.rar | A.11 | CN | Android 9 | MTK scatter package (community conversion) | 4.3 GB | 1cca1a33 (partial hash in filename) | Scatter conversion of the A.11 build. Same hash suffix as the OFP versions above, confirming source parity. | SP Flash Tool Android 9 partition-level restore | Download A.11 Scatter (Google Drive mirror) |
| PCAM10 / CPH1969EX (converted) | A9(PCAM10_CONVERTED_GLOBAL_CPH1969EX_11_C.31_SCATTER.rar | C.31 | Global (CPH1969EX) | Android 10 | MTK scatter package (community conversion) | 3.74 GB | Not provided — verify file size before flashing | Global export build for CPH1969EX. Community-converted scatter from the C.31 global OFP. Use this when restoring a unit that was originally a global variant. | Global export variant stock restore, region mismatch correction | Download C.31 Global Scatter (Google Drive mirror) |
Firmware Overview
OPPO’s branch lettering on this device follows the ColorOS upgrade path. The A-branch is the launch firmware — Android 9, ColorOS 6. Builds run from A.09 (June 2019) through at least A.18 (February 2020). The C-branch introduced Android 10 with ColorOS 7; the builds here range from C.15 to C.43, all dated September 2020. The F-branch brought Android 11 — builds span F.07 (October 2021) through F.11 (July 2022), with an earlier cluster of F.13–F.17 dated mid-to-late 2020, which are likely the initial Android 11 rollout builds before the 2021/2022 maintenance updates.
One anomaly worth noting: F.13’s build date (200826) is later than F.14’s (200719). The version number and build date don’t align chronologically in the expected way. This sometimes happens when OPPO re-signs a build for a specific carrier or regional channel. Treat F.13 as a parallel branch variant, not a strict predecessor to F.14.
Compatibility Warning
The PCAM10 and PCAT10 run MediaTek’s MT6771WT. With SP Flash Tool, the most dangerous mistake is selecting Format All + Download when Download Only is what you need. Format All wipes the entire device including the bootloader partition — on this chipset, if the scatter file has a single incorrect partition address, you end up with a dead board that SP Flash Tool can no longer see. Use Download Only unless you’re recovering from a partition table corruption where there’s nothing left to lose.
The community-converted SCATTER packages in this collection have not been validated by OPPO’s build system. Their partition offsets were generated by the conversion tool. Before loading any scatter file, confirm the scatter header lists MT6771 or MT6771WT as the platform identifier. If it doesn’t match, stop — do not flash.
Cross-flashing between PCAM10 and PCAT10 using a single-model file is possible at the hardware level but can leave the modem firmware in a mismatched state. The dual-model files (labeled PCAM10_PCAT10 in the filename) are specifically packaged to handle both safely.
All firmware files referenced on this page are the intellectual property of their respective manufacturers. Files are linked here solely for repair, recovery, and research purposes. This site does not host, modify, or claim ownership of any firmware files. Rights holders with concerns about a specific link may contact the site administration.
Before You Flash
OFP/RAR Payloads (OPPO Flash Tool)
- Install MediaTek VCOM drivers (MT65xx USB VCOM) before connecting the device
- Extract the RAR/ZIP with WinRAR or 7-Zip — do not flash from inside the archive
- OPPO Flash Tool (ColorOS Flash Tool / OfflineCom) must be installed and launched as Administrator
- Battery should be above 30% if the device powers on; if it’s dead, connect with the original cable and let it reach 5% before proceeding
- Disable Windows Defender real-time protection during the flash — it has a pattern of blocking the VCOM driver handshake mid-session
MTK Scatter Packages (SP Flash Tool)
- Use SP Flash Tool v5.1952 or the latest stable v5 release; avoid v3 for this chipset
- Install MT65xx VCOM USB drivers separately — SP Flash Tool does not bundle them
- Extract the scatter RAR fully before loading; the scatter file must be in the same directory as the partition image files
- Power the device off completely — do not connect while it’s on or in fastboot
- Set SP Flash Tool to Download Only unless you have a specific reason to format; see the Compatibility Warning above
- Extraction path must not contain spaces or non-ASCII characters — SP Flash Tool chokes on them silently
UFI Dump (ISP Tools Only)
- Requires UFI Box, Medusa Pro, or equivalent ISP tool with PCAM10 eMMC pinout support
- This is a chip-level write operation — the device must be disassembled and the eMMC contacted directly
- Only use this file if USB-based flashing has been ruled out entirely
Flash Instructions
These steps cover the SP Flash Tool scatter workflow, which applies to all SCATTER files in this collection. For OFP/RAR payloads, use OPPO’s ColorOS Flash Tool with the same driver setup.
- Install the MT65xx VCOM USB drivers on your Windows PC and verify they appear in Device Manager without error flags.
- Extract the chosen scatter package (e.g.,
PCAM10_PCAT10_11_F.17_200828_dc90228f_SCATTER.rar) to a folder with no spaces in the path — for example,C:\Flash\PCAM10_F17. - Open SP Flash Tool v5 as Administrator. Click Scatter-loading and navigate to the extracted folder. Select the scatter file (filename typically ends in
_scatter.txtorMT6771_Android_scatter.txt). - Confirm the platform header in SP Flash Tool shows MT6771 or MT6771WT. If it shows a different chipset, stop — you have the wrong scatter or wrong device.
- Set the flash mode to Download Only. Verify all required partitions are checked — at minimum: preloader, boot, system, vendor.
- Power off the OPPO A9 PCAM10/PCAT10 completely. Remove the USB cable.
- Click Download in SP Flash Tool, then connect the device via USB while holding the Volume Down button. The tool should detect the device and begin flashing within a few seconds.
- Wait for the green circle (download complete) indicator. Do not disconnect the cable or close the tool during the write process.
- Disconnect the USB cable. The device will reboot automatically. First boot after a full flash on this chipset typically takes 3 to 5 minutes — do not interrupt it.
- Once the device boots, go to Settings → About Phone and confirm the build version matches the firmware you flashed (e.g., F.17 should show in the build number string).
For a full visual walkthrough with screenshots, the SP Flash Tool guide for MediaTek devices covers the complete process.
FAQ
Can I flash the PCAM10 scatter file onto a PCAT10 and vice versa?
The files labeled PCAM10_PCAT10 in the filename are safe for both variants — they’re packaged to handle either. Single-model PCAM10 scatter files are a different story: the modem firmware partition in those packages is calibrated for the full-netcom band configuration, not China Mobile’s. You may end up with a flashed device that boots fine but loses LTE on certain bands. Use the dual-model builds when you’re not sure which variant you’re holding.
The device boots into recovery but SP Flash Tool won’t detect it. What’s wrong?
Recovery mode and download mode are different. SP Flash Tool needs the device fully powered off before connecting — it handles the mode switch itself when you plug in with Volume Down held. If SP Flash Tool still doesn’t see the device, check Device Manager for a yellow-flagged COM port entry, which means the MT65xx VCOM driver isn’t installed correctly. Reinstall the driver, reboot the PC, then try again. Some USB 3.0 ports cause handshake failures with VCOM on this chipset — try a USB 2.0 port directly on the motherboard.
What’s the difference between the OFP payloads and the SCATTER files? Which one should I use?
The OFP/RAR payloads are OPPO’s original firmware packages, flashed using OPPO’s ColorOS Flash Tool (OfflineCom tool). They’re the safest option for a device that powers on and can connect via USB. The SCATTER files are MediaTek partition images for SP Flash Tool — they let you push individual partitions directly, which is useful when the device can’t boot far enough for OPPO’s tool to see it. The SCATTER files in this collection are community conversions, not OEM-issued scatter packages, so use the OFP originals whenever possible.
The A.11 UFI dump — can I use it to restore a phone that’s stuck in a bootloop?
No. A bootlooping device still has working eMMC and a live USB interface. The UFI dump is for chip-level recovery when the eMMC is unresponsive or the partition table is completely destroyed. Using ISP write on a bootlooping phone overwrites the user data partition entirely and requires physical disassembly. If the device bootloops, start with the scatter or OFP files via SP Flash Tool or the OPPO Flash Tool first.
F.13’s build date is later than F.14’s. Is the version numbering wrong, or did I download the wrong file?
The files are correct. OPPO occasionally re-signs or issues revised builds that carry an earlier version string but a later build date — this happens when a build is re-packaged for a specific carrier channel or regional distribution after the next version has already shipped. F.13 and F.14 appear to be parallel channel builds rather than a strict sequential upgrade chain. For most repair purposes, either will restore a working F-branch system; F.17 is still the recommended target if you want the latest F-branch build in this collection.
After flashing the CN firmware, mobile data stopped working on a globally-sold unit. How do I fix it?
This is a region mismatch. The CN builds carry China-specific APN defaults and modem firmware tuning that doesn’t align with global carrier band plans. Flash the CPH1969EX global scatter (A9(PCAM10_CONVERTED_GLOBAL_CPH1969EX_11_C.31_SCATTER.rar) or the PCAM10_CONVERTED_GLOBAL_OS10_SCATTER.rar to restore the global regional package. After flashing, manually enter your carrier’s APN settings — they won’t auto-populate on first boot after a full region switch.
The hash values in the filenames — are those full MD5 checksums I can verify against?
They’re partial hash suffixes, not full checksums. A full MD5 is 32 hex characters; what’s embedded in these filenames (e.g., dc90228f) is 8 characters — likely the first 8 characters of the MD5 or a CRC32 value used for quick build identification in OPPO’s internal systems. They’re useful for confirming you have the right build version, but they can’t substitute for a full checksum verification. Files without any hash in the filename (the early A.11 ZIP, the F.07 and F.11 OFP builds, and the converted packages) have no embedded verification at all — match file size as your primary integrity check for those.