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 the OPPO A9 China variants PCAM10 and PCAT10, both running on MediaTek Helio P70 (MT6771). Two fundamentally different firmware formats are present — OFP packages and scatter ROMs — and they require completely different tools. Using the wrong tool on either format accomplishes nothing at best, and hard-bricks the device at worst, so read the format breakdown before downloading anything.
The OFP packages (the large PCAM10_PCAT10_11_Fx.xx RAR files) are full official stock ROM images in OPPO’s encrypted container format. These go through Realme Flash Tool (also used for OPPO) and are the correct choice for returning a device to completely stock — after root, region changes, or a failed OTA that left the system partition incomplete. The scatter ROMs (files with _SCATTER in the name) are MediaTek partition images with a scatter file that maps each partition to an address. These load into SP Flash Tool and are the right choice when the device is deep-bricked past the bootloader — the phone won’t enumerate for Realme Flash Tool but SP Flash Tool can still reach it. The UFI dump is a raw eMMC read at chip level; it’s not a flashing package — it’s a last resort for ISP/direct-eMMC recovery when all software tools have failed. The converted global scatter packages are community-converted builds adapted from China firmware to run the global/F11 branch — useful for region switching or recovering a device that has already been converted.
Which repair scenarios does this address: bootloop, soft brick, failed OTA, stock restore after root, region mismatch between China and global branch, and chip-level eMMC recovery (UFI file only).
Included Models
- PCAM10 — OPPO A9 China (2019). MediaTek Helio P70 (MT6771V/MT6771WT), 4GB or 6GB or 8GB RAM depending on sub-SKU, 128GB internal. Ships with ColorOS 6 on Android 9. The dominant model in this collection — most files target PCAM10 directly or PCAM10+PCAT10 jointly.
- PCAT10 — OPPO A9 China alternate variant. Same MT6771 platform as PCAM10, regional and network band differences. Files labeled PCAM10_PCAT10 are explicitly documented as covering both variants. Do not flash PCAT10-only firmware to PCAM10 or vice versa without confirming the package explicitly names both.
- CPH1969 — OPPO A9 global/international variant referenced in one converted scatter file in this collection. Same Helio P70 hardware base, different software branch (global ColorOS). The converted scatter targeting CPH1969EX is included specifically for global branch restoration on devices that have been region-switched.
Model Sections
PCAM10 — OPPO A9 China
The MT6771WT variant of the Helio P70 in the PCAM10 is a China full-netcom build with CDMA bands — that matters for flashing because regional firmware includes the modem partition tuned for those bands. If the modem partition gets mismatched (e.g., flashing a global-branch OFP onto a unit that was on China firmware long-term), cellular registration issues can appear. The safest recovery path for a PCAM10 that is simply bootlooping or soft-bricked is one of the PCAM10_PCAT10 OFP packages in Realme Flash Tool — they’re official, they cover both hardware variants, and the flash is clean.
The known failure mode on this chipset combination is eMMC corruption after a partial OTA or power loss mid-flash. When the device shows a black screen and doesn’t enumerate on any tool — not SP Flash Tool, not Realme Flash Tool — that’s usually eMMC block-level damage, and the UFI dump file in this collection is the only path forward from there. That requires a chip-off or ISP pads and a UFI Box or equivalent hardware tool; it’s not a software fix.
PCAT10 — OPPO A9 China Alternate Variant
PCAT10 uses the same MT6771 core as PCAM10. The hardware differences between PCAT10 and PCAM10 are primarily regional network support and internal SKU designation rather than chipset revision. All joint PCAM10_PCAT10 OFP packages in this collection apply equally to both variants — the OFP container handles the branch internally. There is no separate PCAT10-exclusive OFP file in this collection.
CPH1969 — OPPO A9 Global (Converted Scatter Only)
CPH1969EX is the international/global retail designation for the OPPO A9, sharing the same Helio P70 silicon. Only one file in this collection explicitly targets CPH1969 — the converted global scatter package. This is a community conversion, not an official OPPO global ROM, and it’s here specifically to restore devices that were previously on the global branch and need a scatter-based reflash. Using this file on a device that was never on the global branch requires understanding what the region conversion actually changes: primarily the software branch identifier, OTA server endpoint, and pre-loaded apps. The modem and baseband partitions remain MT6771-based regardless.
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 (190729) | China | Android 9 | OFP ZIP | 5 GB | Not provided | Earliest build in collection. ZIP format rather than RAR — extract contents before loading into flash tool. Android 9 baseline; does not include Android 10 or 11 system. | Android 9 stock restore, early baseline recovery | Download A.11 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.17_200828_dc90228f.rar | F.17 (200828) | China | Android 11 | OFP RAR | 4.82 GB | dc90228f (embedded in filename) | Most recent OFP build in collection. F-branch = final stable release series. Best choice for clean stock restore on Android 11. | General stock restore, Android 11 recovery | Download F.17 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.15_200730_956c7d3a.rar | F.15 (200730) | China | Android 11 | OFP RAR | 4.75 GB | 956c7d3a (embedded in filename) | One minor revision behind F.17. Use if F.17 fails to complete flash on a specific unit. | General stock restore, Android 11 fallback | Download F.15 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.14_200719_4c11acd7.rar | F.14 (200719) | China | Android 11 | OFP RAR | 4.9 GB | 4c11acd7 (embedded in filename) | Mid-series F-branch build. Slightly larger than F.15 — no anomaly, normal build size variance. | General stock restore, Android 11 mid-series | Download F.14 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_F.13_200826_75a61388.rar | F.13 (200826) | China | Android 11 | OFP RAR | 5.13 GB | 75a61388 (embedded in filename) | Largest of the F-series OFPs in this collection. Build date 200826 is later than F.14 and F.15 — version numbering and build date do not progress linearly here; F.13 was a separate release track, not simply an older build. | General stock restore, Android 11 | Download F.13 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_C.43_200918_c87bc03e.rar | C.43 (200918) | China | Android 11 | OFP RAR | 6.66 GB | c87bc03e (embedded in filename) | Largest single package in the collection at 6.66 GB. C-branch builds are ColorOS China stable track. C.43 is a late-series release — notably heavier than F-branch builds, likely includes additional system assets. | General stock restore, ColorOS China C-branch | Download C.43 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_C.31_200918_4564331f.rar | C.31 (200918) | China | Android 11 | OFP RAR | 4.32 GB | 4564331f (embedded in filename) | Same build date as C.43 but considerably smaller. C.31 is an earlier C-branch revision — both were staged on the same date internally. | General stock restore, ColorOS China C-branch | Download C.31 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_C.15_200918_d2cbdcfc.rar | C.15 (200918) | China | Android 11 | OFP RAR | 5.36 GB | d2cbdcfc (embedded in filename) | Early C-branch build, same staging date as C.31 and C.43. Use when a specific C-branch baseline is needed for compatibility testing. | C-branch baseline restore | Download C.15 (Google Drive mirror) |
| PCAM10 / PCAT10 | PCAM10_PCAT10_11_A.09_190626_1cca1a33.rar | A.09 (190626) | China | Android 9 | OFP RAR | 4.46 GB | 1cca1a33 (embedded in filename) | Android 9 build, pre-A.11. Earliest OFP RAR in the collection. For cases where the device needs to be walked back to a pre-A.11 state before re-upgrading. | Android 9 early baseline restore | Download A.09 (Google Drive mirror) |
| PCAM10 | PCAM10_11_F.11_2022072319323225.rar | F.11 (20220723) | China | Android 11 | OFP RAR | 3.34 GB | Not provided | PCAM10-only (no PCAT10 in filename). Build date 2022 — later release than most F-series files. No embedded hash in filename. Verify file size against 3.34 GB before flashing. | General stock restore, Android 11 | Download F.11 (Google Drive mirror) |
| PCAM10 | PCAM10_11_F.07_2021101921225089.rar | F.07 (20211019) | China | Android 11 | OFP RAR | 3.43 GB | Not provided | PCAM10-only. 2021 build — matches the F.07 scatter variant in this collection. No embedded hash; verify file size before flashing. | General stock restore, Android 11 | Download F.07 OFP (Google Drive mirror) |
| PCAM10 | PCAM10_11_A.11_190729_1cca1a33.rar | A.11 (190729) | China | Android 9 | OFP RAR | 4.42 GB | 1cca1a33 (embedded in filename) | RAR-format counterpart to the ZIP version of the same build at the top of the collection. Same version string and hash — choose this over the ZIP for faster extraction on most tools. | Android 9 stock restore | Download A.11 RAR (Google Drive mirror) |
| PCAM10 → F11 (Converted) | PCAM10_CONVERTED_TO_F11_C.17_OS10_SCATTER.rar | C.17 OS10 | Converted (F11 branch) | Android 10 | MTK Scatter | 2.1 GB | Not provided | Community conversion of PCAM10 firmware to F11 (OPPO F11) branch on Android 10. Not an official OPPO package. Use only on devices already on or intended for F11 software branch. Verify device identity carefully before flashing. | F11 branch conversion restore, SP Flash Tool recovery | Download F11 Converted Scatter (Google Drive mirror) |
| PCAM10 (Converted Global) | PCAM10_CONVERTED_GLOBAL_OS10_SCATTER.rar | OS10 (Global) | Converted Global | Android 10 | MTK Scatter | 2.09 GB | Not provided | Community conversion to global branch on Android 10. Intended for PCAM10 units being region-switched to global ColorOS. Not from OPPO’s official global ROM servers. | Global branch conversion, region restore | Download Global Converted Scatter (Google Drive mirror) |
| PCAM10 | PCAM10_11_F.07_2021101921225089_SCATTER.rar | F.07 (20211019) | China | Android 11 | MTK Scatter | 3.2 GB | Not provided | Scatter-format version of the F.07 OFP build. Use this — not the OFP — when the device is deep-bricked past bootloader enumeration. | Deep brick recovery via SP Flash Tool | Download F.07 Scatter (Google Drive mirror) |
| PCAM10 | PCAM10_11_A.18_200220_10d3a3db_SCATTER.rar | A.18 (200220) | China | Android 9 / 10 | MTK Scatter | 4.54 GB | 10d3a3db (embedded in filename) | A-branch scatter build from February 2020. Android version isn’t definitively confirmed from filename alone — check About Phone after flashing to confirm. A.18 is a late A-branch release, likely on the Android 9→10 transition. | A-branch scatter recovery | Download A.18 Scatter (Google Drive mirror) |
| PCAM10 | PCAM10_11_A.11_FILE_DUMP_FULL_USERPART_OS9_UFI.rar | A.11 OS9 | China | Android 9 | eMMC Full Dump (UFI) | 1.85 GB | Not provided | Raw eMMC USER partition dump captured with UFI Box. This is not a flashable ROM package — it requires ISP or chip-off eMMC write hardware. Only relevant for dead-boot recovery where all software tools fail to detect the device. | ISP/chip-level eMMC recovery (hardware tool required) | Download UFI Dump (Google Drive mirror) |
| PCAM10 | PCAM10_11_A.11_190729_1cca1a33_SCATTER.rar | A.11 (190729) | China | Android 9 | MTK Scatter | 4.3 GB | 1cca1a33 (embedded in filename) | Scatter counterpart to the A.11 OFP files. Same build, same hash — this version is for SP Flash Tool recovery when the OFP flash path isn’t accessible. | Android 9 deep recovery via SP Flash Tool | Download A.11 Scatter (Google Drive mirror) |
| CPH1969 (Converted Global) | A9(PCAM10_CONVERTED_GLOBAL_CPH1969EX_11_C.31_SCATTER.rar | C.31 (Global) | Converted Global | Android 11 | MTK Scatter | 3.74 GB | Not provided | Community conversion targeting CPH1969EX (global retail variant) on Android 11 C.31. Note the filename has an unclosed parenthesis — this is how the file was packaged; the name is not truncated. Not an official OPPO ROM. | Global branch restore, CPH1969 region recovery | Download CPH1969EX Converted Scatter (Google Drive mirror) |
Compatibility Warning
The Helio P70 (MT6771) in the PCAM10 and PCAT10 carries a specific SP Flash Tool risk that bricks more phones than almost any other mistake in the field: selecting Format All + Download when Download Only is what the situation needs. Format All wipes the preloader and partition table before writing — if the flash fails partway through for any reason (cable drop, driver issue, insufficient power), the phone is completely unrecoverable by software. Unless the device is truly dead-boot and even the preloader won’t enumerate, always start with Download Only on these scatter packages.
For the OFP packages flashed via Realme Flash Tool: the tool handles the partition layout internally, but ensure the correct model is detected before initiating. Flashing a PCAT10-exclusive OFP to a PCAM10 unit (or vice versa) using joint PCAM10_PCAT10 packages is fine — those are explicitly multi-model. Do not attempt to flash the converted global scatter packages to a device that has never been on the global branch without understanding that the branch identifier in software will change permanently.
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.
Flash Instructions
OFP Packages — Realme Flash Tool:
- Download and install the Realme Flash Tool on a Windows PC. Install the MediaTek USB VCOM driver — the phone will not enumerate without it.
- Extract the downloaded RAR or ZIP archive to a local folder with a short path (e.g.,
C:\PCAM10_F17). Avoid long or special-character paths — the tool chokes on them. - Open Realme Flash Tool. In the main window, click the folder icon and browse to the extracted OFP file (e.g.,
PCAM10_PCAT10_11_F.17_200828_dc90228f.ofp). - Power off the OPPO A9 completely. Do not use fast boot or restart — hold the power button until the screen goes black.
- Connect the device to the PC via USB with the phone powered off. The tool should detect the device and show the model identifier.
- Confirm the detected model matches PCAM10 or PCAT10 before proceeding. If it shows an unexpected identifier, disconnect and verify the correct OFP was loaded.
- Click Flash / Start in the tool. The process takes 10–20 minutes depending on package size — do not disconnect or allow the PC to sleep.
- When complete, the tool will show a success status. The device will reboot automatically. First boot after a clean flash takes 3–5 minutes — do not interrupt it.
- After boot, go to Settings → About Phone and confirm the software version matches the build that was flashed (e.g., F.17).
Scatter Packages — SP Flash Tool (MediaTek MT6771):
- Download SP Flash Tool (v5.1916 or later recommended for MT6771) and install the MTK VCOM/preloader USB driver on the PC.
- Extract the scatter RAR to a short local path. Confirm the extracted folder contains a scatter file (typically named
MT6771_Android_scatter.txt) and the partition image files. - Open SP Flash Tool. Click Choose next to the scatter file field and select the
MT6771_Android_scatter.txtfrom the extracted folder. - Set the download mode to Download Only — not Format All. Use Format All only if the device is completely dead-boot and Download Only fails to complete.
- Verify the partition list loaded correctly. All required partitions (boot, system, vendor, etc.) should be checked. Preloader should be checked last if at all — leave it unchecked unless you have a specific reason to reflash it.
- Power off the OPPO A9. Connect it to the PC via USB with the phone powered off and hold Volume Down while inserting the cable to enter download mode.
- SP Flash Tool will detect the device and begin writing. Progress bars will advance per partition — the full process takes 8–15 minutes depending on the scatter package size.
- On completion, disconnect the device, remove and reinsert the battery if accessible, then power on. After boot, confirm the version in Settings → About Phone.
For a full visual walkthrough with screenshots, the SP Flash Tool guide for MediaTek devices covers the complete process.
FAQ
What is the difference between the OFP files and the scatter files for the same build?
The OFP is OPPO’s encrypted container format — it goes into Realme Flash Tool and the tool handles unpacking and writing internally. The scatter file is an extracted/raw MTK partition image set that SP Flash Tool reads directly. Both result in the same flashed firmware. The OFP path requires the bootloader to respond; the scatter path can work on a device that won’t enumerate in bootloader mode at all, which is why scatter files exist for deep-brick recovery on the same builds.
Can the PCAM10 and PCAT10 use the same firmware files?
Files explicitly labeled PCAM10_PCAT10 in the filename are documented as covering both variants and are safe for either. Files labeled PCAM10-only (such as the F.11 and F.07 OFP builds) should only be used on PCAM10 units. Do not assume a PCAM10-only file covers PCAT10 just because the hardware is similar — the partition structures can differ between SKUs.
The filename has a hash at the end (like dc90228f) — is that the file’s checksum?
Yes, for the files where it appears, the hex string embedded in the filename is a checksum (typically MD5 or partial SHA) embedded by OPPO as a package integrity identifier. You can run an MD5 check on the extracted OFP file against that value. For files without a hash in the filename (F.11, F.07 OFP, and the converted scatter packages), no checksum is provided — verify file size against the listed value before flashing.
What does the UFI dump file actually do and when should it be used?
The UFI dump is a raw binary read of the eMMC USER partition taken directly from a working PCAM10 chip with a UFI Box. It can only be written back to another eMMC chip using ISP pads (testpoints on the board) or chip-off. It is not loadable into SP Flash Tool or Realme Flash Tool — it requires hardware like UFI Box, Easy JTAG, or a direct eMMC programmer. Use it only when the device shows no sign of life on any software tool and direct chip access is available.
Is it safe to flash from Android 9 firmware back down from Android 11?
On the MT6771 platform with OPPO firmware, downgrading from Android 11 to Android 9 via OFP is generally possible because OPPO did not implement aggressive anti-rollback (ARB) enforcement on this device generation. That said, the userdata partition will be wiped, and any Android 11 apps or system data will not survive. Use the Android 9 OFP (A.11 or A.09 builds) in Realme Flash Tool, and do not attempt to skip major Android versions in the middle of the process.
Why are there multiple C-branch OFP files (C.15, C.31, C.43) with the same build date?
These were staged internally by OPPO on the same calendar date (200918) as part of a batch archive rather than as simultaneous public releases. The version numbers reflect different release tracks or regional staging milestones within the C-branch, not parallel OTA updates pushed to users at the same time. If restoring a device that was on the C-branch, C.43 is the most complete build; C.15 and C.31 are available here for cases where an earlier C-branch baseline is specifically needed.
The converted global scatter file has an unclosed parenthesis in the filename — is the file corrupted?
No. The filename A9(PCAM10_CONVERTED_GLOBAL_CPH1969EX_11_C.31_SCATTER.rar is exactly how the file was packaged and distributed. The parenthesis issue is in the naming convention used by whoever created the conversion, not a sign of archive corruption. Check the extracted archive integrity (most RAR tools will report CRC errors if the archive is actually damaged) before flashing.