Q1. The ZIP says MT6765—should a Helio P35 scatter be used?

No. XT2025‑1 uses Helio P22 (MT6762); load the MT6762/“pokerp” scatter from the extracted package even if the filename mentions MT6765. Flashing with a wrong platform can hard brick the phone.

Q2. SP Flash Tool stops due to authentication—what now?

Motorola’s MediaTek devices typically enforce SLA/DA authentication. Use an auth bypass method for SP Flash Tool as described in the secure MTK guide; ensure stable USB and a fully charged battery.

Q3. Bootloader unlock commands fail on my E6 Plus—normal?

Many XT2025 units are not eligible for Motorola’s official bootloader unlock, so commands like fastboot oem get_unlock_data can fail. If you only need to restore stock, use firmware flashing or Lenovo RSA/LMSA recovery instead.

Q4. Which package should be used: FLASH_Sign or Forceflash?

Start with the standard FLASH_Sign package. Use the Forceflash variant only if the normal signed process is blocked for your exact same build/region/sku to avoid compatibility issues.

Motorola Moto E6 Plus XT2025‑1 RETLA/LA2 Stock ROM (Android 9 Pie)

The Motorola Moto E6 Plus XT2025‑1 (codename pokerp) shipped with Android 9 Pie and a MediaTek Helio P22 chipset (MT6762), plus a 6.1‑inch 720×1560 display, rear fingerprint reader, and a removable 3000 mAh battery. The “MT6765” label in several shared packages is a naming error; the actual SoC for XT2025‑1 is MT6762 Helio P22.

CRUCIAL WARNING

Chipset correction: Flash as MT6762 (Helio P22) even if the ZIP name says MT6765. Selecting a wrong DA/scatter for MT6765 can brick the device.
Auth required: Motorola MediaTek devices typically require Download Agent/Auth; use an MTK auth bypass workflow with SP Flash Tool where needed.
Do not cross‑flash 32B ↔ 64B: The XT2025‑1 exists in 32 GB and 64 GB SKUs; match your storage variant and region (RETLA/LA2) to avoid modem/band and partition mismatches.
Bootloader unlocking: Many E6 Plus units are not eligible for Motorola’s unlock program; prefer stock flashing or Lenovo Rescue & Smart Assistant (RSA/LMSA) recovery where appropriate.

Prerequisites

Click for the pre‑flash checklist

Backup user data: Internal storage is erased during a full firmware flash.
Battery at 50%+: Prevents interruptions mid‑flash.
Windows PC + micro‑USB data cable: Use a reliable cable/port.
Drivers & tools ready: MediaTek VCOM drivers, SP Flash Tool, and optional MTK auth bypass utility.

Firmware details

Device name: Motorola Moto E6 Plus
Model: XT2025‑1 (RETLA/LA2 variants)
Codename: pokerp
Chipset: MediaTek Helio P22 (MT6762), octa‑core 2.0 GHz, PowerVR GE8320 GPU
Android version: Android 9.0 Pie
Storage SKUs: 32 GB and 64 GB variants (32B/64B in filenames)
Display: 6.1‑inch 720×1560 IPS
Battery: 3000 mAh, removable
LTE bands (LATAM): Common LATAM bands include 1/2/3/4/5/7/8/28 per XT2025‑1 listings; confirm your carrier support
Notes: Build family “PTAS29.401‑36‑3” is a known XT2025‑1 Pie retail line for pokerp

Required tools & downloads

File / Tool	Download
SP Flash Tool (Windows)	Official site
MediaTek USB VCOM Drivers	Download
MTK Auth Bypass guide	Follow this tutorial
Alternative recovery (RSA/LMSA)	Lenovo Rescue & Smart Assistant (RSA)

Stock ROM / firmware (XT2025‑1)

All four packages below target Moto E6 Plus XT2025‑1; chipset text “MT6765” in names is corrected to MT6762 during flashing. Match region and storage (32B/64B) carefully.

Filename	Android / Build	Variant	Region	Notes	Size	Download
Motorola_Moto_E6_Plus_XT2025-1_MT6765_RETLA_P160AN_PVT_9.0_LA_32B_CFC_62.00-00.zip	Android 9 Pie; “62.00-00”	Likely 32 GB (32B)	RETLA	Name shows MT6765 but device is MT6762 Helio P22.	1.37 GB	Google Drive
Motorola_Moto_E6_Plus_XT2025-1_MT6765_P160AN_PVT_9.0_LA2_64B_CFC_133.01-01.zip	Android 9 Pie; “133.01-01”	Likely 64 GB (64B)	LA2	Use on 64 GB SKU only to avoid partition mismatch.	1.7 GB	Google Drive
Motorola_Moto_E6_Plus_XT2025-1_MT6765_DS_PTAS29.401-36-3_P160AN_PVT_9.0_LA2_32B_CFC_199.01-01_FLASH_Sign.zip	Android 9 Pie; PTAS29.401‑36‑3 / “199.01-01”	Dual SIM; 32 GB	LA2	Matches known pokerp retail Pie line. Recommended standard signed flash.	1.5 GB	Google Drive
Motorola_Moto_E6_Plus_XT2025-1_MT6765_DS_PTAS29.401-36-3_P160AN_PVT_9.0_LA2_32B_CFC_199.01-01_FLASH_Sign_Forceflash.zip	Android 9 Pie; PTAS29.401‑36‑3 / “199.01-01”	Dual SIM; 32 GB	LA2	“Forceflash” variant is typically used when normal signed flashing is blocked; prefer standard “FLASH_Sign” first.	1.5 GB	Google Drive

Quick flashing guide

Install MediaTek VCOM drivers, then extract SP Flash Tool and your chosen firmware ZIP (e.g., Motorola_Moto_E6_Plus_XT2025-1_MT6765_DS_PTAS29.401-36-3_P160AN_PVT_9.0_LA2_32B_CFC_199.01-01_FLASH_Sign.zip).
Open flash_tool.exe > “Scatter‑loading” and select the MTK scatter from the firmware folder (it corresponds to MT6762 for this device).
If SP Flash Tool requests authentication, follow the MTK Auth Bypass guide to proceed.
Choose Download Only, power off the phone, click “Download,” then connect the phone via USB to start flashing.
Wait for the success checkmark, disconnect, and boot the device. For step‑by‑step visuals, see the full SP Flash Tool tutorial below.

Detailed tutorials: How to Flash MediaTek Firmware with SP Flash Tool | MTK Auth Bypass (Secure MTK)

FAQs & troubleshooting

Q1. The ZIP says MT6765—should a Helio P35 scatter be used?: No. XT2025‑1 uses Helio P22 (MT6762); load the MT6762/“pokerp” scatter from the extracted package even if the filename mentions MT6765. Flashing with a wrong platform can hard brick the phone.
Q2. SP Flash Tool stops due to authentication—what now?: Motorola’s MediaTek devices typically enforce SLA/DA authentication. Use an auth bypass method for SP Flash Tool as described in the secure MTK guide; ensure stable USB and a fully charged battery.
Q3. Bootloader unlock commands fail on my E6 Plus—normal?: Many XT2025 units are not eligible for Motorola’s official bootloader unlock, so commands like fastboot oem get_unlock_data can fail. If you only need to restore stock, use firmware flashing or Lenovo RSA/LMSA recovery instead.
Q4. Which package should be used: FLASH_Sign or Forceflash?: Start with the standard FLASH_Sign package. Use the Forceflash variant only if the normal signed process is blocked for your exact same build/region/sku to avoid compatibility issues.