DelphiMTKClient is a professional Delphi source code project for developers, software owners,
research teams and companies that want to build their own MediaTek / MTK software on Windows.
This is not positioned as a simple compiled tool for regular users. The main value of the project
is the source code, protocol implementation, architecture and development base it provides.

If you are building a private MTK service product, an internal research tool, a custom flashing solution,
a device maintenance system or a commercial mobile software platform, DelphiMTKClient gives you a ready
Delphi foundation instead of starting MTK protocol development from zero.

The project includes support for the main MTK protocol families used in modern MediaTek workflows:
LEGACY, XFLASH and XML. It also includes many practical
modules around device initialization, DA communication, firmware flashing, partition operations,
file-system access, NV/IMEI handling, RPMB and advanced security-related paths.

Product Overview

Product: DelphiMTKClient (Delphi12) Source code
Technology: Delphi / Windows Desktop Development
Target chipset family: MediaTek / MTK
Protocol families: LEGACY, XFLASH, XML
Target audience: developers, software owners, R&D teams and companies
Delivery type: source code project
Category: Solutions and Source Code

document:

Who Is DelphiMTKClient For?

DelphiMTKClient is designed for technical users who understand source code, protocol integration
and product development. It is useful for people who need to study, extend, customize or integrate
MTK logic into their own software.

Delphi developers who need MTK protocol source code
Software owners building their own MediaTek service product
Research teams working on MTK protocol behavior
Companies that need a customizable MTK Windows codebase
Developers migrating ideas from another language to Delphi
Teams that need private branding, private workflows or model-specific logic

This project is not intended for regular end users who only want to click a button and repair a phone.
It is intended for developers who want the source code and need control over how the MTK workflow is built.

Why Source Code Matters

MTK software development is not only about having a user interface. A serious MTK client needs correct
handling of device detection, handshake, DA loading, storage information, partition layout, flash protocol,
XML command flow, error handling, security states and model-specific behavior.

With DelphiMTKClient, developers get a source code base that can be studied, changed and extended.
You can add your own device profiles, change UI behavior, integrate private DA selection logic,
add custom patch workflows, change logging, connect it to licensing systems or build a branded product
on top of the existing architecture.

Core Protocol Support

LEGACY protocol: classic MediaTek DA-based workflow for supported devices.
XFLASH protocol: modern DA flow with faster partition operations and DA extension paths where available.
XML protocol: MTK V6 / XML command workflow for supported devices and firmware packages.

Protocol availability depends on chipset, boot mode, selected DA, security configuration and target operation.
The source code is structured so developers can inspect and extend these paths for their own requirements.

Main Development Modules

Device Connection and Initialization

BROM and Preloader communication flow
USB / serial communication handling
Handshake and device information reading
Hardware code, software version and security flag parsing
MEID / SOCID reading where available
DA selection and DA upload workflow
Storage information detection for supported EMMC, UFS, NAND and NOR devices

Download Agent and Stage Flow

DA parser and loader metadata usage
Stage-1 / Stage-2 DA upload logic
EMI sending flow
DA extension loading where supported
Carbonara stage authentication path where supported
SLA / DAA related handling where supported
Error handling around DA boot and device state changes

Firmware and Flash Operations

Scatter-based firmware workflow
XML firmware workflow for supported MTK V6 devices
Native flash logic for XFLASH and XML paths
Flash by partition name
Raw partition write support
Preloader read and write operations
Download-only and firmware-upgrade style flows depending on protocol support

Partition and Storage Management

GPT / partition table reading
Partition dump logic
Read, write and erase selected partitions
Full flash read path where supported
GPT write / rebuild-related paths where supported
Partition lookup by name and sector information

File System and Android Information

EXT4 stream read/write paths
Logical partition / super partition handling logic
EROFS and F2FS detection / read paths where implemented
Build.prop and Android information extraction where supported
File management code for supported readable partitions

NV partition backup / write / erase paths
NV item decode logic
LD0B / nvdata related IMEI logic where supported
IMEI repair workflows for selected modes and brands
Hardware key read paths where supported
DXCC / crypto-related integration points where available in protocol flow

RPMB Development Paths

RPMB read logic
RPMB write logic
RPMB erase logic
RPMB key read path where supported
Protocol-specific RPMB integration for supported modes

Security, Patch and Research-Oriented Features

Kamakiri-style payload flow where supported
HeapBait protocol path where supported
Carbonara exploit path where supported
Bootloader unlock / relock logic
Permanent unlock logic for supported targets
FRP and format-related code paths
Vbmeta / dm-verity patch paths where supported
Brand or model-specific patch workflows where implemented

What Developers Can Build With It

Because DelphiMTKClient is delivered as source code, it can be used as a foundation for different types
of products and internal tools.

A branded MTK service software product
A private firmware flashing tool
A research tool for MTK protocol analysis
A device maintenance system for internal company use
A model-specific repair or patch platform
A Windows Delphi application with custom UI and licensing
A learning base for developers studying MediaTek protocol flow

Technical Highlights

Delphi codebase for Windows development
Protocol-oriented architecture for MTK workflows
Separate logic for LEGACY, XFLASH and XML paths
DA parser and stage upload handling
Native partition and flash command paths
MountCore-style file-system access modules
Advanced paths for selected exploit / auth workflows
Practical UI code that can be rebranded or redesigned
Suitable base for commercial customization

Example Development Log Area

Hold boot key And Connect To PC (power off mode)
Waiting for mediatek port (Timeout 3 minute) : Ok
brom service detected
Handshake device : Ok
Reading device Info : Ok Ok
Mediatek XFlash Detected!
CPU Info : MT6768/MT6769 Helio G70/G80/G85
disabling WatchDog Timer WDT disabled Ok
Hardware Sub Code : 0x8A00
Hardware Code : 0x707
Hardware Version : 0xCA00
Software Version : 0x00
Is Secure boot : True
Serial Link authorization Protect : True
download agent authorization Protect : True
SWJTAG enabled: True
EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Root cert required: False
Mem read auth: True
Mem write auth: True
Cmd 0xC8 blocked: True
ME_ID: 0x1B1A97BD943F10FE97AC3D8E0F69B843
SOCID: 0xD597C6EF5EA660011AF11AED38CE555DE1461C227FF618C5C195E8432FF48DF7
Disabling Watchdog timer : Ok
Sending payload : Ok
Trying disable SLA\DAA Kamakiri : Ok
Manual Preloader selected !
Choosing the right da : Ok
Writing download agent : Ok
Jumping Download Agent : Ok
Sync signal : Ok
Setup environment : Ok
Setup param : Ok
Connection Status : brom mode
Sending emi : Ok
uploading stage 2: Ok
Bypassing DA SLA: 
. rnid : 40DDDD360A86399B4A3546D87AD1AAD4
. DA SLA Authentication : Ok Ok
Adding DA Extensions: Ok
▶ Finding target to read info > target=super sector=4767744 (14680064 sectors)
• product : 922.58 MB [EXT4]
• system : 2.43 GB [EXT4]
• vendor : 683.98 MB [EXT4]
▶ Android OS Info
• OEM : Xiaomi
• Model : M2003J15SC
• Name : merlin_in
• Product : merlin
• Market Name : Redmi Note 9
• SDK Ver : 29
• Code Name : REL
• Incremental : V11.0.3.0.QJOINXM
• Build ID : QP1A.190711.020
• Android Ver : 10
• MIUI Ver : 9
• Security Ver : 2020-06-01
• Region : in
• Timezone : Asia/Shanghai
• CPU ABI : arm64-v8a
• SW Ver : Android10_11
• Build Date : Fri Jul 3 20:23:54 CST 2020
• Fingerprint : merlin-user 10 QP1A.190711.020 V11.0.3.0.QJOINXM release-keys
▶ IMEI
• IMEI1 : 867406040929029
• IMEI2 : 867406041929028

Screenshots and Videos

Use the placeholders below for screenshots and videos. Since this is a source code product,
it is better to include both UI screenshots and code/module screenshots.

Videos

Video 1 – Source code overview:

VideoOpen on YouTube

Video 2 – Protocol flow demonstration:

VideoOpen on YouTube

Screenshots

Project structure / source modules:

Main application interface:

Protocol code section:

Flash / partition module:

NV / IMEI module:

Patch / advanced module:

Important Notes for Buyers

This is source code for developers, not a one-click consumer tool.
MTK operations depend on chipset, DA support, boot mode and security state.
Some workflows are model-specific and may require developer-side customization.
Buyers should have Delphi development knowledge or a developer who can maintain the project.
For commercial use, you can customize branding, UI, licensing and workflow logic.

Why Choose DelphiMTKClient Source Code?

Developing MTK protocol software from zero takes time. Developers need to handle low-level communication,
device states, DA workflow, flash commands, partition data, storage differences and many protocol-specific
edge cases. DelphiMTKClient reduces this starting cost by providing a ready Delphi codebase focused on
MediaTek development.

For developers and companies, the real value is flexibility. You can study the implementation, modify it,
remove modules, add new workflows, connect your own backend or licensing system, redesign the UI and build
your own product around the codebase.

If your goal is to own and develop a Delphi-based MTK solution instead of using a closed compiled tool,
DelphiMTKClient is built for that purpose.

Contact

For source code licensing, pricing or technical questions, contact us through the official communication channel.

Telegram / Contact: https://t.me/GsmCoder

DelphiMTKClient Source Code, Delphi MediaTek Protocol