V2 Pro Firmware Download Repack — Sunmi

Many V2 Pro units sold via third-party resellers never receive OTA access. Users hit a wall when their terminal’s printer starts misaligning or the touchscreen drifts, and Sunmi support redirects them to the reseller—who has vanished. A repack becomes the only lifeline.

Step 1: Enable Developer Options on the V2 Pro (tap “Build Number” 7 times) and turn on USB Debugging.

Step 2: Power off the device completely. Then, hold the Volume Down button while connecting the USB cable to the PC. This boots the V2 Pro into Download Mode (a black screen with tiny white text).

Step 3: On your PC, launch ResearchDownload as Administrator. It should detect “Sunmi V2 Pro” in the COM port. sunmi v2 pro firmware download repack

Step 4: Load the firmware scatter file (usually named MT6739_Android_scatter.txt). The tool will list partitions: preloader, boot, system, etc.

Step 5: If using a repack, uncheck the “preloader” box. Why? A corrupted preloader (the very first boot code) from a repack will permanently brick the device. Leave the official preloader intact.

Step 6: Click “Download.” The process takes 3–5 minutes. Do not disconnect the cable. Many V2 Pro units sold via third-party resellers

Step 7: After success, the V2 Pro reboots. First boot after a repack can take up to 10 minutes (Android is rebuilding caches).

How to verify authenticity:


Repacking means modifying firmware contents and rebuilding flash package. Common reasons: add enterprise apps, preconfigure settings, remove bloat, or inject custom configuration. High-level repack steps (assume working with update

Tools commonly used:

High-level repack steps (assume working with update.zip or partition images):

  • Make desired modifications:
  • Repack system image:
  • If update.zip/payload.bin used, rebuild payload using payload_signer or tools that reconstruct the payload structure.
  • Recreate package signature if required by device bootloader/OTA verification. If device enforces signature checks, unsigned repacks may fail to flash.
  • Test on a spare/test device first. Never test on production hardware.
  • Permissions and SELinux:

    Signing: