[SUCCESS REPORT] Xiaomi Redmi A3 Global (blue) – MT6765 / HW Code 0x766 – Stock Preloader and DA Working on Windows 11

Start by reviewing the issue’s successful gettargetconfig and printgpt commands and their output for the Redmi A3 Global on Windows 11. The report documents successful DA initialization and GPT reading, but omits the final reset operation and asks maintainers for interpretation; done would require a maintainer response or a reproducible diagnostic procedure.

[SUCCESS REPORT] Xiaomi Redmi A3 Global (blue) – MT6765 / HW Code 0x766 – Stock Preloader and DA Working on Windows 11

Summary

Successfully established full MTKClient communication with a Xiaomi Redmi A3 Global (blue) using the original preloader and Download Agent extracted from the official Android 15 Fastboot ROM.

The device initially failed during the early USB/watchdog communication stage. After several unsuccessful attempts, we managed to initialize the device, load both DA stages, complete SLA authentication, and read the entire GPT partition table.

The device was subsequently factory-reset successfully and became accessible again.

Important: This report documents the verified connection and GPT-reading procedure. The exact final partition-erasure operation was not captured in the logs and therefore cannot be independently reproduced from this report.

1. Device information

Property | Value -- | -- Manufacturer | Xiaomi Model | Redmi A3 Global Codename | blue Chipset | MediaTek MT6765 / MT8768t Hardware code | 0x766 HW subcode | 0x8A00 HW version | 0xCA00 Bootloader | Locked USB debugging | Disabled Host OS | Windows 11 MTKClient | 2.1.4 Python environment | Virtual environment Firmware used for DA/preloader | V816.0.7.0.VGRMIXM (Android 15) Result | Successful DA initialization, GPT access and device recovery

The files were extracted from the images/ directory.

Only the preloader and Download Agent were explicitly supplied to MTKClient in the successful GPT-reading command. The authentication file was extracted but was not passed using --auth.

5. Successful target configuration query

The following command succeeded:

cd C:\RedmiA3\mtkclient
..venv\Scripts\python.exe .\mtk.py gettargetconfig --preloader "C:\RedmiA3\Firmware\blue_global_images_V816.0.7.0.VGRMIXM_15.0\images\preloader_blue.bin"

--skipwdt

Output excerpt:

Port - Device detected :)

Preloader - Detected regular mode !

Preloader - CPU: MT6765/MT8768t(Helio P35/G35)

Preloader - HW code: 0x766

Preloader - Target config: 0x7

Preloader - SBC enabled: True

Preloader - SLA enabled: True

Preloader - DAA enabled: True

Preloader - SWJTAG enabled: True
Preloader - Root cert required: False

Preloader - Mem read auth: False

Preloader - Mem write auth: False

This was the first successful connection that progressed beyond the earlier initialization failures.

6. Successful Download Agent initialization and GPT access

The following command successfully initialized the Download Agent and read the GPT partition table:

..venv\Scripts\python.exe .\mtk.py printgpt --preloader "C:\RedmiA3\Firmware\blue_global_images_V816.0.7.0.VGRMIXM_15.0\images\preloader_blue.bin"

--loader "C:\RedmiA3\Firmware\blue_global_images_V816.0.7.0.VGRMIXM_15.0\images\MTK_AllInOne_DA.bin" `

--skipwdt

Successful output:

Port - Device detected :)

Preloader - Detected regular mode !

Preloader - HW code: 0x766

DaHandler - Device is protected.

DaHandler - Device is in Preloader-Mode.
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA.bin

DAXFlash - Successfully uploaded stage 1, jumping ..

Preloader - Jumping to 0x200000: ok.

DAXFlash - Successfully received DA sync

DAXFlash - Uploading stage 2...
Exploitation - V5 Device is patched against carbonara :(
DAXFlash - Upload data was accepted. Jumping to stage 2...

DAXFlash - Boot to succeeded.

DAXFlash - Successfully uploaded stage 2
DAXFlash - DA SLA is enabled

No valid sla key found, trying dummy auth ....

SLA Signature was accepted.
Main - Handling da commands ...
GPT Table:

-------------

Despite the message indicating that the device was patched against the carbonara exploit, the Download Agent initialized successfully.

The successful SLA response is particularly interesting:

No valid sla key found, trying dummy auth ....

SLA Signature was accepted.

This is an observed result for this particular device and firmware combination, not evidence that other protected MediaTek devices will behave the same way.

7. Partition table successfully read

MTKClient successfully listed the device's partitions, including:

misc

countrycode

boot_para

para

expdb

frp

nvcfg

nvdata

metadata

protect1

protect2

seccfg

persist

sec1

proinfo

efuse

nvram

boot_a

boot_b

vendor_boot_a

vendor_boot_b

super

cust

rescue

userdata

otp

flashinfo

The device reported an eMMC USER capacity of:

0x1d25d80000 bytes

The full GPT was successfully retrieved, confirming functional communication with the device's storage through the Download Agent.

8. Factory-reset result

Following the successful connection and GPT inspection, the device was restored to an accessible state using MTKClient.

The owner confirmed that the Redmi A3 was successfully reset.

However, the precise final erase command or GUI operation was not captured in the provided logs.

For that reason, this report does not claim that a particular partition-erasure sequence is verified or recommended.

Device-specific partitions such as nvram, nvdata, persist, proinfo, and frp should not be erased indiscriminately.

9. Android version observation

An interesting detail: after the recovery, the owner reported that the device was already running Android 16.

The Android 15 firmware was used to obtain the original preloader and Download Agent. No full Android 15 firmware flash was performed as part of the documented procedure.

The exact installed Android 16 build number has not yet been independently verified.

10. Key findings

1. MTKClient 2.1.4 successfully communicated with the Xiaomi Redmi A3 Global (blue) on Windows 11.

2. The device used MediaTek hardware code 0x766.

3. Initial communication repeatedly failed during early USB/watchdog handling.

4. The successful configuration used --skipwdt and the original preloader_blue.bin.

5. Supplying MTK_AllInOne_DA.bin from the device firmware allowed successful DA initialization.

6. Both DA stages were uploaded successfully.

7. SLA authentication was accepted despite the absence of a separately supplied authentication file.

8. The complete GPT partition table was readable.

9. The bootloader remained locked during the documented procedure.

10. The device was subsequently reported as successfully factory-reset and accessible.

11. Questions for the maintainers

We would appreciate feedback on the following:

• Is the successful SLA acceptance using dummy authentication expected for this MT6765 / HW code 0x766 configuration?

• Could the original device-specific preloader and --skipwdt combination explain why the earlier watchdog failures disappeared?

• Is there any additional diagnostic information that would help improve MTKClient support for the Redmi A3 Global?

• Would a sanitized debug log be useful for further investigation?

Acknowledgements

Many thanks to B. Kerler and all MTKClient contributors, as well as the community members who documented their experiences in GitHub issues.

The open-source tooling and shared troubleshooting knowledge were instrumental in restoring access to this device.

This report was compiled and structured with assistance from ChatGPT, based on actual MTKClient command outputs and the device owner's observations. No unsuccessful operation has been presented as a verified success.

---

Status: SUCCESS – DA initialized, GPT read successfully, device recovered.

Device: Xiaomi Redmi A3 Global (blue)
Chipset: MT6765
HW code: 0x766
MTKClient: 2.1.4
Platform: Windows 11
Report date: 2026-11-09